You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Dan Jemiolo (JIRA)" <ji...@apache.org> on 2007/03/17 18:49:09 UTC
[jira] Closed: (MUSE-211) array element type mismatch when client
sends object[]
[ https://issues.apache.org/jira/browse/MUSE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Jemiolo closed MUSE-211.
----------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Fixed - see SVN message associated with this bug. Thanks again for the sample project and build file - it cut down on the debugging time immensely.
> 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
> Fix For: 2.2.0
>
> Attachments: TestApp.zip
>
>
> 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
RE: [jira] Closed: (MUSE-211) array element type mismatch when client sends object[]
Posted by "Vinh Nguyen (vinguye2)" <vi...@cisco.com>.
Yep, it works...thanks Dan!
-----Original Message-----
From: Vinh Nguyen (vinguye2)
Sent: Sunday, March 18, 2007 12:49 AM
To: muse-dev@ws.apache.org
Subject: RE: [jira] Closed: (MUSE-211) array element type mismatch when
client sends object[]
Thanks Dan for the quick fix! I will test this out as soon as possible,
and will let you know the results. Please enjoy the rest of your
weekend:)
-----Original Message-----
From: Dan Jemiolo (JIRA) [mailto:jira@apache.org]
Sent: Saturday, March 17, 2007 10:49 AM
To: muse-dev@ws.apache.org
Subject: [jira] Closed: (MUSE-211) array element type mismatch when
client sends object[]
[
https://issues.apache.org/jira/browse/MUSE-211?page=com.atlassian.jira.p
lugin.system.issuetabpanels:all-tabpanel ]
Dan Jemiolo closed MUSE-211.
----------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Fixed - see SVN message associated with this bug. Thanks again for the
sample project and build file - it cut down on the debugging time
immensely.
> 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
> Fix For: 2.2.0
>
> Attachments: TestApp.zip
>
>
> 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/T
estApp/services/SimpleResource</wsa:To>
> <wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://cisco.com/testap
p/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:Ad
dress>
> </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(AbstractResourceClien
t.java:294)
> at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
t.java:228)
> at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
t.java:207)
> at
com.cisco.testapp.proxy.simple.SimpleResourceProxy.arrayOperation(Simple
ResourceProxy.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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
RE: [jira] Closed: (MUSE-211) array element type mismatch when client sends object[]
Posted by "Vinh Nguyen (vinguye2)" <vi...@cisco.com>.
Thanks Dan for the quick fix! I will test this out as soon as possible,
and will let you know the results. Please enjoy the rest of your
weekend:)
-----Original Message-----
From: Dan Jemiolo (JIRA) [mailto:jira@apache.org]
Sent: Saturday, March 17, 2007 10:49 AM
To: muse-dev@ws.apache.org
Subject: [jira] Closed: (MUSE-211) array element type mismatch when
client sends object[]
[
https://issues.apache.org/jira/browse/MUSE-211?page=com.atlassian.jira.p
lugin.system.issuetabpanels:all-tabpanel ]
Dan Jemiolo closed MUSE-211.
----------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Fixed - see SVN message associated with this bug. Thanks again for the
sample project and build file - it cut down on the debugging time
immensely.
> 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
> Fix For: 2.2.0
>
> Attachments: TestApp.zip
>
>
> 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/T
estApp/services/SimpleResource</wsa:To>
> <wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://cisco.com/testap
p/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:Ad
dress>
> </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(AbstractResourceClien
t.java:294)
> at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
t.java:228)
> at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
t.java:207)
> at
com.cisco.testapp.proxy.simple.SimpleResourceProxy.arrayOperation(Simple
ResourceProxy.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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org