December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1659) MapDataModel implements Serializable but isn't

by Pete Muir (JIRA)

MapDataModel implements Serializable but isn't ---------------------------------------------- Key: JBSEAM-1659 URL: http://jira.jboss.com/jira/browse/JBSEAM-1659 Project: JBoss Seam Issue Type: Bug Components: Core, JSF Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir See org.jboss.seam.test.DataModelTest.testMapDataModel() -- 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

16 years, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1660) MapDataModel and SetDataModel should allow passing null to setWrappedData

by Pete Muir (JIRA)

MapDataModel and SetDataModel should allow passing null to setWrappedData ------------------------------------------------------------------------- Key: JBSEAM-1660 URL: http://jira.jboss.com/jira/browse/JBSEAM-1660 Project: JBoss Seam Issue Type: Bug Reporter: Pete Muir see org.jboss.seam.test.DataModelTest.testMapDataModel() and org.jboss.seam.test.DataModelTest.testSetDataModel(). This is allowed by the spec. -- 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

16 years, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2379) Hot deployment issues: multiple events fired, old classes don't get GC'd, hotdeploy not atomic

by Allon Rauer (JIRA)

Hot deployment issues: multiple events fired, old classes don't get GC'd, hotdeploy not atomic ---------------------------------------------------------------------------------------------- Key: JBSEAM-2379 URL: http://jira.jboss.com/jira/browse/JBSEAM-2379 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Allon Rauer I love the hot-deploy feature, and i'm even considering using it in production to be able to change and add code without bringing down out services. However, there are several big issues with it currently: 1. Observer methods are tracked by the Init component, but never get cleared upon re-deploy. This leads to invocation of the event listeners in both the old components and the "replacement" hot-deployed components. It also leads to leaking of class objects, as the old Method/Class references don't get released upon re-deploy, eventually leading to a perm-gen out-of-mem. 2. Hot-deploy isn't atomic. If a request comes in concurrent w/ the redeploy, that request may see a mix of old components and re-deployed components, possibly leading to erroneous behavior. -- 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

16 years, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2359) ArrayIndexOutOfBoundsException in org.jboss.seam.contexts.BasicContext.getNames()

by Przemyslaw Jaskierski (JIRA)

ArrayIndexOutOfBoundsException in org.jboss.seam.contexts.BasicContext.getNames() --------------------------------------------------------------------------------- Key: JBSEAM-2359 URL: http://jira.jboss.com/jira/browse/JBSEAM-2359 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Tomcat 6.0.13, Seam CVS 2007-12-07 Reporter: Przemyslaw Jaskierski Priority: Critical Fix For: 2.0.1.GA Load tests. 20 JMeter http threads create session for every iteration on a bunch of pages. Session timeout set to 5 minutes. After 2 minutes I get this: Dec 8, 2007 1:04:48 AM org.apache.catalina.session.StandardSession tellNew SEVERE: Session event listener threw exception java.lang.ArrayIndexOutOfBoundsException: 180 at org.jboss.seam.contexts.BasicContext.getNames(BasicContext.java:60) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:270) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:187) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:124) at org.jboss.seam.servlet.SeamListener.sessionCreated(SeamListener.java:44) 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:829) 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 com.sun.faces.context.SessionMap.getSession(ExternalContextImpl.java:1002) at com.sun.faces.context.SessionMap.get(ExternalContextImpl.java:962) at org.jboss.seam.contexts.BasicContext.get(BasicContext.java:48) at org.jboss.seam.Component.getInstance(Component.java:1851) at org.jboss.seam.Component.getInstance(Component.java:1829) at org.jboss.seam.web.Session.getInstance(Session.java:122) at org.jboss.seam.contexts.FacesLifecycle.beginRequest(FacesLifecycle.java:54) at org.jboss.seam.jsf.SeamPhaseListener.beforeRestoreView(SeamPhaseListener.java:368) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:139) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 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.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 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.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) 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.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292) at org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:183) at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:125) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:107) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:78) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:383) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at net.sf.ehcache.constructs.web.filter.GzipFilter.doFilter(GzipFilter.java:75) at net.sf.ehcache.constructs.web.filter.Filter.doFilter(Filter.java:92) 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.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- 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

16 years, 8 months

5
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2086) ConcurrentModificationException in wildcardViewIds

by Pete Muir (JIRA)

ConcurrentModificationException in wildcardViewIds -------------------------------------------------- Key: JBSEAM-2086 URL: http://jira.jboss.com/jira/browse/JBSEAM-2086 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Pete Muir -- 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

16 years, 8 months

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2234) Documentation for "Integration Testing with Mock Data" is incomplete

by Eduardo Nieto (JIRA)

