Controls
Built with Seam
You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Comparing current revision with historical revision 0. |
From line 9 changed to line 9:
The developers also generously converted several of the source code stages/chapters from Seam in Action to Maven 2 projects as well.
The developers also generously converted several of the source code stages/chapters from [Seam in Action=>http://mojavelinux.com/seainaction] to Maven 2 projects as well.
From line 13 changed to line 13:
The Know IT Objectnet developers fellow Seam and Maven 2 fans to this project. Whether you want to use this template to develop your own projects, or you want to contribute to the project, they invite you to check out the code.
The Know IT Objectnet developers welcome fellow Seam and Maven 2 fans to this project. Whether you want to use this template to develop your own projects, or you want to contribute to the project, they invite you to check out the code.
From line 17 added to lines 17 to 18:
We appreciate the many other efforts lead by community members to assemble a Seam project based on a Maven 2 build, which are listed here.
From line 22 added to line 24:
= [seam-ear-archetype=>http://code.google.com/p/open-archetypes/] - (open-archetypes project)
From line 23 added to lines 26 to 37:
++ SeamTest and Maven
Using SeamTest with Maven can be a challenge because the Embedded JBoss container on which SeamTest relies is not very "classpath" friendly. It brings its own solar system of JAR files with it and those can easily conflict with the classpath built by Maven. Please see the following thread on how best to integrate the two:
[TestNG and Maven - How To Configure It Correctly=>http://sfwk.org/Community/TestNGMavenHowToConfigureItCorrectly]
Play close attention to the responses Dan gives.
++ The future
Be sure to follow the developments in Seam 3, which will include an official Maven 2 archetype for Seam applications. We welcome your feedback and expertise as we "standardize" the structure of this project.
