April 2012 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1126) Generate-entities creates a class with the error

by Alex Narinsky (JIRA)

Generate-entities creates a class with the error ------------------------------------------------ Key: JBSEAM-1126 URL: http://jira.jboss.com/jira/browse/JBSEAM-1126 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 1.2.1.GA, 1.2.0.GA Reporter: Alex Narinsky Priority: Minor I am using generate-entities. Prior to version 1.2 this worked fine. Starting from version 1.2 one generated class contains the error - double definition of one "In" element. Please, see the text below @Name("moviesHome") public class MoviesHome extends EntityHome<Movies> { @In(create = true) ContactsHome contactsHome; @In(create = true) ProjectsHome projectsHome; @In(create = true) ContactsHome contactsHome; -- 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

11 years, 8 months

5
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4658) <s:conversationPropagation> better validation of type parameter

by Andrew Wheeler (JIRA)

<s:conversationPropagation> better validation of type parameter --------------------------------------------------------------- Key: JBSEAM-4658 URL: https://jira.jboss.org/browse/JBSEAM-4658 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR1 Environment: JBoss AS M3 Reporter: Andrew Wheeler The examples for <s:conversationPropagation> in section 7.1 of the documentation state that a nested conversation is started with type="nested". If used with a commandLink this causes handleConversationPropagation to begin a null pageflow. The result is that a NullPointerException is thrown. Section 33.1.1.5 correctly states that type should be "nest". I suggest that a check is performed on the conversationPropagation control to throw an exception if the wrong type is passed. The documentation should be corrected to be consistent. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3405) ClassCastException for Date passed in f:param

by Valerie Griffin (JIRA)

ClassCastException for Date passed in f:param --------------------------------------------- Key: JBSEAM-3405 URL: https://jira.jboss.org/jira/browse/JBSEAM-3405 Project: Seam Issue Type: Bug Affects Versions: 2.0.3.CR1 Environment: ICEfaces 1.7.1, JBOSS 4.2.2, JDK 1.6 Reporter: Valerie Griffin My seam-gen application has tables in which part of the key is a Date field. Therefore, its value is stuffed into an appropriate f:param when I click the Select s:link in the TblList.xhtml display. I get the following stack trace. If I change the code to remove the Date parameter, I do not get the stack trace. (Of course my code doesn't work without it.... I'm going to try wrapping the date in a String-based parameter with getter and setter as a workaround so I can get something working tomorrow.) Exception during request processing: Caused by javax.el.ELException with message: "java.lang.IllegalArgumentException: java.lang.ClassCastException@ccce74" javax.el.BeanELResolver.setValue(BeanELResolver.java:116) javax.el.CompositeELResolver.setValue(CompositeELResolver.java:68) com.sun.faces.el.FacesCompositeELResolver.setValue(FacesCompositeELResolver.java:93) org.jboss.el.parser.AstPropertySuffix.setValue(AstPropertySuffix.java:73) org.jboss.el.parser.AstValue.setValue(AstValue.java:84) org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) org.jboss.seam.core.Expressions$1.setValue(Expressions.java:116) org.jboss.seam.navigation.Pages.applyConvertedValidatedValuesToModel(Pages.java:796) org.jboss.seam.navigation.Pages.postRestore(Pages.java:409) org.jboss.seam.jsf.SeamPhaseListener.postRestorePage(SeamPhaseListener.java:544) org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:390) org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:192) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) com.icesoft.faces.webapp.http.core.JsfLifecycleExecutor.apply(JsfLifecycleExecutor.java:17) com.icesoft.faces.webapp.http.core.PageServer$1.respond(PageServer.java:25) com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:161) com.icesoft.faces.webapp.http.servlet.ThreadBlockingAdaptingServlet$ThreadBlockingRequestResponse.respondWith(ThreadBlockingAdaptingServlet.java:36) com.icesoft.faces.webapp.http.core.PageServer.service(PageServer.java:30) com.icesoft.faces.webapp.http.core.SingleViewServer.service(SingleViewServer.java:48) com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer$Matcher.serviceOnMatch(PathDispatcherServer.java:50) com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer.service(PathDispatcherServer.java:19) com.icesoft.faces.webapp.http.servlet.ThreadBlockingAdaptingServlet.service(ThreadBlockingAdaptingServlet.java:19) com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet.service(EnvironmentAdaptingServlet.java:29) com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:139) com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35) com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:79) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) java.lang.Thread.run(Thread.java:619) Caused by java.lang.IllegalArgumentException with message: "java.lang.ClassCastException@ccce74" sun.reflect.GeneratedMethodAccessor5704.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) javax.el.BeanELResolver.setValue(BeanELResolver.java:108) javax.el.CompositeELResolver.setValue(CompositeELResolver.java:68) com.sun.faces.el.FacesCompositeELResolver.setValue(FacesCompositeELResolver.java:93) org.jboss.el.parser.AstPropertySuffix.setValue(AstPropertySuffix.java:73) org.jboss.el.parser.AstValue.setValue(AstValue.java:84) org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) org.jboss.seam.core.Expressions$1.setValue(Expressions.java:116) org.jboss.seam.navigation.Pages.applyConvertedValidatedValuesToModel(Pages.java:796) org.jboss.seam.navigation.Pages.postRestore(Pages.java:409) org.jboss.seam.jsf.SeamPhaseListener.postRestorePage(SeamPhaseListener.java:544) org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:390) org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:192) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) com.icesoft.faces.webapp.http.core.JsfLifecycleExecutor.apply(JsfLifecycleExecutor.java:17) com.icesoft.faces.webapp.http.core.PageServer$1.respond(PageServer.java:25) com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:161) com.icesoft.faces.webapp.http.servlet.ThreadBlockingAdaptingServlet$ThreadBlockingRequestResponse.respondWith(ThreadBlockingAdaptingServlet.java:36) com.icesoft.faces.webapp.http.core.PageServer.service(PageServer.java:30) com.icesoft.faces.webapp.http.core.SingleViewServer.service(SingleViewServer.java:48) com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer$Matcher.serviceOnMatch(PathDispatcherServer.java:50) com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer.service(PathDispatcherServer.java:19) com.icesoft.faces.webapp.http.servlet.ThreadBlockingAdaptingServlet.service(ThreadBlockingAdaptingServlet.java:19) com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet.service(EnvironmentAdaptingServlet.java:29) com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:139) com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35) com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:79) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2718) JBoss AS Integration reference guide chapter

