August 2008 - seam-issues - Jboss List Archives

[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

17 years, 6 months

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

17 years, 6 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

17 years, 6 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3250) Business process variable is not resolved in process definition EL

by Ivan B (JIRA)

Business process variable is not resolved in process definition EL ------------------------------------------------------------------ Key: JBSEAM-3250 URL: https://jira.jboss.org/jira/browse/JBSEAM-3250 Project: Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.2.SP1 Environment: jbpm-jpdl-3.2.3 jboss-4.2.2.GA Reporter: Ivan B Business process variable, declared in a Seam component as @Out(scope = ScopeType.BUSINESS_PROCESS, required = false) private String bannersCount; does not resolve in jPDL <decision name="check banner list" expression="#{bannersCount}"> <transition to="select stub" name="no banners found"></transition> <transition to="select banner" name="banners found"></transition> </decision> with the following exception 13:28:46,887 FATAL [application] javax.ejb.EJBTransactionRolledbackException: Identity 'bannersCount' does not reference a MethodExpression instance, returned type: java.lang.String javax.faces.el.EvaluationException: javax.ejb.EJBTransactionRolledbackException: Identity 'bannersCount' does not reference a MethodExpression instance, returned type: java.lang.String -- 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

17 years, 6 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3045) urlrewritefilter breaks basic authentication

by Stephane Epardaud (JIRA)

urlrewritefilter breaks basic authentication -------------------------------------------- Key: JBSEAM-3045 URL: http://jira.jboss.com/jira/browse/JBSEAM-3045 Project: Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Stephane Epardaud In web.xml, if I configure the urlwritefilter before the seamfilter, any basic authentication defined in components.xml with <web:authentication-filter url-pattern="/feed/*" auth-type="basic" realm="MyRealm" precedence="0"/> will be ignored. That is, pages in the /feed/* url space will not ask for authentication, and any security restrictions requiring those pages to be accessed as logged in users will throw exceptions. If the urlrewritefilter is defined within the seamfilter, then all works well, except that I'm not sure outboud rewrite rules will work correctly. I haven't found any documentation relating the order in which these filters must be declared in the Seam documentation. If this is not a bug, perhaps it would be nice to document it? -- 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

17 years, 6 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3334) Icefaces example login does not work on JDK5

by Jozef Hartinger (JIRA)

Icefaces example login does not work on JDK5 -------------------------------------------- Key: JBSEAM-3334 URL: https://jira.jboss.org/jira/browse/JBSEAM-3334 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.SP1, 2.1.0.BETA1 Environment: JDK5 update 16 JBoss AS 4.2.3 Fedora 9 Reporter: Jozef Hartinger Log in does not work. After submiting login data page is just reloaded. No exception is present in server log. On JDK6 login works fine -- 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

17 years, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3326) seam-gen icefaces application throws a 404 when creating a new Person following release process

by Jay Balunas (JIRA)

seam-gen icefaces application throws a 404 when creating a new Person following release process ----------------------------------------------------------------------------------------------- Key: JBSEAM-3326 URL: https://jira.jboss.org/jira/browse/JBSEAM-3326 Project: Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Assignee: Gregory Dick Fix For: 2.1.0.BETA2 Follow the release process to create a base set of tables and generate entities. Selecting "save" when creating a new person throws 404 and trying to access : "http://localhost:8080/seamgenIce/iceSubmit('personeditForm');" Possibly related selected save when creating a vehicle does nothing. -- 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

17 years, 6 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3327) seam-gen icefaces "new-form" submit does nothing

by Jay Balunas (JIRA)

seam-gen icefaces "new-form" submit does nothing ------------------------------------------------ Key: JBSEAM-3327 URL: https://jira.jboss.org/jira/browse/JBSEAM-3327 Project: Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Assignee: Gregory Dick Fix For: 2.1.0.BETA2 Follow release process, and create a new form called hello. When you submit the form nothing happens. - no errors, no exception, just nothing. -- 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

17 years, 6 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3290) hibernate tools dependencies should not be in the Seam lib directory

by Jay Balunas (JIRA)

hibernate tools dependencies should not be in the Seam lib directory -------------------------------------------------------------------- Key: JBSEAM-3290 URL: https://jira.jboss.org/jira/browse/JBSEAM-3290 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Jay Balunas Fix For: 2.0.3.CR2, 2.1.0.BETA2 hibernate tools dependencies should not be in the Seam lib directory seamfp/lib/bsh.jar seamfp/lib/common.jar seamfp/lib/freemarker.jar seamfp/lib/hibernate-tools.jar seamfp/lib/jtidy.jar seamfp/lib/runtime.jar seamfp/lib/text.jar These htools deps shouldn't be part of the seam lib -- 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

17 years, 6 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2499) Seam Messages strips any MessageFormat formatting parameters

by Calvin Yu (JIRA)

Seam Messages strips any MessageFormat formatting parameters ------------------------------------------------------------ Key: JBSEAM-2499 URL: http://jira.jboss.com/jira/browse/JBSEAM-2499 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Reporter: Calvin Yu I want to use f:outputFormat to format text so that I can specify the formatting style from resource bundles. In messages.properties: foo=Howdy {0}\! The time is {1, date, MMMM dd} In my Facelets view: <h:outputFormat value="#{messages['foo']}"> <f:param value="#{exampleAction.name}"/> <f:param value="#{exampleAction.date}"/> </h:outputFormat> The result of '#{messages['foo']}' is actually: Howdy {0}\! The time is {1} The reason this is happening is because the Interpolator is using MessageFormat to evaluate {1, date, MMMM dd} with empty parameters (line #141 in Interpolator.java), which results in just {1}. -- 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

17 years, 6 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008