Liu,
I just want to say this is very nice work. Thanks for tackling this. It
almost makes me want to go through the rest of the wsdl extension schemas and
make them not subclass the old TExensibilityElementImpl thing. Would
simplify that stuff quite a bit.
Again, nice job.
Dan
On
Hi,
It looks like the xjc pulgin just loads the extensions once, so you need
to add all the xjc extensions dependencies into each xjc extension test pom.
org.apache.cxf
cxf-xjc-dv
${proje
yeah.
The pom file in the cxf-xjc-wsdlextension:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.apache.cxf
cxf-xjc-wsdlextension
j
I guess you have something wrong on the plugin's pom.
Maybe you need to show the code to let us help you :)
Willem
liucong wrote:
Hi,
I am writing a plugin for xjc.
First I just modify the cxf-xjc-ts and cxf-xjc-ts-test, and make it
work with the -Xwsdlextension, not -Xts. The pom file
Hi,
I am writing a plugin for xjc.
First I just modify the cxf-xjc-ts and cxf-xjc-ts-test, and make it
work with the -Xwsdlextension, not -Xts. The pom file is also changed.
And it works rightly.
Then I copy the modified projects into cxf-xjc-wsdlextension and
cxf-xjc-wsdlextension-tes
Hi,
Thank you for you advice. I do a small experiment. I use
ExtensibilityElement to replace TExtensibilityElementImpl. Also I
modified some codes in the cxf-api project.
It works now.
best regards,
liu
Daniel Kulp wrote:
Liu,
I think for stuff that are "simple" (basically, complex
Liu,
I think for stuff that are "simple" (basically, complexTypes with
simpleContent and simpleType object), you cannot extend
TExtensibilityElementImpl. Instead, you would need to make it implement
ExtensibilityElement interface and add the QName and required fields and such.
Dan
On
Hi,
I do a simple experiment about the design sugguest by Dan.
First, I use jaxb, not xjc. I think they have the principle.
The schema like this[1]:
The generated class for DeliveryModeType like this[2]:
@XmlAccessorType(XmlAcce
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
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 necessa
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:
but I know that doesn't work.
This will probably need some changes to CXF wsdl processing to really get
Hi,
You added a wrong schema, your schema should like this
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]:
http://www.w3.org/2008/07/soap/bindings/JMS/"/>
PERSISTENT
...
If
13 matches
Mail list logo
