1 2 Previous Next 15 Replies Latest reply on Feb 12, 2009 1:07 PM by lightguard

    seam-gen app works on 4.2.3, but blow up on 5

    mangelo123

      I pretty much have a very basic seam-gen generated app that works perfectly on JBoss AS 4.2.3. When I try to deploy to 5 it appears to load ok on startup of AS 5, but when I hit the URL I get the following in the log:


      19:58:44,111 INFO [Contexts] starting up: org.jboss.seam.security.identity
      19:58:44,813 INFO [RuleBase] parsing rules: /security.drl
      19:58:45,846 INFO [Contexts] starting up: org.jboss.seam.web.session
      19:58:46,254 ERROR [compiler] Missing Built-in Tag Libraries! Make sure they are included within the META-INF directory of Facelets' Jar
      19:58:46,294 ERROR [viewhandler] Error Rendering View[/home.xhtml]
      java.lang.NullPointerException
       at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
       at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
       at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
       at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524)
       at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
       at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
       at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216)
       at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
       at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
       at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
       at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
       at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
       at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
       at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
       at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
       at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
       at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
       at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
       at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
       at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
       at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
       at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
       at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
       at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68)
       at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
       at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
       at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
       at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
       at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
       at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
       at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
       at java.lang.Thread.run(Unknown Source)
      
      


        • 1. Re: seam-gen app works on 4.2.3, but blow up on 5
          alesj
          • 2. Re: seam-gen app works on 4.2.3, but blow up on 5
            mangelo123

            That did clear up the first error. Thank you for the solution.

            Now I get the following error stating that my table is not mapped when clearly it is. Like I stated before that this application works on 4.2.3.


            Caused by: javax.el.ELException: /CustomerList.xhtml @125,61 rendered="#{empty customerList.resultList}": Error reading 'resultList' on type org.domain.dillans.session.CustomerList_$$_javassist_1
             at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:76)
             at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:390)
             ... 54 more
            Caused by: java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: Customer is not mapped [select customer from Customer customer]
             at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:601)
             at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:96)
             at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:79)
             at org.jboss.seam.framework.EntityQuery.createQuery(EntityQuery.java:175)
             at org.jboss.seam.framework.EntityQuery.initResultList(EntityQuery.java:73)
             at org.jboss.seam.framework.EntityQuery.getResultList(EntityQuery.java:65)
             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
             at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
             at java.lang.reflect.Method.invoke(Unknown Source)
             at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
             at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
             at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
             at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31)
             at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
             at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:38)
             at org.jboss.seam.util.Work.workInTransaction(Work.java:41)
             at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:32)
             at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
             at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
             at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
             at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
             at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
             at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
             at org.domain.dillans.session.CustomerList_$$_javassist_1.getResultList(CustomerList_$$_javassist_1.java)
             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
             at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
             at java.lang.reflect.Method.invoke(Unknown Source)
             at javax.el.BeanELResolver.getValue(BeanELResolver.java:62)
             at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
             at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
             at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53)
             at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
             at org.jboss.el.parser.AstEmpty.getValue(AstEmpty.java:29)
             at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
             at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
             ... 55 more
            Caused by: org.hibernate.hql.ast.QuerySyntaxException: Customer is not mapped [select customer from Customer customer]
             at org.hibernate.hql.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:181)
             at org.hibernate.hql.ast.tree.FromElementFactory.addFromElement(FromElementFactory.java:110)
             at org.hibernate.hql.ast.tree.FromClause.addFromElement(FromClause.java:93)
             at org.hibernate.hql.ast.HqlSqlWalker.createFromElement(HqlSqlWalker.java:277)
             at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3056)
             at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2945)
             at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688)
             at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544)
             at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281)
             at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229)
             at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:251)
             at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183)
             at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:134)
             at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101)
             at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80)
             at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94)
             at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156)
             at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135)
             at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1650)
             at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:93)
             ... 90 more
            


            • 3. Re: seam-gen app works on 4.2.3, but blow up on 5

              I am also facing the same problem
              Can anyone give the solution please?

              • 4. Re: seam-gen app works on 4.2.3, but blow up on 5
                jaikiran

                 

                I am also facing the same problem
                Can anyone give the solution please?


                Which error (there are a couple of them mentioned in this thread)? You will have to give us more details, including the version of JBossAS and Java you are using and the entire exception stacktrace.

                While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.

                • 5. Re: seam-gen app works on 4.2.3, but blow up on 5
                  lightguard

                  Seeing the same thing (entities not mapped) on JBoss AS 5. My entities are in a WAR file (persistence.xml: WEB-INF/classes/META-INF/persistence.xml, and I do have the namespace in the persistence.xml) I found this thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138668 is that the solution?

                  • 6. Re: seam-gen app works on 4.2.3, but blow up on 5
                    jaikiran

                     

                    "Lightguard" wrote:
                    Seeing the same thing (entities not mapped) on JBoss AS 5. My entities are in a WAR file (persistence.xml: WEB-INF/classes/META-INF/persistence.xml, and I do have the namespace in the persistence.xml) I found this thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138668 is that the solution?


                    I am not at my system right now, but from what i remember, in JBoss-5.0 GA you don't have to change any default settings. All you have to do is create a jar containing those entities and the persistence.xml in the META-INF of the jar and place that jar in .war/WEB-INF/lib. The persistence unit will be picked up and deployed.

                    • 7. Re: seam-gen app works on 4.2.3, but blow up on 5
                      lightguard

                       

                      "jaikiran" wrote:

                      I am not at my system right now, but from what i remember, in JBoss-5.0 GA you don't have to change any default settings. All you have to do is create a jar containing those entities and the persistence.xml in the META-INF of the jar and place that jar in .war/WEB-INF/lib. The persistence unit will be picked up and deployed.


                      Thanks jaikiran, I'll have to give that a try. The workaround we have for not jarring up the JPA Entities is to list them in the persistence.xml using the &lt;class&gt; tag, but that can become very tedious and wind up with a very big persistence.xml file. The idea of putting all the entities inside of a jar and putting that jar into the lib makes a lot of sense. Thanks!

                      • 8. Re: seam-gen app works on 4.2.3, but blow up on 5
                        lightguard

                         

                        "jaikiran" wrote:
                        I am not at my system right now, but from what i remember, in JBoss-5.0 GA you don't have to change any default settings. All you have to do is create a jar containing those entities and the persistence.xml in the META-INF of the jar and place that jar in .war/WEB-INF/lib. The persistence unit will be picked up and deployed.


                        Jaikiran, after looking through the JPA 1.0 spec, this looks like a bug in the AS (or EJB3 / JPA deployer). The spec says that the WEB-INF/classes is a valid place to auto discover the entity classes, it just isn't being scanned, or the classes are not being loaded.

                        • 9. Re: seam-gen app works on 4.2.3, but blow up on 5
                          peterj

                          I think you should be able to place the entity bean in WEB-INF/classes as long as the persistence.xml file is located at WEB-INF/classes/META-INF/persistence.xml. I know I did this recently and it worked, but that might have been 4.2.3 and not 5.0.

                          • 10. Re: seam-gen app works on 4.2.3, but blow up on 5
                            lightguard

                             

                            "PeterJ" wrote:
                            I think you should be able to place the entity bean in WEB-INF/classes as long as the persistence.xml file is located at WEB-INF/classes/META-INF/persistence.xml. I know I did this recently and it worked, but that might have been 4.2.3 and not 5.0.


                            Yeah, it works fine in 4.2.x (and in 4.x in general I believe) but it does not work in 5. You try to do anything that queries the PersistenceContext it dies saying that the classes are not mapped, sorry don't have a full stack trace with me atm.

                            • 11. Re: seam-gen app works on 4.2.3, but blow up on 5
                              peterj

                              You're right. 5.0 barfs. Sigh.

                              • 12. Re: seam-gen app works on 4.2.3, but blow up on 5
                                peterj

                                Hmm, bad choice of wording? By "barfs" I did not mean that as an insult to AS 5.0, rather that 5.0 "expelled an error from deep within". :-0

                                • 13. Re: seam-gen app works on 4.2.3, but blow up on 5
                                  jaikiran

                                  Just gave it a try on JBossAS-5.0 GA and it worked for me without any issues. Here's my app setup:

                                  jar -tf test.war


                                  WEB-INF/classes/META-INF/persistence.xml
                                  WEB-INF/classes/org/myapp/servlet/SimpleServlet.class
                                  WEB-INF/classes/org/myapp/entity/Account.class
                                  WEB-INF/classes/org/myapp/entity/User.class
                                  WEB-INF/web.xml
                                  


                                  persistence.xml:

                                  <?xml version="1.0" encoding="UTF-8"?>
                                  <persistence xmlns="http://java.sun.com/xml/ns/persistence"
                                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                   xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
                                   version="1.0">
                                   <persistence-unit name="tempdb">
                                   <jta-data-source>java:/DefaultDS</jta-data-source>
                                   <properties>
                                   <property name="hibernate.hbm2ddl.auto" value="create-drop"/>
                                   </properties>
                                   </persistence-unit>
                                  </persistence>
                                  


                                  Account and User are my entities, something like this:

                                  @Entity
                                  @Table (name = "Account")
                                  public class Account implements Serializable {
                                  
                                   @Id
                                   @GeneratedValue
                                   @Column (name="id")
                                   private long id;
                                  


                                  And the web.xml:



                                  <?xml version="1.0" encoding="ISO-8859-1"?>
                                  <web-app version="2.5"
                                   xmlns="http://java.sun.com/xml/ns/javaee"
                                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
                                  
                                   <display-name>EJB3 Persistence</display-name>
                                  
                                   <servlet>
                                   <servlet-name>MyTestServlet</servlet-name>
                                   <servlet-class>org.myapp.servlet.SimpleServlet</servlet-class>
                                  
                                   </servlet>
                                  
                                   <servlet-mapping>
                                   <servlet-name>MyTestServlet</servlet-name>
                                   <url-pattern>/invokeServlet</url-pattern>
                                  
                                   </servlet-mapping>
                                  
                                  
                                  
                                  </web-app>


                                  The (test) servlet:

                                  public class SimpleServlet extends HttpServlet
                                  {
                                  
                                  
                                   @PersistenceContext
                                   private EntityManager em;
                                  
                                   public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
                                   {
                                  
                                   try
                                   {
                                   Context ctx = new InitialContext();
                                   TransactionManager txm = (TransactionManager) ctx.lookup("java:TransactionManager");
                                   txm.begin();
                                   System.out.println("Em is " + em);
                                   User user = new User();
                                   user.setName("Jaikiran");
                                   em.persist(user);
                                   em.flush();
                                   txm.commit();
                                   System.out.println("Saved user " + user.getId());
                                   Query query = em.createQuery("from User");
                                   List result = query.getResultList();
                                   System.out.println("Result = " + result.size());
                                   ...


                                  The console logs when the server is deploying the app:

                                  12:45:28,756 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=#tempdb
                                  12:45:28,823 INFO [Version] Hibernate Annotations 3.4.0.GA
                                  12:45:28,845 INFO [Environment] Hibernate 3.3.1.GA
                                  12:45:28,852 INFO [Environment] hibernate.properties not found
                                  12:45:28,857 INFO [Environment] Bytecode provider name : javassist
                                  12:45:28,864 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling
                                  12:45:28,993 INFO [Version] Hibernate Commons Annotations 3.1.0.GA
                                  12:45:28,999 INFO [Version] Hibernate EntityManager 3.4.0.GA
                                  12:45:29,075 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
                                  12:45:29,184 INFO [AnnotationBinder] Binding entity from annotated class: org.myapp.entity.Account
                                  12:45:29,261 INFO [EntityBinder] Bind entity org.myapp.entity.Account on table Account
                                  12:45:29,357 INFO [AnnotationBinder] Binding entity from annotated class: org.myapp.entity.User
                                  12:45:29,357 INFO [EntityBinder] Bind entity org.myapp.entity.User on table User
                                  12:45:29,540 INFO [CollectionBinder] Mapping collection: org.myapp.entity.User.accounts -> Account
                                  12:45:29,553 INFO [Version] Hibernate Validator 3.1.0.GA
                                  12:45:29,613 INFO [HibernateSearchEventListenerRegister] Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.
                                  12:45:29,624 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
                                  12:45:29,635 INFO [InjectedDataSourceConnectionProvider] Using provided datasource
                                  12:45:29,640 INFO [SettingsFactory] RDBMS: HSQL Database Engine, version: 1.8.0
                                  12:45:29,640 INFO [SettingsFactory] JDBC driver: HSQL Database Engine Driver, version: 1.8.0
                                  12:45:29,680 INFO [Dialect] Using dialect: org.hibernate.dialect.HSQLDialect
                                  12:45:29,688 INFO [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
                                  12:45:29,693 INFO [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
                                  12:45:29,697 INFO [TransactionManagerLookupFactory] instantiated TransactionManagerLookup
                                  12:45:29,697 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled
                                  12:45:29,697 INFO [SettingsFactory] Automatic session close at end of transaction: disabled
                                  12:45:29,697 INFO [SettingsFactory] JDBC batch size: 15
                                  12:45:29,697 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled
                                  12:45:29,698 INFO [SettingsFactory] Scrollable result sets: enabled
                                  12:45:29,699 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): disabled
                                  12:45:29,699 INFO [SettingsFactory] Connection release mode: auto
                                  12:45:29,700 INFO [SettingsFactory] Default batch fetch size: 1
                                  12:45:29,700 INFO [SettingsFactory] Generate SQL with comments: disabled
                                  12:45:29,700 INFO [SettingsFactory] Order SQL updates by primary key: disabled
                                  12:45:29,701 INFO [SettingsFactory] Order SQL inserts for batching: disabled
                                  12:45:29,701 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
                                  12:45:29,706 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
                                  12:45:29,706 INFO [SettingsFactory] Query language substitutions: {}
                                  12:45:29,706 INFO [SettingsFactory] JPA-QL strict compliance: enabled
                                  12:45:29,706 INFO [SettingsFactory] Second-level cache: enabled
                                  12:45:29,706 INFO [SettingsFactory] Query cache: disabled
                                  12:45:29,719 INFO [SettingsFactory] Cache region factory : org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge
                                  12:45:29,720 INFO [RegionFactoryCacheProviderBridge] Cache provider: org.hibernate.cache.HashtableCacheProvider
                                  12:45:29,722 INFO [SettingsFactory] Optimize cache for minimal puts: disabled
                                  12:45:29,722 INFO [SettingsFactory] Cache region prefix: persistence.unit:unitName=#tempdb
                                  12:45:29,722 INFO [SettingsFactory] Structured second-level cache entries: disabled
                                  12:45:29,734 INFO [SettingsFactory] Statistics: disabled
                                  12:45:29,735 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled
                                  12:45:29,736 INFO [SettingsFactory] Default entity-mode: pojo
                                  12:45:29,736 INFO [SettingsFactory] Named query checking : enabled
                                  12:45:29,802 INFO [SessionFactoryImpl] building session factory
                                  12:45:30,119 INFO [SessionFactoryObjectFactory] Factory name: persistence.unit:unitName=#tempdb
                                  12:45:30,121 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
                                  12:45:30,126 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: persistence.unit:unitName=#tempdb
                                  12:45:30,126 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext
                                  12:45:30,144 INFO [SchemaExport] Running hbm2ddl schema export
                                  12:45:30,145 INFO [SchemaExport] exporting generated schema to database
                                  12:45:30,147 INFO [SchemaExport] schema export complete
                                  12:45:30,152 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
                                  12:45:30,173 INFO [TomcatDeployment] deploy, ctxPath=/test, vfsUrl=test.war
                                  


                                  And finally when i access the servlet, here's the output as expected:

                                  12:47:30,700 INFO [STDOUT] Invoking doPost
                                  12:47:30,702 INFO [STDOUT] Em is org.jboss.jpa.tx.TransactionScopedEntityManager@13a96ba
                                  12:47:30,876 INFO [STDOUT] Saved user 1
                                  12:47:31,193 INFO [STDOUT] Result = 1
                                  


                                  Are you trying some way else?

                                  • 14. Re: seam-gen app works on 4.2.3, but blow up on 5
                                    lightguard

                                    Hm. Very odd. Those of us that are seeing this problem are deploying seam-gen applications. Makes me wonder if seam-gen is doing something wrong then. It is very odd that the same app works on 4.x and dies on 5. Looks like we'll have to see what the differences are in the persistence.xml files.

                                    Oh, a thought just came to me. Seam has it's own ClassLoader that it's using for incremental hot deploy (which shouldn't affect any other classloaders) of classes in the WEB-INF/dev directory. Could this be throwing things off?

                                    1 2 Previous Next