June 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3101) Blog example XML parsing error when launched in browser

by Jay Balunas (JIRA)

Blog example XML parsing error when launched in browser ------------------------------------------------------- Key: JBSEAM-3101 URL: http://jira.jboss.com/jira/browse/JBSEAM-3101 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.3.CR1 Environment: fedora 8 JDK 1.5 JBoss 4.2.2 Reporter: Jay Balunas Priority: Critical Fix For: 2.0.3.CR1 This is a critical because this may be a result of the facelets update. Could someone take a quick look and check if this is caused by the facelets update? If that is not the case it can just be a major and hold off for the GA. --------------- Example builds and deploys fine. When accessed I get this error in the browser: XML Parsing Error: not well-formed Location: http://localhost:8080/seam-blog/seam/index.xhtml Line Number 83, Column 16: </div> ---------------^ In the log the relevant line is: 10:20:05,599 WARN [UIFormattedText] Seam Text parse error: invalid value of attribute 'style' for element 'table' In the html source this is where the issue is: </p> <table style=" </div> <p> </p> I will attach -- 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, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3094) ManagedPersistenceContext throws away entityManager on sessionWillPassivate event

by Norman Richards (JIRA)

ManagedPersistenceContext throws away entityManager on sessionWillPassivate event --------------------------------------------------------------------------------- Key: JBSEAM-3094 URL: http://jira.jboss.com/jira/browse/JBSEAM-3094 Project: Seam Issue Type: Bug Reporter: Norman Richards Assigned To: Norman Richards Fix For: 2.0.3.GA, 2.1.0.BETA1 sessionWillPassivate() is called after every request when in clustered mode, so throwing away the em forces conversations entities data to be reloaded on every request. (and non-conversational ones to detach) I think we can be a bit smarter about this and preserve the em when we haven't actually failed over. -- 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, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3062) <rich:panel> <f:facet name="header">Welcome!</f:facet> DON´T APPERS

by Thomas Modeneis (JIRA)

<rich:panel> <f:facet name="header">Welcome!</f:facet> DON´T APPERS -------------------------------------------------------------------- Key: JBSEAM-3062 URL: http://jira.jboss.com/jira/browse/JBSEAM-3062 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Reporter: Thomas Modeneis IF you make a new seam-project from the begin: setup new-project and explode try run the app: localhost/app take a look to the welcome message, it dont appear blue (if you put blueSky skin) BUT, MAN BELIVE ME, if you are developing your app, and make many explodes and refresh....like magic the blue title appers again.. I Tink its a richFaces bug, but i´m try to update richFaces libs on /app/lib to these version: richfaces-ui-3.2.0.SR1 and same problem persist. I tink this probblem becomes at jboss-seam-2.0.2.GA because if you try the same process at old seam version, all appears fine. take a look at attached print screen. Thanks alots, Thomas. -- 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3048) Add id attribute to markup for JSF components in Seam examples

by Stan Silvert (JIRA)

Add id attribute to markup for JSF components in Seam examples -------------------------------------------------------------- Key: JBSEAM-3048 URL: http://jira.jboss.com/jira/browse/JBSEAM-3048 Project: Seam Issue Type: Task Components: Examples Affects Versions: 2.0.2.SP1 Reporter: Stan Silvert Assigned To: Stan Silvert Fix For: 2.0.x Adding the id attribute makes the application testable with JSFUnit and also aids debugging. Eventually, we will need to add the id's to the markup for almost all the examples. But the first ones will be those used in JBAS-5560. So at a minimum, we need this task completed for these examples before the next release of Seam: Booking DVD Store JPA example That way, as soon as the examples are published to be Maven repo, we will be ready to run the tests in the AS testsuite. -- 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, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3093) Seam on SAP Netweaver CE 7.1 official support

by Gena Batalski (JIRA)

Seam on SAP Netweaver CE 7.1 official support --------------------------------------------- Key: JBSEAM-3093 URL: http://jira.jboss.com/jira/browse/JBSEAM-3093 Project: Seam Issue Type: Feature Request Components: Platform interoperability Affects Versions: 2.1.0.GA Environment: Seam from SVN, Richfaces 3.2.x, SAP Netweaver Composition Environment 7.1 JEE Reporter: Gena Batalski Priority: Minor Since the current Seam snapshot runs on SAP Netweaver CE 7.1 JEE server, it could be interesting to have the official support of Seam on this platform. The installation hints can be found at http://www.seamframework.org/Documentation/RunningSeamBookingExampleWithS... . -- 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, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2833) Glassfish Jee5 example deployment fails with NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap

by Jay Balunas (JIRA)

