[jira] Created: (AXIS2-3085) In And Out message configuration not reflected in WSDL

2007-08-06 Thread deepak pansheriya (JIRA)
In And Out message configuration not reflected in WSDL
--

 Key: AXIS2-3085
 URL: https://issues.apache.org/jira/browse/AXIS2-3085
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.2
 Environment: JBoss 4.0, WIN XP, java 1.4
Reporter: deepak pansheriya
 Fix For: 1.3


Hi all,
When I use following file as my configuration file
service name=WITSMLService 
description
Testing  AXIS2
/description
messageReceivers
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; 
class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver /
messageReceiver  mep=http://www.w3.org/2004/08/wsdl/in-out;  
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/
/messageReceivers
parameter name=ServiceClass 
locked=falseorg.epoch.witsml.services.WITSMLService/parameter
operation name=WMLS_GetFromStore 
mep=http://www.w3.org/2004/08/wsdl/in-out;
!-- messageReceiver  
mep=http://www.w3.org/2004/08/wsdl/in-out;  
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/--
message label=In
parameter name=WellTypeIn 
locked=falseWellTypeIn/parameter
parameter name=XMLIn locked=falseXMLIn/parameter
parameter name=resultId locked=falsefoo/parameter
/message
message label=Out
parameter name=result locked=falseusername/parameter
parameter name=XMLOut locked=falseXMLOut/parameter
parameter name=SuppMsgOut 
locked=falseSuppMsgOut/parameter
/message
/operation
/service

I get WSDL which is not valid according to above configuration. 
According to above configuration my WSDL should have GetFromStore method with 3 
input and 3 output parameter. bet i get method with 5 input and 1 output 
parameter. my method signature is as below:

public short WMLS_GetFromStore(String WMLtypeIn, String queryIn, String 
optionsIn, String capabilitiesIn, javax.xml.rpc.holders.StringHolder XMLout, 
javax.xml.rpc.holders.StringHolder suppMsgOut)


The output WSDL when I retrieve with WSDL query from browser is  as below
- wsdl:definitions xmlns:axis2=http://services.witsml.epoch.org; 
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; 
xmlns:ns0=http://services.witsml.epoch.org/xsd; 
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; 
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; 
xmlns:ns1=http://org.apache.axis2/xsd; 
xmlns:xs=http://www.w3.org/2001/XMLSchema; 
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; 
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
targetNamespace=http://services.witsml.epoch.org;
  wsdl:documentationWITSMLService/wsdl:documentation 
- wsdl:types
- xs:schema xmlns:ns=http://services.witsml.epoch.org/xsd; 
attributeFormDefault=qualified elementFormDefault=qualified 
targetNamespace=http://services.witsml.epoch.org/xsd;
- xs:element name=WMLS_GetFromStore
- xs:complexType
- xs:sequence
  xs:element name=WMLtypeIn nillable=true type=xs:string / 
  xs:element name=queryIn nillable=true type=xs:string / 
  xs:element name=optionsIn nillable=true type=xs:string / 
  xs:element name=capabilitiesIn nillable=true type=xs:string / 
  xs:element name=XMLout nillable=true type=xs:anyType / 
  xs:element name=suppMsgOut nillable=true type=xs:anyType / 
  /xs:sequence
  /xs:complexType
  /xs:element
- xs:element name=WMLS_GetFromStoreResponse
- xs:complexType
- xs:sequence
  xs:element name=return nillable=true type=xs:short / 
  /xs:sequence
  /xs:complexType
  /xs:element
  /xs:schema
  /wsdl:types
- wsdl:message name=WMLS_GetFromStoreMessage
  wsdl:part name=part1 element=ns0:WMLS_GetFromStore / 
  /wsdl:message
- wsdl:message name=WMLS_GetFromStoreResponse
  wsdl:part name=part1 element=ns0:WMLS_GetFromStoreResponse / 
  /wsdl:message
- wsdl:portType name=WITSMLServicePortType
- wsdl:operation name=WMLS_GetFromStore
  wsdl:input xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; 
message=axis2:WMLS_GetFromStoreMessage wsaw:Action=urn:WMLS_GetFromStore / 
  wsdl:output message=axis2:WMLS_GetFromStoreResponse / 
  /wsdl:operation
  /wsdl:portType
- wsdl:binding name=WITSMLServiceSOAP11Binding 
type=axis2:WITSMLServicePortType
  soap:binding transport=http://schemas.xmlsoap.org/soap/http; 
style=document / 
- wsdl:operation name=WMLS_GetFromStore
  soap:operation soapAction=urn:WMLS_GetFromStore style=document / 
- wsdl:input
  soap:body use=literal / 
  /wsdl:input
- wsdl:output
  soap:body use=literal / 
  /wsdl:output
  /wsdl:operation
  /wsdl:binding
- wsdl:binding name=WITSMLServiceSOAP12Binding 
type=axis2:WITSMLServicePortType
  soap12:binding transport=http://schemas.xmlsoap.org/soap/http; 
style=document / 
- wsdl:operation name=WMLS_GetFromStore
  soap12:operation

[jira] Updated: (AXIS2-3085) In And Out message configuration not reflected in WSDL

