Hi Georg, On 11.02.14 09:13, Georg Kallidis wrote: > Only the bases classes could be apparently generated with the Torque 4 > plugin (?) (BTW In Turbine trunk Torque 3.3 is still present in the > pom.xml).
Yes. This is necessary as long as the old scheduler is still there. The extension / data object classes are in in the java folder > of Fulcrum Security Torque component, but what, if I need to extend the > DO classes? I probably would use the Torque ant tools, which could > generate all needed classes (may be together with other non Turbine > classes) and use another package taking fulcrum-turbine-schema.xml (copy > and paste it into my schema). But at this moment I think a configuration > option is missing, as the classes in > org.apache.fulcrum.security.torque.turbine depend on the DO classes in > package org.apache.fulcrum.security.torque.om. Shouldn´t this be > configurable (at own risk, of course)? I could else not figure out, how > I could use this Fulcrum component for an existing Turbine webapp. The classes generated by Torque refer to the "default" database which can be mapped to any other database you use with Torque. > > May be I try to say, what I think would be best (we know often only the > second best is achieved ;-): > > - build the OR-Mapping classes with or near to other non Turbine classes > (as I will probably have other tables in my database) from another > schema having it in one place. > > - allow for extending DO classes (as they are just skeletons) > > - allow for another package in Fulcrum Security Troque component. In principle, the object classes used can be configured in the component configuration. I never tried this, however. The old Torque Security Service shows what probably needs to be done: It was a Java reflection battlefield. I tried to make it somewhat simpler. If you want to take another shot, feel free. I will support you as best as I can. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
