[ http://issues.apache.org/jira/browse/TAPESTRY-1182?page=all ]

Jesse Kuhnert resolved TAPESTRY-1182.
-------------------------------------

    Resolution: Fixed

Oops...Didn't notice an svn conflict rejection on that one. 

> make ComponentAnnotationWorker extensible
> -----------------------------------------
>
>                 Key: TAPESTRY-1182
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1182
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Annotations
>    Affects Versions: 4.1.1
>            Reporter: Norbert Sándor
>         Assigned To: Jesse Kuhnert
>             Fix For: 4.1.2
>
>         Attachments: patch.txt
>
>
> I'm working on an implementation of global namespaces for Tapestry 4.1. It 
> would solve some of the problems with libraries and namespaces. The 
> implementation is almost done (but there are no docs yet... :( ).
> To make my library more easier to use, I'd like to extend 
> ComponentAnnotationWorker to be able to automatically lookup components in 
> the global namespace.
> For this to work, the following changes are required:
> - ComponentAnnotationWorker should be a hivemind service to be overridable
> - the automatic component type resolution algorithm should go to a separate 
> method to make it easier to reuse the class as a superclass
> I will release the library only if this change is applied to the annotation 
> codebase, because it is a requirement for one of the most important functions 
> of the library.
> It would be great if this change could be part of the final 4.1.1!
> Thanks for your help!
> Regards,
> Norbi

-- 
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



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to