[jira] Updated: (SANDESHA2-181) issues with SandeshaPolicy Bean
"Amila Chinthaka Suriarachchi (JIRA)" <[email protected]>
| Newsgroups | gmane.comp.apache.webservices.fx.devel |
|---|---|
| Message-ID | <820506187.1226486384599.JavaMail.jira@brutus> |
[ https://issues.apache.org/jira/browse/SANDESHA2-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi updated SANDESHA2-181:
---------------------------------------------------
Attachment: patch.txt
this patch fix the problem
> issues with SandeshaPolicy Bean
> -------------------------------
>
> Key: SANDESHA2-181
> URL: https://issues.apache.org/jira/browse/SANDESHA2-181
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Amila Chinthaka Suriarachchi
> Attachments: patch.txt
>
>
> When serializing,
> Sandesha policy bean saves the inactivityTimeoutMeasure and sequenceRemovalTimeout measure. This causes a problem since corresponding time values are stored in bean as milliSeconds. When building back the policy object at the RMAssertionBuilder this again convert the saved value to milliseconds.
> in timeout setting methods even for measure == null case it has to saved to temp variable. otherwise it overrides the value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.