[JBossWS] - jax-rpc/wstools genereate problem
by nirre
Hi all.
I'm having some problems upgrading my environment from jboss 4.0.5 to jboss 4.2 - I'm running the jobossws/wstools included in the respective release:
jboss 4.0.5GA - jbossws-1.0.3.SP1 (date=200609291417)
jboss 4.2GA - jbossws-1.2.1.GA (build=200704151756)"
I'm not running any jbossws installation outside of the jboss appservers.
I'm using jdk1.5.0_11.
The problem is that the code/tools run fine on the jbossws-1.0.3.SP1
but does not work well with the jbossws-1.2.1.GA (build=200704151756). I'm now trying to track down what I have to change/add/remove. Some issues have been with the code itself how the artifacts are generated etc that is all fixed and ok.
But there are still issues in the generating of the artifacts.
part of the wsdl:
<s:element name="GetAllExternalSalesProjectNrsResponse">
| <s:complexType>
| <s:sequence>
| <s:element minOccurs="0" maxOccurs="1" name="GetAllExternalSalesProjectNrsResult" type="tns:ExternalSalesProjectNrsResult" />
| </s:sequence>
| </s:complexType>
| </s:element>
| <s:complexType name="ExternalSalesProjectNrsResult">
| <s:sequence>
| <s:element minOccurs="0" maxOccurs="1" name="Result" type="tns:OperationResult" />
| <s:element minOccurs="0" maxOccurs="1" name="SalesNumbers" type="tns:ArrayOfExternalSalesNumbers" />
| </s:sequence>
| </s:complexType>
| <s:complexType name="OperationResult">
| <s:sequence>
| <s:element minOccurs="1" maxOccurs="1" name="Success" type="s:boolean" />
| <s:element minOccurs="1" maxOccurs="1" name="ResultCode" type="s:int" />
| <s:element minOccurs="0" maxOccurs="1" name="ResultDescription" type="s:string" />
| </s:sequence>
| </s:complexType>
| <s:complexType name="ArrayOfExternalSalesNumbers">
| <s:sequence>
| <s:element minOccurs="0" maxOccurs="unbounded" name="ExternalSalesNumbers" nillable="true" type="tns:ExternalSalesNumbers" />
| </s:sequence>
| </s:complexType>
| <s:complexType name="ExternalSalesNumbers">
| <s:sequence>
| <s:element minOccurs="0" maxOccurs="1" name="Nr" type="s:string" />
| </s:sequence>
| </s:complexType>
The interesting thing with the wsdl is the ArrayOfExternalSalesNumbers there are several of these "structures" in the wsdl.
When I use jbossws-1.0.3.SP1 these does not show up in the jaxrpc-mapping.xml file and artefacts/classes does not get generated ..
BUT when I use jbossws-1.2.1.GA I get the following in my jaxrpc-mapping.xml:
<java-xml-type-mapping>
| <java-type>com.company.theIntegration.ArrayOfExternalSalesNumbers</java-type>
| <root-type-qname xmlns:typeNS='http://company.com/theIntegration'>typeNS:ArrayOfExternalSalesNumbers</root-type-qname>
| <qname-scope>complexType</qname-scope>
| <variable-mapping>
| <java-variable-name>externalSalesNumbers</java-variable-name>
| <xml-element-name>ExternalSalesNumbers</xml-element-name>
| </variable-mapping>
| </java-xml-type-mapping>
BUT no ArrayOfExternalSalesNumbers classes are generated...??
When I then run my application server I get the following warnings:
| [EndpointMetaData] Cannot load class for type: {http://company.com/theIntegration}ArrayOfExternalSalesNumbers,com.company.theIntegration.ArrayOfExternalSalesNumbers
| 09:18:47,347 WARN [EndpointMetaData] Cannot load class for type: {http://company.com/theIntegration}ArrayOfOpportunityID,com.company.theIntegration.ArrayOfOpportunityID
| 09:18:47,363 WARN [EndpointMetaData] Cannot load class for type: {http://company.com/theIntegration}ArrayOfSalesTeamRecord,com.company.theIntegration.ArrayOfSalesTeamRecord
| ... etc etc
|
.. and of course the runtime error:
RemoteException occured when invoking web service method!java.rmi.RemoteException: Call invocation failed; nested exception is: java.io.IOException: Could not transmit message
My wstool-config.xml looks like this:
<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 location="resources/META-INF/wsdl/theIntegration.wsdl">
| <mapping file="jaxrpc-mapping.xml" />
| </wsdl-java>
| </configuration>
and my ant task:
| <wstools dest="${wsgenerated}" config="${conf}/wstools-config.xml"/>
Right now I'm kinda stuck :( I have looked trough the JAX-RPC Userguide 1.2 & 2.0 but from the looks of it I'm doing what the guides say...
Is there any parameter I should use in the wstools generation??
Why is there a difference in the generation?
many thanks in advance for any input at all .... ;)
regards
Niclas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093889#4093889
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093889
17 years
[JBossWS] - Re: SoapFault on returning the web service response
by ggary
So, you think that namespace is the solution to the problem?
I am sure that you are wrong. I did try your suggestion but it did not work.
I made this change:
@WebMethod(operationName="processSpamComplaints")
| @WebResult(name="spamResult",targetNamespace="http://service.responsys.com/rsystools/ws/SpamComplaintWS/1.0")
| @ResponseWrapper(localName="result",className="com.rsys.rsystools.ws.SpamResult",
| targetNamespace="http://service.responsys.com/rsystools/ws/SpamComplaintWS/1.0")
| public SpamResult processSpamComplaints(
|
I did not create RequestWrapper because
a)I am not passing in an instance of class but just few strings.
b)passed in parameters are processed correctly.
So, when I redeployed my service generated wsdl looked like:
<definitions name="SpamComplaintWSService" targetNamespace="http://service.responsys.com/rsystools/ws/SpamComplaintWS/1.0">
| ?
| <types>
| ?
| <xs:schema targetNamespace="http://service.responsys.com/rsystools/ws/SpamComplaintWS/1.0" version="1.0">
| <xs:element name="processSpamComplaints" type="tns:processSpamComplaints"/>
| <xs:element name="result" type="tns:result"/>
| ?
| <xs:complexType name="processSpamComplaints">
| ?
| <xs:sequence>
| <xs:element minOccurs="0" name="email" type="xs:string"/>
| <xs:element minOccurs="0" name="fromAddress" type="xs:string"/>
| <xs:element minOccurs="0" name="mailDate" type="xs:string"/>
| <xs:element minOccurs="0" name="complaintDate" type="xs:string"/>
| <xs:element minOccurs="0" name="mailbox" type="xs:string"/>
| <xs:element minOccurs="0" name="complainer" type="xs:string"/>
| <xs:element minOccurs="0" name="xRext" type="xs:string"/>
| <xs:element minOccurs="0" name="accountName" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| ?
| <xs:complexType name="result">
| ?
| <xs:sequence>
| <xs:element form="qualified" minOccurs="0" name="spamResult" type="tns:result"/>
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
| </types>
| ?
| <message name="SpamComplaintWS_processSpamComplaints">
| <part element="tns:processSpamComplaints" name="processSpamComplaints"/>
| </message>
| ?
| <message name="SpamComplaintWS_processSpamComplaintsResponse">
| <part element="tns:result" name="result"/>
| </message>
| ?
| <portType name="SpamComplaintWS">
| ?
| <operation name="processSpamComplaints" parameterOrder="processSpamComplaints">
| <input message="tns:SpamComplaintWS_processSpamComplaints"/>
| <output message="tns:SpamComplaintWS_processSpamComplaintsResponse"/>
| </operation>
| </portType>
| ?
| <binding name="SpamComplaintWSBinding" type="tns:SpamComplaintWS">
| <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
| ?
| <operation name="processSpamComplaints">
| <soap:operation soapAction=""/>
| ?
| <input>
| <soap:body use="literal"/>
| </input>
| ?
| <output>
| <soap:body use="literal"/>
| </output>
| </operation>
| </binding>
| ?
| <service name="SpamComplaintWSService">
| ?
| <port binding="tns:SpamComplaintWSBinding" name="SpamComplaintWSPort">
| <soap:address location="http://127.0.0.1:80/rsystools/ws/SpamComplaintWS"/>
| </port>
| </service>
| </definitions>
and when I called the web service, the result was exactly like in my original post.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093745#4093745
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093745
17 years