You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Matthias Gaiser (JIRA)" <ji...@apache.org> on 2010/04/21 09:38:51 UTC

[jira] Created: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
----------------------------------------------------

                 Key: AXIS2-4686
                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
             Project: Axis2
          Issue Type: Bug
          Components: codegen, wsdl
    Affects Versions: 1.5, 1.5.1
            Reporter: Matthias Gaiser


I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
Assertion: BP2120
Result failed 
Failure Message A binding has operations that are not unique. 

I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.

I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Commented: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865803#action_12865803 ] 

Matthias Gaiser commented on AXIS2-4686:
----------------------------------------

I agree, one message with zero parts is allowed.

But if you have multiple operations which use request messages with no parts, it can not be distinguished with the body which action to take and therefore violates the Basic Profile 1.1.

Please have a look at:
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#R2710

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Reopened: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi reopened AXIS2-4686:
-------------------------------------------------

      Assignee: Amila Chinthaka Suriarachchi  (was: Lahiru Gunathilake)

please have a look at [1].

it does not say it is not allowed have messages with zero parts.

[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Assigned: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake reassigned AXIS2-4686:
-----------------------------------------

    Assignee: Lahiru Gunathilake

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Updated: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Gaiser updated AXIS2-4686:
-----------------------------------

    Attachment: testws.zip

Containing the test class, the generated wsdl, the corrected wsdl and the build script used to generate the wsdl.

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Updated: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Gaiser updated AXIS2-4686:
-----------------------------------

    Attachment: testws.zip

Containing the test class, the generated wsdl, the corrected wsdl and the build script used to generate the wsdl.

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Updated: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Gaiser updated AXIS2-4686:
-----------------------------------

    Attachment: testws.zip

Containing the test class, the generated wsdl, the corrected wsdl and the build script used to generate the wsdl.

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Reopened: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi reopened AXIS2-4686:
-------------------------------------------------

      Assignee: Amila Chinthaka Suriarachchi  (was: Lahiru Gunathilake)

please have a look at [1].

it does not say it is not allowed have messages with zero parts.

[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Commented: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865803#action_12865803 ] 

Matthias Gaiser commented on AXIS2-4686:
----------------------------------------

I agree, one message with zero parts is allowed.

But if you have multiple operations which use request messages with no parts, it can not be distinguished with the body which action to take and therefore violates the Basic Profile 1.1.

Please have a look at:
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#R2710

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Resolved: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AXIS2-4686.
---------------------------------------

    Resolution: Fixed

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Resolved: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AXIS2-4686.
---------------------------------------

    Resolution: Fixed

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Commented: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865803#action_12865803 ] 

Matthias Gaiser commented on AXIS2-4686:
----------------------------------------

I agree, one message with zero parts is allowed.

But if you have multiple operations which use request messages with no parts, it can not be distinguished with the body which action to take and therefore violates the Basic Profile 1.1.

Please have a look at:
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#R2710

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Assigned: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake reassigned AXIS2-4686:
-----------------------------------------

    Assignee: Lahiru Gunathilake

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Resolved: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AXIS2-4686.
---------------------------------------

    Resolution: Fixed

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Resolved: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AXIS2-4686.
---------------------------------------

    Resolution: Fixed

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Resolved: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AXIS2-4686.
---------------------------------------

    Resolution: Fixed

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Reopened: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi reopened AXIS2-4686:
-------------------------------------------------

      Assignee: Amila Chinthaka Suriarachchi  (was: Lahiru Gunathilake)

please have a look at [1].

it does not say it is not allowed have messages with zero parts.

[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Reopened: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi reopened AXIS2-4686:
-------------------------------------------------

      Assignee: Amila Chinthaka Suriarachchi  (was: Lahiru Gunathilake)

please have a look at [1].

it does not say it is not allowed have messages with zero parts.

[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Assigned: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake reassigned AXIS2-4686:
-----------------------------------------

    Assignee: Lahiru Gunathilake

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Updated: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Gaiser updated AXIS2-4686:
-----------------------------------

    Attachment: testws.zip

Containing the test class, the generated wsdl, the corrected wsdl and the build script used to generate the wsdl.

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Updated: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Gaiser updated AXIS2-4686:
-----------------------------------

    Attachment: testws.zip

Containing the test class, the generated wsdl, the corrected wsdl and the build script used to generate the wsdl.

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Assigned: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake reassigned AXIS2-4686:
-----------------------------------------

    Assignee: Lahiru Gunathilake

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Reopened: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Chinthaka Suriarachchi reopened AXIS2-4686:
-------------------------------------------------

      Assignee: Amila Chinthaka Suriarachchi  (was: Lahiru Gunathilake)

please have a look at [1].

it does not say it is not allowed have messages with zero parts.

[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Assigned: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake reassigned AXIS2-4686:
-----------------------------------------

    Assignee: Lahiru Gunathilake

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Lahiru Gunathilake
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Commented: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865803#action_12865803 ] 

Matthias Gaiser commented on AXIS2-4686:
----------------------------------------

I agree, one message with zero parts is allowed.

But if you have multiple operations which use request messages with no parts, it can not be distinguished with the body which action to take and therefore violates the Basic Profile 1.1.

Please have a look at:
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#R2710

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] Commented: (AXIS2-4686) SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant

Posted by "Matthias Gaiser (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865803#action_12865803 ] 

Matthias Gaiser commented on AXIS2-4686:
----------------------------------------

I agree, one message with zero parts is allowed.

But if you have multiple operations which use request messages with no parts, it can not be distinguished with the body which action to take and therefore violates the Basic Profile 1.1.

Please have a look at:
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#R2710

> SOAP 1.1 Binding not WSI Basic Profile 1.1 compliant
> ----------------------------------------------------
>
>                 Key: AXIS2-4686
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4686
>             Project: Axis2
>          Issue Type: Bug
>          Components: codegen, wsdl
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Matthias Gaiser
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: testws.zip
>
>
> I use Java2WSDL to generate a wsdl for my java code. I have a java class with two methods which do not have any input parameters. Java2wsdl generates empty messages for them, so that the SOAP body does not include any elements.
> I checked the generated wsdl for the SOAP 1.1 binding with the WSI test tool for conformance with the WSI Basic Profile 1.1 and it did not validate successfully:
> Assertion: BP2120
> Result failed 
> Failure Message A binding has operations that are not unique. 
> I then maually corrected the wsdl by adding an empty element with the function name inside the message. This enabled the wsdl to successfully validate against Basic Profile 1.1.
> I will upload a zip with my test java class, build script with the java2wsdl, the original wsdl and my corrected wsdl.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org