Re: problem with wsdl2java in 1.5

[Andreas Veithen]

It looks like your Java runtime environment (GCJ/GNU classpath?) is
incomplete. I would recommend to install Sun's JRE for Linux.

Andreas

On Thu, Jun 25, 2009 at 02:12, Vadim
Letitchevskivletitchev...@teledyne.com wrote:
 wsdl2java in axis2-1.5 did not work for me reporting exceptions like these:

 Exception in thread main java.lang.NoClassDefFoundError:
 org.apache.axis2.description.AxisDescription
    at java.lang.Class.initializeClass(libgcj.so.7rh)
    at java.lang.Class.initializeClass(libgcj.so.7rh)
    at
 org.apache.axis2.description.WSDLToAxisServiceBuilder.init(WSDLToAxisServiceBuilder.java:101)
    at
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.init(WSDL11ToAxisServiceBuilder.java:215)
    at
 org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.init(WSDL11ToAllAxisServicesBuilder.java:63)
    at
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:144)
    at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
    at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
 Caused by: java.lang.ClassNotFoundException:
 java.util.concurrent.ConcurrentHashMap not found in
 gnu.gcj.runtime.SystemClassLoader{urls=[file:NED615Soap.wsdl,file:/home/Ned/axis2-1.5/,file:./,file:/home/Ned/axis2-1.5//lib/activation-1.1.jar,file:/home/Ned/axis2-1.5//lib/axiom-api-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-dom-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-impl-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-ant-plugin-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-clustering-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-corba-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-fastinfoset-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-java2wsdl-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxbri-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxws-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jibx-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-json-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-kernel-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-metadata-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-mtompolicy-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-saaj-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-spring-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-http-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-local-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-xmlbeans-1.5.jar,file:/home/Ned/axis2-1.5//lib/bcel-5.1.jar,file:/home/Ned/axis2-1.5//lib/commons-codec-1.3.jar,file:/home/Ned/axis2-1.5//lib/commons-fileupload-1.2.jar,file:/home/Ned/axis2-1.5//lib/commons-httpclient-3.1.jar,file:/home/Ned/axis2-1.5//lib/commons-io-1.4.jar,file:/home/Ned/axis2-1.5//lib/commons-lang-2.3.jar,file:/home/Ned/axis2-1.5//lib/commons-logging-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-annotation_1.0_spec-1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-jaxws_2.1_spec-1.0.jar,file:/home/Ned/axis2-1.5//lib/geronimo-saaj_1.3_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-stax-api_1.0_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-ws-metadata_2.0_spec-1.1.2.jar,file:/home/Ned/axis2-1.5//lib/httpcore-4.0.jar,file:/home/Ned/axis2-1.5//lib/jalopy-1.5rc3.jar,file:/home/Ned/axis2-1.5//lib/jaxb-api-2.1.jar,file:/home/Ned/axis2-1.5//lib/jaxb-impl-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxb-xjc-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxen-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/jettison-1.0-RC2.jar,file:/home/Ned/axis2-1.5//lib/jibx-bind-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/jibx-run-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/log4j-1.2.15.jar,file:/home/Ned/axis2-1.5//lib/mail-1.4.jar,file:/home/Ned/axis2-1.5//lib/mex-1.5.jar,file:/home/Ned/axis2-1.5//lib/neethi-2.0.4.jar,file:/home/Ned/axis2-1.5//lib/smack-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/smackx-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/soapmonitor-1.5.jar,file:/home/Ned/axis2-1.5//lib/woden-api-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/woden-impl-dom-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/wsdl4j-1.6.2.jar,file:/home/Ned/axis2-1.5//lib/wstx-asl-3.2.4.jar,file:/home/Ned/axis2-1.5//lib/xalan-2.7.0.jar,file:/home/Ned/axis2-1.5//lib/xercesImpl-2.6.2.jar,file:/home/Ned/axis2-1.5//lib/xml-apis-1.3.02.jar,file:/home/Ned/axis2-1.5//lib/xmlbeans-2.3.0.jar,file:/home/Ned/axis2-1.5//lib/xml-resolver-1.2.jar,file:/home/Ned/axis2-1.5//lib/XmlSchema-1.4.3.jar,file:./],
 parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
    at java.net.URLClassLoader.findClass(libgcj.so.7rh)
    at gnu.gcj.runtime.SystemClassLoader.findClass(libgcj.so.7rh)
    at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
    at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
    at java.lang.Class.forName(libgcj.so.7rh)
    at java.lang.Class.initializeClass(libgcj.so.7rh)
    ...7 more
 QUESTIONS:
  When I did all the same but with axis2-1.4 it seems to generate the code. I
 don't know if it is working 

problem with wsdl2java in 1.5

[Vadim Letitchevski]

wsdl2java in axis2-1.5 did not work for me reporting exceptions like these:

Exception in thread main java.lang.NoClassDefFoundError: 
org.apache.axis2.description.AxisDescription
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   at 
org.apache.axis2.description.WSDLToAxisServiceBuilder.init(WSDLToAxisServiceBuilder.java:101)
   at 
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.init(WSDL11ToAxisServiceBuilder.java:215)
   at 
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.init(WSDL11ToAllAxisServicesBuilder.java:63)
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:144)
   at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: java.lang.ClassNotFoundException: 
java.util.concurrent.ConcurrentHashMap not found in 
gnu.gcj.runtime.SystemClassLoader{urls=[file:NED615Soap.wsdl,file:/home/Ned/axis2-1.5/,file:./,file:/home/Ned/axis2-1.5//lib/activation-1.1.jar,file:/home/Ned/axis2-1.5//lib/axiom-api-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-dom-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axiom-impl-1.2.8.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-adb-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-ant-plugin-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-clustering-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-codegen-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-corba-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-fastinfoset-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-java2wsdl-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxbri-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jaxws-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-jibx-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-json-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-kernel-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-metadata-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-mtompolicy-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-saaj-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-spring-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-http-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-transport-local-1.5.jar,file:/home/Ned/axis2-1.5//lib/axis2-xmlbeans-1.5.jar,file:/home/Ned/axis2-1.5//lib/bcel-5.1.jar,file:/home/Ned/axis2-1.5//lib/commons-codec-1.3.jar,file:/home/Ned/axis2-1.5//lib/commons-fileupload-1.2.jar,file:/home/Ned/axis2-1.5//lib/commons-httpclient-3.1.jar,file:/home/Ned/axis2-1.5//lib/commons-io-1.4.jar,file:/home/Ned/axis2-1.5//lib/commons-lang-2.3.jar,file:/home/Ned/axis2-1.5//lib/commons-logging-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-annotation_1.0_spec-1.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-jaxws_2.1_spec-1.0.jar,file:/home/Ned/axis2-1.5//lib/geronimo-saaj_1.3_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-stax-api_1.0_spec-1.0.1.jar,file:/home/Ned/axis2-1.5//lib/geronimo-ws-metadata_2.0_spec-1.1.2.jar,file:/home/Ned/axis2-1.5//lib/httpcore-4.0.jar,file:/home/Ned/axis2-1.5//lib/jalopy-1.5rc3.jar,file:/home/Ned/axis2-1.5//lib/jaxb-api-2.1.jar,file:/home/Ned/axis2-1.5//lib/jaxb-impl-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxb-xjc-2.1.7.jar,file:/home/Ned/axis2-1.5//lib/jaxen-1.1.1.jar,file:/home/Ned/axis2-1.5//lib/jettison-1.0-RC2.jar,file:/home/Ned/axis2-1.5//lib/jibx-bind-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/jibx-run-1.2.1.jar,file:/home/Ned/axis2-1.5//lib/log4j-1.2.15.jar,file:/home/Ned/axis2-1.5//lib/mail-1.4.jar,file:/home/Ned/axis2-1.5//lib/mex-1.5.jar,file:/home/Ned/axis2-1.5//lib/neethi-2.0.4.jar,file:/home/Ned/axis2-1.5//lib/smack-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/smackx-3.0.4.jar,file:/home/Ned/axis2-1.5//lib/soapmonitor-1.5.jar,file:/home/Ned/axis2-1.5//lib/woden-api-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/woden-impl-dom-1.0M8.jar,file:/home/Ned/axis2-1.5//lib/wsdl4j-1.6.2.jar,file:/home/Ned/axis2-1.5//lib/wstx-asl-3.2.4.jar,file:/home/Ned/axis2-1.5//lib/xalan-2.7.0.jar,file:/home/Ned/axis2-1.5//lib/xercesImpl-2.6.2.jar,file:/home/Ned/axis2-1.5//lib/xml-apis-1.3.02.jar,file:/home/Ned/axis2-1.5//lib/xmlbeans-2.3.0.jar,file:/home/Ned/axis2-1.5//lib/xml-resolver-1.2.jar,file:/home/Ned/axis2-1.5//lib/XmlSchema-1.4.3.jar,file:./],
 parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
   at java.net.URLClassLoader.findClass(libgcj.so.7rh)
   at gnu.gcj.runtime.SystemClassLoader.findClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at java.lang.Class.forName(libgcj.so.7rh)
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   ...7 more
QUESTIONS:
 When I did all the same but with axis2-1.4 it seems to generate the code. I 
don't know if it is working yet, but I am wondering if I should just rely on 
axis2-1.4 or fix my problem for axis2-1.5?
I am new to axis2 and java programming in whole. Unfortunately axis2c does not 
support SOAP 1.1 attachments (pure MIME) , only MTOM (am I right?).

Problem with wsdl2java

[Andrea Turli]

Hi all,

I'm trying to consume a secure Axis Web service from a Globus Toolkit 4
service. I generated stubs with standard Axis' wsdl2java from a wsdl
(glite-security-voms-admin-2.0.2.wsdl)where all wsdl:operation are described
this way:

 wsdl:operation name=getVOName
wsdlsoap:operation soapAction=/
 wsdl:input name=getVONameRequest
   wsdlsoap:body encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/; namespace=
http://glite.org/wsdl/services/org.glite.security.voms.service.admin;
use=encoded/
 /wsdl:input
wsdl:output name=getVONameResponse
wsdlsoap:body encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/; namespace=
http://glite.org/wsdl/services/org.glite.security.voms.service.admin;
use=encoded/
 /wsdl:output
wsdl:fault name=VOMSException
wsdlsoap:fault encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/; name=VOMSException namespace=
http://glite.org/wsdl/services/org.glite.security.voms.service.admin;
use=encoded/
 /wsdl:fault
 /wsdl:operation

Let me underline the soapAction=. As far as I understood, in Globus
Toolkit environment, stubs should be generated from a wsdl that expect
soapAction to be populated.

So for test, I've tried to specify, in a given operation of that wsdl, the
correct soapAction. Then I've re-generated the stubs and everything works!

After this long explaination (sorry) my question is: could it be possible
(using some option in wsdl2java command) to inject the correct soapAction at
stub creation time, in order to have GT4 compliant stubs? Or could you
suggest me another workaround?

Thank you very much,

Andrea

Problem Axis2 Wsdl2java generated message

[krishna.arani]

Hi,
In my rpc/literal style webservice, I have a wsdl:message element with
multiple parts in it.  One of the part can be nullable. The problem is the
generated ADB from wsdl2java throws an exception if the part is null while
serialising to xml. 

  wsdl:message name=TryGetByKeyTenantResponse
wsdl:part name=orderKey type=na:OrderKey /
wsdl:part name=entity type=ys:TenantValue /
  /wsdl:message

here the entity can be null. so it is expected that the soap response to
have 

s5:entity xsi:nil=1 xmlns:s5=http://www.syndesis.com/ys/intf;  
  
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/

But the generated ADB class throws an exception if entity is null.

If have moved these two element parts under another type and use that as
part it works by defining nillable=true for the second element. But I dont
want to do this or change the message structure as other parties will have
to chage too. This was working fine with axis1.

any advice on how to go with this issue.
Thanks in advance.

-Krishna Arani

-- 
View this message in context: 
http://www.nabble.com/Problem-Axis2-Wsdl2java-generated-message-tp23175455p23175455.html
Sent from the Axis - User mailing list archive at Nabble.com.

[axis2] Problem with wsdl2java and xsd final attribute

[morten.frank]

Hi,

I have had trouble with generating Java stubs if my type def. contains
the following:

xs:complexType name=time final=extension restriction
  xs:sequence/xs:sequence
/xs:complexType

According to the XSD specification this should be legal:
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#eleme
nt-complexType


It works, if the def. is changed to:

xs:complexType name=time final=#all
  xs:sequence/xs:sequence
/xs:complexType


The generation triggers the following error:

[ERROR] org.apache.ws.commons.schema.constants.Enum$EnumValueException:
Bad Enumeration value 'extension restriction'
java.lang.RuntimeException:
org.apache.ws.commons.schema.constants.Enum$EnumValueException: Bad
Enumeration value 'exten
sion restriction'
at
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilde
r.java:1886)
at
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilde
r.java:1902)
at
org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.ja
va:1627)
at
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(Schema
Builder.java:175)
at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollectio
n.java:347)
at
org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLT
oAxisServiceBuilder.java:140)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleEl
ements(WSDL11ToAxisServiceBuilder.jav
a:2186)


According to a colleague this problem was introduced in axis2 and not
present in axis.

Is this worth a JIRA or is the problem already reported?

Regards
Morten

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis2] Problem with wsdl2java and xsd final attribute

[Amila Suriarachchi]

Please create a jira.

Amila.

On Dec 20, 2007 3:13 PM, [EMAIL PROTECTED] wrote:

 Hi,

 I have had trouble with generating Java stubs if my type def. contains
 the following:

 xs:complexType name=time final=extension restriction
  xs:sequence/xs:sequence
 /xs:complexType

 According to the XSD specification this should be legal:
 http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#eleme
 nt-complexType


 It works, if the def. is changed to:

 xs:complexType name=time final=#all
  xs:sequence/xs:sequence
 /xs:complexType


 The generation triggers the following error:

 [ERROR] org.apache.ws.commons.schema.constants.Enum$EnumValueException:
 Bad Enumeration value 'extension restriction'
 java.lang.RuntimeException:
 org.apache.ws.commons.schema.constants.Enum$EnumValueException: Bad
 Enumeration value 'exten
 sion restriction'
at
 org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilde
 r.java:1886)
at
 org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilde
 r.java:1902)
at
 org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.ja
 va:1627)
