[JBossWS] - Re: Unmarshalling Exception with Web Service Array Input
by sumitsu
I tried using wstools to generate the WSDL, and although there were some differences, notably in that wstools split the schema in two and imported one schema into the other, the stack trace upon invocation did not change at all. I did notice that wstools, unlike wscompile, did not create LiteralSerializers and request/response struct classes, but it may just be that I don't have the settings on wstools to keep source artifacts enabled; I'm not sure.
What I would really like to know is where it is coming up with the com.liaison.InboundWebService.messageProcessing.Array class reference for which the "No ClassLoaders found" exception is being thrown -- I don't recall ever seeing a wscompile/wstools artifact by that name, nor can I find any such references in any of the generated files. Do you know where that comes from, or why it expects that class to exist? I would think that if I could find that out, it might help find the root cause of the problem.
Thanks again for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092758#4092758
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092758
17 years
[JBossWS] - WSSecurity failure on Linux
by PeterJ
I have just spent the better part of a day trying to figure out why my Web service, which uses WSSecurity to either encrypt or sign my messages, works on Windows but not on Linux. What really bugged my is that no matter whether I built the Web service and client on Windows or on Linux, the resulting JARs would work on Windows but not Linux. In other words, I could build on Linux, and those JARs failed on Linux but worked on Windows. And vice-versa.
The error?
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: org.jboss.ws.core.CommonSOAPFaultException: This service requires <wsse:Security>, which is missing.
| at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:69)
| at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
| at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
Then inspiration struck. While attempting to debug the situation, I noticed that log4j correctly picked up its configuration file on Windows, but not on Linux. Apparently on Windows, the client's JAR files are placed first in the classpath, but on Linux they are placed last. Which caused a stray log4j configuration file to be used on Linux. (And yes, I did remove the "-Dlog4j.configuration=wstools-log4j.xml" option from the command line in wsrunclient. Not sure who thought it was a good idea to prevent users from defining their own log4j configuration files.)
Anyway, I changes the order in which the classpath was built, moving the following code in wsrunclient.sh:
while [ $# -ge 1 ]; do
| case $1 in
| "-classpath") WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$2"; shift;;
| *) args="$args \"$1\"";;
| esac
| shift
| done
before these lines:
# Setup the client classpath
| WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/log4j.jar"
| WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar"
The Web service now works correctly on Linux.
Any possibility that the wsrunclient.sh could be permanently fixed?
What I was running:
JBoss 5.0.0 beta3 pulled on Sept 27, which appears to contain jbossws-native-2.0.1.SP1
I checked JBossWS 2.0.0.GA and 2.0.1.GA, and both of their wsrunclient.sh files have the same problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092751#4092751
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092751
17 years
[JBossWS] - wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java
by nirre
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
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092639#4092639
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092639
17 years