When using Native 3.0.5.GA, I am seeing an issue calling no-parameter WS methods. I have
2 of them. The first appears to go through correctly. The 2nd appears fail in the SOAP
binding. The stack trace I am seeing is:
2009-03-22 22:09:28,340 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[HtmlAdaptor]]
Servlet.service() for servlet HtmlAdaptor threw exception
| org.jboss.ws.WSException: Cannot find child element:
{http://service.vmgr.desktone.com/VMgrService}retrieveAllStorageConfigsResponse
| at
org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:917)
| at
org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| at $Proxy154.retrieveAllStorageConfigs(Unknown Source)
| at
com.desktone.server.accessFabric.FabricDelegateImpl.retrieveAllStorageConfigs(FabricDelegateImpl.java:4502)
| at
com.desktone.server.accessFabric.service.FabricDelegateService.retrieveAllStorageConfigs(FabricDelegateService.java:1265)
In fact, no matter how many no-param methods I have, only 1 of them works. So, I also
understand that SOAP does not uniquely identify methods by their signature but rather by
their parameters. So, is this really a limitation? If so, any easier workaround than
including a bogus parameter?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220111#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...