You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Byrne, Steven" <SB...@dorado.com> on 2003/10/29 23:04:23 UTC
Component inheritance/specialization
Can anyone enlighten me as to how to go about allowing component
specialization/customization in Tapestry?
The basic use case that I'm thinking about is one in which team A
produces a set of reusable components, including HTML template
components. Team B uses those components to build and customize a user
interface. Team B wants to be able to alter some or all of the HTML
templates in Team A's components, but without having to actually modify
(rejar) the components produced by Team A. Think of Team B wanting to
"subclass" some or all of components that Team A produces, but not just
the Java portions of the components.
Is there a way to accomplish this in Tapestry? Is there some idiom of
using overidable blocks that the Team A component templates that would
supply the required functionality?
TIA!
Steve
Re: Component inheritance/specialization
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
HTML templates (and I'm guessing .jwc files also) can be overridden by
simply putting them in the same package where the original templates
live, except under WEB-INF/classes. I'm assuming Team A here is
providing a JAR of components that lives in WEB-INF/lib.
I'm doing this quite successfully with the contrib:Table HTML templates.
Erik
On Wednesday, October 29, 2003, at 05:04 PM, Byrne, Steven wrote:
> Can anyone enlighten me as to how to go about allowing component
> specialization/customization in Tapestry?
>
> The basic use case that I'm thinking about is one in which team A
> produces a set of reusable components, including HTML template
> components. Team B uses those components to build and customize a
> user interface. Team B wants to be able to alter some or all of the
> HTML templates in Team A's components, but without having to actually
> modify (rejar) the components produced by Team A. Think of Team B
> wanting to "subclass" some or all of components that Team A produces,
> but not just the Java portions of the components.
>
> Is there a way to accomplish this in Tapestry? Is there some idiom of
> using overidable blocks that the Team A component templates that would
> supply the required functionality?
>
> TIA!
> Steve
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org