Since I seem to be having this conversation with myself, I thought I'd post the solution so I would know what I did wrong. When I used seamgen to generate the entities seam generate-entities It did not properly add the @GeneratedValue annotation to the entity class for the autoincrement field in the table. I'm not sure if this is a hibernate defect, seamgen defect or user error --but it sure was looking for a needle in a haystack.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093184#4093184
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093184
We currently have an early adopter program which includes several household names who have been using JBM in production for some time.
We also have many other non production support customer using JBM and many more again non paying customers using JBM in production.
Currently only developer assist support is available for JBM (apart from our early adopters), but JBM is scheduled to be the default JMS provider in the new JBoss Enterprise Application Platform 4.3, and the brand new JBoss Service Integration Platform which are both due out this December, at which point the highest level of production support will be generally available.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093180#4093180
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093180
so what is the "official" fix to the UnboundedFifoBuffer exception? I'm getting this as well after migrating the Seam booking app from 4.0.5.GA to 4.2.1.GA with Seam 1.2.1.GA. It happens when I'm entering data into the inputText fields in the register use case screen.
I read this entire thread and recall Pete Muir stating that we should use Seam 1.3 with Jboss 4.2 but as far as I know, Seam 1.3 is in alpha.
Our corporate direction it to use JBoss 4.2.1.GA, so what's the recommendation here??
also, how do I access the CVS trunk? is it the same as the following?:
http://snapshots.jboss.org/maven2/
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093173#4093173
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093173
Hi,
being a newbie to Seam and JSF I just built my first Seam webapp running in Tomcat 5.5 (Seam 1.2.1 GA + Facelets).
In order to see when exactly my components (all Pojos) get instantiated I put some debug output in the components' constructors. Now I noticed that Seam, every time it creates a component, apparently calls the constructor twice, first directly then via javassist.
I guess this is normal (because of the proxies?) but just wanted to be sure before putting expensive operations in the constructors...
Thanks for information!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093171#4093171
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093171