tapestry-user@jakarta.apache.org
[Top] [All Lists]

Re: Injecting common properties for multiple pages

Subject: Re: Injecting common properties for multiple pages
From: "Mike Snare"
Date: Mon, 10 Apr 2006 14:54:15 -0400
There would certainly need to be some filtering.

As to the issue of objects in pages, it's really a matter of logic in
pages, since the objects aren't really stored in the pages anyway. 
Shouldn't be an issue.

There are many issues that would need to be addressed, but it should be do-able.

On 4/10/06, Mark <lists@xxxxxxxxxxxxxxx> wrote:
> Mike,
>
> Not sure if it would have to be done in a way that you can specify which
> pages to inject stuff into. Maybe based on the Page interface-/
> implementation classname.
> Otherwise you end up with all kinds of objects in page classes that do
> not want them. Although, I am not sure if this would be pose a problem
> or not.
> It would if you for example hat 2 different page classes that the
> project is split into, and they have the same property name with the
> same interface, but require different implementations. Does that make sense?
>
> MARK

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-user-help@xxxxxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>