Sure... sorry.
Also, when using xmlbeans binding, I get the following error:
Using AXIS2_HOME: /usr/local/axis2
Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun
Retrieving schema at '../../../../fih/1.0/fih-header.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Retrieving schema at
'http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd',
relative to 'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
Retrieving schema at
'http://schemas.xmlsoap.org/ws/2004/08/addressing/', relative to
'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
Retrieving schema at '1.0/receive-purchase-order-request.xsd', relative
to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Retrieving schema at 'LimitedPurchaseOrder.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/1.0/receive-purchase-order-request.xsd'.
Retrieving schema at '1.0/receive-purchase-order-reply.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/1.0] and systemId
[/fih/1.0/fih-header.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/c-efm/purchase-order/1.0]
and systemId [/1.0/receive-purchase-order-request.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/c-efm/purchase-order/1.0]
and systemId [/1.0/receive-purchase-order-reply.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId
[http://www.w3.org/2000/09/xmldsig#] and systemId
[/http:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId
[http://schemas.xmlsoap.org/ws/2004/08/addressing] and systemId
[/http:/schemas.xmlsoap.org/ws/2004/08/addressing]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [http://www.fih.org/XML/WD0] and
systemId [/1.0/LimitedPurchaseOrder.xsd]
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82)
... 3 more
Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException:
http://schemas.xmlsoap.org/ws/2004/08/addressing/:61:1: error:
cvc-enumeration-valid: string value 'none' is not a valid enumeration
value for type of processContents attribute in xs:wildcard
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:242)
... 8 more
Caused by: org.apache.xmlbeans.XmlException:
http://schemas.xmlsoap.org/ws/2004/08/addressing/:61:1: error:
cvc-enumeration-valid: string value 'none' is not a valid enumeration
value for type of processContents attribute in xs:wildcard
at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667)
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:160)
... 8 more
On Wed, 2007-01-17 at 10:41 +0530, Amila Suriarachchi wrote:
> Can you attach your fih-header.xsd file?
>
> On 1/16/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> I just can't seem to get Axis2 1.1.1 wsdl2java.sh to properly
> create
> skeleton code and Axiom or XmlBeans artifacts correctly for,
> what seems
> to be, relatively simple wsdl and xsd's.
>
> Below is the xsd and wsdl information. I have used FC4, FC5,
> Ubuntu and Debian Sarge. I have tried 1.1, a snapshot before
> 1.1.1 and 1.1.1 releases. Sun java 1.5.0_09 and 10.
>
> I am being told that the wsdl and xsd information is valid (by
> the
> original developers). Both NetBeans 5.5 and Eclipse (under
> WDSCi) seem
> to agree that they are at least valid.
>
> When I run wsdl2java with ADB binding, the message parts all
> end up in
> the default package with empty package statements
> ("package ;"). The
> ExtensionMapper.java ends up in an (invalid) null package.
> (It's named
> "null" and on the output src path.)
>
> All of the types, after the first array type, are listed with
> "This was
> an array!" in the comments, but have no array declarations in
> their
> _type_nn classes... the [] markers are not produced after the
> first
> repeating element.
>
> I have looked at trying to clean up this code to make it
> usable, but I
> would think that Axis2 should be producing code that, at the
> very least,
> would compile through the ant build if the wsdl2java succeeds,
> which it
> does complete in this case. If not, it should probably give me
> an error
> in the generation of the ADB code.
>
> Maybe its something simple or I'm just a dope, or both, but I
> am lost.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
<!--
Author: Matthew J. Battey
NOTE: This Document is current as of 12/19/2006. Specific names, namespaces,
URLS and
details specific to the implementation may be subject to change
The purpose of this XML Schema Document is to describe the Header routing
information
for data exchange in a Service Oriented Architecture. Specifically, in the
Freight
Information Highway architecture, Web Services are employed. The definition of
Web Services for the purpose of the Freight Information Highway are as follows:
1) A Web Service uses TCP/IP for network protocol
2) A Web Service uses HTTP for application protocol
3) A Web Service uses SOAP to formulate request data protocol
4) A Web Service uses SOAP to formulate response data protocol
5) A Web Service is "Send Only" or "Request/Response"
With this understanding of the FIH definition of Web Services the two elements
defined in this Schema, request-header and response-header, are to be applied
as the datum inside the Header element of the SOAP request and response messages
respectively.
Features of this schema are:
1) Identify the destination of the message using the "To" element.
2) Identify the source of the message using the "From" element.
3) Identify the intended use of the message using the "Action" element.
4) Identify the unique identity of the message using the "MessageID" element.
4.1) Identify the unique identity of the request message which spawned
the response via the "RelatesTo" element.
5) Give proof of authenticity by providing an XML Digital Signature
for the contents of the message via the "Signature" element.
-->
<xs:schema targetNamespace="urn:/fih/1.0"
xmlns:frh="urn:/fih/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";
xmlns:ds="http://www.w3.org/2000/09/xmldsig#";>
<xs:import namespace="http://www.w3.org/2000/09/xmldsig#";
schemaLocation="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd"/>
<xs:import
namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing";
schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing/"/>
<!-- REQUEST -->
<xs:element name="request-header" type="frh:request-header-type">
<xs:annotation>
<xs:documentation>
This element type is to be used as the "Header"
in a SOAP
request message within the FIH Service Oriented
Architecture.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="request-header-type">
<xs:sequence>
<xs:element ref="wsa:To" minOccurs="1" maxOccurs="1" />
<xs:element ref="wsa:From" minOccurs="1" maxOccurs="1"
/>
<xs:element ref="wsa:ReplyTo" minOccurs="0"
maxOccurs="1" />
<xs:element ref="wsa:FaultTo" minOccurs="0"
maxOccurs="1" />
<xs:element ref="wsa:Action" minOccurs="0"
maxOccurs="1" />
<xs:element ref="wsa:MessageID" minOccurs="0"
maxOccurs="1" />
<xs:element ref="ds:Signature" minOccurs="1"
maxOccurs="1">
<xs:annotation>
<xs:documentation>
This signature is to be applied
to the XML data found within the "Body"
element of the Soap Mesasage,
and should refer to the Body element as such.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<!-- RESPONSE -->
<xs:element name="response-header" type="frh:response-header-type">
<xs:annotation>
<xs:documentation>
This element type is to be used as the "Header"
in a SOAP
response message within the FIH Service
Oriented Architecture.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="response-header-type">
<xs:sequence>
<xs:element ref="wsa:To" minOccurs="1" maxOccurs="1" />
<xs:element ref="wsa:From" minOccurs="1" maxOccurs="1"
/>
<xs:element ref="wsa:MessageID" minOccurs="0"
maxOccurs="1" />
<xs:element ref="wsa:RelatesTo" minOccurs="0"
maxOccurs="1">
<xs:annotation>
<xs:documentation>
This element is intended to
contain the MessageID sent in the request
to allow the receiver to
correlate this response to the initial request.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="ds:Signature" minOccurs="1"
maxOccurs="1">
<xs:annotation>
<xs:documentation>
This signature is to be applied
to the XML data found within the "Body"
element of the Soap Mesasage,
and should refer to the Body element as such.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
