[seam-issues] [JBoss JIRA] Commented: (JBSEAM-3035) upgrade to Spring JAR to version 2.5

[Karel Piwko (JIRA)]

    [ https://jira.jboss.org/browse/JBSEAM-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12535744#action_12535744 ] 

Karel Piwko commented on JBSEAM-3035:
-------------------------------------

Spring version was updated, the auto-discovery of entities in Spring example was overridden by a <class> tag line in META-INF/persistence-spring.xml for each POJO entity, such as: 

<persistence xmlns="http://java.sun.com/xml/ns/persistence" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
     xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" 
     version="1.0"> 
     <persistence-unit name="bookingDatabase" transaction-type="RESOURCE_LOCAL"> 
           <class>org.jboss.seam.example.spring.Booking</class> 
           ... 
     </persistence-unit> 
</persistence>

> upgrade to Spring JAR to version 2.5
> ------------------------------------
>
>                 Key: JBSEAM-3035
>                 URL: https://jira.jboss.org/browse/JBSEAM-3035
>             Project: Seam
>          Issue Type: Task
>          Components: Build, Spring
>    Affects Versions: 2.0.2.GA, 2.1.0.A1
>            Reporter: Dan Allen
>            Assignee: Marek Novotny
>            Priority: Minor
>             Fix For: 2.2.1.CR1
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Without the Spring 2.5 JAR, the org.springframework.web.jsf.el.SpringBeanFacesELResolver is not available. Spring 2.5 is backward compliant, so there should be no reason we are holding back.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira