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 "Antonio Andrade (JIRA)" <ji...@apache.org> on 2008/09/30 22:17:44 UTC
[jira] Created: (AXIS2-4057) OutOnlyAxisOperation: AxisMessage
passed to the addMessage method is not saved as a child of the
AxisOperation
OutOnlyAxisOperation: AxisMessage passed to the addMessage method is not saved as a child of the AxisOperation
--------------------------------------------------------------------------------------------------------------
Key: AXIS2-4057
URL: https://issues.apache.org/jira/browse/AXIS2-4057
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.4
Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.75Gh
Reporter: Antonio Andrade
Priority: Minor
Observed Behavior:
The AxisMessage passed to the OutOnlyAxisOperation.addMessage(AxisMessage, String) method is not saved as a child of the AxisOperation. It's not returned when calling its getChildren method. Instead, the AxisMessage returned is the one created at instantiation time (See OutOnlyAxisOperation .createMessage).
Expected Behavior:
If an AxisMessage is added to an OutOnlyAxisOperation through its addMessage method, the message should be available when calling its getChildren method.
--
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-4057) OutOnlyAxisOperation: AxisMessage
passed to the addMessage method is not saved as a child of the
AxisOperation
Posted by "Antonio Andrade (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Andrade updated AXIS2-4057:
-----------------------------------
Attachment: AXIS2-4057.patch
OutOnlyAxisOperationTest.java
AXIS2-4057: Attaching Patch and JUnit Test. Ready for Review.
1) Adding AxisMessage passed to the OutOnlyAxisOperation.addMessage(AxisMessage, String) as a child of the AxisOperation.
2) Removing the 'outMessage' instance variable in favor of retrieving the AxisMessage from the Map containing its children. Refactoring code accordingly.
> OutOnlyAxisOperation: AxisMessage passed to the addMessage method is not saved as a child of the AxisOperation
> --------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4057
> URL: https://issues.apache.org/jira/browse/AXIS2-4057
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4
> Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.75Gh
> Reporter: Antonio Andrade
> Priority: Minor
> Attachments: AXIS2-4057.patch, OutOnlyAxisOperationTest.java
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Observed Behavior:
> The AxisMessage passed to the OutOnlyAxisOperation.addMessage(AxisMessage, String) method is not saved as a child of the AxisOperation. It's not returned when calling its getChildren method. Instead, the AxisMessage returned is the one created at instantiation time (See OutOnlyAxisOperation .createMessage).
> Expected Behavior:
> If an AxisMessage is added to an OutOnlyAxisOperation through its addMessage method, the message should be available when calling its getChildren method.
--
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