Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350592 - ForbiddenReference in wsdl UI wizard
Summary: ForbiddenReference in wsdl UI wizard
Status: RESOLVED FIXED
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.2.5   Edit
Assignee: Atosa Khoddamhazrati CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard:
Keywords:
Depends on: 339317
Blocks:
  Show dependency tree
 
Reported: 2011-06-28 10:54 EDT by Keith Chong CLA
Modified: 2011-07-07 13:56 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Keith Chong CLA 2011-06-28 10:54:55 EDT
+++ This bug was initially created as a clone of Bug #339317 +++

This "forbidden reference" started showing up recently in our build logs (pasted at end of this comment), in both maintenance and Indigo. Maybe you changed something, but, my first guess is it has simply been hidden before by our "access rules", which I have now turned off ... so we get twice as many "discouraged access" warnings ... and this one extra forbidden Reference. 

Forbidden References are serious since, presumably, the code would not work at runtime, if ordinary OSGi classloading is used. 

I've not looked at the the code in question, but can be because of something in wsdl ui bundle, or could be because org.eclipse.wst.ws.service.policy.ui does not export it. 

= = = =


Source File: org/eclipse/wst/wsdl/ui/internal/wizards/NewWSDLWizard.java
    5. WARNING: ForbiddenReference
    Access restriction: The type ServicePoliciesPropertyPage is not accessible due to restriction on classpath entry /opt/public/webtools/projects/wtp-R3.3.0-I/workdir/plugins/org.eclipse.wst.ws.service.policy.ui/@dot
    NewWSDLWizard.java :
    53 : import org.eclipse.wst.ws.internal.service.policy.ui.properties.ServicePoliciesPropertyPage;
Comment 1 Keith Chong CLA 2011-07-07 13:56:46 EDT
The fix was released to 3.2.5 last week. Resolving.