Does axis2-java2wsdl-maven-plugin work (with Axis2 1.5)?
I am trying to get the java2wsdl Maven plugin to work with no luck. Does anyone have this plugin working? I am using Axis2 1.5 and when I run mvn axis2-java2wsdl:java2wsdl I get a NullPointerException. Can anyone offer some help? Thanks! dave from my pom.xml: plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-java2wsdl-maven-plugin/artifactId executions execution goals goaljava2wsdl/goal /goals /execution /executions configuration classNamecom.full.class.path.Service/className /configuration /plugin
axis2-java2wsdl-maven-plugin for multiple classes
Hi, I need to generate WSDL for multiple classes. Can anyone tell me how to do this with axis2-java2wsdl-maven-plugin. Also, is it possible to generate only a single WSDL file for all the classes rather than having a WSDL file per Class. I am stuck with this problem, any inputs that'll help me proceed will be greatly appreciated. Thanks, Soumya This message (including attachment if any) is confidential and may be privileged. If you have received this message by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. E-mail may contain viruses. Before opening attachments please check them for viruses and defects. While MindTree Limited (MindTree) has put in place checks to minimize the risks, MindTree will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission. MindTree reserves the right to monitor and review the content of all messages sent to or from MindTree e-mail address. Messages sent to or from this e-mail address may be stored on the MindTree e-mail system or else where.
RE: axis2-java2wsdl-maven-plugin for multiple classes
Please reply. Its urgent. From: Soumya S. Hameed Sent: Thursday, November 13, 2008 2:48 PM To: 'axis-user@ws.apache.org' Subject: axis2-java2wsdl-maven-plugin for multiple classes Hi, I need to generate WSDL for multiple classes. Can anyone tell me how to do this with axis2-java2wsdl-maven-plugin. Also, is it possible to generate only a single WSDL file for all the classes rather than having a WSDL file per Class. I am stuck with this problem, any inputs that'll help me proceed will be greatly appreciated. Thanks, Soumya This message (including attachment if any) is confidential and may be privileged. If you have received this message by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. E-mail may contain viruses. Before opening attachments please check them for viruses and defects. While MindTree Limited (MindTree) has put in place checks to minimize the risks, MindTree will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission. MindTree reserves the right to monitor and review the content of all messages sent to or from MindTree e-mail address. Messages sent to or from this e-mail address may be stored on the MindTree e-mail system or else where.
Re: Axis2- Java2Wsdl- ClassnotFoundException
Thanks Moez. That worked. Sanjeev. Moez Benmbarka wrote: Hi, I think you just need to add E:\Axis2c\bin to the CLASSPATH variable or use the fllowing command : java2wsdl.bat -cp E:\Axis2c\bin -cn pkg.Test Regards Moez BM SanjeevGour wrote: Hi, I am trying to generate WSDL using the java2wsdl.bat using the following command- java2wsdl.bat -cn pkg.Test Where my Test class is under the package pkg. I have axis installed in E:\Axis2c. I have put the generated class file in the E:\Axis2c\bin directory under a folder pkg. i.e.- E:\Axis2c\bin\pkg\Test.class. Now when I run the above command I get the exception-Exception in thread main java.lang.ClassNotFoundException: pkg.Test I execute the command from E:\Axis2c\bin directory. Though my test class doesn't contain any special code, I just wonder why I get the ClassNotFounfException. My Test class does not refer to any other class. It just has a main method with one SOP. I have set the AXIS2_HOME env variable and classpath contains entry for my rt.jar. Can somebody please guide me on this? Thank you, Sanjeev Gour. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Axis2--Java2Wsdl--ClassnotFoundException-tp18848964p18867541.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: Build Error using axis2-java2wsdl-maven-plugin
Hi Kyle, Did u find the solution i am also facing the same problem Thanks Venkat -- View this message in context: http://www.nabble.com/Build-Error-using-axis2-java2wsdl-maven-plugin-tp14199743p18873227.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: Build Error using axis2-java2wsdl-maven-plugin
I did not figure out a solution to the problem. In the long run we ended up using Apache CXF. Not sure if this is an option for you but the Maven plugin support is far better then that of Axis2. -Kyle venkuk wrote: Hi Kyle, Did u find the solution i am also facing the same problem Thanks Venkat -- View this message in context: http://www.nabble.com/Build-Error-using-axis2-java2wsdl-maven-plugin-tp14199743p18873358.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: Build Error using axis2-java2wsdl-maven-plugin
Hi Kyle, Thanks for your info about the Apache CXF. :clap: Kyle.Bober wrote: I did not figure out a solution to the problem. In the long run we ended up using Apache CXF. Not sure if this is an option for you but the Maven plugin support is far better then that of Axis2. -Kyle venkuk wrote: Hi Kyle, Did u find the solution i am also facing the same problem Thanks Venkat -- View this message in context: http://www.nabble.com/Build-Error-using-axis2-java2wsdl-maven-plugin-tp14199743p18878176.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]
Axis2- Java2Wsdl- ClassnotFoundException
Hi, I am trying to generate WSDL using the java2wsdl.bat using the following command- java2wsdl.bat -cn pkg.Test Where my Test class is under the package pkg. I have axis installed in E:\Axis2c. I have put the generated class file in the E:\Axis2c\bin directory under a folder pkg. i.e.- E:\Axis2c\bin\pkg\Test.class. Now when I run the above command I get the exception-Exception in thread main java.lang.ClassNotFoundException: pkg.Test I execute the command from E:\Axis2c\bin directory. Though my test class doesn't contain any special code, I just wonder why I get the ClassNotFounfException. My Test class does not refer to any other class. It just has a main method with one SOP. I have set the AXIS2_HOME env variable and classpath contains entry for my rt.jar. Can somebody please guide me on this? Thank you, Sanjeev Gour. -- View this message in context: http://www.nabble.com/Axis2--Java2Wsdl--ClassnotFoundException-tp18848964p18848964.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- Java2Wsdl- ClassnotFoundException
Hi, I think you just need to add E:\Axis2c\bin to the CLASSPATH variable or use the fllowing command : java2wsdl.bat -cp E:\Axis2c\bin -cn pkg.Test Regards Moez BM SanjeevGour wrote: Hi, I am trying to generate WSDL using the java2wsdl.bat using the following command- java2wsdl.bat -cn pkg.Test Where my Test class is under the package pkg. I have axis installed in E:\Axis2c. I have put the generated class file in the E:\Axis2c\bin directory under a folder pkg. i.e.- E:\Axis2c\bin\pkg\Test.class. Now when I run the above command I get the exception-Exception in thread main java.lang.ClassNotFoundException: pkg.Test I execute the command from E:\Axis2c\bin directory. Though my test class doesn't contain any special code, I just wonder why I get the ClassNotFounfException. My Test class does not refer to any other class. It just has a main method with one SOP. I have set the AXIS2_HOME env variable and classpath contains entry for my rt.jar. Can somebody please guide me on this? Thank you, Sanjeev Gour. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] java2wsdl - missing enum
Hi folks,
I am generating my WSDL from java using ?wsdl in the browser for my web
service. I am using Axis2 1.4 and running on Tomcat 5.5.26.
I have a single class as a parameter for one of the methods of the
webservice. One of the variables in that class is of the type below.
@XmlType(name = DataEncodingType)
@XmlEnum
public enum DataEncodingType {
RAW(RAW),
HEX(HEX),
@XmlEnumValue(BASE64)
BASE_64(BASE64);
private final String value;
DataEncodingType(String v) {
value = v;
}
public String value() {
return value;
}
public static DataEncodingType fromValue(String v) {
for (DataEncodingType c: DataEncodingType.values()) {
if (c.value.equals(v)) {
return c;
}
}
throw new IllegalArgumentException(v);
}
}
As you can see, this is a JAXB generated emum class.
But when I generate the WSDL, the complex type that represents this
class, looks like this:
xs:complexType name=DataEncodingType
xs:complexContent
xs:extension base=xs:Enum
xs:sequence/
/xs:extension
/xs:complexContent
/xs:complexType
This is not correct as i am expecting to see the enum values represented
in the class above, present in the complexType.
Can somebody please let me know how to fix this? This used to work a
while back, but for some reason, this isn't working anymore.
Hope to hear from you
~Glen
[axis2] java2wsdl - missing enum
Hi folks,
I am generating my WSDL from java using ?wsdl in the browser for my web
service. I am using Axis2 1.4 and running on Tomcat 5.5.26.
I have a single class as a parameter for one of the methods of the
webservice. One of the variables in that class is of the type below.
@XmlType(name = DataEncodingType)
@XmlEnum
public enum DataEncodingType {
RAW(RAW),
HEX(HEX),
@XmlEnumValue(BASE64)
BASE_64(BASE64);
private final String value;
DataEncodingType(String v) {
value = v;
}
public String value() {
return value;
}
public static DataEncodingType fromValue(String v) {
for (DataEncodingType c: DataEncodingType.values()) {
if (c.value.equals(v)) {
return c;
}
}
throw new IllegalArgumentException(v);
}
}
As you can see, this is a JAXB generated class.
But when I generate the WSDL, the complex type that represents this
class, looks like this:
xs:complexType name=DataEncodingType
xs:complexContent
xs:extension base=xs:Enum
xs:sequence/
/xs:extension
/xs:complexContent
/xs:complexType
This is not correct as i am expecting to see the enum values represented
in the class above, present in the complexType.
Can somebody please let me know how to fix this? This used to work a
while back, but for some reason, this isn't working anymore.
Hope to hear from you
~Glen
Axis2 - Java2WSDL
Hi I have a list of extra classes for which I need to generate WSDL types definition. The org.apache.ws.java2wsdl.Java2WSDL class takes an option -xc class1 -xc class2 . . The problem is that I have a list of classes, which I need to process. In Axis 1 I had the -extraClasses option which could take the list of classes. -extraClasses class1,class2, Please let me know if I have a better option. Thanks Pradeep
Is the axis2 java2WSDL application able to generate wsdl 2.0 output?
Is the axis2 java2WSDL application able to generate wsdl 2.0 output? Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
Re: Is the axis2 java2WSDL application able to generate wsdl 2.0 output?
java2wsdl -wv versionWSDL Version. Valid Options : 2, 2.0, 1.1 - Original Message - From: Jane Allen To: axis-user@ws.apache.org Sent: Thursday, December 27, 2007 4:52 PM Subject: Is the axis2 java2WSDL application able to generate wsdl 2.0 output? Is the axis2 java2WSDL application able to generate wsdl 2.0 output? -- Looking for last minute shopping deals? Find them fast with Yahoo! Search.
Re: [Axis2] Java2WSDL with JAX-WS and JAXB annotations
Thanks Dennis, I'll take a look at that as well, that may be our only choice. I guess at the end of the day, I'm looking to see how I can exclude certain types from being generated in the WSDL. Using @XmlTransient alone doesn't do it. In Axis 1.4 I could take advantage of the org.apache.axis.wsdl.fromJava.Types.getStopClasses() List, so I'm wondering if there is similar functionality to utilize in the Axis2 infrastructure? Ben On 12/20/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: Hi Ben, You may have better luck using Jibx2Wsdl: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/jibx2wsdl You can also see the article at http://www.infoq.com/articles/sosnoski-code-first discussing code first approaches in general, and Jibx2Wsdl in particular. Jibx2Wsdl handles a wider range of inputs than Java2WSDL, and also supports customizations to change the default generation process. You may find that using the generated JiBX data binding also gives you a way to easily use your existing data classes with Axis2. I'll see about adding some links on this to the download documentation for Axis2 1.4. There doesn't seem to be much point in recommending people use Java2WSDL when there are many known limitations, and Jibx2Wsdl does a better job all around. I'll also try to get the documentation finished and a formal release of Jibx2Wsdl soon. - Dennis -- Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Ben Reif wrote: Duncan, Thanks for the input. We're trying to incorporate the WSDL generation into another automated process, so manually generating it with the NetBeans IDE probably won't work for us. I have however, tried using the WsGen tool as well, and I noticed a different problem, the generated WSDL didn't indicate that the operations threw any Faults at all. They were missing from the WSDL completely. Does anyone else have any other thoughts or ideas? Ben On 12/20/07, *Thomson, Duncan* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: -Original Message- From: Ben Reif [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 18, 2007 5:34 PM To: axis-user@ws.apache.org mailto:axis-user@ws.apache.org Subject: [Axis2] Java2WSDL with JAX-WS and JAXB annotations Hi, As I understand it, now the best way to re-use your existing code is to use the JAX-WS and JAXB annotations and then run your code through the Axis2 Java2WSDL utility passing in the -sg argument with the value org.apache.axis2.jaxbri.JaxbSchemaGenerator. in theory should be portable to other platforms and tools as well. FYI, Netbeans has very nice JAX-WS and JAXB support, and does a very nice job of annotation processing. Note that if you use this you don't need Axis at all - instead of Java2WSDL the Netbeans IDE uses a different set of tools - wsgen and wsimport, if I remember correctly. You can also launch these tools directly yourself, and perhaps they are available within other IDEs, I'm not sure. Anyway, the point is, as far as I can tell, with these tools, there's really no need for Axis2. Perhaps someone else will explain why it's needed, but I don't see it. Duncan - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Java2WSDL with JAX-WS and JAXB annotations
-Original Message- From: Ben Reif [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 18, 2007 5:34 PM To: axis-user@ws.apache.org Subject: [Axis2] Java2WSDL with JAX-WS and JAXB annotations Hi, As I understand it, now the best way to re-use your existing code is to use the JAX-WS and JAXB annotations and then run your code through the Axis2 Java2WSDL utility passing in the -sg argument with the value org.apache.axis2.jaxbri.JaxbSchemaGenerator. in theory should be portable to other platforms and tools as well. FYI, Netbeans has very nice JAX-WS and JAXB support, and does a very nice job of annotation processing. Note that if you use this you don't need Axis at all - instead of Java2WSDL the Netbeans IDE uses a different set of tools - wsgen and wsimport, if I remember correctly. You can also launch these tools directly yourself, and perhaps they are available within other IDEs, I'm not sure. Anyway, the point is, as far as I can tell, with these tools, there's really no need for Axis2. Perhaps someone else will explain why it's needed, but I don't see it. Duncan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Java2WSDL with JAX-WS and JAXB annotations
Duncan, Thanks for the input. We're trying to incorporate the WSDL generation into another automated process, so manually generating it with the NetBeans IDE probably won't work for us. I have however, tried using the WsGen tool as well, and I noticed a different problem, the generated WSDL didn't indicate that the operations threw any Faults at all. They were missing from the WSDL completely. Does anyone else have any other thoughts or ideas? Ben On 12/20/07, Thomson, Duncan [EMAIL PROTECTED] wrote: -Original Message- From: Ben Reif [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 18, 2007 5:34 PM To: axis-user@ws.apache.org Subject: [Axis2] Java2WSDL with JAX-WS and JAXB annotations Hi, As I understand it, now the best way to re-use your existing code is to use the JAX-WS and JAXB annotations and then run your code through the Axis2 Java2WSDL utility passing in the -sg argument with the value org.apache.axis2.jaxbri.JaxbSchemaGenerator. in theory should be portable to other platforms and tools as well. FYI, Netbeans has very nice JAX-WS and JAXB support, and does a very nice job of annotation processing. Note that if you use this you don't need Axis at all - instead of Java2WSDL the Netbeans IDE uses a different set of tools - wsgen and wsimport, if I remember correctly. You can also launch these tools directly yourself, and perhaps they are available within other IDEs, I'm not sure. Anyway, the point is, as far as I can tell, with these tools, there's really no need for Axis2. Perhaps someone else will explain why it's needed, but I don't see it. Duncan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Java2WSDL with JAX-WS and JAXB annotations
Hi Ben, You may have better luck using Jibx2Wsdl: http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/jibx2wsdl You can also see the article at http://www.infoq.com/articles/sosnoski-code-first discussing code first approaches in general, and Jibx2Wsdl in particular. Jibx2Wsdl handles a wider range of inputs than Java2WSDL, and also supports customizations to change the default generation process. You may find that using the generated JiBX data binding also gives you a way to easily use your existing data classes with Axis2. I'll see about adding some links on this to the download documentation for Axis2 1.4. There doesn't seem to be much point in recommending people use Java2WSDL when there are many known limitations, and Jibx2Wsdl does a better job all around. I'll also try to get the documentation finished and a formal release of Jibx2Wsdl soon. - Dennis -- Dennis M. Sosnoski SOA and Web Services in Java Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Ben Reif wrote: Duncan, Thanks for the input. We're trying to incorporate the WSDL generation into another automated process, so manually generating it with the NetBeans IDE probably won't work for us. I have however, tried using the WsGen tool as well, and I noticed a different problem, the generated WSDL didn't indicate that the operations threw any Faults at all. They were missing from the WSDL completely. Does anyone else have any other thoughts or ideas? Ben On 12/20/07, *Thomson, Duncan* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: -Original Message- From: Ben Reif [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 18, 2007 5:34 PM To: axis-user@ws.apache.org mailto:axis-user@ws.apache.org Subject: [Axis2] Java2WSDL with JAX-WS and JAXB annotations Hi, As I understand it, now the best way to re-use your existing code is to use the JAX-WS and JAXB annotations and then run your code through the Axis2 Java2WSDL utility passing in the -sg argument with the value org.apache.axis2.jaxbri.JaxbSchemaGenerator. in theory should be portable to other platforms and tools as well. FYI, Netbeans has very nice JAX-WS and JAXB support, and does a very nice job of annotation processing. Note that if you use this you don't need Axis at all - instead of Java2WSDL the Netbeans IDE uses a different set of tools - wsgen and wsimport, if I remember correctly. You can also launch these tools directly yourself, and perhaps they are available within other IDEs, I'm not sure. Anyway, the point is, as far as I can tell, with these tools, there's really no need for Axis2. Perhaps someone else will explain why it's needed, but I don't see it. Duncan - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Java2WSDL with JAX-WS and JAXB annotations
Hi, I have a question about generating WSDL and Schema in Axis2. We have been using Axis 1.4 for quite some time now and are finally ready to upgrade to Axis2. I've read that a lot of people suggest starting with the WSDL, but unfortunately we have a lot of existing Web Services and custom data object (not quite JavaBean compatible) that we are hoping to re-use. Previously we would define typeMapping tags in the server-config.xml and then implement the writeSchema() method on a custom Serializer class to generate out the correct Schema for the WSDL when we use the Java2WSDL utility. As I understand it, now the best way to re-use your existing code is to use the JAX-WS and JAXB annotations and then run your code through the Axis2 Java2WSDL utility passing in the -sg argument with the value org.apache.axis2.jaxbri.JaxbSchemaGenerator. I *think* I read that you *may * be able to use JiBX, but we prefer JAX-WS and JAXB because they are standards and in theory should be portable to other platforms and tools as well. Anyway, my Web Service throws a custom Fault that extends org.apache.axis2.AxisFault. So I've gone through and annotated all the classes (including the custom Fault class), but when I run Java2WSDL I get the exception below because it's trying to write the schema for the AxisFault and it's super classes which aren't JAXB compliant: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 8 counts of IllegalAnnotationExceptions org.apache.axis2.AxisFault does not have a no-arg default constructor. this problem is related to the following location: at org.apache.axis2.AxisFault at com.ams.core.webservices.exceptions.BaseFault at com.ams.core.webservices.exceptions.RecoverableFault org.apache.axiom.om.OMElement is an interface, and JAXB can't handle interfaces. this problem is related to the following location: at org.apache.axiom.om.OMElement at public org.apache.axiom.om.OMElement org.apache.axis2.AxisFault.getDetail() at org.apache.axis2.AxisFault at com.ams.core.webservices.exceptions.BaseFault at com.ams.core.webservices.exceptions.RecoverableFault org.apache.axiom.om.OMElement does not have a no-arg default constructor. this problem is related to the following location: at org.apache.axiom.om.OMElement at public org.apache.axiom.om.OMElement org.apache.axis2.AxisFault.getDetail() at org.apache.axis2.AxisFault at com.ams.core.webservices.exceptions.BaseFault at com.ams.core.webservices.exceptions.RecoverableFault org.apache.axiom.om.OMXMLParserWrapper is an interface, and JAXB can't handle interfaces. this problem is related to the following location: at org.apache.axiom.om.OMXMLParserWrapper at public abstract org.apache.axiom.om.OMXMLParserWrapper org.apache.axiom.om.OMElement.getBuilder() at org.apache.axiom.om.OMElement at public org.apache.axiom.om.OMElement org.apache.axis2.AxisFault.getDetail() at org.apache.axis2.AxisFault at com.ams.core.webservices.exceptions.BaseFault at com.ams.core.webservices.exceptions.RecoverableFault .. My question is, how do you get Java2WSDL or JAXB to ignore Java classes or certain other classes in the Object hierarchy? I tried to put the JAXB 2.1.5jars in the classpath and use the @XmlTransient annotation at the class level by putting a base class in between AxisFault and my custom Fault, but that didn't seem to work either. I would think that this would cause a problem when generating WSDL/Schema for any class that extends certain other classes. Has anyone done this before or have any ideas on how to get around this? I have one last question. Sun's com.sun.tools.ws.WsGen utility from their JAX-WS Reference Implementation generates the WSDL and Schema so that they are broken out into seperate files (WSDL Service/Bindings, WSDL Message and PortTypes, and then a seperate xsd file to define all of the types for a given namespace. Is there any way to get the Axis2 Java2WSDL classes to do this, or does anyone know what I should extend to get this to happen? Thanks in advance, Ben
Build Error using axis2-java2wsdl-maven-plugin
I keep trying to generate a WSDL using the Axis2 Maven plug in but keep receiving the following error upon execution: [DEBUG] Configuring mojo 'org.apache.axis2.maven2:axis2-java2wsdl-maven-plugin:1.1:java2wsdl' -- [DEBUG] (f) className = com.agfa.websend.services.axis2.ws.RegisterUserWS [DEBUG] (f) outputFileName = C:\Projects\AGFA\WebSend\websend-jee-application\websend-webservices-axis2-server\target\classes/generated-resources/ va2wsdl/service.xml [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [axis2-java2wsdl:java2wsdl] java.lang.Exception: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.resolveOutputStream(Java2WSDLCodegenEngine.java:93) at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.init(Java2WSDLCodegenEngine.java:47) at org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo.java:146) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.createNewFile(File.java:883) at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.resolveOutputStream(Java2WSDLCodegenEngine.java:89) ... 20 more [INFO] [ERROR] BUILD ERROR [INFO] [INFO] java.io.IOException: The filename, directory name, or volume label syntax is incorrect [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused
axis2 java2wsdl ant task
Hello, Is there a way to generate a webservice from a java class using an ant task? I couldn't find nice documentation about that :( thanks, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 java2wsdl ant task
There's a maven plugin though. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.test/groupId artifactIdhello/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namehello/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-java2wsdl-maven-plugin/artifactId configuration classNamecom.foo.myservice.MyHandler/className /configuration executions execution goals goaljava2wsdl/goal /goals /execution /executions /plugin /plugins /build /project Or you can call the AXIS2_HOME/bin/java2wsdl.sh command line program using an Ant java / task You can also deploy a Java class as a web service directly. Check this link http://ws.apache.org/axis2/1_3/pojoguide.html Upul On Nov 16, 2007 1:26 PM, Simon Steinacker [EMAIL PROTECTED] wrote: Hello, Is there a way to generate a webservice from a java class using an ant task? I couldn't find nice documentation about that :( thanks, Simon - 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] java2wsdl maven2 plugin problems
I'm having the exact same problem. Has anyone come up with a solution? On Feb 21, 2007, at 4:36 PM, Scot Hale wrote: Hi all, I am trying to use the maven java2wsdl 1.1 plugin, and I have run into several problems. I am using maven 2.0.5, java 5, and Linux Ubuntu 6.10. 1.) Documentation: The example snippet on http://ws.apache.org/axis2/tools/1_1/maven-plugins/maven-java2wsdl- plugin.html is wrong and won't work. This part: /execution configuration classNamecom.foo.myservice.MyHandler/className /configuration /executions /plugin /plugins /build Should be /execution /executions configuration classNamecom.foo.myservice.MyHandler/className /configuration /plugin /plugins /build 2.) Documentation: The example command doesn't work (on the same page). mvn java2wsdl:java2wsdl Should be mvn axis-java2wsdl:java2wsdl 3.) Strangly, a directory gets created in my maven project called home. I think this might be causing other issues as well. It looks like it is taking the full path to my project (for example /home/scot/src/webservice/ ) and lopping off the first /, then creating a new directory ( for example /home/scot/src/webservice/home/scot/src/webservice/target/... ). 4.) When I run the plugin it can't find a class that exists in the standard maven2 directory src/main/java/ ( for example src/main/java/com/DummyHandler.java ). I noticed someone else complained about this on January 22nd, but I didn't see a reply to his post to the mailing list. java.lang.Exception: java.lang.ClassNotFoundException: com.DummyHandler at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.generate (Java2WSDLCodegenEngine.java:58) at org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute (Java2WSDLMojo.java:146) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG oal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.ClassNotFoundException: com.DummyHandler at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect (RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:274) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass (RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java: 319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.apache.ws.java2wsdl.Java2WSDLUtils.namespaceFromClassName (Java2WSDLUtils.java:63) at org.apache.ws.java2wsdl.Java2WSDLUtils.schemaNamespaceFromClassName (Java2WSDLUtils.java:82) at org.apache.ws.java2wsdl.Java2WSDLBuilder.getSchemaTargetNamespace (Java2WSDLBuilder.java:56) at org.apache.ws.java2wsdl.Java2WSDLBuilder.generateWSDL (Java2WSDLBuilder.java:152) at
Re: [AXIS2] java2wsdl maven2 plugin problems
Jared, Scot, Is there a JIRA for it? can you please create one as i don't remember seeing one for this. thanks, dims On 5/15/07, Jared Blitzstein [EMAIL PROTECTED] wrote: I'm having the exact same problem. Has anyone come up with a solution? On Feb 21, 2007, at 4:36 PM, Scot Hale wrote: Hi all, I am trying to use the maven java2wsdl 1.1 plugin, and I have run into several problems. I am using maven 2.0.5, java 5, and Linux Ubuntu 6.10. 1.) Documentation: The example snippet on http://ws.apache.org/axis2/tools/1_1/maven-plugins/maven-java2wsdl- plugin.html is wrong and won't work. This part: /execution configuration classNamecom.foo.myservice.MyHandler/className /configuration /executions /plugin /plugins /build Should be /execution /executions configuration classNamecom.foo.myservice.MyHandler/className /configuration /plugin /plugins /build 2.) Documentation: The example command doesn't work (on the same page). mvn java2wsdl:java2wsdl Should be mvn axis-java2wsdl:java2wsdl 3.) Strangly, a directory gets created in my maven project called home. I think this might be causing other issues as well. It looks like it is taking the full path to my project (for example /home/scot/src/webservice/ ) and lopping off the first /, then creating a new directory ( for example /home/scot/src/webservice/home/scot/src/webservice/target/... ). 4.) When I run the plugin it can't find a class that exists in the standard maven2 directory src/main/java/ ( for example src/main/java/com/DummyHandler.java ). I noticed someone else complained about this on January 22nd, but I didn't see a reply to his post to the mailing list. java.lang.Exception: java.lang.ClassNotFoundException: com.DummyHandler at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.generate (Java2WSDLCodegenEngine.java:58) at org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute (Java2WSDLMojo.java:146) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG oal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.ClassNotFoundException: com.DummyHandler at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect (RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:274) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass (RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java: 319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.apache.ws.java2wsdl.Java2WSDLUtils.namespaceFromClassName (Java2WSDLUtils.java:63) at org.apache.ws.java2wsdl.Java2WSDLUtils.schemaNamespaceFromClassName (Java2WSDLUtils.java:82) at
Trouble in using the axis2-java2wsdl-maven-plugin
Hi, I have a pom file which includes the following plugin declaration. plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-java2wsdl-maven-plugin/artifactId executions execution goals goaljava2wsdl/goal /goals /execution /executions configuration classNamecom.mycompany.MyService/className /configuration /plugin I execute this as: mvn java2wsdl:java2wsdl [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'java2wsdl'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-java2wsdl-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Mar 20 21:15:32 PDT 2007 [INFO] Final Memory: 4M/7M [INFO] I don't know where the reference to maven-java2wsdl-plugin comes from. How do I get around this issue? Regards, Praki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2] java2wsdl maven2 plugin problems
Hi all, I am trying to use the maven java2wsdl 1.1 plugin, and I have run into several problems. I am using maven 2.0.5, java 5, and Linux Ubuntu 6.10. 1.) Documentation: The example snippet on http://ws.apache.org/axis2/tools/1_1/maven-plugins/maven-java2wsdl-plugin.html is wrong and won't work. This part: /execution configuration classNamecom.foo.myservice.MyHandler/className /configuration /executions /plugin /plugins /build Should be /execution /executions configuration classNamecom.foo.myservice.MyHandler/className /configuration /plugin /plugins /build 2.) Documentation: The example command doesn't work (on the same page). mvn java2wsdl:java2wsdl Should be mvn axis-java2wsdl:java2wsdl 3.) Strangly, a directory gets created in my maven project called home. I think this might be causing other issues as well. It looks like it is taking the full path to my project (for example /home/scot/src/webservice/ ) and lopping off the first /, then creating a new directory ( for example /home/scot/src/webservice/home/scot/src/webservice/target/... ). 4.) When I run the plugin it can't find a class that exists in the standard maven2 directory src/main/java/ ( for example src/main/java/com/DummyHandler.java ). I noticed someone else complained about this on January 22nd, but I didn't see a reply to his post to the mailing list. java.lang.Exception: java.lang.ClassNotFoundException: com.DummyHandler at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.generate(Java2WSDLCodegenEngine.java:58) at org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo.java:146) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.ClassNotFoundException: com.DummyHandler at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.apache.ws.java2wsdl.Java2WSDLUtils.namespaceFromClassName(Java2WSDLUtils.java:63) at org.apache.ws.java2wsdl.Java2WSDLUtils.schemaNamespaceFromClassName(Java2WSDLUtils.java:82) at org.apache.ws.java2wsdl.Java2WSDLBuilder.getSchemaTargetNamespace(Java2WSDLBuilder.java:56) at org.apache.ws.java2wsdl.Java2WSDLBuilder.generateWSDL(Java2WSDLBuilder.java:152) at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.generate(Java2WSDLCodegenEngine.java:56) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
[AXIS2] java2wsdl classpath
Are there any examples of setting the classpath with java2wsdl? I've tried: java2wsdl.sh -cp .:/lib/test.jar -cn org.testing.Tester but it fails to find the classes in /lib/test.jar thanks, Alistair -- mov eax,1 mov ebx,0 int 80h - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] java2wsdl classpath
Alistair, The -cp is a java runtime command line option. What ever you pass here is passed to the java.exe that executes the jave code. If you look in the script ( java2wsdl.sh or java2wsdl.bat) you will see that the code (1) creates something called AXIS2_CLASSPATH ( all the axis runtime jars that are required (2) append to (1) the classpath the user passed it with java2wsdl -cp (3) append the %CLASSPATH% variable If you are not familiar with how the jvm treates -cp , I would say - look at the java documentation. On windows , step 3 does not happen. There is JIRA issue open and a patch has been provided. Mj On 2/14/07, Alistair Young [EMAIL PROTECTED] wrote: Are there any examples of setting the classpath with java2wsdl? I've tried: java2wsdl.sh -cp .:/lib/test.jar -cn org.testing.Tester but it fails to find the classes in /lib/test.jar thanks, Alistair -- mov eax,1 mov ebx,0 int 80h - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] java2wsdl classpath
thanks for that. I started with the correct classpath for os x format: java2wsdl.sh -cp .:/lib/test.jar -cn org.test.tester but it doesn't find classes in test.jar Alistair -- mov eax,1 mov ebx,0 int 80h Alistair, The -cp is a java runtime command line option. What ever you pass here is passed to the java.exe that executes the jave code. If you look in the script ( java2wsdl.sh or java2wsdl.bat) you will see that the code (1) creates something called AXIS2_CLASSPATH ( all the axis runtime jars that are required (2) append to (1) the classpath the user passed it with java2wsdl -cp (3) append the %CLASSPATH% variable If you are not familiar with how the jvm treates -cp , I would say - look at the java documentation. On windows , step 3 does not happen. There is JIRA issue open and a patch has been provided. Mj On 2/14/07, Alistair Young [EMAIL PROTECTED] wrote: Are there any examples of setting the classpath with java2wsdl? I've tried: java2wsdl.sh -cp .:/lib/test.jar -cn org.testing.Tester but it fails to find the classes in /lib/test.jar thanks, Alistair -- mov eax,1 mov ebx,0 int 80h - 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 generated code dependent on axis2-java2wsdl jar
Please log a Jira...
~Thilina
On 11/7/06, Paul Fremantle [EMAIL PROTECTED] wrote:
Seems to me we should fix this.
Paul
On 11/7/06, Nigel Charman [EMAIL PROTECTED] wrote:
I've just picked up on a new dependency in 1.1 RC2 and wanted to make
sure it was intentional.
Code generated by WSDL2Java with an ADB databinding now requires
axis2-java2wsdl.jar in order to compile. This wasn't the case in 1.1 RC1.
The dependency is in the following generated code which indirectly
references org.apache.ws.java2wsdl.utils.TypeTable.
public javax.xml.stream.XMLStreamReader
getPullParser(javax.xml.namespace.QName qName){
//We can safely assume an element has only one type
associated with it
return new
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl(MY_QNAME,
new java.lang.Object[]{
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReader.ELEMENT_TEXT,
org.apache.axis2.databinding.utils.ConverterUtil.convertToString(localBase64)
},
null);
}
Regards
Nigel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] WSDL2Java generated code dependent on axis2-java2wsdl jar
I've just picked up on a new dependency in 1.1 RC2 and wanted to make
sure it was intentional.
Code generated by WSDL2Java with an ADB databinding now requires
axis2-java2wsdl.jar in order to compile. This wasn't the case in 1.1 RC1.
The dependency is in the following generated code which indirectly
references org.apache.ws.java2wsdl.utils.TypeTable.
public javax.xml.stream.XMLStreamReader
getPullParser(javax.xml.namespace.QName qName){
//We can safely assume an element has only one type
associated with it
return new
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl(MY_QNAME,
new java.lang.Object[]{
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReader.ELEMENT_TEXT,
org.apache.axis2.databinding.utils.ConverterUtil.convertToString(localBase64)
},
null);
}
Regards
Nigel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]Java2WSDL error
Hi all, I'm trying to execute a Java2WSDL ant task which give me this error. javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory not found what does it means and how can I solve this problem. Regard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 Java2Wsdl
Hi all, Can you give me an example of java2wsdl ant task in Axis2? Regards, Nuno Martins - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 Java2Wsdl
Try this
path id=project.class.path
fileset dir=${user.lib}
include name=**/*.jar /
/fileset
/path
taskdef name=Java2WSDLTask
classname=org.apache.ws.java2wsdl.Java2WSDLTask
classpath refid=project.class.path /
/taskdef
target name=TestWSDL
Java2WSDLTask
className=com.test.IntrfcUserService
outputLocation=${wsdl.dir}
classpathURI=${classpathURI}
targetNamespace=http://UserService.test.com;
targetNamespacePrefix=tns
schemaTargetNamespace=http://UserService.test.com;
schemaTargetNamespacePrefix=stnps
serviceName=UserService
outputFileName=UserService.wsdl
/Java2WSDLTask
/target
-Original Message-
From: Nuno Martins [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 12, 2006 11:13 AM
To: axis-user@ws.apache.org
Subject: Axis2 Java2Wsdl
Hi all,
Can you give me an example of java2wsdl ant task in Axis2?
Regards,
Nuno Martins
-
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 Java2Wsdl
Title: Signature
Charak,
Thank you for tour response.
How can I set classpath for this target? My classpath must contain
binaries and jars in another folder.
Can you give me an example of wsdl2java too?
Regards,
Nuno Martins
Charak, Vikas wrote:
Try this
path id="project.class.path"
fileset dir="${user.lib}"
include name="**/*.jar" /
/fileset
/path
taskdef name="Java2WSDLTask"
classname="org.apache.ws.java2wsdl.Java2WSDLTask"
classpath refid="project.class.path" /
/taskdef
target name="TestWSDL"
Java2WSDLTask
className="com.test.IntrfcUserService"
outputLocation="${wsdl.dir}"
classpathURI="${classpathURI}"
targetNamespace="http://UserService.test.com"
targetNamespacePrefix="tns"
schemaTargetNamespace="http://UserService.test.com"
schemaTargetNamespacePrefix="stnps"
serviceName="UserService"
outputFileName="UserService.wsdl"
/Java2WSDLTask
/target
-Original Message-
From: Nuno Martins [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 12, 2006 11:13 AM
To: axis-user@ws.apache.org
Subject: Axis2 Java2Wsdl
Hi all,
Can you give me an example of java2wsdl ant task in Axis2?
Regards,
Nuno Martins
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] java2wsdl
Hi,
is there a way how java2wsdl can deal with static inner classes?
For example:
Service implementation:
package com.maxviva.test.soap;
import java.util.ArrayList;
import java.util.List;
public class MyTestService
{
public Foo getFoo(String message, int count)
{
Foo f = new Foo();
f.setCount( count );
ListFoo.Bar bars = new ArrayListFoo.Bar();
for(int i=0; i count; i++)
{
Foo.Bar b = new Foo.Bar();
b.setMessage( message + --- + i );
bars.add( b );
}
return f;
}
}
Data implementation:
package com.maxviva.test.soap;
public class Foo
{
private int count;
private Bar[] bars;
public Bar[] getBars()
{
return bars;
}
public void setBars( Bar[] bars )
{
this.bars = bars;
}
public int getCount()
{
return count;
}
public void setCount( int count )
{
this.count = count;
}
public static class Bar
{
private String message = huhu;
public String getMessage()
{
return message;
}
public void setMessage( String message )
{
this.message = message;
}
}
}
Resulting wsdl:
---snip---
xs:element type=types:Foo$Bar name=Foo$Bar /
xs:complexType name=Foo$Bar
---snap---
This causes an error.
Thanks4help,
--
Mit freundlichen Grüssen
Michael Hauck
Software Developer
email: [EMAIL PROTECTED]
---
maxviva GmbH
Luitpoldstraße 9
D 63739 Aschaffenburg
tel: +49 (0)6021 45482-13
fax: +49 (0)6021 45482-22
www.maxviva.com
---
*
Wir sind umgezogen. Bitte beachten Sie die neue Adresse.
*
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] java2wsdl generates unknown namespace
I logged this to http://issues.apache.org/jira/browse/AXIS2-1252 --- Kinichiro Inoguchi [EMAIL PROTECTED] wrote: Hi Deepal, and if you want to change the namespace you can do that too , I executed j2w with -stn option, see below. So, I think namespace should be http://aaa.bbb/types;. C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl Dims, I'll log this to JIRA, anyway. Thanks, kinichiro --- Davanum Srinivas [EMAIL PROTECTED] wrote: Deepal, I completely understand that. What i wanted to do with the bug report was to add a log.INFO saying that the schema target namespace is http://test/xsd; and if you want to change it then specify it on the command line AND/OR at least mention this in docs for j2w how we compute the schema target namespace. makes sense? thanks, dims On 9/27/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi dims; This is not a bug , that is the how it has implemented As I can understand , the package name of the service is test That is why it generate that namespace, so when sending the req need send that with that namespace (pls have a look at the wsdl , req should be according to thta) and if you want to change the namespace you can do that too , changing services,xml Thanks Deepal Davanum Srinivas wrote: Yes, please log a bug. -- dims On 9/27/06, Kinichiro Inoguchi [EMAIL PROTECTED] wrote: Hi, java2wsdl generates unknown namespace, http://test/xsd;. I'm using current nightly. My service class has method sayHello, and returns array of simple java beans HelloBean. Then I run java2wsdl, sayHello and sayHelloResponse are in namespace http://aaa.bbb/types;. But, HelloBean is in unknown namespace http://test/xsd;. Is this a bug ? C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl generated WSDL is like this; wsdl:definitions 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:ns1=http://aaa.bbb/types; xmlns:xxx=http://aaa.bbb; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=http://aaa.bbb; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ax22=http://test/xsd; targetNamespace=http://test/xsd; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=HelloBean type=ax22:HelloBean / xs:complexType name=HelloBean xs:sequence xs:element name=ret1 type=xs:string / xs:element name=ret2 type=xs:int / xs:element name=ret3 type=xs:long / xs:element name=ret4 type=xs:double / xs:element name=ret5 type=xs:float / xs:element name=ret6 type=xs:short / xs:element name=ret7 type=xs:boolean / /xs:sequence /xs:complexType /xs:schema xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:gen798=http://test/xsd; xmlns:ax21=http://aaa.bbb/types; targetNamespace=http://aaa.bbb/types; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=sayHello xs:complexType xs:sequence xs:element name=var1 type=xs:string / xs:element name=var2 type=xs:int / xs:element name=var3 type=xs:long / xs:element name=var4 type=xs:double / xs:element name=var5 type=xs:float / xs:element name=var6 type=xs:short / xs:element name=var7 type=xs:boolean / /xs:sequence /xs:complexType /xs:element xs:element name=sayHelloResponse xs:complexType xs:sequence xs:element name=return maxOccurs=unbounded type=gen798:HelloBean nillable=true / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types ... thanks, kinichiro __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks,
[Axis2] java2wsdl generates unknown namespace
Hi, java2wsdl generates unknown namespace, http://test/xsd;. I'm using current nightly. My service class has method sayHello, and returns array of simple java beans HelloBean. Then I run java2wsdl, sayHello and sayHelloResponse are in namespace http://aaa.bbb/types;. But, HelloBean is in unknown namespace http://test/xsd;. Is this a bug ? C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl generated WSDL is like this; wsdl:definitions 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:ns1=http://aaa.bbb/types; xmlns:xxx=http://aaa.bbb; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=http://aaa.bbb; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ax22=http://test/xsd; targetNamespace=http://test/xsd; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=HelloBean type=ax22:HelloBean / xs:complexType name=HelloBean xs:sequence xs:element name=ret1 type=xs:string / xs:element name=ret2 type=xs:int / xs:element name=ret3 type=xs:long / xs:element name=ret4 type=xs:double / xs:element name=ret5 type=xs:float / xs:element name=ret6 type=xs:short / xs:element name=ret7 type=xs:boolean / /xs:sequence /xs:complexType /xs:schema xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:gen798=http://test/xsd; xmlns:ax21=http://aaa.bbb/types; targetNamespace=http://aaa.bbb/types; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=sayHello xs:complexType xs:sequence xs:element name=var1 type=xs:string / xs:element name=var2 type=xs:int / xs:element name=var3 type=xs:long / xs:element name=var4 type=xs:double / xs:element name=var5 type=xs:float / xs:element name=var6 type=xs:short / xs:element name=var7 type=xs:boolean / /xs:sequence /xs:complexType /xs:element xs:element name=sayHelloResponse xs:complexType xs:sequence xs:element name=return maxOccurs=unbounded type=gen798:HelloBean nillable=true / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types ... thanks, kinichiro __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] java2wsdl generates unknown namespace
Yes, please log a bug. -- dims On 9/27/06, Kinichiro Inoguchi [EMAIL PROTECTED] wrote: Hi, java2wsdl generates unknown namespace, http://test/xsd;. I'm using current nightly. My service class has method sayHello, and returns array of simple java beans HelloBean. Then I run java2wsdl, sayHello and sayHelloResponse are in namespace http://aaa.bbb/types;. But, HelloBean is in unknown namespace http://test/xsd;. Is this a bug ? C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl generated WSDL is like this; wsdl:definitions 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:ns1=http://aaa.bbb/types; xmlns:xxx=http://aaa.bbb; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=http://aaa.bbb; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ax22=http://test/xsd; targetNamespace=http://test/xsd; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=HelloBean type=ax22:HelloBean / xs:complexType name=HelloBean xs:sequence xs:element name=ret1 type=xs:string / xs:element name=ret2 type=xs:int / xs:element name=ret3 type=xs:long / xs:element name=ret4 type=xs:double / xs:element name=ret5 type=xs:float / xs:element name=ret6 type=xs:short / xs:element name=ret7 type=xs:boolean / /xs:sequence /xs:complexType /xs:schema xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:gen798=http://test/xsd; xmlns:ax21=http://aaa.bbb/types; targetNamespace=http://aaa.bbb/types; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=sayHello xs:complexType xs:sequence xs:element name=var1 type=xs:string / xs:element name=var2 type=xs:int / xs:element name=var3 type=xs:long / xs:element name=var4 type=xs:double / xs:element name=var5 type=xs:float / xs:element name=var6 type=xs:short / xs:element name=var7 type=xs:boolean / /xs:sequence /xs:complexType /xs:element xs:element name=sayHelloResponse xs:complexType xs:sequence xs:element name=return maxOccurs=unbounded type=gen798:HelloBean nillable=true / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types ... thanks, kinichiro __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] java2wsdl generates unknown namespace
Hi dims; This is not a bug , that is the how it has implemented As I can understand , the package name of the service is test That is why it generate that namespace, so when sending the req need send that with that namespace (pls have a look at the wsdl , req should be according to thta) and if you want to change the namespace you can do that too , changing services,xml Thanks Deepal Davanum Srinivas wrote: Yes, please log a bug. -- dims On 9/27/06, Kinichiro Inoguchi [EMAIL PROTECTED] wrote: Hi, java2wsdl generates unknown namespace, http://test/xsd;. I'm using current nightly. My service class has method sayHello, and returns array of simple java beans HelloBean. Then I run java2wsdl, sayHello and sayHelloResponse are in namespace http://aaa.bbb/types;. But, HelloBean is in unknown namespace http://test/xsd;. Is this a bug ? C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl generated WSDL is like this; wsdl:definitions 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:ns1=http://aaa.bbb/types; xmlns:xxx=http://aaa.bbb; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=http://aaa.bbb; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ax22=http://test/xsd; targetNamespace=http://test/xsd; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=HelloBean type=ax22:HelloBean / xs:complexType name=HelloBean xs:sequence xs:element name=ret1 type=xs:string / xs:element name=ret2 type=xs:int / xs:element name=ret3 type=xs:long / xs:element name=ret4 type=xs:double / xs:element name=ret5 type=xs:float / xs:element name=ret6 type=xs:short / xs:element name=ret7 type=xs:boolean / /xs:sequence /xs:complexType /xs:schema xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:gen798=http://test/xsd; xmlns:ax21=http://aaa.bbb/types; targetNamespace=http://aaa.bbb/types; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=sayHello xs:complexType xs:sequence xs:element name=var1 type=xs:string / xs:element name=var2 type=xs:int / xs:element name=var3 type=xs:long / xs:element name=var4 type=xs:double / xs:element name=var5 type=xs:float / xs:element name=var6 type=xs:short / xs:element name=var7 type=xs:boolean / /xs:sequence /xs:complexType /xs:element xs:element name=sayHelloResponse xs:complexType xs:sequence xs:element name=return maxOccurs=unbounded type=gen798:HelloBean nillable=true / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types ... thanks, kinichiro __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] java2wsdl generates unknown namespace
Deepal, I completely understand that. What i wanted to do with the bug report was to add a log.INFO saying that the schema target namespace is http://test/xsd; and if you want to change it then specify it on the command line AND/OR at least mention this in docs for j2w how we compute the schema target namespace. makes sense? thanks, dims On 9/27/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi dims; This is not a bug , that is the how it has implemented As I can understand , the package name of the service is test That is why it generate that namespace, so when sending the req need send that with that namespace (pls have a look at the wsdl , req should be according to thta) and if you want to change the namespace you can do that too , changing services,xml Thanks Deepal Davanum Srinivas wrote: Yes, please log a bug. -- dims On 9/27/06, Kinichiro Inoguchi [EMAIL PROTECTED] wrote: Hi, java2wsdl generates unknown namespace, http://test/xsd;. I'm using current nightly. My service class has method sayHello, and returns array of simple java beans HelloBean. Then I run java2wsdl, sayHello and sayHelloResponse are in namespace http://aaa.bbb/types;. But, HelloBean is in unknown namespace http://test/xsd;. Is this a bug ? C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl generated WSDL is like this; wsdl:definitions 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:ns1=http://aaa.bbb/types; xmlns:xxx=http://aaa.bbb; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=http://aaa.bbb; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ax22=http://test/xsd; targetNamespace=http://test/xsd; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=HelloBean type=ax22:HelloBean / xs:complexType name=HelloBean xs:sequence xs:element name=ret1 type=xs:string / xs:element name=ret2 type=xs:int / xs:element name=ret3 type=xs:long / xs:element name=ret4 type=xs:double / xs:element name=ret5 type=xs:float / xs:element name=ret6 type=xs:short / xs:element name=ret7 type=xs:boolean / /xs:sequence /xs:complexType /xs:schema xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:gen798=http://test/xsd; xmlns:ax21=http://aaa.bbb/types; targetNamespace=http://aaa.bbb/types; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=sayHello xs:complexType xs:sequence xs:element name=var1 type=xs:string / xs:element name=var2 type=xs:int / xs:element name=var3 type=xs:long / xs:element name=var4 type=xs:double / xs:element name=var5 type=xs:float / xs:element name=var6 type=xs:short / xs:element name=var7 type=xs:boolean / /xs:sequence /xs:complexType /xs:element xs:element name=sayHelloResponse xs:complexType xs:sequence xs:element name=return maxOccurs=unbounded type=gen798:HelloBean nillable=true / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types ... thanks, kinichiro __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] java2wsdl generates unknown namespace
Hi Deepal, and if you want to change the namespace you can do that too , I executed j2w with -stn option, see below. So, I think namespace should be http://aaa.bbb/types;. C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl Dims, I'll log this to JIRA, anyway. Thanks, kinichiro --- Davanum Srinivas [EMAIL PROTECTED] wrote: Deepal, I completely understand that. What i wanted to do with the bug report was to add a log.INFO saying that the schema target namespace is http://test/xsd; and if you want to change it then specify it on the command line AND/OR at least mention this in docs for j2w how we compute the schema target namespace. makes sense? thanks, dims On 9/27/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi dims; This is not a bug , that is the how it has implemented As I can understand , the package name of the service is test That is why it generate that namespace, so when sending the req need send that with that namespace (pls have a look at the wsdl , req should be according to thta) and if you want to change the namespace you can do that too , changing services,xml Thanks Deepal Davanum Srinivas wrote: Yes, please log a bug. -- dims On 9/27/06, Kinichiro Inoguchi [EMAIL PROTECTED] wrote: Hi, java2wsdl generates unknown namespace, http://test/xsd;. I'm using current nightly. My service class has method sayHello, and returns array of simple java beans HelloBean. Then I run java2wsdl, sayHello and sayHelloResponse are in namespace http://aaa.bbb/types;. But, HelloBean is in unknown namespace http://test/xsd;. Is this a bug ? C:\axis2-std-SNAPSHOT-bin\bin\java2wsdl.bat -cn test.TestService1 -cp . -tn http://aaa.bbb -tp xxx -stn http://aaa.bbb/types -stp yyy -sn TestService1 -of TestService1.wsdl generated WSDL is like this; wsdl:definitions 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:ns1=http://aaa.bbb/types; xmlns:xxx=http://aaa.bbb; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=http://aaa.bbb; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:ax22=http://test/xsd; targetNamespace=http://test/xsd; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=HelloBean type=ax22:HelloBean / xs:complexType name=HelloBean xs:sequence xs:element name=ret1 type=xs:string / xs:element name=ret2 type=xs:int / xs:element name=ret3 type=xs:long / xs:element name=ret4 type=xs:double / xs:element name=ret5 type=xs:float / xs:element name=ret6 type=xs:short / xs:element name=ret7 type=xs:boolean / /xs:sequence /xs:complexType /xs:schema xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:gen798=http://test/xsd; xmlns:ax21=http://aaa.bbb/types; targetNamespace=http://aaa.bbb/types; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=sayHello xs:complexType xs:sequence xs:element name=var1 type=xs:string / xs:element name=var2 type=xs:int / xs:element name=var3 type=xs:long / xs:element name=var4 type=xs:double / xs:element name=var5 type=xs:float / xs:element name=var6 type=xs:short / xs:element name=var7 type=xs:boolean / /xs:sequence /xs:complexType /xs:element xs:element name=sayHelloResponse xs:complexType xs:sequence xs:element name=return maxOccurs=unbounded type=gen798:HelloBean nillable=true / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types ... thanks, kinichiro __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --
RE: [Axis2] JAVA2WSDL Eclipse plugin- How to genera te SOAP1.1 WSDL
If not Eclipse Plug-in then is there a way to use command line to generate SOAP1.1 WSDL. I could not find any such option in org.apache.ws.java2wsdl.Java2WSDL . Any help is appreciated. -Original Message- From: MUHAMMAD IQBAL [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 05, 2006 6:23 PM To: axis-user@ws.apache.org Subject: RE: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Same Problem here, I am using Axis1 WSDL generator tool instead. Regards, Muhammad Iqbal Software Engineer Etilize Inc. cell :0092-300-9377801 From: Charak, Vikas [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Date: Tue, 5 Sep 2006 16:31:42 -0400 Hi, I am using JAVA2WSDL Eclipse plug-in to generate WSDL files. By default it generates SOAP1.2 compliant WSDL files. Is there a way to make the plug-in generate SOAP1.1 WSDL file. Thanks. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL
Hi, I guess the Java2WSDL command line tool (from the nightly build of course) should do the trick for you since it is configured to generate two bindings. The problem could be that the eclipse plugin uses the Axis2 1.0 code base (we only release a plugin with a standard release - plugins are not available in the nightly build) so it would not have that feature. You can try replacing the Axis2 jar of the plugin but other interfaces might have changed so it is not recommended. Ajith On 9/6/06, Charak, Vikas [EMAIL PROTECTED] wrote: If not Eclipse Plug-in then is there a way to use command line to generate SOAP1.1 WSDL. I could not find any such option in org.apache.ws.java2wsdl.Java2WSDL . Any help is appreciated. -Original Message- From: MUHAMMAD IQBAL [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 05, 2006 6:23 PM To: axis-user@ws.apache.org Subject: RE: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Same Problem here, I am using Axis1 WSDL generator tool instead. Regards, Muhammad Iqbal Software Engineer Etilize Inc. cell :0092-300-9377801 From: Charak, Vikas [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Date: Tue, 5 Sep 2006 16:31:42 -0400 Hi, I am using JAVA2WSDL Eclipse plug-in to generate WSDL files. By default it generates SOAP1.2 compliant WSDL files. Is there a way to make the plug-in generate SOAP1.1 WSDL file. Thanks. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] JAVA2WSDL Eclipse plugin- How to genera te SOAP1.1 WSDL
Thanks a lot. Let me try and see how it goes. -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 06, 2006 3:57 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Hi, I guess the Java2WSDL command line tool (from the nightly build of course) should do the trick for you since it is configured to generate two bindings. The problem could be that the eclipse plugin uses the Axis2 1.0 code base (we only release a plugin with a standard release - plugins are not available in the nightly build) so it would not have that feature. You can try replacing the Axis2 jar of the plugin but other interfaces might have changed so it is not recommended. Ajith On 9/6/06, Charak, Vikas [EMAIL PROTECTED] wrote: If not Eclipse Plug-in then is there a way to use command line to generate SOAP1.1 WSDL. I could not find any such option in org.apache.ws.java2wsdl.Java2WSDL . Any help is appreciated. -Original Message- From: MUHAMMAD IQBAL [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 05, 2006 6:23 PM To: axis-user@ws.apache.org Subject: RE: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Same Problem here, I am using Axis1 WSDL generator tool instead. Regards, Muhammad Iqbal Software Engineer Etilize Inc. cell :0092-300-9377801 From: Charak, Vikas [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Date: Tue, 5 Sep 2006 16:31:42 -0400 Hi, I am using JAVA2WSDL Eclipse plug-in to generate WSDL files. By default it generates SOAP1.2 compliant WSDL files. Is there a way to make the plug-in generate SOAP1.1 WSDL file. Thanks. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] JAVA2WSDL Eclipse plugin- How to generate S OAP1.1 WSDL
Hi, I am using JAVA2WSDL Eclipse plug-in to generate WSDL files. By default it generates SOAP1.2 compliant WSDL files. Is there a way to make the plug-in generate SOAP1.1 WSDL file. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL
Same Problem here, I am using Axis1 WSDL generator tool instead. Regards, Muhammad Iqbal Software Engineer Etilize Inc. cell :0092-300-9377801 From: Charak, Vikas [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: [Axis2] JAVA2WSDL Eclipse plugin- How to generate SOAP1.1 WSDL Date: Tue, 5 Sep 2006 16:31:42 -0400 Hi, I am using JAVA2WSDL Eclipse plug-in to generate WSDL files. By default it generates SOAP1.2 compliant WSDL files. Is there a way to make the plug-in generate SOAP1.1 WSDL file. Thanks. - 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] Java2WSDL ceating operations for non-public service methods
Done http://issues.apache.org/jira/browse/AXIS2-1064 -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Wednesday, 23 August 2006 2:30 AM To: axis-user@ws.apache.org Subject: Re: [axis2] Java2WSDL ceating operations for non-public service methods Hi William; William Ferguson wrote: Hi, I'm finding that Java2WSDL is creating a WSDL with operation elements for methods that have private scope in my Service class. Should it be doing that? hmm, as I know it should not do that , can you please create a JIRA attaching your java class and corresponding wsdl. WSDL generated by the AxisServlet only includes the public methods, though these are also the only methods defined in services xml. William - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Java2WSDL ceating operations for non-public service methods
Hi William; William Ferguson wrote: Hi, I'm finding that Java2WSDL is creating a WSDL with operation elements for methods that have private scope in my Service class. Should it be doing that? hmm, as I know it should not do that , can you please create a JIRA attaching your java class and corresponding wsdl. WSDL generated by the AxisServlet only includes the public methods, though these are also the only methods defined in services xml. William - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] Java2WSDL ceating operations for non-public service methods
Hi, I'm finding that Java2WSDL is creating a WSDL with operation elements for methods that have private scope in my Service class. Should it be doing that? WSDL generated by the AxisServlet only includes the public methods, though these are also the only methods defined in services xml. William - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Java2WSDL problem
Thanks a lot Deepal, that was the missing piece. Bille -Ursprüngliche Nachricht- Von: axis-user@ws.apache.org Gesendet: 26.06.06 05:50:07 An: axis-user@ws.apache.org Betreff: Re: [axis2] Java2WSDL problem Can you pls download annogen-0.1.0.jar from codehouse. [EMAIL PROTECTED] wrote: Hi, I'm trying to produce a WSDL-File from my source. - First I tried with the Eclipse-Plugin, but got the Error an Error occured while code generating java.lang.reflect.InvocationTargetException without any further details - Then I tried to run the Java2WSDL-Class inside Eclipse, but I'm not able to compile the source, because there's an library missing for class org.codehaus.jam.JMethod. I searched the web, but I can't find any hints, where to get the according jar-File. My service works fine. It is plain Java-classes, I'm not using generated skeletons. I used the axis2-std-1.0-src.zip for my Java2WSDL-Eclipse project. Could someone please give me any advice. Thanks a lot Bille __ Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Java2WSDL problem
Can you pls download annogen-0.1.0.jar from codehouse. [EMAIL PROTECTED] wrote: Hi, I'm trying to produce a WSDL-File from my source. - First I tried with the Eclipse-Plugin, but got the Error an Error occured while code generating java.lang.reflect.InvocationTargetException without any further details - Then I tried to run the Java2WSDL-Class inside Eclipse, but I'm not able to compile the source, because there's an library missing for class org.codehaus.jam.JMethod. I searched the web, but I can't find any hints, where to get the according jar-File. My service works fine. It is plain Java-classes, I'm not using generated skeletons. I used the axis2-std-1.0-src.zip for my Java2WSDL-Eclipse project. Could someone please give me any advice. Thanks a lot Bille __ Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] Java2WSDL problem
Hi, I'm trying to produce a WSDL-File from my source. - First I tried with the Eclipse-Plugin, but got the Error an Error occured while code generating java.lang.reflect.InvocationTargetException without any further details - Then I tried to run the Java2WSDL-Class inside Eclipse, but I'm not able to compile the source, because there's an library missing for class org.codehaus.jam.JMethod. I searched the web, but I can't find any hints, where to get the according jar-File. My service works fine. It is plain Java-classes, I'm not using generated skeletons. I used the axis2-std-1.0-src.zip for my Java2WSDL-Eclipse project. Could someone please give me any advice. Thanks a lot Bille __ Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Java2WSDL problem in Axis2 Std 1.0
I am trying to convert my code to use Axis2 Std 1.0 instead of 0.93. The various pieces are all done programmatically, rather than using the plugin, as this is for a product. The Java2WSDL runs without breaking in 1.0, but generates an incorrect file. The toy example I am using uses a complex type as the method parameter for the service. In 0.93, you must only put the interface in the default package, but the generated WSDL is correct for a complex type parameter. In 1.0, the generator produces an incorrect WSDL file with two definitions for the complex type: apparently one for the import and one when it appears as a method parameter. The WSDL2Java generation throws an exception because of an incorrect WSDL file: INFO Running: java classname=org.apache.axis2.wsdl.WSDL2Java fork=true classpathref (arg value= -uri ) (arg file=c:\Java\projects2\axis2-std-1.0testbed\build\wsdl\WWPointsCalculator.wsdl ) (arg va lue=-s ) (arg value=-ss ) (arg value=-sd ) (arg value=-o ) (arg file=c:\Java\projects2\axis2-std-1.0 testbed\build\output ) (arg value=-p ) (arg value=testexamples.types ) WARN Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error par sing WSDL WARNat org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:94) WARNat org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) WARNat org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) WARN Caused by: org.apache.axis2.AxisFault: Schema for namespace 'http://PointsCalculator.ve.rec ursionsw.com/types' already contains type 'FoodDescription; nested exception is: WARNjava.lang.RuntimeException: Schema for namespace 'http://PointsCalculator.ve.recursionsw.c om/types' already contains type 'FoodDescription WARNat org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBu ilder.java:243) WARNat org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:87) WARN... 2 more WARN Caused by: java.lang.RuntimeException: Schema for namespace 'http://PointsCalculator.ve.rec ursionsw.com/types' already contains type 'FoodDescription WARNat org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:237) WARNat org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:10 3) WARNat org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:233) WARNat org.apache.axis2.description.WSDL2AxisServiceBuilder.getXMLSchema(WSDL2AxisServiceBuild er.java:959) WARNat org.apache.axis2.description.WSDL2AxisServiceBuilder.copyExtensibleElements(WSDL2AxisSe rviceBuilder.java:1067) WARNat org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBu ilder.java:221) I did not see a reference to this problem on the list or with Google, but perhaps I just missed it. Regards, -- Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Java2WSDL
I only have the binary version 0.94, I am not working from the source, so line numbers don't help me, sorry. -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 15, 2006 11:35 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Java2WSDL Hi Brennan; In the current SVN , Java2WSDL has a main class. org.apache.axis2.wsdl.Java2WSDL line number : 26 Brennan, Sean (IMS) wrote: I am trying to create the wsdl file for my service but it appears there is no longer a main function in the Java2WSDL class, so I keep getting the NoSuchMethodError. Anyone know how to create wsdl files now? Thanks. Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error. -- Thanks, Deepal ~Future is Open~ Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
RE: [Axis2] Java2WSDL
Yeah, that's the one I am trying to use, from release 0.94. I found this link to a bug fix on 1/31/2006 regarding Java2WSDL not having a main method, but it doesn't look like this was fixed until after .94 was released. http://marc2.theaimsgroup.com/?l=axis-devm=113874223427699w=2 Possible that this fix was not released yet? -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 15, 2006 11:50 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Java2WSDL Hi Brian, Are you using the older code? We've introduced a new Java2WSDL class in the wsdl package (org.apache.axis2.wsdl.Java2WSDL) inside the codegen module and it has a main method! Ajith On 3/16/06, Brennan, Sean (IMS) [EMAIL PROTECTED] wrote: I am trying to create the wsdl file for my service but it appears there is no longer a main function in the Java2WSDL class, so I keep getting the NoSuchMethodError. Anyone know how to create wsdl files now? Thanks. Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error. -- Ajith Ranabahu Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
[Axis2] Java2WSDL
I am trying to create the wsdl file for my service but it appears there is no longer a main function in the Java2WSDL class, so I keep getting the NoSuchMethodError. Anyone know how to create wsdl files now? Thanks. Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
Re: [Axis2] Java2WSDL
Hi Brennan; In the current SVN , Java2WSDL has a main class. org.apache.axis2.wsdl.Java2WSDL line number : 26 Brennan, Sean (IMS) wrote: I am trying to create the wsdl file for my service but it appears there is no longer a main function in the Java2WSDL class, so I keep getting the NoSuchMethodError. Anyone know how to create wsdl files now? Thanks. Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error. -- Thanks, Deepal ~Future is Open~
Re: [Axis2] Java2WSDL
Hi Brian, Are you using the older code? We've introduced a new Java2WSDL class in the wsdl package (org.apache.axis2.wsdl.Java2WSDL) inside the codegen module and it has a main method! Ajith On 3/16/06, Brennan, Sean (IMS) [EMAIL PROTECTED] wrote: I am trying to create the wsdl file for my service but it appears there is no longer a main function in the Java2WSDL class, so I keep getting the NoSuchMethodError. Anyone know how to create wsdl files now? Thanks. Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error. -- Ajith Ranabahu
