Hi Tmjee
Dmitry Zubarovsky previously wrote some Tapestry integration classes. You
can take a look in the archives of acegisecurity-developer. We were happy to
add Tapestry integration to the Acegi Security CVS, so you're welcome to
contribute code and tests.
Before sending in your current code, maybe it would help to get in touch
with Dmitry, as perhaps he could give you a copy of what he has done (he
posted most of it to the mailing list anyway!). That way you can compare
your approaches. I don't actually use Tapestry, so we should gain some
feedback from other Tapestry users before making it "officially" part of
Acegi Security.
In relation to dynamic loading of configuration, in early versions of Acegi
Security we used web.xml to hold some configuration. We ultimately relocated
this configuration to the application context, to take advantage of Spring's
various application context loading approaches (such as XML and properties
files). It shouldn't be too difficult to code whichever configuration
repository you want at the Spring level. I'm not sure of the value-add of
having Acegi Security handle different configuration sources when Spring
itself offers existing interfaces and implementations in this area.
Best regards
Ben
________________________________
From: tmjee [mailto:[EMAIL PROTECTED]
Sent: Saturday, 8 May 2004 12:28 PM
To: ben alex
Subject: Tapestry Security Integration
Hi Ben,
I am interested in working on a SecurityInterceptor for Tapestry.
FilterInterceptor is not really suitable as urls are actually generated by
Tapestry and is subjected to change. Users of Tapestry are usually maked
from the details concerning the url. Tapestry do provides a
PageValidateListener that is suitable to do authorisation and authentication
stuff.
I have coded a TapestryInterceptor, TapestryInvocation,
TapestryDefinitionSource (AbstractTapestryDefinitionSource,
TapestryDefinitionMap etc). I am currently half way through the writing the
test cases and testing.
I would iike to contribute the code, if it is possible.
I am also thinking about, also, maybe a DaoDefinitionSource would be
nice. This is about the same as a DaoAuthenticationProvider.
DaoDefinitionSource will have a IoC pluggable DefinitionSourceDao that does
all the loading of definition source. This way, the storing of definition
source is not limited to eg. like in an spring xml file (as properties) but
also alterable dynamically (stored in some datastore). I would like to work
on this also, if it is ok with the developers working on acegi-security.
Can I have your feedback please?
Looking forward to hear from you soon.
regards
tmjee
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Acegisecurity-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
