pluggable EJB modules 2004-02-02 - By Milen Dyankov
Back
Hi all,
I'm thinking of writing J2EE application and I wander if I can make my
EJB modules somewhat pluggable.
What I mean is having one main EJB module (say MainApp) which looks for
another modules under given JNDI names.
For example I may look for accounting module under "MainApp/accounting",
HR module under "MainApp/hr", etc.
Then for example I can have many, customer specific, accounting modules
(using different databases, data structures, etc..).
As long as they all have one and the same main controller bean (say
ControlerSLSB) I will be able to deploy
(or not deploy at all if not needed) a different version of any given
module for different customer.
What I'm thing to do is web front-end for a few different applications.
Suppose a customer A uses some HR management software which is
completely different from the software company B uses.
If I can develop my application to use modules I would have all
application logic (reports, analysis, forecasts, ...)
in my main application and simply deploy a specific module to
communicate with underlying application.
Does this make any sense? So far I see no reason why something like this
should not work,
but it already happened to me that things I have considered simple,
turned out to be impossible.
Is what I'm trying to do a common thing or rather a weird one?
Any comments will be highly appreciated!
Thanks,
Milen Dyankov
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
|
|
