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 200626 - OWSM API not added to classpath after adding policy
Summary: OWSM API not added to classpath after adding policy
Status: RESOLVED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: JAX-WS (show other bugs)
Version: 7.1
Hardware: PC Mac OS X
: P2 normal (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 10:41 UTC by Petr Jiricka
Modified: 2011-08-10 21:32 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 Petr Jiricka 2011-08-03 10:41:12 UTC 
1. Register the WebLogic installation + domain from JDeveloper
2. Create a new web project against this server
3. Create a web service
4. In the popup menu of the service in the project logical view, choose Edit Web Service Attributes
5. Select one or more OWSM policies and click Ok.

=> Extra annotation is added to the web service, e.g.: @weblogic.wsee.jws.jaxws.owsm.SecurityPolicy(uri = "oracle/binding_authorization_permitall_policy")
But this code is underlined as uncompilable, because the class is not on classpath.

The workaround is to add $MW_HOME/oracle_common/modules/ws.api_1.1.0.0.jar to the classpath manually.
Comment 1 Denis Anisimov 2011-08-08 07:40:40 UTC 
There is the special handling code for this.
But it is written as a "typo".

web-main#4302df19770d
Comment 2 Quality Engineering 2011-08-10 21:32:12 UTC 
Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/4302df19770d
User: Denis Anisimov <ads@netbeans.org>
Log: Fix for BZ#200626-OWSM API not added to classpath after adding policy.