at
 org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(Schema
 Builder.java:175)
at
 org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollectio
 n.java:347)
at
 org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLT
 oAxisServiceBuilder.java:140)
at
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleEl
 ements(WSDL11ToAxisServiceBuilder.jav
 a:2186)


 According to a colleague this problem was introduced in axis2 and not
 present in axis.

 Is this worth a JIRA or is the problem already reported?

 Regards
 Morten

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Amila Suriarachchi,
WSO2 Inc.

problem with WSDL2Java and nested complex types

[Dário Abdulrehman]

I generated a Web Service Client with Eclipse 3.2 (which is using Axis 1.3)
from a WSDL that contains nested complex types.

I noticed that the generated Java code doesn't contain the innermost complex
types. Is this some bug in WSDL2Java?

Thanks.

-- 
Dário Abdulrehman
PGP Public Key: http://tinyurl.com/2pm9d7
--

Re: Problem in WSDL2java with eclipse code generator

[Lahiru Sandakith]

The log will be append to the eclipse .log file located at the
eclipse_worksapace/.metadata
Please attach the stack trace there.
thanks
Lahiru

On 9/20/07, ktzanet [EMAIL PROTECTED] wrote:


 Hi,
 I am trying to create java code with eclipse code generator. I first
 created
 the wsdl file with java2wsdl using the same plugin. When I click finish
 though, I get the following message:

 An error occured while completing process -java.lang.InterruptedException:
 There are no parts for fault message:
 {http://service.netmode.ntua.gr}Exception

 Can someone help me?
 Thank you

 This is my wsdl:

 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:xsd=http://service.netmode.ntua.gr/xsd;
 xmlns:ns=http://service.netmode.ntua.gr;
 xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
 targetNamespace=http://service.netmode.ntua.gr;wsdl:typesxs:schema
 xmlns:xs=http://www.w3.org/2001/XMLSchema;
 attributeFormDefault=qualified
 elementFormDefault=qualified
 targetNamespace=http://service.netmode.ntua.gr/xsd;
 xs:element name=ExceptionFault
 xs:complexType
 xs:sequence
 xs:element name=Exception nillable=true
 type=xs:anyType /
 /xs:sequence
 /xs:complexType
 /xs:element
 xs:element name=getLocation
 xs:complexType
 xs:sequence
 xs:element name=id nillable=true
 type=xs:int /
 /xs:sequence
 /xs:complexType
 /xs:element
 xs:element name=getLocationResponse
 xs:complexType
 xs:sequence
 xs:element name=return nillable=true
 type=xs:string /
 /xs:sequence
 /xs:complexType
 /xs:element
 /xs:schema/wsdl:typeswsdl:message
 name=getLocationMessagewsdl:part
 name=part1 element=xsd:getLocation //wsdl:messagewsdl:message
 name=getLocationResponseMessagewsdl:part name=part1
 element=xsd:getLocationResponse //wsdl:messagewsdl:portType
 name=TopologyServicePortTypewsdl:operation
 name=getLocationwsdl:input
 xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
 wsaw:Action=urn:getLocation message=ns:getLocationMessage
 /wsdl:output
 xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
 message=ns:getLocationResponseMessage wsaw:Action=urn:getLocation
 /wsdl:fault message=ns:Exception name=Exception
 //wsdl:operation/wsdl:portTypewsdl:binding
 name=TopologyServiceSOAP11Binding
 type=ns:TopologyServicePortTypesoap:binding
 transport=http://schemas.xmlsoap.org/soap/http; style=document
 /wsdl:operation name=getLocationsoap:operation
 soapAction=urn:getLocation style=document /wsdl:inputsoap:body
 use=literal //wsdl:inputwsdl:outputsoap:body use=literal
 //wsdl:outputwsdl:fault name=Exceptionsoap:body use=literal
 //wsdl:fault/wsdl:operation/wsdl:bindingwsdl:binding
 name=TopologyServiceSOAP12Binding
 type=ns:TopologyServicePortTypesoap12:binding
 transport=http://schemas.xmlsoap.org/soap/http; style=document
 /wsdl:operation name=getLocationsoap12:operation
 soapAction=urn:getLocation style=document /wsdl:inputsoap12:body
 use=literal //wsdl:inputwsdl:outputsoap12:body use=literal
 //wsdl:outputwsdl:fault name=Exceptionsoap12:body use=literal
 //wsdl:fault/wsdl:operation/wsdl:bindingwsdl:service
 name=TopologyServicewsdl:port name=TopologyServiceSOAP11port
 binding=ns:TopologyServiceSOAP11Bindingsoap:address
 location=http://localhost:8080/axis2/services/TopologyService;
 //wsdl:portwsdl:port name=TopologyServiceSOAP12port
 binding=ns:TopologyServiceSOAP12Bindingsoap12:address
 location=http://localhost:8080/axis2/services/TopologyService;
 //wsdl:port/wsdl:service/wsdl:definitions
 --
 View this message in context:
 http://www.nabble.com/Problem-in-WSDL2java-with-eclipse-code-generator-tf4486812.html#a12794863
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Thanks
Lahiru Sandakith

http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC  1AB1 FE5E 7464 1F01 9A0F

Re: Problem in WSDL2java with eclipse code generator

[ktzanet]

Can you please explain this to me because I don't understand.
Thank u



The log will be append to the eclipse .log file located at the
eclipse_worksapace/.metadata
Please attach the stack trace there.
thanks
Lahiru

-- 
View this message in context: 
http://www.nabble.com/Problem-in-WSDL2java-with-eclipse-code-generator-tf4486812.html#a12815037
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem in WSDL2java with eclipse code generator

[ktzanet]

Hi,
I am trying to create java code with eclipse code generator. I first created
the wsdl file with java2wsdl using the same plugin. When I click finish
though, I get the following message:

An error occured while completing process -java.lang.InterruptedException:
There are no parts for fault message:
{http://service.netmode.ntua.gr}Exception

Can someone help me?
Thank you

This is my wsdl:

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:xsd=http://service.netmode.ntua.gr/xsd;
xmlns:ns=http://service.netmode.ntua.gr;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
targetNamespace=http://service.netmode.ntua.gr;wsdl:typesxs:schema
xmlns:xs=http://www.w3.org/2001/XMLSchema; attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://service.netmode.ntua.gr/xsd;
xs:element name=ExceptionFault
xs:complexType
xs:sequence
xs:element name=Exception nillable=true 
type=xs:anyType /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=getLocation
xs:complexType
xs:sequence
xs:element name=id nillable=true type=xs:int /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=getLocationResponse
xs:complexType
xs:sequence
xs:element name=return nillable=true 
type=xs:string /
/xs:sequence
/xs:complexType
/xs:element
/xs:schema/wsdl:typeswsdl:message name=getLocationMessagewsdl:part
name=part1 element=xsd:getLocation //wsdl:messagewsdl:message
name=getLocationResponseMessagewsdl:part name=part1
element=xsd:getLocationResponse //wsdl:messagewsdl:portType
name=TopologyServicePortTypewsdl:operation
name=getLocationwsdl:input
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
wsaw:Action=urn:getLocation message=ns:getLocationMessage /wsdl:output
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
message=ns:getLocationResponseMessage wsaw:Action=urn:getLocation
/wsdl:fault message=ns:Exception name=Exception
//wsdl:operation/wsdl:portTypewsdl:binding
name=TopologyServiceSOAP11Binding
type=ns:TopologyServicePortTypesoap:binding
transport=http://schemas.xmlsoap.org/soap/http; style=document
/wsdl:operation name=getLocationsoap:operation
soapAction=urn:getLocation style=document /wsdl:inputsoap:body
use=literal //wsdl:inputwsdl:outputsoap:body use=literal
//wsdl:outputwsdl:fault name=Exceptionsoap:body use=literal
//wsdl:fault/wsdl:operation/wsdl:bindingwsdl:binding
name=TopologyServiceSOAP12Binding
type=ns:TopologyServicePortTypesoap12:binding
transport=http://schemas.xmlsoap.org/soap/http; style=document
/wsdl:operation name=getLocationsoap12:operation
soapAction=urn:getLocation style=document /wsdl:inputsoap12:body
use=literal //wsdl:inputwsdl:outputsoap12:body use=literal
//wsdl:outputwsdl:fault name=Exceptionsoap12:body use=literal
//wsdl:fault/wsdl:operation/wsdl:bindingwsdl:service
name=TopologyServicewsdl:port name=TopologyServiceSOAP11port
binding=ns:TopologyServiceSOAP11Bindingsoap:address
location=http://localhost:8080/axis2/services/TopologyService;
//wsdl:portwsdl:port name=TopologyServiceSOAP12port
binding=ns:TopologyServiceSOAP12Bindingsoap12:address
location=http://localhost:8080/axis2/services/TopologyService;
//wsdl:port/wsdl:service/wsdl:definitions
-- 
View this message in context: 
http://www.nabble.com/Problem-in-WSDL2java-with-eclipse-code-generator-tf4486812.html#a12794863
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: Problem with wsdl2java

[neiroman neiroman]

My current shell is bash.
 As I see wsdl2java is written for sh and it always executes by sh
interpretator. What will the difference, if I change my shell to zsh for
example ?

For trying another shell I must set up all JAVA enviroment variables

2007/5/28, Davanum Srinivas [EMAIL PROTECTED]:


which shell are you using? can try please try any other alternate
shell(s)?

thanks,
dims

On 5/27/07, Genious Soul [EMAIL PROTECTED] wrote:




 - Original Message 
 From: neiroman neiroman [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Saturday, May 26, 2007 7:58:38 PM
 Subject: Problem with wsdl2java

 Hello, I use Axis2 1.2
 When I try to run wsdl2java I've got the follovving  error

 [EMAIL PROTECTED]:/usr/lib/axis2 wsdl2java.sh -uri tmp.wsdl -ss -sd
  Using AXIS2_HOME:   /usr/lib/axis2
  Using JAVA_HOME:   /usr/java/jdk1.6.0
 /usr/lib/axis2/bin/axis2.sh: line 38: [: !=: unary operator expected
 Unrecognized option: -uri

  
 Don't be flakey. Get Yahoo! Mail for Mobile and
 always stay connected to friends.


--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with wsdl2java

[Amila Suriarachchi]

try replacing the sh in the wsdl2java.sh file with a  .
or use this command
sh axis2.sh org.apache.axis2.wsdl.WSDL2Java your arguments

On 5/28/07, neiroman neiroman [EMAIL PROTECTED] wrote:


My current shell is bash.
  As I see wsdl2java is written for sh and it always executes by sh
interpretator. What will the difference, if I change my shell to zsh for
example ?

For trying another shell I must set up all JAVA enviroment variables

2007/5/28, Davanum Srinivas [EMAIL PROTECTED]:

 which shell are you using? can try please try any other alternate
 shell(s)?

 thanks,
 dims

 On 5/27/07, Genious Soul [EMAIL PROTECTED] wrote:
 
 
 
 
  - Original Message 
  From: neiroman neiroman [EMAIL PROTECTED]
  To: axis-user@ws.apache.org
  Sent: Saturday, May 26, 2007 7:58:38 PM
  Subject: Problem with wsdl2java
 
  Hello, I use Axis2 1.2
  When I try to run wsdl2java I've got the follovving  error
 
  [EMAIL PROTECTED] :/usr/lib/axis2 wsdl2java.sh -uri tmp.wsdl -ss -sd
   Using AXIS2_HOME:   /usr/lib/axis2
   Using JAVA_HOME:   /usr/java/jdk1.6.0
  /usr/lib/axis2/bin/axis2.sh: line 38: [: !=: unary operator expected
  Unrecognized option: -uri
 
   
  Don't be flakey. Get Yahoo! Mail for Mobile and
  always stay connected to friends.


 --
 Davanum Srinivas :: http://davanum.wordpress.com

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






--
Amila Suriarachchi,
WSO2 Inc.

Re: Problem with wsdl2java

[Stephane Roy]

neiroman neiroman wrote:

Hello, I use Axis2 1.2
When I try to run wsdl2java I've got the follovving  error

[EMAIL PROTECTED]:/usr/lib/axis2 wsdl2java.sh -uri tmp.wsdl -ss -sd
 Using AXIS2_HOME:   /usr/lib/axis2
 Using JAVA_HOME:   /usr/java/jdk1.6.0
/usr/lib/axis2/bin/axis2.sh: line 38: [: !=: unary operator expected
Unrecognized option: -uri


I believe I had the same problem when I started to use Axis2.1.2.

I already posted a solution for this problem in a previous thread:
http://marc.info/?l=axis-userm=11787015586w=2

You may take a look at it.

Stephane Roy
Alcatel-Lucent


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with wsdl2java

[Genious Soul]

- Original Message 
From: neiroman neiroman [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Saturday, May 26, 2007 7:58:38 PM
Subject: Problem with wsdl2java

Hello, I use Axis2 1.2
When I try to run wsdl2java I've got the follovving  error

[EMAIL PROTECTED]:/usr/lib/axis2 wsdl2java.sh -uri tmp.wsdl -ss -sd
 Using AXIS2_HOME:   /usr/lib/axis2
 Using JAVA_HOME:   /usr/java/jdk1.6.0
/usr/lib/axis2/bin/axis2.sh: line 38: [: !=: unary operator expected
Unrecognized option: -uri


 

Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

Problem with wsdl2java

[neiroman neiroman]

Hello, I use Axis2 1.2
When I try to run wsdl2java I've got the follovving  error

[EMAIL PROTECTED]:/usr/lib/axis2 wsdl2java.sh -uri tmp.wsdl -ss -sd
Using AXIS2_HOME:   /usr/lib/axis2
Using JAVA_HOME:   /usr/java/jdk1.6.0
/usr/lib/axis2/bin/axis2.sh: line 38: [: !=: unary operator expected
Unrecognized option: -uri

Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports

[footh]

Funny thing is I was just coming to the list to get
clarification on this.  I poured through the specs and
couldn't find where it was explicitly stated as
illegal.

So, then I assume Amila's fix is the official
correction of the problem.  Thanks everyone for your
input.

--- Anne Thomas Manes [EMAIL PROTECTED] wrote:

 I asked for clarification on the xml-dev list.
 Michael Kay concurs with Dennis.
 Duplicate child elements are allowed, even when
 elementFormDefault=qualified.
 
 Anne
 
 On 3/8/07, Anne Thomas Manes [EMAIL PROTECTED]
 wrote:
  Maybe we should ask for clarification from
 Priscilla on this, but my
  intepretation of
 
   Locally scoped attribute and element
 declarations
 
  is that the rule refers only to unqualified
 attributes and elements.
  If you specify elementFormDefault=qualified,
 then all elements in
  the schema are globally scoped unless you specify
 form=unqualified
  on a specific element.
 
  Anne
 
  On 3/8/07, Dennis Sosnoski [EMAIL PROTECTED]
 wrote:
   Hi Amila,
  
   No, there is no such constraint. Schema actually
 states explicitly
  

(http://www.w3.org/TR/xmlschema-1/#concepts-nameSymbolSpaces)
 that:
  
   Locally scoped attribute and element
 declarations are special with
   regard to symbol spaces. Every complex type
 definition defines its own
   local attribute and element declaration symbol
 spaces, where these
   symbol spaces are distinct from each other and
 from any of the other
   symbol spaces. So, for example, two complex type
 definitions having the
   same target namespace can contain a local
 attribute declaration for the
   unqualified name priority, or contain a local
 element declaration for
   the name address, without conflict or
 necessary relation between the two.
  
   Like most parts of the schema specification,
 this doesn't appear to be
   written for clarity. Why the gratuitous
 reference to unqualified name
   when referring to the attribute, for instance,
 when it doesn't make any
   difference whether the name is qualified or
 unqualified? But the
   statement that each complex type definition
 defines its own local
   attribute and element declaration symbol spaces
 is as clear and
   definite as anything in schema.
  
   To make things even more complicated, according
 to Priscilla Walmsley
   (Definitive XML Schema, 13.4.4 Duplication of
 element-type names) you
   can reuse the same element name within a
 particular complex type
   definition providing the elements have the same
 type. This apparently
   means that it's fine to do a definition of the
 type:
  
   complexType
 sequence
   element name=name type=string/
   element name=id type=long/
   element name=name type=string/
 /sequence
   /complexType
  
   I don't know the particular entrails which were
 read to come to this
   conclusion (which I haven't found documented in
 the schema
   recommendation), but since she's part of the
 Schema Working Group her
   statements on schema are generally considered
 authoritative. Something
   to keep in mind when you're writing your code to
 handle complex types.
  
 - Dennis
  
   Dennis M. Sosnoski
   SOA and Web Services in Java
   Training and Consulting
   http://www.sosnoski.com -
 http://www.sosnoski.co.nz
   Seattle, WA +1-425-939-0576 - Wellington, NZ
 +64-4-298-6117
  
  
  
   Amila Suriarachchi wrote:
   
   
On 3/8/07, *Dennis Sosnoski* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
   
Your statement about the names is
 incorrect, Anne. Schema doesn't
allow
the same name to be used for different
 global definitions, but you're
fine reusing names for local elements in
 different complexTypes.
   
I am also not clear about this and would like
 to put this question?
Is there any constranit that says *every
 element in schema should have
a unique Qutalified name?*
since the qualified name of an element only
 depends on the namespace
and the local part of the element then we have
 to conclude that it is
not possible.
   
--
Amila Suriarachchi,
WSO2 Inc.
  
  

-
   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]
 
 



 

No need to miss a message. Get email on-the-go 
with Yahoo! Mail for Mobile. Get started.
http://mobile.yahoo.com/mail 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports

[Dennis Sosnoski]

Sorry I didn't notice your earlier response on this, Anne. The schema 
specification is explicit that each complex type defines its own symbol 
spaces for the element and attribute definitions within that type, as I 
quoted. The locally scoped reference just means that it's not a 
top-level child of the schema element - top-level children of the schema 
are global definitions (and globally-scoped, meaning they're visible 
throughout the schema and also when the schema is included or imported), 
everything else is a local definition.


The added part that I referenced Priscilla on was just that the same 
element or attribute name could be reused within a single complex type 
definition, providing all uses specify the same type. That's something I 
haven't found as part of the schema specification, but was passing on to 
Amila as something to keep in mind when implementing the code.


 - Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Anne Thomas Manes wrote:
I asked for clarification on the xml-dev list. Michael Kay concurs 
with Dennis.
Duplicate child elements are allowed, even when 
elementFormDefault=qualified.


Anne

On 3/8/07, Anne Thomas Manes [EMAIL PROTECTED] wrote:

Maybe we should ask for clarification from Priscilla on this, but my
intepretation of

 Locally scoped attribute and element declarations

is that the rule refers only to unqualified attributes and elements.
If you specify elementFormDefault=qualified, then all elements in
the schema are globally scoped unless you specify form=unqualified
on a specific element.

Anne

On 3/8/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
 Hi Amila,

 No, there is no such constraint. Schema actually states explicitly
 (http://www.w3.org/TR/xmlschema-1/#concepts-nameSymbolSpaces) that:

 Locally scoped attribute and element declarations are special with
 regard to symbol spaces. Every complex type definition defines its own
 local attribute and element declaration symbol spaces, where these
 symbol spaces are distinct from each other and from any of the other
 symbol spaces. So, for example, two complex type definitions having 
the
 same target namespace can contain a local attribute declaration for 
the
 unqualified name priority, or contain a local element declaration 
for
 the name address, without conflict or necessary relation between 
the two.


 Like most parts of the schema specification, this doesn't appear to be
 written for clarity. Why the gratuitous reference to unqualified 
name
 when referring to the attribute, for instance, when it doesn't make 
any

 difference whether the name is qualified or unqualified? But the
 statement that each complex type definition defines its own local
 attribute and element declaration symbol spaces is as clear and
 definite as anything in schema.

 To make things even more complicated, according to Priscilla Walmsley
 (Definitive XML Schema, 13.4.4 Duplication of element-type names) 
you

 can reuse the same element name within a particular complex type
 definition providing the elements have the same type. This apparently
 means that it's fine to do a definition of the type:

 complexType
   sequence
 element name=name type=string/
 element name=id type=long/
 element name=name type=string/
   /sequence
 /complexType

 I don't know the particular entrails which were read to come to this
 conclusion (which I haven't found documented in the schema
 recommendation), but since she's part of the Schema Working Group her
 statements on schema are generally considered authoritative. Something
 to keep in mind when you're writing your code to handle complex types.

   - Dennis

 Dennis M. Sosnoski
 SOA and Web Services in Java
 Training and Consulting
 http://www.sosnoski.com - http://www.sosnoski.co.nz
 Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



 Amila Suriarachchi wrote:
 
 
  On 3/8/07, *Dennis Sosnoski* [EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED] wrote:
 
  Your statement about the names is incorrect, Anne. Schema 
doesn't

  allow
  the same name to be used for different global definitions, 
but you're

  fine reusing names for local elements in different complexTypes.
 
  I am also not clear about this and would like to put this question?
  Is there any constranit that says *every element in schema should 
have

  a unique Qutalified name?*
  since the qualified name of an element only depends on the namespace
  and the local part of the element then we have to conclude that 
it is

  not possible.
 
  --
  Amila Suriarachchi,
  WSO2 Inc.

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL 

Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports

[Dennis Sosnoski]

Hi Amila,

No, there is no such constraint. Schema actually states explicitly 
(http://www.w3.org/TR/xmlschema-1/#concepts-nameSymbolSpaces) that:


Locally scoped attribute and element declarations are special with 
regard to symbol spaces. Every complex type definition defines its own 
local attribute and element declaration symbol spaces, where these 
symbol spaces are distinct from each other and from any of the other 
symbol spaces. So, for example, two complex type definitions having the 
same target namespace can contain a local attribute declaration for the 
unqualified name priority, or contain a local element declaration for 
the name address, without conflict or necessary relation between the two.


Like most parts of the schema specification, this doesn't appear to be 
written for clarity. Why the gratuitous reference to unqualified name 
when referring to the attribute, for instance, when it doesn't make any 
difference whether the name is qualified or unqualified? But the 
statement that each complex type definition defines its own local 
attribute and element declaration symbol spaces is as clear and 
definite as anything in schema.


To make things even more complicated, according to Priscilla Walmsley 
(Definitive XML Schema, 13.4.4 Duplication of element-type names) you 
can reuse the same element name within a particular complex type 
definition providing the elements have the same type. This apparently 
means that it's fine to do a definition of the type:


complexType
 sequence
   element name=name type=string/
   element name=id type=long/
   element name=name type=string/
 /sequence
/complexType

I don't know the particular entrails which were read to come to this 
conclusion (which I haven't found documented in the schema 
recommendation), but since she's part of the Schema Working Group her 
statements on schema are generally considered authoritative. Something 
to keep in mind when you're writing your code to handle complex types.


 - Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Amila Suriarachchi wrote:



On 3/8/07, *Dennis Sosnoski* [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:


Your statement about the names is incorrect, Anne. Schema doesn't
allow
the same name to be used for different global definitions, but you're
fine reusing names for local elements in different complexTypes.

I am also not clear about this and would like to put this question?
Is there any constranit that says *every element in schema should have 
a unique Qutalified name?*
since the qualified name of an element only depends on the namespace 
and the local part of the element then we have to conclude that it is 
not possible.


--
Amila Suriarachchi,
WSO2 Inc. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports

[Anne Thomas Manes]

Maybe we should ask for clarification from Priscilla on this, but my
intepretation of

Locally scoped attribute and element declarations

is that the rule refers only to unqualified attributes and elements.
If you specify elementFormDefault=qualified, then all elements in
the schema are globally scoped unless you specify form=unqualified
on a specific element.

Anne

On 3/8/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:

Hi Amila,

No, there is no such constraint. Schema actually states explicitly
(http://www.w3.org/TR/xmlschema-1/#concepts-nameSymbolSpaces) that:

Locally scoped attribute and element declarations are special with
regard to symbol spaces. Every complex type definition defines its own
local attribute and element declaration symbol spaces, where these
symbol spaces are distinct from each other and from any of the other
symbol spaces. So, for example, two complex type definitions having the
same target namespace can contain a local attribute declaration for the
unqualified name priority, or contain a local element declaration for
the name address, without conflict or necessary relation between the two.

Like most parts of the schema specification, this doesn't appear to be
written for clarity. Why the gratuitous reference to unqualified name
when referring to the attribute, for instance, when it doesn't make any
difference whether the name is qualified or unqualified? But the
statement that each complex type definition defines its own local
attribute and element declaration symbol spaces is as clear and
definite as anything in schema.

To make things even more complicated, according to Priscilla Walmsley
(Definitive XML Schema, 13.4.4 Duplication of element-type names) you
can reuse the same element name within a particular complex type
definition providing the elements have the same type. This apparently
means that it's fine to do a definition of the type:

complexType
  sequence
element name=name type=string/
element name=id type=long/
element name=name type=string/
  /sequence
/complexType

I don't know the particular entrails which were read to come to this
conclusion (which I haven't found documented in the schema
recommendation), but since she's part of the Schema Working Group her
statements on schema are generally considered authoritative. Something
to keep in mind when you're writing your code to handle complex types.

  - Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Amila Suriarachchi wrote:


 On 3/8/07, *Dennis Sosnoski* [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED] wrote:

 Your statement about the names is incorrect, Anne. Schema doesn't
 allow
 the same name to be used for different global definitions, but you're
 fine reusing names for local elements in different complexTypes.

 I am also not clear about this and would like to put this question?
 Is there any constranit that says *every element in schema should have
 a unique Qutalified name?*
 since the qualified name of an element only depends on the namespace
 and the local part of the element then we have to conclude that it is
 not possible.

 --
 Amila Suriarachchi,
 WSO2 Inc.

-
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] Problem running wsdl2java on wsdl with multiple imports

[Anne Thomas Manes]

I asked for clarification on the xml-dev list. Michael Kay concurs with Dennis.
Duplicate child elements are allowed, even when elementFormDefault=qualified.

Anne

On 3/8/07, Anne Thomas Manes [EMAIL PROTECTED] wrote:

Maybe we should ask for clarification from Priscilla on this, but my
intepretation of

 Locally scoped attribute and element declarations

is that the rule refers only to unqualified attributes and elements.
If you specify elementFormDefault=qualified, then all elements in
the schema are globally scoped unless you specify form=unqualified
on a specific element.

Anne

On 3/8/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
 Hi Amila,

 No, there is no such constraint. Schema actually states explicitly
 (http://www.w3.org/TR/xmlschema-1/#concepts-nameSymbolSpaces) that:

 Locally scoped attribute and element declarations are special with
 regard to symbol spaces. Every complex type definition defines its own
 local attribute and element declaration symbol spaces, where these
 symbol spaces are distinct from each other and from any of the other
 symbol spaces. So, for example, two complex type definitions having the
 same target namespace can contain a local attribute declaration for the
 unqualified name priority, or contain a local element declaration for
 the name address, without conflict or necessary relation between the two.

 Like most parts of the schema specification, this doesn't appear to be
 written for clarity. Why the gratuitous reference to unqualified name
 when referring to the attribute, for instance, when it doesn't make any
 difference whether the name is qualified or unqualified? But the
 statement that each complex type definition defines its own local
 attribute and element declaration symbol spaces is as clear and
 definite as anything in schema.

 To make things even more complicated, according to Priscilla Walmsley
 (Definitive XML Schema, 13.4.4 Duplication of element-type names) you
 can reuse the same element name within a particular complex type
 definition providing the elements have the same type. This apparently
 means that it's fine to do a definition of the type:

 complexType
   sequence
 element name=name type=string/
 element name=id type=long/
 element name=name type=string/
   /sequence
 /complexType

 I don't know the particular entrails which were read to come to this
 conclusion (which I haven't found documented in the schema
 recommendation), but since she's part of the Schema Working Group her
 statements on schema are generally considered authoritative. Something
 to keep in mind when you're writing your code to handle complex types.

   - Dennis

 Dennis M. Sosnoski
 SOA and Web Services in Java
 Training and Consulting
 http://www.sosnoski.com - http://www.sosnoski.co.nz
 Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



 Amila Suriarachchi wrote:
 
 
  On 3/8/07, *Dennis Sosnoski* [EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED] wrote:
 
  Your statement about the names is incorrect, Anne. Schema doesn't
  allow
  the same name to be used for different global definitions, but you're
  fine reusing names for local elements in different complexTypes.
 
  I am also not clear about this and would like to put this question?
  Is there any constranit that says *every element in schema should have
  a unique Qutalified name?*
  since the qualified name of an element only depends on the namespace
  and the local part of the element then we have to conclude that it is
  not possible.
 
  --
  Amila Suriarachchi,
  WSO2 Inc.

 -
 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] Problem running wsdl2java on wsdl with multiple imports

[Anne Thomas Manes]

Given that the schema specified elementFormDefault=qualified, the
schema is invalid. You cannot define two elements in a single
namespace with the same local name. The proper fix to Axis2 would be
to generate an error that flags the problem.

The proper fix to the schema is to create a global element called URL
and ref the element from the complex type definitions.

Note also that the first schema (the one imported into the WSDL)
includes a number of element definitions with no type definitions.
e.g.,

   xsd:element name=LoadBlogRequest /

These definitions default to xsd:anyType, which will cause lots of
interop problems. My interpretation of the schema is that these
elements are intended to contain nothing -- basically a void type. If
that is the intention, they should be defined as follows:

  xsd:element name=LoadBlogRequest 
xsd:complexType /
  /xsd:element

Anne

On 3/7/07, Amila Suriarachchi [EMAIL PROTECTED] wrote:

The problem was you had two complex types contain same element name
eg.
 xsd:complexType name=
Entry
 xsd:element name=URL
minOccurs=0 maxOccurs=1
 xsd:simpleType

 xsd:restriction base=xsd:string
 xsd:minLength
 value=0 /
 xsd:maxLength
 value=255 /
 /xsd:restriction
 /xsd:simpleType


 /xsd:element
 /xsd:complexType

and
xsd:complexType
 name=Entry_Reply
 xsd:all minOccurs=0
maxOccurs=1
 xsd:element name=
URL minOccurs=0 maxOccurs=1

 xsd:simpleType
 xsd:restriction base=xsd:string

 xsd:minLength value=0 /
 
xsd:maxLength value=255 /
 /xsd:restriction

 /xsd:simpleType
 /xsd:element
I fixed this by generating a unique suffix. Please check with a nightly
build


 --
Amila Suriarachchi,
WSO2 Inc.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports

[footh]

Thanks both for your responses.  I will inform the
vendor that the schemas need to be corrected.

--- Anne Thomas Manes [EMAIL PROTECTED] wrote:

 Given that the schema specified
 elementFormDefault=qualified, the
 schema is invalid. You cannot define two elements in
 a single
 namespace with the same local name. The proper fix
 to Axis2 would be
 to generate an error that flags the problem.
 
 The proper fix to the schema is to create a global
 element called URL
 and ref the element from the complex type
 definitions.
 
 Note also that the first schema (the one imported
 into the WSDL)
 includes a number of element definitions with no
 type definitions.
 e.g.,
 
 xsd:element name=LoadBlogRequest /
 
 These definitions default to xsd:anyType, which will
 cause lots of
 interop problems. My interpretation of the schema is
 that these
 elements are intended to contain nothing --
 basically a void type. If
 that is the intention, they should be defined as
 follows:
 
xsd:element name=LoadBlogRequest 
  xsd:complexType /
/xsd:element
 
 Anne
 
 On 3/7/07, Amila Suriarachchi
 [EMAIL PROTECTED] wrote:
  The problem was you had two complex types contain
 same element name
  eg.
   xsd:complexType name=
  Entry
   xsd:element name=URL
  minOccurs=0 maxOccurs=1
   xsd:simpleType
  
   xsd:restriction base=xsd:string
   xsd:minLength
   value=0 /
   xsd:maxLength
   value=255 /
   /xsd:restriction
   /xsd:simpleType
  
 
   /xsd:element
   /xsd:complexType
 
  and
  xsd:complexType
   name=Entry_Reply
   xsd:all minOccurs=0
  maxOccurs=1
   xsd:element name=
  URL minOccurs=0 maxOccurs=1
 
   xsd:simpleType
   xsd:restriction base=xsd:string
 
   xsd:minLength value=0 /
   
  xsd:maxLength value=255 /
   /xsd:restriction
 
   /xsd:simpleType
   /xsd:element
  I fixed this by generating a unique suffix. Please
 check with a nightly
  build
 
 
   --
  Amila Suriarachchi,
  WSO2 Inc.
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 



 

Don't get soaked.  Take a quick peek at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports

[Ajith Ranabahu]

Hi,
Please correct me if I'm wrong here. AFAIU while its wrong to have the
same name in two top level elements when the schema elementFormDefault
is qualified, elements declared inside the complex type can have the
same name if they are enclosed in different complex types. In other
words if the elements are enclosed in a type they only need to be
unique in that scope and not the global scope ?

I did not find any duplicate top level elements or types in the given
schemas and they seem correct to me.


Ajith


On 3/7/07, footh [EMAIL PROTECTED] wrote:

Thanks both for your responses.  I will inform the
vendor that the schemas need to be corrected.

--- Anne Thomas Manes [EMAIL PROTECTED] wrote:

 Given that the schema specified
 elementFormDefault=qualified, the
 schema is invalid. You cannot define two elements in
 a single
 namespace with the same local name. The proper fix
 to Axis2 would be
 to generate an error that flags the problem.

 The proper fix to the schema is to create a global
 element called URL
 and ref the element from the complex type
 definitions.

 Note also that the first schema (the one imported
 into the WSDL)
 includes a number of element definitions with no
 type definitions.
 e.g.,

 xsd:element name=LoadBlogRequest /

 These definitions default to xsd:anyType, which will
 cause lots of
 interop problems. My interpretation of the schema is
 that these
 elements are intended to contain nothing --
 basically a void type. If
 that is the intention, they should be defined as
 follows:

xsd:element name=LoadBlogRequest 
  xsd:complexType /
/xsd:element

 Anne

 On 3/7/07, Amila Suriarachchi
 [EMAIL PROTECTED] wrote:
  The problem was you had two complex types contain
 same element name
  eg.
   xsd:complexType name=
  Entry
   xsd:element name=URL
  minOccurs=0 maxOccurs=1
   xsd:simpleType
  
   xsd:restriction base=xsd:string
   xsd:minLength
   value=0 /
   xsd:maxLength
   value=255 /
   /xsd:restriction
   /xsd:simpleType
  
 
   /xsd:element
   /xsd:complexType
 
  and
  xsd:complexType
   name=Entry_Reply
   xsd:all minOccurs=0
  maxOccurs=1
   xsd:element name=
  URL minOccurs=0 maxOccurs=1
 
   xsd:simpleType
   xsd:restriction base=xsd:string
 
   xsd:minLength value=0 /
   
  xsd:maxLength value=255 /
   /xsd:restriction
 
   /xsd:simpleType
   /xsd:element
  I fixed this by generating a unique suffix. Please
 check with a nightly
  build
 
 
   --
  Amila Suriarachchi,
  WSO2 Inc.


-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]







Don't get soaked.  Take a quick peek at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather

-
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] Problem running wsdl2java on wsdl with multiple imports

[Dennis Sosnoski]

Your statement about the names is incorrect, Anne. Schema doesn't allow 
the same name to be used for different global definitions, but you're 
fine reusing names for local elements in different complexTypes.


 - Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Anne Thomas Manes wrote:

Given that the schema specified elementFormDefault=qualified, the
schema is invalid. You cannot define two elements in a single
namespace with the same local name. The proper fix to Axis2 would be
to generate an error that flags the problem.

The proper fix to the schema is to create a global element called URL
and ref the element from the complex type definitions.

Note also that the first schema (the one imported into the WSDL)
includes a number of element definitions with no type definitions.
e.g.,

   xsd:element name=LoadBlogRequest /

These definitions default to xsd:anyType, which will cause lots of
interop problems. My interpretation of the schema is that these
elements are intended to contain nothing -- basically a void type. If
that is the intention, they should be defined as follows:

  xsd:element name=LoadBlogRequest 
xsd:complexType /
  /xsd:element

Anne

On 3/7/07, Amila Suriarachchi [EMAIL PROTECTED] wrote:

The problem was you had two complex types contain same element name
eg.
 xsd:complexType name=
Entry
 xsd:element name=URL
minOccurs=0 maxOccurs=1
 xsd:simpleType

 xsd:restriction base=xsd:string
 xsd:minLength
 value=0 /
 xsd:maxLength
 value=255 /
 /xsd:restriction
 /xsd:simpleType


 /xsd:element
 /xsd:complexType

and
xsd:complexType
 name=Entry_Reply
 xsd:all minOccurs=0
maxOccurs=1
 xsd:element name=
URL minOccurs=0 maxOccurs=1

 xsd:simpleType
 xsd:restriction base=xsd:string

 xsd:minLength value=0 /
 
xsd:maxLength value=255 /
 /xsd:restriction

 /xsd:simpleType
 /xsd:element
I fixed this by generating a unique suffix. Please check with a nightly
build


 --
Amila Suriarachchi,
WSO2 Inc.


-
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] Problem running wsdl2java on wsdl with multiple imports

[Amila Suriarachchi]

On 3/8/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:


Your statement about the names is incorrect, Anne. Schema doesn't allow
the same name to be used for different global definitions, but you're
fine reusing names for local elements in different complexTypes.

I am also not clear about this and would like to put this question?

Is there any constranit that says *every element in schema should have a
unique Qutalified name?*
since the qualified name of an element only depends on the namespace and the
local part of the element then we have to conclude that it is not possible.

--
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Problem running wsdl2java on wsdl with multiple imports

[Amila Suriarachchi]

The problem was you had two complex types contain same element name
eg.

   xsd:complexType name=Entry
  xsd:element name=URL minOccurs=0
maxOccurs=1
xsd:simpleType
xsd:restriction 
base=xsd:string
xsd:minLength value=0 
/
xsd:maxLength value=255 
/
/xsd:restriction
/xsd:simpleType

/xsd:element
/xsd:complexType

and
xsd:complexType name=Entry_Reply
xsd:all minOccurs=0 maxOccurs=1
xsd:element name=URL minOccurs=0 
maxOccurs=1
xsd:simpleType
xsd:restriction 
base=xsd:string
xsd:minLength value=0 
/
xsd:maxLength value=255 
/
/xsd:restriction
/xsd:simpleType
/xsd:element

I fixed this by generating a unique suffix. Please check with a nightly
build


--
Amila Suriarachchi,
WSO2 Inc.

problem with wsdl2java

[Flood, Brendan \(Brendan\) ** CTR **]

I am having a problem with the generated code from wsdl2java
if I have a complexType with one element and several attributes. Here is my
complexType




complexType name=SomeData


sequence


element name=data type=string maxOccurs=unbounded/


/sequence


attribute name=attr1 type=boolean default=false/


attribute name=attr2 type=boolean default=true/


attribute name=attr3 type=boolean default=true/


/complexType




What happens is no code is generated for
the SomeData class and if I include the element of type SomeData in another type,
the generated code shows up as String[] data, so I only get the element. If I
add a 2nd element to the sequence (see below) then I get a SomeData
class generated and this has the elements and attributes in it. I am using Axis
1.3 (I believe RC2, I downloaded it a while ago).




complexType name=SomeData


sequence


element name=data type=string maxOccurs=unbounded/


element name=elem2 type=string/


/sequence


attribute name=attr1 type=boolean default=false/


attribute name=attr2 type=boolean default=true/


attribute name=attr3 type=boolean default=true/


/complexType



Let me know if this is a known problem that may have been fixed in a
later release or if I am doing something wrong.



Thanks,

Brendan Flood,

Re: problem with wsdl2java

[Martin Gainty]

Brendan-
write a bean classwhich 
willmanually encapsulates all of the items as attrbutes of your bean 
class
Then implement the beanclass in your wsdl as 
ComplexDatatype as in this example
wsdl:types schema 
xmlns="http://www.w3.org/2001/XMLSchema" 
targetNamespace="http://weather" import 
namespace="http://schemas.xmlsoap.org/soap/encoding/"/ 
complexType name="YourComplexDataType" 
sequence element name="zip" 
nillable="true" type="xsd:string"/
great example located here
http://www-128.ibm.com/developerworks/webservices/library/ws-complex.htmlHTH,
Martin

This e-mail communication and any attachments may contain confidential and 
privileged information for the use of the designated recipients named above. 
If you are not the intended recipient, you are hereby notified that you have 
receivedthis communication in error and that any review, disclosure, 
dissemination, distribution or copying of it or its contents

  - Original Message - 
  From: 
  Flood, Brendan 
  (Brendan) ** CTR ** 
  To: axis-user@ws.apache.org 
  Sent: Wednesday, October 11, 2006 3:34 
  PM
  Subject: problem with wsdl2java
  
  
  I am having a problem with the 
  generated code from wsdl2java if I have a complexType with one element and 
  several attributes. Here is my complexType
  
   
  complexType name="SomeData"
   
  sequence
   
  element name="data" type="string" 
  maxOccurs="unbounded"/
   
  /sequence
   
  attribute name="attr1" type="boolean" 
  default="false"/
   
  attribute name="attr2" type="boolean" 
  default="true"/
   
  attribute name="attr3" type="boolean" 
  default="true"/
   
  /complexType
   
  
  What happens is no code is generated for 
  the SomeData class and if I include the element of type SomeData in another 
  type, the generated code shows up as String[] data, so I only get the element. 
  If I add a 2nd element to the sequence (see below) then I get a 
  SomeData class generated and this has the elements and attributes in it. I am 
  using Axis 1.3 (I believe RC2, I downloaded it a while 
  ago).
  
   
  complexType name="SomeData"
   
  sequence
   
  element name="data" type="string" 
  maxOccurs="unbounded"/
   
  element name="elem2" type="string"/
   
  /sequence
   
  attribute name="attr1" type="boolean" 
  default="false"/
   
  attribute name="attr2" type="boolean" 
  default="true"/
   
  attribute name="attr3" type="boolean" 
  default="true"/
   
  /complexType
  
  Let me know if this is a known problem that may have 
  been fixed in a later release or if I am doing something 
  wrong.
  
  Thanks,
  Brendan Flood,
  
  

problem with WSDL2Java generated code

[Yadav, Yogendra \(IT\)]

I have 
generatedcode using wsdl2java. Then I wrote a Client.java to call web 
service, while excuting the client I get ClassNotFoundException in 
LoginDocument.java class which is generated by wsdl2java 
"schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder"


C:\work\os-ag-onbank1\codejava -cp 
build\classes;C:\software\axis2\lib\axis2-kernel-SNAPSHOT.jar;C:\software\axis2\lib\xbean-2.2.0.jar;.;C:\software\axis2\lib\axiom-api-1.1.1.jar;C:\software\axis2\lib\stax-api-1.0.1.jar;C:\software\axis2\lib\wsdl4j-1.6.1.jar;C:\software\axis2\lib\XmlSchema-SNAPSHOT.jar;C:\software\axis2\lib\commons-logging-1.1.jar;C:\software\axis2\lib\neethi-SNAPSHOT.jar;C:\software\axis2\lib\stax-1.2.0.jar;C:\software\axis2\lib\axiom-impl-1.1.1.jar;C:\software\axis2\lib\xbean-2.2.0.jar;ClientException 
in thread "main" 
java.lang.ExceptionInInitializerError 
at 
com.example.www.onlinebanking.xsd.LoginDocument$Factory.newInstance(LoginDocument.java:112) 
at Client.login(Client.java:40) at 
Client.main(Client.java:17)Caused by: java.lang.RuntimeException: Cannot 
load SchemaTypeSystem. Unable to load class with name 
schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder. 
Make sure the generated binary files are on the 
classpath. at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783) 
at 
com.example.www.onlinebanking.xsd.LoginDocument.clinit(LoginDocument.java:19) 
... 3 moreCaused by: java.lang.ClassNotFoundException: 
schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder 
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 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) 
at 
java.lang.ClassLoader.loadClass(ClassLoader.java:251) 
at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769) 
... 4 more

any help will be 
appreciated.
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.

RE: problem with WSDL2Java generated code

[Yadav, Yogendra \(IT\)]

I am getting the same errorrunning client for 
Axis2SampleDocLitService WSDL as well. The client code looks like 
this:
import org.apache.axis2.userguide.xsd.*;import 
org.apache.axis2.userguide.xsd.impl.*;import 
com.sample.*;

import java.util.*;

public class Client{

 public static void main(java.lang.String 
args[]){ 
Axis2SampleDocLitServiceStub stub = 
null; 
try{ stub 
= new 
Axis2SampleDocLitServiceStub(null, 
"http://localhost:8080/axis2/services/Axis2SampleDocLitService"); 
 
echoString(stub); } 
catch(Exception 
e){ 
e.printStackTrace(); 
} }

 public static String 
echoString(Axis2SampleDocLitServiceStub 
stub){ 
try{ 
EchoStringParamDocument reqDoc00 = 
EchoStringParamDocument.Factory.newInstance(); 
reqDoc00.setEchoStringParam("echo");

 
EchoStringReturnDocument resDoc00 = 
stub.echoString(reqDoc00);

 return 
resDoc00.getEchoStringReturn(); } 
catch(Exception 
e){ 
e.printStackTrace(); 
} return 
null; }

}

The runtime exception is:
C:\work\Axis2Samplejava -cp 
build\classes;C:\software\axis2\lib\axis2-kernel-SNAPSHOT.jar;C:\software\axis2\lib\xbean-2.2.0.jar;.;C:\software\axis2\lib\axiom-api-1.1.1.jar;C:\software\axis2\lib\stax-api-1.0.1.jar;C:\software\axis2\lib\wsdl4j-1.6.1.jar;C:\software\axis2\lib\XmlSchema-SNAPSHOT.jar;C:\software\axis2\lib\commons-logging-1.1.jar;C:\software\axis2\lib\neethi-SNAPSHOT.jar;C:\software\axis2\lib\stax-1.2.0.jar;C:\software\axis2\lib\axiom-impl-1.1.1.jar;C:\software\axis2\lib\xbean-2.2.0.jar;ClientException 
in thread "main" 
java.lang.ExceptionInInitializerError 
at 
org.apache.axis2.userguide.xsd.EchoStringParamDocument$Factory.newInstance(EchoStringParamDocument.java:50) 
at 
Client.echoString(Client.java:23) 
at Client.main(Client.java:15)Caused by: java.lang.RuntimeException: Cannot 
load SchemaTypeSystem. Unable to load class with name 
schemaorg_apache_xmlbeans.system.s0C55B8F5926240E3576E190A4CD282A2.TypeSystemHolder. 
Make sure the generated binary files are on the 
classpath. at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783) 
at 
org.apache.axis2.userguide.xsd.EchoStringParamDocument.clinit(EchoStringParamDocument.java:19) 
... 3 moreCaused by: java.lang.ClassNotFoundException: 
schemaorg_apache_xmlbeans.system.s0C55B8F5926240E3576E190A4CD282A2.TypeSystemHolder 
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 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) 
at 
java.lang.ClassLoader.loadClass(ClassLoader.java:251) 
at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769) 
... 4 more

What am I doing wrong ?


From: Yadav, Yogendra (IT) Sent: 
Wednesday, October 04, 2006 1:13 PMTo: 
axis-user@ws.apache.orgSubject: problem with WSDL2Java generated code 



I have 
generatedcode using wsdl2java. Then I wrote a Client.java to call web 
service, while excuting the client I get ClassNotFoundException in 
LoginDocument.java class which is generated by wsdl2java 
"schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder"


C:\work\os-ag-onbank1\codejava -cp 
build\classes;C:\software\axis2\lib\axis2-kernel-SNAPSHOT.jar;C:\software\axis2\lib\xbean-2.2.0.jar;.;C:\software\axis2\lib\axiom-api-1.1.1.jar;C:\software\axis2\lib\stax-api-1.0.1.jar;C:\software\axis2\lib\wsdl4j-1.6.1.jar;C:\software\axis2\lib\XmlSchema-SNAPSHOT.jar;C:\software\axis2\lib\commons-logging-1.1.jar;C:\software\axis2\lib\neethi-SNAPSHOT.jar;C:\software\axis2\lib\stax-1.2.0.jar;C:\software\axis2\lib\axiom-impl-1.1.1.jar;C:\software\axis2\lib\xbean-2.2.0.jar;ClientException 
in thread "main" 
java.lang.ExceptionInInitializerError 
at 
com.example.www.onlinebanking.xsd.LoginDocument$Factory.newInstance(LoginDocument.java:112) 
at Client.login(Client.java:40) at 
Client.main(Client.java:17)Caused by: java.lang.RuntimeException: Cannot 
load SchemaTypeSystem. Unable to load class with name 
schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder. 
Make sure the generated binary files are on the 
classpath. at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783) 
at 
com.example.www.onlinebanking.xsd.LoginDocument.clinit(LoginDocument.java:19) 
... 3 moreCaused by: java.lang.ClassNotFoundException: 
schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder 
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 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) 
at 
java.lang.ClassLoader.loadClass(ClassLoader.java:251) 
at 
org.apache.xmlbeans.XmlBeans.typeSystemForCl

RE: problem with WSDL2Java generated code

[Yadav, Yogendra \(IT\)]

never mind resolved: included resource directory generated 
by wsdl2java in the classpath


From: Yadav, Yogendra (IT) Sent: 
Wednesday, October 04, 2006 3:40 PMTo: 
axis-user@ws.apache.orgSubject: RE: problem with WSDL2Java generated 
code 


I am getting the same errorrunning client for 
Axis2SampleDocLitService WSDL as well. The client code looks like 
this:
import org.apache.axis2.userguide.xsd.*;import 
org.apache.axis2.userguide.xsd.impl.*;import 
com.sample.*;

import java.util.*;

public class Client{

 public static void main(java.lang.String 
args[]){ 
Axis2SampleDocLitServiceStub stub = 
null; 
try{ stub 
= new 
Axis2SampleDocLitServiceStub(null, 
"http://localhost:8080/axis2/services/Axis2SampleDocLitService"); 
 
echoString(stub); } 
catch(Exception 
e){ 
e.printStackTrace(); 
} }

 public static String 
echoString(Axis2SampleDocLitServiceStub 
stub){ 
try{ 
EchoStringParamDocument reqDoc00 = 
EchoStringParamDocument.Factory.newInstance(); 
reqDoc00.setEchoStringParam("echo");

 
EchoStringReturnDocument resDoc00 = 
stub.echoString(reqDoc00);

 return 
resDoc00.getEchoStringReturn(); } 
catch(Exception 
e){ 
e.printStackTrace(); 
} return 
null; }

}

The runtime exception is:
C:\work\Axis2Samplejava -cp 
build\classes;C:\software\axis2\lib\axis2-kernel-SNAPSHOT.jar;C:\software\axis2\lib\xbean-2.2.0.jar;.;C:\software\axis2\lib\axiom-api-1.1.1.jar;C:\software\axis2\lib\stax-api-1.0.1.jar;C:\software\axis2\lib\wsdl4j-1.6.1.jar;C:\software\axis2\lib\XmlSchema-SNAPSHOT.jar;C:\software\axis2\lib\commons-logging-1.1.jar;C:\software\axis2\lib\neethi-SNAPSHOT.jar;C:\software\axis2\lib\stax-1.2.0.jar;C:\software\axis2\lib\axiom-impl-1.1.1.jar;C:\software\axis2\lib\xbean-2.2.0.jar;ClientException 
in thread "main" 
java.lang.ExceptionInInitializerError 
at 
org.apache.axis2.userguide.xsd.EchoStringParamDocument$Factory.newInstance(EchoStringParamDocument.java:50) 
at 
Client.echoString(Client.java:23) 
at Client.main(Client.java:15)Caused by: java.lang.RuntimeException: Cannot 
load SchemaTypeSystem. Unable to load class with name 
schemaorg_apache_xmlbeans.system.s0C55B8F5926240E3576E190A4CD282A2.TypeSystemHolder. 
Make sure the generated binary files are on the 
classpath. at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783) 
at 
org.apache.axis2.userguide.xsd.EchoStringParamDocument.clinit(EchoStringParamDocument.java:19) 
... 3 moreCaused by: java.lang.ClassNotFoundException: 
schemaorg_apache_xmlbeans.system.s0C55B8F5926240E3576E190A4CD282A2.TypeSystemHolder 
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 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) 
at 
java.lang.ClassLoader.loadClass(ClassLoader.java:251) 
at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769) 
... 4 more

