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 93799 - AM security for WS client can't be enabled after editing WSIT attributes
Summary: AM security for WS client can't be enabled after editing WSIT attributes
Status: VERIFIED FIXED
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: 92887
  Show dependency tree
 
Reported: 2007-02-01 13:38 UTC by Andrey Yamkovoy
Modified: 2007-08-24 17:18 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 Andrey Yamkovoy 2007-02-01 13:38:50 UTC 
Steps to reproduce:
- Create 2 Web Applications using Java EE version 5.
- Create Web Service with some operation in 1st web application.
- Deploy 1st web application.
- Create Web Service Client in 2nd Web Application for web service created above.
- Create servlet in 2nd web application and put the invokation of some operation
of web service in it.
- Invoke web service attributes in 2nd application.
- Go to 'WSIT' TAB and change some attribute (for example set default username)
and then edit it again to change it to original state/value.
- Notice that after previous step it is impossible to enable AM security in
'Security' TAB.
Comment 1 Peter Liu 2007-02-01 18:44:39 UTC 
It looks like wsit client security attributes can't be turned off.
Comment 2 Martin Grebac 2007-02-02 10:05:19 UTC 
 The wsit *client* security attributes shouldn't break AM at all, that's why. I
think I should rework the check so that it only checks the service wsdl for wsit
security. 
 Any objections?
I reassigned the issue to myself as I think the problem above is in wsit code.
Comment 3 Martin Grebac 2007-02-02 15:48:10 UTC 
I'm checking only the service policy for settings, so it should work now. Client
settings are reflected only if there policy support on service.
Comment 4 Peter Liu 2007-02-08 01:26:46 UTC 
Martin,  

I am reopening this issue because things are not working correctly on the client
side.  Let's talk after you come back from your vacation.

Peter
Comment 5 Martin Grebac 2007-02-12 10:35:17 UTC 
I'd like to see what is not working in this issue. We may talk about it as well,
but the issue should be here.
Comment 6 Peter Liu 2007-02-12 19:15:11 UTC 
First of all, if the web service has wsit security enabled,
WsitConfigProvider.isWsitSecurityEnabled() is not returning true on the client
side.  Also, the reverse is not implemented. If the AM client security is
enabled, shouldnt the wsit client be disabled?
Also, I am not quite sure I understand why if the user enables some attributes
in the wsit client tab, the am client tab doesn't get disabled.
Comment 7 Martin Grebac 2007-02-13 15:05:52 UTC 
To make sure you get the right security status, you need to refresh the client,
otherwise it's impossible to check.

I checked the client checker code in - had to change the exception handling from
security checkers to log only, because I get some everytime on client side.
Comment 8 Jaroslav Pospisil 2007-08-24 17:18:57 UTC 
VERIFIED