Tapestry 5
  1. Tapestry 5
  2. TAP5-631

Contributed ApplicationInitializer not always executed when using tapestry-spring

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3
    • Fix Version/s: 5.1.0.4
    • Component/s: tapestry-spring
    • Labels:
      None

      Description

      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=admin@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=admin@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.

      1. Planning.zip
        144 kB
        Martin Papy

        Activity

        Martin Papy created issue -
        Martin Papy made changes -
        Field Original Value New Value
        Attachment Planning.zip [ 12404861 ]
        Howard M. Lewis Ship made changes -
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Resolution Invalid [ 6 ]
        Martin Papy made changes -
        Resolution Invalid [ 6 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        Howard M. Lewis Ship made changes -
        Status Reopened [ 4 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Summary ApplicationInitializer not allways executed Contributed ApplicationInitializer not allways executed when using tapestry-spring
        Component/s tapestry-spring [ 12312472 ]
        Howard M. Lewis Ship made changes -
        Summary Contributed ApplicationInitializer not allways executed when using tapestry-spring Contributed ApplicationInitializer not always executed when using tapestry-spring
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s 5.1.0.4 [ 12313854 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Martin Papy
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development