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 89504 - client with optimal encoding has invalid header
Summary: client with optimal encoding has invalid header
Status: RESOLVED WORKSFORME
Alias: None
Product: webservices
Classification: Unclassified
Component: WSIT (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-16 19:21 UTC by tamiro
Modified: 2006-11-27 16:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tamiro 2006-11-16 19:21:48 UTC 
Configuration:
- wsit build 1278
- GF promoted b25
- wsit nbms Nov 10
- NB 5.5 FCS
- Non 109 (Java EE 1.4) service/client

Got web service and client working with RM enabled. The in client WSIT tab, 
in Tranport node, checked Optimally Select Optimal Encoding.

On running, the client it now fails with
Exception = javax.xml.ws.soap.SOAPFaultException: A header representing a
Message Addressing Property is not valid and the message cannot be processed
Comment 1 tamiro 2006-11-16 19:50:31 UTC 
This problem only happens when the service had RM enabled. After 
unchecking RM on the service, the problem goes away.
Comment 2 Martin Grebac 2006-11-16 20:19:35 UTC 
Tom, are you saying this combination works manually from command lineand it only
doesn't work in Netbeans?
Comment 3 tamiro 2006-11-16 21:15:22 UTC 
I'm not doing anything in a commandline; striclty netbeans.
I'm saying if the service and client are working with 
RM enabled, and then you go into the client WS attributes 
and enable the transport options you get the header error.
I don't even know if you are supposed to be able to this though.
Comment 4 Martin Grebac 2006-11-27 14:53:09 UTC 
 I'm not able to reproduce, neither with 109/non109 client/service. I'm using
latest WSIT module, and hudson build 1312, everything else is the same.
 Feel free to reopen if you are able to reproduce, please include more exact
reproduction steps then. Thanks.
Comment 5 tamiro 2006-11-27 16:01:06 UTC 
Works for me too now.