We run James inside WebSphere 5 and access EJBs from within Mailet.
When you do it this way you do not need to copy the WebSphere jars into
the James folder as they are found in the normal classloader hierarchy.

If you are running James and WebSphere in separate VMs (it sounds like
you are but I'm not 100% clear on that), try putting the mail jar and
the WebSphere jars at different levels in the classloader chain such
that the mail jar is found before the j2ee jar.   E.g. put the WebSphere
jars into the phoenix lib dir and the mail jar into the SAR-INF lib.  Or
put the mail jar into the phoenix ext directory.

Steve

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Thursday, July 22, 2004 1:59 AM
To: James Users List
Subject: Re: James classloader problems





Hi,

i am working with James 2.2.0 (Phoenix 4.0.1) and WebSphere 5.1.0 (which
uses "J2RE 1.4.1 IBM build cxia321411-20031011").
When i copy all required files for a WebSphere5-client (j2ee.jar,
naminclient.jar, naming.jar, implfactory.properties) to the
"SAR-INF\lib" - directory of the "james.sar", i get the errormessage
"java.lang.NoClassDefFoundError:
com/ibm/ejs/ns/jndi/CNInitialContextFactory". If i remove the file
"mail-1.3.1.jar", from "james.sar" then i get the errormessage
"org.apache.avalon.phoenix.interfaces.ApplicationException:
com/sun/mail/util/SharedByteArrayInputStream". I am not sure, that IBM
supports the upgrading of the j2ee for WebSphere




|---------+---------------------------->
|         |           Danny Angus      |
|         |           <[EMAIL PROTECTED]|
|         |           co.uk>           |
|         |                            |
|         |           22.07.2004 09:52 |
|         |           Please respond to|
|         |           "James Users     |
|         |           List"            |
|         |                            |
|---------+---------------------------->
 
>-----------------------------------------------------------------------
---------------------------------------------------|
  |
|
  |       To:       "James Users List" <[EMAIL PROTECTED]>
|
  |       cc:       (bcc: Christian Inzko/UNIQUARE/AT)
|
  |       Subject:  Re: James classloader problems
|
 
>-----------------------------------------------------------------------
---------------------------------------------------|






> The problem is, that James needs the
> JavaMailAPI-Version 1.3.x and Websphere (Version 4 and 5) seems to 
> have
an
> older version included in the file j2ee.jar

Hmm, interesting problem.
Raise an enhancement request in JIRA and we'll look at it, but I'm not
going to make any promises.

If you could also include details of how james fails and other details
of versions and deployment it might help us.

I suppose theres no chance of you upgrading J2EE or just the javax.mail
part?

d.



************************************************************************
***
The information in this e-mail is confidential and for use by the
addressee(s) only. If you are not the intended recipient (or responsible
for delivery of the message to the intended recipient) please notify us
immediately on 0141 306 2050 and delete the message from your computer.
You may not copy or forward it or use or disclose its contents to any
other person. As Internet communications are capable of data corruption
Student Loans Company Limited does not accept any  responsibility for
changes made to this message after it was sent. For this reason it may
be inappropriate to rely on advice or opinions contained in an e-mail
without obtaining written confirmation of it. Neither Student Loans
Company Limited or the sender accepts any liability or responsibility
for viruses as it is your responsibility to scan attachments (if any).
Opinions and views expressed in this e-mail are those of the sender and
may not reflect the opinions and views of The Student Loans Company
Limit  ed.

This footnote also confirms that this email message has been swept for
the presence of computer viruses.

************************************************************************
**


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to