Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Process Manager (Stardust) » IAF-Stardust: WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL(Policy Exception)
IAF-Stardust: WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL [message #742686] Thu, 20 October 2011 18:25 Go to next message
Vikram Kodak is currently offline Vikram Kodak
Messages: 57
Registered: October 2011
Member
While hitting the IAF-Stardust embedded web service from the a web interface application ( AIX environment ),
we are getting the following error, please see detail trace at bottom

SEVERE: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
Throwable occurred: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(http://xxx.xxx.xxx.xxx:8004/xxx/Stardustservices/soap/WorkflowServiceHttpBasicAuth?wsdl#SslPolicy)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)

Although the same works well in windows environment.

As per the exception it looks that at web service client side, while reading the WSDL ,
it is throwing error while referring the #SslPolicy which is defined in the WSDL provided by Stardust,
here is a portion of reference from InfinityBpmService.wsdl.

<!-- Workflow Service (HTTP Basic Authentication using SSL) -->
      <wsdl:port binding="impl:IWorkflowServiceSoapBinding" name="WorkflowServiceHttpBasicAuthSslEndpoint">
         <wsdlsoap:address location="REPLACE_WITH_ACTUAL_URL" />
         <wsp:PolicyReference URI="#SslPolicy" />
         <wsaw:UsingAddressing wsdl:required="false" />
      </wsdl:port>

[Updated on: Fri, 21 October 2011 04:21]

Report message to a moderator

Re: IAF-Stardust: WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL [message #742688 is a reply to message #742686] Thu, 20 October 2011 18:27 Go to previous messageGo to next message
Vikram Kodak is currently offline Vikram Kodak
Messages: 57
Registered: October 2011
Member
As per testing we have removed the references of #SslPolicy, then started getting the similar error for ="#UsernameTokenPolicy.Then removed the ="#UsernameTokenPolicy including #SslPolicy, then were able to invoke the Stardust web services properly.

As I understand that it is not a good idea to tamper the WSDL provided by Stardust, please do let us know, how to fix this ?,like do we need to do some setting on weblogic server where client application is running?

This is a kind of show stopper, as we are not able to invoke the IAF-Stardust web services from AIX deployment.

Just to add we don't have additional webservices-rt-1.5.jar in lib (the web service client side deployment(AIX)),which was suspected as one of the possible reason while initial analysis.

Another observation about the issue is if we keep the additional webservices-rt-1.5 .jar in deployment path folder of the application in windows environment, we get the same issue in windows environment as well, just removing the webservices-rt-1.5.jar from deployment, makes it work for windows, but not on AIX.
Re: IAF-Stardust: WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL [message #742690 is a reply to message #742688] Thu, 20 October 2011 18:29 Go to previous messageGo to next message
Vikram Kodak is currently offline Vikram Kodak
Messages: 57
Registered: October 2011
Member
We are now successfully able to execute the Stardust web services from our product on the AIX platform.

We corrected the problem by removing the xerces.jar from our deployment.This is a valid solution for us as we have no other need for this jar.
It was added to our deployment as a transient dependency of CXF. Actually it's a dependency of jaxen, which is a dependency of CXF and I was able to safely exclude this item.
Re: IAF-Stardust: WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL [message #1012090 is a reply to message #742688] Wed, 20 February 2013 21:33 Go to previous message
Jan Hendrik Scheufen is currently offline Jan Hendrik Scheufen
Messages: 61
Registered: October 2011
Member

I ran into a similar problem on Weblogic 10.3.3 on Windows with a Stardust version < 0.7 (which included the Metro WS implementation). The error message was
WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST

and concerned the same WSDL subpolicy (#SslPolicy).

The problem seems to come from having two versions of the metro runtime on the classpath. Excluding the webservices-rt artifact from the Stardust build solved the problem.
Previous Topic:Accessing Stardust dynamic web services on Weblogic 10.3 results in 401 Unauthorized response
Next Topic:Unable to load Derby EmbeddedDriver even though it's in the classpath
Goto Forum:
  


Current Time: Thu Sep 18 08:02:24 GMT 2014

Powered by FUDForum. Page generated in 0.02662 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software