Kent,
1 - In my opinion, by far the best way to get started (as you intend to go
on) is described http://wicket.apache.org/quickstart.html here . Once you
have spent 37 seconds (roughly) mastering as much Maven as you'll need for
this purpose, this technique will see you good through most of your upcoming
Wicket projects and help you communicate/exchange stuff more easily with a
lot of other, very helpful Wicket developers.
2 - Do you feel the structure you suggest is an improvement? Where will you
put test resources?
3 - There are several ways to do this - depends on the architecture you
decide on. You can get some ideas
http://cwiki.apache.org/WICKET/wicket-phonebook.html here .
You could inject your DAO instances into the service layer using raw Spring
IoC and inject service objects into your pages (or other Components) using
Wicket's @SpringBean. See the 3 tier service architecture described in your
copy of WiA. You can also read more
http://cwiki.apache.org/WICKET/spring.html here .
If you have more specific questions (eg on how to use @SpringBean with non
Wicket-Components ... etc), it's all quite easy once you know how as the
core developers have made a good job of this - you'll get used to that
feeling with Wicket - you'll get a lot of good help here as many people use
Wicket with Spring and ORM (JPA and/or Hibernate ...).
Regards - Cemal
http://www.jweekend.co.uk jWeekend
Kent Larsson-3 wrote:
I've bought and read most of Wicket in Action (WIA), great book! I'm
exited
to use Wicket but I have some start up questions I feel I need to ask
someone more experienced about.
The project will use Wicket + Spring + Hibernate which I suspect is a
fairly
common combination.
In the bonus chapter on how to setup an environment in WIA it mentions
three
ways to get a quick start: Wicket's quick-start project generator (Wicket
only), QWicket (sets up Wicket + Spring) and AppFuse Light (sets up Wicket
+
Spring + a number of ORM frameworks. Or alternativly I could set it up
myself by hand. I don't want to use Maven 2 as I feel that I have reach my
limit on new technologies for one project (I'm previously familiar with
EJB
3.0, JPA, Servlet + JSP and Ant) and it seems like it requires some time
to
get used to.
http://wicket.apache.org/quickstart.html suggests this project structure:
.\myproject
| pom.xml
|
\---src
+---main
| +---java
| | \---com
| | \---mycompany
| | HomePage.html
| | HomePage.java
| | WicketApplication.java
| |
| +---resources
| | log4j.properties
| |
| \---webapp
| \---WEB-INF
| web.xml
|
\---test
\---java
\---com
\---mycompany
Start.java
I understand that parallell normal source and test source directory
structures is a good thing. However, do you see an advantage in having
/src/main/(java|resources|webapp)/* and /src/test/* ? Why not just have
/src/* , /resources/* , /webapp/* and /test/* and flatten the hierarchy a
bit? What do you use that indirection for?
My last question is how do you integration Spring and Wicket? As there are
several ways I'm in search of some previous experience from people who
have
used these two frameworks together.
To sum up my mail in three questions:
1. Do you recommend that I use some kind of quick start method? And if so,
which one?
2. Why have main and test under the project root, and not src (alias main)
,
resources, webapp and test? (It's only four directories.)
3. How do you recommend that I integrate Spring and Wicket?
MANY thanks for reading!
Best regards,
Kent Larsson
--
View this message in context:
http://www.nabble.com/Beginners-questions%3A-How-integrate-Spring%2BWicket--Quickstart--Why-is-that-directory-hierarchy-recommended--tp21058097p21059761.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
