array element type mismatch when client sends object[]
------------------------------------------------------
Key: MUSE-211
URL: https://issues.apache.org/jira/browse/MUSE-211
Project: Muse
Issue Type: Bug
Affects Versions: 2.1.0
Environment: Muse 2.1.0, JDK1.5
Reporter: Vinh Nguyen
Assigned To: Dan Jemiolo
Priority: Critical
I hope this isn't too late, but can this get fixed for the Muse 2.2 release?
It's a critical blocking issue for us.
When my client proxy tries to send an array of objects, I am getting an "array
element type mismatch" problem on the server side. This occurs in all Muse
releases, including today's nightly build 3/16/07. I suspect the problem
occurs where Muse is trying to cast the array to the appropriate type.
I finally was able to create a small test program to demonsrate this. Attached
is the project zip, which includes a folder containing the client/server trace
output. To test, run the com.cisco.testapp.Main class.
Below is the client output:
[CLIENT TRACE] SOAP envelope contents (outgoing):
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>
<soap:Header>
<wsa:To
xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://localhost:8080/TestApp/services/SimpleResource</wsa:To>
<wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://cisco.com/testapp/simple/array/ArrayOperation</wsa:Action>
<wsa:MessageID
xmlns:wsa="http://www.w3.org/2005/08/addressing";>uuid:13834aa9-876c-43b2-3bb5-025cb2aae886</wsa:MessageID>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing";>
<wsa:Address>http://www.w3.org/2005/08/addressing/role/anonymous</wsa:Address>
</wsa:From>
</soap:Header>
<soap:Body>
<pfx0:ArrayOperation xmlns:pfx0="http://cisco.com/testapp/simple/array";>
<pfx2:SecurityContext
xmlns:pfx2="http://schemas.cisco.com/Security";>
<pfx2:SecurityContext>
<xml-fragment>
<sec:username
xmlns:sec="http://schemas.cisco.com/Security";>user1</sec:username>
<sec:password
xmlns:sec="http://schemas.cisco.com/Security";>password1</sec:password>
</xml-fragment>
</pfx2:SecurityContext>
<pfx2:SecurityContext>
<xml-fragment>
<sec:username
xmlns:sec="http://schemas.cisco.com/Security";>user2</sec:username>
<sec:password
xmlns:sec="http://schemas.cisco.com/Security";>password2</sec:password>
</xml-fragment>
</pfx2:SecurityContext>
</pfx2:SecurityContext>
</pfx0:ArrayOperation>
</soap:Body>
</soap:Envelope>
[CLIENT TRACE] SOAP envelope contents (incoming):
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>
<soap:Header>
<wsa:To
xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://www.w3.org/2005/08/addressing/role/anonymous</wsa:To>
<wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
<wsa:MessageID
xmlns:wsa="http://www.w3.org/2005/08/addressing";>uuid:7af1ee04-5d0c-14f0-a2ec-3d59ca357352</wsa:MessageID>
<wsa:RelatesTo RelationshipType="wsa:Reply"
xmlns:wsa="http://www.w3.org/2005/08/addressing";>uuid:13834aa9-876c-43b2-3bb5-025cb2aae886</wsa:RelatesTo>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing";>
<wsa:Address>http://localhost:8080/TestApp/services/SimpleResource</wsa:Address>
</wsa:From>
</soap:Header>
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>soap:Receiver</soap:Value>
</soap:Code>
<soap:Reason>
<soap:Text>array element type mismatch</soap:Text>
</soap:Reason>
</soap:Fault>
</soap:Body>
</soap:Envelope>
org.apache.muse.ws.addressing.soap.SoapFault: array element type mismatch
at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:294)
at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:228)
at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:207)
at
com.cisco.testapp.proxy.simple.SimpleResourceProxy.arrayOperation(SimpleResourceProxy.java:35)
at
com.cisco.testapp.test.ArrayOperationTest.run(ArrayOperationTest.java:40)
at com.cisco.testapp.Main.main(Main.java:17)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
