Link Details

i like the required param, i hope i try it one day(i dont do web that i dont need)

Wow, really! I think I have now seen every type of annotation there is, oh wait, no i haven't, there is now @IncludeStylesheet( "context:css/myapp.css" ) . I think any framework that needs this kind of hard coding should be shot. I am sure this is just an option, but come on now, stop adding soooo much mind-less sugar and put in more substance. I think after all these frameworks go away, the only one standing will be the fastest, simplistic and the one with the most bang-for-the buck features. Sort of like MemCache for caching, less bloat, more robustness.

you do have a good point

killerweb: The @IncludeStylesheet annotation is just an optional convenience; it is also useful when building components with stylesheets when the stylesheet is packaged inside the JAR (Tapestry builds a safe URL that pulls the asset content from the file stored on the classpath). There's also an important aspect related to localization -- Tapestry will choose the correct localization of the stylesheet based on the user's locale.

Regardless, its also optional; you can completely include stylesheets in your page or component templates using the > element (I just always forget the attributes on it).

Tapestry isn't going away, just the opposite. And it is designed to be the fastest, the easiest, the most concise, and the one with the most bang-for-the-buck features.