> On your advice, I could describe what to do to get the
> booking/"agnostic-like" app to build and run on WAS, but IMHO as an
> end user discovering seam, it is much easier and faster to run a
> script that builds the ear file ready-to-be deployed and then
> inspect what's in the ear to mimic/adapt their own projects.

Yes, I personally prefer this approach.

What do others think?

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.

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.

I've added this statement to the examples/readme.txt file

"If you are just getting started with Seam, it's highly recommended that you
study the jee5/booking example first. This example is designed to run
unmodified on a Java EE 5-compliant application server. Of course, the real
world is never so ideal. Therefore, you'll find modifications that you need to
make for various application servers in the example's readme.txt file. These
instructions can also be found in the Seam reference documentation."

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan