How to update project from 2.0 to 2.1 Seam?

[mikail.ahundov.gmail.com]

What I need to upgrade project from 2.0.3 to 2.1.0 Seam? I use Eclipse. I need to change all libs or some other files?

[sjmenden]

To be safe, I'd recommend creating a new project with Seam 2.1.0 and migrating your 2.0.3 code over.  You may be able to get away with purely copying the libs, but, you may not. 

[mikail.ahundov.gmail.com]

Thank you!!!

[twhitehead.twhiteheadjm.hotmail.com]

My experience was that there were a number of things I had to change.

1. Search all your files for 2.0.xsd and replace with 2.1.xsd

2. If you are using seam pdf then look for http://jboss.com/products/seam/pdf and replace with http://jboss.com/products/seam/document

3. If you are using an ear then make sure jboss-seam.jar is not in your war MANIFEST.INF or the factories in jboss-seam.jar try to load twice and you will see:

java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)

4. If you are using seam mail then I cant help as I could not get past the problems mentioned in http://seamframework.org/Community/SeamMailAgain
So I have roled back to 2.0.3 for now.

[tony.herstell1]

Seamsters please confirm this and pin this thread (and add to).

I have had problems with Seam Message (when Internationalised) but Pete advised using the truck as these are now allegedly fixed.

I, however, decided due to probs with email, to also roll back for now.

Hopefully BETA2 or RC1 will fix things up to the usually very high standard we have been used to.

I as a user (and non contributor at present!) really do appreciate the work the seamsters do.

[utdrew]

If you are using drools to do security checks then you will need to change the import line in your file from:

import org.jboss.seam.security.PermissionCheck

to:

import org.jboss.seam.security.permission.PermissoinCheck

[pmuir]

Tony, the mail issue is not in JIRA. Please file an issue and attach a test case so we can fix it!

[gothmog]

Hi,

Just gone through this somewhat painful process now and in addition to all the above had to changes EL queries that worked in 2.0 that don't work in 2.1 as follows:

framework:entity-query name\="timesheetGroups" ejbql\="select g from Group g where g.tagset.name \= 'timesheet' and (g.account \= \#{currentUser} or g.global is true)"

had to change to

framework:entity-query name\="timesheetGroups" ejbql\="select g from Group g where g.tagset.name \= 'timesheet' and (g.account \= \#{currentUser.id} or g.global is true)"

i.e. had to explicitly add an .id otherwise the EL didn't evaluate properly

Also found that the identity.login action seems hard wired to redirect to home.seam where as before if there was no pages action it would redirect back to where you came from.

No doubt a few more things as I keep going - like now my Jboss Dev Studio keeps giving stackoverflow errors :( but by in large I'm happy to be at the latest codebase - keep up the good work!

Troy

[henrikrathje]

Thanks to Timothy for the tip on deleting the jboss-seam.jar from the ear file before deploying it!

I've just got the seam booking example deployed on

- Portal 2.7.1.GA, with Seam 2.1.1.CR1 and Portlet Bridge 1.0.0b5.. still some weird errors are logged now and then like

ERROR [STDERR] 2009-01-23 08:56:46 org.jboss.portletbridge.AjaxPortletBridge doFacesRequest

, but at least its running and I got rid of the

java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)

Puiihh...Think i'm in deep here... doing a proof-of-concept on the Portal 2.7.1 using Seam and JSF with webservices as integration to the backend which is JBoss ESB 4.4.GA

:-s

- Henrik