May 5, 2008 at 1:56 AM
The reference implementations, quick starts, and spikes feature slightly different implementations of a Bootstrapper class to carry out application initialization duties. Will Prism eventually address bootstrapping as a first class concept, or will this responsibility forever lie with the applications themselves?
May 5, 2008 at 8:45 AM
Do you mean will we have a reusable bootstrapper?

Yes the bootstrapper is different in the quickstarts. We did this because in quickstarts we want you to focus on a specific topic and not have to grok too many concepts, hence quick. We will be pointing this out in our docs. The implementaiton we use in the RI is the recommended approach.

May 5, 2008 at 1:58 PM
Yes, my question is whether the Prism team will eventually create a reusable bootstrapper. Even in the various ramp-up projects, the Bootstrapper classes are more similar than dissimilar.

At the core of my question is whether my team should try to solve the bootstrapping problem for our application set or if we should first wait for guidance from the Prism team. And at the core of that question is what the Prism team considers to be in scope,

Sorry if I'm jumping the gun a bit here. I'm just very excited with this effort and eager to apply it.

May 8, 2008 at 8:20 AM
We are looking into a Boostrapper template (abstract base class) for this.

Thanks for the suggestion.