You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2005/09/14 20:28:57 UTC
[jira] Resolved: (DIRLDAP-53) "LDAP ACIItem" Parser Implementation
[ http://issues.apache.org/jira/browse/DIRLDAP-53?page=all ]
Alex Karasulu resolved DIRLDAP-53:
----------------------------------
Fix Version: 0.9.3
Resolution: Fixed
Committed patch on revision 280902 here:
http://svn.apache.org/viewcvs.cgi?view=rev&rev=280902
> "LDAP ACIItem" Parser Implementation
> ------------------------------------
>
> Key: DIRLDAP-53
> URL: http://issues.apache.org/jira/browse/DIRLDAP-53
> Project: Directory LDAP
> Type: New Feature
> Components: Common
> Versions: 0.9.3
> Reporter: Ersin Er
> Priority: Minor
> Fix For: 0.9.3
> Attachments: ACIItemParser_01.patch
>
> An implementation of ACIItem, ported from X.501 to LDAP, parser is provided as a patch attached with this issue.
> The implementation includes:
> - an almost complete "LDAP ACIItem" Antlr grammar
> - a wrapper around the Antlr generated classes
> - two auxilary classes for parser/lexer pair reusability
> - a test class
> - and a maven configuration update
> TODO:
> - Good test coverage
> - Model integration via actions
> - Cleanup
> ACI is a tough subject and this parser is no exception. This is somewhat a big grammar that needs extensive testing which is missing now. The current grammar does not integrate with ACIItem API implemented by Trustin, because we need to discuss some issues about porting X.501 ACIItem to LDAP and about string representation of some components. After we agree on a robust spec, I'll update the grammar to fully comply with "our ACIItem spec" (Trustin may also need to update his stuff). One more step will be integrating with ACIItem API which will be a one hour task with Trustin's super clear implementation (thanks Trustin!).
> I'll further discuss the issue on the mailing list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira