or the blog tutorial, it uses jpa but could be a prettier example...

http://cwiki.apache.org/confluence/display/WICKET/Blog+Tutorial

Martijn Dashorst wrote:
Take a look at the wicket-phonebook from wicketstuff.org for inspiration.

Martijn

On 2/19/08, Bert Radke <[EMAIL PROTECTED]> wrote:
Hi all,

i 'm evaluating wicket right now with a small project using JPA
(Hibernate) as datalayer.
Together with the "Wicket in Action" (great book so far, thanks), i
could implement
most of the wished features (templating, custom components, ..) but i
'm kind of stuck
with the proper layering of the application.

So far, for test purposes, i have some hard wiring in place that i
want to get ride of.

Most of the application consists of search-forms together with (large) tabular
(read-only) datadisplay.

Right now, i have some (domain/JPA) model classes, DAO's to access them and use
Wicket-Spring to inject the DAO's in the web - part. So i use the JPA POJOs in
Wicket to display the data.

I think of introducing an additional level, 'Wicket-Model' to wrap the
domain-models
into LoadableDetachableModel's. How should they interact with the DAO's? Should
the Wicket-models directly work with the DAO or should i retrieve the
domain - model
outside (Page / Component) and feed the domain-model object into the
wicket-model?

How to archive this best for lists of domain-models (ListView)?

Hacking something together would not be a problem, but i would like to
learn how to
proper layer / separate this in a webapp (current framework i 'm
(forced to) used does
mix it all :( ).

Thanks in advance for taking the time to read this,
Bert

PS: apart from Wicket-Spring i 'm not using any extensions right now,
as this is more of
a learning thing right now.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to