[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction

[ https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu... ] Bernhard Hablesreiter commented on JBIDE-4156: ---------------------------------------------- Ok, just retested everything - the workspace is in sync with the filesystem, everything is refreshed (tested with manual and automatic refresh). Due to the auto-publish feature, everytime (!) I save a java- or xhtml-file the console shows the following entries: 09:08:23,561 INFO [PersistenceUnitDeployment] Stopping persistence unit persistence.units:ear=testapp-ear.ear,unitName=testapp 09:08:23,561 INFO [SessionFactoryImpl] closing 09:08:23,561 INFO [SessionFactoryObjectFactory] Unbinding factory from JNDI name: persistence.units:ear=testapp-ear.ear,unitName=testapp 09:08:23,561 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} 09:08:23,561 INFO [SessionFactoryObjectFactory] Unbound factory from JNDI name: persistence.units:ear=testapp-ear.ear,unitName=testapp 09:08:23,562 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=testappDatasource' from JNDI name 'java:testappDatasource' 09:08:23,624 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=testappDatasource' to JNDI name 'java:testappDatasource' 09:08:23,624 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:ear=testapp-ear.ear,unitName=testapp 09:08:23,640 INFO [Configuration] Reading mappings from resource : META-INF/orm.xml 09:08:23,640 INFO [Ejb3Configuration] [PersistenceUnit: testapp] no META-INF/orm.xml found 09:08:23,640 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider 09:08:23,640 INFO [InjectedDataSourceConnectionProvider] Using provided datasource 09:08:23,687 INFO [SettingsFactory] RDBMS: MySQL, version: 5.1.22-rc-community 09:08:23,687 INFO [SettingsFactory] JDBC driver: MySQL-AB JDBC Driver, version: mysql-connector-java-5.1.6 ( Revision: ${svn.Revision} ) 09:08:23,687 INFO [Dialect] Using dialect: org.hibernate.dialect.MySQL5InnoDBDialect 09:08:23,687 INFO [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory 09:08:23,687 INFO [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup 09:08:23,687 INFO [TransactionManagerLookupFactory] instantiated TransactionManagerLookup 09:08:23,687 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled 09:08:23,687 INFO [SettingsFactory] Automatic session close at end of transaction: disabled 09:08:23,687 INFO [SettingsFactory] JDBC batch size: 15 09:08:23,687 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled 09:08:23,687 INFO [SettingsFactory] Scrollable result sets: enabled 09:08:23,687 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): enabled 09:08:23,687 INFO [SettingsFactory] Connection release mode: auto 09:08:23,687 INFO [SettingsFactory] Default schema: test 09:08:23,687 INFO [SettingsFactory] Maximum outer join fetch depth: 2 09:08:23,687 INFO [SettingsFactory] Default batch fetch size: 1 09:08:23,687 INFO [SettingsFactory] Generate SQL with comments: disabled 09:08:23,687 INFO [SettingsFactory] Order SQL updates by primary key: disabled 09:08:23,687 INFO [SettingsFactory] Order SQL inserts for batching: disabled 09:08:23,687 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory 09:08:23,687 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory 09:08:23,687 INFO [SettingsFactory] Query language substitutions: {} 09:08:23,687 INFO [SettingsFactory] JPA-QL strict compliance: enabled 09:08:23,687 INFO [SettingsFactory] Second-level cache: enabled 09:08:23,687 INFO [SettingsFactory] Query cache: disabled 09:08:23,687 INFO [SettingsFactory] Cache provider: org.hibernate.cache.HashtableCacheProvider 09:08:23,687 INFO [SettingsFactory] Optimize cache for minimal puts: disabled 09:08:23,687 INFO [SettingsFactory] Cache region prefix: testapp-ear_ear,testapp 09:08:23,687 INFO [SettingsFactory] Structured second-level cache entries: disabled 09:08:23,687 INFO [SettingsFactory] Echoing all SQL to stdout 09:08:23,687 INFO [SettingsFactory] Statistics: disabled 09:08:23,687 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled 09:08:23,687 INFO [SettingsFactory] Default entity-mode: pojo 09:08:23,687 INFO [SettingsFactory] Named query checking : enabled 09:08:23,687 INFO [SessionFactoryImpl] building session factory 09:08:23,687 INFO [SessionFactoryObjectFactory] Factory name: persistence.units:ear=testapp-ear.ear,unitName=testapp 09:08:23,687 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} 09:08:23,687 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: persistence.units:ear=testapp-ear.ear,unitName=testapp 09:08:23,687 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext 09:08:23,687 INFO [SchemaUpdate] Running hbm2ddl schema update 09:08:23,687 INFO [SchemaUpdate] fetching database metadata 09:08:23,687 INFO [SchemaUpdate] updating schema 09:08:23,702 INFO [SchemaUpdate] schema update complete 09:08:23,702 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} I did notice a working full-publishing sometimes, however, the application.xml is never touched - this must be because of another descriptor or something... I'll test this on another vista-machine today and see if the problem is somehow related to my vista-setup (however, I can't imagine what it could be...) -- 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