Excellent - I'll take a look ASAP.
One thing I don't get is why booking-ds.xml needs to be deployed
independently; we don't do that for the "normal" WTP projects ?
/max
I have created mavenized Seam Booking example. The project is based
on
the project created by Fred Bricon
(
http://jira.codehaus.org/browse/MNGECLIPSE-688). It is compatible
with JBoss Tools and includes
content assist, Seam validator, etc. All libraries are mavenized
(booking/WebContent/WEB-INF/lib is empty; there isn't any library in
booking-ear; sources are available if they exist in Maven
repositories...).
The size of the mavenized EAR booking archive is about 200K, the size
of non-mavenized EAR booking archive is about 8MB.
In order to test the project, you need to do the following:
- call Help>Project Examples>Seam>Seam Booking example - EAR mavenized
You will get booking, booking-ejb, booking-ear and booking-parent
projects
- add some JBoss Server, JBoss Seam Runtime and database connection
profile
- make resources/booking-ds.xml deployable
- wait until "Maven indexer" and "Maven update dependencies" are
finished
If you deploy the project before maven updates its classpath, it
could happen some libraries not to be deployed
(booking.war/WEB-INF/lib, for instance). If this happens, you need to
close the booking project and open it again (or restart Eclipse).
- deploy booking-ear
- start the server
I have used Eclipse 3.4.1, WTP 3.0.3, JBoss Tools 3.0.0 nigthly,
m2eclipse 0.9.7.200811301806, Seam 2.0.2 SP1, JBoss AS 4.2.3
It is much easier to mavenize a Seam WAR project.
Snjeza