click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CLK-652) Upgrade to Spring 3.0.2 (JBoss 5 compatible)
Date Thu, 08 Apr 2010 14:56:36 GMT

     [ https://issues.apache.org/jira/browse/CLK-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bob Schellink updated CLK-652:
------------------------------

    Affects Version/s:     (was: 2.1.0)
        Fix Version/s:     (was: 2.2.0)

Trying to upgrade to Spring Security 3 turns out to be quite a task, so I'll leave this for
a future release.

Spring 3, especially Spring Security 3, is quite a beast and we should again consider just
splitting it off into its own example application.

I'm recording here the changes I had to make in order to convert to Spring Security 3:

Include the following jars:

spring-aop-3.0.2.RELEASE.jar
spring-asm-3.0.2.RELEASE.jar
spring-beans-3.0.2.RELEASE.jar
spring-context-3.0.2.RELEASE.jar
spring-core-3.0.2.RELEASE.jar
spring-expression-3.0.2.RELEASE.jar
spring-security-core-3.0.2.RELEASE.jar
spring-security-web-3.0.2.RELEASE.jar
spring-tx-3.0.2.RELEASE.jar
spring-web-3.0.2.RELEASE.jar

Here is the full spring-beans.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!--
   Licensed to the Apache Software Foundation (ASF) under one
   or more contributor license agreements.  See the NOTICE file
   distributed with this work for additional information
   regarding copyright ownership.  The ASF licenses this file
   to you under the Apache License, Version 2.0 (the
   "License"); you may not use this file except in compliance
   with the License.  You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing,
   software distributed under the License is distributed on an
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License.
-->

<beans:beans xmlns="http://www.springframework.org/schema/security"
  xmlns:beans="http://www.springframework.org/schema/beans"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:context="http://www.springframework.org/schema/context"
  xsi:schemaLocation="http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
        http://www.springframework.org/schema/context
        http://www.springframework.org/schema/context/spring-context-3.0.xsd
        http://www.springframework.org/schema/security
        http://www.springframework.org/schema/security/spring-security-3.0.xsd">

    <context:component-scan base-package="org.apache.click.examples" scope-resolver="org.apache.click.extras.spring.PageScopeResolver"/>

    <!-- Spring Security Setup -->

    <http auto-config="true">
        <!-- Uncomment the line below if you need login.htm to be accessed through HTTPS,
             and ensure that HTTPS is enabled on the server. -->
        <!--<intercept-url pattern="/springsecurity/login.htm" requires-channel="https"
/>-->

        <!-- Access to pages under the /springsecurity/secure folder requires to be authenticated
-->
        <intercept-url pattern='/springsecurity/secure/**' access='IS_AUTHENTICATED_REMEMBERED'/>

        <!-- Specify the login page url, failure url and default landing page url. -->
        <form-login login-page='/springsecurity/login.htm' authentication-failure-url="/springsecurity/login.htm?auth-error=1"
default-target-url="/"/>

        <!-- Specify a virtual "logout" url which forwards to the logout.htm page. -->
        <logout logout-url="/springsecurity/logout" logout-success-url="/springsecurity/logout.htm"/>
    </http>

    <beans:bean id="authenticationManager" class="org.springframework.security.authentication.ProviderManager">
        <beans:property name="providers">
            <beans:list>
                <beans:ref local="daoAuthenticationProvider" />
            </beans:list>
        </beans:property>
    </beans:bean>

    
    <beans:bean id="daoAuthenticationProvider" class="org.springframework.security.authentication.dao.DaoAuthenticationProvider">
        <beans:property name="userDetailsService" ref="userDetailsService"/>
    </beans:bean>

    <!-- Specify a simple property based authentication provider. For production
         systems switch to LDAP or JDBC based providers. -->

    <authentication-manager>
        <authentication-provider user-service-ref='userDetailsService'/>
    </authentication-manager>

	  <!-- This bean is optional; it isn't used by any other bean as it only listens and logs
-->
    <beans:bean id="loggerListener" class="org.springframework.security.authentication.event.LoggerListener"
/>

</beans:beans>



There were also a couple of package changes but these are easily be picked up by the compiler.

> Upgrade to Spring 3.0.2 (JBoss 5 compatible)
> --------------------------------------------
>
>                 Key: CLK-652
>                 URL: https://issues.apache.org/jira/browse/CLK-652
>             Project: Click
>          Issue Type: Task
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>
> Upgrade to Spring 3.0.2 and Spring Security 3.0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message