Yes, that's correct. I made a mistake and the bean was intended to be stateful. I was surprised that Seam didn't pick up on this as it seems to notice other incorrect annotations and halts deployment.
Perhaps I am expecting too much of frameworks: should annotation based frameworks validate annotation usage? how should they react to any silly usages? is such validation expensive? I think my bad use of the @Scope annotation was an easily made mistake. I would rather the application was not deployed than deployed like this. Another mistake I made previously was to give two components the same name (@Name) in the same scope. This also led to strange behaviour. Again, is this something Seam should pick up on? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934435#3934435 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934435 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
