You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by ilfrin <il...@poczta.onet.pl> on 2003/09/19 00:16:32 UTC
a problem moving TDK to turbine 2.3
Hi,
This is the limit of my abilities I think, for the last few hours I
didn't move one step ahead
I'm using jdk 1.4.2, and the TDK 2.2, which I try to make work with
turbine 2.3 and torque 3.1, percisely I'm concerned about standard
app that is being generated, which I would like to use as a basis
for a production app. I first generated the standard app in 2.2 and
run it, then I changed the lib/*jar files on the app
(webapps/../web-inf/lib)
a) I put there the fileupload jar, turbine 2.3, torque 3.1 and all
the jars that accompany it and removed the old versions from the
dir,
b) then I changed the TR.props for the new one (from turbine 2.3)
and added the lines that were additional compared to the tdk
version (a few lines that include flux as I recall) and I changed
the torque props to use the SharedPool....
c) then I added new turbine-schema security files from torque 3.1,
then I had to change the turbine-security.xml file for the build to
work (the sql schema generator would crash), all the columns that
had a javaName attr in the schema, had to be referenced here the
same way e.g.
<TurbineGroup Name="global" GroupId="1" />
d) I run the app ... and well after doing some other cleaning and
little fixing which I don't recall by now I got the login screen
and atfer I log in as turbine/turbine (or any correct account,
because the login and logout actions work fine) I get to main view
.. and the there's a crash .. (shown below)
it looks like it is looking for the column that was removed from
every table, except user, in the files that I got with torque 3.1
but I have no idea why this occurs ..
if you have any suggestions PLEASE help, cause I'm way past
schedule with my project and I still don't even have a working
spike solution ..
or maybe the TDK 2.3 will come up tomorrow ? :)
neeah .. that would be too easy ..
error message:
org.apache.turbine.util.security.DataBackendException: Failed to build
ACL for user 'turbine': getGroups(Criteria) failed: Column not found:
Unknown column 'TURBINE_GROUP.OBJECTDATA' in 'field list'
--------------------------------------------------------------------------------
java.sql.SQLException: Column not found: Unknown column
'TURBINE_GROUP.OBJECTDATA' in 'field list' at
org.gjt.mm.mysql.MysqlIO.sendCommand(Unknown Source) at
org.gjt.mm.mysql.MysqlIO.sqlQueryDirect(Unknown Source) at
org.gjt.mm.mysql.MysqlIO.sqlQuery(Unknown Source) at
org.gjt.mm.mysql.Connection.execSQL(Unknown Source) at
org.gjt.mm.mysql.Connection.execSQL(Unknown Source) at
org.gjt.mm.mysql.Statement.executeQuery(Unknown Source) at
org.gjt.mm.mysql.jdbc2.Statement.executeQuery(Unknown Source) at
com.workingdogs.village.QueryDataSet.(Unknown Source) at
org.apache.torque.util.BasePeer.executeQuery(BasePeer.java:1539) at
org.apache.torque.util.BasePeer.doSelect(BasePeer.java:1391) at
org.apache.torque.util.BasePeer.doSelect(BasePeer.java:1368) at
org.apache.turbine.om.security.peer.GroupPeer.doSelect(GroupPeer.java:166)
at
org.apache.turbine.services.security.db.DBSecurityService.getGroups(DBSecurityService.java:518)
at
org.apache.turbine.services.security.BaseSecurityService.getAllGroups(BaseSecurityService.java:1199)
at
org.apache.turbine.services.security.db.DBSecurityService.getACL(DBSecurityService.java:151)
at
org.apache.turbine.services.security.TurbineSecurity.getACL(TurbineSecurity.java:478)
at
org.apache.turbine.modules.actions.AccessController.doPerform(AccessController.java:134)
at org.apache.turbine.modules.Action.perform(Action.java:86) at
org.apache.turbine.modules.ActionLoader.exec(ActionLoader.java:134) at
org.apache.turbine.Turbine.doGet(Turbine.java:760) at
org.apache.turbine.Turbine.doPost(Turbine.java:891) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:534) rethrown as
org.apache.torque.TorqueException: Column not found: Unknown column
'TURBINE_GROUP.OBJECTDATA' in 'field list' at
org.apache.torque.util.BasePeer.throwTorqueException(BasePeer.java:236)
at org.apache.torque.util.BasePeer.executeQuery(BasePeer.java:1550) at
org.apache.torque.util.BasePeer.doSelect(BasePeer.java:1391) at
org.apache.torque.util.BasePeer.doSelect(BasePeer.java:1368) at
org.apache.turbine.om.security.peer.GroupPeer.doSelect(GroupPeer.java:166)
at
org.apache.turbine.services.security.db.DBSecurityService.getGroups(DBSecurityService.java:518)
at
org.apache.turbine.services.security.BaseSecurityService.getAllGroups(BaseSecurityService.java:1199)
at
org.apache.turbine.services.security.db.DBSecurityService.getACL(DBSecurityService.java:151)
at
org.apache.turbine.services.security.TurbineSecurity.getACL(TurbineSecurity.java:478)
at
org.apache.turbine.modules.actions.AccessController.doPerform(AccessController.java:134)
at org.apache.turbine.modules.Action.perform(Action.java:86) at
org.apache.turbine.modules.ActionLoader.exec(ActionLoader.java:134) at
org.apache.turbine.Turbine.doGet(Turbine.java:760) at
org.apache.turbine.Turbine.doPost(Turbine.java:891) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:534) Caused by:
java.sql.SQLException: Column not found: Unknown column
'TURBINE_GROUP.OBJECTDATA' in 'field list' at
...... et cetera
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi again .. a little correction
i> c) then I added new turbine-schema security files from torque 3.1,
i> then I had to change the turbine-security.xml file for the build to
i> work (the sql schema generator would crash), all the columns that
i> had a javaName attr in the schema, had to be referenced here the
i> same way e.g.
i> <TurbineGroup Name="global" GroupId="1" />
that is of course not from the new torque but from the new turbine
(torque-security-schema.xml and schedler-schema.xml)
and I also just learned that if I wipe out all the OM classes that
have anything to do with Users and Roles and all that stuff (i leave
only the Rdfs), both from web-inf/classes/org/apache/torque/.. (I
wonder how did that get here .. but it's all generated by the build)
and from web-inf/classes/org/mycomp/newapp/om then .. nothing changes
.. which means that the damn app doesn't care about my OM classes so
where does it get the old schemas from and what are the classes that
try to access it ..
one more thing for the record, all the OM classes compile with a
deprecation warning for overwriting the old getMapBuilder() from
BasePeer
so the SecureScreen from the TDK works just fine as long as the acl
object is null .. if there is a user logged in it crashes ..
as I said .. please try to solve this case ;)
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re[2]: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi Scott,
19 września 2003, 01:48:33, zastalo napisane:
SE> ilfrin wrote:
>> or maybe the TDK 2.3 will come up tomorrow ? :)
>> neeah .. that would be too easy ..
>>
>>
SE> Perhaps the following message will prove useful:
SE> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-user@jakarta.apache.org&msgNo=16192
hmm well I admit that I run into this message a while ago, but I
thought that it is not yet stable enough (the TDK 2.3 itself) to use
it in production purposes, because they're still working on it
completing it and patching, correct me if I'm wrong ..
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re[3]: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi
i> WebappClassLoader: validateJarFile(D:\development\projekty\id\infor\tdk\webapps\
i> bulletins\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, secti
i> on 9.7.2. Offending class: javax/servlet/Servlet.class
ok, I dealed with this error, had to remove the servlet.jar from the
webapps/bulletins/web-inf/lib dir (due to servlet 2.3 spec) .. but
still the app gives me only a 404 error ..
please help ;)
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
Re[3]: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi
i> WebappClassLoader: validateJarFile(D:\development\projekty\id\infor\tdk\webapps\
i> bulletins\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, secti
i> on 9.7.2. Offending class: javax/servlet/Servlet.class
ok, I dealed with this error, had to remove the servlet.jar from the
webapps/bulletins/web-inf/lib dir (due to servlet 2.3 spec) .. but
still the app gives me only a 404 error ..
please help ;)
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re[2]: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi there,
19 września 2003, 01:48:33, zastalo napisane:
SE> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-user@jakarta.apache.org&msgNo=16192
ok, who's the wise guy ? I build the app as it is supposed to be,
while starting tomcat it starts like this
2003-09-20 02:06:15 org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
2003-09-20 02:06:15 org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
2003-09-20 02:06:16 org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
2003-09-20 02:06:17 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.27-LE-jdk14
WebappClassLoader: validateJarFile(D:\development\projekty\id\infor\tdk\webapps\
bulletins\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, secti
on 9.7.2. Offending class: javax/servlet/Servlet.class
log4j:ERROR setFile(null,false) call failed.
java.io.FileNotFoundException: \logs\turbine.log (System cannot find
the path)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
then I get a few more FNFEs with other log files .. then all the
services start et cetera but I can't get the app to work ..
http://localhost:8080/bulletins/servlet/bulletins gives me just a
"HTTP Status 404 - /bulletins/servlet/bulletins" msg from Tomcat ..
any suggestions ? of course I used only the things provided with the
TDK-2.3 test version and changed nothing
after startup in the webapp/bulletins/logs/turbine.log file I get
2003-09-20 02:17:38,842 [main] INFO org.apache.stratum.component.ComponentLoader - loading component: name=torque class=org.apache.torque.Torque config=D:\development\projekty\id\infor\tdk\webapps\bulletins\WEB-INF\conf\Torque.properties
2003-09-20 02:17:38,842 [main] DEBUG org.apache.stratum.component.ComponentLoader - attempting to load 'org.apache.torque.Torque' with the config file 'D:\development\projekty\id\infor\tdk\webapps\bulletins\WEB-INF\conf\Torque.properties'.
2003-09-20 02:17:39,102 [main] DEBUG org.apache.stratum.component.ComponentLoader - good news! org.apache.torque.Torque successfully configured and initialized
and the tdk/logs/localhost_log.xxx file gets me all kinds of msg
from the HostConfig[localhost], StandardHost[localhost],
WebappLoader[/bulletins], ContextConfig[/bulletins],
StandardManager[/bulletins] telling about varius things deployed or
configured for the bulletins app ..
but the browser still gets a 404 error ..
any idea why? please send me any suggestions, cause I don't know where
to start from if it doesn't work from the very beginning, and a 404
error is a not very informative ;)
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re[2]: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi Scott,
19 września 2003, 01:48:33, zastalo napisane:
SE> ilfrin wrote:
>> or maybe the TDK 2.3 will come up tomorrow ? :)
>> neeah .. that would be too easy ..
>>
>>
SE> Perhaps the following message will prove useful:
SE> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-user@jakarta.apache.org&msgNo=16192
hmm well I admit that I run into this message a while ago, but I
thought that it is not yet stable enough (the TDK 2.3 itself) to use
it in production purposes, because they're still working on it
completing it and patching, correct me if I'm wrong ..
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
Re[2]: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi there,
19 września 2003, 01:48:33, zastalo napisane:
SE> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-user@jakarta.apache.org&msgNo=16192
ok, who's the wise guy ? I build the app as it is supposed to be,
while starting tomcat it starts like this
2003-09-20 02:06:15 org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
2003-09-20 02:06:15 org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
2003-09-20 02:06:16 org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
2003-09-20 02:06:17 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.27-LE-jdk14
WebappClassLoader: validateJarFile(D:\development\projekty\id\infor\tdk\webapps\
bulletins\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, secti
on 9.7.2. Offending class: javax/servlet/Servlet.class
log4j:ERROR setFile(null,false) call failed.
java.io.FileNotFoundException: \logs\turbine.log (System cannot find
the path)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
then I get a few more FNFEs with other log files .. then all the
services start et cetera but I can't get the app to work ..
http://localhost:8080/bulletins/servlet/bulletins gives me just a
"HTTP Status 404 - /bulletins/servlet/bulletins" msg from Tomcat ..
any suggestions ? of course I used only the things provided with the
TDK-2.3 test version and changed nothing
after startup in the webapp/bulletins/logs/turbine.log file I get
2003-09-20 02:17:38,842 [main] INFO org.apache.stratum.component.ComponentLoader - loading component: name=torque class=org.apache.torque.Torque config=D:\development\projekty\id\infor\tdk\webapps\bulletins\WEB-INF\conf\Torque.properties
2003-09-20 02:17:38,842 [main] DEBUG org.apache.stratum.component.ComponentLoader - attempting to load 'org.apache.torque.Torque' with the config file 'D:\development\projekty\id\infor\tdk\webapps\bulletins\WEB-INF\conf\Torque.properties'.
2003-09-20 02:17:39,102 [main] DEBUG org.apache.stratum.component.ComponentLoader - good news! org.apache.torque.Torque successfully configured and initialized
and the tdk/logs/localhost_log.xxx file gets me all kinds of msg
from the HostConfig[localhost], StandardHost[localhost],
WebappLoader[/bulletins], ContextConfig[/bulletins],
StandardManager[/bulletins] telling about varius things deployed or
configured for the bulletins app ..
but the browser still gets a 404 error ..
any idea why? please send me any suggestions, cause I don't know where
to start from if it doesn't work from the very beginning, and a 404
error is a not very informative ;)
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl
Re: a problem moving TDK to turbine 2.3
Posted by Scott Eade <se...@backstagetech.com.au>.
ilfrin wrote:
> or maybe the TDK 2.3 will come up tomorrow ? :)
> neeah .. that would be too easy ..
>
>
Perhaps the following message will prove useful:
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-user@jakarta.apache.org&msgNo=16192
HTH,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: a problem moving TDK to turbine 2.3
Posted by Scott Eade <se...@backstagetech.com.au>.
ilfrin wrote:
> or maybe the TDK 2.3 will come up tomorrow ? :)
> neeah .. that would be too easy ..
>
>
Perhaps the following message will prove useful:
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-user@jakarta.apache.org&msgNo=16192
HTH,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
Re: a problem moving TDK to turbine 2.3
Posted by ilfrin <il...@poczta.onet.pl>.
Hi again .. a little correction
i> c) then I added new turbine-schema security files from torque 3.1,
i> then I had to change the turbine-security.xml file for the build to
i> work (the sql schema generator would crash), all the columns that
i> had a javaName attr in the schema, had to be referenced here the
i> same way e.g.
i> <TurbineGroup Name="global" GroupId="1" />
that is of course not from the new torque but from the new turbine
(torque-security-schema.xml and schedler-schema.xml)
and I also just learned that if I wipe out all the OM classes that
have anything to do with Users and Roles and all that stuff (i leave
only the Rdfs), both from web-inf/classes/org/apache/torque/.. (I
wonder how did that get here .. but it's all generated by the build)
and from web-inf/classes/org/mycomp/newapp/om then .. nothing changes
.. which means that the damn app doesn't care about my OM classes so
where does it get the old schemas from and what are the classes that
try to access it ..
one more thing for the record, all the OM classes compile with a
deprecation warning for overwriting the old getMapBuilder() from
BasePeer
so the SecureScreen from the TDK works just fine as long as the acl
object is null .. if there is a user logged in it crashes ..
as I said .. please try to solve this case ;)
--
Thanks,
ilfrin mailto:ilfrin@poczta.onet.pl