You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tuscany.apache.org by Erik Dannenberg <e....@blooparksystems.de> on 2010/03/19 10:55:40 UTC
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?
Re: binding.ws / policySets and exception handling
Posted by Raymond Feng <en...@gmail.com>.
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" <e....@blooparksystems.de>
Sent: Friday, March 19, 2010 2:55 AM
To: "user" <us...@tuscany.apache.org>
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?