Did you add the name annotation to your person class ?

@Name(“person”)
class Person implements Serializable{
…
}

But when I ran the helloworld which I downloaded, it ran perfectly. This is driving me nuts and I even compare the ear file from the downloaded example and my generated ear file and I can’t seem to find a difference. Please help me. Hopefully, I could email the ear file that I am generating as well as the ear file from the downloaded example helloworld.

Update it to

[...]

to get it working with JBoss 5.

With that said, let me respond to your comments:

1) We are not saying the Spring is hell. XML hell is a commonly used phrase that describes the issues with extensive XML configuration. Spring 2.X has improved greatly in this respect, but Seam has used convention over configuration and annotations from the beginning which greatly reduces the amount of XML required.

2) Sure, the responsibility can lie on the developer, but why not make life easy? With an SMPC lazy initialization works like it should, we can edit managed entities throughout the web transaction, and simply flush the results when the web transaction successfully completes.

3) Okay, so we shouldn’t discuss conversations then? Conversations are core to Seam and must be understood to understand how Seam works. Yes, SWF has similar concepts, but that doesn’t mean we should leave these concepts out of the book

We only mention Spring twice in the book to demonstrate an issue that Seam solves through a well-known example. We also do this with other frameworks as well, including EJB and JSF which Seam was originally built to integrate!

shame..

However, the authors have something against Spring.

Dear authors, you should not agressively critisize other framework.

1- You tried to tell us that Spring is a “Hell” because of use of XML => What about seam ? Spring doesn’t encourage the developers to put everything in XML files. So it’s of the responsability of the developer to choose what to put in.

2- Lazy initialization Problem => this is not a Spring problem at all => It’s the developer who should ensure what and when to load data from db => loo, at harnessing hibernate book.

3- Conversation (and other new scopes) => in the Spring webflow there already are something like these.

I think you should have concentrate on seam features instead of barking at Spring.
Look, the spring developers never told that it’s the ‘best’ or whatever. They just created something that they think useful. Even Gavin King worked with this framework. Actually, he firstly created seam to manage workspaces in a JSF/Spring application.