RE: ContextAttributeSelector
Jörg, thanks for your reply. I think I kind of missed that thread. I will have a look into that and possibly convert it to an input module. Regards, Jeroen Reijn -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Posted At: Thursday, December 21, 2006 1:13 AM Posted To: Cocoon Dev List Conversation: ContextAttributeSelector Subject: Re: ContextAttributeSelector Isn't their a thread on the users list about creating generic components using input and output modules for such tasks? Wouldn't be your to-be-donated component one of the first to be deprecated? So what about contributing an InputModuleSelector and a ContextAttributeInputModule ;) Regards Jörg On 20.12.2006 14:32, Jeroen Reijn wrote: Hi all, for one of our project I needed to create selector that could read attributes from the current context (ContextAttributeSelector). I would like to donate the selector. Is there any interest in such a selector or should I just provide the patch in JIRA? Kind regards, Jeroen Reijn
RE: ContextAttributeSelector
Mark, the improved sitemap looks very interesting. I guess that the ServletContext.. is a better name for the component. I've modified some code so it would still fit into cocoon without getting deprecated ;-) I'll test it some more and send in the InputModule tonight. Kind regards, Jeroen Reijn -Original Message- From: Mark Lundquist [mailto:[EMAIL PROTECTED] Posted At: Thursday, December 21, 2006 5:21 AM Posted To: Cocoon Dev List Conversation: ContextAttributeSelector Subject: Re: ContextAttributeSelector On Dec 20, 2006, at 4:13 PM, Joerg Heinicke wrote: Isn't their a thread on the users list about creating generic components using input and output modules for such tasks? Wouldn't be your to-be-donated component one of the first to be deprecated? If I get my way [1], all matchers and selectors as we know them now will be deprecated :-). I hope to contribute that code fairly soon. So what about contributing an InputModuleSelector and a ContextAttributeInputModule ;) We have today an input module selector, it's called SimpleSelector (hopefully, soon also to be deprecated! :-). But a ContextAttributeInputModule would certainly be appreciated. (Would ServletContextInputModule be a better name?) —ml— [1] http://marc.theaimsgroup.com/?t=11651813411r=1w=2
Re: ContextAttributeSelector
Isn't their a thread on the users list about creating generic components using input and output modules for such tasks? Wouldn't be your to-be-donated component one of the first to be deprecated? So what about contributing an InputModuleSelector and a ContextAttributeInputModule ;) Regards Jörg On 20.12.2006 14:32, Jeroen Reijn wrote: Hi all, for one of our project I needed to create selector that could read attributes from the current context (ContextAttributeSelector). I would like to donate the selector. Is there any interest in such a selector or should I just provide the patch in JIRA? Kind regards, Jeroen Reijn
Re: ContextAttributeSelector
On Dec 20, 2006, at 4:13 PM, Joerg Heinicke wrote: Isn't their a thread on the users list about creating generic components using input and output modules for such tasks? Wouldn't be your to-be-donated component one of the first to be deprecated? If I get my way [1], all matchers and selectors as we know them now will be deprecated :-). I hope to contribute that code fairly soon. So what about contributing an InputModuleSelector and a ContextAttributeInputModule ;) We have today an input module selector, it's called SimpleSelector (hopefully, soon also to be deprecated! :-). But a ContextAttributeInputModule would certainly be appreciated. (Would ServletContextInputModule be a better name?) —ml— [1] http://marc.theaimsgroup.com/?t=11651813411r=1w=2
