Thanks Charles.
You don't want to download the Sun J2EE package - Tomcat
supplies its own, and having both on your system at the
same time can lead to some interesting events.
Is this bad planning, or something a user should know
about and work
round? J2EE does get other uses.
As far as I can tell (Tomcat, JBoss, WebLogic, WebSphere),
all the J2EE players provide their own copy of the
necessary pieces of the J2EE jar from Sun, along with their
implementations of the interfaces and abstract classes,
plus their own extensions. Due to the complexity of J2EE
class loading, having the Sun (or any other) J2EE jar in
the classpath results in mixed resolutions - some classes
come from the desired location, others from the wrong
(possibly incompatible) one. Leads to much head-scratching.
So its primarily a classpath issue? I.e. its not a case of *don't
use J2EE* and ensure your classpath order is right.
I guess it is in the documentation... or is it? I'll check.
regards DaveP
--
DISCLAIMER:
NOTICE: The information contained in this email and any attachments is
confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of the
content of it or of any attachment; you are requested to notify the
sender immediately of your receipt of the email and then to delete it
and any attachments from your system.
RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants. However, it
cannot accept any responsibility for any such which are transmitted.
We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily represent
those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
