You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Stefan Vladov (JIRA)" <ji...@apache.org> on 2008/07/14 10:57:33 UTC
[jira] Created: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Message level policy not serialized correctly in wsdl 1.1
---------------------------------------------------------
Key: AXIS2-3907
URL: https://issues.apache.org/jira/browse/AXIS2-3907
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.4
Environment: any
Reporter: Stefan Vladov
AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling {code}addPolicyAsExtElement(inaxisMessage, input) {code} (respectively {code}addPolicyAsExtElement(outAxisMessage, output){code} for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the {code}WSDL11ToAxisServiceBuilder #populateOperations{code}, when calling {code}copyExtensibleElements{code} for the respective message the builder passes {code}message.getExtensibilityElements(){code} instead of for example {code}wsdl4jInputMessage.getExtensibilityElements(){code} (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Updated: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya updated AXIS2-3907:
----------------------------------------------
Fix Version/s: 1.4.1
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Fix For: 1.4.1
>
> Attachments: AxisService2WSDL11_message_policy.txt, TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling
> addPolicyAsExtElement(inaxisMessage, input)
> (respectively
> addPolicyAsExtElement(outAxisMessage, output)
> for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the
> WSDL11ToAxisServiceBuilder #populateOperations
> when calling
> copyExtensibleElements
> for the respective message the builder passes
> message.getExtensibilityElements()
> instead of for example
> wsdl4jInputMessage.getExtensibilityElements()
> (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Updated: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Stefan Vladov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Vladov updated AXIS2-3907:
---------------------------------
Attachment: AxisService2WSDL11_message_policy.txt
And here's a patch for the proposed fix...
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Attachments: AxisService2WSDL11_message_policy.txt, TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling {code}addPolicyAsExtElement(inaxisMessage, input) {code} (respectively {code}addPolicyAsExtElement(outAxisMessage, output){code} for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the {code}WSDL11ToAxisServiceBuilder #populateOperations{code}, when calling {code}copyExtensibleElements{code} for the respective message the builder passes {code}message.getExtensibilityElements(){code} instead of for example {code}wsdl4jInputMessage.getExtensibilityElements(){code} (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Updated: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Stefan Vladov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Vladov updated AXIS2-3907:
---------------------------------
Description:
AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling
addPolicyAsExtElement(inaxisMessage, input)
(respectively
addPolicyAsExtElement(outAxisMessage, output)
for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the
WSDL11ToAxisServiceBuilder #populateOperations
when calling
copyExtensibleElements
for the respective message the builder passes
message.getExtensibilityElements()
instead of for example
wsdl4jInputMessage.getExtensibilityElements()
(which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
was:
AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling {code}addPolicyAsExtElement(inaxisMessage, input) {code} (respectively {code}addPolicyAsExtElement(outAxisMessage, output){code} for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the {code}WSDL11ToAxisServiceBuilder #populateOperations{code}, when calling {code}copyExtensibleElements{code} for the respective message the builder passes {code}message.getExtensibilityElements(){code} instead of for example {code}wsdl4jInputMessage.getExtensibilityElements(){code} (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Attachments: AxisService2WSDL11_message_policy.txt, TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling
> addPolicyAsExtElement(inaxisMessage, input)
> (respectively
> addPolicyAsExtElement(outAxisMessage, output)
> for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the
> WSDL11ToAxisServiceBuilder #populateOperations
> when calling
> copyExtensibleElements
> for the respective message the builder passes
> message.getExtensibilityElements()
> instead of for example
> wsdl4jInputMessage.getExtensibilityElements()
> (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Updated: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Stefan Vladov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Vladov updated AXIS2-3907:
---------------------------------
Attachment: TestEcho2Result.wsdl
And here is the result wsdl that I get when requesting http://localhost:8080/wsstack/services/TestEcho2?wsdl
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Attachments: TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling {code}addPolicyAsExtElement(inaxisMessage, input) {code} (respectively {code}addPolicyAsExtElement(outAxisMessage, output){code} for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the {code}WSDL11ToAxisServiceBuilder #populateOperations{code}, when calling {code}copyExtensibleElements{code} for the respective message the builder passes {code}message.getExtensibilityElements(){code} instead of for example {code}wsdl4jInputMessage.getExtensibilityElements(){code} (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Resolved: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya resolved AXIS2-3907.
-----------------------------------------------
Resolution: Fixed
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Assignee: Sanka Samaranayake
> Fix For: 1.4.1
>
> Attachments: AxisService2WSDL11_message_policy.txt, TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling
> addPolicyAsExtElement(inaxisMessage, input)
> (respectively
> addPolicyAsExtElement(outAxisMessage, output)
> for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the
> WSDL11ToAxisServiceBuilder #populateOperations
> when calling
> copyExtensibleElements
> for the respective message the builder passes
> message.getExtensibilityElements()
> instead of for example
> wsdl4jInputMessage.getExtensibilityElements()
> (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Commented: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618325#action_12618325 ]
Nandana Mihindukulasooriya commented on AXIS2-3907:
---------------------------------------------------
According to the schema [1] of the WSDL 1.1, I don't think we can have extensible elements in the message elements even though WS-I Basic Profile 1.1 allows it. So I think it is better to attach and pick message level policies only from wsdl:portType/wsdl:operation/wsdl:input ,wsdl:portType/wsdl:operation/wsdl:output using @wsp:PolicyURIs attribute as defined in WS-PolicyAttachment [2]. So I changed the 1.4.1 branch head to both pick and attach message level policies from/to wsdl:portType/wsdl:operation/wsdl:input(output).
[1] - http://www.w3.org/TR/wsdl#A4.1
[2] - http://www.w3.org/Submission/WS-PolicyAttachment/#AttachingPolicyUsingWSDL1.1
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Assignee: Sanka Samaranayake
> Fix For: 1.4.1
>
> Attachments: AxisService2WSDL11_message_policy.txt, TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling
> addPolicyAsExtElement(inaxisMessage, input)
> (respectively
> addPolicyAsExtElement(outAxisMessage, output)
> for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the
> WSDL11ToAxisServiceBuilder #populateOperations
> when calling
> copyExtensibleElements
> for the respective message the builder passes
> message.getExtensibilityElements()
> instead of for example
> wsdl4jInputMessage.getExtensibilityElements()
> (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Updated: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Stefan Vladov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Vladov updated AXIS2-3907:
---------------------------------
Attachment: TestEcho2.wsdl
Here is the wsdl with which I deploy the service.
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Attachments: TestEcho2.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling {code}addPolicyAsExtElement(inaxisMessage, input) {code} (respectively {code}addPolicyAsExtElement(outAxisMessage, output){code} for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the {code}WSDL11ToAxisServiceBuilder #populateOperations{code}, when calling {code}copyExtensibleElements{code} for the respective message the builder passes {code}message.getExtensibilityElements(){code} instead of for example {code}wsdl4jInputMessage.getExtensibilityElements(){code} (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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
[jira] Assigned: (AXIS2-3907) Message level policy not serialized
correctly in wsdl 1.1
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-3907:
----------------------------------------
Assignee: Sanka Samaranayake
> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
> Key: AXIS2-3907
> URL: https://issues.apache.org/jira/browse/AXIS2-3907
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: any
> Reporter: Stefan Vladov
> Assignee: Sanka Samaranayake
> Fix For: 1.4.1
>
> Attachments: AxisService2WSDL11_message_policy.txt, TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling
> addPolicyAsExtElement(inaxisMessage, input)
> (respectively
> addPolicyAsExtElement(outAxisMessage, output)
> for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the
> WSDL11ToAxisServiceBuilder #populateOperations
> when calling
> copyExtensibleElements
> for the respective message the builder passes
> message.getExtensibilityElements()
> instead of for example
> wsdl4jInputMessage.getExtensibilityElements()
> (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...
--
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