* John Porter ([EMAIL PROTECTED]) [010824 09:52]:
> > 2. better shareability of components. Something more/different than
> > CPAN provides today.
>
> I still don't understand what this really means. J2EE comes from a
> single vendor. What "shareability" are you referring to as a model?
> And if you're just talking about shareability of components in
> general, there isn't anything better than CPAN, anywhere.
J2EE is a specification, not a product. Lots of vendors produce
Sun-certified 'J2EE-compliant' systems. Since the 'Sun-certified' part
of that can cost a pretty penny, open-source systems (like the
excellent JBoss) have to play semantic games by calling their systems
'J2EE-based'. Irritating.
In any case, you can't really download J2EE. Yes, there's a J2EE
reference implementation, but it's just another J2EE-compliant
system. AFAIK, nobody actually uses it. (Lots of people use the
reference Servlet/JSP container -- Tomcat -- but not the J2EE
reference implementation.)
About the general J2EE topic (this isn't directed at you John): I
think creating such a thing for Perl would be fraught with
difficulties. There are so many alternatives right now for doing
something simple like sending mail that finding a common ground for
complicated tasks like application servers would be extremely
difficult.
Additionally, who would create such a specification? The Perl
community can (IMO) be so suspicious of any attempts to 'unify'
certain aspects of it that such a thing would never get off the
ground. (Many times this suspicion may be justified, but I think it's
part of the culture.)
Not to be a naysayer, but it just seems that Sun is in a fairly unique
position to be issuing such specifications.
Chris
--
Chris Winters ([EMAIL PROTECTED])
Building enterprise-capable snack solutions since 1988.
