October 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3211) Serialization of transient fields on converstion scoped components in clustered enviroment

by Tomaz Cerar (JIRA)

Serialization of transient fields on converstion scoped components in clustered enviroment ------------------------------------------------------------------------------------------ Key: JBSEAM-3211 URL: https://jira.jboss.org/jira/browse/JBSEAM-3211 Project: Seam Issue Type: Bug Components: Core, EJB3 Affects Versions: 2.0.3.CR1 Environment: jboss 4.2.2.GA java 6 x64 windows vista 64bit Reporter: Tomaz Cerar I was debuging one of problems that has shown up on our tests when running in cluster. After adding some debuging code to jbossweb I have finally tracked it down and I am almost 100% sure it is a bug in Seam. here is scenario: I have SFSB that runs in Conversation scope and I have injected lots of various components. and some of those components aren't serializable, so I marked them transient so I wouldnt get any exceptions while serialization. But when I run this code with <distributable /> enabled I allways get exception Non Serializable attribute. But if serialization is done manualy(just to try) everything goes trough fine. I have modifed jbossweb so I got better exception reporting for this scenarios(as naming which parameter), as I found out that seam is trying to put also my transient field in session scope for needs of conversation: error message I got was: {noformat} 12:32:51,903 ERROR [SeamPhaseListener] [] uncaught exception java.lang.IllegalArgumentException: attribute: 'org.jboss.seam.CONVERSATION#12$podporaProdaji' of value: 'si.banka_koper.ws.ppbackend.PodporaProdajiCaching@5092eb76' is not serializable! at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1293) at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1254) at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:130) at com.sun.faces.context.SessionMap.put(ExternalContextImpl.java:972) at org.jboss.seam.contexts.ServerConversationContext.flush(ServerConversationContext.java:298) at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:371) at org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:112) at org.jboss.seam.jsf.SeamPhaseListener.afterRenderResponse(SeamPhaseListener.java:513) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:245) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:192) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.parsek.debug.TimingFilter.doFilter(TimingFilter.java:42) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:42) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:260) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:366) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:493) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:674) {noformat} as I understand seam trys to put everything that is in converstion scope in session event even it is not marked with @Out or marked transient. the compononent is marked only with @In and in that case I don't see why seam sould put it in session as it can be injected anytime... sample code: {code} Scope(ScopeType.CONVERSATION) @Local @Stateful public class DepozitWizardAction implements DepozitWizard, Serializable { private transient static final Logger log = Logger.getLogger(DepozitWizardAction.class); @In private transient PodporaProdaji podporaProdaji; public void someMethod(){ podporaProdaji.callSomeMethod(); } } {code} -- 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

17 years, 2 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3575) Excessive logging from Initialization class for every ajax request

by Jay Balunas (JIRA)

Excessive logging from Initialization class for every ajax request ------------------------------------------------------------------ Key: JBSEAM-3575 URL: https://jira.jboss.org/jira/browse/JBSEAM-3575 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.CR1 Reporter: Jay Balunas Assignee: Pete Muir Fix For: 2.1.1.CR1 Changes to Initialization.java for JBSEAM-3491 included changes to logging that creates the logging below. This shows multiple times for each request. This should probably be changed to debug. 14:51:54,551 INFO [Initialization] Installing components... 14:51:54,551 INFO [Initialization] done redeploying 14:51:55,293 INFO [Initialization] redeploying 14:51:55,293 INFO [Initialization] Installing components... 14:51:55,293 INFO [Initialization] done redeploying 14:51:56,436 INFO [Initialization] redeploying 14:51:56,437 INFO [Initialization] Installing components... 14:51:56,437 INFO [Initialization] done redeploying 14:52:00,206 INFO [Initialization] redeploying 14:52:00,206 INFO [Initialization] Installing components... 14:52:00,206 INFO [Initialization] done redeploying 14:52:01,369 INFO [Initialization] redeploying 14:52:01,369 INFO [Initialization] Installing components... 14:52:01,369 INFO [Initialization] done redeploying 14:52:01,675 INFO [Initialization] redeploying 14:52:01,675 INFO [Initialization] Installing components... 14:52:01,675 INFO [Initialization] done redeploying 14:52:01,942 INFO [Initialization] redeploying 14:52:01,942 INFO [Initialization] Installing components... 14:52:01,943 INFO [Initialization] done redeploying 14:52:02,742 INFO [Initialization] redeploying 14:52:02,742 INFO [Initialization] Installing components... 14:52:02,742 INFO [Initialization] done redeploying -- 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

17 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3574) excel package missing in root.pom

by Daniel Roth (JIRA)

excel package missing in root.pom --------------------------------- Key: JBSEAM-3574 URL: https://jira.jboss.org/jira/browse/JBSEAM-3574 Project: Seam Issue Type: Bug Components: Excel Affects Versions: 2.1.0.CR1 Reporter: Daniel Roth Assignee: Daniel Roth Priority: Critical Fix For: 2.1.0.GA -- 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

