> Is it possible to use Tapestry's parser in tests to verify that template
> syntax is correct?

Certainly not Tapestry's; it's a different syntax :)

> I'd like to run tests (like you do when doing a JSP pre-compile) to verify
> syntax w/o having to start the app and find out at runtime.

I think your best bet is just to write test cases. I can imagine a
tool that simply checks only the syntax of tempatles without
validating them against the runtime component hiearchy. You can open a
feature request if you want.

> Also, is it possible to adjust Wicket's template caching strategy? In other
> words, is it possible to make it like JSP where there's a timestamp check to
> see if a page has been updated?
>
> I realize I can turn off page caching, but does that make Wicket slower than
> a JSP-based solution? Can I provide my own implementation (or configure the
> existing one) to check every 2 minutes?

In fact, it works the other way around. Caching is the default, but in
development mode (not recommended for deployments) every markupfile is
registered with a modification watcher, which by default works by
polling whether files are changed (in which case it will trigger
loading the new markup). The logic for this is in MarkupCache, which
implements IMarkupCache, for which you can supply a custom
implementation if you want (getMarkupSettings#setMarkupCache). This
would be a last resort though, as typically the defaults should work
fine.

Eelco

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to