as I have added a test with defined peer classes 
TurbineDefaultModelManagerTest), which is not yet automatically support in 
torque, the tests failed of course with e.g.

java.lang.ClassCastException: 
org.apache.fulcrum.security.torque.om.TurbineGroupPeerImpl cannot be cast 
to org.apache.fulcrum.security.torque.peer.Peer
        at 
org.apache.fulcrum.security.torque.peer.PeerManagerDefaultImpl.getPeerInstance(PeerManagerDefaultImpl.java:44)

I could comment out the tests again, until Torque is able to generate Peer 
interfaces or another solution is found ...

Best regards, Georg



Von:    Thomas Vandahl <[email protected]>
An:     [email protected]
Datum:  02.08.2016 18:24
Betreff:        Re: svn commit: r1754914 - in 
/turbine/fulcrum/trunk/security/torque/src/java/org/apache/fulcrum/security/torque/om:
 
TurbineGroupPeerImpl.java TurbinePermissionPeerImpl.java 
TurbineRolePeerImpl.java TurbineUserPeerImpl.java



On 02.08.16 15:40, [email protected] wrote:
> Author: gk
> Date: Tue Aug  2 13:40:01 2016
> New Revision: 1754914
> 
> URL: http://svn.apache.org/viewvc?rev=1754914&view=rev
> Log:
> TRB-98
> -  until Torque 4.1 is not released (TORQUE-309 is already resolved), 
add peer interface 
org.apache.fulcrum.security.torque.peer.TorqueTurbinePeer manually to 
otherwise generated peer impl classes.
> 
> Added:
> 
turbine/fulcrum/trunk/security/torque/src/java/org/apache/fulcrum/security/torque/om/TurbineGroupPeerImpl.java
 
  (with props)
> 
turbine/fulcrum/trunk/security/torque/src/java/org/apache/fulcrum/security/torque/om/TurbinePermissionPeerImpl.java
 
  (with props)
> 
turbine/fulcrum/trunk/security/torque/src/java/org/apache/fulcrum/security/torque/om/TurbineRolePeerImpl.java
 
  (with props)
> 
turbine/fulcrum/trunk/security/torque/src/java/org/apache/fulcrum/security/torque/om/TurbineUserPeerImpl.java
 
  (with props)

Actually you should not need these classes. You can always create an
instance of BasePeerImpl and configure it accordingly. Fulcrum security
does not use advanced Torque features.

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to