17 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3573) Seam wicket example - IllegalStateException on deploy

by Jozef Hartinger (JIRA)

Seam wicket example - IllegalStateException on deploy ----------------------------------------------------- Key: JBSEAM-3573 URL: https://jira.jboss.org/jira/browse/JBSEAM-3573 Project: Seam Issue Type: Bug Components: Examples, Wicket Affects Versions: 2.1.0.GA Environment: JDK 5 JBoss AS 4.2.3 Reporter: Jozef Hartinger Attachments: wicket-deploy.txt Example does not deploy due to IllegalStateException: @Restrict on a Wicket component must specify an expression -- 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

17 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3256) Chase up a sane logging API for JExcelAPI

by Pete Muir (JIRA)

Chase up a sane logging API for JExcelAPI ----------------------------------------- Key: JBSEAM-3256 URL: https://jira.jboss.org/jira/browse/JBSEAM-3256 Project: Seam Issue Type: Task Components: Excel Reporter: Pete Muir Assignee: Nicklas Karlsson -- 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

17 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3539) Update Seam 2.1 reference with websphere shared library settings for JSF

by Jay Balunas (JIRA)

Update Seam 2.1 reference with websphere shared library settings for JSF ------------------------------------------------------------------------ Key: JBSEAM-3539 URL: https://jira.jboss.org/jira/browse/JBSEAM-3539 Project: Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1 Reporter: Jay Balunas Assignee: Marek Novotny Fix For: 2.1.0.GA A user reported that setting up a shared library for JSF solved one of the issue with Seam 2.1 - see forum post for details. -- 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

17 years, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3561) seam-icefaces example hanging with message "Conversation has timed out or expired"

by judy guglielmin (JIRA)

seam-icefaces example hanging with message "Conversation has timed out or expired" ---------------------------------------------------------------------------------- Key: JBSEAM-3561 URL: https://jira.jboss.org/jira/browse/JBSEAM-3561 Project: Seam Issue Type: Bug Components: ICE Faces Integration Environment: ICEfaces-1.7.2 Seam trunk, jboss-4.2.3.GA Reporter: judy guglielmin Assignee: judy guglielmin Priority: Blocker Fix For: 2.1.0.GA When multiple tabs are opened, any further action performed on them (link or button) results in the above-mentioned message and the application hangs. -- 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

17 years, 3 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2961) Because of seam-gen lib changes hsqldb.jar is not where it used to be - search for reference that might need changes

by Jay Balunas (JIRA)

Because of seam-gen lib changes hsqldb.jar is not where it used to be - search for reference that might need changes -------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2961 URL: http://jira.jboss.com/jira/browse/JBSEAM-2961 Project: Seam Issue Type: Task Components: Build Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor There was some places that referred to the hsqldb.jar in the seam-gen/lib directory. Search svn for references and just verify that the calls or references are still correct. Most likely would be in the reference docs, or in seam-gen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3569) Clarify docs on depends= for facesContext

by Samuel Mendenhall (JIRA)

Clarify docs on depends= for facesContext ----------------------------------------- Key: JBSEAM-3569 URL: https://jira.jboss.org/jira/browse/JBSEAM-3569 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.CR1, 2.0.3.CR1 Reporter: Samuel Mendenhall Priority: Minor The following example results in a null FacesContext: @Startup(depends = "org.jboss.seam.faces.facesContext") @Scope(ScopeType.APPLICATION) @Name("SomeBean") public class SomeBean { @Logger private Log log; @Create public void init() { FacesContext facesContext = FacesContext.getCurrentInstance(); log.info("FacesContext: " + facesContext); } } The docs are misleading in the sense that it promotes the idea that depends = "org.jboss.seam.faces.facesContext" means this bean will have access to the facesContext if it depends on it. This is not true as there isn't a guarantee at this point that the underlying JSF implementation is started. This may affect more than just the depends on facesContext, it would be nice to have a general guideline detailed on what and what can not be relied on. -- 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

17 years, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3567) Seam welcome message incorrect on AS5

by Jozef Hartinger (JIRA)

Seam welcome message incorrect on AS5 ------------------------------------- Key: JBSEAM-3567 URL: https://jira.jboss.org/jira/browse/JBSEAM-3567 Project: Seam Issue Type: Bug Affects Versions: 2.0.3.CR1 Environment: JBoss AS 5.0.0.CR2 Reporter: Jozef Hartinger Priority: Minor I am getting "Welcome to Seam null" or even "Welcome to Seam 5.0.0.CR2" message in log when deploying Seam examples or seam-gen-erated project on AS 5 -- 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

17 years, 3 months

1
1
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 October 2008