precompile Tapestry files

[ma...@yahoo.de]

Hi @all,

I'm just reading the book "Tapestry in Action".
I really like the concepts of Tapestry and I like to think to get rid of the JSPs ;-)

And I like the idea to configure my pages and components in order to reduce the amount of code.

But I'm missing something: Can I also precompile the Tapestry files (Templates, Pages, ...) like JSP files ?
I mean you can put a lot of OGNL-code or refer to JAVA-methods in the templates, so there should be way to check for errors before
deploying an application and testing at runtime.

Thanks & Regards
Martin



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

Re: precompile Tapestry files

[Jamie <ja...@dang.com>]

Tapestry pages aren't compiled, as they don't use JSPs. However, there 
is a lot of run-time injection. To aid in performance, Tapestry uses 
pooling. The first time a page is rendered, it's a lot slower than 
subsequent requests.

I haven't explored if there's a way to initialize a pool at startup.

Erik? Howard? ...?

maddinontheworks@yahoo.de wrote:

>Hi @all,
>
>I'm just reading the book "Tapestry in Action".
>I really like the concepts of Tapestry and I like to think to get rid of the JSPs ;-)
>
>And I like the idea to configure my pages and components in order to reduce the amount of code.
>
>But I'm missing something: Can I also precompile the Tapestry files (Templates, Pages, ...) like JSP files ?
>I mean you can put a lot of OGNL-code or refer to JAVA-methods in the templates, so there should be way to check for errors before
>deploying an application and testing at runtime.
>
>Thanks & Regards
>Martin
>
>
>
>---------------------------------------------------------------------
>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

Re: Creating checkboxes for multiple select items.

[Paul Ferraro <pm...@columbia.edu>]

Have you looked at the contrib:MultiplePropertySelection component?  It 
does exactly this.

Paul

Random Tapestry User wrote:

> Hi all,
>
> Not sure if I'm missing something here. I've read the book, and I know 
> this must be something simple I have overlooked.
>
> I have a survey that the user needs to fill out.
>
> The survey object, has question objects. Each question object has a 
> number of choices, either single-select or multiple select.
>
> I have created a @ListEdit component that iterates the questions just 
> fine, but I'm struggling a bit with constructing the choices for the 
> user.
>
> The questions have basically 2 cases, multiple select, and single select.
>
> I'm going to implement the single select with a @RadioGroup.
>
> I WANT to implement the multiple select with checkboxes, instead of a 
> multi-select input field.
>
> Is there a standard solution for this, using checkboxes for a multiple 
> select ?
>
> Thanks in advance,
> tappapp
>
> ---------------------------------------------------------------------
> 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

Creating checkboxes for multiple select items.

[Random Tapestry User <ta...@comcast.net>]

Hi all,

Not sure if I'm missing something here. I've read the book, and I know 
this must be something simple I have overlooked.

I have a survey that the user needs to fill out.

The survey object, has question objects. Each question object has a 
number of choices, either single-select or multiple select.

I have created a @ListEdit component that iterates the questions just 
fine, but I'm struggling a bit with constructing the choices for the user.

The questions have basically 2 cases, multiple select, and single select.

I'm going to implement the single select with a @RadioGroup.

I WANT to implement the multiple select with checkboxes, instead of a 
multi-select input field.

Is there a standard solution for this, using checkboxes for a multiple 
select ?

Thanks in advance,
tappapp

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

Re: precompile Tapestry files

[Nathan Kopp <nk...@mailshell.com>]

> Hi @all,
>
> I'm just reading the book "Tapestry in Action".
> I really like the concepts of Tapestry and I like to think to get rid of
the JSPs ;-)
>
> And I like the idea to configure my pages and components in order to
reduce the amount of code.
>
> But I'm missing something: Can I also precompile the Tapestry files
(Templates, Pages, ...) like JSP files ?
> I mean you can put a lot of OGNL-code or refer to JAVA-methods in the
templates, so there should be way to check for errors before
> deploying an application and testing at runtime.
>
> Thanks & Regards
> Martin

If I understand correctly, you're asking for compile-time error reporting.
The Spindle plug-in for Eclipse does some of this, but it doesn't seem to
issue errors (or even warnings) for ognl expressions.  There are some good
reasons for this, since Tapestry uses runtime bytecode modification to
dynamically sublcass/alter your classes.  Still, it would certainly be nice
if we could check our ognl expressions at compile time.

-Nathan


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