You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "Malinda Kaushalye Kapuruge (JIRA)" <ji...@apache.org> on 2008/07/08 05:04:31 UTC
[jira] Created: (RAMPARTC-114) Timestamp recision in milliseconds
Timestamp recision in milliseconds
----------------------------------
Key: RAMPARTC-114
URL: https://issues.apache.org/jira/browse/RAMPARTC-114
Project: Rampart/C
Issue Type: New Feature
Components: Rampart-core
Affects Versions: Current
Environment: N/A
Reporter: Malinda Kaushalye Kapuruge
Assignee: Malinda Kaushalye Kapuruge
Fix For: Current
We need to give the user the option of specifying whether it's required or not to use milliseconds in times stamps.
Simply introduce the new assertion to the policy as a Rampar/C Config policy
<rampc:precisionInMilliseconds>false/true</rampc:precisionInMilliseconds>
Some implementations fail to identify the milliseconds appearing in the timestamps. The default behavior should be
"true"=>milliseconds appear in the timestamp
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (RAMPARTC-114) Timestamp precision in milliseconds
Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
S.Uthaiyashankar resolved RAMPARTC-114.
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: Current)
1.3.0
Assignee: S.Uthaiyashankar (was: Malinda Kaushalye Kapuruge)
Fixed in revision 701336.
Introduced new assertion <rampc:PrecisionInMilliseconds>. values will be in True/False.
> Timestamp precision in milliseconds
> ------------------------------------
>
> Key: RAMPARTC-114
> URL: https://issues.apache.org/jira/browse/RAMPARTC-114
> Project: Rampart/C
> Issue Type: New Feature
> Components: Rampart-core
> Affects Versions: Current
> Environment: N/A
> Reporter: Malinda Kaushalye Kapuruge
> Assignee: S.Uthaiyashankar
> Fix For: 1.3.0
>
>
> We need to give the user the option of specifying whether it's required or not to use milliseconds in times stamps.
> Simply introduce the new assertion to the policy as a Rampar/C Config policy
> <rampc:precisionInMilliseconds>false/true</rampc:precisionInMilliseconds>
> Some implementations fail to identify the milliseconds appearing in the timestamps. The default behavior should be
> "true"=>milliseconds appear in the timestamp
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPARTC-114) Timestamp precision in milliseconds
Posted by "Malinda Kaushalye Kapuruge (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Malinda Kaushalye Kapuruge updated RAMPARTC-114:
------------------------------------------------
Summary: Timestamp precision in milliseconds (was: Timestamp recision in milliseconds)
> Timestamp precision in milliseconds
> ------------------------------------
>
> Key: RAMPARTC-114
> URL: https://issues.apache.org/jira/browse/RAMPARTC-114
> Project: Rampart/C
> Issue Type: New Feature
> Components: Rampart-core
> Affects Versions: Current
> Environment: N/A
> Reporter: Malinda Kaushalye Kapuruge
> Assignee: Malinda Kaushalye Kapuruge
> Fix For: Current
>
>
> We need to give the user the option of specifying whether it's required or not to use milliseconds in times stamps.
> Simply introduce the new assertion to the policy as a Rampar/C Config policy
> <rampc:precisionInMilliseconds>false/true</rampc:precisionInMilliseconds>
> Some implementations fail to identify the milliseconds appearing in the timestamps. The default behavior should be
> "true"=>milliseconds appear in the timestamp
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.