Yes, the request might be comming from a careless client that misses to
namespace qualify the operation name.
If is valid, we dont not have provision for an invalid rpc
element.
What is fixed in SP1 is, that the namespace can also be defined on the envelope.
View the original post :
http://
"[EMAIL PROTECTED]" wrote : This is fixed in jbossws-1.0.3.SP1
Or maybe not.
I'm seeing the same behavior with 1.0.3.SP1
Do I have to change jboss-xml-binding.jar with this release?
| 2006-11-09 14:02:01,181 DEBUG [org.jboss.ws.server.StandardEndpointServlet]
doPost: /jbossws-samples-rpcstyl
http://repository.jboss.com/jboss/jbossws/1.0.3.SP1/
http://repository.jboss.com/jboss/jbossws14/1.0.3.SP1/ (jdk1.4)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984044#3984044
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=re
"[EMAIL PROTECTED]" wrote : This is fixed in jbossws-1.0.3.SP1
Great!
But can you tell me how can I get a copy of 1.0.3.SP1?
I'm a lowly user. It was hard enough trying to find a link to download the
1.0.3.GA release.
Thanks!
View the original post :
http://www.jboss.com/index.html?module=b
This is fixed in jbossws-1.0.3.SP1
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983250#3983250
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983250
___
jboss-user mailing l
anonymous wrote : You could try and modify your client...
The client is a "black box" so I'm stuck with trying to configure the service
so it won't choke on an empty Namespace.
Just to clarify, the missing namespace is tolerated if the service is deployed
under tomcat50-jwsdp; JBoss 1.0.3 throw
You could try and modify your client to include a line like this.
envelope.addNamespaceDeclaration(PREFIX,NAMESPACE_URI);
Where prefix would be "rpc" and NAMESPACE "http://org.jboss.ws/samples/rpcstyle";
That would add an adicional name space declaration like in your soapui example.
View the
