September 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2348) seam generate-ui fails for @OneToOne @PrimaryKeyJoinColumn annotated fields

by Thorsten Kunz (JIRA)

seam generate-ui fails for @OneToOne @PrimaryKeyJoinColumn annotated fields --------------------------------------------------------------------------- Key: JBSEAM-2348 URL: http://jira.jboss.com/jira/browse/JBSEAM-2348 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Environment: Seam 2.0.0.GA JBoss Tools Reporter: Thorsten Kunz Since I do use JBoss Tool I assume that this is cause by an error in the underlying seam generate-ui. It fails if you have entities annotated like this: public class User implements Serializable { @Id @GeneratedValue private Long id; @OneToOne @PrimaryKeyJoinColumn private UserData userData; } public class UserData implements Serializable { @Id private Long id; @OneToOne @PrimaryKeyJoinColumn private User user; } This will result in this Exception: org.eclipse.core.runtime.CoreException: org.hibernate.tool.hbm2x.ExporterException: Error while processing template view/list.xhtml.ftl org.eclipse.core.runtime.CoreException[666]: org.hibernate.tool.hbm2x.ExporterException: Error while processing template view/list.xhtml.ftl Caused by: freemarker.core.InvalidReferenceException: Expression property.value.typeName is undefined on line 39, column 6 in view/list.xhtml.ftl -- 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

15 years, 9 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3441) For a pages.xml <exception> element the attributes of a nested <end-conversation> element are ignored

by Jacob Orshalick (JIRA)

For a pages.xml <exception> element the attributes of a nested <end-conversation> element are ignored ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3441 URL: https://jira.jboss.org/jira/browse/JBSEAM-3441 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.BETA1 Reporter: Jacob Orshalick Assignee: Jacob Orshalick Priority: Minor In testing the <end-conversation /> tag within an <exception> handler, and it seems that all conversation attributes are ignored. The pages XSD allows: before-redirect, if, and root, but they are not actually used during exception handling. This will require parsing the <end-conversation /> attributes in org.jboss.seam.exception.Exceptions and building support into the org.jboss.seam.exception.RedirectHandler hierarchy. -- 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

15 years, 9 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1943) Support for destroying the entire ConversationStack

by Jacob Orshalick (JIRA)

Support for destroying the entire ConversationStack --------------------------------------------------- Key: JBSEAM-1943 URL: http://jira.jboss.com/jira/browse/JBSEAM-1943 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Reporter: Jacob Orshalick There are situations where I would like to be able to destroy the entire conversation stack if a particular action occurs (say a user cancels everything during a nested conversation, an exception occurs during a nested conversation, etc). I am currently accomplishing this through the following: private void endRootConversation() { Conversation conversation = Conversation.instance(); while(conversation.isNested()) { conversation.root(); } conversation.endBeforeRedirect(); } I would prefer to say something like @End(root=true) or specifying conversationPropogation="endRoot". Similar discussions on the forum are: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112414&postdays=... http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118936&postdays=... -- 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

15 years, 9 months

4
26
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3088) Allow supported locales to be configured in the component descriptor

by Dan Allen (JIRA)

Allow supported locales to be configured in the component descriptor -------------------------------------------------------------------- Key: JBSEAM-3088 URL: http://jira.jboss.com/jira/browse/JBSEAM-3088 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.1.0.GA Just about the only setting that we still need to configure in faces-config.xml is the collection of supported locales. The Application class in the JSF API exposes the public method setSupportedLocales(Collection) to configure this collection. The support this feature request, a new application-scoped component will need to be created in the international package. The LocaleSelector cannot be used since it is per user session. -- 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

15 years, 9 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2947) seam-gen crud app throws exception if duplicate entry added

by Jay Balunas (JIRA)

seam-gen crud app throws exception if duplicate entry added ----------------------------------------------------------- Key: JBSEAM-2947 URL: http://jira.jboss.com/jira/browse/JBSEAM-2947 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Create a seam-gen project and reverse engineer a DB (I used the tables from the release-process.txt). Add an new entry in one of the tables then attempt to add another identical entry ( just the primary key will do it as well). You will see an exception (jsf error page) that basically says cannot add duplicate entry. Could just add a simple check instead of throwing the exception. -- 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

15 years, 9 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-2907) seam-gen should make their List classes type safe

by Dan Allen (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-2907?page=com.atlassian.jira.pl... ] Dan Allen resolved JBSEAM-2907. ------------------------------- Fix Version/s: 2.0.3.CR2 Resolution: Done Done. I also updated EntityList.java. > seam-gen should make their List classes type safe > ------------------------------------------------- > > Key: JBSEAM-2907 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2907 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Dan Allen > Fix For: 2.0.3.CR2, 2.1.0.CR1 > > > Currently seam-gen generates CustomerList extends EntityQuery > If it instead did CustomerList extends EntityQuery<Customer> then the code java and EL based completion would know its methods referred to Customer and not just Object. -- 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

