common resources in jwc files

[RS...@agl.com.au]

is there any consideration going on regarding a way to include common jwc
resource artifacts in multiple jwc files without redundantly inserting them
into each file? for example, setting the same validation delegate class for
all components in an app without including a bean defintiion in each
component?

we could

1 - provide a tag to insert a jwc section from another file into an
existing jwc file, and keep common stuff in that file

2 - specify a tag or attribute in the copmponent schema indicating a
particular jwc file in some way extends a base, whereby it inherits its
parent's resources.

tapestry's great - i use it whenever i can, but this is just one thing i've
noticed that can become an annoyance when doing big apps.

i should acknowledge i may be missing something and/or have no general idea
what the hell i'm talking about. feel free to enlighten me...


**********************************************************************
This email is intended solely for the use of the addressee
and may contain information that is confidential or privileged.
If you receive this email in error please notify the sender and
delete the email immediately.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: common resources in jwc files

[Erik Hatcher <er...@ehatchersolutions.com>]

On Feb 21, 2005, at 8:13 PM, RSimic@agl.com.au wrote:
> is there any consideration going on regarding a way to include common 
> jwc
> resource artifacts in multiple jwc files without redundantly inserting 
> them
> into each file? for example, setting the same validation delegate 
> class for
> all components in an app without including a bean defintiion in each
> component?

You can already do this by making a base page class that provides a 
validation delegate.  Call it getValidationDelegate()  - no need to 
define a bean, simply use "ognl:validationDelegate" for the forms in 
the pages that are subclassed from your custom base page class.

> 1 - provide a tag to insert a jwc section from another file into an
> existing jwc file, and keep common stuff in that file

I suppose you could hack this with entity reference includes right now, 
but thats ugly.

> 2 - specify a tag or attribute in the copmponent schema indicating a
> particular jwc file in some way extends a base, whereby it inherits its
> parent's resources.
>
> tapestry's great - i use it whenever i can, but this is just one thing 
> i've
> noticed that can become an annoyance when doing big apps.

I agree..... it is not cleanly reusable and extensible like we'd all 
expect it to be when it comes to component and page specifications.

	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org