Hi all,

    This question isn't unique to jboss, but I hope that it's something a
lot of people have thought about, and understand better than me...

    I'm trying to understand a good deployment scheme for a web application,
that is, where do my classes go?

    I've got the following categories of classes:

    1. EJB classes -- that is the XxxHome, XxxBean and Xxx classes
    2. Client classes -- mostly wrapper classes which find home interfaces,
create beans and delegate to them
    3. Bean implemenatation classes -- used by many of the XxxBean classes.
    4. Value object classes -- used by the EJB classes and the Client
classes. Other common support classes come into this catgory too.

My understanding of an EAR archive is: (ignoring war files for now)

    foo.ear:
        META-INF:
            MANIFEST.MF - can have class path
            application.xml - names application, lists ejb jar files and war
files
        bean1.jar:
            META-INF:
                MANIFEST.MF - auto generated, not very interesting
                ejb-jar.xml - bean deployment parameters
            Bean1.class
            Bean1Bean.class
            Bean1Home.class -- should I have other classes in bean1.jar
        bean2.jar:
            <like bean 1>

Now, I believe that I can have other files in the EAR file as mentioned in
the class path in the MANIFEST.MF:

        lib:
            this.jar - these jar files contain category 2, 3 and 4 classes
            that.jar

Does this make sense? What do other people do?

Thanks for any tips.

Tom

--
[EMAIL PROTECTED]     http://members.optushome.com.au/tomdavies


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to