Hello,
> But this is always a point of issue--a single vendor never has all the
> "right" parts. Some might have the O-R mapping layers I want, but won't do
> the correct remoting I want, and so on. EJB is a monolithic
> solution; I want
> to mix 'n match implementation components.
Well... it is an app server! It provides you facilities but if you need
other facilities, maybe this app server is not for you. App servers are not
the solution for all problems. And this is the same for J2EE, .NET, DNA,
WebObjects, ...
As for the monolithic thing, maybe. But you can still extend app servers or
integrate other services (JCA, ...)
While I don't think that app servers are THE solution to every problem, I
also don't think that app servers are the bad boy that allow to build
nothing but pet store web sites. You know, someone you meet people that say
that they prefer to code their financial application in Motorola 68000
assembler because "they can really fine tune memory and processor register
allocation"... ;) Well, sure...
> Whoa--JMX has nothing to do with what's going on here. JMX is
> about managing
> the server, not adding functionality to the services managed by the app
> server. This is completely orthogonal.
Here, I let Rickard answers ;)
You will love JMX :)
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".
