If that's the case then I withdraw my comments. Thanks ;-)
-----Original Message-----
From: Zsombor Gegesy [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 10, 2002 11:08 AM
To: Turbine Torque Users List
Subject: Re[2]: Why is the database name hardcoded EVERYWHERE?
Hello Thierry,
Monday, June 10, 2002, 4:35:37 PM, you wrote:
LT> I'd say that is a requirement. We have some internal jsp web pages
LT> that we point to different Oracle instances, and we would be unable
LT> to use torque as the infrastructure because of that. Furthermore,
LT> it would be impossible to migrate an application through a
LT> development/testing/deployment cycle without reconfiguring and
LT> recompiling (assuming of course that there are distinct database
LT> instances devoted to each phase) and I suspect that most QA policies
LT> might not allow that.
You dont have to recompile anything, just modify the turbine run-time configuration file.
> I'd have to say yes. If you change your database name on the DB, then
> you update the Torque and build properties file and then you just run
> ant again and rebuild the XXXPeer classes. Then the system will work
> fine with your renamed database.
No, as far as I see, the "hardcoded database name" is just a symbolic name, for grouping Torque Objects. There is no need for recompiling anything.
bye
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
