Hi Thomas,
I have created an issue in JIRA TRB-92. At the moment I am bit at a
loss: I already had finished a implementation as I described, but then I
moved the code more to the Torque package, which is not so elegant, as
it duplicates some methods (I use now an Peer Manager class, would be
some kind of mixin), but the "extension" is then more bundled in the
proper component. But I depend on interfaces in the generated Peer
classes (in both solutions). This could be done manually - and we would
all be fine, although testing could come only after this step. Torque
could not do this (adding interfaces into the generated peer classes) as
far as I can see (I posted a question in Torque user mailing list).
There is another solution: Because the DO Torque classes provide a
getPeer method, a generated Peer interface (with getPeer method) could
get the peer this way, but would nonetheless after this being stucked,
as this interface does not know and could not know (just kind of marker
interface to get the Peer), which peer methods are used (e.g.
retrieveByPK or List<T> doSelect). Should we go this way? Am I missing
anything??
At the moment I would stay with the current (not yet checked in)
solution having a PeerManager in the Torque component...
Best regards, Georg
P.S: Torque 4 maven plugin generates all classes properly, I did a wrong
statement in my first post.
Von: Thomas Vandahl <[email protected]>
An: Turbine Developers List <[email protected]>,
Datum: 15.02.2014 17:55
Betreff: Re: fulcrum security torque and turbine v4-m2
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]
