July 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-4878) Create migration guide from Seam 2.2 to Seam 2.3 for reference guide

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4878: --------------------------------- Summary: Create migration guide from Seam 2.2 to Seam 2.3 for reference guide Key: JBSEAM-4878 URL: https://issues.jboss.org/browse/JBSEAM-4878 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4320) Conversation propagation in SeamTest is broken.

by Arno Mittelbach (JIRA)

Conversation propagation in SeamTest is broken. ----------------------------------------------- Key: JBSEAM-4320 URL: https://jira.jboss.org/jira/browse/JBSEAM-4320 Project: Seam Issue Type: Bug Reporter: Arno Mittelbach Coversation propagation between FacesRequests in SeamTest is broken when redirects occur. If a conversation is started in a FacesRequest that ends with a redirect, this conversation cannot be restored in a consecutive FacesRequest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] (JBSEAM-4978) Seam-gen commands using hibernate-tools doesn't work

by Tomas Remes (JIRA)

Tomas Remes created JBSEAM-4978: ----------------------------------- Summary: Seam-gen commands using hibernate-tools doesn't work Key: JBSEAM-4978 URL: https://issues.jboss.org/browse/JBSEAM-4978 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.BETA2 Reporter: Tomas Remes Fix For: 2.3.0.CR1 Seam-gen commands like "generate-model","generate", "generate-ui" does not work, because it's using old hibernate-tools version. Major problem is that this old version is using classes from hibernate-core 3.2.4 (and probably many other jars) and those are not compatible with hibernate 4 versions. So when you try for example command "generate-model", you will get following error: {noformat} jboss-seam-2.3.0.CR1-SNAPSHOT/seam-gen/build.xml:1554: java.lang.NoClassDefFoundError: org/hibernate/engine/Mapping {noformat} I am trying/investigating how is this used in JBoss Tools, but as far as I've understood there is entirely bundled old hibernate 3 and its related stuff. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
13
0 / 0

[JBoss JIRA] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5002: ------------------------------------- Summary: Components included with ui:include src="#{pageScopedViewId} broken Key: JBSEAM-5002 URL: https://issues.jboss.org/browse/JBSEAM-5002 Project: Seam 2 Issue Type: Bug Components: JSF Integration Affects Versions: 2.3.0.BETA2 Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986) Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.0.CR1 The following scenario that used to work in AS5/Seam2.2 doesn't work anymore in AS7/Seam2.3 for page-scoped and conversation-scoped "viewId" components: index.xhtml: {code} <h:form> <h:commandButton action="#{viewId.component1}" value="Component 1" /> <h:commandButton action="#{viewId.component2}" value="Component 2" /> </h:form> <ui:include src="#{viewId.viewId}"/> {code} {code} @Scope(ScopeType.PAGE) @Name("viewId") public class ViewIdComponent implements Serializable { private String viewId = "/component1.xhtml"; public void setViewId(String viewId) { this.viewId = viewId; } public String getViewId() { return viewId; } public void component1() { setViewId("/component1.xhtml"); } public void component2() { setViewId("/component2.xhtml"); } } {code} (compoent1 and 2 are redacted, contain a simple form) Only the first component works properly, actions in "component2" doesn't seem to be called after switching to "Component 2". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
13
0 / 0

[JBoss JIRA] (JBSEAM-4884) Misc issues

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4884: --------------------------------- Summary: Misc issues Key: JBSEAM-4884 URL: https://issues.jboss.org/browse/JBSEAM-4884 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir Fix For: 2.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
5
0 / 0

[JBoss JIRA] (JBSEAM-4882) Verify JBDS "seam-gen" works with new Maven structure

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4882: --------------------------------- Summary: Verify JBDS "seam-gen" works with new Maven structure Key: JBSEAM-4882 URL: https://issues.jboss.org/browse/JBSEAM-4882 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir Fix For: 2.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4693) 6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml

by simon lebettre (JIRA)

6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml --------------------------------------------------------------------------------- Key: JBSEAM-4693 URL: https://jira.jboss.org/browse/JBSEAM-4693 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: simon lebettre this does not make sense : " 6.12.2. Enabling Seam exception handling To enable Seam's exception handling, we need to make sure we have the master servlet filter declared in web.xml: " ==> Of course the master filter is in web.xml ! this would be more relevant : "we need to make sure that <web:exception-filter url-pattern="*.seam" /> is declared in components.xml" I m not being picky about the doc, it's been 7 months I have a bad user experience or loose some exception feedback because I forgot this line in components.xml ! -- 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

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] (JBSEAM-4881) Verify Seam-gen works with maven build structure

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4881: --------------------------------- Summary: Verify Seam-gen works with maven build structure Key: JBSEAM-4881 URL: https://issues.jboss.org/browse/JBSEAM-4881 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4487) Concurrent requests; one invalidates the session, results in recursive loop of session creation

by dave atkins (JIRA)

Concurrent requests; one invalidates the session, results in recursive loop of session creation ----------------------------------------------------------------------------------------------- Key: JBSEAM-4487 URL: https://jira.jboss.org/jira/browse/JBSEAM-4487 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1, 2.1.1.GA Environment: Jboss 4.2.2 with shipped Tomcat on Linux. Reporter: dave atkins I noticed that we had an massive number of sessions on one of our tomcat nodes that hosts our modest Seam app. After some investigation I discovered this in the log 2009-11-25 17:38:02,521 INFO [org.jboss.seam.contexts.Contexts] starting up: org.jboss.seam.web.session 2009-11-25 17:38:02,522 INFO [org.jboss.seam.contexts.Contexts] starting up: org.jboss.seam.security.identity 2009-11-25 17:38:02,522 INFO [org.jboss.seam.contexts.Contexts] starting up: org.jboss.seam.web.session 2009-11-25 17:38:02,522 INFO [org.jboss.seam.contexts.Contexts] starting up: org.jboss.seam.security.identity 2009-11-25 17:38:02,522 INFO [org.jboss.seam.contexts.Contexts] starting up: org.jboss.seam.web.session This is repeated for thousands of lines. After digging around the seam code I realised that if you have two concurrent requests and one invalidates the session before the other is finished, seam goes into an recursive loop of session creation (normally ended by stack overflow). Here's a stack trace showing two recursions. at org.jboss.seam.Component.newInstance(Component.java:2094) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:209) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:141) at org.jboss.seam.servlet.SeamListener.sessionCreated(SeamListener.java:45) at org.apache.catalina.session.StandardSession.tellNew(StandardSession.java:397) at org.apache.catalina.session.StandardSession.setId(StandardSession.java:369) at org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:828) at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:291) at org.apache.catalina.connector.Request.doGetSession(Request.java:2312) at org.apache.catalina.connector.Request.getSession(Request.java:2075) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:216) at org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:545) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:216) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:216) at com.sun.faces.context.SessionMap.getSession(ExternalContextImpl.java:1002) at com.sun.faces.context.SessionMap.get(ExternalContextImpl.java:962) at org.jboss.seam.contexts.ServerConversationContext.get(ServerConversationContext.java:110) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:189) at org.jboss.seam.Component.getInstance(Component.java:1949) at org.jboss.seam.Component.getInstance(Component.java:1944) at org.jboss.seam.Component.getInstance(Component.java:1924) at org.jboss.seam.Component.getInstance(Component.java:1919) at org.jboss.seam.security.Identity.create(Identity.java:101) at sun.reflect.GeneratedMethodAccessor2896.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) at org.jboss.seam.Component.callComponentMethod(Component.java:2211) at org.jboss.seam.Component.callCreateMethod(Component.java:2134) at org.jboss.seam.Component.newInstance(Component.java:2094) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:209) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:141) at org.jboss.seam.servlet.SeamListener.sessionCreated(SeamListener.java:45) at org.apache.catalina.session.StandardSession.tellNew(StandardSession.java:397) at org.apache.catalina.session.StandardSession.setId(StandardSession.java:369) at org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:828) at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:291) at org.apache.catalina.connector.Request.doGetSession(Request.java:2312) at org.apache.catalina.connector.Request.getSession(Request.java:2075) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:216) at org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:545) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:216) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:216) at com.sun.faces.context.SessionMap.getSession(ExternalContextImpl.java:1002) at com.sun.faces.context.SessionMap.get(ExternalContextImpl.java:962) at org.jboss.seam.contexts.ServerConversationContext.get(ServerConversationContext.java:110) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:189) at org.jboss.seam.Component.getInstance(Component.java:1949) at org.jboss.seam.Component.getInstance(Component.java:1944) at org.jboss.seam.Component.getInstance(Component.java:1924) at org.jboss.seam.Component.getInstance(Component.java:1919) at org.jboss.seam.security.Identity.create(Identity.java:101) at sun.reflect.GeneratedMethodAccessor2896.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) at org.jboss.seam.Component.callComponentMethod(Component.java:2211) at org.jboss.seam.Component.callCreateMethod(Component.java:2134) at org.jboss.seam.Component.newInstance(Component.java:2094) This problem is partially documented here - https://jira.jboss.org/jira/browse/JBSEAM-2888, unfortunately this bugfix didn't solve the root cause of the problem. The problem is caused by the SessionMap used by ServerConversationContext. Internally the session map uses HttpServletRequest.getSession(true) to retrieve the session, which creates a new session if the one defined on the HttpServletRequest is invalid or null. Unfortunately, when the new session is created session listeners are informed before the session has been set on the HttpServletRequest. Seam is one of these session listeners and creates a new Identity on session creation, which in turn accesses the SessionMap, still before the new Session has been set on the request. This leads to an infinite recursive loop. The SessionMap used is returned by externalContext.getSessionMap(). One solution could be to implement our own SessionMap that doesn't attempt to create a new session if the current session is invalid or null, although I've no idea how this would impact on other Seam code. The problem is relatively easy to create. In our application we have a search page that can take quite a while to complete a request. If we log out of the application in another tab before the search has completed the problem arises. We are using seam 2.1.1.GA. I've looked at the source code for the latest release and it appears that the problem will still occur due to use of SessionMap. Out current workaround is to add a ThreadLocal to Identity.create that counts recursive calls. If more then two recursive calls are detected an IllegalProcessState exception is thrown. This isn't definitely isn't a permanent solution, but stops our server creating 100,000 sessions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
18
0 / 0

[JBoss JIRA] (JBSEAM-4901) Seam reference guide requires set up english locale

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4901: ------------------------------------- Summary: Seam reference guide requires set up english locale Key: JBSEAM-4901 URL: https://issues.jboss.org/browse/JBSEAM-4901 Project: Seam 2 Issue Type: Bug Components: Build Affects Versions: 2.3.0.ALPHA Environment: CZ locale Reporter: Marek Novotny [INFO] --- maven-jdocbook-plugin:2.3.5:generate (jdocbook:generate) @ seam-reference-guide --- 10 [main] INFO org.jboss.jdocbook.render.RendererImpl - Starting rendering en-US/pdf redirecting output to file [/home/mana/projects/git/seam-svn-git/Seam_2_3/seam-reference-guide/target/docbook/work/log/console-en-US-pdf.log] Error on line 4 column 17 of file:/home/mana/projects/git/seam-svn-git/Seam_2_3/seam-reference-guide/src/docbook/en-US/master.xml: Error reported by XML parser: Invalid byte 1 of 1-byte UTF-8 sequence. {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
12
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2012