Ted Neward wrote:
>...
>
>Shone, I'm afraid that the explicit component management that you're looking
>for isn't there in EJB. What you *really* wanted, rather than porting the
>app over to EJB, was to use something that conformed to JSR-111, the
>Services API JSR, which isn't even close to being finished yet. :/ Having
>said that, though....
>
>...
>
>Had I been around when you were considering the port, I'd have suggested you
>not do it; unfortunately, that's water under the bridgework. You might take
>a look at Apache Avalon (Berin Loritsch is on the JSR 111 Expert Group) as
>another Services Framework, you might take a look at JNLP as a deployment
>framework, and I humbly suggest you might find a few ideas in my
>"Server-Based Java Programming" book.
>
>Ted Neward
>{.NET || Java} Course Author & Instructor, DevelopMentor
>(http://www.develop.com)
>http://www.javageeks.com/tneward
>
In addition to Avalon, you might look at HP's Common Services Framework
(underlying their HP-Internet Server and HP-Application Server) or the
Enhydra Services Architectures underlying the Lutris Enhydra App Server.
Both these frameworks are being considered as APIs or concept-sources
for the JSR-111 work and might be very useful to someone doing a mixture
of J2EE and custom-components (services). Of course, until/unless
JSR-111 (or JSR-159, which is probably better for this purpose because
it's J2EE-specific) blesses a standard, any work you do in this way is
subject to some level of vendor lock-in...
Wayne Stidolph
===========================================================================
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".