What am I doing wrong ?


From: Yadav, Yogendra (IT) Sent: 
Wednesday, October 04, 2006 1:13 PMTo: 
axis-user@ws.apache.orgSubject: problem with WSDL2Java generated code 



I have 
generatedcode using wsdl2java. Then I wrote a Client.java to call web 
service, while excuting the client I get ClassNotFoundException in 
LoginDocument.java class which is generated by wsdl2java 
"schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder"


C:\work\os-ag-onbank1\codejava -cp 
build\classes;C:\software\axis2\lib\axis2-kernel-SNAPSHOT.jar;C:\software\axis2\lib\xbean-2.2.0.jar;.;C:\software\axis2\lib\axiom-api-1.1.1.jar;C:\software\axis2\lib\stax-api-1.0.1.jar;C:\software\axis2\lib\wsdl4j-1.6.1.jar;C:\software\axis2\lib\XmlSchema-SNAPSHOT.jar;C:\software\axis2\lib\commons-logging-1.1.jar;C:\software\axis2\lib\neethi-SNAPSHOT.jar;C:\software\axis2\lib\stax-1.2.0.jar;C:\software\axis2\lib\axiom-impl-1.1.1.jar;C:\software\axis2\lib\xbean-2.2.0.jar;ClientException 
in thread "main" 
java.lang.ExceptionInInitializerError 
at 
com.example.www.onlinebanking.xsd.LoginDocument$Factory.newInstance(LoginDocument.java:112) 
at Client.login(Client.java:40) at 
Client.main(Client.java:17)Caused by: java.lang.RuntimeException: Cannot 
load SchemaTypeSystem. Unable to load class with name 
schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder. 
Make sure the generated binary files are on the 
classpath. at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783) 
at 
com.example.www.onlinebanking.xsd.LoginDocument.clinit(LoginDocument.java:19) 
... 3 moreCaused by: java.lang.ClassNotFoundException: 
schemaorg_apache_xmlbeans.system.s28FB12A440F78A928205C7E789D0196A.TypeSystemHolder 
at 
java.net.URLClassLoader$1.run(URLClassLoader.java:200) 
at java.security.AccessController.doPrivileged(Native 
Method) at 
java.net.URLClassLoader.findClass(URLClassLoa

Problem with WSDL2Java generation

[Kai Hüner]

Hello,

When I try to generate Java code of a WSDL-file (using the eclipse
plugin, newest release of axis2), I get an error message telling me
SchemaCompilationException: Unsupported content Complex Content !.
Is there any known workaround (e.g. newer jar files of a nightly
build) or have I to do a redesign of my schemas?

best regards,
Kai Huener

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with wsdl2java

[Hoda Shums]

Hi,
 
I've ran into a seemingly simple problem that I can't find a solution
to. It seems that if you create a WSDL with request and response message
having the same element, axis's wsdl2java does not create java classes
reflecting that behavior. Here's an example:
 
xsd:element name=XYZ type=tns:XYZType/
xsd:element name=XYZ2 type=tns:XYZType/
 
wsdl:message name=getXYZResponse
wsdl:part name=body element=tns:XYZ/wsdl:part
/wsdl:message
wsdl:message name=getXYZRequest
wsdl:part name=body element=tns:XYZ/wsdl:part
/wsdl:message

wsdl:portType name=XYZPort
wsdl:operation name=getXYZ
wsdl:input message=tns:getXYZRequest/
wsdl:output message=tns:getXYZResponse/
/wsdl:operation
/wsdl:portType

If I use this example in my WSDL, then the getXYZ method's return type
is void in the generated java class. But, if I replace either the
request or response's element with XYZ2, then the code generated is
perfectly fine. I need to have the soap request and response messages
looking the same, so that is not a viable option. Is there a work
around? I'm using Axis 1.4.
 
Thanks

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with WSDL2Java Generated Code using JiBX bindings

[Dennis Sosnoski]

Hi John,

I'd suspect the problem here is in the use of a fault - this is 
something I hadn't tried out, and it looks like it's confusing things 
because of the special way Axis2 code generation handles the exception. 
I'm not even sure what's actually appropriate in this case - should your 
StandardError class actually be an exception, or should there be a 
generated exception class that has a StandardError field? In any case, 
you should enter this in Jira and attach the files. I'm hoping to get 
the code in place for unwrapping message elements using JiBX binding 
over the next week or so, and will try to get this fixed at the same time.


Incidentally, you no longer need to supply default constructors in your 
data classes, you can instead use the add-constructors='true' attribute 
on your binding element (added as part of the JiBX 1.1 changes).


Thanks for including JiBX in the subject line of your email. I don't 
try to follow all the Axis(1) messages on these lists, so unless the 
subject line mentions Axis2 or JiBX I'm probably not going to read it.


 - Dennis

Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117



John Grantham wrote:



I wonder if anybody has encountered this issue, and might know if i am 
doing something wrong, or if this is a bug?


I am using WSDL2Java, which works ok with regular ADB bindings.  I 
want to use my own java value objects, however, and have been trying 
out JiBX.  My jibx bindings test out ok, and the WSDL2Java code 
generation using jibx works somewhat, but it generates a 
MessageReceiverInOut class that has a compilation problem where it 
catches my custom exception and calls toOm(...).


also, none of the /resources files are getting generated, including 
services.xml.


intel mac
Eclipse 3.2.0
java 1.5.0-06
jibx 1.1




Here are my schemas:


?xml version=1.0 encoding=UTF-8 ?
xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema;
  targetNamespace=http://nextgen.ubc/schema/Dictionary; 
  xmlns:dict=http://nextgen.ubc/schema/Dictionary;


  xsd:simpleType name=StudentNumber
xsd:restriction base=xsd:string
  xsd:length value=8/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=LastName
xsd:restriction base=xsd:string
  xsd:maxLength value=20/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=GivenName
xsd:restriction base=xsd:string
  xsd:maxLength value=20/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=Program
xsd:restriction base=xsd:string
  xsd:minLength value=2/
  xsd:maxLength value=4/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=Campus
xsd:restriction base=xsd:string
  xsd:enumeration value=VAN/
  xsd:enumeration value=OKAN/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=Street
xsd:restriction base=xsd:string
  xsd:maxLength value=30/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=City
xsd:restriction base=xsd:string
  xsd:maxLength value=30/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=Province
xsd:restriction base=xsd:string
  xsd:enumeration value=BC/
  xsd:enumeration value=AB/
  xsd:enumeration value=SK/
  xsd:enumeration value=MB/
  xsd:enumeration value=ON/
  xsd:enumeration value=PQ/
  xsd:enumeration value=NB/
  xsd:enumeration value=NS/
  xsd:enumeration value=PE/
  xsd:enumeration value=NF/
  xsd:enumeration value=YT/
  xsd:enumeration value=NT/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=PostalCode
xsd:restriction base=xsd:string
  xsd:pattern value=([A-Z]\d[A-Z]\d[A-Z]\d)/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=ErrorMessage
xsd:restriction base=xsd:string
  xsd:maxLength value=30/
/xsd:restriction
  /xsd:simpleType

  xsd:simpleType name=ErrorCode
xsd:restriction base=xsd:string
  xsd:length value=4/
/xsd:restriction
  /xsd:simpleType
/xsd:schema



?xml version=1.0 encoding=UTF-8 ?
xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema;
  targetNamespace=http://nextgen.ubc/schema/StudentKey; 
  xmlns:key=http://nextgen.ubc/schema/StudentKey;

  xmlns:dict=http://nextgen.ubc/schema/Dictionary;

  xsd:import namespace=http://nextgen.ubc/schema/Dictionary; 
schemaLocation=Dictionary.xsd/


  xsd:element name=StudentNumber type=dict:StudentNumber/

  xsd:element name=StudentKey
xsd:complexType
  xsd:sequence
xsd:element ref=key:StudentNumber minOccurs=1 maxOccurs=1/
  /xsd:sequence
/xsd:complexType
  /xsd:element
/xsd:schema



?xml version=1.0 encoding=UTF-8 ?
xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema;
  targetNamespace=http://nextgen.ubc/schema/Address; 
  xmlns:addr=http://nextgen.ubc/schema/Address;

  

Re: Problem with WSDL2Java with HTTP POST

[Anne Thomas Manes]

Use Axis2.On 5/31/06, Jose Manuel Cercós Moreno [EMAIL PROTECTED] wrote:
Thanks Warren but i don't want a SOAP communication i want use HTTPPOST only without SOAP protocol. I think that Axis is limited to onlySOAP communitacion.I had been searching yesterday all the day in google and didn't find
anything respect this and thanks for your english correct, englishisn't my first language. Bye.On 5/31/06, Warren Crossing [EMAIL PROTECTED] wrote:
 What is the wsdl2java command look like exactley?I can't believe google didn't know the answer ;-( I would expect the wsdl to look like.. wsdl:input name=mensajesencillo
 wsdlsoap:body use=encoded encodingStyle=http://schemas.xmlsoap.org/soap/encoding/ namespace=urn:
http://sencillo/ /wsdl:input why does it not? And it's not a void interface it's just empty or with no members
-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: Problem with WSDL2Java with HTTP POST

[Jose Manuel Cercós Moreno]

Thanks Warren but i don't want a SOAP communication i want use HTTP
POST only without SOAP protocol. I think that Axis is limited to only
SOAP communitacion.
I had been searching yesterday all the day in google and didn't find
anything respect this and thanks for your english correct, english
isn't my first language. Bye.

On 5/31/06, Warren Crossing [EMAIL PROTECTED] wrote:

What is the wsdl2java command look like exactley?  I can't believe
google didn't know the answer ;-(

I would expect the wsdl to look like..

wsdl:input name=mensajesencillo
wsdlsoap:body use=encoded
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
namespace=urn:http://sencillo/
/wsdl:input

why does it not?


And it's not a void interface it's just empty or with no members





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with WSDL2Java with HTTP POST

[Jose Manuel Cercós Moreno]

I'm trying to create a stub from .wsdl that i had created where the
binding is POST and when i executed the wsdl2java command i get an
void interface. Why? I had been to search in google and i haven't
anything.
Thanks in advance.

WSDL

?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=http://sencillo;
xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
targetNamespace=http://sencillo;
wsdl:message name=mensajesencillo
wsdl:part name=Email type=s:string/
wsdl:part name=ServiceName type=s:string/
wsdl:part name=OperationName type=s:string/
/wsdl:message
wsdl:portType name=SencilloHttp_Post
wsdl:operation name=operacionsencilla
wsdl:input message=tns:mensajesencillo/
/wsdl:operation
/wsdl:portType
wsdl:binding name=SencilloHttp_Post type=tns:SencilloHttp_Post
http:binding verb=POST/
wsdl:operation name=operacionsencilla
http:operation location=operacionsencilla/
wsdl:input
mime:mimeXml part=Body/ 
/wsdl:input
/wsdl:operation
/wsdl:binding
wsdl:service name=WSDLTester
wsdl:port name=SencilloHttp_Post 
binding=tns:SencilloHttp_Post
http:address
location=http://192.168.153.100:8080/appProxyAmadeus/servlet/svlProxyAmadeus/
/wsdl:port
/wsdl:service
/wsdl:definitions

INTERFACE

package sencillo;

public interface WSDLTester extends javax.xml.rpc.Service {
}

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with WSDL2Java with HTTP POST

[Anne Thomas Manes]

You don't have a message part called Body, so this reference doesn't make sense:mime:mimeXml part=Body/Anne
On 5/30/06, Jose Manuel Cercós Moreno [EMAIL PROTECTED] wrote:
I'm trying to create a stub from .wsdl that i had created where thebinding is POST and when i executed the wsdl2java command i get anvoid interface. Why? I had been to search in google and i haven'tanything.
Thanks in advance.WSDL?xml version=1.0 encoding=UTF-8?wsdl:definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/xmlns:s=http://www.w3.org/2001/XMLSchema
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/xmlns:tns=http://sencilloxmlns:tm=
http://microsoft.com/wsdl/mime/textMatching/xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/targetNamespace=http://sencillowsdl:message name=mensajesencillo
wsdl:part name=Email type=s:string/wsdl:part name=ServiceName type=s:string/wsdl:part name=OperationName type=s:string/
/wsdl:messagewsdl:portType name=SencilloHttp_Postwsdl:operation name=operacionsencillawsdl:input message=tns:mensajesencillo/
/wsdl:operation/wsdl:portTypewsdl:binding name=SencilloHttp_Post type=tns:SencilloHttp_Posthttp:binding verb=POST/
wsdl:operation name=operacionsencillahttp:operation location=operacionsencilla/wsdl:inputmime:mimeXml part=Body/
/wsdl:input/wsdl:operation/wsdl:bindingwsdl:service name=WSDLTesterwsdl:port name=SencilloHttp_Post binding=tns:SencilloHttp_Post
http:addresslocation=http://192.168.153.100:8080/appProxyAmadeus/servlet/svlProxyAmadeus/
/wsdl:port/wsdl:service/wsdl:definitionsINTERFACEpackage sencillo;public interface WSDLTester extends javax.xml.rpc.Service {}
-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: Problem with WSDL2Java with HTTP POST

[Jose Manuel Cercós Moreno]

I have changed the input element by mime:content
type=application/x-www-form-urlencoded /and get the interface
without methods.
anyway, thanks Anne.

WSDL

?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=http://sencillo;
xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=http://sencillo;
wsdl:message name=mensajesencillo
wsdl:part name=Email type=s:string/
wsdl:part name=ServiceName type=s:string/
wsdl:part name=OperationName type=s:string/
/wsdl:message
wsdl:portType name=SencilloHttp_Post
wsdl:operation name=operacionsencilla
wsdl:input message=tns:mensajesencillo/
/wsdl:operation
/wsdl:portType
wsdl:binding name=SencilloHttp_Post type=tns:SencilloHttp_Post
http:binding verb=POST/
wsdl:operation name=operacionsencilla
http:operation location=/operacionsencilla/
wsdl:input
mime:content 
type=application/x-www-form-urlencoded /   
/wsdl:input
/wsdl:operation
/wsdl:binding
wsdl:service name=WSDLTester
wsdl:port name=SencilloHttp_Post 
binding=tns:SencilloHttp_Post
http:address
location=http://192.168.153.100:8080/appProxyAmadeus/servlet/svlProxyAmadeus/
/wsdl:port
/wsdl:service
/wsdl:definitions

INTERFACE

package sencillo;

public interface WSDLTester extends javax.xml.rpc.Service {
}



On 5/30/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:

You don't have a message part called Body, so this reference doesn't make
sense:

mime:mimeXml part=Body/

Anne


 On 5/30/06, Jose Manuel Cercós Moreno [EMAIL PROTECTED] wrote:

 I'm trying to create a stub from .wsdl that i had created where the
binding is POST and when i executed the wsdl2java command i get an
void interface. Why? I had been to search in google and i haven't
anything.
 Thanks in advance.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with WSDL2Java with HTTP POST

[Warren Crossing]

What is the wsdl2java command look like exactley?  I can't believe 
google didn't know the answer ;-(


I would expect the wsdl to look like..

wsdl:input name=mensajesencillo
	wsdlsoap:body use=encoded 
encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
namespace=urn:http://sencillo/

/wsdl:input

why does it not?


And it's not a void interface it's just empty or with no members

� wrote:

I'm trying to create a stub from .wsdl that i had created where the
binding is POST and when i executed the wsdl2java command i get an
void interface. Why? I had been to search in google and i haven't
anything.
Thanks in advance.

WSDL

?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=http://sencillo;
xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
targetNamespace=http://sencillo;
wsdl:message name=mensajesencillo
wsdl:part name=Email type=s:string/
wsdl:part name=ServiceName type=s:string/
wsdl:part name=OperationName type=s:string/
/wsdl:message
wsdl:portType name=SencilloHttp_Post
wsdl:operation name=operacionsencilla
wsdl:input message=tns:mensajesencillo/
/wsdl:operation
/wsdl:portType
wsdl:binding name=SencilloHttp_Post type=tns:SencilloHttp_Post
http:binding verb=POST/
wsdl:operation name=operacionsencilla
http:operation location=operacionsencilla/
wsdl:input
mime:mimeXml part=Body/   
/wsdl:input

/wsdl:operation
/wsdl:binding
wsdl:service name=WSDLTester
wsdl:port name=SencilloHttp_Post 
binding=tns:SencilloHttp_Post

http:address
location=http://192.168.153.100:8080/appProxyAmadeus/servlet/svlProxyAmadeus/ 


/wsdl:port
/wsdl:service
/wsdl:definitions

INTERFACE

package sencillo;

public interface WSDLTester extends javax.xml.rpc.Service {
}

-
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]

Problem with WSDL2Java for the DataHandler type using ?wsdl

[subir.sasikumar]

Hi,



I am using AXIS 1.2 over Tomcat 5.5.9 appserver with
jdk1.5.0_03. I have deployed my web services in both Linux and Windows. I found
the problem in only linux.



The problem that I am facing is that the ?wsdl feature of
the Axis is not generating the wsdl:types section correctly.



I have defined a dataHandler element as follows



 typeMapping 


xmlns:apachesoap=http://xml.apache.org/xml-soap


qname=apachesoap:DataHandler


languageSpecificType=java:javax.activation.DataHandler 


deserializer=org.apache.axis.encoding.ser.JAFDataHandlerDeserializerFactory


serializer=org.apache.axis.encoding.ser.JAFDataHandlerSerializerFactory 


encodingStyle=http://schemas.xmlsoap.org/soap/encoding/

 /



And also I have added the xmlns:apachesoap in the deployment
tag of my deploy.wsdd



My web service in the deploy.wsdd looks like this.



 operation returnQName=uploadStatus


 returnType=xsd:boolean


 name=uploadMediaTitle


 xmlns:xsd=http://www.w3.org/2001/XMLSchema





parameter name=name type=xsd:string/


parameter name=description type=xsd:string/


parameter name=mediaTitleMimeTypeCode type=xsd:string/


parameter name=dataHandler type=apachesoap:DataHandler /


/operation



The problem is that the ?wsdl that generates the wsdl for my
service does not generate the correct wsdl:type. It some times have and some
times does not have the type declaration in the generated wsdl because of which
the stubs generation throws the following error.



java.io.IOException: Type DataHandler is referenced but not
defined.

 at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol

Table.java:663)

 at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543

)

 at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav

