6 Replies Latest reply on Jan 4, 2008 3:19 AM by asoldano

Wrong incomming SOAP not intercepted

bossy Jan 24, 2007 9:45 AM

Could someone please tell me does JBoss enforce the restrictions put in the wsdl and how?
I have WS that runs under JBoss. In my wsdl I put a restriction on one of the elements to make sure that it's always present in the request:

<element name='mailbox' nillable='false' minOccurs="1" maxOccurs="1" type='string' />

I was expecting that in the unlikely event this element is missing from the request, this will be intercepted and an appropriate SOAP exception will be thrown, without me having to do anything.

The debug shows, though, that that's not the case.
The request is accepted and sent for processing, which of course fails, as there's missing information.

Do I need to do additional validation or am I right to think that JBoss should enforce the restrictions itself?
Thanks.

1. Re: Wrong incomming SOAP not intercepted

thomas.diesler Feb 14, 2007 3:36 PM (in response to bossy)

This should be fixed in jbossws-1.2.0. JAXB validates these basic restrictions.

Let me find out how jbossxb should treat these restrictions ...
Actions
2. Re: Wrong incomming SOAP not intercepted

thomas.diesler Feb 14, 2007 3:38 PM (in response to bossy)

What version of jbossws is this?
Actions
3. Re: Wrong incomming SOAP not intercepted

bossy Feb 15, 2007 4:18 AM (in response to bossy)

I'm using JBoss 4.0.4
Thanks
Actions
4. Re: Wrong incomming SOAP not intercepted

bossy Feb 15, 2007 4:20 AM (in response to bossy)

I'm sorry. I missread the question - it's jbossws1.4.
Actions
5. Re: Wrong incomming SOAP not intercepted

bkruns Jan 3, 2008 11:14 AM (in response to bossy)

We are running jbossws 1.2.0.SP1 and it still does not seem to be doing the basic WSDL validations. We have an elements setup as minoccurs=1 and it excepts the SOAP message even if that elements is not provided.
Actions
6. Re: Wrong incomming SOAP not intercepted

asoldano Jan 4, 2008 3:19 AM (in response to bossy)

"bkruns" wrote:
We are running jbossws 1.2.0.SP1 and it still does not seem to be doing the basic WSDL validations. We have an elements setup as minoccurs=1 and it excepts the SOAP message even if that elements is not provided.

Do you have the same problem with JBossWS 2.0.X ?
You may eventually create a a jira issue with a simple test reproducing the problem so that we can take care of it.
Thank you
Actions

Go to original post