Re: Axis2 wsdl2java jibx: No mapping defined for element
Hi, you need to check the binding.xml file and verify there is a correct
mapping defined for ElementName. There should be an entry like this:
value name=ElementName ns=http://sample/types/
The element name and namespace in the binding file needs to match the WSDL
definition.
Anshuk Pal Chaudhuri-2 wrote:
Hello,
Mentioned an incorrect subject line in my earlier mail. My applogies.
I am trying to integrate axis2 1.5 with jibx 1.2.1.
I am not sure that is a problem with axis2 or jibx.
I have the wsdl file and the schema with me.
I have used the jibx org.jibx.schema.codegen.CodeGen to generate the
objects the binding file from the schema.
I then enhance the classes using the jibx binding compiler way.Uptil now
all fine.
Then when am trying to generate server side skeletons using:
org.apache.axis2.wsdl.WSDL2Java -uri Service.wsdl -d jibx -Ebindingfile
binding.xml -s -ss -sd -scn ServiceName
referring
http://ws.apache.org/axis2/1_1_1/jibx/jibx-codegen-integration.html#wsdl
I am getting errors.
The stacktrace:
Exception in thread main
org.apache.axis2.wsdl.codegen..CodeGenerationException
java.lang.RuntimeException: No mapping defined for element
{http://sample/types
}ElementName
I am not sure where I went wrong, also I did find it being mentioned in
quite a few number of places such as,
http://marc.info/?l=axis-userm=117028406518758w=2
But I really did not find any solution, I think somebody has got some
workaround for this.
If I use jaxb instead of jibx, it works fine, there is not binding file in
such a case, is the generated the binding file in correct, I am not really
sure so hinting at different things.
Can anyone help in some workaround.
Regards,
Anshuk
--
View this message in context:
http://www.nabble.com/Axis2-wsdl2java-jibx%3A-No-mapping-defined-for-element-tp25603967p25668398.html
Sent from the Axis - User mailing list archive at Nabble.com.
Axis2 wsdl2java jibx: No mapping defined for element
Hello,
Mentioned an incorrect subject line in my earlier mail. My applogies.
I am trying to integrate axis2 1.5 with jibx 1.2.1.
I am not sure that is a problem with axis2 or jibx.
I have the wsdl file and the schema with me.
I have used the jibx org.jibx.schema.codegen.CodeGen to generate the objects
the binding file from the schema.
I then enhance the classes using the jibx binding compiler way.Uptil now all
fine.
Then when am trying to generate server side skeletons using:
org.apache.axis2.wsdl.WSDL2Java -uri Service.wsdl -d jibx -Ebindingfile
binding.xml -s -ss -sd -scn ServiceName
referring
http://ws.apache.org/axis2/1_1_1/jibx/jibx-codegen-integration.html#wsdl
I am getting errors.
The stacktrace:
Exception in thread main
org.apache.axis2.wsdl.codegen..CodeGenerationException
java.lang.RuntimeException: No mapping defined for element
{http://sample/types
}ElementName
I am not sure where I went wrong, also I did find it being mentioned in quite a
few number of places such as,
http://marc.info/?l=axis-userm=117028406518758w=2
But I really did not find any solution, I think somebody has got some
workaround for this.
If I use jaxb instead of jibx, it works fine, there is not binding file in such
a case, is the generated the binding file in correct, I am not really sure so
hinting at different things.
Can anyone help in some workaround.
Regards,
Anshuk
Re: [Axis2] Axis2 1.2 JiBX update
Dennis, I downloaded your updated axis2-jibx-1.2b.jar replacement for axis2-jibx-1.2.jar and was unable to run your jibx-library example with it. It generated the following exception (and, strangely enough, a BUILD SUCCESSFUL Ant message): ant run Buildfile: build.xml run: [java] Exception in thread main org.apache.axis2.AxisFault: java.lang.NoSuchMethodError: org.apache.axis2.jibx.JiBXDataSource.init(Ljava/lang/Object;ILjava/lang/String;Ljava/lang/String;Ljava/lang/String;[I[Ljava/lang/String;Lorg/jibx/runtime/IBindingFactory;)V [java] at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) [java] at org.apache.axis2.jibx.library.JibxLibraryStub.getBook(JibxLibraryStub.java:474) [java] at org.apache.axis2.jibx.library.WebServiceClient.main(WebServiceClient.java:42) [java] Java Result: 1 BUILD SUCCESSFUL Total time: 2 seconds After replacing the updated axis2-jibx-1.2b.jar with the original axis2-jibx-1.2.jar, the example built and ran fine. Any idea what the cause might be? -David DSosnoski wrote: Hi Pavel, If you can email me (directly) the trace from the exception I'll try to see what's going wrong and get it corrected. If you can also send me your WSDL and binding, along with the generated stub and message receiver, these would probably help. - Dennis Pavel Sharov wrote: Dennis and others, I am using Axis2 1.1.1. I've updated my old Axis2 JiBX distribution 'axis2-jibx-1.1.1.jar' with the newest one 'axis2-jibx-1.1.1c.jar' probably you are talking about in your posting here (downloaded it from http://www.sosnoski.com/jibx-wiki/space/axis2-jibx). I will not go deeply into details now - will put my problem briefly, maybe that will suffice to get a hint on the reason of the problem. I'm using the WSDL2Java to generate both client and server Java code from my WSDL and some JiBX bindings. With the previous distribution it's all ok. However, with the recent update, I am getting a Namespace not found error (which namespace - not specified) in runtime when trying to marshall/unmarshall. The exception is caused by a call to the constructor of org.apache.axis2.jibx.JiBXDataSource class, either in my client stub or in my server message receiver. I wouldn't like to continue using the old distribution as I see some important bugs fixed in the new one. Could you please give me any hint on what is going on? Thank you a lot in advance! Pavel -Original Message- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 3:30 PM To: axis-user Subject: [Axis2] Axis2 1.2 JiBX update I've updated the axis2-jibx.jar module for the 1.2 release of Axis2 to fix some problems with serialization (discovered while testing my validation module :-[ - see the prior post). The update is available on the axis2-jibx wiki page: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx The same issues are likely causing problems some users have experienced using JiBX with Rampart on the 1.1.1 release. I'll try to backport the fixes to the 1.1.1 code soon. - Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/RE%3A--Axis2--Axis2-1.2-JiBX-update-tf3833808.html#a11177870 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Axis2 1.2 JiBX update
Dennis and others, I am using Axis2 1.1.1. I've updated my old Axis2 JiBX distribution 'axis2-jibx-1.1.1.jar' with the newest one 'axis2-jibx-1.1.1c.jar' probably you are talking about in your posting here (downloaded it from http://www.sosnoski.com/jibx-wiki/space/axis2-jibx). I will not go deeply into details now - will put my problem briefly, maybe that will suffice to get a hint on the reason of the problem. I'm using the WSDL2Java to generate both client and server Java code from my WSDL and some JiBX bindings. With the previous distribution it's all ok. However, with the recent update, I am getting a Namespace not found error (which namespace - not specified) in runtime when trying to marshall/unmarshall. The exception is caused by a call to the constructor of org.apache.axis2.jibx.JiBXDataSource class, either in my client stub or in my server message receiver. I wouldn't like to continue using the old distribution as I see some important bugs fixed in the new one. Could you please give me any hint on what is going on? Thank you a lot in advance! Pavel -Original Message- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 3:30 PM To: axis-user Subject: [Axis2] Axis2 1.2 JiBX update I've updated the axis2-jibx.jar module for the 1.2 release of Axis2 to fix some problems with serialization (discovered while testing my validation module :-[ - see the prior post). The update is available on the axis2-jibx wiki page: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx The same issues are likely causing problems some users have experienced using JiBX with Rampart on the 1.1.1 release. I'll try to backport the fixes to the 1.1.1 code soon. - Dennis -- Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.2 JiBX update
Hi Pavel, If you can email me (directly) the trace from the exception I'll try to see what's going wrong and get it corrected. If you can also send me your WSDL and binding, along with the generated stub and message receiver, these would probably help. - Dennis Pavel Sharov wrote: Dennis and others, I am using Axis2 1.1.1. I've updated my old Axis2 JiBX distribution 'axis2-jibx-1.1.1.jar' with the newest one 'axis2-jibx-1.1.1c.jar' probably you are talking about in your posting here (downloaded it from http://www.sosnoski.com/jibx-wiki/space/axis2-jibx). I will not go deeply into details now - will put my problem briefly, maybe that will suffice to get a hint on the reason of the problem. I'm using the WSDL2Java to generate both client and server Java code from my WSDL and some JiBX bindings. With the previous distribution it's all ok. However, with the recent update, I am getting a Namespace not found error (which namespace - not specified) in runtime when trying to marshall/unmarshall. The exception is caused by a call to the constructor of org.apache.axis2.jibx.JiBXDataSource class, either in my client stub or in my server message receiver. I wouldn't like to continue using the old distribution as I see some important bugs fixed in the new one. Could you please give me any hint on what is going on? Thank you a lot in advance! Pavel -Original Message- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 3:30 PM To: axis-user Subject: [Axis2] Axis2 1.2 JiBX update I've updated the axis2-jibx.jar module for the 1.2 release of Axis2 to fix some problems with serialization (discovered while testing my validation module :-[ - see the prior post). The update is available on the axis2-jibx wiki page: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx The same issues are likely causing problems some users have experienced using JiBX with Rampart on the 1.1.1 release. I'll try to backport the fixes to the 1.1.1 code soon. - Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.2 JiBX update
Ok, added a fix for this (along with a couple of other issues) to the 1.2 update and also backported the update to 1.1.1. - Dennis Dennis Sosnoski wrote: Hi Joanna, Misleading error message, an something that should probably not be an error in the first place. What's really going on is that the code expects abstract mappings to use a type-name, and if an abstract mapping has neither name nor type-name you'll get this error. If you can add either a type-name or a name to this mapping without messing up the binding that should get you through it; otherwise, I'll get this fixed later today and do an update. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Joanna Muench wrote: Thanks for fixing that so quickly Dennis. I need to update to Axis2 1.2 since in Axis2 1.1.1 I'm not able to see the wsdl despite putting it under META-INF in the .aar (works in 1.2). But the new wsdl2java doesn't like my jibx bindings and I get the following error: [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Non-abstract mapping for class edu.iris.ws.base.Author needs element name. [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main (WSDL2Java.java:21) The error occurs with jibx 1.3, 1.4 and your most recent jars. Thanks, Joanna On 5/17/07, *Dennis Sosnoski* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I've updated the axis2-jibx.jar module for the 1.2 release of Axis2 to fix some problems with serialization (discovered while testing my validation module :-[ - see the prior post). The update is available on the axis2-jibx wiki page: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx The same issues are likely causing problems some users have experienced using JiBX with Rampart on the 1.1.1 release. I'll try to backport the fixes to the 1.1.1 code soon. - Dennis -- Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Axis2 1.2 JiBX update
I've updated the axis2-jibx.jar module for the 1.2 release of Axis2 to fix some problems with serialization (discovered while testing my validation module :-[ - see the prior post). The update is available on the axis2-jibx wiki page: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx The same issues are likely causing problems some users have experienced using JiBX with Rampart on the 1.1.1 release. I'll try to backport the fixes to the 1.1.1 code soon. - Dennis -- Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.2 JiBX update
Thanks for fixing that so quickly Dennis. I need to update to Axis2 1.2 since in Axis2 1.1.1 I'm not able to see the wsdl despite putting it under META-INF in the .aar (works in 1.2). But the new wsdl2java doesn't like my jibx bindings and I get the following error: [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Non-abstract mapping for class edu.iris.ws.base.Author needs element name. [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate( CodeGenerationEngine.java:256) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) The error occurs with jibx 1.3, 1.4 and your most recent jars. Thanks, Joanna On 5/17/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: I've updated the axis2-jibx.jar module for the 1.2 release of Axis2 to fix some problems with serialization (discovered while testing my validation module :-[ - see the prior post). The update is available on the axis2-jibx wiki page: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx The same issues are likely causing problems some users have experienced using JiBX with Rampart on the 1.1.1 release. I'll try to backport the fixes to the 1.1.1 code soon. - Dennis -- Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.2 JiBX update
Hi Joanna, Misleading error message, an something that should probably not be an error in the first place. What's really going on is that the code expects abstract mappings to use a type-name, and if an abstract mapping has neither name nor type-name you'll get this error. If you can add either a type-name or a name to this mapping without messing up the binding that should get you through it; otherwise, I'll get this fixed later today and do an update. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Joanna Muench wrote: Thanks for fixing that so quickly Dennis. I need to update to Axis2 1.2 since in Axis2 1.1.1 I'm not able to see the wsdl despite putting it under META-INF in the .aar (works in 1.2). But the new wsdl2java doesn't like my jibx bindings and I get the following error: [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Non-abstract mapping for class edu.iris.ws.base.Author needs element name. [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main (WSDL2Java.java:21) The error occurs with jibx 1.3, 1.4 and your most recent jars. Thanks, Joanna On 5/17/07, *Dennis Sosnoski* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I've updated the axis2-jibx.jar module for the 1.2 release of Axis2 to fix some problems with serialization (discovered while testing my validation module :-[ - see the prior post). The update is available on the axis2-jibx wiki page: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx The same issues are likely causing problems some users have experienced using JiBX with Rampart on the 1.1.1 release. I'll try to backport the fixes to the 1.1.1 code soon. - Dennis -- Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : Re: axis2 with jibx
JiBX data binding is the only option that *does* support unwrapped in
the 1.1.1 release. I'm not sure about the cause of your problem, Benoit,
but I've posted a detailed example of JiBX unwrapped handling with full
source code and build files at
http://www.sosnoski.com/jibx-wiki/space/axis2-jibx Try running through
that example and see if it helps.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Benoit Decherf wrote:
Why is the wrapped style a prefered option ?
The big advantage of unwrapped style is to use my own class. If I use
the wrapped style I would have to transform the object used by axis to
my own object.
So, is there another databing which let me use my own class (so
unwrapped style) with jdk 1.4 ?
Thanks
Benoit
*/Nilesh Ghorpade [EMAIL PROTECTED]/* a écrit :
Hi,
I believe the JiBX has not got an extensive support for unwrapped
document style. Hence you had to change the WSDL as well as the
binding file.
I suggest you go in for the wrapped style which is also a
preffered option over unwrapped.
The way you are passing the binding file to the code gen task is
correct i.e. using the -Ebindingfile option.
Hope this helps :-)
Regards
Nile
*/Benoit Decherf [EMAIL PROTECTED]/* wrote:
Hi,
I'm trying to create a webservice using jibx.
So first, I create my business class and my dto.
Then, I create the jibx binding:
java -cp
~/tools/jibx-genbinding.jar:~/jibx/lib/jibx-bind.jar:src/
org.jibx.binding.BindingGenerator -f resources/binding.xml -m
samples.quickstart.dto.Person
Then, the wsdl:
java2wsdl.sh -o resources/ -cp build -cn
samples.quickstart.service.jibx.TestService
And now, I want to create the message receiver and the
skeleton interface. But when if I just execute:
wsdl2java.sh -uri TestService.wsdl -o build -d jibx
-Ebindingfile resources/binding.xml -uw -sd -ss --ssi
I've got an error:
Caused by: java.lang.RuntimeException: Cannot unwrap element
{http://jibx.service.quickstart.samples/xsd}getPersonResponse:
no abstract mapping definition found for type
{http://dto.quickstart.samples/xsd}Person (used by element
{http://jibx.service.quickstart.samples/xsd}return)
at
org.apache.axis2.jibx.CodeGenerationUtility.unwrapMessage(CodeGenerationUtility.java:576)
To generate the classes I need first to modify the binding and
the wsdl. What is wrong with the commands ?
My other question is :
How can I pass the binding file to the codegen task ?
Découvrez une nouvelle façon d'obtenir des réponses à toutes
vos questions ! Profitez des connaissances, des opinions et
des expériences des internautes sur Yahoo! Questions/Réponses
http://fr.rd.yahoo.com/evt=42054/*http://fr.answers.yahoo.com.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
questions ! Profitez des connaissances, des opinions et des
expériences des internautes sur Yahoo! Questions/Réponses
http://fr.rd.yahoo.com/evt=42054/*http://fr.answers.yahoo.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE : Re: axis2 with jibx
Why is the wrapped style a prefered option ?
The big advantage of unwrapped style is to use my own class. If I use the
wrapped style I would have to transform the object used by axis to my own
object.
So, is there another databing which let me use my own class (so unwrapped
style) with jdk 1.4 ?
Thanks
Benoit
Nilesh Ghorpade [EMAIL PROTECTED] a écrit : Hi,
I believe the JiBX has not got an extensive support for unwrapped document
style. Hence you had to change the WSDL as well as the binding file.
I suggest you go in for the wrapped style which is also a preffered option
over unwrapped.
The way you are passing the binding file to the code gen task is correct i.e.
using the -Ebindingfile option.
Hope this helps :-)
Regards
Nile
Benoit Decherf [EMAIL PROTECTED] wrote: Hi,
I'm trying to create a webservice using jibx.
So first, I create my business class and my dto.
Then, I create the jibx binding:
java -cp ~/tools/jibx-genbinding.jar:~/jibx/lib/jibx-bind.jar:src/
org.jibx.binding.BindingGenerator -f resources/binding.xml -m
samples.quickstart.dto.Person
Then, the wsdl:
java2wsdl.sh -o resources/ -cp build -cn
samples.quickstart.service.jibx.TestService
And now, I want to create the message receiver and the skeleton interface. But
when if I just execute:
wsdl2java.sh -uri TestService.wsdl -o build -d jibx -Ebindingfile
resources/binding.xml -uw -sd -ss --ssi
I've got an error:
Caused by: java.lang.RuntimeException: Cannot unwrap element
{http://jibx.service.quickstart.samples/xsd}getPersonResponse: no abstract
mapping definition found for type {http://dto.quickstart.samples/xsd}Person
(used by element {http://jibx.service.quickstart.samples/xsd}return)
at
org.apache.axis2.jibx.CodeGenerationUtility.unwrapMessage(CodeGenerationUtility.java:576)
To generate the classes I need first to modify the binding and the wsdl. What
is wrong with the commands ?
My other question is :
How can I pass the binding file to the codegen task ?
-
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes
sur Yahoo! Questions/Réponses.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses.
axis2 with jibx
Hi,
I'm trying to create a webservice using jibx.
So first, I create my business class and my dto.
Then, I create the jibx binding:
java -cp ~/tools/jibx-genbinding.jar:~/jibx/lib/jibx-bind.jar:src/
org.jibx.binding.BindingGenerator -f resources/binding.xml -m
samples.quickstart.dto.Person
Then, the wsdl:
java2wsdl.sh -o resources/ -cp build -cn
samples.quickstart.service.jibx.TestService
And now, I want to create the message receiver and the skeleton interface. But
when if I just execute:
wsdl2java.sh -uri TestService.wsdl -o build -d jibx -Ebindingfile
resources/binding.xml -uw -sd -ss --ssi
I've got an error:
Caused by: java.lang.RuntimeException: Cannot unwrap element
{http://jibx.service.quickstart.samples/xsd}getPersonResponse: no abstract
mapping definition found for type {http://dto.quickstart.samples/xsd}Person
(used by element {http://jibx.service.quickstart.samples/xsd}return)
at
org.apache.axis2.jibx.CodeGenerationUtility.unwrapMessage(CodeGenerationUtility.java:576)
To generate the classes I need first to modify the binding and the wsdl. What
is wrong with the commands ?
My other question is :
How can I pass the binding file to the codegen task ?
-
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses.
Re: axis2 with jibx
Hi,
I believe the JiBX has not got an extensive support for unwrapped document
style. Hence you had to change the WSDL as well as the binding file.
I suggest you go in for the wrapped style which is also a preffered option
over unwrapped.
The way you are passing the binding file to the code gen task is correct i.e.
using the -Ebindingfile option.
Hope this helps :-)
Regards
Nile
Benoit Decherf [EMAIL PROTECTED] wrote: Hi,
I'm trying to create a webservice using jibx.
So first, I create my business class and my dto.
Then, I create the jibx binding:
java -cp ~/tools/jibx-genbinding.jar:~/jibx/lib/jibx-bind.jar:src/
org.jibx.binding.BindingGenerator -f resources/binding.xml -m
samples.quickstart.dto.Person
Then, the wsdl:
java2wsdl.sh -o resources/ -cp build -cn
samples.quickstart.service.jibx.TestService
And now, I want to create the message receiver and the skeleton interface. But
when if I just execute:
wsdl2java.sh -uri TestService.wsdl -o build -d jibx -Ebindingfile
resources/binding.xml -uw -sd -ss --ssi
I've got an error:
Caused by: java.lang.RuntimeException: Cannot unwrap element
{http://jibx.service.quickstart.samples/xsd}getPersonResponse: no abstract
mapping definition found for type {http://dto.quickstart.samples/xsd}Person
(used by element {http://jibx.service.quickstart.samples/xsd}return)
at
org.apache.axis2.jibx.CodeGenerationUtility.unwrapMessage(CodeGenerationUtility.java:576)
To generate the classes I need first to modify the binding and the wsdl. What
is wrong with the commands ?
My other question is :
How can I pass the binding file to the codegen task ?
-
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes
sur Yahoo! Questions/Réponses.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
