CALLING ALL CODERS!

I'm pretty much done with the SPI (Service Provider Interface) for a security system 
to be integrated into Struts.  I've taken some ideals from the Turbine Security 
Service and simplified others.

The basic premise; four pricipals, StrutsUser, StrutsGroup, StrutsRole and 
StrutsPermission.

StrutsUser - The user, with a HashMap backed attribute collection.
StrutsGroup - A collection of StrutsUsers.
StrutsPermission - A representation of a permission to perform an action, simply holds 
its permission name.
StrutsRole - A collection of StrutsPermissions to make grouping of permissions easier.

I need assistance in creating SPIAdapters.  These are the adapter between the rights 
system fa�ade for the Struts application and a persistence enginge of some kind.  The 
adapter must know how to initialise itself (a Commons-Configuration object is 
supplied, from an XML document) and how to initialise its resources.  At present the 
adapter must only implement one interface to be used with the rights system 
"SPIAdapter".

I will be working on a Torque backed SPIAdapter and I'm looking for others to help, 
with maybe a Hibernate backed one and Castor, or even an XML backed one.  If you feel 
like contributing any other engine support please feel free.  I'll be co-ordinating 
the activities, and hopefully will have a CVS module up shortly.

I've attached the interface to be implemented, if anyone has any questions please feel 
free to email me direct, and just so I can keep tabs please email me if you want to 
contribute a provider.

I'd suggest for the time being putting all providers in their own package, e.g. 
com.shadowraider.struts.security.provider.torque for the Torque Provider.

Best regards,

Cameron Gray
Operations Director, UltraSpeed UK Limited

Tel/Fax: 0800 689 9898 W: www.ultraspeed.co.uk
AIM: UltraSpeedNetOps ICQ: 159796008

Portable:  Survives system reboot.

Attachment: SPIAdapter.java
Description: SPIAdapter.java

Reply via email to