[ https://issues.apache.org/jira/browse/TAP5-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698270#action_12698270 ]
Martin Papy commented on TAP5-631: ---------------------------------- You are right. As soon as I comment the piece of code that calls the Spring service involved, the initializeApplication(context,initilizer) is allways called again... Here I just commented the line >>> aDaoService.initDao(); public void initializeApplication(Context context, ApplicationInitializer initializer) { for (DaoService<?> aDaoService : _lDaoServices) { aDaoService.initDao(); } initializer.initializeApplication(context); } > ApplicationInitializer not allways executed > ------------------------------------------- > > Key: TAP5-631 > URL: https://issues.apache.org/jira/browse/TAP5-631 > Project: Tapestry 5 > Issue Type: Bug > Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3 > Reporter: Martin Papy > Priority: Blocker > Attachments: Planning.zip > > > I noticed something very odd : sometimes the ApplicationInitilizer is not > executed. The difference between two launches ? At first sight : none (no > code changed, db is always recreated). > What I am sure of : > - ApplicationInitializer ( and my contribution ) is always created : I can > see them in logs > - I don't change anything between 2 tries. Just "maven jetty:run" launched > from Eclipse, then stop then launched again. > - If I execute the same app with T5.0.18 => No problem : > ApplicationInitializer is always launched > - If I switch back to T5.1.0.2 => random phenomenon appears again > At this point... I am not sure it is a real bug... But I don't know were to > look at. One thing is important. This behaviour occured after I added > Spring/JPA (before that I was using tapestry-hibernate Module). > This are the result of two consecutive launches : > Success : > [INFO] services.PlanningModuleInitializer Create PlanningModuleInitializer > >>>>>>>>>>>>>>>> PlanningModuleInitializer.initializeApplication > >>>>>>>>>>>>>>>> <<<<<<<<<<<<<<<<<<<<<<< > Hibernate: select count(*) as col_0_0_ from TBL_USER userimpl0_ limit ? > [DEBUG] impl.AbstractDaoImpl Count 'class > com.makheia.planning.model.impl.UserImpl' Entities : 0 records > [INFO] impl.UserDaoImpl Initialising UserDao default datas > Hibernate: select userfuncti0_.USERFUNCTION_ID as USERFUNC1_3_3_, > [............] > [DEBUG] impl.AbstractDaoImpl Persisting class > com.makheia.planning.model.impl.UserImpl - Object : [User > [Id=0][FullName=admin admin][email=ad...@localhost]] > [DEBUG] interceptors.TimeStampInterceptor Update [createdDate] value to Mon > Apr 06 13:14:47 CEST 2009 > [DEBUG] interceptors.TimeStampInterceptor Update [updatedDate] value to Mon > Apr 06 13:14:47 CEST 2009 > [DEBUG] interceptors.TimeStampInterceptor Change TimeStamp before saving > [[User [Id=0][FullName=admin admin][email=ad...@localhost]]] : TS = Mon Apr > 06 13:14:47 CEST 2009 > Hibernate: insert into TBL_USER (TS_CREATEDDATE, TS_LASTMODIFIEDBY, > TS_UPDATEDDATE, USER_ACCOUNT_NON_EXPIRED, USER_ACCOUNT_NON_LOCKED, > USER_CREDENTIALS_NON_EXPIRED, USER_EMAIL, USER_ENABLED, USER_FIRSTNAME, > USER_GROUP_ID, USER_LASTNAME, USER_PASSWORD, USER_PHONENUMBER, > USER_SALUTATION, userFunction, USER_USERNAME) values (?, ?, ?, ?, ?, ?, ?, ?, > ?, ?, ?, ?, ?, ?, ?, ?) > [INFO] spring.SpringModule Spring version 2.5.6 with 58 defined beans. > Failure (launched 10 sec later without changing anything) : > [INFO] services.PlanningModuleInitializer Create PlanningModuleInitializer > [INFO] spring.SpringModule Spring version 2.5.6 with 58 defined beans. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.