a:516)

 at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav

a:493)

 at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)

 at
java.lang.Thread.run(Thread.java:534)



Can some one tell me the reason for this?



Can some body tell me is this not the
correct group that could help me or that I have to send the mail to developers
list also? I hope somebody might have got the above problem.



Thanks and regards



Subir S











The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com

Problem with WSDL2Java for the DataHandler type using ?wsdl

[subir.sasikumar]

Hi,



I am using AXIS 1.2 over Tomcat 5.5.9 appserver with
jdk1.5.0_03. I have deployed my web services in both Linux and Windows. I found
the problem in only linux.



The problem that I am facing is that the ?wsdl feature of
the Axis is not generating the wsdl:types section correctly.



I have defined a dataHandler element as follows



 typeMapping 

 xmlns:apachesoap=http://xml.apache.org/xml-soap

 qname=apachesoap:DataHandler

 languageSpecificType=java:javax.activation.DataHandler 

 deserializer=org.apache.axis.encoding.ser.JAFDataHandlerDeserializerFactory


serializer=org.apache.axis.encoding.ser.JAFDataHandlerSerializerFactory 


encodingStyle=http://schemas.xmlsoap.org/soap/encoding/

 /



And also I have added the xmlns:apachesoap in the deployment
tag of my deploy.wsdd



