Dear Peter, when do you think that Turbine 2.4 will be released?
A questions about the usage of flucrum-security: Can I map any version fields necessary for optimisic locking?!? Another question about antelope: What are you using for as validation framwork? Is it planed to use commons-validator for this job? Another sugesstion: The upcomming Turbine relases will heavliy lines on top of Avalon. Whe decided to use Spring as our IoC container instead as it offers execellent transcation support, hibernate integration and as well AOP. I guess the Spring is so flexible to reuse our Avalon Services as the are normally just beans, but reagarding lifecyle I have some doubts. It would be cool to get see more container independent services which can be plugged into Avalon, Pico and of course Spring IoC. I'm not trying to start another religous debate about the used framwork, but for __your__ needs Spring seems to be the best solution, and it would be cool to the the Turbine users decide what fits best. Thx & Bye Toby -----Urspr�ngliche Nachricht----- Von: Peter Courcoux [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 17. Juni 2004 00:00 An: Turbine Users List Betreff: RE: I need simple Access Control (Security) with Turbine withoutACL�s or Roles, how to do? It's been said before, and I know its not ideal, but the best place to start looking at this is to go to http://zebra.tigris.org and look at the zebra-antelope web application. It uses turbine, and hibernate and fulcrum-security. Don't be put off by the zebra workflow references. The zebra engine is not yet embedded in the antelope example. I know that Zebra-Antelope does use a recent 2.4-dev build, but I believe that it is the best resource we currently have for seeing how to use Hibernate with Turbine. Also fulcrum-security does the job for which it was written, but it is not a complete 'out-of-the-box' solution. Again, this is probably the best resource we currently have for getting an implementation working which can then be customised to suit. Look at how the fulcrum-security stuff works. If I recall correctly the ACL interface in fulcrum-security is an empty interface, so I think you can do what you want with it. You may need to customise the AccessController, which builds the ACL, the LoginUser action and possibly a SessionValidator. All of these are pluggable by changing the default settings in TurbineResources.properties. Peter On Wed, 2004-06-16 at 22:09, ANSI Webmaster wrote: > Ok i've been reading up like a crazed hippodrome on all the hibernate stuff, > and I'm also interested in where I can plug this into the Turbine ACL... > This was also part of why I wanted to use the new version in the CVS as it > said it had removed all the old Torque stuff. > > So where do I begin with this, whats a good place to start? > > /M > > -----Original Message----- > From: Eric Pugh [mailto:[EMAIL PROTECTED] > Sent: 10. juni 2004 19:39 > To: Turbine Users List > Subject: RE: I need simple Access Control (Security) with Turbine without > ACL�s or Roles, how to do? > > You are right about needing to use the Adapter.. If you are using Fulcrum > Security through the older Turbine Security service which is what things > like the default session validators and rundata use to look things up. > However, if you have reimplemented any of these things (which is pretty > commong) then you can just lookup the Fulcrum Security service directly like > any ohter avalon component and use methods.. > > A typical example would be admin screens that need extended security > information. For an example of this, check out the Antelope example app > available from here: http://zebra.tigris.org > > Eric > > > -----Original Message----- > > From: Lester Ward [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 10, 2004 6:43 PM > > To: 'Turbine Users List' > > Subject: RE: I need simple Access Control (Security) with Turbine > > without ACL�s or Roles, how to do? > > > > > > > If you use the Turbine adapter, you inherit a lot of that stuff, > > > but it runs in the 2.3 environment. If you use Fulcrum Security > > > directly, then all of that stuff is gone. > > > > I was under the impression that the only way to use Fulcrum Security with > > Turbine 2.3 was through the adaptor, but the statement above > > seems to imply > > otherwise. Could you elaborate? How does one not use the Turbine > > adaptor and > > still use Turbine? > > > > --------------------------------------------------------------------- > > 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] > > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
