You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Matt Lovett (JIRA)" <ji...@apache.org> on 2007/01/30 15:54:33 UTC
[jira] Created: (SANDESHA2-70) Add option to use Message
Serialization with the in-memory store
Add option to use Message Serialization with the in-memory store
----------------------------------------------------------------
Key: SANDESHA2-70
URL: https://issues.apache.org/jira/browse/SANDESHA2-70
Project: Sandesha2
Issue Type: New Feature
Reporter: Matt Lovett
Now that Axis2 has the code to serialize and restore message contexts, as well as the capability to pause and resume the engine, we can use this code instead of sending messages through the sandesha transport. This avoids a second send of each message, and avoids the 'retransmittable phases'.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2-70) Add option to use Message
Serialization with the in-memory store
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Lovett resolved SANDESHA2-70.
----------------------------------
Resolution: Fixed
> Add option to use Message Serialization with the in-memory store
> ----------------------------------------------------------------
>
> Key: SANDESHA2-70
> URL: https://issues.apache.org/jira/browse/SANDESHA2-70
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: Matt Lovett
> Attachments: serialize.patch
>
>
> Now that Axis2 has the code to serialize and restore message contexts, as well as the capability to pause and resume the engine, we can use this code instead of sending messages through the sandesha transport. This avoids a second send of each message, and avoids the 'retransmittable phases'.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-70) Add option to use Message
Serialization with the in-memory store
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Lovett updated SANDESHA2-70:
---------------------------------
Attachment: serialize.patch
This patch demonstrates using the serialisation code, controlled by a flag in the sandesha module xml. It also introduces a re-run of the scenarios tests, with the option enabled.
This patch passes most of the tests, but fails sync 2-way with the 1.0 spec level. The problem seems to be that the transport is never signalled, so the reply messages never get sent. This is probably because the RequestResponseTransport instance doesn't make it through the serialize / deserialze process. I'll fix that before I commit the patch, but I'm attaching what I have so that people can take a look.
Matt
> Add option to use Message Serialization with the in-memory store
> ----------------------------------------------------------------
>
> Key: SANDESHA2-70
> URL: https://issues.apache.org/jira/browse/SANDESHA2-70
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: Matt Lovett
> Attachments: serialize.patch
>
>
> Now that Axis2 has the code to serialize and restore message contexts, as well as the capability to pause and resume the engine, we can use this code instead of sending messages through the sandesha transport. This avoids a second send of each message, and avoids the 'retransmittable phases'.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-70) Add option to use Message
Serialization with the in-memory store
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469657 ]
Chamikara Jayalath commented on SANDESHA2-70:
---------------------------------------------
Hi Matt,
I'm OK with this (providing that it passes all test cases :-) ).
Also hope u will keep the current approach as the default.
Chamikara
> Add option to use Message Serialization with the in-memory store
> ----------------------------------------------------------------
>
> Key: SANDESHA2-70
> URL: https://issues.apache.org/jira/browse/SANDESHA2-70
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: Matt Lovett
> Attachments: serialize.patch
>
>
> Now that Axis2 has the code to serialize and restore message contexts, as well as the capability to pause and resume the engine, we can use this code instead of sending messages through the sandesha transport. This avoids a second send of each message, and avoids the 'retransmittable phases'.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-70) Add option to use Message
Serialization with the in-memory store
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469657 ]
Chamikara Jayalath commented on SANDESHA2-70:
---------------------------------------------
Hi Matt,
I'm OK with this (providing that it passes all test cases :-) ).
Also hope u will keep the current approach as the default.
Chamikara
> Add option to use Message Serialization with the in-memory store
> ----------------------------------------------------------------
>
> Key: SANDESHA2-70
> URL: https://issues.apache.org/jira/browse/SANDESHA2-70
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: Matt Lovett
> Attachments: serialize.patch
>
>
> Now that Axis2 has the code to serialize and restore message contexts, as well as the capability to pause and resume the engine, we can use this code instead of sending messages through the sandesha transport. This avoids a second send of each message, and avoids the 'retransmittable phases'.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2-70) Add option to use Message
Serialization with the in-memory store
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Lovett resolved SANDESHA2-70.
----------------------------------
Resolution: Fixed
> Add option to use Message Serialization with the in-memory store
> ----------------------------------------------------------------
>
> Key: SANDESHA2-70
> URL: https://issues.apache.org/jira/browse/SANDESHA2-70
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: Matt Lovett
> Attachments: serialize.patch
>
>
> Now that Axis2 has the code to serialize and restore message contexts, as well as the capability to pause and resume the engine, we can use this code instead of sending messages through the sandesha transport. This avoids a second send of each message, and avoids the 'retransmittable phases'.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-70) Add option to use Message
Serialization with the in-memory store
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Lovett updated SANDESHA2-70:
---------------------------------
Attachment: serialize.patch
This patch demonstrates using the serialisation code, controlled by a flag in the sandesha module xml. It also introduces a re-run of the scenarios tests, with the option enabled.
This patch passes most of the tests, but fails sync 2-way with the 1.0 spec level. The problem seems to be that the transport is never signalled, so the reply messages never get sent. This is probably because the RequestResponseTransport instance doesn't make it through the serialize / deserialze process. I'll fix that before I commit the patch, but I'm attaching what I have so that people can take a look.
Matt
> Add option to use Message Serialization with the in-memory store
> ----------------------------------------------------------------
>
> Key: SANDESHA2-70
> URL: https://issues.apache.org/jira/browse/SANDESHA2-70
> Project: Sandesha2
> Issue Type: New Feature
> Reporter: Matt Lovett
> Attachments: serialize.patch
>
>
> Now that Axis2 has the code to serialize and restore message contexts, as well as the capability to pause and resume the engine, we can use this code instead of sending messages through the sandesha transport. This avoids a second send of each message, and avoids the 'retransmittable phases'.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org