My web service in the deploy.wsdd looks like this.



 operation returnQName=uploadStatus

 
returnType=xsd:boolean

 
name=uploadMediaTitle

 
xmlns:xsd=http://www.w3.org/2001/XMLSchema

 

 parameter name=name type=xsd:string/

 parameter name=description type=xsd:string/

 parameter name=mediaTitleMimeTypeCode type=xsd:string/

 parameter name=dataHandler type=apachesoap:DataHandler /

 /operation



The problem is that the ?wsdl that generates the wsdl for my
service does not generate the correct wsdl:type. It some times have and some
times does not have the type declaration in the generated wsdl because of which
the stubs generation throws the following error.



java.io.IOException: Type DataHandler is referenced but not
defined.

 at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol

Table.java:663)

 at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543

)

 at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav

a:516)

 at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav

a:493)

 at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)

 at
java.lang.Thread.run(Thread.java:534)



Can some one tell me the reason for this?



Thanks and regards



Subir S












The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com

Re: [Axis2] problem with WSDL2Java generated stubs and databinding

[iksrazal]

Nikola, 

This might be easier for you - it works for me using the .93 release. 

 Options options = stub._getClientOptions();
  options.setAction(http://smartSWANS/smartLogin;);

Where the relevant section of the wsdl is: 

 wsdl:operation name=smartLogin
  soap:operation soapAction=http://smartSWANS/smartLogin; 
style=document /
  wsdl:input
soap:body use=literal /
  /wsdl:input
  wsdl:output
soap:body use=literal /
  /wsdl:output
/wsdl:operation

Or you could try the latest nightly: 

http://cvs.apache.org/dist/axis2/nightly/

HTH,
iksrazal

Em Terça 27 Dezembro 2005 14:14, o Nikola Zifra escreveu:
 Hi iksrazal and Chintaka,
   this is the part of the stub code  generated  by the  0.92  version of
 the WSDL2Java  tool:

org.apache.axis2.clientapi.Call _call = new
 org.apache.axis2.clientapi.Call(_serviceContext);
 _call.setTransportInfo(this.senderTransport,this.listenerTransport,this.use
SeparateListener); _call.setDoREST(this.doRest);

 org.apache.axis2.context.MessageContext _messageContext = 
 getMessageContext(); _call.setTo(this.toEPR);
   _call.setSoapAction(echoString);

   And this is the part generated by 0.93 version of WSDL2Java tool:

 org.apache.axis2.client.Call _call = new 
 org.apache.axis2.client.Call(_serviceContext);
 _call.setClientOptions(_clientOptions);
 org.apache.axis2.context.MessageContext _messageContext = 
 getMessageContext(); if(_clientOptions.getSoapAction() == null) {

 }

if(_clientOptions.getAction() == null) {

}

   Notice that two different Call classes with different APIs are used in 
 0.92 and 0.93 version of the generated stub.You can't add line 
 _call.setSoapAction(echoString)  to the 0.93 version gen code  because
 the org.apache.axis2.client.Call used in the 0.93 does not have  method
 setSoapAction() . You can just use 
 _clientOptions.setSoapAction(echoString) but it seems that it does  not
 resolve my issue, because I am still getting the exception I've complained
 about.

   When I modify the 0.93 version code like this i am still getting the
 exception:

   rg.apache.axis2.client.Call _call = new
 org.apache.axis2.client.Call(_serviceContext);
 _call.setClientOptions(_clientOptions);
 org.apache.axis2.context.MessageContext _messageContext = 
 getMessageContext(); if(_clientOptions.getSoapAction() == null) {
  System.out.println(\n\n\n SETTING  SOAP ACTION);
  _clientOptions.setSoapAction(echoString);
   }

   org.apache.axis2.AxisFault: org.apache.axis2.AxisFault: Operation Not 
 found EPR is 
 http://localhost:8080/axis2/services/Axis2SampleDocLitPortType and WSA 
 Action = at
 org.apache.axis2.engine.DispatchingChecker.invoke(DispatchingChecker.java:7
0) at org.apache.axis2.engine.Phase.invoke(Phase.java:167)
   at
 org.apache.axis2.engine.AxisEngine.invokePhases(AxisEngine.java:443) at
 org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:137)

   When I modify the 0.93 code in the following  manner :

   org.apache.axis2.client.Call _call = new
 org.apache.axis2.client.Call(_serviceContext);
 _call.setClientOptions(_clientOptions);

 org.apache.axis2.context.MessageContext _messageContext = 
 getMessageContext(); _clientOptions.setSoapAction(echoString);
