Marc,

I believe I have done this.  I have many ejb-ref's some in the same jar and
several in the other jars there are no complains deploying the beans where the
ejb-ref points to a bean in the same .jar  Of course I might be making some
sort of XML error, but as I say the beans/refs local to the jar seem to deploy
ok.


For instance here is a snippet of the jboss.xml for the orders.jar file it
references other beans as you see but it only complains about CustomerEnt
which is in a different jar.

 <entity>
     <ejb-name>OrderEnt</ejb-name>
     <jndi-name>OrderEnt</jndi-name>
       <ejb-ref>
          <ejb-ref-name>ejb/CustomerEnt</ejb-ref-name>
          <jndi-name>CustomerEnt</jndi-name>
        </ejb-ref>
       <ejb-ref>
          <ejb-ref-name>ejb/LargeOrderSes</ejb-ref-name>
          <jndi-name>LargeOrderSes</jndi-name>
        </ejb-ref>
       <ejb-ref>
          <ejb-ref-name>ejb/ItemEnt</ejb-ref-name>
          <jndi-name>ItemEnt</jndi-name>
        </ejb-ref>
       <ejb-ref>
          <ejb-ref-name>ejb/ItemEnt</ejb-ref-name>
          <jndi-name>ItemEnt</jndi-name>
        </ejb-ref>
   </entity>


thanks
Tom




 > in jboss.xml of bean a specify the jndi name of bean b (under ejb-ref)
> 
> marc
> 
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of
> |[EMAIL PROTECTED]
> |Sent: Saturday, February 03, 2001 3:50 PM
> |To: [EMAIL PROTECTED]
> |Subject: [jBoss-User] Revisting Multiple Jar files.
> |
> |
> |Dear all,
> |
> |I found the email below in the archives about some of the 
> |challenges of using
> |multiple jar files and I am having problems in this area.
> |
> |I am trying to do this 
> |
> |EJB JAR 'A'                  EJB JAR 'B'
> |bean 'a'      -- calls ->        bean 'b'
> |
> |I arrange for the EJB JAR B to be deployed first but when I try to 
> |deploy EJB
> |JAR A I get an error saying bean 'b' is not found within this application.
> |
> | I don't want to combine my beans into on jar file (and I would argue I
> |shouldn't need to).    I have tried putting the Home,Remote and 
> |implementation
> |classes of the bean 'b' into a seperate jar file in the CLASSPATH 
> |as well as
> |in the ext directory.
> |
> |Any assistance would be greatly appreciated.
> |
> |TIA
> |Tom Daly
> |
> |
> |
> |>From the Archives ...
> |
> |    Hi guys!
> |
> |    There were some threads about how you do things with multiple jars. So
> |    here are my $.02 :
> |    a) Be aware that beans in one jar can't access/see classes in other
> |    jars. It is intended to be that way.
> |    b) To solve a) some people suggest adding the jars to /lib/ext/ or
> |    extending the classpath to include the jars in the deployment 
> |directory.
> |    Be aware that there could be a big problem with that. Since the jar is
> |    in the classpath now and the container starts looking for 
> |ejb-jar.xml it
> |    may get it from the jar in the classpath and not from the jar it
> |    actually wants to deploy !
> |    c) There are two solutions I am aware of: 1) include everything in one
> |    jar and merge the descriptors or 2) only include the remote and home
> |    interfaces into one jar you can include into the class-path (NO
> |    ejb-jar.xml). Be careful with updates of your interfaces then.
> |
> |    Any other solutions ?
> |
> |    Ciao,
> |    Tobias
> |
> |
> |
> |
> |--
> |--------------------------------------------------------------
> |To subscribe:        [EMAIL PROTECTED]
> |To unsubscribe:      [EMAIL PROTECTED]
> |List Help?:          [EMAIL PROTECTED]
> |
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> List Help?:          [EMAIL PROTECTED]
> 




--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]

Reply via email to