The problem is that the specs are not well defined in this regard in
my opinion. The approach taken by JBoss is that if you have
created an ear with ejbs and wars, the wars are likely to call the ejbs
so why not simplify the deployment of the wars by not requiring the
ejb classes to be redundantly bundled. It would be great of the specs
were explicit, but so many steps in deployment are left to the "Deployer"
role and the app server tools that is makes it hard to define a simple
developer created ear package(I guess).
----- Original Message -----
From: "Remus Jivcu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 24, 2001 11:59 PM
Subject: Re: [JBoss-user] Classloader problem in ear
> Scott M Stark wrote:
>
> > This is the expected behavior given the current ear deployer. EJB classes
> > are made available to wars and if you put you servlets in the ejb-jar archive
> > it will be seen there first as this is ahead of the war classes. If you don't
> > want this behavior only include the servlet in the war.
>
> Hi Scott,
>
> Thanks for your answer. Now I understand the different behaviours mentioned in my
> post.
>
> But I have another question. I guess this is not written anywhere in any spec,
> but why classes in the war file should be aware of classes in EJB jar file ? One
> needs only home and remote interfaces in war file for all EJBs deployed and
> that's it ... Or is there something more ?
> I assume that this is probably an optimization of JBoss architecture, also being
> spec compliant. But the question still remains : shouldn't be a clear separation
> between classloaders and classes from EJB jars and war files ?
>
> Thanks in advance,
>
> Remus.
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
