Saaj classloader issues on Websphere

Question

I am getting the dreaded error on application startup.
E WSSERVLET11: failed to parse runtime descriptor: java.lang.NoSuchMethodError: javax/xml/soap/MessageFactory.newInstance(Ljava/lang/String;)Ljavax/xml/soap/MessageFactory;
java.lang.NoSuchMethodError: javax/xml/soap/MessageFactory.newInstance (Ljava/lang/String;)Ljavax/xml/soap/MessageFactory;
Has anyone been successful deploying the JAXWS stack on WAS 6.1? I tried setting it to use the application classloader first, but to no avail. There is a feature pack for WAS 6.1, but I think it only supports JAXWS 2.0 and I was hoping to use 2.1.

Answer 1

Hi Sabha,
I somehow feel dynamic proxies have an answer for this. didn;t do much of
research for realization of thought.
ofcourse given the fact there should be some external means to intimate the
server that the file has changed and from where to pickup the new version of
interface implementation from.
Does that make sense??
- Rajeev
"Sabha" <[email protected]> wrote in message news:[email protected]..
>
"Rajeev Dave" <[email protected]> wrote in message
news:[email protected]..
Hi EJB/Classloader gurus,
Environment: weblogic 5.1 sp 9, windows NT
1. I redploy a EJB by using the hot deploy facility
2. All clients who are using the bean are thrown Redployment Exception
3. The bean implementation class definition is immidiately replaced by
the
new class file
What I want is that the clients using this bean during the processs of
redployment should not be thrown an exception but be served by theprevious
version of the bean itself. Any new clients logging into the site shouldbe
servled by the new class files. So in essence, the bean should be slowly
phased out rather than a instantaneous replacement.
Weblogic currently does not support graceful shutdown and redeployment of
the Applications during redeployment.
Now taking this on a general note,
1. CustomClassloader1 loads class A
2. I want to replace the class A by a newer version of it in which justthe
implementation inside a couple of methods of class A are changed.
Once a class has been loaded by a classloader, another version of the same
class cannot be loaded nor can the class be unloaded.
One has to unload the entire classloader and instantiate a new classloader
to load the newer version of the class to achive this.
Is it possible to achieve this. I have been breaking my head on this forno
avail. Or any other approach to achieve this.
Any ideas are welcome.
- Rajeev Dave
-Sabha