Documentation for "Integration Testing with Mock Data" is incomplete -------------------------------------------------------------------- Key: JBSEAM-2234 URL: http://jira.jboss.com/jira/browse/JBSEAM-2234 Project: JBoss Seam Issue Type: Release Components: Documentation Affects Versions: 2.0.0.GA Environment: Jboss SEAM 2.0.0.GA Project generated using seam-gen TestNg eclipse plugin PostgreSQL 8.1 Reporter: Eduardo Nieto I wanted to do a very simple test using the instructions in this chapter of the Reference Documentation: "31.3.1. Integration Testing with Mock Data" (http://docs.jboss.com/seam/2.0.0.GA/reference/en/html/testing.html#d0e19428) and I found two problems with the documentation: #1 Datasource value: Most users wouldn't know that TestNG plugin is going to look for datasources in the bootstrap/deploy directory. This should be explained and also that the "java:/DefaultDS" has no relation to the database used to generate the project. #2 Using DBMS that are not Hypersonic Tests using other DBMS should override three methods (disableReferentialIntegrity, enableReferentialIntegrity and editConfig). I've found this commented on the source of the class "DbUnitSeamTest" and this MUST be documented on the Reference Documentation -- 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

16 years, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1887) Session timeout results in javax.faces.application.ViewExpiredException

by Jacob Orshalick (JIRA)

Session timeout results in javax.faces.application.ViewExpiredException ----------------------------------------------------------------------- Key: JBSEAM-1887 URL: http://jira.jboss.com/jira/browse/JBSEAM-1887 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Jacob Orshalick If the session times out, JSF throws a ViewExpiredException during the RESTORE_VIEW phase. The issue is described in more detail at the JBoss Form Reference. An example can be provided if required. -- 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

16 years, 8 months

4
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1567) Complete documentation for seam-ui

by Pete Muir (JIRA)

Complete documentation for seam-ui ---------------------------------- Key: JBSEAM-1567 URL: http://jira.jboss.com/jira/browse/JBSEAM-1567 Project: JBoss Seam Issue Type: Task Components: JSF Reporter: Pete Muir Many of the attributes on seam ui controls have descriptions, not all. As JBossTools is now in play, this is more important, as they are actually displayed in the IDE ootb! -- 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

16 years, 8 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2230) Allow Seam to work with the WebLogic JAAS server authentication without any source code modifications

by Krasimir Chobantonov (JIRA)

Allow Seam to work with the WebLogic JAAS server authentication without any source code modifications ----------------------------------------------------------------------------------------------------- Key: JBSEAM-2230 URL: http://jira.jboss.com/jira/browse/JBSEAM-2230 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Environment: BEA WebLogic Server v. 10 MP1 (The issue should be observable from version 8 and up) Reporter: Krasimir Chobantonov Priority: Optional When using JBoss Identity for server delegated security authentication using the jaas-config-name attribute in security:identity XML element inside JBoss SEAM components.xml file and deploying that on BEA WebLogic Server then the authentication is always failing if the default WebLogic JAAS module is used. Follows the WebLogic server JAAS configuration file content : myrealm { weblogic.security.auth.login.UsernamePasswordLoginModule required authOnLogin="true" debug="false"; }; The problem is that the WebLogic server passes JAAS callback weblogic.security.auth.callback.URLCallback on which Seam throws an UnsupportedCallbackException class exception. To make this functionality to work you have to either 1) create custom JAAS module for WebLogic server 2) Extend org.jboss.seam.security.Identity and org.jboss.seam.security.RuleBasedIdentity classes to override protected CallbackHandler getDefaultCallbackHandler() method and include a new else branch before the default that throws UnsupportedCallbackException } else if (callbacks[i].getClass().getName().equals ("weblogic.security.auth.callback.URLCallback")) { // deliberately ignored. } 3) Include the code in 2 inside the JBoss Seam Identity class - not having the User to debug why it is not working and then to create a new class to extend that in order to make it workable In my opinion performing 3 will be the easier from User's point of view and will allow Seam to use WebLogic JAAS server authentication without any coding from JBoss Seam User point of view. Note that the proposed code doesn't depend on any BEA WebLogic specific classes. -- 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

16 years, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1997) ConversationList not refreshed when beginning a long-running conversation

by Jacob Orshalick (JIRA)

ConversationList not refreshed when beginning a long-running conversation ------------------------------------------------------------------------- Key: JBSEAM-1997 URL: http://jira.jboss.com/jira/browse/JBSEAM-1997 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Reporter: Jacob Orshalick If an action executes with an @Begin and returns the user to the same page, the conversationList is not updated with the new ConversationEntry. It appears that the problem is the current implementation of conversationList is a factory method scoped to the PAGE. A patch that works is to make the ConversationList a manager component rather than a factory method. I will attach the patch. Please see the forum reference for more information. -- 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

16 years, 8 months

2
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007