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 84897 - NB doesn't create PolicyReference if there's Policy already present
Summary: NB doesn't create PolicyReference if there's Policy already present
Status: VERIFIED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: WSIT (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-14 13:44 UTC by Martin Grebac
Modified: 2007-04-03 15:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Starting WSDL without PolicyReference element (3.74 KB, text/xml)
2006-09-14 13:45 UTC, Martin Grebac 		Details
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 Martin Grebac 2006-09-14 13:44:49 UTC 
Steps to reproduce:

Create WS from WSDL from attached wsdl *WSA.wsdl
Open Edit WS Attributes
Click on RM or any other security settings
The old policy is reused, and PolicyReference is not created.

 Correct behaviour of NB would be to generate a new policy next to the existing
one, and/or first let user choose whether he wants to bind the existing policy
to binding scope.
Comment 1 Martin Grebac 2006-09-14 13:45:45 UTC 
Created attachment 33944 [details]
Starting WSDL without PolicyReference element
Comment 2 Martin Grebac 2006-09-14 13:46:24 UTC 
Workaround is to put PolicyReference element manually under binding element, or
remove/rename the policy already present in the wsdl.
Comment 3 Martin Grebac 2006-11-08 10:58:25 UTC 
Fixed in v2.2
Comment 4 Martin Grebac 2007-04-03 15:51:49 UTC 
v