if(_clientOptions.getSoapAction() == null) {


 }

if(_clientOptions.getAction() == null) {

}
   I got the the following exception:

   org.apache.axis2.AxisFault: null; nested exception is:
   java.lang.NullPointerException
   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:190)
   at 
 org.apache.axis2.userguide.Axis2SampleDocLitPortTypeMessageReceiver.invokeB
usinessLogic(Axis2SampleDocLitPortTypeMessageReceiver.java:120) at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Abstrac
tInOutSyncMessageReceiver.java:36) 
   Caused by: java.lang.NullPointerException
   at 
 org.apache.axis2.userguide.databinding.Axis2SampleDocLitPortTypeechoStringD
atabindingSupporter.toOM(Axis2SampleDocLitPortTypeechoStringDatabindingSuppo
rter.java:34) at 
 org.apache.axis2.userguide.Axis2SampleDocLitPortTypeMessageReceiver.invokeB
usinessLogic(Axis2SampleDocLitPortTypeMessageReceiver.java:106) ... 20 more

   Could you pls. be more specific what part of the generated code should I
 modify and how?

   Regards,
   Nikola






 Eran Chinthaka [EMAIL PROTECTED] wrote:  -BEGIN PGP
 SIGNED MESSAGE- Hash: SHA1

   Nikola, the iksrazal's method will fix the problem, BUT ..
   I should accept that its a bug in 0.93 release, which is now fixed in
   current SVN head.

   - -- Chinthaka

   iksrazal wrote:
