FWIW,
I've managed to get a working @Email validator by replacing all the hiberate*.jar files in my JBOSS/server/default/lib directory with the following:
hibernate-annotations.jar (from hibernate-annoations-3.3.0.GA)
| hibernate-commons-annotations.jar (ditto)
| hibernate-entitymanager.jar (from hibernate-entitymanager-3.3.1.GA)
| ejb3-persistance.jar (from hibernate-entitymanager-3.3.1.GA)
| hibernate-validator.jar (from hibernate-validator-3.0.0.GA)
| hibernate3.jar (from hibernate-3.2.5.ga)
I've replaced the lib/hibernate-all.jar bundled with Seam with the above for compile-time and all seems to work OK so far.
I've not tested the @Min validator that originally started this thread.
Seam 1.2.1-GA
JBoss 4.2.1
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073780#4073780
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073780
Hello,
i'm trying to get the testng tests working.
Could please someone explain, why the method invocation on a POJO- Seam- component is correctly intercepted by EE5SeamInvocationContext but each call to an ejb3 component is intercepted by EJB3InterceptorsInterceptor if i use the Jboss embedded.
This small deviation results in a fully loss of injection on EJB3-Seam-components. The POJO-components receive their injections as expected.
Thanks, Gena
PS. With the full installed jboss all works fine
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073774#4073774
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073774
hi,
our app is running into an exception and the problem has been put into JIRA - JBAS-4075. The thing is, JBossAS-4.0.5-SP1 is mentioned as having the fix and I am lost on how to get ahold of that (the service pack). I can't find any links etc, no mention in the download section.
so do I need to get all the source from SVN / CVS and just compile updated stuff?
and I remember reading somewhere for performance reasons, compiling may not be a bad thing as the standard build has debug stuff turned on and no optional compile flags etc - is there much point to doing this?
thanks
doug
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073768#4073768
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073768
I am not using JSF
But i tried using the renderRequest...
ServerInvocationContext serverContext = jrr.getControllerContext().getServerInvocation().getServerContext();
That call is throwing the following exception.
19:36:16,531 ERROR [CommandServlet] Exception in command invocation
| java.lang.LinkageError: Class org/jboss/portal/core/controller/ControllerContext violates loader constraints
| at java.lang.ClassLoader.defineClass1(Native Method)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073766#4073766
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073766
The lifecycle of an EJB3 extended persistence context is tied to the lifecycle of the bean that is using it. Seam allows you to use a bean with an extended persistence context, but it doesn't provide an extended persistence context to anything. Instead, the seam-managed persistence context is scoped to the conversation. Are both requests happening in the same conversation or are they separate conversations?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073763#4073763
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073763