we are on the way to migrate our old struts web app to something more
modern.
our first try was seam/jsf, but the performance of jsf was very
disappointing.
so now our plan is to use seam (as we like its component model and the
performance was quite good - after using @BypassInterceptors....) with
wicket;
on the one hand we are very impressed by wicket's java-centric approach, on
the other hand we have a lack of understanding of how to achieve some basic
things with wicket, as our experience comes from jsp and jsf.
there are some problems that we didnt find an elegant solution for with
wicket, perhaps somebody can help us to understand the wicket way...
1) working with many attributes of an object
we have some pages where we access many attributes of an object, say we want
to show all 20 attributes of a person and all 10 attributes of
person.getAddress();
in the PersonPage.java i would have to add 30 label (or input) components,
30 lines with nearly identical java code: add(new Label("firstName",
person.getName() );
isn't it tedious to always keep PersonDetails.java and PersonDetails.html
files in sync? in jsf/jsp the changes are only in the jsp/xhtml
2) page composition
in tiles and facelet compositions the layout is separated in templates
(with navigation, sidebars, header, footers, ...) that decorate the concrete
pages (eg the personDetails page); its possible that the concrete page
(personDetail.xhtml) defines some content of the decoration, e.g. that the
window title of the template should be replaced with: "<title>Details of ${
person.name}</title>";
in the template i would write <title><tiles:insert
name="windowTitle"/></title> with tiles or <ui:insert name="windowTitle"/>
in facelets;
the content for windowTitle is defined in personDetails.xhtml or in the
tiles definition for the personDetails.jsp
3) preview functionality
is this right: as soon as we use page composition and components, the
preview feature is gone; how do you experienced wicket users handle this? is
it usable in a prototype phase - before the html prototype is decomposed
into composition parts and components?
is there a resource on the web that helps with the task of migrating from
jsf to wicket?
the only one i know is the seam-booking example with the two versions; a
migration guide could be a motivation for jsf users to try out wicket (and
find out thats it better... :-) .
thanx in advance, uwe!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
