Hello,
> 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.
I am not sure I completely agree with you.
Sometimes, when you think your application can't fit in J2EE, it may be
because you have tried to mimic to much the original design. It doesn't mean
that is the case here, but who knows! Furthermore, the hot-deployement
feature is not a design issue: in this case you have to choose the app
server vendor that fits your needs. But it is always the case for other
parts as well(persistence tool, deployement tools, management tool, ...)
Then, if you are going to make some "proprietary" developments, why not
instead use an app server that offer what you need (hot-deployement) and
make proprietary developments part of JMX service (that are more and more
available in app servers)? There are some app servers that offer
hot-deployement features.
I am really not sure I would rebuilt my own app server using available
frameworks... would the cost be worth?
Cheers,
Sacha
===========================================================================
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".
