> Leon Messerschmidt wrote:
>
> > I added a new service named AssemblerBrokerService to the cvs. I also
added
> > some settings to the TR.properties file to support
AssemblerBrokerService.
>
> Looks good!
Cool!
> I would suggest defining constants in BaseJavaFactory for the strings that
> the specific Java factories are using.
>
> I would also suggest leaving only the Service interface, implementation
> and facade class (yet to be written) in this package, and moving
> the other classes to the turbine.util hierarchy.
>
> turbine.util.assemblerbroker.AssemblerFactory
> turbine.util.assemblerbroker.java.BaseFactory
> turbine.util.assemblerbroker.java.ActionFactory
> turbine.util.assemblerbroker.java.ScreenFactory
> turbine.util.assemblerbroker.java.NavigationFactory
>
> and then adding your classes under
> turbine.util.assemblerbroker.jpython
+1
Speaking of jpython integration. I'm not sure if we want to distribute the
jpython.jar with Turbine - most people will probably not want to.
What would be the best way of distributing my jpython assembler factories?
I can use Class.forname (kinda like the O'reilly uploader did) so that you
don't need jpython to compile. I can probably also make a separate .jar,
but somehow that doesn't appeal to me... Any thoughts on this?
> We have a long tradition of crazy package partitioning :)
he, he :-)
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
