[jira] Commented: (AXIS2-2609) Incorrectly generated stub functions

2007-08-27 Thread Amila Chinthaka Suriarachchi (JIRA)

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

Amila Chinthaka Suriarachchi commented on AXIS2-2609:
-

soap body parts is optional it is correct.
But where the spec says what to do when the parts absent. As you have told most 
of the people do not use the parts element since it is optional. but they 
expect the message part goes through the wire. So Axis2 has implement it as in 
that way.
But if you want not to say something then you have to specify parts=.


 Incorrectly generated stub functions 
 -

 Key: AXIS2-2609
 URL: https://issues.apache.org/jira/browse/AXIS2-2609
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2
Reporter: Gul Onural
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: test.zip


 The release 1.2 wsdl2 java generates incorrect stub functions for the 
 operations that has header part only, no payload.
 This was correctly done with version axis2 1.1.1. Something changed in 
 between the two releases in this area is causing the problem.
 For example, operation and message are defined something similar to  :
   operation name=queryX
  input message=queryXRequest/
  output message=queryXResponse/
   /operation
message name=queryXRequest
   part name=header element=id/
/message
 The generated stubs contains the id twice :
   public  com.mycompany.QueryXResponseDocument queryX(
 com.mycompany.IdDocument id2,
 com.mycompany.IdDocument id3)
 throws java.rmi.RemoteException
 {
 ...
 }

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (AXIS2-2609) Incorrectly generated stub functions

2007-05-10 Thread Amila Chinthaka Suriarachchi (JIRA)

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

Amila Chinthaka Suriarachchi commented on AXIS2-2609:
-

Sorry for the late reply
yes that is how it works in Axis2 1.2.

The problem here is that if you do not say  soap:body parts= use=literal/ 
then some implementation may interpret it not using parts and some may use 
available part as spec has not clearly define this. but if you specifically put 
 soap:body parts= use=literal/ then any implementation should support 
this sine this is define in the spec.

We added lot of WSDL validation code for Axis2 1.2


 Incorrectly generated stub functions 
 -

 Key: AXIS2-2609
 URL: https://issues.apache.org/jira/browse/AXIS2-2609
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2
Reporter: Gul Onural
 Assigned To: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: test.zip


 The release 1.2 wsdl2 java generates incorrect stub functions for the 
 operations that has header part only, no payload.
 This was correctly done with version axis2 1.1.1. Something changed in 
 between the two releases in this area is causing the problem.
 For example, operation and message are defined something similar to  :
   operation name=queryX
  input message=queryXRequest/
  output message=queryXResponse/
   /operation
message name=queryXRequest
   part name=header element=id/
/message
 The generated stubs contains the id twice :
   public  com.mycompany.QueryXResponseDocument queryX(
 com.mycompany.IdDocument id2,
 com.mycompany.IdDocument id3)
 throws java.rmi.RemoteException
 {
 ...
 }

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (AXIS2-2609) Incorrectly generated stub functions

2007-05-03 Thread Gul Onural (JIRA)

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

Gul Onural commented on AXIS2-2609:
---


This behavior has changed since Axis2 1.1, where I didn't have to
specify empty string in the
body part. Omitting body (no soap:body parts= use=literal/) in the
input worked with Axis2 1.1.

Have you had a chance to test if body parts= works with axis2 1.2? 

Gul





 Incorrectly generated stub functions 
 -

 Key: AXIS2-2609
 URL: https://issues.apache.org/jira/browse/AXIS2-2609
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2
Reporter: Gul Onural
 Assigned To: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: test.zip


 The release 1.2 wsdl2 java generates incorrect stub functions for the 
 operations that has header part only, no payload.
 This was correctly done with version axis2 1.1.1. Something changed in 
 between the two releases in this area is causing the problem.
 For example, operation and message are defined something similar to  :
   operation name=queryX
  input message=queryXRequest/
  output message=queryXResponse/
   /operation
message name=queryXRequest
   part name=header element=id/
/message
 The generated stubs contains the id twice :
   public  com.mycompany.QueryXResponseDocument queryX(
 com.mycompany.IdDocument id2,
 com.mycompany.IdDocument id3)
 throws java.rmi.RemoteException
 {
 ...
 }

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (AXIS2-2609) Incorrectly generated stub functions

2007-05-02 Thread Amila Chinthaka Suriarachchi (JIRA)

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

Amila Chinthaka Suriarachchi commented on AXIS2-2609:
-

use 
operation name=sampleOperation
 soap:operation 
soapAction=http://www.mycompany.com/SampleService/queryServers; 
style=document/
 input
soap:header message=tns:sampleRequest part=header 
use=literal/
soap:body parts= use=literal/
 /input
 output
soap:body parts=payload use=literal/
 /output
  /operation

please specifically specify you don't want to send any thing in the body. 
Otherwise it picks the message part as the body part. 

 Incorrectly generated stub functions 
 -

 Key: AXIS2-2609
 URL: https://issues.apache.org/jira/browse/AXIS2-2609
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2
Reporter: Gul Onural
 Assigned To: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: test.zip


 The release 1.2 wsdl2 java generates incorrect stub functions for the 
 operations that has header part only, no payload.
 This was correctly done with version axis2 1.1.1. Something changed in 
 between the two releases in this area is causing the problem.
 For example, operation and message are defined something similar to  :
   operation name=queryX
  input message=queryXRequest/
  output message=queryXResponse/
   /operation
message name=queryXRequest
   part name=header element=id/
/message
 The generated stubs contains the id twice :
   public  com.mycompany.QueryXResponseDocument queryX(
 com.mycompany.IdDocument id2,
 com.mycompany.IdDocument id3)
 throws java.rmi.RemoteException
 {
 ...
 }

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]