July 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-4985) seamdiscs example, The class 'org.jboss.seam.example.seamdiscs.model.Artist' does not have the property 'bandMembers'."

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4985: ------------------------------------- Summary: seamdiscs example, The class 'org.jboss.seam.example.seamdiscs.model.Artist' does not have the property 'bandMembers'." Key: JBSEAM-4985 URL: https://issues.jboss.org/browse/JBSEAM-4985 Project: Seam 2 Issue Type: Bug Components: Examples Affects Versions: 2.3.0.BETA2 Environment: JBoss AS 7.1.2.Final Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.0.CR1 Clicking on Bob Dylan shows an error page: "The class 'org.jboss.seam.example.seamdiscs.model.Artist' does not have the property 'bandMembers'." -- 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

12 years, 5 months

3
5
0 / 0

[JBoss JIRA] (JBSEAM-4954) Incorrect documentation for Remoting

by David Miller (JIRA)

David Miller created JBSEAM-4954: ------------------------------------ Summary: Incorrect documentation for Remoting Key: JBSEAM-4954 URL: https://issues.jboss.org/browse/JBSEAM-4954 Project: Seam 2 Issue Type: Task Components: Documentation Issues Affects Versions: 2.2.2.Final Reporter: David Miller Priority: Minor In the remoting section of the seam documentation (Chapter 25. Remoting, http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html_single/#remoting) the @WebRemote annotation should be in the HelloAction class, not the interface HelloLocal(http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html_si.... I can only get @WebRemote to work if it's in the class. -- 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

12 years, 5 months

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

12 years, 5 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

12 years, 5 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

12 years, 5 months

6
36
0 / 0

[JBoss JIRA] (JBSEAM-4959) Seam gen needs to use different default JDBC driver than HSQLDB

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4959: ------------------------------------- Summary: Seam gen needs to use different default JDBC driver than HSQLDB Key: JBSEAM-4959 URL: https://issues.jboss.org/browse/JBSEAM-4959 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.BETA2 Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.CR1 Seam-gen uses as default JDBC Driver HSQLDB 1.8.x. That is problematic in usage with AS 7.1.x. We should provide as default JDBC driver H2 or other JDBC 4 compliant driver. -- 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

12 years, 5 months

2
5
0 / 0

[JBoss JIRA] (JBSEAM-4997) Deadlock with components using factories of each other

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4997: ------------------------------------- Summary: Deadlock with components using factories of each other Key: JBSEAM-4997 URL: https://issues.jboss.org/browse/JBSEAM-4997 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.3.0.BETA2 Environment: Seam 2.3.0.CR1-SNAPSHOT r14979, AS 7.1.2.Final Reporter: Marek Schmidt Assignee: Marek Novotny The patch in JBSEAM-4861 introduced a potential deadlock with components using each other factories, such as in the following sample: {code} @Scope(ScopeType.APPLICATION) @Name("factoryLock.knitFactory") public static class KnitFactory { @Factory(value="factoryLock.knitPurl", scope=ScopeType.SESSION) public String getDoubleKnit() { return "knit(" + (String)Component.getInstance("factoryLock.purl") + ")"; } @Factory(value="factoryLock.knit", scope=ScopeType.SESSION) public String getKnit() { return "knit"; } } @Scope(ScopeType.APPLICATION) @Name("factoryLock.purlFactory") public static class PurlFactory { @Factory(value="factoryLock.purlKnit", scope=ScopeType.SESSION) public String getDoublePurl() { return "purl(" + (String)Component.getInstance("factoryLock.knit") + ")"; } @Factory(value="factoryLock.purl", scope=ScopeType.SESSION) public String getPurl() { return "purl"; } } {code} this may cause a deadlock if two different requests in the same session ask for #{factoryLock.knitPurl} and #{factoryLock.purlKnit} respectively. The problem is that different threads may lock the components in different order. -- 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

12 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBSEAM-4983) Migrate seamdiscs testsuite

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4983: ------------------------------------- Summary: Migrate seamdiscs testsuite Key: JBSEAM-4983 URL: https://issues.jboss.org/browse/JBSEAM-4983 Project: Seam 2 Issue Type: Task Components: Examples Affects Versions: 2.3.0.BETA2 Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: 2.3.0.CR1 The seamdiscs integration tests are to be migrated to arq/junit/seamtest -- 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

12 years, 5 months

2
2
0 / 0

[JBoss JIRA] (JBSEAM-4970) jboss-seam-ui has non-optional compile-scoped dependency on richfaces artifacts

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4970: ------------------------------------- Summary: jboss-seam-ui has non-optional compile-scoped dependency on richfaces artifacts Key: JBSEAM-4970 URL: https://issues.jboss.org/browse/JBSEAM-4970 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.3.0.BETA2 Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.0.CR1 jboss-seam-ui has non-optional compile-scoped dependency on richfaces-core-impl, richfaces-components-api, richfaces-components-ui. -- 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

12 years, 5 months

2
2
0 / 0

[JBoss JIRA] (JBSEAM-4967) seam-messages fails with "The absolute uri: http://jboss.com/products/seam/taglib cannot be resolved in either web.xml or the jar files deployed with this application"

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4967: ------------------------------------- Summary: seam-messages fails with "The absolute uri: http://jboss.com/products/seam/taglib cannot be resolved in either web.xml or the jar files deployed with this application" Key: JBSEAM-4967 URL: https://issues.jboss.org/browse/JBSEAM-4967 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.3.0.BETA2 Environment: AS 7.1.2.Final Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.0.CR1 seam-messages fails with {noformat} org.apache.jasper.JasperException: The absolute uri: http://jboss.com/products/seam/taglib cannot be resolved in either web.xml or the jar files deployed with this application org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116) org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:239) org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:152) org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:386) org.apache.jasper.compiler.Parser.parseDirective(Parser.java:448) org.apache.jasper.compiler.Parser.parseElements(Parser.java:1398) org.apache.jasper.compiler.Parser.parse(Parser.java:130) org.apache.jasper.compiler.ParserController.doParse(ParserController.java:255) org.apache.jasper.compiler.ParserController.parse(ParserController.java:103) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:194) org.apache.jasper.compiler.Compiler.compile(Compiler.java:360) org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:607) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:546) javax.faces.context.ExternalContextWrapper.dispatch(ExternalContextWrapper.java:93) com.sun.faces.application.view.JspViewHandlingStrategy.executePageToBuildView(JspViewHandlingStrategy.java:364) com.sun.faces.application.view.JspViewHandlingStrategy.buildView(JspViewHandlingStrategy.java:154) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:100) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) {noformat} -- 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

12 years, 5 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2012