Hi Brian,
thank you for your answer, but I think, this is not a WebSphere problem,
because my Mailetclass acts as a j2ee-client to the sessionbean and so the
james-classloader is responsible for loading the correct version of the
JavaMailAPI. Do you know, if James also works with older versions of the
JavaMailAPI (1.2 or 1.1) ?
Thanks,
Christian
|---------+---------------------------->
| | "Brian J. |
| | Sayatovic" |
| | <[EMAIL PROTECTED]> |
| | |
| | 22.07.2004 12:34 |
| | Please respond to|
| | "James Users |
| | List" |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------|
|
|
| To: James Users List <[EMAIL PROTECTED]>
|
| cc: [EMAIL PROTECTED]
|
| Subject: Re: James classloader problems
|
>--------------------------------------------------------------------------------------------------------------------------|
Christian,
WebSphere classloaders can be very tricky, and differ even between
WebSphere 4 and 5. Depending on the module visibilitiy you have
selected, WebSphere classloaders in WebSphere 4 typically DO NOT
delegate to their parent to load a class before looking in themselves.
In this "parent last" mode, your module will look in itself for classes
first and only delegate to the parent if its not found there. However,
in the J2EEApplicationMode module visibilty (settable via a system
property, not the admin screens), the parent is delegated to first.
Thus, any older version of JavaMail API in WebSphere's own classloader
would be loaded before yours. You can adjust the delegation mode via a
system property.
In WebSphere 5, there are different classloading settings, but they
allow you to achieve the same goals.
I suggest you use Google Groups opr your favorite news reader to search
the ibm.software.websphere.application-server newsgroup. Here's the
Google Groups link for it:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&group=ibm.software.websphere.application-server
Regards,
Brian.
[EMAIL PROTECTED] wrote:
>
>
>I have written my own mailets which parse the incoming mails and then call
>an sessionbean (which is running in the websphere applicationserver ) to
>store some informations about the mails in a database. It worked fine
while
>the James-Server was running in my testenvironment in WSAD
>(WebSphereStudio) but i cannot make it run in the production-system,
>because of classpath-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 which is required to access
the
>sessionbean. Does someone have an idea how to solve this problem ?
>I have tried to put the required jar-files into the lib-directory of the
>james-installation and also into the "SAR-INF\lib" - directory of the
>"james.sar" - file but nothing helped because the classloader always loads
>the JavaMail-API from "j2ee.jar" before the newest version from
>"mail-1.3.1".jar
>
>Thanks
>Christian
>
>
>---------------------------------------------------------------------
>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]
