Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: dev@cxf.apache.org
Subject: Re: How to add wsdl extension for SOAP/JMS.
Date: Thu, 25 Jun 2009 09:57:54 -0400
User-Agent: KMail/1.11.4 (Linux/2.6.30-gentoo-r1; KDE/4.2.4; x86_64; ; )
Cc: liucong <liucong07@gmail.com>
References: <4A40FA0F.20500@gmail.com> <200906241427.04185.dkulp@apache.org>
 <4A430D96.9090706@gmail.com>
In-Reply-To: <4A430D96.9090706@gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906250957.55273.dkulp@apache.org>

On Thu June 25 2009 1:39:34 am liucong wrote:
> Hi, Dan,
>
>     Thank you very much for your advice.  By some experiments for the
> WSDL extension. I think it is right that this WSDL extension needs some
> changes to CXF wsdl processing. And the CXF wsdl processing will supoort
> the entension in SOAP/JMS.  I think this kind of extension is necessary
> for CXF wsdl processing.

The best place to look is in the cxf trunk/common/xjc/ts project.   That 
project is an XJC plugin that adds "toString" methods to all the generated 
types.  


For MOST cases, you would need make the superclass be 
TExtensibilityElementImpl instead of Object.   

In other cases, it's a bit more complex:
1) For stuff that sublasses JAXBElement, you would need to make it implement 
ExtensibilityElement and add those methods and field.

2) For Enums - I think the stuff from (1) applies as well, not really sure 
though.

Technically, it PROBABLY just needs to apply to "root" elements.  (Stuff with 
@XmlRootElement annotations).  


Dan


>     Are there any documents which help me finish this kind of
> extension?  thank you! :-)
>
> Liu
>
> Daniel Kulp wrote:
> > Hmm...   I'm not really sure.   I don't think there IS a schema that
> > would work properly for this.   My gut feeling was something like:
> >
> >
> > <xs:complexType name="deliveryModeType">
> >     <xs:simpleContent>
> >         <xs:restriction base="wsdl:tExtensibilityElement">
> >            <xs:enumeration value="PERSISTENT" />
> >            <xs:enumeration value="NON_PERSISTENT" />
> >        </xs:restriction>
> >     </xs:simpleContent>
> > </xs:complexType>
> >
> > but I know that doesn't work.
> >
> > This will probably need some changes to CXF wsdl processing to really get
> > this to work well.   Actually, this could provide a good opportunity to
> > cleanup the JAXB WSDL   extension mechanism to NOT require that the
> > schema extends the wsdl:tExtensibilityElement type.   I'm actually
> > thinking a xjc plugin that would make all the generated types
> > automatically implement the wsdl4j ExtensibiltyElement interface and add
> > the methods/fields for that.
> >
> > That can significantly cleanup the CXF schemas for all the extensors.  
> > It would be completely automatic.
> >
> > Dan
> >
> > On Tue June 23 2009 11:51:43 am liucong wrote:
> >> Hi,
> >> I want to add wsdl extension for SOAP/JMS according to
> >> http://www.w3.org/TR/2008/WD-soapjms-20081121/#wsdl-extensions.
> >>
> >> For example, I want add wsdl extension for DeliveryMode property. I edit
> >> the wsdl file like[1]:
> >> <wsdl:binding name="JMSGreeterPortBinding"
> >> type="tns:JMSGreeterPortType"> <soap:binding style="document"
> >> transport="http://www.w3.org/2008/07/soap/bindings/JMS/"/>
> >>
> >> <soapjms:deliveryMode>PERSISTENT</soapjms:deliveryMode>
> >>
> >> <wsdl:operation name="greetMe">
> >> <soap:operation soapAction="test" style="document"/>
> >> <wsdl:input name="greetMeRequest">
> >> <soap:body use="literal"/>
> >> </wsdl:input>
> >> <wsdl:output name="greetMeResponse">
> >> <soap:body use="literal"/>
> >> </wsdl:output>
> >> </wsdl:operation>
> >> ...
> >> </wsdl:binding>
> >>
> >> If I add the extension schema like this[2]:
> >>
> >> <xs:element name="deliveryMode" type="soapjms:deliveryModeType" />
> >>
> >> <xs:complexType name="deliveryModeType">
> >> <xs:complexContent>
> >> <xs:extension base="wsdl:tExtensibilityElement">
> >> <xs:sequence>
> >> <xs:element name="deliveryMode">
> >> <xs:simpleType>
> >> <xs:restriction base="xs:string">
> >> <xs:enumeration value="PERSISTENT" />
> >> <xs:enumeration value="NON_PERSISTENT" />
> >> </xs:restriction>
> >> </xs:simpleType>
> >> </xs:element>
> >> </xs:sequence>
> >> </xs:extension>
> >> </xs:complexContent>
> >> </xs:complexType>
> >>
> >> But I can't get the extension in the wsdl.
> >> If I change the wsdl like this[3]:
> >> <wsdl:binding name="JMSGreeterPortBinding"
> >> type="tns:JMSGreeterPortType"> <soap:binding style="document"
> >> transport="http://www.w3.org/2008/07/soap/bindings/JMS/"/>
> >>
> >> <soapjms:deliveryMode><soapjms:deliveryMode>PERSISTENT</soapjms:delivery
> >>Mod e></soapjms:deliveryMode>
> >>
> >> <wsdl:operation name="greetMe">
> >> <soap:operation soapAction="test" style="document"/>
> >> <wsdl:input name="greetMeRequest">
> >> <soap:body use="literal"/>
> >> </wsdl:input>
> >> <wsdl:output name="greetMeResponse">
> >> <soap:body use="literal"/>
> >> </wsdl:output>
> >> </wsdl:operation>
> >> ...
> >> </wsdl:binding>
> >>
> >> I'll get the result of deliveryMode extension.
> >> I think the wsdl extension just can add attributes, element to a
> >> extension element in CXF. But I can't get the extension element's value.
> >> Is it right?
> >>
> >> My question is: how to get the extension information in [1]. What does
> >> the extension schema look like?
> >>
> >> thanks.
> >> Liu

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog