Hi All,
We have followed this directory structure (lets call it STRUCTURE) for one
of our EJB developments. I would like to see what people feel about this
STRUCTURE and compare against one of the proposed alternatives for the next
development phase. I have listed the alternative under ALT_STRUCTURE.

----------------------------------------------------------------------------
----
++++++++++
STRUCTURE
++++++++++

ModuleA - Parent package having beans belonging to this module

ModuleA.Interfaces - package containing all the interfaces (Remote, Home)
pertaining to Entity beans belonging to the ModuleA

ModuleA.Exceptions - Contains all the application level exceptions used in
ModuleA

ModuleA.DBWrappers - Utility data objects, primay keys pertaining to Entity
Beans of ModuleA

ModuleA.Server - Implementation classes of Entity Beans belonging to ModuleA

ModuleA.Session - Subpackage to hold the session bean packages which act on
the above entity beans

ModuleA.Session.Interfaces - Interfaces belonging to Session Beans which
operate on Enity Beans belonging to ModuleA

ModuleA.Session.Server - Implemenation classes of Session Beans belonging to
ModuleA

This way, no matter how many beans(1..*) are there in that module, their
implementation details would be within these 6 packages. No single bean has
its "own space" (if you will) in the package structure.


+++++++++++++++++
ALT_STRUCUTURE
+++++++++++++++++
ModuleA - same as above

ModuleA.Bean1- Parent package for bean1

ModuleA.Bean1.Entity - All constructs which go to constructing Bean1.
Includes Home, Remote interfaces, Bean implementation and any data objects.

ModuleA.Bean1.Session - All constructs which go to building session beans
(if any)that would work with Bean1.Includes Home, Remote interfaces, Bean
implementation and any data objects.


This way for N number of beans, we would have
ModuleA.Bean1..N                - Parent packages
ModuleA.Bean1..N.Entity  - Entity bean packages
ModuleA.Bean1..N.Session - Session Bean packages

But, each bean can exist within its own space in the package structure.

----------------------------------------------------------------------------
---------
I would really appreciate the opinions of this list about these 2 structures
especially regarding packaging wrt J2EE as
1.      as a module with one jar containing all the bean classes
2.      as a module with one jar containing all the individual beans as jars
themselves
3.      Usage of these beans/modules in clients (servlets, etc)



If someone feels there is even a better way, I am all ears here.

Thanks for your patience.
Madhu

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to