JBossDeveloper

Hi Ana,

This sounds promising ! Which JBossWs and JBoss AS release did you use ? Would you mind sharing your code ?

Our procedure for developing the code was a bit different. We are using handwritten WSDL and XSD, everything else is generated from this, then the @SchemaValidation tag was added to the code.

Best regards, Luc.

Hi Ana,

Thanks a lot ! I will try it out asap !

Luc.

Hi Ana,

It worked now, thanks again ! I had to flatten my WSDL (copy the XSD that I imported into the file itself) and rename the class that implemented the endpoint to make jbossws understand it, but now I end up in the errorhandler on schema validation errors.

A remaining problem, that for now makes the feature not so useful: if I throw an exception in my handler, nothing happens. As in: the client gets back nothing (nope, nada, zero bytes) instead of a SOAP fault I was expecting.

Cheers, Luc.

Hi Ana,

I did not deploy the demo app, as far as I can remember, just tried to mimick as much as I could your approach.

I tried calling my app with SoapUI, which shows HTTP headers are returned but nothing else. The Sax exceptions simply end up in the app server log.

I am suspecting the problem might have something to do with the webservice being generated top-down from the WSDL, but this is just a guess.

I hope to have some time soon to do some more experiments: deploying your demo app and also trying to run the JBoss testcase.

Cheers, Luc.

Hi Ana,

I got your sample to deploy and it works as expected (i.e. exceptions returned to client). Comparing with my project, I think I know now what is the problem.

See

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141744

for further discussion / questions.

Cheers, Luc.