[ https://issues.apache.org/jira/browse/COCOON-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cédric Damioli updated COCOON-2197: ----------------------------------- Fix Version/s: 2.3.1 (was: 2.3.0) > Making the cocoon-auth-block acegi-security-sample work > ------------------------------------------------------- > > Key: COCOON-2197 > URL: https://issues.apache.org/jira/browse/COCOON-2197 > Project: Cocoon > Issue Type: Wish > Components: - Samples > Affects Versions: 2.2 > Reporter: Patrick Heiden > Assignee: Grzegorz Kossakowski > Priority: Minor > Fix For: 2.3.1 > > Attachments: cocoon-acegi-sample-svn-diff.patch > > > The current acegi-security-sample doesn't work with acegi version used! > So an update to spring-security (2.0.0-SNAPSHOT) fixed that problem. > Following steps need to be performed: > 1) get the latest trunk from spring-security (acegi) (see [1] for details) > 2) compile and install that trunk (mvn install, maybe skip the more than 1000 > tests ;) > 3) change the pom.xml of cocoon-acegisecurity-sample block: > replace the acegi dependency with: > <dependency> > <groupId>org.springframework.security</groupId> > <artifactId>spring-security-core</artifactId> > <version>2.0.0-SNAPSHOT</version> > <exclusions> > <exclusion> > <groupId>avalon-framework</groupId> > <artifactId>avalon-framework</artifactId> > </exclusion> > </exclusions> > </dependency> > 4) replacements in META-INF/cocoon/xpatch/acegi-filter-patch.xweb: > every org.acegi. ... should be replaced by org.springframework.security > 5) the same needs to be done for all bean's class attribute inside > META-INF/cocoon/spring/cocoon-acegisecurity.xml > 6) mvn install; mvn jetty:run > I would guess, that by making acegi a spring portfolio project, the rework on > that project > contains better adoption of spring bean-lifecycles. -- This message was sent by Atlassian Jira (v8.20.10#820010)