Hi,
I have a question of understanding:
I have written a validator, which is working pretty fine,... well actually it should.
The validator gets called twice.
If I create a new Object of an entity with an autogenerated ID and persist it,
the validator gets called before this entity has an ID and returns TRUE, so no validation error.
But then the thing:
After the entity got his ID it gets validated again and then (caused by some validation rules i have written) the validator returns false and there is no message thrown to the JSF, instead i get a regular "Transaction failed".
Any ideas why the validator is called twice and how to avoid this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102998#4102998
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102998
Have you taken a look at the jee example - that runs under Glassfish (as do the hibernate and jpa examples, and the other examples can of course be made to run under glassfish). I don't believe we currently have an example for geronimo.
We are currently working on documenting running Seam apps on other app servers (e.g. Seam 2 docs have a section for OC4J, more to come like that) and are in the process of setting up a QA lab/staff to test Seam on app servers other than JBoss AS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102996#4102996
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102996
"gavin.king(a)jboss.com" wrote : Are people actually using Seam's integration testing stuff? I've seen very few questions about this, which allows various possible explanations:
|
| (1) Everyone is using it and it Just Works
| (2) No-one understands it or no-one knows it exists
| (3) No-one does integration testing
| (4) There is some fundamental limitation which means people can't use it on their projects (eg. they are required to use JUnit instead of TestNG)
|
| Any feedback on this would be very useful.
|
| Thanks
(4) Seam's integration testing stuff has fundamental limitations like no decent error messages, integration with DBUnit, etc.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102995#4102995
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102995