March 2008 - seam-issues - Jboss List Archives

[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

18 years

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

18 years

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

18 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2731) Wiki search engine returns protected document content

by Christian Bauer (JIRA)

Wiki search engine returns protected document content ----------------------------------------------------- Key: JBSEAM-2731 URL: http://jira.jboss.com/jira/browse/JBSEAM-2731 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Blocker Apparently either the indexing of read access levels or the now deprecated Lucene QueryFilter are buggy. -- 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

18 years

1
2
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

18 years

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

18 years

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2743) Compilation fails during Seam generate-entities when model class name matches session ejb name.

by David Cloutier (JIRA)

Compilation fails during Seam generate-entities when model class name matches session ejb name. ----------------------------------------------------------------------------------------------- Key: JBSEAM-2743 URL: http://jira.jboss.com/jira/browse/JBSEAM-2743 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.0.A1, 2.0.1.GA Environment: win xp, jboss as 4 Reporter: David Cloutier If I have two tables TABLE_ONE and TABLE_ONE_LIST saem-gen creates two model classes TableOne and TableOneList and also creates four session ejb classes, two of which are called: TableOneList and TableOneListList. The session ejb TableOneList and the model class TableOneList conflict as the package names are not qualified in the source. -- 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

18 years

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2742) SEAM genereate-entities fails during the model compilation when legacy table name is "ENTITY" .

by David Cloutier (JIRA)

SEAM genereate-entities fails during the model compilation when legacy table name is "ENTITY" . ----------------------------------------------------------------------------------------------- Key: JBSEAM-2742 URL: http://jira.jboss.com/jira/browse/JBSEAM-2742 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.0.A1, 2.0.1.GA Environment: Windows XP. JBoss 4 AS, Java 1.6 Reporter: David Cloutier When running seam generate-entities on a legacy Oracle database with a table named "ENTITY" the generate-entities fails during the compilation step because of the ambiguity between Hibernates Entity annotation and the "Entity" model created by 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

18 years

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2621) debug page missing url-encoding for component viewing

by Nicklas Karlsson (JIRA)

debug page missing url-encoding for component viewing ----------------------------------------------------- Key: JBSEAM-2621 URL: http://jira.jboss.com/jira/browse/JBSEAM-2621 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Environment: JBoss 4.2.2.GA Reporter: Nicklas Karlsson If I have a component named "käyttäjä", I can see it on the debug page but clicking on the link goes to .../debug.seam?name=käyttäjä&cid=1 and the component contents is not listed. The correct form in this case should be .../debug.seam?name=k%e4ytt%e4j%e4&cid=1 -- 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

18 years

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2676) JBossSeam-2.1-sun16 testsuite build failing

by Jay Balunas (JIRA)

JBossSeam-2.1-sun16 testsuite build failing ------------------------------------------- Key: JBSEAM-2676 URL: http://jira.jboss.com/jira/browse/JBSEAM-2676 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.1.0.GA Reporter: Jay Balunas Assigned To: Pete Muir The JBossSeam-2.1-sun16 build started to fail on 2-19-08 with the following error turing the "jarui" target: java] [INFO] Parse config file /qa/services/hudson/hudson_workspace/workspace/JBossSeam-2.1-sun16/seam/ui/src/main/config/component/transformImageType.xml [java] [ERROR] Error on generate component [java] org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [java] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:509) [java] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:285) [java] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:400) [java] at org.apache.commons.digester.Digester.<init>(Digester.java:346) [java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:119) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.createConfig(GenerateMojo.java:253) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.execute(GenerateMojo.java:92) [java] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [java] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [java] Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [java] at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:420) [java] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:502) [java] ... 24 more [java] Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category [java] at java.lang.Class.getDeclaredConstructors0(Native Method) [java] at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) [java] at java.lang.Class.getConstructor0(Class.java:2699) [java] at java.lang.Class.getConstructor(Class.java:1657) [java] at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:417) [java] ... 25 more [java] [INFO] ------------------------------------------------------------------------ [java] [ERROR] BUILD ERROR [java] [INFO] ------------------------------------------------------------------------ [java] [INFO] Error in component generation -- 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

18 years

2
2
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 March 2008