[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3821) seam-gen - entity is not mapped in war project on AS5

Thu Jan 8 10:11:04 EST 2009

    [ https://jira.jboss.org/jira/browse/JBSEAM-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445876#action_12445876 ] 

Julien Kronegg commented on JBSEAM-3821:
----------------------------------------

I had the same issue. The server startup sequence is the following:

15:33:23,440 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
15:33:23,440 INFO  [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120)
...
15:35:07,612 INFO  [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=#testSeamProject2
15:35:07,706 INFO  [Version] Hibernate Annotations 3.4.0.GA
15:35:07,721 INFO  [Environment] Hibernate 3.3.1.GA
15:35:08,034 INFO  [Environment] hibernate.properties not found
15:35:08,050 INFO  [Environment] Bytecode provider name : javassist
15:35:08,050 INFO  [Environment] using JDK 1.4 java.sql.Timestamp handling
15:35:08,206 INFO  [Version] Hibernate Commons Annotations 3.1.0.GA
15:35:08,206 INFO  [Version] Hibernate EntityManager 3.4.0.GA
15:35:08,378 WARN  [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
15:35:09,487 INFO  [AnnotationBinder] Binding entity from annotated class: org.domain.testseamproject2.entity.SqlColumn
15:35:09,581 INFO  [EntityBinder] Bind entity org.domain.testseamproject2.entity.SqlColumn on table SQL_COLUMN
... (other entities are discovered or the like)
15:35:15,487 INFO  [Version] Hibernate Validator 3.1.0.GA
15:35:15,628 INFO  [HibernateSearchEventListenerRegister] Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.
15:35:16,018 INFO  [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
15:35:16,034 INFO  [InjectedDataSourceConnectionProvider] Using provided datasource
15:35:17,143 INFO  [SettingsFactory] RDBMS: Microsoft SQL Server, version: 9.00.3042
15:35:17,143 INFO  [SettingsFactory] JDBC driver: Microsoft SQL Server 2005 JDBC Driver, version: 1.2.2828.100
15:35:17,175 INFO  [Dialect] Using dialect: org.hibernate.dialect.SQLServerDialect
15:35:17,190 INFO  [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
15:35:17,206 INFO  [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
...
15:35:29,565 INFO  [ServletContextListener] Welcome to Seam 2.1.1.GA
...
15:35:51,800 INFO  [Initialization] Installing components...
...
15:36:36,175 INFO  [Contexts] starting up: org.jboss.seam.security.persistentPermissionResolver
15:36:36,175 WARN  [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required.
15:36:36,175 INFO  [Contexts] starting up: org.jboss.seam.security.permissionMapper
15:36:36,175 INFO  [Contexts] starting up: org.jboss.seam.navigation.pages
15:36:36,659 INFO  [Contexts] starting up: testSeamProject2EntityManagerFactory
... (here, the entity manager is supposed to bind the entities, which is not the case. Thus, the first query raises a QuerySyntaxException because the entity is not mapped)

We found the following workaround: in the persistence.xml, we added a <class> tag for each entity, so the that when the testSeamProject2EntityManagerFactory is started up, all entities are loaded.
The persistence.xml now looks like:

   <persistence-unit name="testSeamProject2" transaction-type="JTA">
      <provider>org.hibernate.ejb.HibernatePersistence</provider>
      <jta-data-source>java:/testSeamProject2Datasource</jta-data-source>

      <class>org.domain.testseamproject2.entity.MyEntityClass1</class>
      <class>org.domain.testseamproject2.entity.MyEntityClass2</class>
      <class>org.domain.testseamproject2.entity.MyEntityClass3</class>

      <properties>
         <property name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect"/>
         <property name="hibernate.hbm2ddl.auto" value=""/>
         <property name="hibernate.show_sql" value="true"/>
         <property name="hibernate.format_sql" value="true"/>
         <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
      </properties>
   </persistence-unit>

At that point, we suppose that there is a loading problem, possibly involving the seam.properties (which must be present in the root directory of a jar so that the jar is inspected for entities) and/or hot deployment.

> seam-gen - entity is not mapped in war project on AS5
> -----------------------------------------------------
>
>                 Key: JBSEAM-3821
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3821
>             Project: Seam
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 2.1.1.CR2
>         Environment: JDK5
> JBoss AS 5.0.0.GA
>            Reporter: Jozef Hartinger
>             Fix For: 2.1.2.CR1
>
>         Attachments: genWarRich.txt
>
>
> When accessing generated entity page the application is failing on "org.hibernate.hql.ast.QuerySyntaxException: Vehicle is not mapped [select vehicle from Vehicle vehicle]" . I am using standard release-process.txt database tables. To reproduce the issue: 
> 1.) Create new war project and generate entities. 
> 2.) Log into the application and click PersonList or VehicleList

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira