5 Replies Latest reply on Oct 14, 2007 6:06 AM by Niclas S

    wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java

    Niclas S Newbie

      Hi all.

      I have upgraded my application server to jboss 4.2 and with that the jbossws was uppgraded aswell. Now my ant scripts/config files wont work...

      The folllowing works in jboss 4.0.5GA:

      <configuration xmlns="http://www.jboss.org/jbossws-tools" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.jboss.org/jbossws-tools http://www.jboss.org/jbossws-tools/schema/jbossws-tool_1_0.xsd">
       <wsdl-java file="myWsdl.wsdl">
       <mapping file="jaxrpc-mapping.xml" />
       </wsdl-java>
      </configuration>


      And when I run this i get this error when using wstools.bat:

      Exception in thread "main" java.io.IOException: Cannot parse config: Failed to parse source: cvc-complex-type.3.2.2: Attribute 'file' is not allowed to appear in element 'wsdl-java'. @ *unknown*[3,69]
       at org.jboss.ws.tools.config.ToolsSchemaConfigReader.readConfig(ToolsSchemaConfigReader.java:141)
       at org.jboss.ws.tools.WSTools.generate(WSTools.java:67)
       at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
       at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: cvc-complex-type.3.2.2: Attribute 'file' is not allowed to appear in element
       'wsdl-java'. @ *unknown*[3,69]
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:178)
       at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:169)
       at org.jboss.ws.tools.config.ToolsSchemaConfigReader.readConfig(ToolsSchemaConfigReader.java:137)
       ... 3 more
      Caused by: org.xml.sax.SAXException: cvc-complex-type.3.2.2: Attribute 'file' is not allowed to appear in element 'wsdl-java'. @ *unknown*[3,69]
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:348)
       at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
       at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source)
       at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
       at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
       at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
       at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
       at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:174)
       ... 5 more


      when searching the internet I´ve come across lots of people using the file attribute (+it tworks with jboss 4.0.5).

      Would be great if someone could shed some light on the matter for me. Any help is appreciated, links, other resources etc (Ihave looked at JbossWs page in manuals but no luck...).

      thanks in advance
      nirre

        • 1. Re: wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java
          Niclas S Newbie

          fixed it... i must say it was kinda of an obscure fix...

          added the following in wstool.bat:

          set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/wsdl4j.jar
          set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxrpc.jar
          set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxws.jar
          set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jboss-saaj.jar
          


          and change the "file"attibute to "location" in the wstool-config.xml ...

          but thanks anyway.

          IF someone knows why or have comment of the problem/fix I'm very interessed!!

          regards
          nirre

          • 2. Re: wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java
            Richard Opalka Newbie

            And which JBossWS version are you using? You can see it in the system console when server boots.

            Richard

            • 3. Re: wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java
              Niclas S Newbie

              then one included in jboss 4.2 - jbossws-1.2.1.GA (build=200704151756)

              I have another problem now. Wstool now (with the above mentioned version) generates "strange array data types" in the jax-rpc file (and it does not generate the corresponding java files) - they where not generated when using the jbossws 1.03 (the one incuded in jboss 4.0.5)...

              At runtime I know get errors like:

              [EndpointMetaData] Cannot load class for type: {http://company.com/theIntegration}ArrayOfOpportunityID,com.company.theIntegration.ArrayOfOpportunityID


              and then I get a:

              RemoteException occured when invoking web service method!java.rmi.RemoteException: Call invocation failed; nested exception is:
               java.io.IOException: Could not transmit message


              I dont want to edit the jax-rpc file manually so my question is if arrays is handled differently between the versions.

              My integrations do work when I use jboss 4.0.4GA and 4.0.5GA (and respective "standard jbossws" for the releases) but I have some difficulties then It comes to the one incuded in jboss4.2.

              It would be great If anyone have some resources, links that I could go to to learn more. I have looked trough some of the documention found at the jbossws site but I think I´m following the examples etc...

              regards
              Niclas

              • 4. Re: wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java
                Alessio Soldano Master

                 

                "nirre" wrote:
                then one included in jboss 4.2 - jbossws-1.2.1.GA (build=200704151756)

                I have another problem now. Wstool now (with the above mentioned version) generates "strange array data types" in the jax-rpc file (and it does not generate the corresponding java files) - they where not generated when using the jbossws 1.03 (the one incuded in jboss 4.0.5)...

                At runtime I know get errors like:
                [EndpointMetaData] Cannot load class for type: {http://company.com/theIntegration}ArrayOfOpportunityID,com.company.theIntegration.ArrayOfOpportunityID


                and then I get a:

                RemoteException occured when invoking web service method!java.rmi.RemoteException: Call invocation failed; nested exception is:
                 java.io.IOException: Could not transmit message



                This seems to me the same as http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120947.
                I also invite you to create a minimal application reproducing the bug and attaching it to a new tools-jaxrpc jira issue. Then the community might take care of it.
                Thank you

                • 5. Re: wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java
                  Niclas S Newbie

                  I rewrote the build script and used wsconsume instead and had to rewrite some of my beans etc etc, but eventually I got it working.

                  I still think the change of behaviour of the wtools is strange.

                  thanks anyway.

                  /niclas