by Jay Balunas (JIRA)

JBoss AS Integration reference guide chapter -------------------------------------------- Key: JBSEAM-2718 URL: http://jira.jboss.com/jira/browse/JBSEAM-2718 Project: JBoss Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Optional Following the existing interop reference guide chapters create a JBoss integration chapter. This is optional but could be useful for differences between AS 4 and AS 5. This would also show that Seam treats the containers the same. Almost all of the examples and most of the documents already discuss this (by default) - but it still could be useful to have. Likely version: JBoss 4.2.x and JBoss 5.x -- 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

11 years, 8 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1167) hot-deploy changes broke hibernate tools integration (and possible also testng)

by Max Andersen (JIRA)

hot-deploy changes broke hibernate tools integration (and possible also testng) ------------------------------------------------------------------------------- Key: JBSEAM-1167 URL: http://jira.jboss.com/jira/browse/JBSEAM-1167 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.2.1.GA Reporter: Max Andersen Priority: Critical .classpath in seam-gen previously pointed to test-build where hibernate tools could pick up a META-INF/persistence.xml file. Now it points to build/model and is actually never used because all src output is explicitly set. Thus no proper persistence unit is defined in eclipse now. -- 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

11 years, 8 months

6
11
0 / 0

[JBoss JIRA] (JBSEAM-4889) Improvements to maven-ear-plugin configuration of seam booking 2.3

by Fred Bricon (JIRA)

