Re: WSDL2Java error
On Thu, Nov 20, 2008 at 8:47 AM, warnockm [EMAIL PROTECTED] wrote:
I'm trying to use WSDL2Java to create some shell java code from a WSDL file
I
created. I created the SOAP server in PHP and used the WSDL file to create
code in c# using Visual Studio 2008. This works very well, but when i try
it using the Axis2 tool, i get an error.
My WSDL file is: https://www.warnockinc.com/Dunbar/ws/wsdl/dunbar.wsdl
The error is:
wsdl2java -uri https://www.warnockinc.com/Dunbar/ws/wsdl/dunbar.wsdl
Using AXIS2_HOME: C:\axis2\
Using JAVA_HOME:C:\Program Files\Java\jre6\
Retrieving document at
'https://www.warnockinc.com/Dunbar/ws/wsdl/dunbar.wsdl'.
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException: can not find
type
{http://schemas.xmlsoap.org/soap/encoding/}Arrayhttp://schemas.xmlsoap.org/soap/encoding/%7DArrayfrom
the parent schema
http://
schema.example.com
at
org.apache.axis2.schema.SchemaCompiler.copyMetaInfoHierarchy(SchemaCompiler.java:1296)
at
org.apache.axis2.schema.SchemaCompiler.processComplexContent(SchemaCompiler.java:1258)
at
org.apache.axis2.schema.SchemaCompiler.processContentModel(SchemaCompiler.java:1153)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1097)
at
org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:1017)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:931)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
at
org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:563)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:370)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:280)
at
org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
... 8 more
Any idea what this would be? Thanks!
Here the problem is Axis2 does not support SoapEncoding.
Thanks,
Amila.
--
View this message in context:
http://www.nabble.com/WSDL2Java-error-tp20594340p20594340.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: WSDL2Java error
Thanks, that helps. Specifically, is it the SOAP-ENC part? It occurs when
there is an array of a complex data type. I read more about this, and many
people have a problem with it. What is the alternative to this?
Amila Suriarachchi wrote:
On Thu, Nov 20, 2008 at 8:47 AM, warnockm [EMAIL PROTECTED] wrote:
I'm trying to use WSDL2Java to create some shell java code from a WSDL
file
I
created. I created the SOAP server in PHP and used the WSDL file to
create
code in c# using Visual Studio 2008. This works very well, but when i
try
it using the Axis2 tool, i get an error.
My WSDL file is: https://www.warnockinc.com/Dunbar/ws/wsdl/dunbar.wsdl
The error is:
wsdl2java -uri https://www.warnockinc.com/Dunbar/ws/wsdl/dunbar.wsdl
Using AXIS2_HOME: C:\axis2\
Using JAVA_HOME:C:\Program Files\Java\jre6\
Retrieving document at
'https://www.warnockinc.com/Dunbar/ws/wsdl/dunbar.wsdl'.
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException: can not
find
type
{http://schemas.xmlsoap.org/soap/encoding/}Arrayhttp://schemas.xmlsoap.org/soap/encoding/%7DArrayfrom
the parent schema
http://
schema.example.com
at
org.apache.axis2.schema.SchemaCompiler.copyMetaInfoHierarchy(SchemaCompiler.java:1296)
at
org.apache.axis2.schema.SchemaCompiler.processComplexContent(SchemaCompiler.java:1258)
at
org.apache.axis2.schema.SchemaCompiler.processContentModel(SchemaCompiler.java:1153)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1097)
at
org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:1017)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:931)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
at
org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:563)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:370)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:280)
at
org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
... 8 more
Any idea what this would be? Thanks!
Here the problem is Axis2 does not support SoapEncoding.
Thanks,
Amila.
--
View this message in context:
http://www.nabble.com/WSDL2Java-error-tp20594340p20594340.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
--
View this message in context:
http://www.nabble.com/WSDL2Java-error-tp20594340p20632805.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: WSDL2JAVA ERROR- No bindings found in wsdl
Hi,
This wsdl gives us the common data types for operations and fault
types...,
?xml version=1.0 encoding=UTF-8?
project default=JB_Default_Task
taskdef name=java2wsdl
classname=org.apache.axis.tools.ant.wsdl.Java2WsdlAntTask/
taskdef name=wsdl2java
classname=org.apache.axis.tools.ant.wsdl.Wsdl2javaAntTask/
property name=baseDir
value=/home/serkans/jbproject/ParlayxCommon/
target name=JB_Default_Task
wsdl2java
all=true
debug=false
helperGen=false
noimports=false
output=${baseDir}/java/src
serverside=true
skeletonDeploy=true
testcase=true
timeout=0
typeMappingVersion=1.1
url=file://${baseDir}/wsdl/parlayx_common_faults_2_0.wsdl
verbose=false
noWrapped=false
mapping
namespace=http://www.csapi.org/schema/parlayx/common/v2_1;
package=com.mycompany.util.parlayx.common.v2_1/
/wsdl2java
/target
/project
This was working..
After reading the AXIS2 pojo guide I see that I must use data types as
POJO...
The other wsdls (which are defining a web service has bindings and port
types) will give me that data types if I generate code with wsdl2java
Thanks everybody..
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Monday, April 09, 2007 8:32 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL2JAVA ERROR- No bindings found in wsdl
The Parley WSDL only defines messages. It does not define portTypes or
bindings. WSDL2Java cannot generate code from this WSDL (neither Axis
1.x or Axis2 can do so).
If you were able to generate code using Axis 1.x , then you must have
had another WSDL that imported the Parley WSDL.
Anne
On 4/9/07, Serkan Sunel [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi,
That wsdl is working with old version of axis...
I am able to generate java code with old version of axis (1.3)...
We are implementing telco related operations with that...
That wsdl is a standart in telecommication industry..
It comes from http://www.parlay.org/en/specifications/pxws.asp
Anybody can help about this ?
Must I define that types specified in xsds as pojo ?
From: Krishnamoorthy J (HCL Financial Services)
[mailto:[EMAIL PROTECTED]
Sent: Monday, April 09, 2007 3:22 PM
To: axis-user@ws.apache.org
Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl
This is the wsdl in the attachment which has only messages defined. Even
with the Axis 1.x this will not work.
?xml version=1.0 encoding=UTF-8?
!-- January 5, 2006 --
wsdl:definitions
name=common_faults
targetNamespace=
http://www.csapi.org/wsdl/parlayx/common/v2_0/faults
http://www.csapi.org/wsdl/parlayx/common/v2_0/faults
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:parlayx_common_xsd=http://www.csapi.org/schema/parlayx/common/v2_
1
wsdl:types
xsd:schema elementFormDefault=qualified
xsd:import
namespace=http://www.csapi.org/schema/parlayx/common/v2_1;
schemaLocation=parlayx_common_types_2_1.xsd/
/xsd:schema
/wsdl:types
wsdl:message name=ServiceException
wsdl:part name=ServiceException
element=parlayx_common_xsd:ServiceException/
/wsdl:message
wsdl:message name=PolicyException
wsdl:part name=PolicyException
element=parlayx_common_xsd:PolicyException/
/wsdl:message
/wsdl:definitions
From: Serkan Sunel [mailto:]
Sent: Monday, April 09, 2007 5:49 PM
To: axis-user@ws.apache.org
Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl
Hi,
I have been using this wsdl with old version of AXIS ..
I was able to generate java code with axis 1.X
Project was working old axis ..
I only wanted to upgr my dependency..
You sure that wsdl is wrong ?
From: Krishnamoorthy J (HCL Financial Services)
[mailto:[EMAIL PROTECTED]
Sent: Monday, April 09, 2007 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl
Your WSDL is not complete.
Check this tutorial http://www.w3schools.com/wsdl/default.asp
From: Serkan Sunel [mailto:[EMAIL PROTECTED]
Sent: Monday, April 09, 2007 4:15 PM
To: axis-user@ws.apache.org
Subject: WSDL2JAVA ERROR- No bindings found in wsdl
Hi all,
I am a newbie for axis2
Can you tell me how can I generate java code for the wsdl and XSD files
(attached)..
I am gettimg the following errors..
[EMAIL PROTECTED] wsdl] java org.apache.axis2.wsdl.WSDL2Code -uri
parlayx_common_faults_2_0.wsdl --serverside-interface
Retrieving schema at 'parlayx_common_types_2_1.xsd', relative to
'file:/home/serkans/products/utilities/current/utilities/parlayx/wsdl/'.
log4j:WARN No appenders could
RE: WSDL2JAVA ERROR- No bindings found in wsdl
Your WSDL is not complete. Check this tutorial http://www.w3schools.com/wsdl/default.asp From: Serkan Sunel [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 4:15 PM To: axis-user@ws.apache.org Subject: WSDL2JAVA ERROR- No bindings found in wsdl Hi all, I am a newbie for axis2 Can you tell me how can I generate java code for the wsdl and XSD files (attached).. I am gettimg the following errors.. [EMAIL PROTECTED] wsdl] java org.apache.axis2.wsdl.WSDL2Code -uri parlayx_common_faults_2_0.wsdl --serverside-interface Retrieving schema at 'parlayx_common_types_2_1.xsd', relative to 'file:/home/serkans/products/utilities/current/utilities/parlayx/wsdl/'. log4j:WARN No appenders could be found for logger (org.apache.axis2.description.WSDL11ToAxisServiceBuilder). log4j:WARN Please initialize the log4j system properly. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl; nested exception is: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) ... 1 more Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL 11ToAxisServiceBuilder.java:377) at org.apache.axis2 Thanks.. Serkan SUNEL DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---
RE: WSDL2JAVA ERROR- No bindings found in wsdl
Hi, I have been using this wsdl with old version of AXIS .. I was able to generate java code with axis 1.X Project was working old axis .. I only wanted to upgr my dependency.. You sure that wsdl is wrong ? From: Krishnamoorthy J (HCL Financial Services) [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 3:09 PM To: axis-user@ws.apache.org Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl Your WSDL is not complete. Check this tutorial http://www.w3schools.com/wsdl/default.asp From: Serkan Sunel [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 4:15 PM To: axis-user@ws.apache.org Subject: WSDL2JAVA ERROR- No bindings found in wsdl Hi all, I am a newbie for axis2 Can you tell me how can I generate java code for the wsdl and XSD files (attached).. I am gettimg the following errors.. [EMAIL PROTECTED] wsdl] java org.apache.axis2.wsdl.WSDL2Code -uri parlayx_common_faults_2_0.wsdl --serverside-interface Retrieving schema at 'parlayx_common_types_2_1.xsd', relative to 'file:/home/serkans/products/utilities/current/utilities/parlayx/wsdl/'. log4j:WARN No appenders could be found for logger (org.apache.axis2.description.WSDL11ToAxisServiceBuilder). log4j:WARN Please initialize the log4j system properly. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl; nested exception is: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) ... 1 more Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL 11ToAxisServiceBuilder.java:377) at org.apache.axis2 Thanks.. Serkan SUNEL DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---
RE: WSDL2JAVA ERROR- No bindings found in wsdl
This is the wsdl in the attachment which has only messages defined. Even with the Axis 1.x this will not work. ?xml version=1.0 encoding=UTF-8? !-- January 5, 2006 -- wsdl:definitions name=common_faults targetNamespace=http://www.csapi.org/wsdl/parlayx/common/v2_0/faults; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:parlayx_common_xsd=http://www.csapi.org/schema/parlayx/common/v2_ 1 wsdl:types xsd:schema elementFormDefault=qualified xsd:import namespace=http://www.csapi.org/schema/parlayx/common/v2_1; schemaLocation=parlayx_common_types_2_1.xsd/ /xsd:schema /wsdl:types wsdl:message name=ServiceException wsdl:part name=ServiceException element=parlayx_common_xsd:ServiceException/ /wsdl:message wsdl:message name=PolicyException wsdl:part name=PolicyException element=parlayx_common_xsd:PolicyException/ /wsdl:message /wsdl:definitions From: Serkan Sunel [mailto:] Sent: Monday, April 09, 2007 5:49 PM To: axis-user@ws.apache.org Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl Hi, I have been using this wsdl with old version of AXIS .. I was able to generate java code with axis 1.X Project was working old axis .. I only wanted to upgr my dependency.. You sure that wsdl is wrong ? From: Krishnamoorthy J (HCL Financial Services) [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 3:09 PM To: axis-user@ws.apache.org Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl Your WSDL is not complete. Check this tutorial http://www.w3schools.com/wsdl/default.asp From: Serkan Sunel [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 4:15 PM To: axis-user@ws.apache.org Subject: WSDL2JAVA ERROR- No bindings found in wsdl Hi all, I am a newbie for axis2 Can you tell me how can I generate java code for the wsdl and XSD files (attached).. I am gettimg the following errors.. [EMAIL PROTECTED] wsdl] java org.apache.axis2.wsdl.WSDL2Code -uri parlayx_common_faults_2_0.wsdl --serverside-interface Retrieving schema at 'parlayx_common_types_2_1.xsd', relative to 'file:/home/serkans/products/utilities/current/utilities/parlayx/wsdl/'. log4j:WARN No appenders could be found for logger (org.apache.axis2.description.WSDL11ToAxisServiceBuilder). log4j:WARN Please initialize the log4j system properly. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl; nested exception is: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) ... 1 more Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL 11ToAxisServiceBuilder.java:377) at org.apache.axis2 Thanks.. Serkan SUNEL DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---
RE: WSDL2JAVA ERROR- No bindings found in wsdl
Hi, That wsdl is working with old version of axis... I am able to generate java code with old version of axis (1.3)... We are implementing telco related operations with that... That wsdl is a standart in telecommication industry.. It comes from http://www.parlay.org/en/specifications/pxws.asp Anybody can help about this ? Must I define that types specified in xsds as pojo ? From: Krishnamoorthy J (HCL Financial Services) [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 3:22 PM To: axis-user@ws.apache.org Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl This is the wsdl in the attachment which has only messages defined. Even with the Axis 1.x this will not work. ?xml version=1.0 encoding=UTF-8? !-- January 5, 2006 -- wsdl:definitions name=common_faults targetNamespace=http://www.csapi.org/wsdl/parlayx/common/v2_0/faults; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:parlayx_common_xsd=http://www.csapi.org/schema/parlayx/common/v2_ 1 wsdl:types xsd:schema elementFormDefault=qualified xsd:import namespace=http://www.csapi.org/schema/parlayx/common/v2_1; schemaLocation=parlayx_common_types_2_1.xsd/ /xsd:schema /wsdl:types wsdl:message name=ServiceException wsdl:part name=ServiceException element=parlayx_common_xsd:ServiceException/ /wsdl:message wsdl:message name=PolicyException wsdl:part name=PolicyException element=parlayx_common_xsd:PolicyException/ /wsdl:message /wsdl:definitions From: Serkan Sunel [mailto:] Sent: Monday, April 09, 2007 5:49 PM To: axis-user@ws.apache.org Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl Hi, I have been using this wsdl with old version of AXIS .. I was able to generate java code with axis 1.X Project was working old axis .. I only wanted to upgr my dependency.. You sure that wsdl is wrong ? From: Krishnamoorthy J (HCL Financial Services) [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 3:09 PM To: axis-user@ws.apache.org Subject: RE: WSDL2JAVA ERROR- No bindings found in wsdl Your WSDL is not complete. Check this tutorial http://www.w3schools.com/wsdl/default.asp From: Serkan Sunel [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 4:15 PM To: axis-user@ws.apache.org Subject: WSDL2JAVA ERROR- No bindings found in wsdl Hi all, I am a newbie for axis2 Can you tell me how can I generate java code for the wsdl and XSD files (attached).. I am gettimg the following errors.. [EMAIL PROTECTED] wsdl] java org.apache.axis2.wsdl.WSDL2Code -uri parlayx_common_faults_2_0.wsdl --serverside-interface Retrieving schema at 'parlayx_common_types_2_1.xsd', relative to 'file:/home/serkans/products/utilities/current/utilities/parlayx/wsdl/'. log4j:WARN No appenders could be found for logger (org.apache.axis2.description.WSDL11ToAxisServiceBuilder). log4j:WARN Please initialize the log4j system properly. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl; nested exception is: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) ... 1 more Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL 11ToAxisServiceBuilder.java:377) at org.apache.axis2 Thanks.. Serkan SUNEL DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---
Re: WSDL2JAVA ERROR- No bindings found in wsdl
The Parley WSDL only defines messages. It does not define portTypes or bindings. WSDL2Java cannot generate code from this WSDL (neither Axis 1.x or Axis2 can do so). If you were able to generate code using Axis 1.x, then you must have had another WSDL that imported the Parley WSDL. Anne On 4/9/07, Serkan Sunel [EMAIL PROTECTED] wrote: Hi, That wsdl is working with old version of axis… I am able to generate java code with old version of axis (1.3)… We are implementing telco related operations with that… That wsdl is a standart in telecommication industry.. It comes from http://www.parlay.org/en/specifications/pxws.asp Anybody can help about this ? Must I define that types specified in xsds as pojo ? -- *From:* Krishnamoorthy J (HCL Financial Services) [mailto: [EMAIL PROTECTED] *Sent:* Monday, April 09, 2007 3:22 PM *To:* axis-user@ws.apache.org *Subject:* RE: WSDL2JAVA ERROR- No bindings found in wsdl This is the wsdl in the attachment which has only messages defined. Even with the Axis 1.x this will not work. ?xml version=1.0 encoding=UTF-8? !-- January 5, 2006 -- wsdl:definitions name=common_faults targetNamespace=http://www.csapi.org/wsdl/parlayx/common/v2_0/faults; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:parlayx_common_xsd= http://www.csapi.org/schema/parlayx/common/v2_1; wsdl:types xsd:schema elementFormDefault=qualified xsd:import namespace= http://www.csapi.org/schema/parlayx/common/v2_1; schemaLocation=parlayx_common_types_2_1.xsd/ /xsd:schema /wsdl:types wsdl:message name=ServiceException wsdl:part name=ServiceException element=parlayx_common_xsd:ServiceException/ /wsdl:message wsdl:message name=PolicyException wsdl:part name=PolicyException element=parlayx_common_xsd:PolicyException/ /wsdl:message /wsdl:definitions -- *From:* Serkan Sunel [mailto:] *Sent:* Monday, April 09, 2007 5:49 PM *To:* axis-user@ws.apache.org *Subject:* RE: WSDL2JAVA ERROR- No bindings found in wsdl Hi, I have been using this wsdl with old version of AXIS .. I was able to generate java code with axis 1.X Project was working old axis .. I only wanted to upgr my dependency.. You sure that wsdl is wrong ? -- *From:* Krishnamoorthy J (HCL Financial Services) [mailto: [EMAIL PROTECTED] *Sent:* Monday, April 09, 2007 3:09 PM *To:* axis-user@ws.apache.org *Subject:* RE: WSDL2JAVA ERROR- No bindings found in wsdl Your WSDL is not complete. Check this tutorial http://www.w3schools.com/wsdl/default.asp -- *From:* Serkan Sunel [mailto:[EMAIL PROTECTED] *Sent:* Monday, April 09, 2007 4:15 PM *To:* axis-user@ws.apache.org *Subject:* WSDL2JAVA ERROR- No bindings found in wsdl Hi all, I am a newbie for axis2 Can you tell me how can I generate java code for the wsdl and XSD files (attached).. I am gettimg the following errors.. [EMAIL PROTECTED] wsdl] java org.apache.axis2.wsdl.WSDL2Code -uri parlayx_common_faults_2_0.wsdl --serverside-interface Retrieving schema at 'parlayx_common_types_2_1.xsd', relative to 'file:/home/serkans/products/utilities/current/utilities/parlayx/wsdl/'. log4j:WARN No appenders could be found for logger ( org.apache.axis2.description.WSDL11ToAxisServiceBuilder). log4j:WARN Please initialize the log4j system properly. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init( CodeGenerationEngine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl; nested exception is: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init( CodeGenerationEngine.java:103) ... 1 more Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding( WSDL11ToAxisServiceBuilder.java:377) at org.apache.axis2 Thanks.. Serkan SUNEL DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure
RE: WSDL2Java error generating WSDL 2.0 / 2.1
Anne, Thank you, that was the problem. I had namespace defined as xmlns:tns=urn:xsd.jaxb.service targetNamespace=urn:xsd.jaxb.service I changed it to xmlns:tns=http://xsd.jaxb.service; targetNamespace=http://xsd.jaxb.service; Does urn has to be one of the concrete protocols ? Can't it be urn ? Appreciate the response. -yogen -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 14, 2007 9:27 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java error generating WSDL 2.0 / 2.1 Do you have a URI in your WSDL called XSDService.wsdl? Perhaps you're using it for a namespace URI? As the error indicates, this is a malformed URI. A URI must begin with a protocol scheme, such as urn:, http: mailto:, ftp:, etc. Anne On 2/14/07, Yadav, Yogendra (IT) [EMAIL PROTECTED] wrote: Hi, I get error when try to generate v2.0 or v2.1 WSDL. Am I doing something wrong ? wsdl2java -wv 2.0 -d none -p com.xsd.input -ss -sd -g -uri XSDService.wsdl -pn XSDNODBServicePortType Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:116) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: WSDLException: faultCode=PARSER_ERROR: Could not create a URL from context URI null and location URI XSDService.wsdl.: no protocol : XSDService.wsdl: java.net.MalformedURLException: no protocol: XSDService.wsdl at java.net.URL.init(URL.java:567) at java.net.URL.init(URL.java:464) at org.apache.woden.internal.util.StringUtils.getURL(Unknown Source) at org.apache.woden.internal.DOMWSDLReader.readWSDL(Unknown Source) at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.init(WSDL20ToA xisServiceBuilder.java:95) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:90) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) at org.apache.woden.internal.DOMWSDLReader.readWSDL(Unknown Source) at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.init(WSDL20ToA xisServiceBuilder.java:95) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:90) ... 2 more wsdl2java -wv 2.1 -d none -p com.xsd.input -ss -sd -g -uri XSDService.wsdl -pn XSDNODBServicePortType Retrieving schema at 'purchaseorder.xsd', relative to 'file:/C:/work/AXIS2-Examples/document-oriented-service/xsd-based/no-bin ding/tmp/'. Feb 14, 2007 7:02:43 PM org.apache.axis2.description.WSDL11ToAxisServiceBuilder populateService SEVERE: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType; nested exception is: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) ... 2 more Caused by: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL 11ToAxisServiceBuilder.java:344) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:200) ... 3 more thanx -yogen NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL2Java error generating WSDL 2.0 / 2.1
urn: is a valid scheme for a URI. Please open a JIRA. (Is this error in Woden or in Axis2?) On 2/15/07, Yadav, Yogendra (IT) [EMAIL PROTECTED] wrote: Anne, Thank you, that was the problem. I had namespace defined as xmlns:tns=urn:xsd.jaxb.service targetNamespace=urn:xsd.jaxb.service I changed it to xmlns:tns=http://xsd.jaxb.service; targetNamespace=http://xsd.jaxb.service; Does urn has to be one of the concrete protocols ? Can't it be urn ? Appreciate the response. -yogen -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 14, 2007 9:27 PM To: axis-user@ws.apache.org Subject: Re: WSDL2Java error generating WSDL 2.0 / 2.1 Do you have a URI in your WSDL called XSDService.wsdl? Perhaps you're using it for a namespace URI? As the error indicates, this is a malformed URI. A URI must begin with a protocol scheme, such as urn:, http: mailto:, ftp:, etc. Anne On 2/14/07, Yadav, Yogendra (IT) [EMAIL PROTECTED] wrote: Hi, I get error when try to generate v2.0 or v2.1 WSDL. Am I doing something wrong ? wsdl2java -wv 2.0 -d none -p com.xsd.input -ss -sd -g -uri XSDService.wsdl -pn XSDNODBServicePortType Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:116) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: WSDLException: faultCode=PARSER_ERROR: Could not create a URL from context URI null and location URI XSDService.wsdl.: no protocol : XSDService.wsdl: java.net.MalformedURLException: no protocol: XSDService.wsdl at java.net.URL.init(URL.java:567) at java.net.URL.init(URL.java:464) at org.apache.woden.internal.util.StringUtils.getURL(Unknown Source) at org.apache.woden.internal.DOMWSDLReader.readWSDL(Unknown Source) at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.init(WSDL20ToA xisServiceBuilder.java:95) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:90) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) at org.apache.woden.internal.DOMWSDLReader.readWSDL(Unknown Source) at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.init(WSDL20ToA xisServiceBuilder.java:95) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:90) ... 2 more wsdl2java -wv 2.1 -d none -p com.xsd.input -ss -sd -g -uri XSDService.wsdl -pn XSDNODBServicePortType Retrieving schema at 'purchaseorder.xsd', relative to 'file:/C:/work/AXIS2-Examples/document-oriented-service/xsd-based/no-bin ding/tmp/'. Feb 14, 2007 7:02:43 PM org.apache.axis2.description.WSDL11ToAxisServiceBuilder populateService SEVERE: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType; nested exception is: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) ... 2 more Caused by: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL 11ToAxisServiceBuilder.java:344) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL11ToAxisServiceBuilder.java:200) ... 3 more thanx -yogen NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error
Re: WSDL2Java error generating WSDL 2.0 / 2.1
Do you have a URI in your WSDL called XSDService.wsdl? Perhaps you're using it for a namespace URI? As the error indicates, this is a malformed URI. A URI must begin with a protocol scheme, such as urn:, http: mailto:, ftp:, etc. Anne On 2/14/07, Yadav, Yogendra (IT) [EMAIL PROTECTED] wrote: Hi, I get error when try to generate v2.0 or v2.1 WSDL. Am I doing something wrong ? wsdl2java -wv 2.0 -d none -p com.xsd.input -ss -sd -g -uri XSDService.wsdl -pn XSDNODBServicePortType Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:116) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: WSDLException: faultCode=PARSER_ERROR: Could not create a URL from context URI null and location URI XSDService.wsdl.: no protocol : XSDService.wsdl: java.net.MalformedURLException: no protocol: XSDService.wsdl at java.net.URL.init(URL.java:567) at java.net.URL.init(URL.java:464) at org.apache.woden.internal.util.StringUtils.getURL(Unknown Source) at org.apache.woden.internal.DOMWSDLReader.readWSDL(Unknown Source) at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.init(WSDL20ToAxisServiceBuilder.java:95) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:90) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) at org.apache.woden.internal.DOMWSDLReader.readWSDL(Unknown Source) at org.apache.axis2.description.WSDL20ToAxisServiceBuilder.init(WSDL20ToAxisServiceBuilder.java:95) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:90) ... 2 more wsdl2java -wv 2.1 -d none -p com.xsd.input -ss -sd -g -uri XSDService.wsdl -pn XSDNODBServicePortType Retrieving schema at 'purchaseorder.xsd', relative to 'file:/C:/work/AXIS2-Examples/document-oriented-service/xsd-based/no-binding/tmp/'. Feb 14, 2007 7:02:43 PM org.apache.axis2.description.WSDL11ToAxisServiceBuilder populateService SEVERE: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:112) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType; nested exception is: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:250) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:103) ... 2 more Caused by: org.apache.axis2.AxisFault: No port found for the given name :XSDNODBServicePortType at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.findBinding(WSDL11ToAxisServiceBuilder.java:344) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:200) ... 3 more thanx -yogen NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL2Java Error
Title: WSDL2Java Error By the way, there is a good article under http://devresource.hp.com/drc/slide_presentations/schemaWSDL/index.jsp about usage ofwsdl:import and xsd:import (exactly saying what Brennan said, and more...) Gul From: Spies, Brennan [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 4:23 PMTo: axis-user@ws.apache.orgSubject: RE: WSDL2Java Error Paul, wsdl:import is only used for importing other wsdl files, not xsd. If you want to import/include xsd, you should do so inside the wsdl:types section. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message-From: Stevens, Paul A [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 9:10 AMTo: axis-user@ws.apache.orgSubject: WSDL2Java Error We are getting the following error trying to convert a wsdl to java: D:\ehro\wsdl_testWSDL2Java -uri "eTrust spml-wsdl.wsdl" -o test Using AXIS2_HOME: D:\axis2 Using JAVA_HOME: D:\j2sdk1.4.2_08 log4j:WARN No appenders could be found for logger (org.apache.axis2.i18n.ProjectResourceBundle). log4j:WARN Please initialize the log4j system properly. Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:96) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: WSDLException (at /wsdl:definitions/wsdl:import): faultCode=3DINVALID_WSDL: Encountered illegal extension attribute 'schemaLocation'. Extension attributes must be in a namespace other than WSDL's.: at com.ibm.wsdl.xml.WSDLReaderImpl.parseExtensibilityAttributes(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(Cod eGenerationEngine.java:238) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:81) ... 2 more Here is the wsdl: ?xml version="1.0" encoding="utf-8"? wsdl:definitions name="eTrust IAM SPML Service" targetNamespace="urn:oasis:names:tc:SPML:1:0:wsdl" xmlns:xsd="http://www.w3.org/1/XMLSchema" xmlns:tns="urn:oasis:names:tc:SPML:1:0:wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:spml="urn:oasis:names:tc:SPML:1:0:req" xmlns="http://schemas.xmlsoap.org/wsdl/" wsdl:import namespace="urn:oasis:names:tc:SPML:1:0:req" schemaLocation="http://www.oasis-open.org/committees/download.php/2396/cs-pstc-spml-schema-1.0.xsd"/ wsdl:documentation This is a web-service interface to the eTrust Admin user provisioning functions such as add, modify, delete, search, and extended requests. It provides a platform- and language-independent protocol that allows the eTrust Provisioning Server to respond to requests generated from any Requesting Authority (RA) able to construct a valid SPML request. /wsdl:documentation wsdl:message name="SPMLBatchRequestMessage" wsdl:part name="body" element="spml:batchRequest" / /wsdl:message wsdl:message name="SPMLBatchResponseMessage" wsdl:part name="body" element="spml:batchResponse" / /wsdl:message wsdl:message name="SPMLAddRequestMessage" wsdl:part name="body" element="spml:addRequest" / /wsdl:message wsdl:message name="SPMLAddResponseMessage" wsdl:part name="body" element="spml:addResponse" / /wsdl:message wsdl:message name="SPMLModifyRequestMessage" wsdl:part name="body" element="spml:modifyRequest" / /wsdl:message wsdl:message name="SPMLModifyResponseMessage" wsdl:part name="body" element="spml:modifyResponse" / /wsdl:message wsdl:message name="SPMLDeleteRequestMessage" wsdl:part name="body" element="spml:deleteRequest" / /wsdl:message wsdl:message name="SPMLDeleteResponseMessage" wsdl:part name="body" element="spml:deleteResponse" / /wsdl:message wsdl:message name="SPMLSearchRequestMessage" wsdl:part name="body" element="spml:searchRequest" / /wsdl:message wsdl:message name="SPMLSearchResponseMessage" wsdl:part name="body" element="spml:searchResponse" / /wsdl:message wsdl:message name="SPMLExtendedRequestMessage" wsdl:part name="body" element=
Re: WSDL2Java error
Note that import (both wsdl and xsd) doesn't change the targetNamespace of the imported namespace (hence the rule about no namespace coercion). import just gives you the ability to reference entities from the other namespace. On 4/20/06, Dies Koper [EMAIL PROTECTED] wrote: Hello Anne, Dink, I'm not sure I understand Dies's first recommendation. The targetNamespace of the types schema should NOT be the same as the imported namespace, ifx. (If you want to incorporate a namespace of the same name, you must use xsd:include rather than xsd:import). You might want to verify theSorry, I meant the targetNamespace of the XSD that is being imported.But I was wrong. I forgot that Namespace coercion on wsdl:import is disallowed by the Profile. in the WS-I BP spec (R2005) only applied towsdl:import, not to xsd:import.Regards,Dies On 4/20/06, Dies Koper [EMAIL PROTECTED] wrote: Hello Dink, Maybe you can use www.ws-i.org's WS-I test tool to check your WSDL. 1. The target name of your schema ( http://www.ifxforum.org) should be the same as the namespace (now urn:ifxforum-org) you specify in the xsd:import. 2. The names of the wsdl:input elements (tns:DoIFXRqMsg and tns:DoIFXRsMsg are not valid NCName values. Other than that it looks okay to me. Regards, Dies Dink wrote: Hello all, I have created a WSDL for a web service called WS017. The WSDL is put on http://mis.ccu.edu.tw/~dink/WS017.wsdl . However I can't use the Axis WSDL2Java tool to produce the stub for this service. Can somebody help me to check if the WSDL is error? Anyone can use the command line java org.apache.axis.wsdl.WSDL2Java http://mis.ccu.edu.tw/~dink/WS017.wsdl -p stub to test the WSDL. Best Regard, Dink Lo
Re: WSDL2Java error
Hello Dink, Maybe you can use www.ws-i.org's WS-I test tool to check your WSDL. 1. The target name of your schema (http://www.ifxforum.org;) should be the same as the namespace (now urn:ifxforum-org) you specify in the xsd:import. 2. The names of the wsdl:input elements (tns:DoIFXRqMsg and tns:DoIFXRsMsg are not valid NCName values. Other than that it looks okay to me. Regards, Dies Dink wrote: Hello all, I have created a WSDL for a web service called WS017. The WSDL is put on http://mis.ccu.edu.tw/~dink/WS017.wsdl . However I can't use the Axis WSDL2Java tool to produce the stub for this service. Can somebody help me to check if the WSDL is error? Anyone can use the command line java org.apache.axis.wsdl.WSDL2Java http://mis.ccu.edu.tw/~dink/WS017.wsdl -p stub to test the WSDL. Best Regard, Dink Lo
Re: WSDL2Java error
Dink,You need to declare some namespaces in your wsdl:definitions statement, e.g., xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ xmlns:wsdlsoap= http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:tns=urn:ifxforum-org:WSDL:1:PortType xmlns:types=urn:ifxforum-org:WSDL:1:PortType:types xmlns:ifx=urn:ufxforum-org:XSD:1I'm not sure I understand Dies's first recommendation. The targetNamespace of the types schema should NOT be the same as the imported namespace, ifx. (If you want to incorporate a namespace of the same name, you must use xsd:include rather than xsd:import). You might want to verify the namespace URI of the imported schema. Should it be urn:ifxforum-org:XSD:1 rather than urn:ufxforum-org:XSD:1? Dies's second point is accurate. (Drop the prefix, or just remove the name attributes.)AnneOn 4/20/06, Dies Koper [EMAIL PROTECTED] wrote:Hello Dink,Maybe you can use www.ws-i.org's WS-I test tool to check your WSDL.1. The target name of your schema (http://www.ifxforum.org) should bethe same as the namespace (now urn:ifxforum-org) you specify in the xsd:import.2. The names of the wsdl:input elements (tns:DoIFXRqMsg andtns:DoIFXRsMsg are not valid NCName values.Other than that it looks okay to me.Regards,Dies Dink wrote: Hello all, I have created a WSDL for a web service called WS017. The WSDL is put on http://mis.ccu.edu.tw/~dink/WS017.wsdl . However I can't use the Axis WSDL2Java tool to produce the stub for this service. Can somebody help me to check if the WSDL is error? Anyone can use the command line java org.apache.axis.wsdl.WSDL2Java http://mis.ccu.edu.tw/~dink/WS017.wsdl -p stub to test the WSDL. Best Regard, Dink Lo
Re: WSDL2Java error
Hello Anne, Dink, I'm not sure I understand Dies's first recommendation. The targetNamespace of the types schema should NOT be the same as the imported namespace, ifx. (If you want to incorporate a namespace of the same name, you must use xsd:include rather than xsd:import). You might want to verify the Sorry, I meant the targetNamespace of the XSD that is being imported. But I was wrong. I forgot that Namespace coercion on wsdl:import is disallowed by the Profile. in the WS-I BP spec (R2005) only applied to wsdl:import, not to xsd:import. Regards, Dies On 4/20/06, Dies Koper [EMAIL PROTECTED] wrote: Hello Dink, Maybe you can use www.ws-i.org's WS-I test tool to check your WSDL. 1. The target name of your schema (http://www.ifxforum.org;) should be the same as the namespace (now urn:ifxforum-org) you specify in the xsd:import. 2. The names of the wsdl:input elements (tns:DoIFXRqMsg and tns:DoIFXRsMsg are not valid NCName values. Other than that it looks okay to me. Regards, Dies Dink wrote: Hello all, I have created a WSDL for a web service called WS017. The WSDL is put on http://mis.ccu.edu.tw/~dink/WS017.wsdl . However I can't use the Axis WSDL2Java tool to produce the stub for this service. Can somebody help me to check if the WSDL is error? Anyone can use the command line java org.apache.axis.wsdl.WSDL2Java http://mis.ccu.edu.tw/~dink/WS017.wsdl -p stub to test the WSDL. Best Regard, Dink Lo
Re: WSDL2Java error.
I don't quite understand the SAX exception, but there are serious errors in the WSDL document. I suggest you go back to the people that gave you the WSDL and tell them that they need to fix it. It contains the following errors: 1- You must supply a name for the WSDL document. It must not be an empty string. 2- You must not use wsdl:import to import schemas. Because you are trying to assemble multiple schemas from the same namespace, you must use xsd:include. 3- A wsdl:part definition must contain an element attribute when using document style or a type attribute when using rpc style. It must not include both attributes. 4- A portType's wsdl:operation definition should not include a parameterOrder attribute when using document style. 5- A document style binding must use literal encoding. 6- If you want to access this service from a remote system, you must specify a DNS-resolvable URL in the location attribute in the wsdlsoap:address definition (not localhost). Here is a corrected WSDL (except for error #6 -- please specify a proper location): ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=http://ejbs.websrv.napsi.eng.it; name=webServ xmlns:impl=http://ejbs.websrv.napsi.eng.it; xmlns:intf=http://ejbs.websrv.napsi.eng.it; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:requestRicIndividuo=http://webServ; xmlns:responseRicIndividuo=http://webServ; xmlns:requestRicToponomastica=http://webServ; xmlns:responseRicToponomastica=http://webServ; xmlns:requestUpdate=http://webServ; xmlns:responseUpdate=http://webServ; !-- WSDL created by Apache Axis version: 1.2beta3 Built on Aug 01, 2004 (05:59:22 PDT) -- wsdl:types xsd:schema targetNamespace=http://webServ; xsd:include schemaLocation=inputRicIndividuo.xsd/ xsd:include schemaLocation=inputToponomastica.xsd/ xsd:include schemaLocation=outputRicIndividuo.xsd/ xsd:include schemaLocation=outputToponomastica.xsd/ !--xsd:include schemaLocation=inputUpdate.xsd/ xsd:include schemaLocation=outputUpdate.xsd/-- /xsd:schema /wsdl:types wsdl:message name=updateRequest wsdl:part name=input element=requestUpdate:update/ /wsdl:message wsdl:message name=updateResponse wsdl:part name=updateReturn element=responseUpdate:esitoAggiornamento/ /wsdl:message !-- Sezione di ricerca tramite codice famiglia -- !-- Request di ricerca byFamilyCode -- wsdl:message name=byFamilyCodeRequest wsdl:part name=input element=requestRicIndividuo:ricercaIndividuo/ /wsdl:message wsdl:message name=byFamilyCodeResponse wsdl:part name=byFamilyCodeReturn element=responseRicIndividuo:esitoRicercaIndividuo/ /wsdl:message !-- Sezione di ricerca toponomastica. -- !-- Request di ricerca toponomastica -- wsdl:message name=toponomasticRequest wsdl:part name=input element=requestRicToponomastica:ricercaToponomastica/ /wsdl:message !-- Response di ricerca toponomastica -- wsdl:message name=toponomasticResponse wsdl:part name=toponomasticReturn element=responseRicToponomastica:esitoRicercaToponomastica/ /wsdl:message !-- Sezione di ricerca tramite dati utenti -- !-- Request di ricerca byUserData -- wsdl:message name=byUserDataRequest wsdl:part name=input element=requestRicIndividuo:ricercaIndividuo/ /wsdl:message !-- Response di ricerca byUserData -- wsdl:message name=byUserDataResponse wsdl:part name=byUserDataReturn element=responseRicIndividuo:esitoRicercaIndividuo/ /wsdl:message !-- Sezione di ricerca tramite codice fiscale -- !-- Request di ricerca byFiscalCode -- wsdl:message name=byFiscalCodeRequest wsdl:part name=doc element=requestRicIndividuo:ricercaIndividuo/ /wsdl:message !-- Response di ricerca byFiscalCode -- wsdl:message name=byFiscalCodeResponse wsdl:part name=byFiscalCodeReturn element=responseRicIndividuo:esitoRicercaIndividuo/ /wsdl:message wsdl:portType name=Searcher wsdl:operation name=update wsdl:input message=impl:updateRequest name=updateRequest/ wsdl:output message=impl:updateResponse name=updateResponse/ /wsdl:operation wsdl:operation name=byFiscalCode wsdl:input message=impl:byFiscalCodeRequest name=byFiscalCodeRequest/ wsdl:output message=impl:byFiscalCodeResponse name=byFiscalCodeResponse/ /wsdl:operation wsdl:operation name=byUserData wsdl:input message=impl:byUserDataRequest name=byUserDataRequest/ wsdl:output message=impl:byUserDataResponse name=byUserDataResponse/ /wsdl:operation wsdl:operation name=byFamilyCode wsdl:input message=impl:byFamilyCodeRequest name=byFamilyCodeRequest/ wsdl:output message=impl:byFamilyCodeResponse name=byFamilyCodeResponse/ /wsdl:operation wsdl:operation name=toponomastic wsdl:input message=impl:toponomasticRequest name=toponomasticRequest/ wsdl:output
