RE: [ebxmlms-general] MSH and client WebApp on same web server

[<ant...@re...>]

To get this working you can download the source code from Sun for SAAJ,
modify the AttachmentPartImpl class and then recompile.
I can't remember the address at Sun to download the source but if you search
the site you should find it. Obviously you'll need to check the
licencing on what you can do with your changes but for testing I'm sure it's
fine.

For more details have a look at the sun java forums at
http://forum.java.sun.com/thread.jsp?forum=34&thread=240020

for the changes necessary

Anthony Ellis
Red Wahoo
-----------------------------
Tel:  +61 438 878 003
www.redwahoo.com


-----Original Message-----
From: ebx...@li...
[mailto:ebx...@li...]On Behalf Of Ronald van
Kuijk
Sent: Friday, March 14, 2003 1:05 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] MSH and client WebApp on same web server


Look at the message below (and the response from Sun), we ran into the
same issue on an internal project. It seems to be a bug in SAAJ

---------------------------------------------

Renzo Toma wrote:
 >
 > Hi Sun people,
 >
 > We have JAXM packaged in an EAR file and activation on the
 > systemclasspath of a BEA Weblogic server. When the AttachmentPartImpl
 > class (part of SAAJ) of JAXM is loaded in a static block it seems to
 > define the DataHandler.setDataContentHandlerFactory within Activation.
 > When the factory is already set Activation throws an Error exception
 > which JAXM does not catch properly and thus crashes JAXM.
 >
 > During development we want to redeploy our EAR a lot, but since
 > Activation crashes JAXM we are required to coldstart Weblogic.
 >
 > I checked with the latest Activation 1.0.2 and SAAJ 1.1.1 in WSDSP 1.1
 > and it's still here.
 >
 > To cope with this situation we may need to create a quick patch on
 > Activation which does not throw an Error exception.
 > But we hope you can fix this on your code.
 >

I talked to our people who own SAAJ and they believe it's a SAAJ problem
that they're going to try to address in a future release.

-------------------------------------------------

Or in short, you cannot have to apps on one server using the same saaj
implementation but deployed twice (in different ear/war/jar)

Ronald

simon čarni probeerde het volgende duidelijk te maken op 13-3-2003 23:52:

> Hi team.
> My situation is looks like this:
> I implemented MessageListener as a Servlet. Both, MSH and client are
> installed on same web server (Tomcat 4.0.4). When the mesage for my
> listener arrives I get following error:
>
> java.lang.Error: DataContentHandlerFactory already defined
>
> at
>
javax.activation.DataHandler.setDataContentHandlerFactory(DataHandler.java:6
28)
>
> at
>
com.sun.xml.messaging.saaj.soap.AttachmentPartImpl.<clinit>(AttachmentPartIm
pl.java:35)
>
> at
> com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:124)
>
> at
>
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageFact
oryImpl.java:32)
>
> at hk.hku.cecid.phoenix.message.handler.Request$Monitor.run(Unknown
> Source).
>
> I assume that on one web server only one DataContentHandlerFactory can
> be defined. Is there any way to get around this problem???
>
> If I just simply copy-paste the client web app to another server it
> works without any mistakes, but would really like to have both (MSH
> and client) on same server.
>
> Thank's in advance
>
>
>
> Simon
>
>
>
>
>





-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general