RE: Deploying to Weblogic 10.3.1

Carl Roberts wrote:

Thanks Glen,

I will try your setup.  

BTW, since Oracle WebLogic claims to follow the Glassfish implementation and I couldn't get any further with my previous approach, I figured why not remove the metro webservices-*.jar files from my WEB-INF\lib directory and just go with the Weblogic implementation of Glassfish. Theoretically this should work.

Well,

I changed the web.xml to run the Implementation class directly by commenting out the listener:

<?xml version="1.0" encoding="UTF-8" ?>
- <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/j2ee">
  <display-name>DocumentServiceSoap11</display-name>
- <!--
  <listener>
    <listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
  </listener>
 

  -->
- <servlet>
  <servlet-name>DocumentServiceSoap11</servlet-name>
- <!-- <servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
  -->
  <servlet-class>com.oracle.webservices.documentservice.server.DocumentServiceImpl</servlet-class>
  <load-on-startup>0</load-on-startup>
  </servlet>
- <servlet-mapping>
  <servlet-name>DocumentServiceSoap11</servlet-name>
  <url-pattern>/DocumentService</url-pattern>
  </servlet-mapping>
- <session-config>
  <session-timeout>60</session-timeout>
  </session-config>
  </web-app>

And I am getting a little further I think, but now I am getting this error, indicating the Weblogic schema validator is not up to par with Metro's 2.0 one, because it is complaining about default attribute for xsd:element not being valid?  Isn't default attribute for xsd:element a standard attribute?  It seems like a schema that worked fine before under tomcat now has problems under Weblogic.

Here is the error from weblogic:

Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error [HTTP:101216]Servlet: "DocumentServiceSoap11" failed to preload on startup in Web application: "DocumentServiceImpl". javax.xml.ws.WebServiceException: org.xml.sax.SAXParseException: s4s-att-not-allowed: Attribute 'default' cannot appear in element 'element'. at com.sun.xml.ws.server.ServerSchemaValidationTube.<init>(ServerSchemaValidationTube.java:69) at com.sun.xml.ws.api.pipe.ServerTubeAssemblerContext.createValidationTube(ServerTubeAssemblerContext.java:221) at weblogic.wsee.jaxws.tubeline.standard.StandardTubelineDeploymentListener$13.createServer(StandardTubelineDeploymentListener.java:158) at weblogic.wsee.jaxws.WLSTubelineAssemblerFactory$TubelineAssemblerImpl.createServer(WLSTubelineAssemblerFactory.java:105) at com.sun.xml.ws.server.WSEndpointImpl.<init>(WSEndpointImpl.java:158) at weblogic.wsee.jaxws.WLSContainer$WLSEndpointFactory$WLSEndpointImpl.<init>(WLSContainer.java:413) at ''

This is getting a little frustrating.  I guess I am going to try going back to including the webservies-*.jar files and using saaj-impl-3.2.jar from Sun instead of 3.1 version.  I noticed the 3.2 version contains a META-INF\services directory with some factory classes while the 3.1 version I was using does not.  I am hoping this solves the problem.

 

-----Original Message-----
From: Carl Roberts [mailto:carl.roberts@oracle.com]
Sent: Friday, July 10, 2009 8:58 AM
To: glen.mazza@gmail.com
Cc: users@metro.dev.java.net
Subject: RE: Deploying to Weblogic 10.3.1

Hi Glen,

Thanks for your response.  Much appreciated. I tried your package names per the link you gave me instead of mine.  Here are the ones I am using now:

        <package-name>com.sun.xml.*</package-name>
      <package-name>javax.xml.bind.*</package-name>

But I am back to a different error that I saw before:

Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error weblogic.application.ModuleException:
Message icon - Error com.sun.xml.internal.messaging.saaj.soap.LocalStrings != com.sun.xml.messaging.saaj.soap.LocalStrings

I noticed the saaj-impl namespace is also com.sun.xml.* so I am wondering if it has to do with this.

I have also tried including the saaj-impl-1.3.jar file in the WEB-INF\lib directory of the war inside the ear and redeploying but I get the same error.  Have you seen this error before?

Do you have a sample ear file that you used for testing that I could try to deploy on my instance of Weblogic Server 10.3.1?

Thanks,

Joe

-----Original Message-----
From: Glen Mazza [mailto:glen.mazza@gmail.com]
Sent: Thursday, July 09, 2009 7:03 PM
To: users@metro.dev.java.net
Subject: RE: Deploying to Weblogic 10.3.1


I used somewhat different <p-a-p/s>--perhaps my list would help:
http://www.jroller.com/gmazza/entry/deploying_metro_and_cxf_based

Glen


Carl Roberts wrote:
>
>    <prefer-application-packages>
>
>       <package-name>javax.jws.*</package-name>
>
>         <package-name>javax.xml.soap.*</package-name>
>
>    </prefer-application-packages>
>
> </weblogic-application>
>
> The deployment process in Weblogic then complains that my service
> implementation class does not have @WebService or @WebServiceProvider
> annotation, but it does:
>

--
View this message in context: http://www.nabble.com/Deploying-to-Weblogic-10.3.1-tp24415730p24419290.html
Sent from the Metro - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
For additional commands, e-mail: users-help@metro.dev.java.net



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
For additional commands, e-mail: users-help@metro.dev.java.net



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
For additional commands, e-mail: users-help@metro.dev.java.net