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 "Samuel Isokpunwu (JIRA)" <ji...@apache.org> on 2007/07/17 02:07:05 UTC
[jira] Created: (AXIS2-2978) Attachment optimization properties are
not current in client request context
Attachment optimization properties are not current in client request context
----------------------------------------------------------------------------
Key: AXIS2-2978
URL: https://issues.apache.org/jira/browse/AXIS2-2978
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Affects Versions: M2
Reporter: Samuel Isokpunwu
The client request context is not properly updated when mtom enablement state properties changes.
Example test scenario:
{
---------
---------
SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
binding.setMTOMEnabled(true);
---------
response = dispatch.invoke(request);
---------
binding.setMTOMEnabled(false);
---------
response = dispatch.invoke(request);
---------
---------
}
Since the client request context for a previous request is being cached and reused for a subsequent request, any attachment optimization properties changes, in the test scenario above, are ignored. Will be adding code to check and copy over any new properties updates.
--
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-2978) Attachment optimization properties
are not current in client request context
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikhil Thaker resolved AXIS2-2978.
----------------------------------
Resolution: Fixed
Attached patch has already been commited by Rich Scheuerle with Revision # 556730.
> Attachment optimization properties are not current in client request context
> ----------------------------------------------------------------------------
>
> Key: AXIS2-2978
> URL: https://issues.apache.org/jira/browse/AXIS2-2978
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: M2
> Reporter: Samuel Isokpunwu
> Assignee: Nikhil Thaker
> Attachments: bt66899patch.txt
>
>
> The client request context is not properly updated when mtom enablement state properties changes.
> Example test scenario:
> {
> ---------
> ---------
> SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
> binding.setMTOMEnabled(true);
> ---------
> response = dispatch.invoke(request);
> ---------
> binding.setMTOMEnabled(false);
> ---------
> response = dispatch.invoke(request);
> ---------
> ---------
> }
> Since the client request context for a previous request is being cached and reused for a subsequent request, any attachment optimization properties changes, in the test scenario above, are ignored. Will be adding code to check and copy over any new properties updates.
--
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] Closed: (AXIS2-2978) Attachment optimization properties are
not current in client request context
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikhil Thaker closed AXIS2-2978.
--------------------------------
> Attachment optimization properties are not current in client request context
> ----------------------------------------------------------------------------
>
> Key: AXIS2-2978
> URL: https://issues.apache.org/jira/browse/AXIS2-2978
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: M2
> Reporter: Samuel Isokpunwu
> Assignee: Nikhil Thaker
> Attachments: bt66899patch.txt
>
>
> The client request context is not properly updated when mtom enablement state properties changes.
> Example test scenario:
> {
> ---------
> ---------
> SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
> binding.setMTOMEnabled(true);
> ---------
> response = dispatch.invoke(request);
> ---------
> binding.setMTOMEnabled(false);
> ---------
> response = dispatch.invoke(request);
> ---------
> ---------
> }
> Since the client request context for a previous request is being cached and reused for a subsequent request, any attachment optimization properties changes, in the test scenario above, are ignored. Will be adding code to check and copy over any new properties updates.
--
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-2978) Attachment optimization properties are
not current in client request context
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2978:
------------------------------------
Assignee: Jeff Barrett
> Attachment optimization properties are not current in client request context
> ----------------------------------------------------------------------------
>
> Key: AXIS2-2978
> URL: https://issues.apache.org/jira/browse/AXIS2-2978
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: M2
> Reporter: Samuel Isokpunwu
> Assignee: Jeff Barrett
> Attachments: bt66899patch.txt
>
>
> The client request context is not properly updated when mtom enablement state properties changes.
> Example test scenario:
> {
> ---------
> ---------
> SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
> binding.setMTOMEnabled(true);
> ---------
> response = dispatch.invoke(request);
> ---------
> binding.setMTOMEnabled(false);
> ---------
> response = dispatch.invoke(request);
> ---------
> ---------
> }
> Since the client request context for a previous request is being cached and reused for a subsequent request, any attachment optimization properties changes, in the test scenario above, are ignored. Will be adding code to check and copy over any new properties updates.
--
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-2978) Attachment optimization properties
are not current in client request context
Posted by "Jeff Barrett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Barrett reassigned AXIS2-2978:
-----------------------------------
Assignee: Nikhil Thaker (was: Jeff Barrett)
Nikhil is going to handle this.
> Attachment optimization properties are not current in client request context
> ----------------------------------------------------------------------------
>
> Key: AXIS2-2978
> URL: https://issues.apache.org/jira/browse/AXIS2-2978
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: M2
> Reporter: Samuel Isokpunwu
> Assignee: Nikhil Thaker
> Attachments: bt66899patch.txt
>
>
> The client request context is not properly updated when mtom enablement state properties changes.
> Example test scenario:
> {
> ---------
> ---------
> SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
> binding.setMTOMEnabled(true);
> ---------
> response = dispatch.invoke(request);
> ---------
> binding.setMTOMEnabled(false);
> ---------
> response = dispatch.invoke(request);
> ---------
> ---------
> }
> Since the client request context for a previous request is being cached and reused for a subsequent request, any attachment optimization properties changes, in the test scenario above, are ignored. Will be adding code to check and copy over any new properties updates.
--
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-2978) Attachment optimization properties are
not current in client request context
Posted by "Samuel Isokpunwu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samuel Isokpunwu updated AXIS2-2978:
------------------------------------
Attachment: bt66899patch.txt
A patch for the defect.
> Attachment optimization properties are not current in client request context
> ----------------------------------------------------------------------------
>
> Key: AXIS2-2978
> URL: https://issues.apache.org/jira/browse/AXIS2-2978
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: M2
> Reporter: Samuel Isokpunwu
> Attachments: bt66899patch.txt
>
>
> The client request context is not properly updated when mtom enablement state properties changes.
> Example test scenario:
> {
> ---------
> ---------
> SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
> binding.setMTOMEnabled(true);
> ---------
> response = dispatch.invoke(request);
> ---------
> binding.setMTOMEnabled(false);
> ---------
> response = dispatch.invoke(request);
> ---------
> ---------
> }
> Since the client request context for a previous request is being cached and reused for a subsequent request, any attachment optimization properties changes, in the test scenario above, are ignored. Will be adding code to check and copy over any new properties updates.
--
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