Henning Schmiedehausen wrote:
Please report problems with this RC to our issue tracker at

I'm not sure where to put this as these are not exactly Turbine problems, so I decided to go with the list.

- Commons configuration 1.1 logs failed JNDI lookups at ERROR level. If one uses the mixed configuration as described in the configuration-howto, this means an error entry in the log with every access to a not overridden configuration key. This is at least annoying. I recommend reverting to 1.0 for this reason, at least until somebody can come up with an idea how to fix this.

- The generated OM-classes for the TorqueSecurityService rely on a database called "default" in their maps. I don't know if that is a Torque issue, but this behaviour needs a special DataSource configuration for "default" where the previous version simply used the configured default DataSource as in

        torque.database.default=turbine

Do I miss something? Some configuration key perhaps?

Any comments/hints are welcome.

Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to