I added in seam.properties and that seemed to help. Now I'm getting an exception like this:
javax.naming.NameNotFoundException: RegisterDudeAction not bound
All I want to do is have a user click on a button, and then it makes an output in the log!
THANK YOU! As with everything else in JBoss world, the problem usually comes down to one line of XML somewhere.
Overall, my biggest problem with Java is the error messages are not helpful. Seam could have put a message in the exception saying, "check the JNDI pattern in components.xml" or something like that. Now that I see how that pattern is being used, it's obvious what needs to be there.
Again, thank you. Now I have Seam linked in to a simple web form, and I can probably solve things from here.
Submit a bug in JIRA - it's one of the big problems people seem to run into and would require one catch/throw of an exception AFAICS.
Ok, I'll do that.
As a developer, I would say that "Lame error reporting" is Java's worst problem. Instead of throwing "Cannot find class: java.util.StringBuilder", the JVM should say, "You need to upgrade to Java 1.5. Go to http://java.com to download it". That kind of thing. A stack trace is a very helpful debugging tool, but only to the person who thoroughly understands the code that generated the stack trace. Everyone else needs not just a stack trace, but an ERROR MESSAGE that gives some information about what the problem is and how to solve it.
Software used to give messages like, "This program failed due to Error 54839". Fortunately people have realized that those types of messages are worthless. I would submit that Java's exception mechanism is better, but developers should be strongly encouraged to provide meaningful, readable error messages in addition.
That's why we need feedback from users, to see where you are having problems and improve from that.
Thanks for the contribution !
(Recall: a contribution is not always "code contribution", feeback *is* contribution)
Note that the reason Seam does not blow up with an exception is that the jndiPattern is NOT required in all cases. You can use only JavaBean components. Or you can use @JndiName.
Still, a warning would not hurt.