Tapestry 4.0.2 Custom ApplicationInitializers Firing Twice!

[Karthik N]

Hi,

We have a custom set of HiveMind initializers that we're using with Tapestry
4.0.2.

OgnlFixesInitializer belongs to a different module than
DomainPackagesInitializer.

It should be fired BEFORE DomainPackagesInitializer and hence we have the
dependency configured.

While deploying this on Tomcat 5.5.17 as an exploded WAR, we observe that
both OgnlFixesInitializer and DomainPackagesInitializer get fired TWICE.

I have an initialized boolean member variable, and it prints FALSE both
times, indicating that the two different instances of OgnlFixesInitializer
and DomainPackagesInitializer are being created!

Any help would be most appreciated!

<module id="com.blah.ui.tapestry" version="1.0.0" >
   <service-point id="OgnlFixesInitializer" interface="
org.apache.tapestry.services.ApplicationInitializer">
       <create-instance class="OgnlFixesInitializer"/>
   </service-point>

   <contribution configuration-id="tapestry.init.ApplicationInitializers">
       <command id="OgnlFixesInitializer"
object="service:OgnlFixesInitializer"/>
   </contribution>
</module>

<module id="com.blah.util.tapestry" version="1.0.0" >

   <service-point id="DomainPackagesInitializer" interface="
org.apache.tapestry.services.ApplicationInitializer">
       <create-instance class="DomainPackagesInitializer"/>
   </service-point>
   <contribution configuration-id="tapestry.init.ApplicationInitializers">
       <command id="DomainPackagesInitializer"
object="service:DomainPackagesInitializer"
                        before="
com.effigent.ui.tapestry.OgnlFixesInitializer"/>
   </contribution>

</module>

Thanks, Karthik