Nikola,
   
   
   
Try following this thread - worked for me when I had a similiar
   
problem:

   

Problem with WSDL2Java?

[Tim R J Langford]

Hello All,

I am upgrading some SOAP clients from Axis 1.2 to Axis 1.3 Final. One of 
them upgraded with little effort,  just some changes to the code that 
processed the new bean convention style generate by WSDL2Java. The other 
project  is proving very troublesome however.


#1 : Firstly the schema beans appear NOT to generate properly. For 
example the following Schema section :



 s:complexType name=RoomStayCandidateType
   s:sequence
 s:element minOccurs=0 maxOccurs=1 name=GuestCounts 
type=s1:GuestCountType /
 s:element minOccurs=0 maxOccurs=unbounded 
name=RoomAmenity type=s1:RoomAmenityPrefType /

   /s:sequence
   s:attribute name=RoomType type=s:string /
   s:attribute name=RoomTypeCode type=s:string /
   s:attribute name=Quantity type=s:positiveInteger /
   s:attribute name=Composite type=s:boolean /
 /s:complexType
 s:complexType name=GuestCountType
   s:sequence
 s:element minOccurs=0 maxOccurs=unbounded 
name=GuestCount type=s1:GuestCountTypeGuestCount /

   /s:sequence
   s:attribute name=IsPerRoom type=s:boolean /
 /s:complexType
 s:complexType name=GuestCountTypeGuestCount
   s:attribute name=AgeQualifyingCode type=s:string /
   s:attribute name=Age type=s:nonNegativeInteger /
   s:attribute name=Count type=s:positiveInteger /
 /s:complexType


But here WSDL2Java enerates a RoomStayCandidateType object that 
contains an array of GuestCountTypeGuestCount objects as a member. It 
does not generate a GuestCountType at all. This of course breaks the 
service. The old version of WSDL2Java generated all these classes as was 
to be expected, and only messed up setting the action type on one of the 
services (whihc was easilly fixed with a code post processor). I assume 
this is a bug. The schema seems valid to me.



#2 : Another problem occured in the generated source where a constructor 
was created thats calls Object.super() as follows...


public class VendorMessageType  implements java.io.Serializable {
   private java.lang.String infoType;  // attribute

   private 
org.opentravel.www.OTA._2003._05.FormattedTextSubSectionTypeParagraph[][] 
formattedTextType;  // attribute


   public VendorMessageType() {
   }

   public VendorMessageType(
  
org.opentravel.www.OTA._2003._05.FormattedTextSubSectionTypeParagraph[][] 
param1,

  java.lang.String Title,
  org.apache.axis.types.Language Language,
  java.lang.String infoType) {
   super(
   param1,
   Title);
   this.Language = Language;
   this.infoType = infoType;
   }

...
etc
...

}

???


When I searched the mailing list I noticed a few possibly similar 
questions to this, but no reponse I could act on. Is there any 
possibility of fixing these problems? If not is there any method of 
fixing/altering the generated source form the old version of Axis 
WSDL2Java to work with new 1.3 library? For example could I code to the 
correctly generated old 1.1 SOAP beans to get them to work with 1.3?


Thanks very much for your help and time! This has become a real show 
stopper, and I got deadlines and a crazy boss!


Tim

Re: Problem with WSDL2Java?

[Christian Schmitz]

Hi Tim,

I think my problem discussed on the title wsdl2java does not generate 
class-files for complexTypes seems to be the same as yours. Try the 
--wrapArrays (-w) option when generating the sources.


Regards,
Christian

Tim R J Langford schrieb:


Hello All,

I am upgrading some SOAP clients from Axis 1.2 to Axis 1.3 Final. One 
of them upgraded with little effort,  just some changes to the code 
that processed the new bean convention style generate by WSDL2Java. 
The other project  is proving very troublesome however.


#1 : Firstly the schema beans appear NOT to generate properly. For 
example the following Schema section :



 s:complexType name=RoomStayCandidateType
   s:sequence
 s:element minOccurs=0 maxOccurs=1 name=GuestCounts 
type=s1:GuestCountType /
 s:element minOccurs=0 maxOccurs=unbounded 
name=RoomAmenity type=s1:RoomAmenityPrefType /

   /s:sequence
   s:attribute name=RoomType type=s:string /
   s:attribute name=RoomTypeCode type=s:string /
   s:attribute name=Quantity type=s:positiveInteger /
   s:attribute name=Composite type=s:boolean /
 /s:complexType
 s:complexType name=GuestCountType
   s:sequence
 s:element minOccurs=0 maxOccurs=unbounded 
name=GuestCount type=s1:GuestCountTypeGuestCount /

   /s:sequence
   s:attribute name=IsPerRoom type=s:boolean /
 /s:complexType
 s:complexType name=GuestCountTypeGuestCount
   s:attribute name=AgeQualifyingCode type=s:string /
   s:attribute name=Age type=s:nonNegativeInteger /
   s:attribute name=Count type=s:positiveInteger /
 /s:complexType


But here WSDL2Java enerates a RoomStayCandidateType object that 
contains an array of GuestCountTypeGuestCount objects as a member. 
It does not generate a GuestCountType at all. This of course breaks 
the service. The old version of WSDL2Java generated all these classes 
as was to be expected, and only messed up setting the action type on 
one of the services (whihc was easilly fixed with a code post 
processor). I assume this is a bug. The schema seems valid to me.



#2 : Another problem occured in the generated source where a 
constructor was created thats calls Object.super() as follows...


public class VendorMessageType  implements java.io.Serializable {
   private java.lang.String infoType;  // attribute

   private 
org.opentravel.www.OTA._2003._05.FormattedTextSubSectionTypeParagraph[][] 
formattedTextType;  // attribute


   public VendorMessageType() {
   }

   public VendorMessageType(
  
org.opentravel.www.OTA._2003._05.FormattedTextSubSectionTypeParagraph[][] 
param1,

  java.lang.String Title,
  org.apache.axis.types.Language Language,
  java.lang.String infoType) {
   super(
   param1,
   Title);
   this.Language = Language;
   this.infoType = infoType;
   }

...
etc
...

}

???


When I searched the mailing list I noticed a few possibly similar 
questions to this, but no reponse I could act on. Is there any 
possibility of fixing these problems? If not is there any method of 
fixing/altering the generated source form the old version of Axis 
WSDL2Java to work with new 1.3 library? For example could I code to 
the correctly generated old 1.1 SOAP beans to get them to work with 1.3?


Thanks very much for your help and time! This has become a real show 
stopper, and I got deadlines and a crazy boss!


Tim





--


Besuchen Sie unsere kostenlose Veranstaltung
Effizientes Prozess- und IT-Management -
Die Verbindung von ARIS mit IT-Infrastrukturen
am 24.11.2005 in Köln. Anmeldungen unter
http://www.opitz-consulting.de

OPITZ CONSULTING Gummersbach GmbH
Christian Schmitz -  Dipl.-Wirtschaftsinformatiker (FH)
Kirchstr. 6 - D-51647 Gummersbach
Telefon (Fax): +49 2261 6001-0 (-1139) - Mobil: +49 170 5545138
http://www.opitz-consulting.de

Re: Problem with WSDL2Java?

[Tim R J Langford]

Hello Christian!

Thankyou very much for your swift response, and you are indeed correct! 
I added the 'wrapArrays=true' to the ant task and everything generated 
as expected and now my messages are full of extra nilable elements and 
work just fine with no changes to my processing code at all! A direct 
upgrade - great!


Thankyou Sir, and much respect to you.

Regards,

Tim


