June 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2579) Messages.properties do not work as expected with multiple WARs inside multiple Seam EARs

by Reind D (JIRA)

Messages.properties do not work as expected with multiple WARs inside multiple Seam EARs ---------------------------------------------------------------------------------------- Key: JBSEAM-2579 URL: http://jira.jboss.com/jira/browse/JBSEAM-2579 Project: JBoss Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.1.GA Environment: JBoss 4.2.2 Reporter: Reind D When 2 Seam apps are deployed, both with multiple WARs each of which as a WEB-INF/classes/messages.properties file, the messages for one of the web contexts will not work. Instead, the messages for the other WAR in the same EAR will be displayed. I've attached a sample application that demonstrates this behavior. It is modified from the "Registration" example. Steps: 1) Untar the archive 2) Copy to the app server's deploy directory 3) Go to the following URLs: http://localhost:8080/a/register.seam http://localhost:8080/b/register.seam http://localhost:8080/c/register.seam http://localhost:8080/d/register.seam The 'expected' and 'actual' fields should always match, but they won't in 1 case. -- 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, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2797) There should be one ResourceLoader per module inside an EAR

by Gregory Tanneau (JIRA)

There should be one ResourceLoader per module inside an EAR ----------------------------------------------------------- Key: JBSEAM-2797 URL: http://jira.jboss.com/jira/browse/JBSEAM-2797 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Environment: Windows XP, Seam 2.0.1.GA with JBoss 4.2.1.GA Reporter: Gregory Tanneau According to the following scenario : One MAIN.EAR with tow web modules - APP1.WAR (with messages_one_xx.properties) - APP2.WAR (with messages_two_xx.properties) When starting JBoss, the first webapp accessed makes the Resource Loader search for bundles (ie. I access APP1, messages_one_xx.properties are found). When the second webapp is accessed, the Resource Loader assumes bundles are already loaded (messages_two are NOT loaded). I think there should be (in this cas) TWO ResourceLoaders, one per web module. -- 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, 8 months

7
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4019) Problem with SeamResourceBundle

by Alexander Belov (JIRA)

Problem with SeamResourceBundle ------------------------------- Key: JBSEAM-4019 URL: https://jira.jboss.org/jira/browse/JBSEAM-4019 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Alexander Belov There is a problem with SeamResourceBundle. I have EAR application with two WAR modules. Every module has it's own component.xml file in WEB-INF path. I confugure every WAR module to use it's own list of resource bundles. When I login in one of these modules, SeamResourceBundle reads list of resource bundles and caches them. Later I go to another module. This time cache of SeamResourceBundle is not empty, it has data from the first module. So, resource bundles from the second module cannot be read, and I see keys of resource bundles, not values. -- 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, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4261) When an @Unwrap annotated method returns null, JSF EL returns the wrapper itself

by Gino Miceli (JIRA)

When an @Unwrap annotated method returns null, JSF EL returns the wrapper itself -------------------------------------------------------------------------------- Key: JBSEAM-4261 URL: https://jira.jboss.org/jira/browse/JBSEAM-4261 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.GA Reporter: Gino Miceli Seam component: @Name("test") public class Wrapper { @Unwrap public String getAString() { return null; } } JSF page: <html> <head xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"> <title>Unwrap test</title> </head> <body> #{empty test ? 'test is null' : test.class.name} </body> </html> Outputs Wrapper_$$_javassist_seam_2 This behavior appeared after updating from 2.1.1.GA to 2.1.2.GA. Similar to JBSEAM-283 -- 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, 8 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4259) Seam-gen allows entering invalid package name

by Ondrej Skutka (JIRA)

Seam-gen allows entering invalid package name --------------------------------------------- Key: JBSEAM-4259 URL: https://jira.jboss.org/jira/browse/JBSEAM-4259 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.CR1 Reporter: Ondrej Skutka Priority: Minor seam-gen setup allows an user to enter an invalid package name (including hyphens) and generates incompilable code. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4258) Redirect in navigation rules doesn't work

by Ondrej Skutka (JIRA)

Redirect in navigation rules doesn't work ----------------------------------------- Key: JBSEAM-4258 URL: https://jira.jboss.org/jira/browse/JBSEAM-4258 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.CR1 Environment: JBoss 5.1.0, Sun JDK 1.6.0.13 Reporter: Ondrej Skutka Priority: Blocker Fix For: 2.2.0.GA Redirecting in navigation rules (pages.xml) doesn't work. For example in booking example, after registering, a user is not redirected to home.xhtml even though he's successfully registered. Or in the dvdstore application when user enters seam-dvdstore/admin/admin, he's not redirected to home.xhtml due to AuthorizationException. This issue blocks testing of 2.2.0.CR1, because the ftests rely on it. -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4256) Title of section 16.3 disappeared in the doc (internationalizing/labels), and section 16.4, 16.5 and 16.6 should be under section 16.3

by Denis Forveille (JIRA)

Title of section 16.3 disappeared in the doc (internationalizing/labels), and section 16.4, 16.5 and 16.6 should be under section 16.3 --------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4256 URL: https://jira.jboss.org/jira/browse/JBSEAM-4256 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.2.0.CR1 Reporter: Denis Forveille Assignee: Denis Forveille Priority: Trivial Fix For: 2.2.0.GA There is a erroneous "/" in the <section id="labels" /> tag and a missing </section> tag before "the "Timezones" section -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4255) CLONE -Using rich:listShuttle for N*N relations in seam-gen

by Vania Lopes (JIRA)

CLONE -Using rich:listShuttle for N*N relations in seam-gen ----------------------------------------------------------- Key: JBSEAM-4255 URL: https://jira.jboss.org/jira/browse/JBSEAM-4255 Project: Seam Issue Type: Feature Request Components: JSF Integration, Tools Environment: Seam 2.0.1+ (integrating rich faces 3.1.3+) Reporter: Vania Lopes A weak point in SEAM is the automatic generation of N-N CRUD pages With RichFaces 3.1.3, the listShuttle could allow easy CRUDing in N-N relations (and also or in 1-N relations). Maybe can someone find time to update the seam-gen templates and drive it to an higher level of user experience ? :) -- 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-1913) EL with parameters not work in a <ui:composition> facelet component

by Gilliard Cordeiro (JIRA)

EL with parameters not work in a <ui:composition> facelet component ------------------------------------------------------------------- Key: JBSEAM-1913 URL: http://jira.jboss.com/jira/browse/JBSEAM-1913 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 1.2.1.GA Environment: Windows or Linux, Java 6, Tomcat 6.0.14 Reporter: Gilliard Cordeiro EL with parameters not work in a <ui:composition> facelet component. The value of parameters is available in a <h:outputText>, for instance, but is null when executing a Java action methods. -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2385) EL parsing ?: poorly

by David Fedchenko (JIRA)

EL parsing ?: poorly -------------------- Key: JBSEAM-2385 URL: http://jira.jboss.com/jira/browse/JBSEAM-2385 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 2.0.1.CR1 Environment: Win XP, JBoss AS 4.2.2.GA Reporter: David Fedchenko Priority: Minor This throws an exception: #{referralController.newReferral ? messages.referralTitleNew: messages.referralTitleExisting} It can be avoided by adding a space before the colon. -- 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
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 June 2009