January 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: JBWS-1464 - Adding MTOM support to WSDL To Java - Design

by darran.lofthouse＠jboss.com

The process of generating the WSDL from the SEI is covered by a separate Jira task: - [url] http://jira.jboss.com/jira/browse/JBWS-1466[/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004514#4004514 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004514

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1464 - Adding MTOM support to WSDL To Java - Design

by noel.rocher＠jboss.com

In practice, we should make simple for users to generate a wsdl. What they are used to do today when the wsdl is not trivial : - write a java interface that is a copy of the SEI but with all attachment params replaced with String params. - generate the wsdl with wtools from this interface - make simple changes to wsdl to replace string type by what is required for wstools to detect attachments - test if client side is correctly generated from this wsdl - test if the server side is working with this stubs calls View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004500#4004500 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004500

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1464 - Adding MTOM support to WSDL To Java - Design

by noel.rocher＠jboss.com

anonymous wrote : 1 - Map all binary types to javax.activation.DataHandler | | A global configuration option can be set to switch on MTOM mapping and all types that are based on xs:base64Binary or xs:hexBinary can be mapped to javax.activation.DataHandler. I see base64Binary data that should not be considered as attachment. It's a type that is often used for IDs. For exemple, you can have an operation with an ID as argument and an attachment as a result. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004492#4004492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004492

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1464 - Adding MTOM support to WSDL To Java - Design

by darran.lofthouse＠jboss.com

This thread is to discuss the options for adding MTOM support to WSDL To Java. There are a number of options for how this can be implemented and a number of obstacles to overcome for the more advanced implementations. The main obstacle is that it is not possible to get access to the expectedContentTypes attribute using the xerces schema API. On the plus side there currently does not apear to be any work required on generating the JAX RPC mapping file, this just requires a variable mapping (which does not contain type information) in the corresponding java-xml-type-mapping. This mapping is already correctly generation. At the moment I see the following options for how this could be implemented: - 1 - Map all binary types to javax.activation.DataHandler A global configuration option can be set to switch on MTOM mapping and all types that are based on xs:base64Binary or xs:hexBinary can be mapped to javax.activation.DataHandler. 2 - Global configuration to specify what binary types should be mapped to. A global configuration option can be added to specify what the binary types should be mapped to. This would assume all binary types can be mapped to the same type. 3 - Allow configuration to map XML types to specific Java types. This would mean if the schema contains different types based off the binary types then it will be possible for each to be mapped to a different Java type. This would however not work when the binary types are mapped as follows as it will not be possible to differentiate between them: - <element name="legacyData" | xmime:expectedContentTypes="text/xml" | type="xmime:base64Binary"/> | 4 - A more advanced configuration to allow the specific elements to be identified. | <complexType name='Employee'> | <sequence> | <element name="firstname" type="xsd:string"/> | <element name="lastname" type="xsd:string"/> | <element name="legacyData" xmime:expectedContentTypes="text/xml" | type="xmime:base64Binary"/> | </sequence> | </complexType> | So for this example the configuration would allow the user to specify that the element legacyData of the type Employee should be mapped to a specific Java type. 5 - Switch on generation of synthetic annotations. The xerces implementation has a feature that can be enabled to generate a synthetic annotation when a schema component has non-schema attributes. This annotation could then be parsed to extract the expectedContentTypes. This of course would be xerces implementation specific. An appropriate Java type can then be selected based on the list of content types. 6 - Add a pre-generation step to read mime information from the WSDL Add a step before generation to read all expectedContentTypes from the schema (Possibly using the synthetic annotations approach), this will store the data in a model - as part of the main generation step this model can be read if a binary type is found to check if mime types have been specified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004323#4004323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004323

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1464 Clarification of the MTOM related specificatio

by jason.greene＠jboss.com

You are correct. Also the expectedContentType value, if present is ignored, since the xerces schema API can't represent it. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004013#4004013 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004013

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1464 Clarification of the MTOM related specifications.

by darran.lofthouse＠jboss.com

I have been looking at the following specification to try and get a better understanding of how the mime type for binary content is specified in the schema and in the actual document transmitted: - http://www.w3.org/TR/xml-media-types/ My interpretation is that the 'expectedContentTypes' attribute is an annotation which is added to the XML schema to list the mime types that can be represented by the binary content. My interpretation of the 'contentType' is that this is used on the document instance itself (not the schema) to specify what is the actual mime type of the binary data being transmitted. So in the schema 'expectedContentTypes' can be used to list a set of mime types and then in the document 'contentType' is used to specify what is being transmitted in this document instance. However in the user guide and in some test cases we seem to be using 'contentType' in the place of 'expectedContentTypes' or in addition to 'expectedContentTypes' in the schema. This seems incorrect to me, should it really be possible to use 'contentType' in the schema? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004005#4004005 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004005

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Design of wsimport

by jason.greene＠jboss.com

The JAXB XJC api does this, so it will be there ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003992#4003992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003992

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Design of wsimport

by dwin

Just a neat feature to include, it'd be nice if xs:annotation <xs: documentation> gets translated into java docs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003989#4003989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003989

17 years, 4 months

1
0
0 / 0

Re: JBoss WS Features

by Thomas Diesler

17 years, 4 months

3
2
0 / 0

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

by darran.lofthouse＠jboss.com

Here is the correct extract: - <schema targetNamespace='http://www.jboss.org/support/photoalbum/types' | xmlns='http://www.w3.org/2001/XMLSchema' | xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' | xmlns:tns='http://www.jboss.org/support/photoalbum/types' | xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' | xmlns:ref='http://ws-i.org/profiles/basic/1.1/xsd'> | <complexType name='Photo'> | <sequence> | <element name='caption' nillable='true' type='string'/> | <element name='image' type='ref:swaRef'/> | </sequence> | </complexType> | <element name='publishPhoto' type='tns:Photo'/> | <element name='publishPhotoResponse' type='int'/> | </schema> | </types> | | <message name='AlbumEndpoint_publishPhoto'> | <part element='ns1:publishPhoto' name='publishPhoto'/> | <part name='mimepart' type='xsd:hexBinary'/> | </message> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003040#4003040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003040

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