Re: Eclipse User Libraries and Tapestry 4.0.2
Look at http://www.eclipseplugincentral.com/Web_Links-index-req- viewlink-cid-865.html LibCopy plugin is doing this job for Maven project. I guess you can have a look at the way it is working and just do the same in your project. Regards, SP On May 15, 2007, at 4:33 PM, #Cyrille37# wrote: #Cyrille37# a écrit : Hello, For every Tapestry project I've to copy all Tapestry libraries in the WEB-INF/lib folder. Like I'm using Windows I could not using symbolic links. By that way, each project are heavy. I'd tried to define Tapestry as a Eclipse User Library but jars are not deployed at runtime so the tapestry apache redirect filter is not found. Do you know a way to avoid this heavy copying ?? I've read the HowToSetupEclipseWtp but the author has the same problem. Regards cyrille I forget to specify that I've added the Tapestry Eclipse User Libray in the BuildPath AND in the classpath of the Server Launch configuration for Tomcat5.5 cyrille - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Change in T5 (localization)
Hi Howard, I do really appreciate T5. It's quite impressive right now and expect it to be the definitive framework when completed. for now I have a remark. Page http://tapestry.apache.org/tapestry5/ tapestry-core/guide/localization.html includes a strange translation of "Welcome Back" : Or, perhaps, a French version: page-title=Votre Compte greeting=Bienvenue en arriere I would translate Welcome Back: "Bienvenue de nouveau". Regards, SP
Re: session persistance?
Yes, from what I understand persist is just to keep value between
request. so every-time you request the page the object is in this
case recreated.
If you want to keep this object across a session you need ASO (see T5
doc on persistence).
You can also (but will not be kept a session level) perform a test in
your class to instantiate only once the object and keep it for the
page or request only.
SP
On Apr 9, 2007, at 3:34 AM, Patrick Moore wrote:
Hi there --
does anyone have some thoughts on why:
@Persist
@InitialValue("new java.util.HashSet()")
public abstract Set getFollowUpMessages();
public abstract void setFollowUpMessages(Set set);
keeps on resetting the set to a new HashSet between http requests?
It looks like according to the @Persist documentation this is the
correct
way to set an initial value if there is no value already in the
session. But
it seems not to be the case...
-Pat
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Best page templating strategy
Just one question, why don't you use a CSS layout + ASSET in stead
of component (this does not apply to the sidebar).
Rgds,
SP
On Apr 10, 2007, at 8:28 AM, Yann Ramin wrote:
I'm using T5 to do some experimental testing, creating some mockup
applications to teach me more about the framework.
My question is, how do you best handle multi-part layouts?
For instance, a Layout can be composed of a Body and a Sidebar. The
Sidebar can be a component.
My current approach is to have a
Page.java:
public Page {
@Component
private Layout _layout;
@Component
private Sidebar _sidebar;
}
Page.html:
fee fi fo fum
This feels suboptimal, as I'm encoding the location of the sidebar
into each and every page (namely always coming after the main div).
I'd like to have the Sidebar component in the Layout component, but
feed this component from the Page to the Layout (as the Sidebar
component could be different on every page). I.e., sidebar="sidebar">, but that is a parameter, not a component, so
afaik won't work like I expect it to (it didn't in testing, but
could have been anything).
Any way of accomplishing this? Any better solutions to this
problem? Am I missing something?
BTW, T5 is a great framework - having lots of fun with it!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
