On 2002.03.11 05:10:47 -0500 Alex Loubyansky wrote: > As For Me: > I consider jar file like a sentence in the text. A sentence expresses a > finished (complete) thought and I see jar file to contain some finished > (complete) set of class files to perform some task(s). Thus, including > helper-classes, state-holder-classes and not limited to only one EJB. I > think, it's insufficient to place each EJB in a separate jar file. > As to third party jar files, if my application is an ear file I'll put > them in the ear and set classpath in the manifest file. If I have many > ear > files need the same third party jar files then I'll add them in the > global > classpath. > > Other thoughts?
in jboss 3 and in jboss 2.4.x using the ScopedDeployer the classes in different ears can see each other as well. You still have to make sure they are deployed in the correct order to satisfy dependencies. david jencks > > alex > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, March 10, 2002 6:47 PM > > To: [EMAIL PROTECTED] > > Subject: [JBoss-user] general deployment question > > > > We have built a large number of session and bmp entity beans > > as part of our technology framework. For historical reasons > > we organized each entity bean (along with home and remote > > interfaces and primary key class) into a jar. Same with the > > session beans. In the deployment descriptors, we used the > > ejb-link tag to identify ejb references, even though the > > references were not in the same jar. Again, this was because > > the documentation at the time on all this stuff was not very > > good and we just had examples to go off of. Somehow, we get > > away with this in jboss, even though it's not correct to use > > ejb-link for references outside of a jar. Note, all the jar > > files, and there are about 30 now, are packaged into an ear. > > We then have a jboss.xml per jar which basically defines any > > jdbc references we may have as well as declares the jndi > > names for each of the beans in the ejb-jar.xml. > > > > We have a client who insists on using borland's app server > > (let's not get into why here...) and borland is choking, and > > i think rightly so, because the ejb-link references are to > > beans outside of the jar. My question is, why was i able to > > get away with this in jboss. > > > > In a related area, we have a fair number of helper classes > > that all these beans use (base classes for our beans, data > > structures to hold the data passed back to the client apps, > > etc.). Right now, we add jar files holding these classes, as > > well as third party jars, to the jboss classpath. Is this > > the right thing to do, or is the right thing to stuff these > > helper classes into each jar (or the ear file)... I > > apologize if this question seems basic, but we've spent more > > time just trying to make things work and less trying to > > understand every single aspect of this. Things are calming > > down a bit right now and I'd like to reexamine our approach > > here. Most of the documentation out there deals with > > relatively simple applications, or gets bogged down with > > discussions of war files, etc. (we're not a web app, at least > > not yet). > > > > Any help or suggestions would be much appreciated. As I've > > said, we've managed to get all this to work, though I think > > we have some configuration issues yet to deal with. > > > > Thanks > > > > Eric Kaplan > > Armanta, Inc. > > 55 Madison Ave. > > Morristown, NJ 07960 > > Phone: (973) 326-9600 > > > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
