On Wednesday 14 July 2010 8:12:37 pm ironman77 wrote:
> Glen,
> 
> Thank you for your reply.
> 
> On using publishedEndpointUrl, we are getting the following error in our
> application logs.  We are using Websphere as our app server, not sure if
> this is relavent to it.
> 
> Relevant Configuration from cxf-servlet.xml:
> <jaxws:endpoint id="tService"
>               implementor="#TService"
>               address="/TService"
>               wsdlLocation="WEB-INF/wsdl/TService.wsdl"
>               
> publishedEndpointUrl="https://blahblah.com/tea/services/TService";>
>               <jaxws:properties>
>                       <entry key="schema-validation-enabled" value="true" />
>               </jaxws:properties>
> </jaxws:endpoint>
> 
> 
> relevant Service elemetn from TService.wsdl:
> <wsdl:service name="TService">
>               <wsdl:port name="TService"
>                       binding="tns:TServiceSoapBinding">
>                       <soap:address 
location="https://blahblah.com/tea/services/TService"/>
>               </wsdl:port>
> </wsdl:service>
> 
> 
> Error Message:
> 
> XACMLPolicyPa E XACMLPolicyParser$XACMLErrorHandler error() CWRGS4054E A
> error was issued while parsing the XML document at line 44, column 32.
> cvc-complex-type.2.4.a: Invalid content was found starting with element
> 'PolicySetIdReference'. One of
> '{"urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySet,
> "urn:oasis:names:tc:xacml:2.0:policy:schema:os":Policy,
> "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySetIdReference,
> "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicyIdReference,
> "urn:oasis:names:tc:xacml:2.0:policy:schema:os":CombinerParameters,
> "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicyCombinerParameters,
> "urn:oasis:names:tc:xacml:2.0:policy:schema:os":PolicySetCombinerParameters
> , "urn:oasis:names:tc:xacml:2.0:policy:schema:os":Obligations}' is
> expected.
> 

Is there a stack trace on that?    That's a strange error.  

Is there a "PolicySetIdReference" element in the wsdl anywhere?    What that 
error basically says (normally) is that there is an unqualified 
"PolicySetIdReference" element in there, but it SHOULD be qualified.   

Dan


> 
> is the soap address in wsdl ok?  are we missing something that is obvious?
> Any thoughts, ideas, are greatly appreciated.
> 
> Thank you,
> J

-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog

Reply via email to