Thanks for the reply. I looked at the URL you sent but I think the handler chain they're setting up is for a jbossws service end point.
I'm trying to set up a handler for a client. The application is not deployed as part of a war file. It's deployed in a jar file as a j2ee 1.4 web service client (I think this is called a JSR-109 client - see http://labs.jboss.com/portal/jbossws/user-guide/en/html/clients.html ). The contents of the jar file includes the following in /META-INF:
/META-INF/application-client.xml
/META-INF/jaxrpc-mapping.xml
/META-INF/jboss-client.xml
/META-INF/wsdl/TestService.wsdl
I think the jbossws examples (version 1.0.3) includes an example of what I'm trying to do under the handler directory. The handler example connects to a locally hosted web service whilst I connect to a remotely (.NET) hosted web service.
As I say I don't get any exceptions on deployment so I'm quite stumped about what jboss is doing.
Cheers,
Alex[/url]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983708#3983708
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983708
Hi,
I have a rpc type webservice. I works perfectly but I tried to do stress tests so I ran 20 calling my webservice with the same args.
After some time, the request created(I logged the request on the client side with an handler), is false.
Correct is :
...
<env:body>
<ns1:getSettings xmlns:ns1='http://mycompany.com'>
<String_1 xmlns=''>AAAAA</String_1>
<String_2 xmlns=''>BBBBB</String_2>
</ns1:getSettings>
</env:body>
wrong is :
...
<env:body>
<ns1:getSettings xmlns:ns1='http://mycompany.com'>
<String_1 xmlns='' xmlns:xsi='http://www.w3c.org/2001/XMLSchema-instance' xsi:nil='1' />
<String_2 xmlns=''>BBBBB</String_2>
</ns1:getSettings>
</env:body>
or
...
<env:body>
<ns1:getSettings xmlns:ns1='http://mycompany.com'>
<String_1 xmlns=''>AAAAA</String_1>
<String_2 xmlns='' xmlns:xsi='http://www.w3c.org/2001/XMLSchema-instance' xsi:nil='1' />
</ns1:getSettings>
</env:body>
I don't understand why this happens because I execute the axact same code on the client and server side. I found no issue on jira. For me this problem is easily repoducible as soon as I have at least 10 threads calling the ws concurrently.
Thanks,
Vincent.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983668#3983668
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983668