2007-08-06 Thread deepak pansheriya (JIRA)

 [ 
https://issues.apache.org/jira/browse/AXIS2-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

deepak pansheriya updated AXIS2-3085:
-

Attachment: store.wsdl
services.xml

here I have attached service and WSDL files.

 In And Out message configuration not reflected in WSDL
 --

 Key: AXIS2-3085
 URL: https://issues.apache.org/jira/browse/AXIS2-3085
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.2
 Environment: JBoss 4.0, WIN XP, java 1.4
Reporter: deepak pansheriya
 Fix For: 1.3

 Attachments: services.xml, store.wsdl


 Hi all,
 When I use following file as my configuration file
 service name=WITSMLService 
   description
   Testing  AXIS2
   /description
   messageReceivers
   messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; 
 class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver /
   messageReceiver  mep=http://www.w3.org/2004/08/wsdl/in-out;  
 class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/
   /messageReceivers
   parameter name=ServiceClass 
 locked=falseorg.epoch.witsml.services.WITSMLService/parameter
   operation name=WMLS_GetFromStore 
 mep=http://www.w3.org/2004/08/wsdl/in-out;
   !-- messageReceiver  
 mep=http://www.w3.org/2004/08/wsdl/in-out;  
 class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/--
   message label=In
   parameter name=WellTypeIn 
 locked=falseWellTypeIn/parameter
   parameter name=XMLIn locked=falseXMLIn/parameter
   parameter name=resultId locked=falsefoo/parameter
   /message
   message label=Out
   parameter name=result locked=falseusername/parameter
   parameter name=XMLOut locked=falseXMLOut/parameter
   parameter name=SuppMsgOut 
 locked=falseSuppMsgOut/parameter
   /message
   /operation
 /service
 I get WSDL which is not valid according to above configuration. 
 According to above configuration my WSDL should have GetFromStore method with 
 3 input and 3 output parameter. bet i get method with 5 input and 1 output 
 parameter. my method signature is as below:
 public short WMLS_GetFromStore(String WMLtypeIn, String queryIn, String 
 optionsIn, String capabilitiesIn, javax.xml.rpc.holders.StringHolder XMLout, 
 javax.xml.rpc.holders.StringHolder suppMsgOut)
 The output WSDL when I retrieve with WSDL query from browser is  as below
 - wsdl:definitions xmlns:axis2=http://services.witsml.epoch.org; 
 xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; 
 xmlns:ns0=http://services.witsml.epoch.org/xsd; 
 xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; 
 xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; 
 xmlns:ns1=http://org.apache.axis2/xsd; 
 xmlns:xs=http://www.w3.org/2001/XMLSchema; 
 xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; 
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
 targetNamespace=http://services.witsml.epoch.org;
   wsdl:documentationWITSMLService/wsdl:documentation 
 - wsdl:types
 - xs:schema xmlns:ns=http://services.witsml.epoch.org/xsd; 
 attributeFormDefault=qualified elementFormDefault=qualified 
 targetNamespace=http://services.witsml.epoch.org/xsd;
 - xs:element name=WMLS_GetFromStore
 - xs:complexType
 - xs:sequence
   xs:element name=WMLtypeIn nillable=true type=xs:string / 
   xs:element name=queryIn nillable=true type=xs:string / 
   xs:element name=optionsIn nillable=true type=xs:string / 
   xs:element name=capabilitiesIn nillable=true type=xs:string / 
   xs:element name=XMLout nillable=true type=xs:anyType / 
   xs:element name=suppMsgOut nillable=true type=xs:anyType / 
   /xs:sequence
   /xs:complexType
   /xs:element
 - xs:element name=WMLS_GetFromStoreResponse
 - xs:complexType
 - xs:sequence
   xs:element name=return nillable=true type=xs:short / 
   /xs:sequence
   /xs:complexType
   /xs:element
   /xs:schema
   /wsdl:types
 - wsdl:message name=WMLS_GetFromStoreMessage
   wsdl:part name=part1 element=ns0:WMLS_GetFromStore / 
   /wsdl:message
 - wsdl:message name=WMLS_GetFromStoreResponse
   wsdl:part name=part1 element=ns0:WMLS_GetFromStoreResponse / 
   /wsdl:message
 - wsdl:portType name=WITSMLServicePortType
 - wsdl:operation name=WMLS_GetFromStore
   wsdl:input xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; 
 message=axis2:WMLS_GetFromStoreMessage wsaw:Action=urn:WMLS_GetFromStore 
 / 
   wsdl:output message=axis2:WMLS_GetFromStoreResponse / 
   /wsdl:operation
   /wsdl:portType
 - wsdl:binding name=WITSMLServiceSOAP11Binding 
 type=axis2:WITSMLServicePortType
   soap:binding transport=http://schemas.xmlsoap.org/soap/http; 
 style=document / 
 - wsdl:operation name=WMLS_GetFromStore
   soap:operation soapAction

[axis2] Importing source in Eclipse

2007-08-01 Thread deepak . pansheriya
Hi All,

I am new to maven and interested in axis2 development. Could anybody 
suggest me how to import axis2 project in eclipse. So i can start my 
contribution to axis2 team.

thanks,
Deepak Jerambhai Pansheriya
Tata Consultancy Services
Yantra Park -(STPI)
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com

Experience certainty. IT Services
   Business Solutions
   Outsourcing

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you