On Mon, 2002-03-18 at 13:12, robert burrell donkin wrote: > hi Stephane > > i developed a texen extension which sounds a little similar to this last > year (for use in another jakarta project). i seem to remember that the > general feeling then was that texen development was frozen (in terms of > adding a lot of extra functionality) pending separating texen out from the > main velocity distribution (maybe into a separate velocity subproject) and > so the extension never made it in. i don't know whether this still holds > true now or - if so - whether you might be able to get some momentum for > the separation once velocity 1.3 is out.
How about post 1.3 we propose to move texen out. I think there are three of use who are very familiar with it. You, myself and Stephane. I'm up for it if you guys are. > - robert > > On Monday, March 18, 2002, at 04:05 PM, Stephane Bailliez wrote: > > > > > For Torque, to generate the classes from the VM I have felt the need to > > feed > > the context with a few pull tools to help with complex manipulation in the > > vm. > > > > This is somewhat an extension of the context properties (these are not > > static) so I'm cross posting so that both worlds know it, I don't think > > this > > can be seen as Torque specific but rather Texen related. Barely this a > > couple of tools like StringUtils, FileUtils and Calendar would fit most > > needs but some could need more (just like the tools in Turbine for > > example) > > > > However question remains how to specify it. > > Obviouslly it would be nice to set it up from the existing context > > properties files but classpath comes into play as well. Did anyone thought > > about something like that ? > > If we take a Ant only configuration approach that would be something like: > > > > <texentask ...> > > <tools> > > <classpath refid="myclasspath"/> > > <tool name="Strings" classname="org.apache.lang.Strings"/> > > <tool name="Files" classname="org.apache.lang.Files"/> > > <tool name="Calendar > > classname="java.util.GregorianCalendar"/> > > </tools> > > </texentask> > > > > And maybe add a helper to describe the tools from a properties file. but > > tool.Strings=org.apache.lang.Strings > > tool.Files=... > > > > Otherwise we can assume that 'tool.<name>=<classname>' to be a reserved > > keyword for adding tools to the context and just add a classpath element > > to > > Texen to optionally load tools from this loader if specified. > > > > Thoughts ? > > > > Stephane > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]. > > org> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]. > > org> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