PS: Maybe it would be worth setting 'wrapArrays=true' by default, 
because in my case when set to false WSDL2Java actually created 
non-compilable code in one case, and in the others forced me to change 
alot of the message processing code? Or is my usage an exception to 
normal usage?







Christian Schmitz wrote:


Hi Tim,

I think my problem discussed on the title wsdl2java does not generate 
class-files for complexTypes seems to be the same as yours. Try the 
--wrapArrays (-w) option when generating the sources.


Regards,
Christian

Tim R J Langford schrieb:


Hello All,

I am upgrading some SOAP clients from Axis 1.2 to Axis 1.3 Final. One 
of them upgraded with little effort,  just some changes to the code 
that processed the new bean convention style generate by WSDL2Java. 
The other project  is proving very troublesome however.


#1 : Firstly the schema beans appear NOT to generate properly. For 
example the following Schema section :



 s:complexType name=RoomStayCandidateType
   s:sequence
 s:element minOccurs=0 maxOccurs=1 name=GuestCounts 
type=s1:GuestCountType /
 s:element minOccurs=0 maxOccurs=unbounded 
name=RoomAmenity type=s1:RoomAmenityPrefType /

   /s:sequence
   s:attribute name=RoomType type=s:string /
   s:attribute name=RoomTypeCode type=s:string /
   s:attribute name=Quantity type=s:positiveInteger /
   s:attribute name=Composite type=s:boolean /
 /s:complexType
 s:complexType name=GuestCountType
   s:sequence
 s:element minOccurs=0 maxOccurs=unbounded 
name=GuestCount type=s1:GuestCountTypeGuestCount /

   /s:sequence
   s:attribute name=IsPerRoom type=s:boolean /
 /s:complexType
 s:complexType name=GuestCountTypeGuestCount
   s:attribute name=AgeQualifyingCode type=s:string /
   s:attribute name=Age type=s:nonNegativeInteger /
   s:attribute name=Count type=s:positiveInteger /
 /s:complexType


But here WSDL2Java enerates a RoomStayCandidateType object that 
contains an array of GuestCountTypeGuestCount objects as a member. 
It does not generate a GuestCountType at all. This of course breaks 
the service. The old version of WSDL2Java generated all these classes 
as was to be expected, and only messed up setting the action type on 
one of the services (whihc was easilly fixed with a code post 
processor). I assume this is a bug. The schema seems valid to me.



#2 : Another problem occured in the generated source where a 
constructor was created thats calls Object.super() as follows...


public class VendorMessageType  implements java.io.Serializable {
   private java.lang.String infoType;  // attribute

   private 
org.opentravel.www.OTA._2003._05.FormattedTextSubSectionTypeParagraph[][] 
formattedTextType;  // attribute


   public VendorMessageType() {
   }

   public VendorMessageType(
  
org.opentravel.www.OTA._2003._05.FormattedTextSubSectionTypeParagraph[][] 
param1,

  java.lang.String Title,
  org.apache.axis.types.Language Language,
  java.lang.String infoType) {
   super(
   param1,
   Title);
   this.Language = Language;
   this.infoType = infoType;
   }

...
etc
...

}

???


When I searched the mailing list I noticed a few possibly similar 
questions to this, but no reponse I could act on. Is there any 
possibility of fixing these problems? If not is there any method of 
fixing/altering the generated source form the old version of Axis 
WSDL2Java to work with new 1.3 library? For example could I code to 
the correctly generated old 1.1 SOAP beans to get them to work with 1.3?


Thanks very much for your help and time! This has become a real show 
stopper, and I got deadlines and a crazy boss!


Tim

problem with WSDL2Java using a schema import with attributeGroup

[Guy, Steven \(IT\)]

I'm having a problem with WSDL2Java generating the wrong java code for a
wsdl that defines an array of (attribute, array) touples.
 
When I inline the schema into the wsdl file, it works fine.  When I
export the schema to a separate xsd file, it seems to collapse
everything into an array of arrays.  (Dropping off the attribute and
condensing it).
 
I'm running axis 1.2.1 final with the -v -a arguments.  When it runs
correctly, it generates Record1.java and Record1MySet.java.  When it is
failing, it just generates Record1.java.
 
I've attached 3 files.  
 
AttrGroupService.wsdl--- has inlined schema and works as expected
 
AttrGroupService2.wsdl   -- wsdl that imports a schema (doesn't work)
AttrGroupService2.xsd
 
Any ideas?
 
thanks,
Steven Guy


NOTICE: If received in error, please destroy and notify sender.  Sender does 
not waive confidentiality or privilege, and use is prohibited.


AttrGroupService2.xsd
Description: AttrGroupService2.xsd


AttrGroupService.wsdl
Description: AttrGroupService.wsdl


AttrGroupService2.wsdl
Description: AttrGroupService2.wsdl

Re: Problem with WSDL2Java

[Venkat Reddy]

What is the error??

WSDL2Java doesn't need tomcat to be running unless you have any
references to wsdl imports or the wsdl itself, fetched from a URL
served by tomcat, which is not the case in your example.

- venkat

On 8/22/05, Arun Bhandari [EMAIL PROTECTED] wrote:
 Hi Venkat,
 
 Thanks for your help. I made the correction, but I am still facing an issue.
 
 Here is the command line that I am using:
 
 java -classpath
 .\webapps\axis\WEB-INF\lib\axis.jar;.\webapps\axis\WEB-INF\lib\log4j-1.2.8.jar;.\webapps\axis\WEB-INF\lib\commons-discovery-0.2.jar;.\webapps\axis\WEB-INF\lib\commons-logging-1.0.4.jar;.\webapps\axis\WEB-INF\lib\wsdl4j-1.5.1.jar;.\webapps\axis\WEB-INF\lib\saaj.jar;.\webapps\axis\WEB-INF\lib\axis-ant.jar;.\webapps\axis\WEB-INF\lib\jaxrpc.jar;C:\Sun\jwsdp-1.6\jaxp\lib\jaxp-api.jar;C:\Sun\jwsdp-1.6\jwsdp-shared\lib\mail.jar;C:\Sun\jwsdp-1.6\jwsdp-shared\lib\activation.jar
 org.apache.axis.wsdl.WSDL2Java SaleOrder.wsdl
 
 I am executing this command line from my container (tomcat) home folder.
 Please let me know if  you have an idea for this error.
 
 Thanks,
 Arun.
 
 
 On 8/22/05, Venkat Reddy [EMAIL PROTECTED] wrote:
  Your WSDL has a wsdl:fault element in binding section which doesn't
  correspond to the one defined in portType section. After correcting
  this error, I could run WSDL2Java without any issues. Here is the
  corrected version of wsdl:fault inside binding section of your WSDL.
 
 wsdl:fault name=SaleError
 soap:fault use=literal
  namespace=http://FaultMessageNamespace; name=SaleError/
 /wsdl:fault
 
  - venkat
 
 
  On 8/22/05, Arun Bhandari [EMAIL PROTECTED] wrote:
   Hi,
  
   I have attached my WSDL. Thanks for your response
  
   On 8/22/05, Venkat Reddy [EMAIL PROTECTED] wrote:
please post your WSDL.
   
- venkat
   
On 8/22/05, Arun Bhandari [EMAIL PROTECTED] wrote:
 I am using Apache Axis 1.2 with java jdk 1.5, Tomcat as my web 
 container.
 I have ensured that all the Axis jars in my classpath.

 I am trying to generate a client stub using a WSDL, but I get the
 following error:

 
 java.lang.NullPointerException
   at javax.wsdl.OperationType.equals(Unknown Source)
   at 
 org.apache.axis.wsdl.toJava.JavaGeneratorFactory.constructSignat=
 ures(
 JavaGeneratorFactory.java:1393)
   at 
 org.apache.axis.wsdl.toJava.JavaGeneratorFactory.generatorPass(J=
 avaGe
 neratorFactory.java:213)
   at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:424)
   at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:44)
   at 
 org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361=
 )
   at java.lang.Thread.run(Unknown Source)
 
 Any help will be appreciated.

 --
 Thanks  Regards,

 Arun Bhandari

   
  
  
   --
   Thanks  Regards,
  
   Arun Bhandari
  
  
  
 
 
 
 --
 Thanks  Regards,
 
 Arun Bhandari

Problem running WSDL2Java

[Miller, Janet]

I am a newbie.  I have just installed Axis and tried to WSDL2Java for
the first time, but I am getting the following error:

log4j:WARN No appenders could be found for logger
(org.apache.axis.i18n.ProjectR
esourceBundle).
log4j:WARN Please initialize the log4j system properly.


Why do I need to have log4j setup to run the WSDL2Java utility?  The
Axis documentation doesn't say anything about this or how to do this.
Where does the log4j.xml file need to be?  Does anyone have a basic
log4j.xml file that they could point me to that will work with
WSDL2Java?

Thanks,

Jan

RE: Problem running WSDL2Java

[Ferruh Zamangör]

When you have download the axis.jar I think in the examples are a
log4j.properties file. You must not set up log4j to run wsdl2java it's only
warning message not an error message.

Ferruh 


 --- Ursprüngliche Nachricht ---
 Von: Miller, Janet [EMAIL PROTECTED]
 An: axis-user@ws.apache.org
 Betreff: RE: Problem running WSDL2Java
 Datum: Wed, 29 Jun 2005 11:10:12 -0400
 
 But I am not even using Tomcat when I run the wsdl2Java.
 
 -Original Message-
 From: Patrick Quinn [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 29, 2005 10:41 AM
 To: axis-user@ws.apache.org
 Subject: RE: Problem running WSDL2Java
 
 
 I'm a newbie too, but I thought I'd reply in case somebody else doesn't
 get back to you. I think you are meant to include a log4j.properties
 file in the $CATALINA_HOME/common/lib area. Maybe this is related to the
 problem? Just guessing, sorry! Pat
 
 -Original Message-
 From: Miller, Janet [mailto:[EMAIL PROTECTED] 
 Sent: 29 June 2005 15:29
 To: axis-user@ws.apache.org
 Subject: Problem running WSDL2Java
 
 
 I am a newbie.  I have just installed Axis and tried to WSDL2Java for
 the first time, but I am getting the following error:
 
 log4j:WARN No appenders could be found for logger
 (org.apache.axis.i18n.ProjectR esourceBundle). log4j:WARN Please
 initialize the log4j system properly.
 
 
 Why do I need to have log4j setup to run the WSDL2Java utility?  The
 Axis documentation doesn't say anything about this or how to do this.
 Where does the log4j.xml file need to be?  Does anyone have a basic
 log4j.xml file that they could point me to that will work with
 WSDL2Java?
 
 Thanks,
 
 Jan
 
 __
 This email has been scanned by the MessageLabs Email Security System.
 For more information please visit http://www.messagelabs.com/email 
 __
 

-- 
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

RE: Problem running WSDL2Java

[Arijit Mukherjee]

Hi

This is a warning - you can ignore it. WSDL2Java would still generate
the stubs and skeletons... 

AM

-Original Message-
From: Miller, Janet [mailto:[EMAIL PROTECTED] 
Sent: 29 June 2005 16:10
To: axis-user@ws.apache.org
Subject: RE: Problem running WSDL2Java

But I am not even using Tomcat when I run the wsdl2Java.

-Original Message-
From: Patrick Quinn [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 29, 2005 10:41 AM
To: axis-user@ws.apache.org
Subject: RE: Problem running WSDL2Java


I'm a newbie too, but I thought I'd reply in case somebody else doesn't
get back to you. I think you are meant to include a log4j.properties
file in the $CATALINA_HOME/common/lib area. Maybe this is 
related to the
problem? Just guessing, sorry! Pat

-Original Message-
From: Miller, Janet [mailto:[EMAIL PROTECTED] 
Sent: 29 June 2005 15:29
To: axis-user@ws.apache.org
Subject: Problem running WSDL2Java


I am a newbie.  I have just installed Axis and tried to WSDL2Java for
the first time, but I am getting the following error:

log4j:WARN No appenders could be found for logger
(org.apache.axis.i18n.ProjectR esourceBundle). log4j:WARN Please
initialize the log4j system properly.


Why do I need to have log4j setup to run the WSDL2Java utility?  The
Axis documentation doesn't say anything about this or how to do this.
Where does the log4j.xml file need to be?  Does anyone have a basic
log4j.xml file that they could point me to that will work with
WSDL2Java?

Thanks,

Jan

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

RE: Problem running WSDL2Java

[zhangyu]

Run the wsdl2Java with specified classpath in which the log4j.properties  
locates.
Reason:
In Axis1.1,you can find a log4j.properties in the axis.jar;but in axis1.2,the 
axis.jar no longer include it.So
you should do it by handle. 

Best Regards,

Robert Zhang
Email:[EMAIL PROTECTED]
Tel:86-010-62014411-2437

- 原邮件 -
从: Miller, Janet [EMAIL PROTECTED]
日期: 星期三, 六月 29日, 2005 下午11:10
主题: RE: Problem running WSDL2Java

 But I am not even using Tomcat when I run the wsdl2Java.
 
 -Original Message-
 From: Patrick Quinn [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 29, 2005 10:41 AM
 To: axis-user@ws.apache.org
 Subject: RE: Problem running WSDL2Java
 
 
 I'm a newbie too, but I thought I'd reply in case somebody else 
 doesn'tget back to you. I think you are meant to include a 
 log4j.propertiesfile in the $CATALINA_HOME/common/lib area. Maybe 
 this is related to the
 problem? Just guessing, sorry! Pat
 
 -Original Message-
 From: Miller, Janet [mailto:[EMAIL PROTECTED] 
 Sent: 29 June 2005 15:29
 To: axis-user@ws.apache.org
 Subject: Problem running WSDL2Java
 
 
 I am a newbie.  I have just installed Axis and tried to WSDL2Java for
 the first time, but I am getting the following error:
 
 log4j:WARN No appenders could be found for logger
 (org.apache.axis.i18n.ProjectR esourceBundle). log4j:WARN Please
 initialize the log4j system properly.
 
 
 Why do I need to have log4j setup to run the WSDL2Java utility?  The
 Axis documentation doesn't say anything about this or how to do this.
 Where does the log4j.xml file need to be?  Does anyone have a basic
 log4j.xml file that they could point me to that will work with
 WSDL2Java?
 
 Thanks,
 
 Jan
 
 __
 This email has been scanned by the MessageLabs Email Security System.
 For more information please visit http://www.messagelabs.com/email 
 __