15 years, 9 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3328) Imported seam-gen project into jbtools 2.1.1 has missing jstl.jar

by Jay Balunas (JIRA)

Imported seam-gen project into jbtools 2.1.1 has missing jstl.jar ----------------------------------------------------------------- Key: JBSEAM-3328 URL: https://jira.jboss.org/jira/browse/JBSEAM-3328 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Fix For: 2.1.0.BETA2 If you import a seam gen ear project following the directions in the release process the project will have the following error ""Project 'seamgenEar' is missing required library: 'lib/jstl.jar'"" This is after using the correct seam runtime, and adding seam functionality to project. the jstl.jar is not in the seamgen project and it is not in the seam 2.1.0 dist -- 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

15 years, 9 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2546) Interpolator should support escaping of #{ character combination

by Dan Allen (JIRA)

Interpolator should support escaping of #{ character combination ---------------------------------------------------------------- Key: JBSEAM-2546 URL: http://jira.jboss.com/jira/browse/JBSEAM-2546 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.CR2 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.1.0.GA Attachments: JBSEAM-2546-v1.txt There is an inconsistency between the native JSF parser and Seam's Interpolator, which is used to resolve page descriptions in the pages.xml file, amongst other places. If you need to place a # character just before the value binding expression, you must escape with with a backslash (\) according to the EL specification (i.e. \##{contextVariable}). However, the Interpolator chokes when it encounters this syntax. The Interpolator should be changed to ignore a # sign if escaped. -- 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

15 years, 9 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3404) Extended Identity component is not being loaded during Initialization process

by Luis Tama (JIRA)

Extended Identity component is not being loaded during Initialization process ----------------------------------------------------------------------------- Key: JBSEAM-3404 URL: https://jira.jboss.org/jira/browse/JBSEAM-3404 Project: Seam Issue Type: Bug Components: Core, Security Affects Versions: 2.1.0.BETA1 Environment: Seam 2.1.0-SNAPSHOT # 303 Reporter: Luis Tama I have this Extended Identity component, which lets me render different home pages according to the user roles: @Name("org.jboss.seam.security.identity") @Scope(ScopeType.SESSION) @Install(precedence = Install.APPLICATION) @BypassInterceptors @Startup public class Identity extends org.jboss.seam.security.Identity { private static final String DEFAULT_HOME_PAGE = "/home/home.xhtml"; private String homePage = DEFAULT_HOME_PAGE; // getter and setter for homePage, and business logic // and some other important properties related to my business model... } In Seam 2.1.0.BETA1, it works fine: ... 21:53:16,159 INFO [Initialization] Installing components... ... 21:53:16,921 INFO [Component] Component: org.jboss.seam.security.identity, scope: SESSION, type: JAVA_BEAN, class: org.ostion.siplacad.session.Identity ... In Seam 2.1.0-SNAPSHOT # 303, it's not being loaded: ... 21:55:54,125 INFO [Initialization] Installing components... ... 21:55:55,500 INFO [Component] Component: org.jboss.seam.security.identity, scope: SESSION, type: JAVA_BEAN, class: org.jboss.seam.security.Identity ... 21:55:56,765 INFO [Initialization] two components with same name, higher precedence wins: org.jboss.seam.security.identity ... So I can't access identity.homePage from my webapp. I can see this exception in debug.seam: Exception during request processing: Caused by javax.el.MethodNotFoundException with message: "Method not found: org.jboss.seam.security.Identity(a)9527ee.renderHomePage()" ... I will not post the full stack trace, because the obvious reason for the problem is that the extended component is not being loaded by Seam. I checked Seam source code, comparing versions BETA1 and SNAPSHOT # 303: Class org.jboss.seam.Component has no changes between versions. Class org.jboss.seam.security.Identity has changed, but i don't think there is a problem there. Class org.jboss.seam.init.Initialization does have some changes, specially regarding hotDeploymentStrategy. I guess there is a problem is with the hacks over there. Please check this. I must tell I switched to the SNAPSHOT to not have the "NPE with hot Redeployment" issue, but now I can't even see my webapp!! -- 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

15 years, 9 months

3
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3434) More docs for pages.xsd

by Pete Muir (JIRA)

More docs for pages.xsd ----------------------- Key: JBSEAM-3434 URL: https://jira.jboss.org/jira/browse/JBSEAM-3434 Project: Seam Issue Type: Task Components: JSF Integration Reporter: Pete Muir Assignee: Pete Muir -- 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

15 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2008