[EMAIL PROTECTED] wrote:
>
> I'd like to take Velocity 1.1 and ExtendedProperties from Apache
> commons-collections.jar into use in Turbine 2.2 (maybe in 2.1 also, if we
> have enough time to test it). I'll have time to do the changes during the
> coming weekend. Are there any objections to consider (maybe Jason has
> already done something)?
Velocity 1.1 will make it into Turbine 2.1. I have added some code
to torque to allow templates to be retrieved from jar files and/or
the classpath. When I've tested it I will roll it into Velocity and
I would like to update torque so that it is easier for projects to
upgrade templates used for source/sql generation.
There has been some discussion on the commons list (but mostly I
have discussed this with Geir) about creating a Configuration interface
and using the ExtendedProperties as a concrete implementation.
I was going to wander through the source and replace all the old
Configuration references to ExtendedProperties, but that's just
another round of hard coding. I think with a little effort we
can make a relatively simple Configuration interface so that
config info can be pulled from XML files, ExtendedProperties, LDAP
or whatever. This is why I haven't removed the references to the
Configuration class.
James Strachan on the commons list was also talking about something
like this as well. I would rather not just plug in the
ExtendedProperties,
I think we should plug in a more general configuration mechnanism into
Turbine and the Services framework especially if we hope to make the
Services framework available to non-turbine users.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://jakarta.apache.org/commons
http://tambora.zenplex.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
