RE: Muse on WebLogic?

[Campana Jr., Salvatore J]

Title: Message

I added a default constructor to MuwsAxisServlet which should resolve that issue....but....

 

As for the QName issue...This is an issue with portability.  Weblogic's version of QName obviously does not support the QName constructor with 3 arguments. Even though the webapp contains the correct/expected version of QName it is not being picked up because of the Weblogic classloader.   You will probably run into allot of these sorts of things, especially when it comes to the implementation of SOAPElement.....In a previous project we had worked through these sorts of issues, so it can be done...unfortunately it is a matter of working through these issues as they arise....The classloader assigned by Weblogic for the webapp has some context already and that is where the mismatches will occur....

 

Porting the code to BEA is not a high priority for the project, it is viewed as an enhancement.  We wanted to make it portable, but do not have the cycles to port it as of right now.  If you would like to attempt to work through this and supply patches, that would be great.  Feel free to ping the list with questions etc...

 

-Sal

---

From: Joseph Kueser [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 12:56 PM
To: [EMAIL PROTECTED]
Subject: RE: Muse on WebLogic?

Thanks Sal,

 

Yes, I am trying to deploy this as a webapp.  Weblogic claims it deployed ok, but I still get the error messages shown below, and the ResourceManagerServlet isn't accessible.

 

If I ever figure this out, I'll make sure to let you guys know.  I don't mind treading on new ground when necessary, but I'll still happily take any help I can get.

 

Thanks again!

 

Joe Kueser

Gestalt, LLC

 

 -----Original Message-----
From: Campana Jr., Salvatore J [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 12:13 PM
To: [EMAIL PROTECTED]
Subject: RE: Muse on WebLogic?

The Muse implementation was designed to be portable to other SOAP platforms.  The portability would rely on a number of things.  My first thought is this...How did you deploy this to Weblogic?  Are you simply deploying our webapp to Weblogic?  In this case, the webapp is Axis, so you are effectively running Axis in Weblogic.....Please let us know if that is what you are trying to do.

 

You should know that while an abstraction layer has been maintained for portability, no attempts have been made to run Muse on Weblogic.  You are treading on new ground....

 

-Sal

---

From: Joseph Kueser [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 11:57 AM
To: [EMAIL PROTECTED]
Subject: Muse on WebLogic?

Hi, I'm new here, so please excuse my ignorance.  That will fade with time.

 

We're experimenting with Muse, working toward a WSDM solution, and have managed to get the tutorials and our own *WSResource classes working fine and dandy under Tomcat.  One of our first real tasks is going to be creating a JMX/WSDM Adapter for an existing project we have.  Now the problem is that the application that we need to attach to runs under WebLogic, and there's no getting around that.

 

So, I was hoping that someone here could give me some guidance on getting Muse to work under WebLogic.  I know just enough about Tomcat and WebLogic to be dangerous, but thought they were relatively drop-in compatible.

 

When I try to deploy either my homegrown WS Resource or one from the tutorials, I get the following errors at WebLogic startup (trimmed down a bit to make it easier on the eyes):

 

<Feb 2, 2005 11:20:29 AM EST> <Error> <HTTP> <BEA-101125> <[ServletContext(id=77
5647,name=muse,context-path=/muse)] Error occurred while instantiating servlet:
"ResourceManagerServlet".
java.lang.NoSuchMethodError: javax.xml.namespace.QName.<init>(Ljava/lang/String;
Ljava/lang/String;Ljava/lang/String;)V
        at org.apache.ws.muws.Muws05Constants.<clinit>(Muws05Constants.java:53)
        at org.apache.ws.resource.properties.impl.XmlBeansResourcePropertiesMana
gerImpl.<clinit>(XmlBeansResourcePropertiesManagerImpl.java:88)
        at org.apache.ws.resource.AbstractXmlBeansWSResource.createPropertiesMan
ager(AbstractXmlBeansWSResource.java:210)
        at org.apache.ws.resource.AbstractWSResource.<init>(AbstractWSResource.j
ava:116)
        at org.apache.ws.resource.AbstractXmlBeansWSResource.<init>(AbstractXmlB
eansWSResource.java:87)
        at org.apache.ws.resource.AbstractXmlBeansWSResource.<init>(AbstractXmlB
eansWSResource.java:100)
        at axis.org.apache.ws.generated.registry.AbstractRegistryWsdmServiceWSRe
source.<init>(AbstractRegistryWsdmServiceWSResource.java:34)
        at axis.org.apache.ws.generated.registry.RegistryWsdmServiceWSResource.<
init>(RegistryWsdmServiceWSResource.java:41)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

...>

 

<Feb 2, 2005 11:20:30 AM EST> <Error> <HTTP> <BEA-101216> <Servlet: "ResourceMan
agerServlet" failed to preload on startup in Web application: "muse".
javax.servlet.ServletException: Servlet class: 'org.apache.ws.platform.axis.tran
sport.http.MuwsAxisServlet' doesn't have a default constructor
        at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(Servl
etStubImpl.java:1032)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
        at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubIm
pl.java:904)
        at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStub
Impl.java:883)
        at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
mpl.java:822)
        at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
ervletContext.java:3333)
        at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebApp
ServletContext.java:3290)
...>

 

Any help would be very much appreciated.

 

Joe Kueser

Gestalt, LLC