[Acegisecurity-developer] Re: Javadocs from acegisecurity.sf.net ?

[Eoin Curran]

oops. found it.
http://acegisecurity.sourceforge.net/multiproject/acegi-security/apidocs/index.html
e.
Eoin Curran wrote:
An earlier message 
(http://sourceforge.net/mailarchive/message.php?msg_id=8803445) 
pointed to javadocs at
http://www.monkeymachine.co.uk/acegi/apidocs/index.html

These don't seem to exist (anymore). I can't find the javadoc on the 
site either. Would it be possible to publish the javadoc to the site? 
(maven should do this easily enough?).

eoin.


---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer

RE: [Acegisecurity-developer] Reducing the number of filters needed in web.xml

[Carlos Sanchez]

To sum up,

I'll create a class called net.sf.acegisecurity.FilterChain, with a property 
called filters.

About the syntax, I looked at map, that would suit here, but Spring 
application context don't allow beans as keys, maybe a lack of
functionality?

If we use this one we lose validation, so another option could be:

bean id=filterMapping abstract=true 
class=net.sf.acegisecurity.FilterMapping
property name=mappingvalue/*/value/property
/bean

bean id=channelProcessingFilterMapping parent=filterMapping
property name=filterref local=channelProcessingFilter//property
/bean

bean id=authenticationProcessingFilterMapping parent=filterMapping
property name=filterref 
local=authenticationProcessingFilter//property
/bean

bean id=filterChain class=net.sf.acegisecurity.FilterChain
property name=filters
list
ref local=channelProcessingFilterMapping/
ref local=authenticationProcessingFilterMapping/
/list
/property
/bean


More verbose, sure, but allows validation and avoids parsing and it's unlikely 
to change from one app to another.
If you are using XML you should avoid parsing text, that's the goal of XML. The 
problem is that Spring DTD is a bit verbose.


On Mon, 24 Jan 2005 11:15:03 +1100, Ben Alex [EMAIL PROTECTED] wrote:
 bryan ( [EMAIL PROTECTED]) wrote:
 
 
 bean id=filterChain class=net.sf.acegisecurity.FilterChain
 
 property name=filters
 value
 channelProcessingFilter=/*
 authenticationProcessingFilter=/*
 basicProcessingFilter=/*
 sessionIntegrationFilter=/*
 securityEnforcementFilter=/*
 /value
 /property
 
 /bean
 
 
 
 
 +1, especially using the syntax shown above as it's nice and intuitive.
 
 
 ---
 This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
 Tool for open source databases. Create drag--drop reports. Save time
 by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
 Download a FREE copy at http://www.intelliview.com/go/osdn_nl
 ___
 Home: http://acegisecurity.sourceforge.net
 Acegisecurity-developer mailing list
 Acegisecurity-developer@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
 




---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer