On Thu, 2004-06-17 at 07:55, ANSI Webmaster wrote: > Alright i'll work through it and see how it looks like. > > I've heard a lot of muttering about that I should use the Spring framework > for accessing hibernate. Do you have any experience on this, and if, hows > does this blend in to Fulcrum? > Sorry, I cannot help here. I have never used Spring.
> /M > > -----Original Message----- > From: Peter Courcoux [mailto:[EMAIL PROTECTED] > Sent: 17. juni 2004 00:00 > To: Turbine Users List > Subject: 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
