Sorry for the late reply, the generated interface looks as it should, my defined exceptions appear in the throws list of the interface, they also get thrown by the client. The exceptions work as expected if i don't activate the authentication policy. Could this be a ssl issue? The policy expects a ssl connection, i configured tomcat to handle that and just set the endpoint in the wsdl to point to tomcat's ssl port.
thanks, Erik ----- Original Message ----- From: "Raymond Feng" <[email protected]> To: "user" <[email protected]> Sent: Friday, March 19, 2010 4:39:01 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: binding.ws / policySets and exception handling It seems that the HTTP server side produced an HTML page instead of XML. How does your generated interface look like? The exceptions on the "throws" list will be interesting to see. You also have to make sure that the target component implementation throw such user exceptions. Thanks, Raymond -------------------------------------------------- From: "Erik Dannenberg" <[email protected]> Sent: Friday, March 19, 2010 2:55 AM To: "user" <[email protected]> Subject: binding.ws / policySets and exception handling > Hi, > > currently got a problem with tuscany 1.6 which im not sure is a bug or > misconfiguration on my part. > > Its a composite i made topdown, so wsdl/xsd first then wsdl2java, it also > uses sdo as databinding and a good amount of defined soap faults. After > everything was working as expected i added a authentication policyset. But > as soon as i add the requires= tags to the composite, exceptions dont get > handled correctly, as on the client side i just get a > > org.osoa.sca.ServiceRuntimeException: org.apache.axis2.AxisFault: First > Element must contain the local name, Envelope , but found html > at > org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediateFault(MediatorImpl.java:317) > > when i should get something like a NoSuchUserException. The service logs > show nothing unusual with rampart and tuscany log levels set to debug. > > Everything else is working as it should. The policyset is pretty much the > rampart standard sample for usertoken authorization. The service is > running in a webapp in tomcat, could this be the problem?
