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:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
