This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 126083 - Configure Message Handlers
Summary: Configure Message Handlers
Status: RESOLVED WORKSFORME
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Roderico Cruz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-28 12:53 UTC by ganeshk_tsm
Modified: 2008-03-26 06:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
It has 2 projects zipped. Server Project Name - SoapTest. Client Project Name - SoapClient. I have added a Soap Message handler to the Client. I dont see any effect on that. I am seeing the Server being invoked without passing through Soap Handler. (34.44 KB, text/plain)
2008-01-29 08:45 UTC, ganeshk_tsm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ganeshk_tsm 2008-01-28 12:53:01 UTC
I have created a Message Handler for Web Service Reference i.e. a Web Client. I am trying to retrieve the Soap Message 
that is going as a request from the Client and also the response from the Server. Through Configure Handler option in 
Netbeans, I configured the Handler. The Handler is not being effected at all. The request is not passing through the 
Handler. The same thing works when I use it in the Server instead of Client. Can you please let me know the right way 
to do it or if this is a bug with Netbeans?

Thanks,
Ganesan.K.
Comment 1 Milan Kuchtiak 2008-01-28 13:36:09 UTC
Have you tried to Clean & Build you project ?

AFAIK, the Client handler configuration affects the local wsdl file located under xml-resources/web-service-references.
Then, you need to re-generate the jax-ws artifacts (java classes in build/generated/wsimport/client/...).
The Clean & Build action should does that. If not it is a bug.
Comment 2 Roderico Cruz 2008-01-28 20:23:44 UTC
This should work on clients. Kindly zip up your project and attach to this bug. Thanks.
Comment 3 ganeshk_tsm 2008-01-29 08:45:29 UTC
Created attachment 55693 [details]
It has 2 projects zipped. Server Project Name - SoapTest. Client Project Name - SoapClient. I have added a Soap Message handler to the Client. I dont see any effect on that. I am seeing the Server being invoked without passing through Soap Handler.
Comment 4 Jaroslav Pospisil 2008-03-25 15:37:00 UTC
Additional information (zipped projects) added - please evaluate.
Comment 5 Roderico Cruz 2008-03-26 06:52:45 UTC
I tried your projects and the handlers work fine. The server log correctly printed your statements in handleMessage():

==============================================================START==========================================================
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SOAPClient] has already been started
Mar 25, 2008 10:38:32 PM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/SOAPClient]
Mar 25, 2008 10:38:32 PM org.apache.catalina.core.StandardContext start
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SOAPClient] has already been started
SOAP RESPONSE SENT
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:getName
xmlns:ns2="http://test.com/"><name></name></ns2:getName></S:Body></S:Envelope>
SOAP REQUEST RECEIVED
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header/><S:Body><ns2:getName
xmlns:ns2="http://test.com/"><name/></ns2:getName></S:Body></S:Envelope>
SOAP RESPONSE SENT
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:getNameResponse
xmlns:ns2="http://test.com/"><return>SOAP Test</return></ns2:getNameResponse></S:Body></S:Envelope>
SOAP REQUEST RECEIVED
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header/><S:Body><ns2:getNameResponse
xmlns:ns2="http://test.com/"><return>SOAP Test</return></ns2:getNameResponse></S:Body></S:Envelope>
SOAP RESPONSE SENT
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:getName
xmlns:ns2="http://test.com/"><name></name></ns2:getName></S:Body></S:Envelope>
SOAP REQUEST RECEIVED
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header/><S:Body><ns2:getName
xmlns:ns2="http://test.com/"><name/></ns2:getName></S:Body></S:Envelope>
SOAP RESPONSE SENT
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:getNameResponse
xmlns:ns2="http://test.com/"><return>SOAP Test</return></ns2:getNameResponse></S:Body></S:Envelope>
SOAP REQUEST RECEIVED
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header/><S:Body><ns2:getNameResponse
xmlns:ns2="http://test.com/"><return>SOAP Test</return></ns2:getNameResponse></S:Body></S:Envelope>
================================================END========================================================================

I am closing this as WORKSFORME. If you still experience this problem, kindly send the server log as this looks like a
problem in the deployment of the service and/or client.