Ben Alex wrote:
My vote is for offering to help Jackrabbit implement an IoC-supporting design. If we can achieve that, it is of benefit to all IoC communities, not just Spring. We'd probably still continue with this project and focus on a Spring JSR 170 abstraction layer (eg wrap all those checked exceptions), and value-adding the Jackrabbit core infrastructure with Spring-specific features (eg ACL integration, nice PropertyEditors to facilitate wiring, JDBC-based repository etc).
i agree completely. in re CalDAV, we can obviously continue this pattern of cooperation by contributing core support directly to Jackrabbit and Spring extensions to this project.
what are your thoughts on implementing the WebDAV ACL spec? JSR 170 defines a narrower set of permissions than WebDAV ACL, and it doesn't offer any way to manage permissions. i'm curious what Jackrabbit's plans are for WebDAV ACL, if any.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Acegiwebdav-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegiwebdav-developer
