axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-2694) Trouble using complex type definitions
Date Sun, 01 Jul 2007 00:56:04 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509344
] 

Davanum Srinivas commented on AXIS2-2694:
-----------------------------------------

Specific issue is because of the wrong message sent by the client. Please ask other questions
on the mailing list.

thanks,
dims

> Trouble using complex type definitions
> --------------------------------------
>
>                 Key: AXIS2-2694
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2694
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Windows XP, Tomcat 5.0
>            Reporter: Helmut Ackermann
>            Assignee: Amila Chinthaka Suriarachchi
>            Priority: Blocker
>             Fix For: 1.3
>
>         Attachments: Main.java, Main.java
>
>
> Hi all,
> I installed an Axis 1.2 version in a Tomcat 5.0 container on a Windows XP system.
> I defined a simple web service using the WSDL 2.0 specification, see below.
> I had only success when the input and output parameters where of type xsd:string.
> Using a complex type definition I ended always with an error like
> "java.lang.RuntimeException: Unexpected subelement getRelatedConcepts"
> Also it was not possible to invoke the Rest service from the browser the input string
had not been transfered.
> Against when I tried the same with your MyService.echo example it worked fine.
> Here are my questions:
> Why is the types section of the echo MyService.wsdl2 file so long, is it really necessary
to include all this stuff?
> Can one already work with schema includes and import, do you provide a proper example?
> Most important:
> how does one has to specify a operation (method) in the call ServiceClient and in case
of Rest in the browser-URL?
> how does one specify the parameters in a ServiceClient (using no generated stub)?
> Is there any simple and short explanation of the dispatching algorithm?
> What is the freedom when defining methods and parameter types in the types-section of
a wsdl 2.0?
> What pattern do you recommend for that?
> What is the real effect of the "useOriginalwsdl" parameter in the services file - when
it is true and when it is false?
> Is the error message: 
> "java.net.URISyntaxException: Illegal character in path at index 20: file:/D:/Exec/Tomcat
5.0/work/Ca talina/localhost/axis2_2.1/loader/META-INF/schema.catalog" 
> in my Tomcat window serious - and if what is wrong with my installation?
> Thank you very much in advance
> Helmut Ackermann
> Deutscher Wetterdienst
> Kaiserleistraße 42
> 63067 Offenbach
> Germany
> Helmut.Ackermann@dwd.de
> here is the WSDL I was using:
> <ws2:description 
>     xmlns:ws2="http://www.w3.org/ns/wsdl"
>     targetNamespace="http://onto.vmc.org/ontoService/wsdl2"
>     xmlns:tns="http://onto.vmc.org/ontoService/wsdl2"
>     xmlns:ons="http://onto.vmc.org/ontomenu"
>     xmlns:wsoap="http://www.w3.org/ns/wsdl/soap"
>     xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
>     xmlns:wsdlx="http://www.w3.org/ns/wsdl-extensions"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>     xsi:schemaLocation="http://www.w3.org/ns/wsdl/soap http://www.w3.org/2002/ws/desc/ns/soap.xsd
http://www.w3.org/2003/05/soap-envelope http://www.w3.org/2003/05/soap-envelope http://www.w3.org/ns/wsdl-extensions
http://www.w3.org/2002/ws/desc/ns/wsdl-extensions.xsd http://www.w3.org/ns/wsdl http://www.w3.org/2002/ws/desc/ns/wsdl20.xsd
http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema.xsd"
>     >
>     
>   <!-- Type definitions -->
>   <ws2:types>
>     <xsd:schema targetNamespace="http://onto.vmc.org/ontomenu"
>             xmlns:xml="http://www.w3.org/XML/1998/namespace"
>                 xmlns:ons="http://onto.vmc.org/ontomenu" 
>                 xmlns="http://onto.vmc.org/ontomenu"> 
>       <!--xsd:include schemaLocation="OntoServiceSchema.xsd"/-->
>       
>       <xsd:element name="getRelatedConcepts" type="xsd:string"/>
>       
>       <!-- das folgende läuft bislang nicht auch mit dem xsd:include habe ich Probleme

>           noch keine komplexen Typen zum Laufen gebracht!! 15.5.2007 16:10!!
>       <xsd:element name="getRelatedConcepts">
>         <xsd:complexType>
>           <xsd:sequence>
>             <xsd:element name="conceptID" type="xsd:string"/>
>           </xsd:sequence>
>         </xsd:complexType>
>       </xsd:element>
>       -->
>       
>       <xsd:element name="relatedConcepts" type="xsd:string"/>    
>       <!--xsd:element name="relatedConcepts" type="OntoRelativesType"/!-->    
>       <xsd:element name="invalidDataError" type="xsd:string"/>    
>     </xsd:schema>
>   </ws2:types>
>   <!-- -->
>   
>   <ws2:interface name="ontoServiceInterface">
>     <ws2:fault name="invalidDataFault" element="ons:invalidDataError"/>
>       
>     <ws2:operation name="getRelatedConcepts"
>                      pattern="http://www.w3.org/ns/wsdl/in-out"> 
>                      <!--
>                      style="http://www.w3.org/ns/wsdl/style/iri"
>                      wsdlx:safe="true">
>                      -->
>       <!--ws2:input messageLabel="In" element="ons:getRelatedConcepts"/-->
>       <ws2:input messageLabel="In" element="ons:getRelatedConcepts"/>
>       <ws2:output messageLabel="Out" element="ons:relatedConcepts"/>
>       <ws2:outfault ref="tns:invalidDataFault" messageLabel="Out"/>
>     </ws2:operation>
>   </ws2:interface>
>   
>   <ws2:binding name="ontoServiceSOAPBinding"
>                interface="tns:ontoServiceInterface"
>                type="http://www.w3.org/ns/wsdl/soap"
>                wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/">
>     <ws2:operation ref="tns:getRelatedConcepts"
>                    wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response"/>
>     <!--ws2:fault ref="tns:invalidDataFault" wsoap:code="soap:Sender"/-->
>   </ws2:binding>
>   
>   <ws2:service name="ontoService"
>                interface="tns:ontoServiceInterface">
>     <ws2:endpoint name="ontoServiceEndpoint"
>                   binding="tns:ontoServiceSOAPBinding"
>                   address="http://localhost:8080/ontoService-ws2"/>
>   </ws2:service>
>   
> </ws2:description>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message