Re: XMLBeans binding and defaultnamespace
This problem is created due to two namespaces in WSDL. Attached wsdl has namespace http://infiniti:8080/axis/TestArray.jws for input and http://DefaultNamespace http://defaultnamespace/ for output of messages. Is it the WSDL that is wrong i.e. it should have same namesapce for input and output or it is smoe shortcoming of Axis2 to not able to parse such wsdl, i am using Xmlbeans as databinding. On Thu, Jan 14, 2010 at 4:57 PM, rahul yadav rahulyada...@gmail.com wrote: Hi All, I am using XMLBeans databinding to generate java from wsdl, in the generated source a package named defaultnamespace and defaultnamespace.impl are also generated. When i try to call the webservice using generated stub it throws exception complaining about this package. here is the trace log. org.apache.axis2.AxisFault: error: The document is not a echointarrayrespo...@http://infiniti:8080/axis/TestArray.jws: document element namespace mismatch expected http://infiniti:8080/axis/TestArray.jws; got http://DefaultNamespace; at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at testarray20100114155323.TestArrayServiceStub.fromOM(TestArrayServiceStub.java:468) at testarray20100114155323.TestArrayServiceStub.echoIntArray(TestArrayServiceStub.java:189) at client.Consumer.main(Consumer.java:30) Caused by: org.apache.xmlbeans.XmlException: error: The document is not a echointarrayrespo...@http://infiniti:8080/axis/TestArray.jws: document element namespace mismatch expected http://infiniti:8080/axis/TestArray.jws; got http://DefaultNamespace; at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) at testarray20100114155323.EchoIntArrayResponseDocument$Factory.parse(EchoIntArrayResponseDocument.java:128) at testarray20100114155323.TestArrayServiceStub.fromOM(TestArrayServiceStub.java:457) ... 2 more Attached is the wsdl used to generate java source. Can sombody suggest me what is going wrong? and why this defaulnamespace package is getting created. Thanks Regards, Rahul Yadav
Re: XMLBeans binding and defaultnamespace
does anybody has idea on this issue? Is this the shortcoming of Axis2?? On Thu, Jan 14, 2010 at 4:57 PM, rahul yadav rahulyada...@gmail.com wrote: Hi All, I am using XMLBeans databinding to generate java from wsdl, in the generated source a package named defaultnamespace and defaultnamespace.impl are also generated. When i try to call the webservice using generated stub it throws exception complaining about this package. here is the trace log. org.apache.axis2.AxisFault: error: The document is not a echointarrayrespo...@http://infiniti:8080/axis/TestArray.jws: document element namespace mismatch expected http://infiniti:8080/axis/TestArray.jws; got http://DefaultNamespace; at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at testarray20100114155323.TestArrayServiceStub.fromOM(TestArrayServiceStub.java:468) at testarray20100114155323.TestArrayServiceStub.echoIntArray(TestArrayServiceStub.java:189) at client.Consumer.main(Consumer.java:30) Caused by: org.apache.xmlbeans.XmlException: error: The document is not a echointarrayrespo...@http://infiniti:8080/axis/TestArray.jws: document element namespace mismatch expected http://infiniti:8080/axis/TestArray.jws; got http://DefaultNamespace; at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) at testarray20100114155323.EchoIntArrayResponseDocument$Factory.parse(EchoIntArrayResponseDocument.java:128) at testarray20100114155323.TestArrayServiceStub.fromOM(TestArrayServiceStub.java:457) ... 2 more Attached is the wsdl used to generate java source. Can sombody suggest me what is going wrong? and why this defaulnamespace package is getting created. Thanks Regards, Rahul Yadav
XMLBeans binding and defaultnamespace
Hi All, I am using XMLBeans databinding to generate java from wsdl, in the generated source a package named defaultnamespace and defaultnamespace.impl are also generated. When i try to call the webservice using generated stub it throws exception complaining about this package. here is the trace log. org.apache.axis2.AxisFault: error: The document is not a echointarrayrespo...@http://infiniti:8080/axis/TestArray.jws: document element namespace mismatch expected http://infiniti:8080/axis/TestArray.jws; got http://DefaultNamespace; at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at testarray20100114155323.TestArrayServiceStub.fromOM(TestArrayServiceStub.java:468) at testarray20100114155323.TestArrayServiceStub.echoIntArray(TestArrayServiceStub.java:189) at client.Consumer.main(Consumer.java:30) Caused by: org.apache.xmlbeans.XmlException: error: The document is not a echointarrayrespo...@http://infiniti:8080/axis/TestArray.jws: document element namespace mismatch expected http://infiniti:8080/axis/TestArray.jws; got http://DefaultNamespace; at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) at testarray20100114155323.EchoIntArrayResponseDocument$Factory.parse(EchoIntArrayResponseDocument.java:128) at testarray20100114155323.TestArrayServiceStub.fromOM(TestArrayServiceStub.java:457) ... 2 more Attached is the wsdl used to generate java source. Can sombody suggest me what is going wrong? and why this defaulnamespace package is getting created. Thanks Regards, Rahul Yadav TestArray.jws Description: Binary data
Re: Use XMLBeans with Axis1?
wsdl2java could use xmlbeans when you invoking it to map wsdl objects in java beans. You can use SOAPUI , a GUI to automate webservice code generation using Axis1 o 2 (and not only axis), to do that. So on generated classes you can manipulate objects using get set, so xmlBeans is transparent to the programmer, you can see it just as included packeges in generated classes. I hope to be more clear. Bye Olindo 2009/11/17 KARR, DAVID (ATTCINW) dk0...@att.com Ok, I guess I should have worded my question differently. Can you tell me HOW you did it? Show me the required elements and what they look like. *From:* Olindo Pindaro [mailto:o.pind...@gmail.com] *Sent:* Monday, November 16, 2009 2:59 PM *To:* axis-user@ws.apache.org *Subject:* Re: Use XMLBeans with Axis1? I just relased a project using Axis 1.4 with xmlbeans. No problem, the Integration is natural, seamless. 2009/11/16 KARR, DAVID (ATTCINW) dk0...@att.com I know that usage of Axis1 is probably pretty rare now, but I wanted to know whether there is any (successful) experience integrating Axis1 with XMLBeans. I've done some searches on the internet, and the only ones I found were people who gave up. :) Bye! -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830 -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830
RE: Use XMLBeans with Axis1?
Specifically, I need to see exactly how you tell wsdl2java to use xmlbeans. I'm using the Ant task. I don't need to know that I can, I just need to know how to do it. I've examined the available options for the Ant task, and I just don't see it. From: Olindo Pindaro [mailto:o.pind...@gmail.com] Sent: Tuesday, November 17, 2009 1:13 AM To: axis-user@ws.apache.org Subject: Re: Use XMLBeans with Axis1? wsdl2java could use xmlbeans when you invoking it to map wsdl objects in java beans. You can use SOAPUI , a GUI to automate webservice code generation using Axis1 o 2 (and not only axis), to do that. So on generated classes you can manipulate objects using get set, so xmlBeans is transparent to the programmer, you can see it just as included packeges in generated classes. I hope to be more clear. Bye Olindo 2009/11/17 KARR, DAVID (ATTCINW) dk0...@att.com Ok, I guess I should have worded my question differently. Can you tell me HOW you did it? Show me the required elements and what they look like. From: Olindo Pindaro [mailto:o.pind...@gmail.com] Sent: Monday, November 16, 2009 2:59 PM To: axis-user@ws.apache.org Subject: Re: Use XMLBeans with Axis1? I just relased a project using Axis 1.4 with xmlbeans. No problem, the Integration is natural, seamless. 2009/11/16 KARR, DAVID (ATTCINW) dk0...@att.com I know that usage of Axis1 is probably pretty rare now, but I wanted to know whether there is any (successful) experience integrating Axis1 with XMLBeans. I've done some searches on the internet, and the only ones I found were people who gave up. :) Bye! -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830 -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830
Re: Use XMLBeans with Axis1?
I dont'use Ant, i use SoapUI, http://www.soapui.org/, more easy. 2009/11/17 KARR, DAVID (ATTCINW) dk0...@att.com Specifically, I need to see exactly how you tell wsdl2java to use xmlbeans. I’m using the Ant task. I don’t need to know that I can, I just need to know how to do it. I’ve examined the available options for the Ant task, and I just don’t see it. *From:* Olindo Pindaro [mailto:o.pind...@gmail.com] *Sent:* Tuesday, November 17, 2009 1:13 AM *To:* axis-user@ws.apache.org *Subject:* Re: Use XMLBeans with Axis1? wsdl2java could use xmlbeans when you invoking it to map wsdl objects in java beans. You can use SOAPUI , a GUI to automate webservice code generation using Axis1 o 2 (and not only axis), to do that. So on generated classes you can manipulate objects using get set, so xmlBeans is transparent to the programmer, you can see it just as included packeges in generated classes. I hope to be more clear. Bye Olindo 2009/11/17 KARR, DAVID (ATTCINW) dk0...@att.com Ok, I guess I should have worded my question differently. Can you tell me HOW you did it? Show me the required elements and what they look like. *From:* Olindo Pindaro [mailto:o.pind...@gmail.com] *Sent:* Monday, November 16, 2009 2:59 PM *To:* axis-user@ws.apache.org *Subject:* Re: Use XMLBeans with Axis1? I just relased a project using Axis 1.4 with xmlbeans. No problem, the Integration is natural, seamless. 2009/11/16 KARR, DAVID (ATTCINW) dk0...@att.com I know that usage of Axis1 is probably pretty rare now, but I wanted to know whether there is any (successful) experience integrating Axis1 with XMLBeans. I've done some searches on the internet, and the only ones I found were people who gave up. :) Bye! -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830 -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830 -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830
Use XMLBeans with Axis1?
I know that usage of Axis1 is probably pretty rare now, but I wanted to know whether there is any (successful) experience integrating Axis1 with XMLBeans. I've done some searches on the internet, and the only ones I found were people who gave up. :)
RE: Use XMLBeans with Axis1?
Ok, I guess I should have worded my question differently. Can you tell me HOW you did it? Show me the required elements and what they look like. From: Olindo Pindaro [mailto:o.pind...@gmail.com] Sent: Monday, November 16, 2009 2:59 PM To: axis-user@ws.apache.org Subject: Re: Use XMLBeans with Axis1? I just relased a project using Axis 1.4 with xmlbeans. No problem, the Integration is natural, seamless. 2009/11/16 KARR, DAVID (ATTCINW) dk0...@att.com I know that usage of Axis1 is probably pretty rare now, but I wanted to know whether there is any (successful) experience integrating Axis1 with XMLBeans. I've done some searches on the internet, and the only ones I found were people who gave up. :) Bye! -- Olindo Pindaro http://www.linkedin.com/in/olindopindaro +39 3939455830
Re: Regarding XMLBeans generation Of files
Certainly you can do this - XMLBeans is open source code, so get a copy of the source and modify it to generate the kind of class structure you want in your own custom version. Otherwise, follow Amila's suggestion and go with another data binding approach. ADB is very easy to use with Axis2 and provides good support for schema. JAXB's data model isn't quite as nice as ADB's, but probably has been more thoroughly tested with all kinds of schema variations. JiBX lets you customize the data model, and works especially well with modular schemas where different groups are using different subsets of the overall schema, but currently requires you to generate the data model separately from the Axis2 linkage code and doesn't support all features of schema (with xsi:type the most significant lack). Unfortunately (from your point of view), all of these other data bindings use simpler models than those generated by XMLBeans, so you're going to need to make changes to your application code to work with the other bindings. On the plus side, your application code should be significantly simpler once you've made the changes (and will also run somewhat faster). - Dennis -- Dennis M. Sosnoski Java XML and Web Services 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 sri ram wrote: Can some one look into this . --- On *Fri, 16/10/09, sri ram /pinnamaraju_sri...@yahoo.co.in/* wrote: From: sri ram pinnamaraju_sri...@yahoo.co.in Subject: Re: Regarding XMLBeans generation Of files To: axis-user@ws.apache.org Date: Friday, 16 October, 2009, 12:02 PM Since we have already done an extensive coding using this databinding . Its highly unlikely to revert back. So now we are trying to improvise the generator itself :( Hmm ... is there no other way to achieve the below queries. -Sriram --- On *Fri, 16/10/09, Amila Suriarachchi /amilasuriarach...@gmail.com/* wrote: From: Amila Suriarachchi amilasuriarach...@gmail.com Subject: Re: Regarding XMLBeans generation Of files To: axis-user@ws.apache.org Date: Friday, 16 October, 2009, 11:56 AM can you try another data binding frame work like adb or jaxbri. thanks, Amila. On Thu, Oct 15, 2009 at 2:51 PM, sri ram pinnamaraju_sri...@yahoo.co.in wrote: Attaching the files --- On *Thu, 15/10/09, sri ram /pinnamaraju_sri...@yahoo.co.in/* wrote: From: sri ram pinnamaraju_sri...@yahoo.co.in Subject: Regarding XMLBeans generation Of files To: axis-user@ws.apache.org Date: Thursday, 15 October, 2009, 2:50 PM Hi all, As we know that XMLbeans generates a lot of file reading the schema. I have tried my best to modify the schema to best known format to reduce the number of files. And I have been succesfull in doing that . What I see is that there are a lot of unused methods that are getting generated in files that are generated .Unused in my code of implementation. For example there are a lot of overloaded parse methods that are generated ,which are public and static and hence need to be loaded in the memory even if they are used or not. So my concern is can we suppress the generation of these methods by using some options in the command line (while compiling the schema). Else can we change the source code of the XMLBeans generator to get the required methods. If yes what are jars that we can modify without violating any of the rules of open source code . I have attached two files to show the number of methods that are actually in use. And what we want to achieve. The number of files that are generated are 4029 . The number of line we want to reduce is 50 line in each file . ie approx 50 * 4000= 200,000 Our schema is ever increasing with every version. It will allow my application to work better and faster. Can someone quickly respond to it. Thanks in advance -Sriram Now, send attachments up to 25MB with Yahoo! India Mail. Learn how http://in.rd.yahoo.com/tagline_galaxy_2/*http://in.overview.mail.yahoo.com/photos
Re: Regarding XMLBeans generation Of files
can you try another data binding frame work like adb or jaxbri. thanks, Amila. On Thu, Oct 15, 2009 at 2:51 PM, sri ram pinnamaraju_sri...@yahoo.co.inwrote: Attaching the files --- On *Thu, 15/10/09, sri ram pinnamaraju_sri...@yahoo.co.in* wrote: From: sri ram pinnamaraju_sri...@yahoo.co.in Subject: Regarding XMLBeans generation Of files To: axis-user@ws.apache.org Date: Thursday, 15 October, 2009, 2:50 PM Hi all, As we know that XMLbeans generates a lot of file reading the schema. I have tried my best to modify the schema to best known format to reduce the number of files. And I have been succesfull in doing that . What I see is that there are a lot of unused methods that are getting generated in files that are generated .Unused in my code of implementation. For example there are a lot of overloaded parse methods that are generated ,which are public and static and hence need to be loaded in the memory even if they are used or not. So my concern is can we suppress the generation of these methods by using some options in the command line (while compiling the schema). Else can we change the source code of the XMLBeans generator to get the required methods. If yes what are jars that we can modify without violating any of the rules of open source code . I have attached two files to show the number of methods that are actually in use. And what we want to achieve. The number of files that are generated are 4029 . The number of line we want to reduce is 50 line in each file . ie approx 50 * 4000= 200,000 Our schema is ever increasing with every version. It will allow my application to work better and faster. Can someone quickly respond to it. Thanks in advance -Sriram -- Now, send attachments up to 25MB with Yahoo! India Mail. Learn howhttp://in.rd.yahoo.com/tagline_galaxy_2/*http://in.overview.mail.yahoo.com/photos . -- Connect more, do more and share more with Yahoo! India Mail. Learn morehttp://in.rd.yahoo.com/tagline_galaxy_3/*http://in.overview.mail.yahoo.com/ . -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Regarding XMLBeans generation Of files
Since we have already done an extensive coding using this databinding . Its highly unlikely to revert back. So now we are trying to improvise the generator itself :( Hmm ... is there no other way to achieve the below queries. -Sriram --- On Fri, 16/10/09, Amila Suriarachchi amilasuriarach...@gmail.com wrote: From: Amila Suriarachchi amilasuriarach...@gmail.com Subject: Re: Regarding XMLBeans generation Of files To: axis-user@ws.apache.org Date: Friday, 16 October, 2009, 11:56 AM can you try another data binding frame work like adb or jaxbri. thanks, Amila. On Thu, Oct 15, 2009 at 2:51 PM, sri ram pinnamaraju_sri...@yahoo.co.in wrote: Attaching the files --- On Thu, 15/10/09, sri ram pinnamaraju_sri...@yahoo.co.in wrote: From: sri ram pinnamaraju_sri...@yahoo.co.in Subject: Regarding XMLBeans generation Of files To: axis-user@ws.apache.org Date: Thursday, 15 October, 2009, 2:50 PM Hi all, As we know that XMLbeans generates a lot of file reading the schema. I have tried my best to modify the schema to best known format to reduce the number of files. And I have been succesfull in doing that . What I see is that there are a lot of unused methods that are getting generated in files that are generated .Unused in my code of implementation. For example there are a lot of overloaded parse methods that are generated ,which are public and static and hence need to be loaded in the memory even if they are used or not. So my concern is can we suppress the generation of these methods by using some options in the command line (while compiling the schema). Else can we change the source code of the XMLBeans generator to get the required methods. If yes what are jars that we can modify without violating any of the rules of open source code . I have attached two files to show the number of methods that are actually in use. And what we want to achieve. The number of files that are generated are 4029 . The number of line we want to reduce is 50 line in each file . ie approx 50 * 4000= 200,000 Our schema is ever increasing with every version. It will allow my application to work better and faster. Can someone quickly respond to it. Thanks in advance -Sriram Now, send attachments up to 25MB with Yahoo! India Mail. Learn how. Connect more, do more and share more with Yahoo! India Mail. Learn more. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/ Keep up with people you care about with Yahoo! India Mail. Learn how. http://in.overview.mail.yahoo.com/connectmore
Regarding XMLBeans generation Of files
Hi all, As we know that XMLbeans generates a lot of file reading the schema. I have tried my best to modify the schema to best known format to reduce the number of files. And I have been succesfull in doing that . What I see is that there are a lot of unused methods that are getting generated in files that are generated .Unused in my code of implementation. For example there are a lot of overloaded parse methods that are generated ,which are public and static and hence need to be loaded in the memory even if they are used or not. So my concern is can we suppress the generation of these methods by using some options in the command line (while compiling the schema). Else can we change the source code of the XMLBeans generator to get the required methods. If yes what are jars that we can modify without violating any of the rules of open source code . I have attached two files to show the number of methods that are actually in use. And what we want to achieve. The number of files that are generated are 4029 . The number of line we want to reduce is 50 line in each file . ie approx 50 * 4000= 200,000 Our schema is ever increasing with every version. It will allow my application to work better and faster. Can someone quickly respond to it. Thanks in advance -Sriram Keep up with people you care about with Yahoo! India Mail. Learn how. http://in.overview.mail.yahoo.com/connectmore
Re: Regarding XMLBeans generation Of files
Attaching the files
--- On Thu, 15/10/09, sri ram pinnamaraju_sri...@yahoo.co.in wrote:
From: sri ram pinnamaraju_sri...@yahoo.co.in
Subject: Regarding XMLBeans generation Of files
To: axis-user@ws.apache.org
Date: Thursday, 15 October, 2009, 2:50 PM
Hi all,
As we know that XMLbeans generates a lot of file reading the schema.
I have tried my best to modify the schema to best known format to reduce the
number of files.
And I have been succesfull in doing that .
What I see is that there are a lot of unused methods that are getting
generated in files that are generated .Unused in my code of implementation.
For example there are a lot of overloaded parse methods that are generated
,which are
public and static and hence need to be loaded in the memory even if they are
used or not.
So my concern is can we suppress the generation of these methods
by using some options in the command line (while compiling the schema).
Else can we change the source code of the XMLBeans generator to get the
required methods. If yes what are jars that we can
modify without violating any of the rules of open source code .
I have attached two files to show the number of methods that are actually in
use.
And what we want to achieve.
The number of files that are generated are 4029 .
The number of line we want to reduce is 50 line in each file .
ie approx 50 * 4000= 200,000
Our schema is ever increasing with every version.
It will allow my application to work better and faster.
Can someone quickly respond to it.
Thanks in advance
-Sriram
Now, send attachments up to 25MB with Yahoo! India Mail. Learn how.
Connect more, do more and share more with Yahoo! India Mail. Learn more.
http://in.overview.mail.yahoo.com//*
* XML Type: AddPersonGroupMatrixReq
* Namespace: http://www.kiran.com/AXL/API/8.0
* Java type: com.kiran.www.AddPersonGroupMatrixReq
*
* Automatically generated - do not modify.
*/
package com.kiran.www;
/**
* An XML AddPersonGroupMatrixReq(@http://www.kiran.com).
*
* This is a complex type.
*/
public interface AddPersonGroupMatrixReq extends com.kiran.www.APIRequest
{
public static final org.apache.xmlbeans.SchemaType type =
(org.apache.xmlbeans.SchemaType)
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(AddPersonGroupMatrixReq.class.getClassLoader(),
schemaorg_apache_xmlbeans.system.sC9186F50FFFED779ED0597E80002DA3D).resolveHandle(addPersongroupmatrixreq1467type);
/**
* Gets the PersonGroupMatrix element
*/
com.kiran.www.XPersonGroupMatrix getPersonGroupMatrix();
/**
* Sets the PersonGroupMatrix element
*/
void setPersonGroupMatrix(com.kiran.www.XPersonGroupMatrix
PersonGroupMatrix);
/**
* Appends and returns a new empty PersonGroupMatrix element
*/
com.kiran.www.XPersonGroupMatrix addNewPersonGroupMatrix();
/**
* A factory class with static methods for creating instances
* of this type.
*/
public static final class Factory
{
public static com.kiran.www.AddPersonGroupMatrixReq newInstance() {
return (com.kiran.www.AddPersonGroupMatrixReq)
org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, null ); }
public static com.kiran.www.AddPersonGroupMatrixReq
newInstance(org.apache.xmlbeans.XmlOptions options) {
return (com.kiran.www.AddPersonGroupMatrixReq)
org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, options
); }
/** @param xmlAsString the string value to parse */
public static com.kiran.www.AddPersonGroupMatrixReq
parse(java.lang.String xmlAsString) throws org.apache.xmlbeans.XmlException {
return (com.kiran.www.AddPersonGroupMatrixReq)
org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type,
null ); }
public static com.kiran.www.AddPersonGroupMatrixReq
parse(java.lang.String xmlAsString, org.apache.xmlbeans.XmlOptions options)
throws org.apache.xmlbeans.XmlException {
return (com.kiran.www.AddPersonGroupMatrixReq)
org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type,
options ); }
/** @param file the file from which to load an xml document */
public static com.kiran.www.AddPersonGroupMatrixReq parse(java.io.File
file) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (com.kiran.www.AddPersonGroupMatrixReq)
org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, null ); }
public static com.kiran.www.AddPersonGroupMatrixReq parse(java.io.File
file, org.apache.xmlbeans.XmlOptions options) throws
org.apache.xmlbeans.XmlException, java.io.IOException {
return (com.kiran.www.AddPersonGroupMatrixReq)
org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, options
); }
public static
How can I force namespace declarations in the envelope? (Axis2 1.4.1 / XMLbeans 2.3 / Java 1.4.2)
Hi, by default, Axis2 seems to put namespace declarations like 'xmlns:ns=http://my.namespace.com/this/one/is/it;' at the latest / deepest point in the XML possible, which seems to be perfectly in line with W3C requirements. My SOAP client has to talk to the Web Service via a XML security gateway (probably Cisco ACE XML gateway) which is configured to require all namespaces of the request to be declared in the SOAP envelope. How can I achieve that using Axis2 1.4.1? Environment: - IBM WebSphere Application Server 6.0.2 / IBM Java 1.4.2 JRE (stuck to) - Axis2 1.4.1 / XMLbeans 2.3.0 (only for client operation) Examples: That is what Axis2 currently produces, using simply the generated Java stub class: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header Request xmlns=http://premconn.premiereconnect.com/2007/02; soapenv:mustUnderstand=0 ReceiverKeyhttp://my.receiver.key//ReceiverKey RequestIDf0aFQR5s_AIBYHgdN16pqlf/RequestID Authentication XDDSAuth RequesterID###/RequesterID Password***/Password /XDDSAuth /Authentication /Request /soapenv:Header soapenv:Body ns:ListCreateRequest xmlns:ns=http://premconn.premiereconnect.com/2007/02; ns:SubmitIdf0aFQR5s_AIBYHgdN16pqlf/ns:SubmitId etc. etc. etc. And *that* is what ACE XML gateway seems to expect: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns=http://premconn.premiereconnect.com/2007/02; soapenv:Header ns:Request soapenv:mustUnderstand=0 ns:ReceiverKeyhttp://my.receiver.key//ns:ReceiverKey ns:RequestIDf0aFQR5s_AIBYHgdN16pqlf/ns:RequestID ns:Authentication ns:XDDSAuth ns:RequesterID###/ns:RequesterID ns:Password***/ns:Password /ns:XDDSAuth /ns:Authentication /ns:Request /soapenv:Header soapenv:Body ns:ListCreateRequest ns:SubmitIdf0aFQR5s_AIBYHgdN16pqlf/ns:SubmitId etc. etc. etc. How can I force Axis2 to produce output that conforms to these requirements? Maybe this is related to Jira #AXIS2-4215 , URL: https://issues.apache.org/jira/browse/AXIS2-4215 Thanks in advance for useful hints and help, -- Dipl.-Inform. Christian Gosch, PMI PMP Systems Architecture, Project Management inovex GmbH Büro Pforzheim Karlsruher Strasse 71 D-75179 Pforzheim Tel: +49 (0)7231 3191-85 Fax: +49 (0)7231 3191-91 c.go...@inovex.de www.inovex.de Sitz der Gesellschaft: Pforzheim AG Mannheim, HRB 502126 Geschäftsführer: Stephan Müller
RE: How can I force namespace declarations in the envelope? (Axis2 1.4.1 / XMLbeans 2.3 / Java 1.4.2)
Finally I found a solution by deep and rigorous web search... http://stackoverflow.com/questions/74960/how-do-i-add-a-namespace-reference-to-a-soap-response-with-apache-axis2-and-wsdl2 explains how to do it. BUT: The result is not that nice. To be honest: I forgot to mention that I generated the client code with WSDL2Java and wanted to use the generated stu(b|ff) just as it fell on my HD. The solution presented on the page urled above basically supports this approach by adding minimal extensions to the generated code. BUT: (1) You have to add the extension to every method request implementation in the generated code. At least every method implementation your client code will use :-) (2) The approach is to add a namespace declaration as early as possible to the envelope generated. Thats quite fine, but its not early enough: The SOAP message body is already constructed and already contains its own namespace declaration(s) as required, when the envelope is generated. Thus the namespace in question (or: all namespaces in question) tend(s) to be declared twice: In the envelope and at (their) first occurrence in the body. (3) The SOAP header is generated *after* adding the namespace declaration in this approach, but its visibility scope downwards into the element hierarchy is only 1 step, that is: Elements directly beneath the Header element make use of the namespace declared, but elements deeper inside will receive their own default namespace declaration -- using the same URL of course. Finally I do not yet have a confirmation that this format of SOAP call really will pass the XML security gateway. But calling the Web Service directly works fine :-) I will update this thread if there are relevant news :-) Christian -Original Message- From: Christian Gosch Sent: Tuesday, September 22, 2009 3:30 PM To: axis-user Subject: How can I force namespace declarations in the envelope? (Axis2 1.4.1 / XMLbeans 2.3 / Java 1.4.2) Hi, by default, Axis2 seems to put namespace declarations like 'xmlns:ns=http://my.namespace.com/this/one/is/it;' at the latest / deepest point in the XML possible, which seems to be perfectly in line with W3C requirements. My SOAP client has to talk to the Web Service via a XML security gateway (probably Cisco ACE XML gateway) which is configured to require all namespaces of the request to be declared in the SOAP envelope. How can I achieve that using Axis2 1.4.1? Environment: - IBM WebSphere Application Server 6.0.2 / IBM Java 1.4.2 JRE (stuck to) - Axis2 1.4.1 / XMLbeans 2.3.0 (only for client operation) Examples: That is what Axis2 currently produces, using simply the generated Java stub class: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header Request xmlns=http://premconn.premiereconnect.com/2007/02; soapenv:mustUnderstand=0 ReceiverKeyhttp://my.receiver.key//ReceiverKey RequestIDf0aFQR5s_AIBYHgdN16pqlf/RequestID Authentication XDDSAuth RequesterID###/RequesterID Password***/Password /XDDSAuth /Authentication /Request /soapenv:Header soapenv:Body ns:ListCreateRequest xmlns:ns=http://premconn.premiereconnect.com/2007/02; ns:SubmitIdf0aFQR5s_AIBYHgdN16pqlf/ns:SubmitId etc. etc. etc. And *that* is what ACE XML gateway seems to expect: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns=http://premconn.premiereconnect.com/2007/02; soapenv:Header ns:Request soapenv:mustUnderstand=0 ns:ReceiverKeyhttp://my.receiver.key//ns:ReceiverKey ns:RequestIDf0aFQR5s_AIBYHgdN16pqlf/ns:RequestID ns:Authentication ns:XDDSAuth ns:RequesterID###/ns:RequesterID ns:Password***/ns:Password /ns:XDDSAuth /ns:Authentication /ns:Request /soapenv:Header soapenv:Body ns:ListCreateRequest ns:SubmitIdf0aFQR5s_AIBYHgdN16pqlf/ns:SubmitId etc. etc. etc. How can I force Axis2 to produce output that conforms to these requirements? Maybe this is related to Jira #AXIS2-4215 , URL: https://issues.apache.org/jira/browse/AXIS2-4215 Thanks in advance for useful hints and help, -- Dipl.-Inform. Christian Gosch, PMI PMP Systems Architecture, Project Management inovex GmbH Büro Pforzheim Karlsruher Strasse 71 D-75179 Pforzheim Tel: +49 (0)7231 3191-85 Fax: +49 (0)7231 3191-91 c.go...@inovex.de www.inovex.de Sitz der Gesellschaft: Pforzheim AG Mannheim, HRB 502126 Geschäftsführer: Stephan Müller !DSPAM:4ab8d33e326661724765873!
Re: [AXIS2 1.4.1 - Xmlbeans] validating an input parameter with anyType in it
Hello, I don't understand your suggestion; the only types fo any are xs:anyType or xs:anySimpleType , where do you suggests to use Any ? Thanks Martin Kidby a écrit : Hi. I may be wide of the mark, but whilst I was researching my problem, I saw an article similar to your problem that suggested the use of 'Any' rather than 'AnyType' Hope it helps you. -Original Message- From: Michel Etienne [mailto:michel.etie...@dryade.net] Sent: 03 September 2009 15:47 To: axis-user@ws.apache.org; axis-...@ws.apache.org mailto:axis-...@ws.apache.org Subject: Re: [AXIS2 1.4.1 - Xmlbeans] validating an input parameter with anyType in it Hello Since I had no answer yet, I repost my question . Does anybody have an idea ? Thanks Best regards Michel Etienne Michel Etienne a écrit : Hello, I have a problem when I try to validate an input parameter with an AnyType member I use Xmlbeans and I get this error on the server side (I made a sample program to show the problem) 2009-07-06 16:23:16,109 [HttpConnection-8080-1] WARN Server - Invalid object demo.dryade.soap.impl.RequestDocumentImpl error: cvc-elt.4.2: Invalid xsi:type qname: 'typ:SpecificType' in element RequestPart 2009-07-06 16:23:16,125 [HttpConnection-8080-1] WARN Server - Invalid content = soap:Request xmlns:soap=http://soap.dryade.demo; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; RequestPart typ:element6 xmlns:typ=http://types.dryade.demo;1/typ:element6 typ:element7 xmlns:typ=http://types.dryade.demo;test/typ:element7 typ:element8 xsi:type=typ:SpecificType xmlns:typ=http://types.dryade.demo; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; typ:element4true/typ:element4 typ:element5any test/typ:element5 /typ:element8 /RequestPart /soap:Request if the server produce an output with the same AnyType , it validate correctly : in an input-output transaction 2009-07-06 16:23:16,125 [HttpConnection-8080-1] INFO Server - Valid object demo.dryade.soap.impl.RequestResponseDocumentImpl in an ouput-only transaction 2009-07-06 16:23:16,250 [HttpConnection-8080-2] INFO Server - Valid object demo.dryade.soap.impl.NotifyDocumentImpl on the client side, the structures are always valid. I send you the entire code I used for this exemple; it is made with AXIS2 1.4.1 on Windows XP platform with Java 1.6 (I can send the entire project archive if necessary) Thanks for help Best regards Michel Etienne Cambridge Online Systems Ltd is registered in England and Wales with company number 1381717 Registered office: 163 Cambridge Science Park, Milton Road Cambridge CB4 0GP Disclaimer: The contents of this e-mail are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. _ Cambridge Online Latest News: Please visit our Website at http://www.cambridgeonline.net http://www.cambridgeonline.net/ Ce message entrant est certifié sans virus connu. Analyse effectuée par AVG - www.avg.fr Version: 8.5.409 / Base de données virale: 270.13.76/2342 - Date: 09/02/09 18:03:00
RE: [AXIS2 1.4.1 - Xmlbeans] validating an input parameter with anyType in it
Hi. I may be wide of the mark, but whilst I was researching my problem, I saw an article similar to your problem that suggested the use of 'Any' rather than 'AnyType' Hope it helps you. -Original Message- From: Michel Etienne [mailto:michel.etie...@dryade.net] Sent: 03 September 2009 15:47 To: axis-user@ws.apache.org; axis-...@ws.apache.org Subject: Re: [AXIS2 1.4.1 - Xmlbeans] validating an input parameter with anyType in it Hello Since I had no answer yet, I repost my question . Does anybody have an idea ? Thanks Best regards Michel Etienne Michel Etienne a écrit : Hello, I have a problem when I try to validate an input parameter with an AnyType member I use Xmlbeans and I get this error on the server side (I made a sample program to show the problem) 2009-07-06 16:23:16,109 [HttpConnection-8080-1] WARNServer - Invalid object demo.dryade.soap.impl.RequestDocumentImpl error: cvc-elt.4.2: Invalid xsi:type qname: 'typ:SpecificType' in element RequestPart 2009-07-06 16:23:16,125 [HttpConnection-8080-1] WARNServer - Invalid content = soap:Request xmlns:soap=http://soap.dryade.demo; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; RequestPart typ:element6 xmlns:typ=http://types.dryade.demo;1/typ:element6 typ:element7 xmlns:typ=http://types.dryade.demo;test/typ:element7 typ:element8 xsi:type=typ:SpecificType xmlns:typ=http://types.dryade.demo; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; typ:element4true/typ:element4 typ:element5any test/typ:element5 /typ:element8 /RequestPart /soap:Request if the server produce an output with the same AnyType , it validate correctly : in an input-output transaction 2009-07-06 16:23:16,125 [HttpConnection-8080-1] INFO Server - Valid object demo.dryade.soap.impl.RequestResponseDocumentImpl in an ouput-only transaction 2009-07-06 16:23:16,250 [HttpConnection-8080-2] INFO Server - Valid object demo.dryade.soap.impl.NotifyDocumentImpl on the client side, the structures are always valid. I send you the entire code I used for this exemple; it is made with AXIS2 1.4.1 on Windows XP platform with Java 1.6 (I can send the entire project archive if necessary) Thanks for help Best regards Michel Etienne Cambridge Online Systems Ltd is registered in England and Wales with company number 1381717 Registered office: 163 Cambridge Science Park, Milton Road Cambridge CB4 0GP Disclaimer: The contents of this e-mail are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. _ Cambridge Online Latest News: Please visit our Website at http://www.cambridgeonline.net
Problem xmlbeans with swa
Hi all ! Is it possible to use SwA when source code is generated by xmlbeans ? Cause when i do it, the soap message is not well send. There is no body message. Thanks in advance, _ Découvrez toutes les possibilités de communication avec vos proches http://www.microsoft.com/windows/windowslive/default.aspx
[AXIS2 1.4.1 - Xmlbeans] validating an input parameter with anyType in it
Hello,
I have a problem when I try to validate an input parameter with an
AnyType member
I use Xmlbeans and I get this error on the server side (I made a sample
program to show the problem)
2009-07-06 16:23:16,109 [HttpConnection-8080-1] WARN
Server - Invalid object demo.dryade.soap.impl.RequestDocumentImpl
error: cvc-elt.4.2: Invalid xsi:type qname: 'typ:SpecificType' in
element RequestPart
2009-07-06 16:23:16,125 [HttpConnection-8080-1] WARN
Server - Invalid content =
soap:Request xmlns:soap=http://soap.dryade.demo;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
RequestPart
typ:element6 xmlns:typ=http://types.dryade.demo;1/typ:element6
typ:element7 xmlns:typ=http://types.dryade.demo;test/typ:element7
typ:element8 xsi:type=typ:SpecificType
xmlns:typ=http://types.dryade.demo;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
typ:element4true/typ:element4
typ:element5any test/typ:element5
/typ:element8
/RequestPart
/soap:Request
if the server produce an output with the same AnyType , it validate
correctly :
in an input-output transaction
2009-07-06 16:23:16,125 [HttpConnection-8080-1] INFO Server - Valid object
demo.dryade.soap.impl.RequestResponseDocumentImpl
in an ouput-only transaction
2009-07-06 16:23:16,250 [HttpConnection-8080-2] INFO Server - Valid object
demo.dryade.soap.impl.NotifyDocumentImpl
on the client side, the structures are always valid.
I send you the entire code I used for this exemple; it is made with
AXIS2 1.4.1 on Windows XP platform with Java 1.6
(I can send the entire project archive if necessary)
Thanks for help
Best regards
Michel Etienne
Server source :
package demo.server;
import org.apache.log4j.Logger;
import java.util.ArrayList;
import javax.xml.namespace.QName;
import org.apache.xmlbeans.SchemaType;
import org.apache.xmlbeans.XmlBeans;
import org.apache.xmlbeans.XmlObject;
import org.apache.xmlbeans.XmlOptions;
import org.apache.xmlbeans.XmlValidationError;
import org.apache.xmlbeans.impl.common.QNameHelper;
import demo.dryade.soap.DemoServicesSkeletonInterface;
import demo.dryade.soap.NotifyDocument;
import demo.dryade.soap.RequestDocument;
import demo.dryade.soap.RequestResponseDocument;
import demo.dryade.soap.RequestResponseDocument.RequestResponse;
import demo.dryade.types.ComplexType1;
import demo.dryade.types.SpecificType;
public class Server implements DemoServicesSkeletonInterface
{
/**
* Logger for this class
*/
private static final Logger logger = Logger.getLogger(Server.class);
public static boolean checkXmlSchema(XmlObject object)
{
if (object == null)
{
logger.warn(validation null object);
return false;
}
ArrayListXmlValidationError validationErrors = new
ArrayListXmlValidationError();
XmlOptions validationOptions = new XmlOptions();
validationOptions.setErrorListener(validationErrors);
boolean validation = object.validate(validationOptions);
if (!validation)
{
StringBuffer errorTxt = new StringBuffer( Invalid object
+object.getClass().getName());
for (XmlValidationError error : validationErrors)
{
errorTxt.append(\n );
errorTxt.append(error.toString());
}
logger.warn(errorTxt);
logger.warn(Invalid content = \n+object.toString());
}
else
{
logger.info( Valid object +object.getClass().getName());
}
return validation;
}
@Override
public RequestResponseDocument Request(RequestDocument request)
{
checkXmlSchema(request);
RequestResponseDocument response =
RequestResponseDocument.Factory.newInstance();
RequestResponse reqResponse = response.addNewRequestResponse();
ComplexType1 part = reqResponse.addNewResponsePart();
part.addElement1(12);
part.setElement2(test);
SpecificType elt3 = SpecificType.Factory.newInstance();
elt3.setElement4(true);
elt3.setElement5(any test);
part.setElement3(elt3);
checkXmlSchema(response);
return response;
}
@Override
public void Notify(NotifyDocument notify)
{
checkXmlSchema(notify);
}
}
Client Source :
package demo.client;
import java.math.BigInteger;
import java.util.ArrayList;
import org.apache.log4j.Logger;
import org.apache.xmlbeans.XmlObject;
import org.apache.xmlbeans.XmlOptions;
import org.apache.xmlbeans.XmlValidationError;
import demo.dryade.soap.DemoServices;
import demo.dryade.soap.DemoServicesStub;
import demo.dryade.soap.NotifyDocument;
import demo.dryade.soap.RequestDocument;
import demo.dryade.soap.RequestResponseDocument;
import demo.dryade.soap.NotifyDocument.Notify;
import demo.dryade.soap.RequestDocument.Request;
import demo.dryade.types.ComplexType1;
import demo.dryade.types.ComplexType2;
import demo.dryade.types.SpecificType;
/**
* @author michel
*
*/
public class Client
{
/**
* Logger for this class
*/
private static final Logger logger = Logger.getLogger(Client.class);
public static boolean checkXmlSchema(XmlObject object)
{
if (object == null)
{
logger.warn(validation null object);
return false;
}
ArrayListXmlValidationError validationErrors = new
Does Axis2-xmlbeans data binding support Unwrapping in Doc/Lit mode
We know that unwrapping works fine with adb but does anyone know if this is officially supported with xmlbeans. Thanks John
Xmlbeans unwrapped code generation
Currently unwrapped xml code generation fails to compile. I believe this is a known issue. Are there any news about when this is going to be fixed? Bosko
Using xmlbeans binding and axiom in same service
Hi A possible stupid question, but I need ask it, when making a service that can handle mtom. Can one generate the service from WSDL using any databinding(xmlbeans,adb) etc? Just as long as one enables it in the service.xml? and does the same stand for the client side generation of code? cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
Axis2: Mismatched xmlbeans class names
What causes this class name mismatch? In my jar file, I have the following class. schemaorg_apache_xmlbeans/system/sBBF8DB3578287A3861C364EA0385E717/TypeSystemHolder.class At runtime, I experience Unable to load: schemaorg_apache_xmlbeans.system.sBE617FEA02624726C1BF84F8C0A8EDDF.TypeSystemHolder This occurs when I try to run the Axis2SampleDocLitService client. Scott Vigil http://svis.com
RE: Axis2: Mismatched xmlbeans class names
Hi Scott, Did you generate the XMLbeans using scomp and graft it on to the Axis2 skel/stub generated with the -Ewdc option? If you did, Axis2 and XMLBeans munge the namespaces two different ways ensuring that the two systems are incompatible. If you just used WSDL2Java with -d xmlbeans, perhaps you should try using the overwrite flag (-or) as you perhaps have an old files hanging in your build target dir. Or perhaps you have multiple TypeSystemHolder elements in different namespaces? Martin -Original Message- From: sc...@svis.com [mailto:sc...@svis.com] Sent: Wednesday, March 18, 2009 1:02 PM To: axis-user@ws.apache.org Subject: Axis2: Mismatched xmlbeans class names What causes this class name mismatch? In my jar file, I have the following class. schemaorg_apache_xmlbeans/system/sBBF8DB3578287A3861C364EA0385E717/TypeS ystemHolder.class At runtime, I experience Unable to load: schemaorg_apache_xmlbeans.system.sBE617FEA02624726C1BF84F8C0A8EDDF.TypeS ystemHolder This occurs when I try to run the Axis2SampleDocLitService client. Scott Vigil http://svis.com
RE: XMLBeans-Axis2 - Type naming differences
Martin, The workaround is that you need to specify an .xsdconfig file. This lets you take control of how XMLBeans generates package names, rather then relying on the defaults. In addition, Axis2's wsdl2java also uses the .xsdconfig file. You can find the XML schema definitions for the .xsdconfig syntax in xmlconfig.xsd (this link http://svn.apache.org/viewvc/xmlbeans/trunk/src/configschema/schema/xml config.xsd?view=markup is to the web SVN version) You'd have an xsdconfig file something like this: !-- This file used by XMLBeans, to override some of the defaults -- xb:config xmlns:xb=http://xml.apache.org/xmlbeans/2004/02/xbean/config; xb:namespace uri=http://example.com/testService/2009/03; xb:packagecom.example.testService.x2009.x03/xb:package /xb:namespace /xb:config The above results in exactly the same XMLBeans-generated names as XMLBeans would generate without the file. The main reason to have this file is that you can tell wsdl2java to use these names: % wsdl2java.sh -d xmlbeans -xsdconfig example.xsdconfig ... Definitely feels like a bug in 'wsdl2java.sh -d xmlbeans', that Axis2 doesn't use the same conventions even though you say '-d xmlbeans'. -- Jeff From: martin.ba...@wellsfargo.com Sent: Wednesday, March 11, 2009 6:16 PM To: axis-user@ws.apache.org Subject: XMLBeans-Axis2 - Type naming differences Hello, I am using Axis2 1.4 and XMLBeans 2.4. I would like to use XMLBeans ant task to generate all the XMLBeans artifacts and use Axis2 to just generate the skels and stubs. This is because I have a mix of .wsdl's and .xsd's I need to generate and would like to normalize the resource files. What I've found is, though, that the Axis2 tasks and XMLBeans tasks name entities differently when a span in the entity path starts with a number. For example: Element namespace - com/example/testService/2009/03 Schema - com/example/testService/2009/03/myTestSchema XMLBeans generated element - com.example.testService.x2009.x03.myTestSchema Axis2 generated element - com.example.testService._2009._03.myTestSchema Note that XMLbeans prepends 'x' and Axis2 '_' to numeric paths. This difference changes the resource index mapping making it impossible to use the separately generated files. Can anyone tell me how to normalize the naming between Axis2 and XMLBeans? Thanks in advance, Martin CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.
RE: XMLBeans-Axis2 - Type naming differences
Thanks Jeff This is certainly one approach. However, there are many, many paths and they change, making this approach impracticable. I was hoping there's a switch, but I guess Axis2 is calling an XMLbeans jar directly and passing it's own prefixes via method calls. It would certainly help if XMLBeans and Axis used the same standards ;) I'll log a bug. Thanks Martin From: Jeff Martin [mailto:jmar...@telecomsys.com] Sent: Thursday, March 12, 2009 8:51 AM To: axis-user@ws.apache.org Subject: RE: XMLBeans-Axis2 - Type naming differences Martin, The workaround is that you need to specify an .xsdconfig file. This lets you take control of how XMLBeans generates package names, rather then relying on the defaults. In addition, Axis2's wsdl2java also uses the .xsdconfig file. You can find the XML schema definitions for the .xsdconfig syntax in xmlconfig.xsd (this link http://svn.apache.org/viewvc/xmlbeans/trunk/src/configschema/schema/xml config.xsd?view=markup is to the web SVN version) You'd have an xsdconfig file something like this: !-- This file used by XMLBeans, to override some of the defaults -- xb:config xmlns:xb=http://xml.apache.org/xmlbeans/2004/02/xbean/config; xb:namespace uri=http://example.com/testService/2009/03; xb:packagecom.example.testService.x2009.x03/xb:package /xb:namespace /xb:config The above results in exactly the same XMLBeans-generated names as XMLBeans would generate without the file. The main reason to have this file is that you can tell wsdl2java to use these names: % wsdl2java.sh -d xmlbeans -xsdconfig example.xsdconfig ... Definitely feels like a bug in 'wsdl2java.sh -d xmlbeans', that Axis2 doesn't use the same conventions even though you say '-d xmlbeans'. -- Jeff _ From: martin.ba...@wellsfargo.com Sent: Wednesday, March 11, 2009 6:16 PM To: axis-user@ws.apache.org Subject: XMLBeans-Axis2 - Type naming differences Hello, I am using Axis2 1.4 and XMLBeans 2.4. I would like to use XMLBeans ant task to generate all the XMLBeans artifacts and use Axis2 to just generate the skels and stubs. This is because I have a mix of .wsdl's and .xsd's I need to generate and would like to normalize the resource files. What I've found is, though, that the Axis2 tasks and XMLBeans tasks name entities differently when a span in the entity path starts with a number. For example: Element namespace - com/example/testService/2009/03 Schema - com/example/testService/2009/03/myTestSchema XMLBeans generated element - com.example.testService.x2009.x03.myTestSchema Axis2 generated element - com.example.testService._2009._03.myTestSchema Note that XMLbeans prepends 'x' and Axis2 '_' to numeric paths. This difference changes the resource index mapping making it impossible to use the separately generated files. Can anyone tell me how to normalize the naming between Axis2 and XMLBeans? Thanks in advance, Martin CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.
XMLBeans-Axis2 - Type naming differences
Hello, I am using Axis2 1.4 and XMLBeans 2.4. I would like to use XMLBeans ant task to generate all the XMLBeans artifacts and use Axis2 to just generate the skels and stubs. This is because I have a mix of .wsdl's and .xsd's I need to generate and would like to normalize the resource files. What I've found is, though, that the Axis2 tasks and XMLBeans tasks name entities differently when a span in the entity path starts with a number. For example: Element namespace - com/example/testService/2009/03 Schema - com/example/testService/2009/03/myTestSchema XMLBeans generated element - com.example.testService.x2009.x03.myTestSchema Axis2 generated element - com.example.testService._2009._03.myTestSchema Note that XMLbeans prepends 'x' and Axis2 '_' to numeric paths. This difference changes the resource index mapping making it impossible to use the separately generated files. Can anyone tell me how to normalize the naming between Axis2 and XMLBeans? Thanks in advance, Martin
Re: Failed when creating xmlbeans binding from WS-Trust.wsdl
Hi any hints on how to solve this, below is the wsdl that I'm trying to generate the xmlbeans binding, tried with both axis2 1.3 and 1.4, here is. ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=http://no.plab/hakont/sts; xmlns:tns=http://no.plab/hakont/sts; xmlns:wst= http://schemas.xmlsoap.org/ws/2005/02/trust; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:xs= http://www.w3.org/2001/XMLSchema; name=EsysbioStSService xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; !-- this is the WS-I BP-compliant way to import a schema -- wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xs:import namespace= http://schemas.xmlsoap.org/ws/2005/02/trust; schemaLocation=ws-trust.xsd / /xs:schema /wsdl:types !-- WS-Trust defines the following GEDs -- wsdl:message name=RequestSecurityTokenMsg wsdl:part name=request element=wst:RequestedSecurityToken / /wsdl:message wsdl:message name=RequestSecurityTokenResponseMsg wsdl:part name=response element=wst:RequestSecurityTokenResponse / /wsdl:message wsdl:message name=RequestSecurityTokenResponseCollectionMsg wsdl:part name=responseCollection element=wst:RequestSecurityTokenResponseCollection / /wsdl:message !-- This portType models the full request/response the Security Token Service: -- wsdl:portType name=WSSecurityRequestor wsdl:operation name=SecurityTokenResponse wsdl:input message=tns:RequestSecurityTokenResponseMsg / /wsdl:operation wsdl:operation name=SecurityTokenResponse2 wsdl:input message=tns:RequestSecurityTokenResponseCollectionMsg / /wsdl:operation wsdl:operation name=Challenge wsdl:input message=tns:RequestSecurityTokenResponseMsg / wsdl:output message=tns:RequestSecurityTokenResponseMsg / /wsdl:operation wsdl:operation name=Challenge2 wsdl:input message=tns:RequestSecurityTokenResponseMsg / wsdl:output message=tns:RequestSecurityTokenResponseCollectionMsg / /wsdl:operation /wsdl:portType !-- These portTypes model the individual message exchanges -- wsdl:portType name=SecurityTokenRequestService wsdl:operation name=RequestSecurityToken wsdl:input message=tns:RequestSecurityTokenMsg / /wsdl:operation /wsdl:portType wsdl:portType name=SecurityTokenService wsdl:operation name=RequestSecurityToken wsdl:input message=tns:RequestSecurityTokenMsg / wsdl:output message=tns:RequestSecurityTokenResponseMsg/ /wsdl:operation /wsdl:portType wsdl:binding name=STSBinding type=tns:SecurityTokenService soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=RequestSecurityToken soap:operation soapAction= http://schemas.xmlsoap.org/ws/2005/02/trust/wsdl/RequestSecurityToken; / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=EsysbioStSService wsdl:port name=EsysbioSTS binding=tns:STSBinding soap:address location=http://localhost:8080/axis2/services/STS; / /wsdl:port /wsdl:service /wsdl:definitions 2009/1/26 Håkon Sagehaug hakon.sageh...@bccs.uib.no -- Forwarded message -- From: Håkon Sagehaug hakon.sageh...@bccs.uib.no Date: 2009/1/26 Subject: Failed when creating xmlbeans binding from WS-Trust.wsdl To: axis-user@ws.apache.org Sent it to the wrong list -- Forwarded message -- From: Håkon Sagehaug hakon.sageh...@bccs.uib.no Date: 2009/1/26 Subject: Failed when creating xmlbeans binding from WS-Trust.wsdl To: axis-...@ws.apache.org Hi I wanted to make a STS service and copied the WS-Trust.wsdl from the ws-trust specification and added binding and service description, but when I want to create an xmlbeans binding I get this error Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: http://schemas.xmlsoap.org/ws/2004/08/addressing/:61:1: error: cvc-enumeration-valid: string value 'none' is not a valid enumeration value for type of processContents attribute in xs:wildcard I use this command wsdl2java.sh -uri wsdl/WS-Trust.wsdl -ss -d xmlbeans -sd -p no.plab.hakont.sts -s and running axis2 1.4.1 Any hits on this, since I 've not done anything else then adding a binding and service to the wsdl I dont get what's wrong in this case. I can compile the schema on it's own using xmlbeans, but not when I want to create ws stub classes using the xmlbeans binding. cheers, Håkon -- Håkon Sagehaug, Software Developer Parallab, Bergen Center for Computational
Re: Failed when creating xmlbeans binding from WS-Trust.wsdl
hi I just had to change the schema to http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3.xsd from before i had http://schemas.xmlsoap.org/ws/2005/02/trust/ws-trust.xsd 2009/1/27 Håkon Sagehaug hakon.sageh...@bccs.uib.no Hi any hints on how to solve this, below is the wsdl that I'm trying to generate the xmlbeans binding, tried with both axis2 1.3 and 1.4, here is. ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=http://no.plab/hakont/sts; xmlns:tns=http://no.plab/hakont/sts; xmlns:wst= http://schemas.xmlsoap.org/ws/2005/02/trust; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:xs= http://www.w3.org/2001/XMLSchema; name=EsysbioStSService xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; !-- this is the WS-I BP-compliant way to import a schema -- wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xs:import namespace= http://schemas.xmlsoap.org/ws/2005/02/trust; schemaLocation=ws-trust.xsd / /xs:schema /wsdl:types !-- WS-Trust defines the following GEDs -- wsdl:message name=RequestSecurityTokenMsg wsdl:part name=request element=wst:RequestedSecurityToken / /wsdl:message wsdl:message name=RequestSecurityTokenResponseMsg wsdl:part name=response element=wst:RequestSecurityTokenResponse / /wsdl:message wsdl:message name=RequestSecurityTokenResponseCollectionMsg wsdl:part name=responseCollection element=wst:RequestSecurityTokenResponseCollection / /wsdl:message !-- This portType models the full request/response the Security Token Service: -- wsdl:portType name=WSSecurityRequestor wsdl:operation name=SecurityTokenResponse wsdl:input message=tns:RequestSecurityTokenResponseMsg / /wsdl:operation wsdl:operation name=SecurityTokenResponse2 wsdl:input message=tns:RequestSecurityTokenResponseCollectionMsg / /wsdl:operation wsdl:operation name=Challenge wsdl:input message=tns:RequestSecurityTokenResponseMsg / wsdl:output message=tns:RequestSecurityTokenResponseMsg / /wsdl:operation wsdl:operation name=Challenge2 wsdl:input message=tns:RequestSecurityTokenResponseMsg / wsdl:output message=tns:RequestSecurityTokenResponseCollectionMsg / /wsdl:operation /wsdl:portType !-- These portTypes model the individual message exchanges -- wsdl:portType name=SecurityTokenRequestService wsdl:operation name=RequestSecurityToken wsdl:input message=tns:RequestSecurityTokenMsg / /wsdl:operation /wsdl:portType wsdl:portType name=SecurityTokenService wsdl:operation name=RequestSecurityToken wsdl:input message=tns:RequestSecurityTokenMsg / wsdl:output message=tns:RequestSecurityTokenResponseMsg/ /wsdl:operation /wsdl:portType wsdl:binding name=STSBinding type=tns:SecurityTokenService soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=RequestSecurityToken soap:operation soapAction= http://schemas.xmlsoap.org/ws/2005/02/trust/wsdl/RequestSecurityToken; / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=EsysbioStSService wsdl:port name=EsysbioSTS binding=tns:STSBinding soap:address location= http://localhost:8080/axis2/services/STS; / /wsdl:port /wsdl:service /wsdl:definitions 2009/1/26 Håkon Sagehaug hakon.sageh...@bccs.uib.no -- Forwarded message -- From: Håkon Sagehaug hakon.sageh...@bccs.uib.no Date: 2009/1/26 Subject: Failed when creating xmlbeans binding from WS-Trust.wsdl To: axis-user@ws.apache.org Sent it to the wrong list -- Forwarded message -- From: Håkon Sagehaug hakon.sageh...@bccs.uib.no Date: 2009/1/26 Subject: Failed when creating xmlbeans binding from WS-Trust.wsdl To: axis-...@ws.apache.org Hi I wanted to make a STS service and copied the WS-Trust.wsdl from the ws-trust specification and added binding and service description, but when I want to create an xmlbeans binding I get this error Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: http://schemas.xmlsoap.org/ws/2004/08/addressing/:61:1: error: cvc-enumeration-valid: string value 'none' is not a valid enumeration value for type of processContents attribute in xs:wildcard I use this command wsdl2java.sh -uri wsdl/WS-Trust.wsdl -ss -d xmlbeans -sd -p no.plab.hakont.sts -s and running axis2 1.4.1 Any hits on this, since I 've not done
Fwd: Failed when creating xmlbeans binding from WS-Trust.wsdl
-- Forwarded message -- From: Håkon Sagehaug hakon.sageh...@bccs.uib.no Date: 2009/1/26 Subject: Failed when creating xmlbeans binding from WS-Trust.wsdl To: axis-user@ws.apache.org Sent it to the wrong list -- Forwarded message -- From: Håkon Sagehaug hakon.sageh...@bccs.uib.no Date: 2009/1/26 Subject: Failed when creating xmlbeans binding from WS-Trust.wsdl To: axis-...@ws.apache.org Hi I wanted to make a STS service and copied the WS-Trust.wsdl from the ws-trust specification and added binding and service description, but when I want to create an xmlbeans binding I get this error Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: http://schemas.xmlsoap.org/ws/2004/08/addressing/:61:1: error: cvc-enumeration-valid: string value 'none' is not a valid enumeration value for type of processContents attribute in xs:wildcard I use this command wsdl2java.sh -uri wsdl/WS-Trust.wsdl -ss -d xmlbeans -sd -p no.plab.hakont.sts -s and running axis2 1.4.1 Any hits on this, since I 've not done anything else then adding a binding and service to the wsdl I dont get what's wrong in this case. I can compile the schema on it's own using xmlbeans, but not when I want to create ws stub classes using the xmlbeans binding. cheers, Håkon -- Håkon Sagehaug, Software Developer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) -- Håkon Sagehaug, Software Developer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) -- Håkon Sagehaug, Software Developer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
code generated with xmlbeans cannot be compiled
I am using the latest CodeGenerationUtility from SVN trunk because the current CodeGenerationUtility from axis2-xmlbeans-1.4.1 has a bug and produce Unexpected end of file after null However, the code generated references to functions which are not generated: 1. toEnvelope 2. toOM 3. fromOM What am I missing?
XMLBeans deserialisation classpath issues with inherited types
Hi, currently I am confronted with some wired XMLBeans classpath issue during deserialisation of inherited types. First of all the setup: - Axis2-141, Tomcat 6, XMLBeans 2.3.0 - the web service is deployed as an aar containing a lib folder where all service related libraries are situated (especially the generated xbeans) - the axis2/WEB-INF/lib folder contains just the default jars - all the xbeans were generated separately by scomp and are located in a single jar - the service was generated using the -Ewdc switch and the dummy schemas are not included in the generated service jar (the jar actually only contains the Stub, the MessageReceivers, the Skeleton and several Faults (declared in the WSDL file)) So far so good. No problem at all, everything runs fine, except: In our type xsds we have some inheritance (snippet): [...] element name=UsernameIdentity type=ia_types:UsernameIdentityType substitutionGroup=ia_types:AttributedIdentity/ complexType name=UsernameIdentityType complexContent extension base=ia_types:AttributedIdentityType sequence element name=username type=string/ /sequence /extension /complexContent /complexType complexType name=UsernameIdentityPropertyType sequence minOccurs=0 element ref=ia_types:UsernameIdentity/ /sequence /complexType element name=GroupIdentity type=ia_types:GroupIdentityType substitutionGroup=ia_types:AttributedIdentity/ complexType name=GroupIdentityType complexContent extension base=ia_types:AttributedIdentityType sequence element name=groupname type=string/ /sequence /extension /complexContent /complexType complexType name=GroupIdentityPropertyType sequence minOccurs=0 element ref=ia_types:GroupIdentity/ /sequence /complexType element name=AttributedIdentity type=ia_types:AttributedIdentityType substitutionGroup=ia_types:Identity/ complexType name=AttributedIdentityType complexContent extension base=ia_types:IdentityType sequence element name=attributes type=ia_types:IdentityAttributesType/ element name=identities complexType sequence element ref=ia_types:AttributedIdentity minOccurs=0 maxOccurs=unbounded/ /sequence /complexType /element /sequence /extension /complexContent /complexType element name=Identity type=ia_types:IdentityType/ complexType name=IdentityType sequence element name=id type=integer/ element name=origin type=string/ element name=refProfile type=pms_types:ProfilePropertyType minOccurs=0/ element name=active type=boolean/ /sequence /complexType complexType name=IdentityPropertyType sequence minOccurs=0 element ref=ia_types:Identity/ /sequence /complexType [...] Now the service offers a request to create a new identity: element name=createIdentityRequest type=ia_requests:createIdentityRequest/ complexType name=createIdentityRequest sequence element name=identity type=ia_types:IdentityType/ /sequence /complexType If I send the following request: ns:createIdentityRequest xmlns:ns=http://www.enviromatics.net/WS/IdentityManagementAndAuthenticationService/requests/2.0 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; ns1:identity xmlns:ns1=http://www.enviromatics.net/WS/IdentityManagementAndAuthenticationService/requests/2.0 xmlns:ns=http://www.enviromatics.net/WS/IdentityManagementAndAuthenticationService/types/2.0 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://www.enviromatics.net/WS/IdentityManagementAndAuthenticationService/requests/2.0 xsi:type=ns:GroupIdentityType ns:id xsi:nil=true/ ns:originhttp://127.0.0.1:8091/axis214/services/IdentityManagementAndAuthenticationService /ns:origin ns:refProfile/ ns:activefalse/ns:active ns:attributes xsi:type=ns:KeyVectorIdentityAttributesType/ ns:identities/ ns:groupnametestGroup/ns:groupname /ns1:identity /ns:createIdentityRequest which actually represents an instance of GroupIdentityType (see xsi:type=ns:GroupIdentityType) but XMLBeans parameter does not create an instance of GroupIdentityType(Impl) but of IdentityType(Impl) which cannot be cast (obviously). The funny thing about this is that if I place the xbeans jar in the axis2/WEB-INF/lib folder
XMLBeans
Hi all When I run WSDL2Java using XMLBeans as databinding,It generates lot of schema binary files. When we build the entire xsb files and deploy it,It takes 80 minutes. Can any one suggest a way to reduce this somehow. Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
Re: Axis2-1.4.1 and Xmlbeans 2.4.0
On Tue, Nov 11, 2008 at 7:50 PM, David Ojeda [EMAIL PROTECTED] wrote: Hello, I've noticed that xmlbeans has released a new version 2.4.0. Does anyone have any ideas/experience using axis2-1.4.1 and that version of xmlbeans instead of 2.3.0 ? The changelog is available at http://svn.apache.org/viewvc/xmlbeans/trunk/CHANGES.txt?revision=666108view=markup I would specifically use xmlbeans 2.4.0 for code generation, could this be a problem since axis2 uses 2.3.0? I don't think so. try replacing the xmlbeans jar with the new one. thanks, Amila. Thank you -- David Ojeda - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Axis2-1.4.1 and Xmlbeans 2.4.0
Hello, I've noticed that xmlbeans has released a new version 2.4.0. Does anyone have any ideas/experience using axis2-1.4.1 and that version of xmlbeans instead of 2.3.0 ? The changelog is available at http://svn.apache.org/viewvc/xmlbeans/trunk/CHANGES.txt?revision=666108view=markup I would specifically use xmlbeans 2.4.0 for code generation, could this be a problem since axis2 uses 2.3.0? Thank you -- David Ojeda - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XMLBeans customization parameters in Maven
Can you be more specific? From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2008 7:31 AM To: axis-user@ws.apache.org Subject: Re: XMLBeans customization parameters in Maven you can use xc (ie. -Exc) option to specify the xmlbeans config file with wsdl2java command line tool. check whether you can set an option like that. thanks, Amila. On Thu, Oct 30, 2008 at 10:49 PM, [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hello, Anybody knows how to provide external XMLBeans configuration file as a parameter in axis2-wsdl2code-maven-plugin ? Plug-in has namespaceURIs, however it's doesn't allow external customization file. Regards, Benjamin. - To unsubscribe, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: XMLBeans customization parameters in Maven
you can use xc (ie. -Exc) option to specify the xmlbeans config file with wsdl2java command line tool. check whether you can set an option like that. thanks, Amila. On Thu, Oct 30, 2008 at 10:49 PM, [EMAIL PROTECTED] wrote: Hello, Anybody knows how to provide external XMLBeans configuration file as a parameter in axis2-wsdl2code-maven-plugin ? Plug-in has namespaceURIs, however it's doesn't allow external customization file. Regards, Benjamin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
XMLBeans customization parameters in Maven
Hello, Anybody knows how to provide external XMLBeans configuration file as a parameter in axis2-wsdl2code-maven-plugin ? Plug-in has namespaceURIs, however it's doesn't allow external customization file. Regards, Benjamin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2.1.4 MTOM w/ XmlBeans
Hi, I see that Axis2.1.1 had documentation that supported MTOM with XmlBeans ( http://ws.apache.org/axis2/1_1/mtom-guide.html#252). Axis 2.1.4 no longers has this documentation. Is MTOM supported with 2.1.4 and XmlBeans? I am curious since it seems that schema containing binary data works with XmlBeans as expected. The only difference is that the byte array is made available and not a data handler. It was broken and nobody was able/interested in fixing it. Also I cannot recall the exact error, may be you can find it in the JIRA. To be honest I'm not a big fan of using XMLBeans for MTOM mainly due to the following inefficiency in XMLBeans when it comes to binary data handling.. XMLBeans does not support binary, but Axiom supports. So when using XMLBeans the binary data gets converted to base64 encoded string inside XMLBeans and then back to binary when writing the message. ADB seems to have a file caching mechanism described here ( http://ws.apache.org/axis2/1_3/mtom-guide.html#41). Is this specific to ADB? Or can this mechanism somehow be applied to XmlBeans? I'd like to not have the entire document loaded into memory and would like to stream to to disk if over a certain size using XmlBeans as the data binding library. File caching is generic to Axis2.. It does not depend on the data binding as it happens in a much deeper layer. But I feel that even when file caching is there, XMLBeans might try to load the content of the attachment in to the memory. thanks, Thilina Thanks, Alejandro - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://thilinag.blogspot.com
Axis2.1.4 MTOM w/ XmlBeans
Hi, I see that Axis2.1.1 had documentation that supported MTOM with XmlBeans (http://ws.apache.org/axis2/1_1/mtom-guide.html#252). Axis 2.1.4 no longers has this documentation. Is MTOM supported with 2.1.4 and XmlBeans? I am curious since it seems that schema containing binary data works with XmlBeans as expected. The only difference is that the byte array is made available and not a data handler. ADB seems to have a file caching mechanism described here (http://ws.apache.org/axis2/1_3/mtom-guide.html#41). Is this specific to ADB? Or can this mechanism somehow be applied to XmlBeans? I'd like to not have the entire document loaded into memory and would like to stream to to disk if over a certain size using XmlBeans as the data binding library. Thanks, Alejandro - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
xmlbeans in Axis (not Axis2) using Eclipse IDE
Hello everyone, I'd like to know if someone of you knows how to modify the wizard used in Ecipse to create Web Services Skeleton to use a xmlbeans data binding. Alternatively, it could help to know what an how needs to be changed in a project generated by that wizard in order to use xmlbeans in the web service. -- View this message in context: http://www.nabble.com/xmlbeans-in-Axis-%28not-Axis2%29-using-Eclipse-IDE-tp19978820p19978820.html 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: Error when generating the proxies using xmlbeans
In able to continue my work I tried -Ewdc (for xmlbeans) options of wsdl2java, and I could generate the files using xmlbens scomp. Now which files should I replace ? Thanks -- -Ewdc (for xmlbeans) Generate code with a dummy schema. if someone use this option they have to generate the xmlbeans code seperately with the scomp command comes with the xmlbeans distribution and replace the Axis2 generated classes with correct classes From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:01 PM To: axis-user@ws.apache.org Subject: Error when generating the proxies using xmlbeans Hi, I have a WSDL file which imports other WSDL files and they import XSD files. Looks like one of the XSD is being referred multiple times. I guess normally this shouldn't be an issue but when I use the xmlbeans binding I am getting an error saying that I have Duplicate global type . When I use the default binding ADB I don't get an error message but I can't use ADB because of its limitations for inherited complex types. I am using axis2 1.4.1 . Do you have any suggestions to work around the issue? Thanks Using JAVA_HOME:d:\jdev\10g10134\jdk Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. [INFO] A SOAP port was not found - picking a random port! [INFO] Resolving schema with publicId [http://schemas.zzz.com/OpenActivity/1/0/Reservation/] and systemId [XReservationService.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException
Re: Error when generating the proxies using xmlbeans
In my experience, I have to delete everything except the skeleton, message
receiver, and fault classes if any.
I do this with an ant task, so maybe this will help:
java classname=org.apache.axis2.wsdl.WSDL2Java
failonerror=true
fork=true
classpath refid=axis2.classpath/
classpath location=etc/axis2log4j/
arg value=-d/
arg value=xmlbeans/
arg value=-g/
arg value=-ss/
arg value=-Ewdc/
arg value=-xsdconfig/
arg file=xsd/NStoPkg.xsdconfig/
arg value=-sd/
arg value=-o/
arg file=output/${ws.name}/
arg value=--noBuildXML/
arg value=-uri/
arg file=wsdl/${ws.name}.wsdl/
/java
delete includeemptydirs=true
fileset dir=output/${ws.name}/src
include name=**/*/
exclude name=**/.svn/**/
exclude name=**/*Skeleton.java/
exclude name=**/*MessageReceiverInOut.java/
exclude name=**/*Fault.java/
/fileset
/delete
Note that all my fault classes are named *Fault, so their classes are not
deleted.
On Wednesday 01 October 2008 08:32:29 Soyer, Muhammed A. wrote:
In able to continue my work I tried -Ewdc (for xmlbeans) options of
wsdl2java, and I could generate the files using xmlbens scomp. Now which
files should I replace ?
Thanks
--
-Ewdc (for xmlbeans) Generate code with a dummy schema. if someone use
this option they have to generate the xmlbeans code seperately with the
scomp command comes with the xmlbeans distribution and replace the Axis2
generated classes with correct classes
From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:01 PM
To: axis-user@ws.apache.org
Subject: Error when generating the proxies using xmlbeans
Hi,
I have a WSDL file which imports other WSDL files and they import XSD
files. Looks like one of the XSD is being referred multiple times. I guess
normally this shouldn't be an issue but when I use the xmlbeans binding I
am getting an error saying that I have Duplicate global type . When I
use the default binding ADB I don't get an error message but I can't use
ADB because of its limitations for inherited complex types.
I am using axis2 1.4.1 . Do you have any suggestions to work around the
issue?
Thanks
Using JAVA_HOME:d:\jdev\10g10134\jdk
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document
at 'XClassService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XClassService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at
'XSpaService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XSpaService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at
'XCustomer.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at
'XLocation.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XLocationObjects.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at
'XTee.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at
'XDiningService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XDiningService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. Retrieving document at
'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document
at 'XClassService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XClassService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd
RE: Error when generating the proxies using xmlbeans
Hi David,
Thanks for your reply. It says that it will generate a dummy schema but when
I look at the generated files they look legitimate, which files should be dummy?
Thanks
-Original Message-
From: David Ojeda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 10:08 AM
To: axis-user@ws.apache.org
Subject: Re: Error when generating the proxies using xmlbeans
In my experience, I have to delete everything except the skeleton, message
receiver, and fault classes if any.
I do this with an ant task, so maybe this will help:
java classname=org.apache.axis2.wsdl.WSDL2Java
failonerror=true
fork=true
classpath refid=axis2.classpath/
classpath location=etc/axis2log4j/
arg value=-d/
arg value=xmlbeans/
arg value=-g/
arg value=-ss/
arg value=-Ewdc/
arg value=-xsdconfig/
arg file=xsd/NStoPkg.xsdconfig/
arg value=-sd/
arg value=-o/
arg file=output/${ws.name}/
arg value=--noBuildXML/
arg value=-uri/
arg file=wsdl/${ws.name}.wsdl/
/java
delete includeemptydirs=true
fileset dir=output/${ws.name}/src
include name=**/*/
exclude name=**/.svn/**/
exclude name=**/*Skeleton.java/
exclude name=**/*MessageReceiverInOut.java/
exclude name=**/*Fault.java/
/fileset
/delete
Note that all my fault classes are named *Fault, so their classes are not
deleted.
On Wednesday 01 October 2008 08:32:29 Soyer, Muhammed A. wrote:
In able to continue my work I tried -Ewdc (for xmlbeans) options of
wsdl2java, and I could generate the files using xmlbens scomp. Now which
files should I replace ?
Thanks
--
-Ewdc (for xmlbeans) Generate code with a dummy schema. if someone use
this option they have to generate the xmlbeans code seperately with the
scomp command comes with the xmlbeans distribution and replace the Axis2
generated classes with correct classes
From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:01 PM
To: axis-user@ws.apache.org
Subject: Error when generating the proxies using xmlbeans
Hi,
I have a WSDL file which imports other WSDL files and they import XSD
files. Looks like one of the XSD is being referred multiple times. I guess
normally this shouldn't be an issue but when I use the xmlbeans binding I
am getting an error saying that I have Duplicate global type . When I
use the default binding ADB I don't get an error message but I can't use
ADB because of its limitations for inherited complex types.
I am using axis2 1.4.1 . Do you have any suggestions to work around the
issue?
Thanks
Using JAVA_HOME:d:\jdev\10g10134\jdk
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document
at 'XClassService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XClassService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at
'XSpaService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XSpaService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at
'XCustomer.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at
'XLocation.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XLocationObjects.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at
'XTee.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at
'XDiningService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XDiningService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. Retrieving document at
'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2
Re: Error when generating the proxies using xmlbeans
Hello Muhammed,
I am not sure about this. When I faced this problem I wasn't sure which files
should be deleted. I didn't find any docs about this but this -Ewdc was
crucial for my project (generation time was 5min without it and 10seconds with
it).
The main problem was that there were duplicate classes in the jar generated by
scomp and the classes generated by wsdl2java.
What I did was erase everything but the ones I wrote in my last message[*]
Then I encountered more problems since I now needed the soap, wsdl and xml xsd
classes (Apparently the dummy classes of these xsd were generated by
wsdl2java... but I did not have the implementation classes). So my solution
was generating these classes with scomp as well. I am enclosing these xsd in
case you need them.
Hope it helps, but sorry I do not know the answer to your question
[*] I forgot that I must delete also schemaorg_apache_xmlbeans/**
On Wednesday 01 October 2008 10:16:31 Soyer, Muhammed A. wrote:
Hi David,
Thanks for your reply. It says that it will generate a dummy schema but
when I look at the generated files they look legitimate, which files should
be dummy?
Thanks
-Original Message-
From: David Ojeda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 10:08 AM
To: axis-user@ws.apache.org
Subject: Re: Error when generating the proxies using xmlbeans
In my experience, I have to delete everything except the skeleton, message
receiver, and fault classes if any.
I do this with an ant task, so maybe this will help:
java classname=org.apache.axis2.wsdl.WSDL2Java
failonerror=true
fork=true
classpath refid=axis2.classpath/
classpath location=etc/axis2log4j/
arg value=-d/
arg value=xmlbeans/
arg value=-g/
arg value=-ss/
arg value=-Ewdc/
arg value=-xsdconfig/
arg file=xsd/NStoPkg.xsdconfig/
arg value=-sd/
arg value=-o/
arg file=output/${ws.name}/
arg value=--noBuildXML/
arg value=-uri/
arg file=wsdl/${ws.name}.wsdl/
/java
delete includeemptydirs=true
fileset dir=output/${ws.name}/src
include name=**/*/
exclude name=**/.svn/**/
exclude name=**/*Skeleton.java/
exclude name=**/*MessageReceiverInOut.java/
exclude name=**/*Fault.java/
/fileset
/delete
Note that all my fault classes are named *Fault, so their classes are not
deleted.
On Wednesday 01 October 2008 08:32:29 Soyer, Muhammed A. wrote:
In able to continue my work I tried -Ewdc (for xmlbeans) options of
wsdl2java, and I could generate the files using xmlbens scomp. Now which
files should I replace ?
Thanks
--
-Ewdc (for xmlbeans) Generate code with a dummy schema. if someone use
this option they have to generate the xmlbeans code seperately with the
scomp command comes with the xmlbeans distribution and replace the Axis2
generated classes with correct classes
From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:01 PM
To: axis-user@ws.apache.org
Subject: Error when generating the proxies using xmlbeans
Hi,
I have a WSDL file which imports other WSDL files and they import XSD
files. Looks like one of the XSD is being referred multiple times. I
guess normally this shouldn't be an issue but when I use the xmlbeans
binding I am getting an error saying that I have Duplicate global type
. When I use the default binding ADB I don't get an error message
but I can't use ADB because of its limitations for inherited complex
types.
I am using axis2 1.4.1 . Do you have any suggestions to work around the
issue?
Thanks
Using JAVA_HOME:d:\jdev\10g10134\jdk
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document
at 'XClassService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XClassService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at
'XSpaService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XSpaService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2
RE: Error when generating the proxies using xmlbeans
Thanks for your help, I found another workaround for my case, I commented the
repeating imports and I could generate proxy classes then..
Thanks
-Original Message-
From: David Ojeda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 11:02 AM
To: axis-user@ws.apache.org
Subject: Re: Error when generating the proxies using xmlbeans
Hello Muhammed,
I am not sure about this. When I faced this problem I wasn't sure which files
should be deleted. I didn't find any docs about this but this -Ewdc was crucial
for my project (generation time was 5min without it and 10seconds with it).
The main problem was that there were duplicate classes in the jar generated by
scomp and the classes generated by wsdl2java.
What I did was erase everything but the ones I wrote in my last message[*]
Then I encountered more problems since I now needed the soap, wsdl and xml xsd
classes (Apparently the dummy classes of these xsd were generated by
wsdl2java... but I did not have the implementation classes). So my solution was
generating these classes with scomp as well. I am enclosing these xsd in case
you need them.
Hope it helps, but sorry I do not know the answer to your question
[*] I forgot that I must delete also schemaorg_apache_xmlbeans/**
On Wednesday 01 October 2008 10:16:31 Soyer, Muhammed A. wrote:
Hi David,
Thanks for your reply. It says that it will generate a dummy schema
but when I look at the generated files they look legitimate, which
files should be dummy?
Thanks
-Original Message-
From: David Ojeda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 10:08 AM
To: axis-user@ws.apache.org
Subject: Re: Error when generating the proxies using xmlbeans
In my experience, I have to delete everything except the skeleton,
message receiver, and fault classes if any.
I do this with an ant task, so maybe this will help:
java classname=org.apache.axis2.wsdl.WSDL2Java
failonerror=true
fork=true
classpath refid=axis2.classpath/
classpath location=etc/axis2log4j/
arg value=-d/
arg value=xmlbeans/
arg value=-g/
arg value=-ss/
arg value=-Ewdc/
arg value=-xsdconfig/
arg file=xsd/NStoPkg.xsdconfig/
arg value=-sd/
arg value=-o/
arg file=output/${ws.name}/
arg value=--noBuildXML/
arg value=-uri/
arg file=wsdl/${ws.name}.wsdl/
/java
delete includeemptydirs=true
fileset dir=output/${ws.name}/src
include name=**/*/
exclude name=**/.svn/**/
exclude name=**/*Skeleton.java/
exclude name=**/*MessageReceiverInOut.java/
exclude name=**/*Fault.java/
/fileset
/delete
Note that all my fault classes are named *Fault, so their classes are
not deleted.
On Wednesday 01 October 2008 08:32:29 Soyer, Muhammed A. wrote:
In able to continue my work I tried -Ewdc (for xmlbeans) options
of wsdl2java, and I could generate the files using xmlbens scomp.
Now which files should I replace ?
Thanks
--
-Ewdc (for xmlbeans) Generate code with a dummy schema. if someone
use this option they have to generate the xmlbeans code seperately
with the scomp command comes with the xmlbeans distribution and
replace the Axis2 generated classes with correct classes
From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:01 PM
To: axis-user@ws.apache.org
Subject: Error when generating the proxies using xmlbeans
Hi,
I have a WSDL file which imports other WSDL files and they import
XSD files. Looks like one of the XSD is being referred multiple
times. I guess normally this shouldn't be an issue but when I use
the xmlbeans binding I am getting an error saying that I have
Duplicate global type . When I use the default binding ADB I
don't get an error message but I can't use ADB because of its
limitations for inherited complex types.
I am using axis2 1.4.1 . Do you have any suggestions to work
around the issue?
Thanks
Using JAVA_HOME:d:\jdev\10g10134\jdk
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving
schema wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving
document at 'XClassService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving
schema wsdl:imported from 'XClassService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D
Error when generating the proxies using xmlbeans
Hi, I have a WSDL file which imports other WSDL files and they import XSD files. Looks like one of the XSD is being referred multiple times. I guess normally this shouldn't be an issue but when I use the xmlbeans binding I am getting an error saying that I have Duplicate global type . When I use the default binding ADB I don't get an error message but I can't use ADB because of its limitations for inherited complex types. I am using axis2 1.4.1 . Do you have any suggestions to work around the issue? Thanks Using JAVA_HOME:d:\jdev\10g10134\jdk Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. [INFO] A SOAP port was not found - picking a random port! [INFO] Resolving schema with publicId [http://schemas.zzz.com/OpenActivity/1/0/Reservation/] and systemId [XReservationService.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused
Problem with generating the proxy classes using xmlbeans
Hi, I can generate the proxy classes by using the default binding but I need to use xmlbeans because of the limitations of ADB. When I try xmlbeans it is erroring out in some enumeration definitions. Is my WSDL file incorrect or do we have a problem with xmlbeans? I am sending a simplified WSDL file having the same issue. Here is the error I am getting D:\oad:\jdev\axis2-1.4.1\\bin\wsdl2java --noBuildXML -or -p com.zz -uri msoyer.wsdl -d xmlbeans d:\jdev\10g10134\jdk java version 1.4.2_08 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode) Using AXIS2_HOME: D:\jdev\axis2-1.4.1 Using JAVA_HOME:d:\jdev\10g10134\jdk Retrieving document at 'msoyer.wsdl'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:115) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: cvc-datatype-valid.1.1: string value '119' does not match pattern for xs:ID at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:325) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: cvc-datatype-valid.1.1: string value '119' does not match pattern for xs:ID at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:189) ... 8 more msoyer.wsdl Description: msoyer.wsdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03
try to put all the jar files under the lib folder of the service archive (.aar file) to WEB-INF/lib folder. thanks, Amila. On Wed, Sep 17, 2008 at 9:58 AM, Soyer, Muhammed A. [EMAIL PROTECTED]wrote: Hi, I spent almost all my day trying to solve this issue. I am consuming web services using axis2 1.4.1 with XmlBeans binding. Everything works fine if I consume the web services with my test clients . But when I deploy my application to an app server (Oc4j or Oracle AS) I am getting some errors. When I try with jdk 1.5 it works fine.. I debugged the application and this line is the cause of the exception. It is in request document class. return (org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument)org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance(type, null); I did some further testing and found that it is happening when I call org.apache.xmlbeans.XmlBeans.getContextTypeLoader() The error messages that I am getting are 1. JBO-29000: Unexpected exception caught: java.lang.IllegalAccessError, msg=tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument 2. tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument As I understand somehow the application server is not allowing the XMLBeans APIs to dynamically load the classes ..But I couldn't find a way to convince it.. Does anybody have any idea by any chance? Thanks a lot -ms -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: Axis2 databinding xmlbeans: ArrayStoreException even within sample perf.wsdl
Hi everyone, finally solved, found the root cause, a classpath related issue. Within my ~/.ant/lib was a old xbean-1-jar residing which was loaded first. After removing the jar from the .ant/lib-folder, the sample works as expected Christian Christian Vogt schrieb am 11.09.2008 12:52: Hi everyone, I am trying out the xmlbeans databinding with axis2 and ran into an issue even with the distributed sample-wsdl-file 'perf.wsdl'. ADB is working fine, but when switching ot xmlbeans-databinding, there is the following exception thrown: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.tool.ant.AntCodegenTask.execute(AntCodegenTask.java:416) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 13 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:115) ... 14 more Caused by: java.lang.RuntimeException: java.lang.ArrayStoreException at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:325) ... 19 more Caused by: java.lang.ArrayStoreException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.toArray(ArrayList.java:304) at org.apache.axis2.xmlbeans.CodeGenerationUtility.convertToSchemaArray(CodeGenerationUtility.java:562) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:189) ... 19 more Find attached my build-file and the verbose ant-output plus the perf.wsdl coming with the axis2-1.4.1 distribution, just in case. I also tried previous axis2-releases with the same result. Any ideas why the sample wsdl cannot be used with xmlbeans-databinding? Thanks Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03
I don't have an aar file because I am not hosting the web services I am consuming them from a web application.. From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 3:05 AM To: axis-user@ws.apache.org Subject: Re: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03 try to put all the jar files under the lib folder of the service archive (.aar file) to WEB-INF/lib folder. thanks, Amila. On Wed, Sep 17, 2008 at 9:58 AM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I spent almost all my day trying to solve this issue. I am consuming web services using axis2 1.4.1 with XmlBeans binding. Everything works fine if I consume the web services with my test clients . But when I deploy my application to an app server (Oc4j or Oracle AS) I am getting some errors. When I try with jdk 1.5 it works fine.. I debugged the application and this line is the cause of the exception. It is in request document class. return (org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument)org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance(type, null); I did some further testing and found that it is happening when I call org.apache.xmlbeans.XmlBeans.getContextTypeLoader() The error messages that I am getting are 1. JBO-29000: Unexpected exception caught: java.lang.IllegalAccessError, msg=tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument 2. tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument As I understand somehow the application server is not allowing the XMLBeans APIs to dynamically load the classes ..But I couldn't find a way to convince it.. Does anybody have any idea by any chance? Thanks a lot -ms -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
RE: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03
Some more details .. I could make it work if I change the below getClassLoader with Thread.currentThread().getContextClassLoader() org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(FetchProfileResponseDocument.class.getClassLoader() This is a generated code and normally works fine with jdk 1.5 .. I guess there should be some setting to make it work in 1.4 as well.. Any Idea ? From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 7:10 AM To: axis-user@ws.apache.org Subject: RE: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03 I don't have an aar file because I am not hosting the web services I am consuming them from a web application.. From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 3:05 AM To: axis-user@ws.apache.org Subject: Re: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03 try to put all the jar files under the lib folder of the service archive (.aar file) to WEB-INF/lib folder. thanks, Amila. On Wed, Sep 17, 2008 at 9:58 AM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I spent almost all my day trying to solve this issue. I am consuming web services using axis2 1.4.1 with XmlBeans binding. Everything works fine if I consume the web services with my test clients . But when I deploy my application to an app server (Oc4j or Oracle AS) I am getting some errors. When I try with jdk 1.5 it works fine.. I debugged the application and this line is the cause of the exception. It is in request document class. return (org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument)org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance(type, null); I did some further testing and found that it is happening when I call org.apache.xmlbeans.XmlBeans.getContextTypeLoader() The error messages that I am getting are 1. JBO-29000: Unexpected exception caught: java.lang.IllegalAccessError, msg=tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument 2. tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument As I understand somehow the application server is not allowing the XMLBeans APIs to dynamically load the classes ..But I couldn't find a way to convince it.. Does anybody have any idea by any chance? Thanks a lot -ms -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03
Hi, I spent almost all my day trying to solve this issue. I am consuming web services using axis2 1.4.1 with XmlBeans binding. Everything works fine if I consume the web services with my test clients . But when I deploy my application to an app server (Oc4j or Oracle AS) I am getting some errors. When I try with jdk 1.5 it works fine.. I debugged the application and this line is the cause of the exception. It is in request document class. return (org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument)org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance(type, null); I did some further testing and found that it is happening when I call org.apache.xmlbeans.XmlBeans.getContextTypeLoader() The error messages that I am getting are 1. JBO-29000: Unexpected exception caught: java.lang.IllegalAccessError, msg=tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument 2. tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument As I understand somehow the application server is not allowing the XMLBeans APIs to dynamically load the classes ..But I couldn't find a way to convince it.. Does anybody have any idea by any chance? Thanks a lot -ms
Axis2 databinding xmlbeans: ArrayStoreException even within sample perf.wsdl
Hi everyone, I am trying out the xmlbeans databinding with axis2 and ran into an issue even with the distributed sample-wsdl-file 'perf.wsdl'. ADB is working fine, but when switching ot xmlbeans-databinding, there is the following exception thrown: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.tool.ant.AntCodegenTask.execute(AntCodegenTask.java:416) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 13 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:115) ... 14 more Caused by: java.lang.RuntimeException: java.lang.ArrayStoreException at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:325) ... 19 more Caused by: java.lang.ArrayStoreException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.toArray(ArrayList.java:304) at org.apache.axis2.xmlbeans.CodeGenerationUtility.convertToSchemaArray(CodeGenerationUtility.java:562) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:189) ... 19 more Find attached my build-file and the verbose ant-output plus the perf.wsdl coming with the axis2-1.4.1 distribution, just in case. I also tried previous axis2-releases with the same result. Any ideas why the sample wsdl cannot be used with xmlbeans-databinding? Thanks Christian Apache Ant version 1.6.5 compiled on November 9 2005 Buildfile: build.xml Detected Java version: 1.5 in: /usr/lib/jvm/java-1.5.0-sun-1.5.0.15/jre Detected OS: Linux parsing buildfile /home/cv/temp/axis2xmlbeans/build.xml with URI = file:///home/cv/temp/axis2xmlbeans/build.xml Project base dir set to: /home/cv/temp/axis2xmlbeans Build sequence for target(s) `main' is [main] Complete build sequence is [main, ] main: [delete] Deleting directory /home/cv/temp/axis2xmlbeans/~/temp/axis2xmlbeans [delete] Deleting directory /home/cv/temp/axis2xmlbeans/~/temp/axis2xmlbeans [mkdir] Created dir: /home/cv/temp/axis2xmlbeans/~/temp/axis2xmlbeans [codegen] Retrieving document at '/opt/java/axis2/samples/wsdl/perf.wsdl'. BUILD FAILED /home/cv/temp/axis2xmlbeans/build.xml:29: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.tool.ant.AntCodegenTask.execute(AntCodegenTask.java:418) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main
Asynchronous web services using Axis2 with XMLBeans binding
I am developing asynchronous web services using Axis2 with XMLBeans binding. 1)We are using this command to generate the client stubs WSDL2Java -uri ABC.wsdl -d xmlbeans -a 2)When calling stub's startxyz() method through our Client Program for asynchronous calling of our web service, the request is not going to server side and it is not showing any client side exception. 3)But when we change _operationClient.execute(true); line in startxyz() method of the client stub which was earlier _operationClient.execute(false); the request went to server side. Axis 1.4 version is used There is one solution to it. Putting Thread.sleep(2) after the .startxx method call works fine. But i have to send hundreds of records asynchronysly. If I write Thread.sleep(2), It will take 20 seconds for processing each request. I have to reduce this time as much as we can. Is there any other way to overcome this problem? Thanks, Aseem -- View this message in context: http://www.nabble.com/Asynchronous-web-services-using-Axis2-with-XMLBeans-binding-tp19373251p19373251.html 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: Asynchronous web services using Axis2 with XMLBeans binding
On Mon, Sep 8, 2008 at 8:00 PM, Aseem Sharma [EMAIL PROTECTED]wrote: I am developing asynchronous web services using Axis2 with XMLBeans binding. 1)We are using this command to generate the client stubs WSDL2Java -uri ABC.wsdl -d xmlbeans -a 2)When calling stub's startxyz() method through our Client Program for asynchronous calling of our web service, the request is not going to server side and it is not showing any client side exception. 3)But when we change _operationClient.execute(true); line in startxyz() method of the client stub which was earlier _operationClient.execute(false); the request went to server side. Axis 1.4 version is used There is one solution to it. Putting Thread.sleep(2) after the .startxx method call works fine. But i have to send hundreds of records asynchronysly. If I write Thread.sleep(2), It will take 20 seconds for processing each request. I have to reduce this time as much as we can. Is there any other way to overcome this problem? This is something to manage with you application logic. There is no need to keep a sleep for every request. but you have to keep the client alive until it sends all the messages. thanks, Amila. Thanks, Aseem -- View this message in context: http://www.nabble.com/Asynchronous-web-services-using-Axis2-with-XMLBeans-binding-tp19373251p19373251.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: MTOM XMLBeans axis2 1.4
AFAIK MTOM support in Axis2 XMLBeans data binding is broken for some time (my apologies if somebody fixed it recently)... People are not much motivated for supporting XMLBeans as it does not have the native binary support as ADB+Axiom has. As a result all the binary data needs to be encoded back and forth to from base64 when supporting MTOM with XML beans giving many limitations and inefficiencies. thanks, Thilina On Sun, Aug 17, 2008 at 9:31 PM, Shehan Simen [EMAIL PROTECTED] wrote: Hi All, I have a web service which uses axis2 1.4 and uses ADB. But my client code is XMLBeans, Axis2 1.4. Does XMLBeans support MTOM? Can I send an attachment from my client using MTOM? Thanks. -- Thilina Gunarathne - http://thilinag.blogspot.com
MTOM XMLBeans axis2 1.4
Hi All, I have a web service which uses axis2 1.4 and uses ADB. But my client code is XMLBeans, Axis2 1.4. Does XMLBeans support MTOM? Can I send an attachment from my client using MTOM? Thanks.
Re: XMLBeans ? is there a better approach
Hi Amila , The other databindings provided by axis2 are ADB and JIBX However XMLBeans provides 100% schema support which is a great advantage of using this databinding which may not be there in other databinding's . So can any one please tell the advantages of other databindings. Thanks And Regards Sriram P --- On Fri, 1/8/08, Amila Suriarachchi [EMAIL PROTECTED] wrote: From: Amila Suriarachchi [EMAIL PROTECTED] Subject: Re: XMLBeans ? is there a better approach To: axis-user@ws.apache.org Date: Friday, 1 August, 2008, 10:56 AM On Thu, Jul 31, 2008 at 2:31 PM, sri ram [EMAIL PROTECTED] wrote: Hi all, Can anyone give me the better approach of databinding that I have to follow for my project.This project has almost 396 method and can be more in the upcoming releases, which are exposed as webservices. So while using XMLBeans as databinding it created many .java and xsb files . These files take ,quite a long time to get compiled and sometimes have OutOfMemoryException and we have to set out heap size to get rid of this exception. Once the aar file is deployed into the server and send a SOAP request ,the Axis Servlet takes more time to get initialized which is one of the main performance drawback. So can any one suggest a better databinding to have better performance as a whole A databinding which can give 100% schema support,Quick response and Quick initialization of the servlet. try to use ADB or jaxbri thanks Amila. Thanks And Regards Sriram P . Unlimited freedom, unlimited storage. Get it now -- Amila Suriarachchi, WSO2 Inc. Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/
Re: XMLBeans ? is there a better approach
On Fri, Aug 1, 2008 at 1:48 PM, sri ram [EMAIL PROTECTED]wrote: Hi Amila , The other databindings provided by axis2 are ADB and JIBX However XMLBeans provides 100% schema support which is a great advantage of using this databinding which may not be there in other databinding's . So can any one please tell the advantages of other databindings. Axis2 provides jaxb data binding as well (-d jaxbri) ADB - Does not support Xml schema 100% (but it provides most of the common schema constructs), but faster than others. Jaxbri - Provides 100% Xml schema support. this is the java standard. Jibx - Can bind wsdl to use existing classes. thanks, Amila. Thanks And Regards Sriram P --- On *Fri, 1/8/08, Amila Suriarachchi [EMAIL PROTECTED]*wrote: From: Amila Suriarachchi [EMAIL PROTECTED] Subject: Re: XMLBeans ? is there a better approach To: axis-user@ws.apache.org Date: Friday, 1 August, 2008, 10:56 AM On Thu, Jul 31, 2008 at 2:31 PM, sri ram [EMAIL PROTECTED]wrote: Hi all, Can anyone give me the better approach of databinding that I have to follow for my project.This project has almost 396 method and can be more in the upcoming releases, which are exposed as webservices. So while using XMLBeans as databinding it created many .java and xsb files . These files take ,quite a long time to get compiled and sometimes have OutOfMemoryException and we have to set out heap size to get rid of this exception. Once the aar file is deployed into the server and send a SOAP request ,the Axis Servlet takes more time to get initialized which is one of the main performance drawback. So can any one suggest a better databinding to have better performance as a whole A databinding which can give 100% schema support,Quick response and Quick initialization of the servlet. try to use ADB or jaxbri thanks Amila. Thanks And Regards Sriram P . -- Unlimited freedom, unlimited storage. Get it nowhttp://in.rd.yahoo.com/tagline_mail_2/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/ -- Amila Suriarachchi, WSO2 Inc. -- Unlimited freedom, unlimited storage. Get it nowhttp://in.rd.yahoo.com/tagline_mail_2/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/ -- Amila Suriarachchi, WSO2 Inc.
Re: XMLBeans ? is there a better approach
Hi David, I just wanted to confirm regarding this. Does the scomp compiler doesn't show any Out of Memory Exeptions? And Moreover when we use wsdl2java command we do mention the databinding using -d option ,if we mention XMLBeans in that option will it not recompile the schema.Or is there a way to eliminate the recompiling of the schema . Would like to know your ideas on this which is of a great help . Thanks And Regards Sriram P --- On Fri, 1/8/08, David Ojeda [EMAIL PROTECTED] wrote: From: David Ojeda [EMAIL PROTECTED] Subject: Re: XMLBeans ? is there a better approach To: axis-user@ws.apache.org Date: Friday, 1 August, 2008, 3:50 AM Hello, I had a similar problem with XMLBeans, but regarding file generation. The XSDs I used were very big (10k classes), so this caused an OutOfMemoryException when doing wsdl2java. The solution I found was generating the XMLBeans classes in a separate xml with scomp and using wsdl2java with the -Ewdc option. Maybe this idea will help you. On Thursday 31 July 2008 04:31:13 am sri ram wrote: Hi all, Can anyone give me the better approach of databinding that I have to follow for my project.This project has almost 396 method and can be more in the upcoming releases, which are exposed as webservices. So while using XMLBeans as databinding it created many .java and xsb files . These files take ,quite a long time to get compiled and sometimes have OutOfMemoryException and we have to set out heap size to get rid of this exception. Once the aar file is deployed into the server and send a SOAP request ,the Axis Servlet takes more time to get initialized which is one of the main performance drawback. So can any one suggest a better databinding to have better performance as a whole A databinding which can give 100% schema support,Quick response and Quick initialization of the servlet. Thanks And Regards Sriram P . Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/ -- Ing. David Ojeda Integra Consultores Caracas, Venezuela - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Connect with friends all over the world. Get Yahoo! India Messenger at http://in.messenger.yahoo.com/?wm=n/
Re: XMLBeans ? is there a better approach
Hello Sriram,
Yes, scomp compiles without any OutofMemoryExceptions. However, I had to
increase the memory to 384mb, -Xmx and -Xms work fine also in case you need to
increase the memory.
When using wsdl2java I use the following options, it doesn't compile the schema
at all since it uses the -Edwc option.
!-- - - - - - - - - - - - - - - - - -
target: wsdl2java
- - - - - - - - - - - - - - - - - --
target name=wsdl2java description=Create service implementation with
wsdl2java
mkdir dir=output/${ws.name}/
java classname=org.apache.axis2.wsdl.WSDL2Java
failonerror=true
fork=true
classpath refid=axis2.classpath/
classpath location=etc/axis2log4j/
arg value=-d/ !-- use xmlbeans --
arg value=xmlbeans/
arg value=-ss/ !--generate skeleton --
arg value=-Ewdc/!-- do not generate xmlbeans classes--
arg value=-xsdconfig/
arg file=xsd/NStoPkg.xsdconfig/
arg value=-sd/ !-- generate services.xml --
arg value=-o/ !-- output directory --
arg file=output/${ws.name}/
arg value=--noBuildXML/
arg value=-uri/
arg file=wsdl/${ws.name}.wsdl/ !-- wsdl --
/java
echoService classes generated with WSDL2Java, erasing classes that
will
be replaced by xmlbeans classes/echo
delete includeemptydirs=true
fileset dir=output/${ws.name}/src
include name=**/*/
exclude name=**/.svn/**/
exclude name=**/*Skeleton.java/
exclude name=**/*MessageReceiverInOut.java/
exclude name=**/*Fault.java/
/fileset
fileset dir=output/${ws.name}/resources
include name=schemaorg_apache_xmlbeans/**/
/fileset
/delete
/target
This is my xmlbeans task:
!-- =
target: generate.xbeans
= --
target name=generate.xbeans depends=prepare, check.xbeans
description=Generate xmlbeans classes unless=xbean.uptodate
xmlbean
failonerror=true
memoryInitialSize=384m
memoryMaximumSize=384m
destfile=${jar.dir}/${xbean.filename}
javasource=1.4
classpathref=class.path
fileset refid=wsdl.files/
fileset refid=xsd.files/
/xmlbean
/target
On Friday 01 August 2008 05:04:01 am sri ram wrote:
Hi David,
I just wanted to confirm regarding this.
Does the scomp compiler doesn't show any Out of Memory Exeptions?
And Moreover when we use wsdl2java command we do mention the databinding
using -d option ,if we mention XMLBeans in that option will it not
recompile the schema.Or is there a way to eliminate the recompiling of the
schema .
Would like to know your ideas on this which is of a great help .
Thanks And Regards
Sriram P
--- On Fri, 1/8/08, David Ojeda [EMAIL PROTECTED] wrote:
From: David Ojeda [EMAIL PROTECTED]
Subject: Re: XMLBeans ? is there a better approach
To: axis-user@ws.apache.org
Date: Friday, 1 August, 2008, 3:50 AM
Hello,
I had a similar problem with XMLBeans, but regarding file generation.
The XSDs I used were very big (10k classes), so this caused an
OutOfMemoryException when doing wsdl2java.
The solution I found was generating the XMLBeans classes in a separate xml
with
scomp and using wsdl2java with the -Ewdc option.
Maybe this idea will help you.
On Thursday 31 July 2008 04:31:13 am sri ram wrote:
Hi all,
Can anyone give me the better approach of databinding that I have
to
follow for my project.This project has almost 396 method and can be more
in the upcoming releases, which are exposed as webservices. So while
using XMLBeans as databinding it created many .java and xsb files .
These
files
take ,quite a long time to get compiled and sometimes have
OutOfMemoryException and we have to set out heap size to get rid of this
exception. Once the aar file is deployed into the server and send a SOAP
request ,the Axis Servlet takes more time to get initialized which is one
of the main performance drawback. So can any one suggest a better
databinding to have better performance as a whole A databinding which
can
give 100% schema support,Quick response and Quick initialization of the
servlet.
Thanks And Regards
Sriram P
.
Unlimited freedom, unlimited storage. Get it now, on
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08
Re: XMLBeans ? is there a better approach
Hello, I had a similar problem with XMLBeans, but regarding file generation. The XSDs I used were very big (10k classes), so this caused an OutOfMemoryException when doing wsdl2java. The solution I found was generating the XMLBeans classes in a separate xml with scomp and using wsdl2java with the -Ewdc option. Maybe this idea will help you. On Thursday 31 July 2008 04:31:13 am sri ram wrote: Hi all, Can anyone give me the better approach of databinding that I have to follow for my project.This project has almost 396 method and can be more in the upcoming releases, which are exposed as webservices. So while using XMLBeans as databinding it created many .java and xsb files . These files take ,quite a long time to get compiled and sometimes have OutOfMemoryException and we have to set out heap size to get rid of this exception. Once the aar file is deployed into the server and send a SOAP request ,the Axis Servlet takes more time to get initialized which is one of the main performance drawback. So can any one suggest a better databinding to have better performance as a whole A databinding which can give 100% schema support,Quick response and Quick initialization of the servlet. Thanks And Regards Sriram P . Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/ -- Ing. David Ojeda Integra Consultores Caracas, Venezuela - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Server ADB and client xmlBeans?
I think it is ok, because the client does not need to know what data binding the server side use. It does not even need to know what language(java or c#) the server use. Regards --- Guanxia Zhuang (Robin) Sycamore Networks (Shanghai China) Phone: 021-24050832 From: Shehan Simen [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2008 10:39 AM To: axis-user@ws.apache.org Subject: Server ADB and client xmlBeans? Hi, My axis2 service is using version 1.4 and using ADB. The client is using axis xml beans. Do I need to do any configuration to talk between client and server? I generate the server code using wsdl2java. The client is generated using wsdl2java too, but data binding is xml beans (but sever using ADB). Please let me know. Regards.
Re: XMLBeans ? is there a better approach
On Thu, Jul 31, 2008 at 2:31 PM, sri ram [EMAIL PROTECTED]wrote: Hi all, Can anyone give me the better approach of databinding that I have to follow for my project.This project has almost 396 method and can be more in the upcoming releases, which are exposed as webservices. So while using XMLBeans as databinding it created many .java and xsb files . These files take ,quite a long time to get compiled and sometimes have OutOfMemoryException and we have to set out heap size to get rid of this exception. Once the aar file is deployed into the server and send a SOAP request ,the Axis Servlet takes more time to get initialized which is one of the main performance drawback. So can any one suggest a better databinding to have better performance as a whole A databinding which can give 100% schema support,Quick response and Quick initialization of the servlet. try to use ADB or jaxbri thanks Amila. Thanks And Regards Sriram P . -- Unlimited freedom, unlimited storage. Get it nowhttp://in.rd.yahoo.com/tagline_mail_2/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/ -- Amila Suriarachchi, WSO2 Inc.
Axis 2.1.3: Wsdl2java with xmlbeans binding on linux fails to generate code using Exchange Web Service WSDL file
Hello, I have run across into issues where wsdl2java fails to generate java codes from Exchange Web Service WSDL file on linux machine. The error reported is: Retrieving schema at 'messages.xsd', relative to 'file:/tmp/axis2-1.3/bin/'. Retrieving schema at 'types.xsd', relative to 'file:/tmp/axis2-1.3/bin/messages. xsd'. [INFO] Resolving schema with publicId [http://schemas.microsoft.com/exchange/services/2006/messages] and systemId [messages.xsd] [INFO] Resolving schema with publicId [http://schemas.microsoft.com/exchange/services/2006/types] and systemId [types.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenera tionEngine.java:265) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBe ansExtension.java:114) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenera tionEngine.java:218) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j ava:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess orImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBe ansExtension.java:103) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: project://local/types.xsd:51:1: error: cvc-enumeration-valid: string value 'none' is no t a valid enumeration value for type of processContents attribute in xs:wildcard at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGen erationUtility.java:319) ... 8 more Caused by: org.apache.xmlbeans.XmlException: project://local/types.xsd:51:1: error: cvc-enumeration-valid: string value 'none' is not a valid enumeration value for type of processContents attribute in xs:wildcard at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(Schem aTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j ava:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess orImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGen erationUtility.java:183) ... 8 more I am using the same binary and wsdl file on windows and that works fine. I have verified something obvious such as, windows line feed, correct import path, etc. I saw various mailing list archive, and it looks like a genuine issue in xmlbeans which has been fixed in 2.2. I have tried to update xmlbeans to 2.4 version, but the issue persists. I have also verified the class path on my linux environtment to ensure that we don't errorneously pick up older version of any library. Please advise. Best regards, Ridwan
Re: Axis 2.1.3: Wsdl2java with xmlbeans binding on linux fails to generate code using Exchange Web Service WSDL file
On Tue, Jul 29, 2008 at 12:51 AM, Ridwan Tan (ridtan) [EMAIL PROTECTED]wrote: Hello, I have run across into issues where wsdl2java fails to generate java codes from Exchange Web Service WSDL file on linux machine. The error reported is: Retrieving schema at 'messages.xsd', relative to '* file:/tmp/axis2-1.3/bin/*'. Retrieving schema at 'types.xsd', relative to '* file:/tmp/axis2-1.3/bin/messages*. xsd'. [INFO] Resolving schema with publicId [* http://schemas.microsoft.com/exchange/services/2006/messages*http://schemas.microsoft.com/exchange/services/2006/messages] and systemId [messages.xsd] [INFO] Resolving schema with publicId [* http://schemas.microsoft.com/exchange/services/2006/types*http://schemas.microsoft.com/exchange/services/2006/types] and systemId [types.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:114) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:218) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:103) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: project://local/types.xsd:51:1: error: cvc-enumeration-valid: string value 'none' is no t a valid enumeration value for type of processContents attribute in xs:wildcard at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:319) ... 8 more Caused by: org.apache.xmlbeans.XmlException: project://local/types.xsd:51:1: error: cvc-enumeration-valid: string value 'none' is not a valid enumeration value for type of processContents attribute in xs:wildcard at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:183) ... 8 more I am using the same binary and wsdl file on windows and that works fine. I have verified something obvious such as, windows line feed, correct import path, etc. I saw various mailing list archive, and it looks like a genuine issue in xmlbeans which has been fixed in 2.2. I have tried to update xmlbeans to 2.4 version, but the issue persists. I have also verified the class path on my linux environtment to ensure that we don't errorneously pick up older version of any library. try to compile this wsdl file using the XmlBeans Scheama compiler tool in linux platform. thanks, Amila. Please advise. Best regards, Ridwan -- Amila Suriarachchi, WSO2 Inc.
ADB Server XmlBeans at Client
Hi, Can I use ADB at server side and Xmlbeans in client side? Wsdl2java tools support this in axis2? Regards, Shehan
Re: ADB Server XmlBeans at Client
On Wed, Jul 16, 2008 at 10:59 PM, Shehan Simen [EMAIL PROTECTED] wrote: Hi, Can I use ADB at server side and Xmlbeans in client side? definitely. This is the whole idea about the web services. Even the server can be .Net as well. thanks, Amila. Wsdl2java tools support this in axis2? Regards, Shehan -- Amila Suriarachchi, WSO2 Inc.
axis2-1.4, xmlbeans, mtom, weblogic
Hi all, I developed a web service in java with axis2-1.4 (using xmlbeans, mtom) and generated java code from eclipse plug-in. The service deployed successfully onto Weblogic 8.1, BUT when it is invoked throws the following exception on server side: (I did deploy the same service on axis2server BUT NO Error- It works perfect.) Error is only on Weblogic -8.1 [ERROR] java.lang.NullPointerException at org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.jav a:122) at org.apache.axis2.engine.Phase.invoke(Phase.java:317) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques t(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se rvletStubImpl.java:1077) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl. java:465) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl. java:348) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r un(WebAppServletContext.java:7047) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu bject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121 ) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl etContext.java:3902) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl. java:2773) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) Error on the client side: [java] org.apache.axis2.AxisFault: java.lang.NullPointerException [java] at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java :512) [java] at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out InAxisOperation.java:370) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:416) [java] at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:228) [java] at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) [java] at mymtomns.SendAppAttServiceStub.sendData(SendAppAttServiceStub.java:169) [java] at mymtomns.SendAppAttClient.main(SendAppAttClient.java:60) Any suggestions or feedback would be much appreciated. Thanks Meena -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
RE:RE: axis2-1.4, xmlbeans, mtom, weblogic
I did develop a web service to send attachment using MTOM - xmlbeans, axis2-1.4 and deploy and tested successfully on weblogic. Now I created another webservice to send an Application and documents. This service works on axis2server, but not on weblogic. If xmlbeans doesn't support MTOM, then what is the best approach to send attachments as well as perform schema validation. Any help / suggestion / feedback is much appreciated. Thanks Meena -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: 05 June 2008 13:24 To: [EMAIL PROTECTED] Subject: Re: axis2-1.4, xmlbeans, mtom, weblogic On Thu, Jun 5, 2008 at 9:00 AM, Karunanidhi, Meena [EMAIL PROTECTED] wrote: I developed a web service in java with axis2-1.4 (using xmlbeans, mtom) and generated java code from eclipse plug-in. xmlbeans in axis2 doesn't support mtom. This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. snip Don't post confidential emails to a public list. Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AXis2-1.4 xmlbeans
Hi I need to send base64binary data as a attachment (as file size is huge) along with Order details (which needs to be validated against schema). Request OrderDetailsOrderID/Cost/date/ etc.. /OrderDetails attachment/attachment /Request Robert lazarski sent a mail saying Axis2 does not support xmlbeans MTOM binding. What would be the best approach to create a web service to do both schema validation and MTOM binding. Kindly advice. Meena -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
RE: AXis2-1.4 xmlbeans
I did develop a webservice to accept just the OrderId and attachment (MTOM) - using xmlbeans and deploy it onto weblogic. And able to test the service successfully. Working request Request OrderDetailsOrderID/Cost/date/ etc.. /OrderDetails attachment/attachment /Request Following throws NullPointerException - if the web service is deployed to Weblogic. (But works fine when deployed to axis2server) -=== Request OrderDetailsOrderID/Cost/date/ etc.. /OrderDetails attachment/attachment /Request Kindly advice Thanks in advance Meena From: Karunanidhi, Meena Sent: 05 June 2008 14:06 To: 'axis-user@ws.apache.org' Subject: AXis2-1.4 xmlbeans Hi I need to send base64binary data as a attachment (as file size is huge) along with Order details (which needs to be validated against schema). Request OrderDetailsOrderID/Cost/date/ etc.. /OrderDetails attachment/attachment /Request Robert lazarski sent a mail saying Axis2 does not support xmlbeans MTOM binding. What would be the best approach to create a web service to do both schema validation and MTOM binding. Kindly advice. Meena -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
AXis2-1.4 xmlbeans MTOM
Hi I need to send base64binary data as a attachment (as file size is huge) along with Order details (which needs to be validated against schema). Request OrderDetailsOrderID/Cost/date/ etc.. /OrderDetails attachment/attachment /Request Robert lazarski sent a mail saying Axis2 does not support xmlbeans MTOM binding. What would be the best approach to create a web service to do both schema validation and MTOM binding. Following throws NullPointerException - if the web service is deployed to Weblogic. (But works fine when deployed to axis2server) -=== Request OrderDetailsOrderID/Cost/date/ etc.. /OrderDetails attachment/attachment /Request Kindly advice Thanks in advance Meena -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
RE: AXis2-1.4 xmlbeans MTOM
Apologies for annoyed you with the previous mail. -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: 05 June 2008 15:21 To: axis-user@ws.apache.org Subject: Re: AXis2-1.4 xmlbeans MTOM On Thu, Jun 5, 2008 at 11:14 AM, Karunanidhi, Meena [EMAIL PROTECTED] wrote: Anyone looking into this... I recommend you read this over and over again until its memorized word for word. http://www.catb.org/~esr/faqs/smart-questions.html Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXis2-1.4 xmlbeans MTOM
ADB supports MTOM and does some schema validation... You can try code generating to your WSDL using ADB.. ~Thilina On Thu, Jun 5, 2008 at 7:28 AM, Karunanidhi, Meena [EMAIL PROTECTED] wrote: Apologies for annoyed you with the previous mail. -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: 05 June 2008 15:21 To: axis-user@ws.apache.org Subject: Re: AXis2-1.4 xmlbeans MTOM On Thu, Jun 5, 2008 at 11:14 AM, Karunanidhi, Meena [EMAIL PROTECTED] wrote: Anyone looking into this... I recommend you read this over and over again until its memorized word for word. http://www.catb.org/~esr/faqs/smart-questions.html Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://thilinag.blogspot.com
Axis 2 Callback - SSL, XMLBeans, over the internet
Hi, I am using an SSL client, XMLBeans binding and a client that the server cannot connect to over the internet. The steps are 1. Client connects to service using SSL and receives sync. response. 2. We have a service URL on the client also. When the server tries to call this service running on the client( We call it asynch notification ) it is blocked because the connection is over the internet and the client is not set up to receive a call like that. There is no publicly available IP. What is the difference between the above two in case of an async.call ? When a sync response can come back, an axis 2 async. call back can also come back ? Right ? How do One-way / two-way transports work over SSL ? Can callbacks use the same SSL session ? Thanks, Mohan -- View this message in context: http://www.nabble.com/Axis-2-Callback---SSL%2C-XMLBeans%2C-over-the-internet-tp17623346p17623346.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem with Arrays Axis2 and Xmlbeans
hi all we are facing a problem with AXIS2 and Xmlbeans while using Arrays WSDL having the following entry element name=cardHolderDTOArray nillable=true type=impl:ArrayOf_tns2_nillable_CardHolderDTO/ Also having complexType name=ArrayOf_tns2_nillable_CardHolderDTO complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns2:CardHolderDTO[]/ /restriction /complexContent /complexType when we generates the corresponding class using the wsdl2java it will generates the ArrayOfTns2NillableCardHolderDTOImpl and ArrayOfTns2NillableCardHolderDTO our problem is We were not able to set the CardHolderDTO[] in the skeleton also not able to retrieve the elements from the ArrayOfTns2NillableCardHolderDTO in the stub the problem is ArrayOfTns2NillableCardHolderDTO is not proving any get or set methods to set and get the DTO. only we can create an instance using the factory by this axis generated class Can anyone help us in this regard Thanks Sreejith -- View this message in context: http://www.nabble.com/problem-with-Arrays-Axis2-and-Xmlbeans-tp17595689p17595689.html 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-1.3, xmlbeans error
Any update on this. Thanks Meena From: Karunanidhi, Meena Sent: 29 May 2008 16:14 To: '[EMAIL PROTECTED]' Subject: Axis2-1.3, xmlbeans error Hi I created a web service using Axis2-1.3, xmlbeans on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: I am NOT using any authentication for my web service, it is simple enough to send and receive an order. Any suggestions,pls Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
xmlbeans - Parser already accessed!
Hi I created a web service using Axis2-1.3, xmlbeans with MTOM attachments on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: Is this an error with AXIOM Serialization Any help would be appreciated. Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
AXIOM xmlbeans - Parser already accessed!
Found a similar bug in the following link https://issues.apache.org/jira/browse/AXIS2-3068?page=com.atlassian.jira .plugin \ I tried nightly build ... still the client throws the below exception. Any help or suggestion would be greatly appreciated. Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) Thanks Meena From: Karunanidhi, Meena Sent: 30 May 2008 14:28 To: 'axis-user@ws.apache.org'; '[EMAIL PROTECTED]' Subject: xmlbeans - Parser already accessed! Hi I created a web service using Axis2-1.3, xmlbeans with MTOM attachments on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: Is this an error with AXIOM Serialization Any help would be appreciated. Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
axis2-1.3 xmlbeans parser error
Hi I created a web service using Axis2-1.3, xmlbeans on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: I am NOT using any authentication for my web service, it is simple enough to send and receive an order. Any suggestions,pls Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
Axis2-1.3, xmlbeans error
Hi I created a web service using Axis2-1.3, xmlbeans on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: I am NOT using any authentication for my web service, it is simple enough to send and receive an order. Any suggestions,pls Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
Can Axis2 w/ XMLBeans db use pregenerated XMLBeans resource files?
Hello All, I have a substantial namespace with a number of WS's I need to call dotted around it. I'm using the Axis 2 client with XMLBeans databinding. Creating each call client using WSDL2Java against the individual .wsdl's causes the resources used by XMLBeans to be generated each time. Given the size of the namespace and proximity of the WS calls, this is a long and largely redundant process. I would like to pre-generate the XMLBeans resources prior to any WSDL2Java call and have WSDL2Java utilize the pre-generated resources rather than generating resources each time. May I ask if this possible and how? Thanks in advance, Martin
AXIS2 -Ewdc option for wsdl2java using xmlbeans databinding
I downloaded the axis2 nightly build in order to try the -Ewdc wsdl2java
option.
When I run the wsdl2java for the StockQuotePrice quicksample and use the
-Ewdc option for xmlbeans binding, I get the following errors:
compile.src:
[javac] Compiling 214 source files to
c:\swdev\axis2-SNAPSHOT\samples\quickstartxmlbeans\build\service\build\classes
[javac]
c:\swdev\axis2-SNAPSHOT\samples\quickstartxmlbeans\build\service\src\samples\quickstart\service\xmlbeans\StockQuoteServiceSkeleton.java:40:
cannot find symbol
[javac] symbol : method getSymbol()
[javac] location: interface
samples.quickstart.service.xmlbeans.xsd.UpdateDocument.Update
[javac] map.put(param0.getUpdate().getSymbol(), new
Double(param0.getUpdate().getPrice()));
[javac] ^
[javac]
c:\swdev\axis2-SNAPSHOT\samples\quickstartxmlbeans\build\service\src\samples\quickstart\service\xmlbeans\StockQuoteServiceSkeleton.java:40:
cannot find symbol
[javac] symbol : method getPrice()
[javac] location: interface
samples.quickstart.service.xmlbeans.xsd.UpdateDocument.Update
[javac] map.put(param0.getUpdate().getSymbol(), new
Double(param0.getUpdate().getPrice()));
[javac]
^
[javac]
c:\swdev\axis2-SNAPSHOT\samples\quickstartxmlbeans\build\service\src\samples\quickstart\service\xmlbeans\StockQuoteServiceSkeleton.java:44:
cannot find symbol
[javac] symbol : method getSymbol()
[javac] location: interface
samples.quickstart.service.xmlbeans.xsd.GetPriceDocument.GetPrice
[javac] Double price = (Double)
map.get(param1.getGetPrice().getSymbol());
[javac] ^
[javac]
c:\swdev\axis2-SNAPSHOT\samples\quickstartxmlbeans\build\service\src\samples\quickstart\service\xmlbeans\StockQuoteServiceSkeleton.java:54:
cannot find symbol
[javac] symbol : method setReturn(double)
[javac] location: interface
samples.quickstart.service.xmlbeans.xsd.GetPriceResponseDocument.GetPriceResponse
[javac] res.setReturn(ret);
[javac]^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 4 errors
BUILD FAILED
c:\swdev\axis2-SNAPSHOT\samples\quickstartxmlbeans\build.xml:77: The
following error occurred while executing this line:
c:\swdev\axis2-SNAPSHOT\samples\quickstartxmlbeans\build\service\build.xml:50:
Compile failed; see the compiler error output for details.
Here's the ant task for running wsdl2java:
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpathref=axis2.wl.xmlbeans.classpath
arg line=-uri ${wsdl.uri}/
arg line=-s/
arg line=-ss/
arg line=-sd/
arg line=-ssi/
arg line=-ap/
arg line=-ns2p
http://quickstart.samples/xsd=samples.quickstart.service.xmlbeans.xsd/
arg line=-l java/
arg line=-p samples.quickstart.service.xmlbeans/
arg line=-d xmlbeans/
arg line=-o ${build.dir}/service/
arg line=-Ewdc/
/java
I don't get any errors, when I remove the -Ewdc option. Do you know
what's wrong?
Thanks,
Jonathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS2 wsdl2java limitations using jibx and xmlbeans databinding
On Sun, Mar 9, 2008 at 9:09 AM, Jonathan Joseph [EMAIL PROTECTED] wrote: Dennis, The wsdl works with ADB, with the exception of the 2 part declarations in a message declaration. I plan to enter a separte bug in JIRA for the jibx/soapheader, jibx/circular imports cases that you can look at (I'll provide the wsdl). And I plan to enter a separate JIRA bug for the xmlbeans circular imports case for the xmlbeans experts. Here are my results using ADB binding: Test Case 1: adb binding: 2 parts in a message. Results: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: More than one part for message getPriceMessage This is a problem with your wsdl. According to the Basic profile if there are multiple parts for an message, (in document style) the part which should used must be specified at the binding level. eg. wsdl:operation name=Test soap:operation soapAction=Test/ wsdl:input soap:body use=literal parts=RequestMsg/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation thanks, Amila. Test Case 2: adb binding: circular imports: Results: OK - NO ERRORS Retrieving schema wsdl:imported from '../../../schema/StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/quickstartadb/resources/META-INF/'. Retrieving schema at 'StockQuoteB.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteA.xsd'. Retrieving schema at 'StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteB.xsd'. Retrieving schema wsdl:imported from '../../../schema/StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/quickstartadb/resources/META-INF/'. Retrieving schema at 'StockQuoteB.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteA.xsd'. Retrieving schema at 'StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteB.xsd'. Test Case 3: soap header declaration: Results: OK - NO ERRORS Thanks, Jonathan Dennis Sosnoski wrote: Hi Jonathan, Since you didn't provide the modified WSDL it's difficult to say what's going wrong with this. Does your WSDL work with ADB? I gather you're using a header part, which probably has not been tested thoroughly. If you want to enter a Jira on this I'll take a look at the JiBX handling. - Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: AXIS2 wsdl2java limitations using jibx and xmlbeans databinding
On Sat, Mar 8, 2008 at 3:39 AM, [EMAIL PROTECTED] wrote:
I'm trying to use wsdl2java from the Axis2 v1.3 distribution to
generate soap headers, and import xml schemas via either jibx or
xmlbeans databinding. I've run into some limitations using wsdl2java
and wanted to confirm my findings. All my tests used the
StockQuoteService wsdl provided in the quickstartjibx and
quickstartxmlbeans examples.
1) Test Results for more than one part element per message element:
-jibx: obtained the following error.
Caused by: org.apache.axis2.AxisFault: message
{http://quickstart.samples/}myHeaderMessagehttp://quickstart.samples/%7DmyHeaderMessagenot
found in the WSDL
-xmlbeans: obtained the following error.
Caused by:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:More
than one part for message
getPriceMessage
This is because of the problem I mentioned earlier.
2) Test Results for Cirular imports in a wsdl, where xml schema A
imports schema B, which imports the original schema A:
-jibx: didn't try. xml schema is complicated.
-xmlbeans: Get 'Duplicate global element' Error.
Caused by: org.apache.xmlbeans.XmlException:
project://local/AlertInfrastructureTransactions.xsd:14:5: error:
sch-props-correct.2: Duplicate global element:
[EMAIL PROTECTED] (Original global
element found in file: null)
Try this.
When generating the code with wsdl2java tool use -Ewdc option. This would
generate some dummy classes for Xml beans.
Then generate the Xmlbeans classes with the scomp tool comes with the
Xmlbeans distribution.
Then replace the above dummy classes with the latter generated data bind
classes.
3) Test Results for soap headers added to binding.
-jibx: Get mapping error when soap:header ... is added to binding.
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: No mapping defined for element
{http://quickstart.samples/xsd}myHeaderhttp://quickstart.samples/xsd%7DmyHeader
-xmlbeans: works, as long as there is a separate 1 part message for
the header.
even for headers you have to specify the part of the message to be used
wsdl:operation name=Test
soap:operation soapAction=Test/
wsdl:input
soap:body use=literal parts=RequestMsg/
soap:header use=literal part=HeaderMsg
message=tns:HeaderMsg/
/wsdl:input
wsdl:output
soap:body use=literal/
/wsdl:output
/wsdl:operation
thanks,
Amila.
Based on these findings, I plan to use xmlbeans databinding and pass
the xml documents as string parameters, then use xmlbeans to create
the binding objects in the invoked service method.
Has anyone run into the issues cited above or had different experiences?
Thanks,
Jonathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi,
WSO2 Inc.
Re: AXIS2 wsdl2java limitations using jibx and xmlbeans databinding
Correction: There is no bug to report for jbix/circular imports. Jonathan Joseph wrote: Dennis, The wsdl works with ADB, with the exception of the 2 part declarations in a message declaration. I plan to enter a separte bug in JIRA for the jibx/soapheader, jibx/circular imports cases that you can look at (I'll provide the wsdl). And I plan to enter a separate JIRA bug for the xmlbeans circular imports case for the xmlbeans experts. Here are my results using ADB binding: Test Case 1: adb binding: 2 parts in a message. Results: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: More than one part for message getPriceMessage Test Case 2: adb binding: circular imports: Results: OK - NO ERRORS Retrieving schema wsdl:imported from '../../../schema/StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/quickstartadb/resources/META-INF/'. Retrieving schema at 'StockQuoteB.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteA.xsd'. Retrieving schema at 'StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteB.xsd'. Retrieving schema wsdl:imported from '../../../schema/StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/quickstartadb/resources/META-INF/'. Retrieving schema at 'StockQuoteB.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteA.xsd'. Retrieving schema at 'StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteB.xsd'. Test Case 3: soap header declaration: Results: OK - NO ERRORS Thanks, Jonathan Dennis Sosnoski wrote: Hi Jonathan, Since you didn't provide the modified WSDL it's difficult to say what's going wrong with this. Does your WSDL work with ADB? I gather you're using a header part, which probably has not been tested thoroughly. If you want to enter a Jira on this I'll take a look at the JiBX handling. - Dennis - 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 wsdl2java limitations using jibx and xmlbeans databinding
Thanks Amila for pointing out the missing 'parts' attribute in the
soap:body of my wsdl:binding.
7 out of 9 of my tests are now working. Here are my results thus far
using wsdl2java for ADB, JIBX, XMLBeans data bindings:
ADB Binding: All my test cases are working for ADB.
XMLBeans Binding: still have a problem with circular imports.
--
Amila, I don't quite understand how to proceed. What is the -Ewdc
option? I tried the -Ewdc wsdl2java option using the same import
declaration for the xmlschema that causes circular references, and got
the same error for circular imports (Duplicate global type). There were
no classes, under the build/service/classes directory due to the error.
I've compiled the xmlschemas via scomp, but am not sure on how to proceed.
Results:
java.lang.RuntimeException: org.apache.xmlbeans.XmlException:
project://local/StockQuoteA.xsd:17:5: error: sch-props-correct.2:
Duplicate global type: [EMAIL PROTECTED]
(Original global type found in file: null)
JIBX Binding: still have problem with the 2 part message declartion
(which works with ADB binding)
-
Test Case 1: soap header declaration, using a wsdl:part element from
a wsdl:message element that contains 2 wsdl:part elements.
Results:
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: No mapping defined for element
{http://quickstart.samples/xsd}myHeader
Relevant parts of the WSDL:
wsdl:definitions xmlns:axis2=http://quickstart.samples/;
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:ns=http://quickstart.samples/xsd;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
targetNamespace=http://quickstart.samples/;
wsdl:types
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://quickstart.samples/xsd;
xs:element name=myHeader type=xs:string/
etc.
/wsdl:types
wsdl:message name=getPriceMessage
wsdl:part name=myHeaderMessagePart element=ns:myHeader/
wsdl:part name=part1 element=ns:getPrice/
/wsdl:message
wsdl:binding name=StockQuoteServiceSOAP11Binding
type=axis2:StockQuoteServicePortType
soap:binding transport=http://schemas.xmlsoap.org/soap/http;
style=document/
wsdl:operation name=getPrice
soap:operation soapAction=urn:getPrice style=document/
wsdl:input
soap:header message=axis2:getPriceMessage
part=myHeaderMessagePart use=literal/
soap:body use=literal parts=part1
namespace=http://quickstart.samples//
/wsdl:input
etc
/wsdl:binding
Amila Suriarachchi wrote:
On Sat, Mar 8, 2008 at 3:39 AM, [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'm trying to use wsdl2java from the Axis2 v1.3 distribution to
generate soap headers, and import xml schemas via either jibx or
xmlbeans databinding. I've run into some limitations using wsdl2java
and wanted to confirm my findings. All my tests used the
StockQuoteService wsdl provided in the quickstartjibx and
quickstartxmlbeans examples.
1) Test Results for more than one part element per message
element:
-jibx: obtained the following error.
Caused by: org.apache.axis2.AxisFault: message
{http://quickstart.samples/}myHeaderMessage
http://quickstart.samples/%7DmyHeaderMessage not found in the WSDL
-xmlbeans: obtained the following error.
Caused by:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
More than one part for message
getPriceMessage
This is because of the problem I mentioned earlier.
2) Test Results for Cirular imports in a wsdl, where xml schema A
imports schema B, which imports the original schema A:
-jibx: didn't try. xml schema is complicated.
-xmlbeans: Get 'Duplicate global element' Error.
Caused by: org.apache.xmlbeans.XmlException:
project://local/AlertInfrastructureTransactions.xsd:14:5: error:
sch-props-correct.2: Duplicate global element:
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] (Original
global
element found in file: null)
Try this.
When generating the code with wsdl2java tool use -Ewdc option. This
would generate some dummy classes for Xml beans.
Then generate the Xmlbeans classes with the scomp tool comes with the
Xmlbeans distribution.
Then replace the above dummy classes with the latter generated data
bind classes.
3) Test Results for soap headers added to binding.
-jibx: Get mapping error when soap:header ... is added to binding.
Exception in thread
Re: AXIS2 wsdl2java limitations using jibx and xmlbeans databinding
On Mon, Mar 10, 2008 at 6:14 AM, Jonathan Joseph [EMAIL PROTECTED]
wrote:
Thanks Amila for pointing out the missing 'parts' attribute in the
soap:body of my wsdl:binding.
7 out of 9 of my tests are now working. Here are my results thus far
using wsdl2java for ADB, JIBX, XMLBeans data bindings:
ADB Binding: All my test cases are working for ADB.
XMLBeans Binding: still have a problem with circular imports.
--
Amila, I don't quite understand how to proceed. What is the -Ewdc
option? I tried the -Ewdc wsdl2java option using the same import
declaration for the xmlschema that causes circular references, and got
the same error for circular imports (Duplicate global type).
Sorry I forgot to mention. This feature only available with the nightly
builds. I added this feature
after Axis2 1.3.
There were
no classes, under the build/service/classes directory due to the error.
I've compiled the xmlschemas via scomp, but am not sure on how to proceed.
if you use a nightly build then when you use the -Ewdc with wsdl2java tool
it would generate the
code with some dummy classes for XMLbeans data binding. Then you can replace
these classes with the
above generated code.
thanks,
Amila.
Results:
java.lang.RuntimeException: org.apache.xmlbeans.XmlException:
project://local/StockQuoteA.xsd:17:5: error: sch-props-correct.2:
Duplicate global type: [EMAIL PROTECTED]
(Original global type found in file: null)
JIBX Binding: still have problem with the 2 part message declartion
(which works with ADB binding)
-
Test Case 1: soap header declaration, using a wsdl:part element from
a wsdl:message element that contains 2 wsdl:part elements.
Results:
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: No mapping defined for element
{http://quickstart.samples/xsd}myHeaderhttp://quickstart.samples/xsd%7DmyHeader
Relevant parts of the WSDL:
wsdl:definitions xmlns:axis2=http://quickstart.samples/;
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:ns=http://quickstart.samples/xsd;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
targetNamespace=http://quickstart.samples/;
wsdl:types
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://quickstart.samples/xsd;
xs:element name=myHeader type=xs:string/
etc.
/wsdl:types
wsdl:message name=getPriceMessage
wsdl:part name=myHeaderMessagePart element=ns:myHeader/
wsdl:part name=part1 element=ns:getPrice/
/wsdl:message
wsdl:binding name=StockQuoteServiceSOAP11Binding
type=axis2:StockQuoteServicePortType
soap:binding transport=http://schemas.xmlsoap.org/soap/http;
style=document/
wsdl:operation name=getPrice
soap:operation soapAction=urn:getPrice style=document/
wsdl:input
soap:header message=axis2:getPriceMessage
part=myHeaderMessagePart use=literal/
soap:body use=literal parts=part1
namespace=http://quickstart.samples//
/wsdl:input
etc
/wsdl:binding
Amila Suriarachchi wrote:
On Sat, Mar 8, 2008 at 3:39 AM, [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'm trying to use wsdl2java from the Axis2 v1.3 distribution to
generate soap headers, and import xml schemas via either jibx or
xmlbeans databinding. I've run into some limitations using
wsdl2java
and wanted to confirm my findings. All my tests used the
StockQuoteService wsdl provided in the quickstartjibx and
quickstartxmlbeans examples.
1) Test Results for more than one part element per message
element:
-jibx: obtained the following error.
Caused by: org.apache.axis2.AxisFault: message
{http://quickstart.samples/}myHeaderMessagehttp://quickstart.samples/%7DmyHeaderMessage
http://quickstart.samples/%7DmyHeaderMessage not found in the WSDL
-xmlbeans: obtained the following error.
Caused by:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
More than one part for message
getPriceMessage
This is because of the problem I mentioned earlier.
2) Test Results for Cirular imports in a wsdl, where xml schema A
imports schema B, which imports the original schema A:
-jibx: didn't try. xml schema is complicated.
-xmlbeans: Get 'Duplicate global element' Error.
Caused by: org.apache.xmlbeans.XmlException:
project://local/AlertInfrastructureTransactions.xsd:14:5: error:
sch-props
Re: AXIS2 wsdl2java limitations using jibx and xmlbeans databinding
Dennis, The wsdl works with ADB, with the exception of the 2 part declarations in a message declaration. I plan to enter a separte bug in JIRA for the jibx/soapheader, jibx/circular imports cases that you can look at (I'll provide the wsdl). And I plan to enter a separate JIRA bug for the xmlbeans circular imports case for the xmlbeans experts. Here are my results using ADB binding: Test Case 1: adb binding: 2 parts in a message. Results: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: More than one part for message getPriceMessage Test Case 2: adb binding: circular imports: Results: OK - NO ERRORS Retrieving schema wsdl:imported from '../../../schema/StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/quickstartadb/resources/META-INF/'. Retrieving schema at 'StockQuoteB.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteA.xsd'. Retrieving schema at 'StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteB.xsd'. Retrieving schema wsdl:imported from '../../../schema/StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/quickstartadb/resources/META-INF/'. Retrieving schema at 'StockQuoteB.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteA.xsd'. Retrieving schema at 'StockQuoteA.xsd', relative to 'file:/C:/swdev/wsproto/schema/StockQuoteB.xsd'. Test Case 3: soap header declaration: Results: OK - NO ERRORS Thanks, Jonathan Dennis Sosnoski wrote: Hi Jonathan, Since you didn't provide the modified WSDL it's difficult to say what's going wrong with this. Does your WSDL work with ADB? I gather you're using a header part, which probably has not been tested thoroughly. If you want to enter a Jira on this I'll take a look at the JiBX handling. - Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AXIS2 wsdl2java limitations using jibx and xmlbeans databinding
I'm trying to use wsdl2java from the Axis2 v1.3 distribution to
generate soap headers, and import xml schemas via either jibx or
xmlbeans databinding. I've run into some limitations using wsdl2java
and wanted to confirm my findings. All my tests used the
StockQuoteService wsdl provided in the quickstartjibx and
quickstartxmlbeans examples.
1) Test Results for more than one part element per message element:
-jibx: obtained the following error.
Caused by: org.apache.axis2.AxisFault: message
{http://quickstart.samples/}myHeaderMessage not found in the WSDL
-xmlbeans: obtained the following error.
Caused by:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: More than one part for message
getPriceMessage
2) Test Results for Cirular imports in a wsdl, where xml schema A
imports schema B, which imports the original schema A:
-jibx: didn't try. xml schema is complicated.
-xmlbeans: Get 'Duplicate global element' Error.
Caused by: org.apache.xmlbeans.XmlException:
project://local/AlertInfrastructureTransactions.xsd:14:5: error:
sch-props-correct.2: Duplicate global element:
[EMAIL PROTECTED] (Original global
element found in file: null)
3) Test Results for soap headers added to binding.
-jibx: Get mapping error when soap:header ... is added to binding.
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: No mapping defined for element
{http://quickstart.samples/xsd}myHeader
-xmlbeans: works, as long as there is a separate 1 part message for
the header.
Based on these findings, I plan to use xmlbeans databinding and pass
the xml documents as string parameters, then use xmlbeans to create
the binding objects in the invoked service method.
Has anyone run into the issues cited above or had different experiences?
Thanks,
Jonathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS2 wsdl2java limitations using jibx and xmlbeans databinding
Hi Jonathan,
Since you didn't provide the modified WSDL it's difficult to say what's
going wrong with this. Does your WSDL work with ADB?
I gather you're using a header part, which probably has not been tested
thoroughly. If you want to enter a Jira on this I'll take a look at the
JiBX handling.
- 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
[EMAIL PROTECTED] wrote:
I'm trying to use wsdl2java from the Axis2 v1.3 distribution to
generate soap headers, and import xml schemas via either jibx or
xmlbeans databinding. I've run into some limitations using wsdl2java
and wanted to confirm my findings. All my tests used the
StockQuoteService wsdl provided in the quickstartjibx and
quickstartxmlbeans examples.
1) Test Results for more than one part element per message element:
-jibx: obtained the following error.
Caused by: org.apache.axis2.AxisFault: message
{http://quickstart.samples/}myHeaderMessage not found in the WSDL
-xmlbeans: obtained the following error.
Caused by:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
More than one part for message getPriceMessage
2) Test Results for Cirular imports in a wsdl, where xml schema A
imports schema B, which imports the original schema A:
-jibx: didn't try. xml schema is complicated.
-xmlbeans: Get 'Duplicate global element' Error.
Caused by: org.apache.xmlbeans.XmlException:
project://local/AlertInfrastructureTransactions.xsd:14:5: error:
sch-props-correct.2: Duplicate global element:
[EMAIL PROTECTED] (Original global
element found in file: null)
3) Test Results for soap headers added to binding.
-jibx: Get mapping error when soap:header ... is added to binding.
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: No mapping defined for element
{http://quickstart.samples/xsd}myHeader
-xmlbeans: works, as long as there is a separate 1 part message for
the header.
Based on these findings, I plan to use xmlbeans databinding and pass
the xml documents as string parameters, then use xmlbeans to create
the binding objects in the invoked service method.
Has anyone run into the issues cited above or had different experiences?
Thanks,
Jonathan
-
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]
XMLBeans AXIS2 Responses
I'm working with a web service that someone else has designed and I have to host one or two operations. I'm using AXIS2 XMLBeans databindings. I've got one operation in my *skeleton class which returns a complex type. I've set the object up correctly in my skeleton class, and if you invoke the .xmlText method, you get correctly formatted XML and I can also get values correctly from the XMLBeans objects. The problem comes though when this is returned through AXIS to the client - the XML that gets returned has no data in it and simply contains the text unknown - but looking closer, it's an AxisFault that's returned not the response I expect. I've done some digging and found some options in the axis2.xml which gives me more details on the exception I'm getting. Would anyone be able to suggest what I need to do to fix this? Dumping the XML just prior to this exception shows and it all looks ok. xml-fragment xsi:nil=true xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;typ:CERS2EXTSYS_H azmat_Request_Ack xmlns:typ=urn:hazreq/typestyp:ack_msg CERSRefId=12736383783 StatusCode=Ok StatusMessage=Message Processed Succesfully!//typ:CERS2EXTSYS_Hazmat_Request_Ack/xml-fragment ?xml version='1.0' encoding='utf-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Body soapenv:Faultfaultcodesoapenv:Server/faultcodefaultstringunknown /faultstringdetailExceptionorg.apache.axis2.AxisFault#xd; at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)#xd; at com.mcpplc.destin8.cers.soap.EXTSYS2CERSServiceTxMessageReceiverInOut.in vokeBusinessLogic(EXTSYS2CERSServiceTxMessageReceiverInOut.java:599)#xd ; at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusine ssLogic(AbstractInOutSyncMessageReceiver.java:42)#xd; at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessa geReceiver.java:96)#xd; at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)#xd; at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques t(HTTPTransportUtils.java:275)#xd; at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120) #xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#xd; at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se rvletStubImpl.java:1077)#xd; at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl. java:465)#xd; at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl. java:348)#xd; at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r un(WebAppServletContext.java:7047)#xd; at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu bject.java:321)#xd; at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121 )#xd; at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl etContext.java:3902)#xd; at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl. java:2773)#xd; at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)#xd; at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)#xd; Caused by: org.apache.axiom.om.OMException#xd; at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:2 33)#xd; at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocu mentImpl.java:130)#xd; at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOM Builder.java:359)#xd; at com.mcpplc.destin8.cers.soap.EXTSYS2CERSServiceTxMessageReceiverInOut.to OM(EXTSYS2CERSServiceTxMessageReceiverInOut.java:947)#xd; at com.mcpplc.destin8.cers.soap.EXTSYS2CERSServiceTxMessageReceiverInOut.to Envelope(EXTSYS2CERSServiceTxMessageReceiverInOut.java:1522)#xd; at com.mcpplc.destin8.cers.soap.EXTSYS2CERSServiceTxMessageReceiverInOut.in vokeBusinessLogic(EXTSYS2CERSServiceTxMessageReceiverInOut.java:208)#xd ; ... 17 more#xd; /Exception/detail/soapenv:Fault/soapenv:Body/soapenv:Envelope ]
XmlBeans version with Axis 1.3?
Hi, What version of XmlBeans does Axis2 1.3 use? When following the samples, I noticed that using the -d xmlbeans option in the Ant task generates some org.xmlsoap.schemas.* artifacts which I'm not sure if they are used by Axis2 or XmlBeans. XmlBeans 2.2.0 doesn't have these artifacts. Aloha, -Vinh
RE: XmlBeans version with Axis 1.3?
Sorry, looks like I found the answer to my question. From the file name xbeans-2.2.0.jar, I can see XmlBeans 2.2.0 is still being used. From: Vinh Nguyen (vinguye2) Sent: Tuesday, February 05, 2008 10:57 AM To: axis-user@ws.apache.org Subject: XmlBeans version with Axis 1.3? Hi, What version of XmlBeans does Axis2 1.3 use? When following the samples, I noticed that using the -d xmlbeans option in the Ant task generates some org.xmlsoap.schemas.* artifacts which I'm not sure if they are used by Axis2 or XmlBeans. XmlBeans 2.2.0 doesn't have these artifacts. Aloha, -Vinh
XMLBeans with Axis2 - getter methods
Hi Axis Users, I'm currently using Axis2 with xmlbeans as my databinding. I have a wsdl file from a company providing a web service that I want to use. I use ant wsgen to generate the source files from the wsdl schema and then I compile my java files to a jar. I can build Document types and ResponseDocument types and I can invoke the methods on the stub. I see my SOAP message going out over the wire - and I see the response message returning (using wireshark). However - when I try to access the data in the nodes using for example: XResponseDocument.getResponse().getResult().getArray(); - where getArray - should return an array of Items - I originally couldn't access anything of type Array - I altered the wsdl - so that soapenc:Array types were replaced by sequences - and regenerated and it seems to work now - however - now when I try and access the values in the Items (which have an id (int), value(string) and a code(string) ) - I get null. - I am using the jar file: axis2-xmlbeans-1.1.1.jar -- I don't know the entire history of the project - however I see that the latest version of xmlbeans is 2.3. - so my next step is to try the latest version of xmlbeans. - however - if there are any known issues with this configuration (where would I find a list like that?) - or you could make any recommendations - they would be greatly appreciated. Best regards, David -- David Swensen Software Entwickler. freiheit.com technologies gmbh Straßenbahnring 22 / 20251 Hamburg, Germany fon +49 (0)40 / 890584-0 fax +49 (0)40 / 890584-20 HRB Hamburg 70814 86F7 0928 CFE3 8953 3652 71E3 202B AFEA 84DE 850B Geschäftsführer: Claudia Dietze, Stefan Richter, Jörg Kirchhof - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLBeans with Axis2 - getter methods
Hi Robert, Thanks for your quick response. We are using Axis2 1.1.1 So the upgrade is definately an option. I've had a closer look and we are using xmlbeans 2.2.0 (my bad!) Thanks for the info - we'll try and see. Best regards, David On Do, 2007-11-29 at 13:44 -0500, robert lazarski wrote: What version of axis2 are you using - try upgrading to 1.3 if you are not running that already - you may be running into what may be an old bug. soapenc:Array is not supported by axis2 AFAIK - I'm surprised wsdl2java ran without any errors even on xmlbeans. There's some talk of supporting soapenc in the next release, but I'm not sure what the state of that is. IIRC xmlbeans is 2.3 is now what's in svn or perhaps easier a nightly build. HTH, Robert On Nov 29, 2007 1:06 PM, David Swensen [EMAIL PROTECTED] wrote: Hi Axis Users, I'm currently using Axis2 with xmlbeans as my databinding. I have a wsdl file from a company providing a web service that I want to use. I use ant wsgen to generate the source files from the wsdl schema and then I compile my java files to a jar. I can build Document types and ResponseDocument types and I can invoke the methods on the stub. I see my SOAP message going out over the wire - and I see the response message returning (using wireshark). However - when I try to access the data in the nodes using for example: XResponseDocument.getResponse().getResult().getArray(); - where getArray - should return an array of Items - I originally couldn't access anything of type Array - I altered the wsdl - so that soapenc:Array types were replaced by sequences - and regenerated and it seems to work now - however - now when I try and access the values in the Items (which have an id (int), value(string) and a code(string) ) - I get null. - I am using the jar file: axis2-xmlbeans-1.1.1.jar -- I don't know the entire history of the project - however I see that the latest version of xmlbeans is 2.3. - so my next step is to try the latest version of xmlbeans. - however - if there are any known issues with this configuration (where would I find a list like that?) - or you could make any recommendations - they would be greatly appreciated. Best regards, David -- David Swensen Software Entwickler. freiheit.com technologies gmbh Straßenbahnring 22 / 20251 Hamburg, Germany fon +49 (0)40 / 890584-0 fax +49 (0)40 / 890584-20 HRB Hamburg 70814 86F7 0928 CFE3 8953 3652 71E3 202B AFEA 84DE 850B Geschäftsführer: Claudia Dietze, Stefan Richter, Jörg Kirchhof - 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] -- David Swensen Software Entwickler. freiheit.com technologies gmbh Straßenbahnring 22 / 20251 Hamburg, Germany fon +49 (0)40 / 890584-0 fax +49 (0)40 / 890584-20 HRB Hamburg 70814 86F7 0928 CFE3 8953 3652 71E3 202B AFEA 84DE 850B Geschäftsführer: Claudia Dietze, Stefan Richter, Jörg Kirchhof - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLBeans with Axis2 - getter methods
What version of axis2 are you using - try upgrading to 1.3 if you are not running that already - you may be running into what may be an old bug. soapenc:Array is not supported by axis2 AFAIK - I'm surprised wsdl2java ran without any errors even on xmlbeans. There's some talk of supporting soapenc in the next release, but I'm not sure what the state of that is. IIRC xmlbeans is 2.3 is now what's in svn or perhaps easier a nightly build. HTH, Robert On Nov 29, 2007 1:06 PM, David Swensen [EMAIL PROTECTED] wrote: Hi Axis Users, I'm currently using Axis2 with xmlbeans as my databinding. I have a wsdl file from a company providing a web service that I want to use. I use ant wsgen to generate the source files from the wsdl schema and then I compile my java files to a jar. I can build Document types and ResponseDocument types and I can invoke the methods on the stub. I see my SOAP message going out over the wire - and I see the response message returning (using wireshark). However - when I try to access the data in the nodes using for example: XResponseDocument.getResponse().getResult().getArray(); - where getArray - should return an array of Items - I originally couldn't access anything of type Array - I altered the wsdl - so that soapenc:Array types were replaced by sequences - and regenerated and it seems to work now - however - now when I try and access the values in the Items (which have an id (int), value(string) and a code(string) ) - I get null. - I am using the jar file: axis2-xmlbeans-1.1.1.jar -- I don't know the entire history of the project - however I see that the latest version of xmlbeans is 2.3. - so my next step is to try the latest version of xmlbeans. - however - if there are any known issues with this configuration (where would I find a list like that?) - or you could make any recommendations - they would be greatly appreciated. Best regards, David -- David Swensen Software Entwickler. freiheit.com technologies gmbh Straßenbahnring 22 / 20251 Hamburg, Germany fon +49 (0)40 / 890584-0 fax +49 (0)40 / 890584-20 HRB Hamburg 70814 86F7 0928 CFE3 8953 3652 71E3 202B AFEA 84DE 850B Geschäftsführer: Claudia Dietze, Stefan Richter, Jörg Kirchhof - 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: Axis2C: WSDL2C with xmlbeans databinding generates Java files
there is no xmlbeans databinding available for c. The only databindng available for c is ADB (default). Please report this to http://ws.apache.org/axis2/c/ thanks, Amila. On Nov 20, 2007 12:21 AM, Lingjia Yang [EMAIL PROTECTED] wrote: Hi, I am trying to use WSDL2C (from axis2-1.3) to generate client stubs with xmlbeans databinding. I started with the simple wsdl in axis2c-src-1.1.0\samples\codegen\databinding\Calculator.wsdl. $ ~/tools/axis2/axis2-1.3/bin/axis2.sh org.apache.axis2.wsdl.WSDL2C -uri Calcul ator.wsdl -d xmlbeans It created 2 directories: src and resources. In the src directory, it only has 2 C files: axis2_stub_Calculator.c axis2_stub_Calculator.h. The axis2_stub_Calculator.h includes files that are not generated. #include adb_localhost.axis.calculator.DivResponseDocument.h #include adb_localhost.axis.calculator.DivDocument.h #include adb_localhost.axis.calculator.MulResponseDocument.h #include adb_localhost.axis.calculator.MulDocument.h #include adb_localhost.axis.calculator.AddResponseDocument.h #include adb_localhost.axis.calculator.AddDocument.h #include adb_localhost.axis.calculator.SubResponseDocument.h #include adb_localhost.axis.calculator.SubDocument.h All the files under 'localhost' and 'org' directroies are java files. I tried to specify the language using '-l c' but it didn't help. I have also tried with '-d adb -u' and the code generator works fine. Thanks in advance for the help! Lingjia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