Fred Bricon created JBSEAM-4889: ----------------------------------- Summary: Improvements to maven-ear-plugin configuration of seam booking 2.3 Key: JBSEAM-4889 URL: https://issues.jboss.org/browse/JBSEAM-4889 Project: Seam 2 Issue Type: Bug Affects Versions: 2.3.0.ALPHA Reporter: Fred Bricon While testing seam booking with m2e-wtp/JBT, I noticed a few things you might want to fix wrt the [maven-ear-plugin configuration|http://anonsvn.jboss.org/repos/seam/branches/community/Seam...] : - maven-ear-plugin <version>2.3.2</version> is kinda obsolete, you can bump it to 2.6 - EAR <version> is not set in <configuration>, so by default an application.xml 1.3 will be generated (and Facet 1.3 will be installed in WTP). You should set <version>5</version> - <earSourceExcludes>**/application.xml, **/jboss-app.xml</earSourceExcludes> was added when m2e-wtp was creating these files (like 2 years ago). I'd remove that now. - <generateApplicationXml>true</generateApplicationXml> is redundant (it's the default value) and can be removed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
8
0 / 0

[JBoss JIRA] (JBSEAM-4940) @CaptchaResponse throws javax.validation exception

by Andrea Martino (JIRA)

Andrea Martino created JBSEAM-4940: -------------------------------------- Summary: @CaptchaResponse throws javax.validation exception Key: JBSEAM-4940 URL: https://issues.jboss.org/browse/JBSEAM-4940 Project: Seam 2 Issue Type: Bug Components: Core, Framework Affects Versions: 2.3.0.BETA1 Environment: JBOSS 7.1 AS + JSF2 + RichFaces 4.2 Reporter: Andrea Martino When the JSF login page sets the captcha value in the "org.jboss.seam.captcha.captcha" component, a "contains Constraint annotation, but does not contain a groups parameter" exception is thrown. Create a new customized "captcha" as following: {code:title=MyCaptcha.java|borderStyle=solid} @Name("myCaptcha") public class MyCaptcha extends org.jboss.seam.captcha.Captcha { private String myResponse; @org.jboss.seam.captcha.CaptchaResponse public String getMyResponse{ return myResponse; } public void setMyResponse(String myResponse) { this.myResponse = myResponse; } } {code} Just create a JSF page and set the "myResponse" field annotated with "CaptchaResponse" in the above component: {code:xml} <h:form> <h:inputText value="#{myCaptcha.myResponse}" size="5"/> <h:commandButton action="#{myLogin.login}" value="Login" /> </h:form> {code} The above code works in Seam 2.2.x, but throws a javax.validation exception complaining about missing "group" in Seam 2.3.0.Beta1 ("contains Constraint annotation, but does not contain a groups parameter"). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
5
0 / 0

[JBoss JIRA] (JBSEAM-4883) Seam 2.3 samples show usage of ant builds

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4883: --------------------------------- Summary: Seam 2.3 samples show usage of ant builds Key: JBSEAM-4883 URL: https://issues.jboss.org/browse/JBSEAM-4883 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir Fix For: 2.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
8
0 / 0

[JBoss JIRA] (JBSEAM-4918) Cannot deploy Seam project generated in JBDS - other problems

by Tomas Remes (JIRA)

Tomas Remes created JBSEAM-4918: ----------------------------------- Summary: Cannot deploy Seam project generated in JBDS - other problems Key: JBSEAM-4918 URL: https://issues.jboss.org/browse/JBSEAM-4918 Project: Seam 2 Issue Type: Bug Affects Versions: 2.3.0.BETA1 Environment: JBDS 5.0 Beta1, Seam 2.3.0.Beta1, JBoss AS7.1.0.Final Reporter: Tomas Remes Fix For: 2.3.0.BETA2 There are some next following problems when trying to deploy Seam project war generated in JBDS. First is the war missing WEB-INF/lib/dom4j.jar, which produces java.lang.ClassNotFoundException: org.dom4j.DocumentException. Second is that there probably shouldn't be any com.sun.facelets.FaceletViewHandler configuration in faces-config.xml, because it causes java.lang.ClassNotFoundException: com.sun.facelets.FaceletViewHandler. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

6
36
0 / 0

[JBoss JIRA] (JBSEAM-4874) Support JSF 2.0 including new JSF features

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4874: --------------------------------- Summary: Support JSF 2.0 including new JSF features Key: JBSEAM-4874 URL: https://issues.jboss.org/browse/JBSEAM-4874 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir Features to support TBD. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2012