I want to pursue the idea of doing more of the service construction in non-reflective code.
So, a module will be able to delegate to a class, and that class will be used instead of a ServiceImplementationFactory to build services; there will be a naming convention used to define what services are defined in the module class (vs. in the XML). I'm hoping this will help speed application startup. Tapestry 4.0 is too slow to start. I'd like to look elsewhere for other speedups; perhaps a custom Map implementation tuned for small numbers of elements. Annoations would be nice, but I think we want to keep HiveMind/Tapestry useable with JDK 1.3 for a while longer ... something to discuss. Perhaps JDK 1.4 so we could ditch ORO. I'd like to see a replacement for BuilderFactory called "InjectionFactory" that uses significantly streamlined XML. I want to be able to use a Schema to parse an arbitrary XML stream. I want to see descriptors that allow Spring code to be used as native HiveMInd services. I'd like to (expirement with) caching the contents of XML descriptors on the file system so that restarts of an application are faster. On 9/21/05, David J. M. Karlsen <[EMAIL PROTECTED]> wrote: > James Carman wrote: > > What do we want to accomplish with the 1.2 release? > > > Thorough and consistent documentation. I really think this would help on > HiveMind's popularity. > > -- > David J. M. Karlsen - +47 90 68 22 43 > http://www.davidkarlsen.com > http://mp3.davidkarlsen.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
