You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Georg Kallidis <ge...@cedis.fu-berlin.de> on 2014/02/11 09:13:51 UTC
fulcrum security torque and turbine v4-m2
Hi,
I have a little bit concerns about the current state of the Torque OR
-Mapping in the Fulcrum Security Torque Component, and how to integrate
it into the Turbine Framework. Current state is:
In Fulcrum Security Torque rev 1524160 from 17. September 2013 "Switch
security model to Fulcrum Security API"
In Turbine rev 1526838 from 27. September 2013 "Temporarily add the
code that should have been generated by Torque, until 4.1 is released".
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). 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.
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.
Thanks,
Best regards, Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Antwort: Re: fulcrum security torque and turbine v4-m2
Posted by Georg Kallidis <ge...@cedis.fu-berlin.de>.
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 <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>,
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: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: Antwort: Re: fulcrum security torque and turbine v4-m2
Posted by Thomas Vandahl <tv...@apache.org>.
On 07.04.14 12:14, Georg Kallidis wrote:
> shows a lot of inconsistencies, and almost in any case Torque 3.3 is
> involved (cft. copied output below).
I'm not sure what this plugin shows here.
> Should we not clean up this soon? The easiest way to do this seems to be
> to introduce another Fulcrum component scheduler to get rid of this (?)
This is what fulcrum-quartz was meant for. I had this almost working a
couple of years ago, then my hard disk died suddenly. And this part of
the development went with it...
We should give it another try.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Antwort: Re: fulcrum security torque and turbine v4-m2
Posted by Georg Kallidis <ge...@cedis.fu-berlin.de>.
Hi,
I just read in a previous thread of this mail conversation:
> (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.
Checking the dependencies with
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.3.1</version>
<executions>
<execution>
<id>enforce</id>
<configuration>
<rules>
<DependencyConvergence />
</rules>
</configuration>
<goals>
<goal>enforce</goal>
</goals>
</execution>
</executions>
</plugin>
shows a lot of inconsistencies, and almost in any case Torque 3.3 is
involved (cft. copied output below).
Should we not clean up this soon? The easiest way to do this seems to be
to introduce another Fulcrum component scheduler to get rid of this (?)
Best regards, Georg
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Turbine 4.0-M2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce) @ turbine ---
[WARNING]
Dependency convergence error for
commons-configuration:commons-configuration:1.8 paths to dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-configuration:commons-configuration:1.8
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-configuration:commons-configuration:1.4
[WARNING]
Dependency convergence error for commons-logging:commons-logging:1.1.1
paths to dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-configuration:commons-configuration:1.8
+-commons-logging:commons-logging:1.1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-logging:commons-logging:1.1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-intake:1.0.6
+-commons-logging:commons-logging:1.1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-beanutils:commons-beanutils-core:1.7.0
+-commons-logging:commons-logging:1.0
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-logging:commons-logging:1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-org.apache.jcs:jcs:1.3
+-commons-logging:commons-logging:1.1
[WARNING]
Dependency convergence error for
commons-collections:commons-collections:3.2.1 paths to dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-collections:commons-collections:3.2.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-parser:1.0.2
+-commons-collections:commons-collections:3.2
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-beanutils:commons-beanutils-core:1.7.0
+-commons-collections:commons-collections:2.0
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-collections:commons-collections:3.2
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-impl:2.2.1
+-commons-collections:commons-collections:3.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-instrumented:2.2.1
+-commons-collections:commons-collections:3.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.velocity:velocity:1.7
+-commons-collections:commons-collections:3.2.1
[WARNING]
Dependency convergence error for commons-lang:commons-lang:2.6 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-configuration:commons-configuration:1.8
+-commons-lang:commons-lang:2.6
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-lang:commons-lang:2.6
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-localization:1.0.6
+-commons-lang:commons-lang:2.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-parser:1.0.2
+-commons-lang:commons-lang:2.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-intake:1.0.6
+-commons-lang:commons-lang:2.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-lang:commons-lang:2.3
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-security-api:1.1.0-SNAPSHOT
+-commons-lang:commons-lang:2.5
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-security-memory:1.1.0-SNAPSHOT
+-commons-lang:commons-lang:2.5
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.velocity:velocity:1.7
+-commons-lang:commons-lang:2.4
[WARNING]
Dependency convergence error for commons-pool:commons-pool:1.4 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-intake:1.0.6
+-commons-pool:commons-pool:1.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-dbcp:commons-dbcp:1.2.2
+-commons-pool:commons-pool:1.3
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-pool:commons-pool:1.3
[WARNING]
Dependency convergence error for javax.mail:mail:1.4.1 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-javax.mail:mail:1.4.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.commons:commons-email:1.2
+-javax.mail:mail:1.4.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-log4j:log4j:1.2.15
+-javax.mail:mail:1.4
[WARNING]
Dependency convergence error for concurrent:concurrent:1.0 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-org.apache.jcs:jcs:1.3
+-concurrent:concurrent:1.0
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-impl:2.2.1
+-concurrent:concurrent:1.3.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-instrumented:2.2.1
+-concurrent:concurrent:1.3.4
[WARNING] Rule 0:
org.apache.maven.plugins.enforcer.DependencyConvergence failed with
message:
Failed while enforcing releasability the error(s) are [
Dependency convergence error for
commons-configuration:commons-configuration:1.8 paths to dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-configuration:commons-configuration:1.8
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-configuration:commons-configuration:1.4
,
Dependency convergence error for commons-logging:commons-logging:1.1.1
paths to dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-configuration:commons-configuration:1.8
+-commons-logging:commons-logging:1.1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-logging:commons-logging:1.1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-intake:1.0.6
+-commons-logging:commons-logging:1.1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-beanutils:commons-beanutils-core:1.7.0
+-commons-logging:commons-logging:1.0
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-logging:commons-logging:1.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-org.apache.jcs:jcs:1.3
+-commons-logging:commons-logging:1.1
,
Dependency convergence error for
commons-collections:commons-collections:3.2.1 paths to dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-collections:commons-collections:3.2.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-parser:1.0.2
+-commons-collections:commons-collections:3.2
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-beanutils:commons-beanutils-core:1.7.0
+-commons-collections:commons-collections:2.0
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-collections:commons-collections:3.2
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-impl:2.2.1
+-commons-collections:commons-collections:3.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-instrumented:2.2.1
+-commons-collections:commons-collections:3.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.velocity:velocity:1.7
+-commons-collections:commons-collections:3.2.1
,
Dependency convergence error for commons-lang:commons-lang:2.6 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-configuration:commons-configuration:1.8
+-commons-lang:commons-lang:2.6
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-commons-lang:commons-lang:2.6
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-localization:1.0.6
+-commons-lang:commons-lang:2.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-parser:1.0.2
+-commons-lang:commons-lang:2.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-intake:1.0.6
+-commons-lang:commons-lang:2.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-lang:commons-lang:2.3
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-security-api:1.1.0-SNAPSHOT
+-commons-lang:commons-lang:2.5
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-security-memory:1.1.0-SNAPSHOT
+-commons-lang:commons-lang:2.5
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.velocity:velocity:1.7
+-commons-lang:commons-lang:2.4
,
Dependency convergence error for commons-pool:commons-pool:1.4 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.fulcrum:fulcrum-intake:1.0.6
+-commons-pool:commons-pool:1.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-dbcp:commons-dbcp:1.2.2
+-commons-pool:commons-pool:1.3
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-commons-pool:commons-pool:1.3
,
Dependency convergence error for javax.mail:mail:1.4.1 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-javax.mail:mail:1.4.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.commons:commons-email:1.2
+-javax.mail:mail:1.4.1
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-log4j:log4j:1.2.15
+-javax.mail:mail:1.4
,
Dependency convergence error for concurrent:concurrent:1.0 paths to
dependency are:
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.torque:torque-runtime:3.3
+-org.apache.jcs:jcs:1.3
+-concurrent:concurrent:1.0
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-impl:2.2.1
+-concurrent:concurrent:1.3.4
and
+-org.apache.turbine:turbine:4.0-M2-SNAPSHOT
+-org.apache.excalibur.component:excalibur-component:2.2.1
+-org.apache.excalibur.components:excalibur-pool-instrumented:2.2.1
+-concurrent:concurrent:1.3.4
]
...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Antwort: Re: fulcrum security torque and turbine v4-m2
Posted by Georg Kallidis <ge...@cedis.fu-berlin.de>.
Hi Thomas,
thanks for the details and hints. Yes, some reflection would be
necessary.
I think at the moment about extending AbstractEntityManager with a
"peerClass" attribute/child providing (optionally) a (Non-Base-)PeerImpl
class. The code would be very similar to the existing code for
"className", except that a single "peerInstance" method in the API
manager class is sufficient, if I use some kind of generic marker
interface (instantiating could be done only once may be). I would not
prefer another layer in the API/Fulcrum Torque component at the moment.
Most of the TorqueTurbine..ManagerImpl classes then could use this
method. The TorqueAbstractTurbine .. classes would remain untouched.
This would be of some help and may be sufficient. This breaks the
encapsulation a little bit up, but we have some more decoupling.
As Turbine uses Torque-ORM extensively, I think it is justified to have
some more considerations concering Torque integration.
I´ll check it in in the next days ..
Best regards, Georg
Von: Thomas Vandahl <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>,
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: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: fulcrum security torque and turbine v4-m2
Posted by Thomas Vandahl <tv...@apache.org>.
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: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org