May 2012 - seam-issues - Jboss List Archives

[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

12 years, 3 months

6
11
0 / 0

[JBoss JIRA] (JBSEAM-4975) Seam-gen generated project entityManager problem

by Tomas Remes (JIRA)

Tomas Remes created JBSEAM-4975: ----------------------------------- Summary: Seam-gen generated project entityManager problem Key: JBSEAM-4975 URL: https://issues.jboss.org/browse/JBSEAM-4975 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.CR1 Reporter: Tomas Remes When you generate Seam project in Seam-gen, it will create build.xml inside your new project. In this build.xml file there is handled "puJndiName" variable, which is then referenced in components.xml. The problem is that this variable is not set properly, because it depends on value of variable "seamBootstrapsPu" and this variable is assigned based on availability of ${jboss.home}/lib/jboss-vfs.jar file, which does not exist in AS7. So the problem is this line (69) in build.xml: {noformat} <available file="${jboss.home}/lib/jboss-vfs.jar"/> {noformat} When the entityManager could'nt be found, following exception occurs: {noformat} Caused by: javax.naming.NameNotFoundException: entityManager -- service jboss.naming.context.java.entityManager at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:119) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:257) {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, 3 months

2
6
0 / 0

[JBoss JIRA] (JBSEAM-4960) seam-gen project classpath not updated

by Tomas Remes (JIRA)

Tomas Remes created JBSEAM-4960: ----------------------------------- Summary: seam-gen project classpath not updated Key: JBSEAM-4960 URL: https://issues.jboss.org/browse/JBSEAM-4960 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.BETA2 Reporter: Tomas Remes Fix For: 2.3.0.CR1 Project generated by seam-gen does not have updated classpath entries thus there are following errors after importing project to JBDS/JBT: {noformat} Project 'myproject' is missing required library: 'bootstrap' Project 'myproject' is missing required library: 'lib/core.jar' Project 'myproject' is missing required library: 'lib/ejb-api.jar' Project 'myproject' is missing required library: 'lib/hibernate-annotations.jar' Project 'myproject' is missing required library: 'lib/hibernate-search.jar' Project 'myproject' is missing required library: 'lib/janino.jar' Project 'myproject' is missing required library: 'lib/jboss-embedded-api.jar' Project 'myproject' is missing required library: 'lib/jsf-api.jar' Project 'myproject' is missing required library: 'lib/jsf-facelets.jar' Project 'myproject' is missing required library: 'lib/persistence-api.jar' Project 'myproject' is missing required library: 'lib/richfaces-api.jar' {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, 3 months

6
47
0 / 0

[JBoss JIRA] (JBSEAM-4977) Metawidget examples broken, metawidget annotations ignored

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4977: ------------------------------------- Summary: Metawidget examples broken, metawidget annotations ignored Key: JBSEAM-4977 URL: https://issues.jboss.org/browse/JBSEAM-4977 Project: Seam 2 Issue Type: Bug Components: Examples Affects Versions: 2.3.0.BETA2 Environment: AS 7.1.2 Reporter: Marek Schmidt Fix For: 2.3.0.CR1 Metawidget booking example is broken. The Book Hotel page (book.seam view) looks as if the metawidget annotations were ignored (e.g. hidden fields are displayed, smoking is a checkbox instead of a radio button, etc.) -- 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, 3 months

4
6
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

12 years, 3 months

2
8
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, 3 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, 3 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, 3 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, 3 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, 3 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2012