[jboss-user] [JBoss Seam] - Failure to create and deploy a Seam project using the new st

I've spent the last couple of days trying to overcome my problem, without sucess ... I've downloaded the new RedHat studio, as I'm relatively new to Seam, and wanted "someone else" to do all the seam setup for me. I'm trying to build a simple WebApp with EJB3 support (I want my actions to be S

[jboss-user] [JBoss Seam] - Re: Failure to create and deploy a Seam project using the ne

Looks like I'm not the only one ... It also looks like this problem isn't 100% solved yet. Perhaps someone can offer a bypass, then. I want my Action classes to be able to use Entities (Entity beans). Is there a way to get this functionality without using Session Beans ? (right now I'm getting

[jboss-user] [JBoss Seam] - Re: Failure to create and deploy a Seam project using the ne

I must be missing something ... If I try what you suggest, then the EntityManager would still be : javax.persistence.EntityManager, and at runtime, it fails with : org.jboss.seam.RequiredException: In attribute requires non-null value: register.em What am I doing wrong ? View the original post

[jboss-user] [JBoss Seam] - Re: Failure to create and deploy a Seam project using the ne

That worked !! Thanks a lot. So now that I can have entity access in my POJO actions, is there any point in insisting to use SLSB (once the Studio\Seam\AS bug is fixed) ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077240#4077240 Reply to the post : http

[jboss-user] [JBoss Seam] - Re: Failure to create and deploy a Seam project using the ne

One more question (I guess I'll have more, as I find more and more things that need be adjusted as a result of this change) : Previously, the container was responsible for generating the DDL and keeping the DB schema with my entity classes. Now that I've switched to using just Hibernate, how do

[jboss-user] [JBoss Seam] - Re: Failure to create and deploy a Seam project using the ne

I guess that's not the problem ... The schema does get updated by Hibernate, but still I'm getting the following exception : javax.faces.el.EvaluationException: java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: User is not mapped [select u from User u where u.name=:

[jboss-user] [JBoss Seam] - Problems switching from SLSB Action to POJO Actions

Due to evalutaion of RH Studio, and the bug with EJB3 support in it, I'm trying to switch my simple Seam application from SLSB actions to POJO Actions. I've got my app to deploy Ok, but I'm having the following problem : When a user tried to register to the system, an RegisterAction class is la

[jboss-user] [JBoss Seam] - Re: Problems switching from SLSB Action to POJO Actions

BTW, I'm using Seam 1.2.1 on JBoss AS 4.0.5 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077621#4077621 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077621 ___ jboss-user

[jboss-user] [JBoss Seam] - Seam remoting and persistence

I'm just starting to play with Seam remoting, and I'm having the following problem with persistence : My POJO actions are able to query the DB just fine, but when trying to create a new entity instnace, the persist() method seems to return without doing anything in the DB. I'm attaching the re

[jboss-user] [JBoss Seam] - Re: Seam remoting and persistence

Thanks for the reply ! I will, but before I do, maybe this piece of info would help : When I switched to using EJB SLSB as actions, the problem went away. There seems to be something wrong (or mis-configured) with the replacement of the container-managed transactions. Even though I think I've co