Hmm, I don’t think I can agree with that.  SiteMesh, AFAIK, can aggregate from whole host of markup sources to produce a “finished product”.  I don’t see how that can be accomplished in the example you presented or with Wicket in general, not with out a lot of work that is. 

 

This is the main reason I stopped trying to use Wicket to produce portal layouts.  It is more effort than it is worth to try and get a single component/page merge arbitrary markup.  The whole “one markup source per component” tends to break down very quickly in this type of setting and is, IMOHO, a short-coming of most of component-based web frameworks that are popping up.  That last thing I want to do is require my layout and decoration designers to create new component classes for each layout they come up with.

 

Don’t get me wrong; Wicket is wonderful for straight-forward application development.  However I feel it lacks the flexibility to work well as a generalized, light-weight layout engine.  Not everything is a nail ya’ know ;-)

 

If any of the Wicket gurus out there feel I have misspoken, please let me know as I would still love to replace Jetspeed 2’s existing layout/decoration mechanism with Wicket. 

 

Regards,

Scott T. Weaver

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Berman
Sent: Wednesday, October 26, 2005 3:57 PM
To: [email protected]
Subject: Re: [Wicket-user] SiteMesh and Wicket are compatible?

 

There is no need to use SiteMesh if you are using Wicket.  Wicket has mechanisms which accomplish the same thing but even better.  Take a look at Borders, Panels, and markup inheritance (http://www.wicket-wiki.org.uk/wiki/index.php/Markup_inheritance)

--Andrew

On 10/26/05, Jeff Miller <[EMAIL PROTECTED]> wrote:

Has anyone attempted to use SiteMesh (http://www.opensymphony.com/sitemesh/) with Wicket?  If yes, are there any issues or limitations?

 

Thanks,

Jeff



Jeff Miller
[EMAIL PROTECTED]


Yahoo! FareChase - Search multiple travel sites in one click.

 

Reply via email to