January 2007 - jbossws-dev - Jboss List Archives

Re: [JBoss JIRA] Resolved: (JBWS-1384) Attachment parts with doclit message

by Thomas Diesler

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by jason.greene＠jboss.com

"jason.greene(a)jboss.com" wrote : "thomas.diesler(a)jboss.com" wrote : | | Also, this WSDL violates BP 1.0 because it uses "type" on the part definition for a document/literal web service. It must be element. | | | | | | | <part name="attachmentContents" type="xsd:string"/> | | | | | | | Note, this comment is wrong, the AP 1.0 spec allows type or element. BP 1.0 only governs the standard SOAP binding not the MIME binding. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002107#4002107 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002107

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by jason.greene＠jboss.com

I just fixed support for this in trunk. See the JBWS-1384 test case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002103#4002103 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002103

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by jason.greene＠jboss.com

Yes, you are right R2910 in AP 1.0 explicitly allows both. I was mixing swa ref requirements. Anyway I will make sure this is handled correctly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002029#4002029 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002029

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by darran.lofthouse＠jboss.com

I think the original WSDL at the top of the user post is correct, the basic profile only specifies that the part must reference elements if the part is referenced from a soapbind:body element, it doesn't specify a requirement for mime:content parts. anonymous wrote : R2204 A document-literal binding in a DESCRIPTION MUST refer, in each of its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the element attribute. The attachments profile also contains the following parts defined in a document/literal example: - | <wsdl:message name="ClaimIn"> | <wsdl:part name="body" element="types:ClaimDetail"/> | <wsdl:part name="ClaimPhoto" type="xsd:base64Binary"/> | </wsdl:message> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001996#4001996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001996

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1452 - WSDL To Java, Array unwrapping.

by jason.greene＠jboss.com

The case in 732 is a contrived example that was made to have good coverage of jbossxb's handling of nulls and arrays. In most cases, a document/literal wrapped wsdl will not wrap the array yet again in another element definition. Take a look at the wscompile output of testMethod(String[] request, int foo) You should see something like this | <complexType name="testMethod"> | <sequence> | <element name = "request" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> | <element name="foo" type="xsd:int"/> | </sequence> | </complexType> | The only reason to create a wrapper element is to be able to have a distinction between a null array, and a null array element. Without the wrapper, as in above, this is not possible. Even so, for the purpose of simplifying the wsdl, most toolkits will make the sacrifice. That said there is no reason to not do it for document/literal, so you can disable that check if you like. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001994#4001994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001994

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by jason.greene＠jboss.com

I will revert the patch that disabled this, and take a look and see if there are any bugs with doc/lit attachments, but the use case that that jira issue was testing was using an invalid WSDL file, so this may have been the real problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001985#4001985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001985

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by darran.lofthouse＠jboss.com

That's good, my understanding matches yours - I thought we had full support for attachments and it was just tools that needed enhancing then I found that comment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001975#4001975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001975

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by jason.greene＠jboss.com

That's wrong. This has been supported before, it's supposed to work. I reopened the issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001970#4001970 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001970

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by darran.lofthouse＠jboss.com

How about the mapping of the attachment to the parameters of the method on the SEI? At the moment on the server side the only way I see to get access to the attachment is to use the SOAPMessage class and call the getAttachments method. On the client side it apears that the only way to send the attachments is to use the 'org.jboss.ws.core.jaxrpc.StubExt' interface as described in JBWS-1384. At the moment in the class JAXRPCMetaDataBuilder there is a comment: - anonymous wrote : | // we don't support swa binding parameters in document style | // http://jira.jboss.org/jira/browse/JBWS-1384 | Is this something we will support? At the moment deployments created using wscompile can not be deployed because we do not process the mapping defined. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001865#4001865 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001865

17 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev January 2007