Re: Project activity

Onno Scheffers <[email protected]> Fri, 19 Aug 2005 19:38:36 +0200
Newsgroups gmane.comp.java.enhydra.barracuda.general
Message-ID <[email protected]>
This is a multi-part message in MIME format...

------------=_1124473133-15681-170
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Massimo Lusetti wrote:

>>Wicket is going to be very powerful, but is not yet as mature as either
>>Barracuda or Tapestry. But it is fast becoming one of the most popular
>>web based frameworks. I think it is really a framework to keep an eye on
>>for the future. It takes a lot of ideas from Tapestry, but tries to keep
>>it all simpler and does much more in code (where Tapestry requires lots
>>of XML configuration files).
>>    
>>
>
>You can get rid of XML with annotations.
>  
>
Not really (last tried in T4Beta2)... only if you place all HTML-files 
into the context-root. That means you make your templates/prototype 
publicly accessible, while they shouldn't be in my opinion.
I'd like to place them into the WEB-INF folder. Tapestry doesn't pick 
them up then unless you have the a .page file available there.

>The "special attribute" could also be (is configurable) the "id"
>attribute which is and attribute of any object. So if you would like
>to have it you can still have it.
>  
>
Yes, you can make that attribute anything you'd like. But no matter what 
you name it, that ID will be removed while rendering the components. 
That means if you set the 'special attribute' to 'id', the id's will be 
stripped from the output. That could render your DHTML useless (since 
client side scripts may depend on those ID's as well).

Regards,

Onno



------------=_1124473133-15681-170
Content-Type: text/plain; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: 8bit



--

Barracuda mailing list

[email protected]

http://www.objectweb.org/wws/lists/projects/barracuda


------------=_1124473133-15681-170--