RE: Re[2]: Why is the database name hardcoded EVERYWHERE?Hi all,
I just ported over from Turbine2.1 to Turbine 2.2, and am using the
decoupled Torque. Everything has shaken out fine (no security in my app
:-) ) except for some methods that do a set of an int:
javac.compile:
[javac] Compiling 71 source files to C:\kinaseprofiler\target\classes
[javac]
C:\kinaseprofiler\src\java\com\upstate\kinaseprofiler\scheduledjobs\
ScintillationFileMonitor.java:440: setCol(int) in
com.upstate.kinaseprofiler.tor
que.db.om.BaseReaction cannot be applied to (<null>)
[javac]
reworkRe
action.setCol( null );
[javac]
In my .xml file the column Col is marked as an INTEGER, but the only method
generated was setCol(int), no setCol(Integer) therefore I can not pass in
any NULLS! Kind of a showstopper for me.. I didn't see anything in the
build.properties, could it be I need to upgrade to CVS Head of torque?
Eric
-----Original Message-----
From: Lach, Thierry [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 10, 2002 11:51 AM
To: 'Turbine Torque Users List'
Subject: RE: Re[2]: Why is the database name hardcoded EVERYWHERE?
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]>