Glassfish Jee5 example deployment fails with NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap --------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2833 URL: http://jira.jboss.com/jira/browse/JBSEAM-2833 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR1 Environment: Glassfish V2.1 Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.CR2 This is typically missing "concurrent.jar" however - I have seen that "jboss-archive-browsing.jar" fixes this issue as well. This was following instructions in the readme.txt in the jee5 example. [#|2008-04-02T16:19:48.569-0400|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=17;_ThreadName=Thread-25;_RequestID=c40ebac4-b942-4743-adbc-c8515f9ec122;| java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap at org.jboss.util.file.ArchiveBrowser.<clinit>(ArchiveBrowser.java:52) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:626) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:350) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) at com.sun.enterprise.server.PersistenceUnitLoaderImpl.load(PersistenceUnitLoaderImpl.java:149) at com.sun.enterprise.server.PersistenceUnitLoaderImpl.load(PersistenceUnitLoaderImpl.java:84) at com.sun.enterprise.server.AbstractLoader.loadPersistenceUnits(AbstractLoader.java:898) at com.sun.enterprise.server.ApplicationLoader.doLoad(ApplicationLoader.java:184) at com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:126) at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244) at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336) at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210) at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645) at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928) at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912) at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461) at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176) at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308) at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226) at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298) at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635) at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:744) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358) at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90) at $Proxy1.invoke(Unknown Source) at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304) at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174) at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:145) at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:537) at java.lang.Thread.run(Thread.java:595) |#] [#|2008-04-02T16:19:48.572-0400|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=Thread-25;EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap;_RequestID=c40ebac4-b942-4743-adbc-c8515f9ec122;|ADM5603:Event listener error [EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap]|#] -- 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, 7 months

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3053) Natural conversation id initialized at wrong time, leading to exceptions

by Dan Allen (JIRA)

Natural conversation id initialized at wrong time, leading to exceptions ------------------------------------------------------------------------ Key: JBSEAM-3053 URL: http://jira.jboss.com/jira/browse/JBSEAM-3053 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1, 2.0.2.SP1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.x, 2.1.0.BETA1 When there is a request to use a natural conversation, and the conversation id is not part of the request, the natural value (EL) is being resolved prior to the temporary conversation being initialized, potentially leading to exceptions. The natural value should be resolved when the conversation id provider is asked to initialize a value. -- 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, 7 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2956) seambay example throws an exception when placing a bid on the camera

by Jay Balunas (JIRA)

seambay example throws an exception when placing a bid on the camera -------------------------------------------------------------------- Key: JBSEAM-2956 URL: http://jira.jboss.com/jira/browse/JBSEAM-2956 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Attempt to bid on the camera - possibly other items as well. With or without a value for the bid. A seam error page is seen, and the exception below: 15:35:45,922 ERROR [SeamPhaseListener] swallowing exception org.jboss.seam.RequiredException: @In attribute requires non-null value: auctionDetail.entityManager at org.jboss.seam.Component.getValueToInject(Component.java:2175) at org.jboss.seam.Component.injectAttributes(Component.java:1598) at org.jboss.seam.Component.inject(Component.java:1416) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.seam.example.seambay.AuctionDetailAction_$$_javassist_7.getAuction(AuctionDetailAction_$$_javassist_7.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2089) at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1926) at org.jboss.seam.Component.getInstance(Component.java:1863) at org.jboss.seam.Component.getInstance(Component.java:1840) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.parser.AstValue.getValue(AstValue.java:63) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:111) at org.jboss.seam.navigation.ELConversationIdParameter.getParameterValue(ELConversationIdParameter.java:68) at org.jboss.seam.navigation.ELConversationIdParameter.getConversationId(ELConversationIdParameter.java:63) at org.jboss.seam.core.ConversationPropagation.restoreNaturalConversationId(ConversationPropagation.java:123) at org.jboss.seam.core.ConversationPropagation.restoreConversationId(ConversationPropagation.java:56) at org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:387) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) 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.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.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:406) 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.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) 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.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.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.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:595) -- 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, 7 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3090) web XSD incorrectly declares servlet-session element

by Dan Allen (JIRA)

web XSD incorrectly declares servlet-session element ---------------------------------------------------- Key: JBSEAM-3090 URL: http://jira.jboss.com/jira/browse/JBSEAM-3090 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1, 2.0.2.SP1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.3.CR1, 2.1.0.BETA1 The XSD for the web comonent namespace incorrectly declares the component servlet-session, when it should be session. The element maps to the org.jboss.seam.web.Session class with component name org.jboss.seam.web.session. Chapter 13 (security) of the reference documentation is even more off base by getting both the namespace and the component name wrong, suggesting that it is <core:servlet-session invalidate-on-scheme-change="true"/> -- 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, 7 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3072) seam dist /extras directory is not there - no mail-ra.rar

by Jay Balunas (JIRA)

seam dist /extras directory is not there - no mail-ra.rar --------------------------------------------------------- Key: JBSEAM-3072 URL: http://jira.jboss.com/jira/browse/JBSEAM-3072 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.0.2.SP1 Reporter: Jay Balunas Priority: Critical Fix For: 2.0.3.CR1 In the docs it talks about the mail-ra.rar being in the "/extras" directory in the dist. The "/extras" directory is not in the dist. See the forum entry for more info. -- 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, 7 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2008