I take that back, they added support for mixing @SOAPBinding in maintenance release of JSR-181. In this case, we need to move parameter style to the operation level.

 

http://jira.jboss.com/jira/browse/JBWS-1416

 

Also, this is tested by the CTS:

 

http://jira.jboss.com/jira/browse/JBCTS-425

 

The message level test will still need to be removed though, because the user is required to actually specify the binding type properly.

 

-Jason

 

From: jbossws-dev-bounces@lists.jboss.org [mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Jason T. Greene
Sent: Thursday, December 07, 2006 7:03 PM
To: Thomas Diesler
Cc: jbossws-dev@lists.jboss.org
Subject: RE: [jbossws-dev] Document/Wrapped can not be a message type

 

You can’t mix parameter styles in the same endpoint

 

From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 07, 2006 4:49 PM
To: Jason T. Greene
Cc: jbossws-dev@lists.jboss.org
Subject: Re: [jbossws-dev] Document/Wrapped can not be a message type

 

http://jira.jboss.com/jira/browse/JBWS-1414

What about a SEI like this

MyService
{
       public void foo(String one, String two);

       public void bar(SOAPElement elmt);
}

Jason T. Greene wrote: 

-----Original Message-----
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 07, 2006 12:42 PM
To: Jason T. Greene
Cc: jbossws-dev@lists.jboss.org
Subject: Re: [jbossws-dev] Document/Wrapped can not be a message type
 
This is saying:
 
if document/wrapped and the endpoint is not a SOAPElement endpoint do
the wrapping.
 
There are occasions where a message type endpoint registers as
document/wrapped
 
    
 
We should fix this then. As I was saying, it's illegal for a wrapped
type to be a message style service. A message style service is simply a
bare service with a SOAPElement or DOM Element for a parameter.
 
I have created a jira issue for this:
http://jira.jboss.com/jira/browse/JBWS-1414
 
-Jason
 

 

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx