<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
> On your advice, I could describe what to do to get the<br>
> booking/"agnostic-like" app to build and run on WAS, but IMHO as an<br>
> end user discovering seam, it is much easier and faster to run a<br>
> script that builds the ear file ready-to-be deployed and then<br>
> inspect what's in the ear to mimic/adapt their own projects.<br>
<br>
</div>Yes, I personally prefer this approach.<br>
<br>
What do others think?<br></blockquote></div><br>While I think the instructions are important, because they emphasize the changes that have to be made, I wish there was a build that would automate the modifications so that we lower the barrier to getting hands on.<br>
<br>And yes, now that JBoss AS 5 is out, the jee5 app should be the first example any newcomer to Seam tries. Is there a place where we asterisk the default example? If so, we should asterisk the jee5 one.<br><br>I've added this statement to the examples/readme.txt file<br>
<br>"If you are just getting started with Seam, it's highly recommended that you<br>study the jee5/booking example first. This example is designed to run<br>unmodified on a Java EE 5-compliant application server. Of course, the real<br>
world is never so ideal. Therefore, you'll find modifications that you need to<br>make for various application servers in the example's readme.txt file. These<br>instructions can also be found in the Seam reference documentation."<br>
<br>-Dan<br><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br>