Tapestry Integration Best Practice Advise

[Hensley, Richard]

I seeking best practice advise for using HiveMind in a Tapestry application.

This is my design so far:

I'm using the HiveMindFilter to initialize the registry.

I overrode createGlobal() in my engine to do the following:
    protected Object createGlobal(RequestContext arg0) {
        Global global = (Global) super.createGlobal(arg0);
        global.setRegistry(HiveMindFilter.getRegistry(arg0.getRequest()));
        return global;
    }

My global object has getXXX methods for all the services that I might need.
They are implemented something like:

    public Census getCensus() {
        return (Census) this.registry.getService(Census.class.getName(),
                Census.class);
    }

And my service definition is:

module (id=com.mckesson.lab.services version="1.0.0")
{
  service-point (id=Census interface=com.mckesson.lab.services.Census)
}

I have an interfaces jar that contains nothing but interface declarations
and the HiveMind service point declarations.

I have an implementation jar that contains all the implementation classes
and the HiveMind service point implementation declarations.

I'm fairly new to the use of a IoC container, so I could be all wet in this
design.

Any comments would be most appreciated.

Richard


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]