You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Jeff MAURY (JIRA)" <ji...@apache.org> on 2009/07/11 11:14:14 UTC
[jira] Created: (DIRSTUDIO-500) Review RequestID processing
Review RequestID processing
---------------------------
Key: DIRSTUDIO-500
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-500
Project: Directory Studio
Issue Type: Bug
Components: studio-dsml-parser
Reporter: Jeff MAURY
Fix For: 1.5.0
DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSHARED-53) Review RequestID processing
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874560#action_12874560 ]
Pierre-Arnaud Marcelot commented on DIRSHARED-53:
-------------------------------------------------
The original thread on the ML for this issue is available here:
http://directory.markmail.org/thread/bjlswcnhoi5d254j
> Review RequestID processing
> ---------------------------
>
> Key: DIRSHARED-53
> URL: https://issues.apache.org/jira/browse/DIRSHARED-53
> Project: Directory Shared
> Issue Type: Bug
> Reporter: Jeff MAURY
> Fix For: 0.9.20
>
>
> DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSHARED-53) Review RequestID processing
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSHARED-53:
---------------------------------------
Fix Version/s: 0.9.20
(was: 0.9.19)
> Review RequestID processing
> ---------------------------
>
> Key: DIRSHARED-53
> URL: https://issues.apache.org/jira/browse/DIRSHARED-53
> Project: Directory Shared
> Issue Type: Bug
> Reporter: Jeff MAURY
> Fix For: 0.9.20
>
>
> DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSHARED-53) Review RequestID processing
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864257#action_12864257 ]
Emmanuel Lecharny commented on DIRSHARED-53:
--------------------------------------------
I'm not sure I clearly understand the problem...
> Review RequestID processing
> ---------------------------
>
> Key: DIRSHARED-53
> URL: https://issues.apache.org/jira/browse/DIRSHARED-53
> Project: Directory Shared
> Issue Type: Bug
> Reporter: Jeff MAURY
> Fix For: 0.9.19
>
>
> DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSHARED-53) Review RequestID processing
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842651#action_12842651 ]
Stefan Seelmann commented on DIRSHARED-53:
------------------------------------------
Moved to shared, DSML parser is now part of shared.
> Review RequestID processing
> ---------------------------
>
> Key: DIRSHARED-53
> URL: https://issues.apache.org/jira/browse/DIRSHARED-53
> Project: Directory Shared
> Issue Type: Bug
> Reporter: Jeff MAURY
>
> DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSHARED-53) Review RequestID processing
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSHARED-53:
---------------------------------------
Fix Version/s: 1.0.0-RC1
(was: 0.9.20)
Postponed
> Review RequestID processing
> ---------------------------
>
> Key: DIRSHARED-53
> URL: https://issues.apache.org/jira/browse/DIRSHARED-53
> Project: Directory Shared
> Issue Type: Bug
> Reporter: Jeff MAURY
> Fix For: 1.0.0-RC1
>
>
> DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSTUDIO-500) Review RequestID processing
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seelmann updated DIRSTUDIO-500:
--------------------------------------
Fix Version/s: (was: 1.5.0)
postponed
> Review RequestID processing
> ---------------------------
>
> Key: DIRSTUDIO-500
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-500
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-dsml-parser
> Reporter: Jeff MAURY
>
> DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSHARED-53) Review RequestID processing
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSHARED-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSHARED-53:
---------------------------------------
Fix Version/s: 0.9.19
> Review RequestID processing
> ---------------------------
>
> Key: DIRSHARED-53
> URL: https://issues.apache.org/jira/browse/DIRSHARED-53
> Project: Directory Shared
> Issue Type: Bug
> Reporter: Jeff MAURY
> Fix For: 0.9.19
>
>
> DSMLRequestID are processed as LDAPMessageID so as non-null integers. The spec is not clear about it but it is declared as an XML string in the schema. However, the Abandon request id is also a string to how to correlate to LDAP message id, the spec does not describe clearly the scope of the request id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.