<Resolvido> Problema com EJB´s JBOSS -

Programação Java
#1

Bom dia,
Galera eu estou tendo esse meu SessionBean Boleto, detalhe tenho outros sessionbeans que estão todos ok, não estou entendo pq esse está falhando:

java.lang.RuntimeException: javax.naming.NameNotFoundException: cim/Boleto

Segue meu jboss.xml:

[code]<?xml version="1.0" encoding="UTF-8"?>

java:/jaas/mic

 <!--
   To add beans that you have deployment descriptor info for, add
   a file to your XDoclet merge directory called jboss-beans.xml that contains
   the <session></session>, <entity></entity> and <message-driven></message-driven>
   markup for those beans.
 -->

  <session>
     <ejb-name>Boleto</ejb-name>
     <jndi-name>cim/Boleto</jndi-name>
     <configuration-name>SSL Clustered Stateless SessionBean</configuration-name>

      <clustered>true</clustered>
      <cluster-config>
          <partition-name>Greenline</partition-name>
          <home-load-balance-policy>org.jboss.ha.framework.interfaces.RoundRobin</home-load-balance-policy>
          <bean-load-balance-policy>org.jboss.ha.framework.interfaces.RoundRobin</bean-load-balance-policy>
      </cluster-config>

    <method-attributes>
    </method-attributes>
  </session>

<!--
  write a merge file jboss-webservices.ent for webservice-description 
-->

 <!--
   To specify your own assembly descriptor info here, add a file to your
   XDoclet merge directory called jboss-assembly-descriptor.xml that contains
   the <assembly-descriptor></assembly-descriptor> markup.
 -->
[/code]

ejb-jar.xml

[code]<?xml version="1.0" encoding="UTF-8"?>


Generated by XDoclet

  <!-- Session Beans -->
  <session >
     <description><![CDATA[]]></description>

     <ejb-name>User</ejb-name>

     <home>br.com.greenlinesaude.cim.service.interfaces.UserHome</home>
     <remote>br.com.greenlinesaude.cim.service.interfaces.User</remote>
     <ejb-class>br.com.greenlinesaude.cim.service.ejb.UserSession</ejb-class>
     <session-type>Stateless</session-type>
     <transaction-type>Bean</transaction-type>

  </session>

  <session >
     <description><![CDATA[]]></description>

     <ejb-name>Boleto</ejb-name>

     <home>br.com.greenlinesaude.cim.service.interfaces.BoletoHome</home>
     <remote>br.com.greenlinesaude.cim.service.interfaces.Boleto</remote>
     <ejb-class>br.com.greenlinesaude.cim.service.ejb.BoletoSession</ejb-class>
     <session-type>Stateless</session-type>
     <transaction-type>Bean</transaction-type>

  </session>

 <!--
   To add session beans that you have deployment descriptor info for, add
   a file to your XDoclet merge directory called session-beans.xml that contains
   the <session></session> markup for those beans.
 -->

  <!-- Entity Beans -->
 <!--
   To add entity beans that you have deployment descriptor info for, add
   a file to your XDoclet merge directory called entity-beans.xml that contains
   the <entity></entity> markup for those beans.
 -->

  <!-- Message Driven Beans -->
 <!--
   To add message driven beans that you have deployment descriptor info for, add
   a file to your XDoclet merge directory called message-driven-beans.xml that contains
   the <message-driven></message-driven> markup for those beans.
 -->

 <!--
   To specify your own assembly descriptor info here, add a file to your
   XDoclet merge directory called assembly-descriptor.xml that contains
   the <assembly-descriptor></assembly-descriptor> markup.
 -->
sys 
 <!--
   To specify additional method-permission elements, add a file in the merge
   directory called ejb-method-permissions.ent that contains them.
 -->
sys User * sys Boleto * 
 <!--
   To specify additional container-transaction elements, add a file in the merge
   directory called ejb-container-transactions.ent that contains them.
 -->

 <!--
   To specify additional message-destination elements, add a file in the merge
   directory called ejb-message-destinations.ent that contains them.
 -->

 <!--
   To specify an exclude-list element, add a file in the merge directory
   called ejb-exclude-list.xml that contains it.
 -->
[/code]
#2

Resolvido!

Eu estava com um problema no jar com meus ejbs e não tinha percebido

#3