February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-619) Make the booking work on WAS EJB3 Preview

by Michael Yuan (JIRA)

Make the booking work on WAS EJB3 Preview ----------------------------------------- Key: JBSEAM-619 URL: http://jira.jboss.com/jira/browse/JBSEAM-619 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.0.GA Reporter: Michael Yuan Assigned To: Michael Yuan Priority: Minor IBM EJB3 implementation: https://www14.software.ibm.com/iwm/web/cc/earlyprograms/websphere/was61ejb3/ -- 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, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-620) Make the booking work on WLS 10.0 Preview

by Michael Yuan (JIRA)

Make the booking work on WLS 10.0 Preview ----------------------------------------- Key: JBSEAM-620 URL: http://jira.jboss.com/jira/browse/JBSEAM-620 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.0.GA Reporter: Michael Yuan Priority: Minor WebLogic 10.0 -- 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, 10 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-546) seam-gen should be runnable from outside of the seam dir

by Norman Richards (JIRA)

seam-gen should be runnable from outside of the seam dir -------------------------------------------------------- Key: JBSEAM-546 URL: http://jira.jboss.com/jira/browse/JBSEAM-546 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Norman Richards the seam script can only be run from within the seam install directory. It should be runnable from anywhere. I suggest adding the following, mostly stolen from the JBoss run.sh script: DIRNAME=`dirname $0` if [ "x$SEAM_HOME" = "x" ]; then # get the full path (without any relative bits) SEAM_HOME=`cd $DIRNAME; pwd` fi cd $SEAM_HOME/seam-gen This would allow the application to be run from anywhere, and also gives the user the ability to specify SEAM_HOME if they want to. I'm sure run.bat shows how to best accomplish this for non-UNIX people. -- 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, 10 months

3
3
0 / 0

[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, 10 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2692) Overriding security messages

by Jens Weintraut (JIRA)

Overriding security messages ---------------------------- Key: JBSEAM-2692 URL: http://jira.jboss.com/jira/browse/JBSEAM-2692 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.1.GA Environment: WinXP SP2, JBoss AS 4.2.2, ICEfaces 1.7.0 Beta1 Reporter: Jens Weintraut Fix For: 2.0.2.GA Overrinding security messages (e. g. "org.jboss.seam.loginSuccessful") doesn't work. -- 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, 10 months

2
6
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, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2642) components.xml circular references

by Tomas Cerny (JIRA)

components.xml circular references ---------------------------------- Key: JBSEAM-2642 URL: http://jira.jboss.com/jira/browse/JBSEAM-2642 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Environment: Linux Gentoo, quad core intel Q6600, 3 Screens ;D. JBoss AS 4.2.2 Reporter: Tomas Cerny Priority: Minor Fix For: 2.1.x components.xml Code: <component name="userSecurityService" class="edu.my.service.export.impl.userSecurityServiceImpl" scope="application"> <property name="serviceLocator">#{serviceLocator}</property> </component> <component name="serviceLocator" class="edu.my.service.ServiceLocator" scope="application"> <property name="userSecurityService">#{userSecurityService}</property> </component> I am receiving stack overflow on container when hit the server. Spring can handle this. -- 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, 10 months

2
1
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, 10 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, 10 months

3
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008