I've been thinking on the same subject some time ago, and it seems
that the whole J2EE spec assumes that you build a complete
application out of several web applications and/or EJBs and then deploy
them at once (just check the roles they define).
One of the problems with dynamic EJB discovery process has to do with
how the calls are made from the client to the EJB implementation. If your
core package does not have direct access to the add-on home/remote
interfaces
(since they are not packaged in), you're going to find yourself in a very
server-specific area (class loading and so on)...
If you want this kind of loose-coupling between you components, maybe you
should consider a diferent approach (e.g: message-driven beans and/or
web-services)...
Philippe.
----- Original Message -----
From: "Duarte Nuno Loreto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: terça-feira, 18 de junho de 2002 17:10
Subject: [JBoss-user] Question about B2B and <ejb-ref>
> Hello!
>
> On the project I'm working on, we have several EJBs that constitute the
main
> application ("core" from now one). We also have other EJBs that contain
> business logic ("add-ons" from now on). We are using
> JBoss2.4.6_Tomcat-4.0.3.
>
> One of the EJBs on the core has code to dinamically call EJBs on the
> add-ons. The core EJB reads from a XML file the name of the add-on class,
> the method and necessary parameters and calls it.
>
> The purpose of the application includes adding new add-on EJBs and call
them
> just by adding entries to the configuration XML file (that is not
deployed,
> it resides on the $JBOSS_DIS/conf/<project-name> directory).
>
> Now we have a problem. We are packing the core EJBs and add-on EJBs on the
> same .ear. We want to break up this in to applications and deploy them
> separatly. So that more add-on EJBs can be deployed without having to
> redeploy the core. But we are facing a problem...
>
> The descriptor of the core EJB that makes the dynamic invocations seems to
> need the <ejb-ref> tag for each one of the add-on EJBs. So, adding a new
EJB
> to the add-on group would always force us to redeploy the core module with
> the new descriptor.
>
> Is this really necessary? Is there any way we can deploy core with no
> ejb-refs and make core know about the new EJBs as we deploy them?
>
> I thank you for reading my question. Hope to hear from you.
>
> Duarte Loreto
>
> --------------------------------------------------------------------------
--
> Bringing you mounds of caffeinated joy
> >>> http://thinkgeek.com/sf <<<
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
