July 2008 - seam-issues - Jboss List Archives

[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, 7 months

7
12
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, 7 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, 7 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-967) JBoss Seam - Support authentication from a realm (on Tomcat)

by Bradley Smith (JIRA)

JBoss Seam - Support authentication from a realm (on Tomcat) ------------------------------------------------------------ Key: JBSEAM-967 URL: http://jira.jboss.com/jira/browse/JBSEAM-967 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Bradley Smith Please see discussion in the JBoss forum reference. The idea is to allow the Seam Identity (security) component to get the Principal from the HttpServletRequest and to delegate the hasRole() calls to the HttpServletRequest as well. This is because, in my case, Tomcat has already forced the user to authenticate if necessary and the authentication, authorization information is available in the container's HttpServletRequest impl. Principal userPrincipal = httpServletRequest.getUserPrincipal(); boolean hasRole(String roleName) { return httpServletRequest.isUserInRole(roleName); } public String getUsername() { return httpServletRequest.getRemoteUser(); } public boolean isLoggedIn() { return httpServletRequest.getUserPrincipal() != null; } -- 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, 7 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2523) Identity component should be scoped to the WAR module

by Reind D (JIRA)

Identity component should be scoped to the WAR module ----------------------------------------------------- Key: JBSEAM-2523 URL: http://jira.jboss.com/jira/browse/JBSEAM-2523 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.1.CR1 Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA) Reporter: Reind D I have an EAR with two web modules. I have configured the 'Identity authenticateMethod' in components.xml to use a different a method for each WAR (authA.authenticate, authB.authenticate). When attempting to login to the 'b' webapp it invokes the authenticateMethod defined in a.war. Attempting to login to the 'a' webapp works as expected. It appears as though the Identity component is not scoped to the WAR. The EAR is packaged as follows: my-application.ear/ a.war/ WEB-INF/ components.xml ... b.war/ WEB-INF/ components.xml ... web.jar Congure authentication as follows in both components.xml files: a.war/WEB-INF/components.xml <security:identity authenticate-method="#{authA.authenticate}" /> b.war/WEB-INF/components.xml <security:identity authenticate-method="#{authB.authenticate}" /> -- 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, 7 months

6
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2854) Provide a way to nest pageflows

by Marcell Barbacena (JIRA)

Provide a way to nest pageflows ------------------------------- Key: JBSEAM-2854 URL: http://jira.jboss.com/jira/browse/JBSEAM-2854 Project: JBoss Seam Issue Type: Feature Request Components: BPM, Core, JSF Controls Affects Versions: 2.0.1.GA Environment: All Reporter: Marcell Barbacena The current behaviour of pageflow subprocess tag is to include the pageflow definition in the the current flow, meaning that the parent pageflow is paused until the included pageflow ends. However, sometimes it is desired that the parent pageflow do not "pause" and that the included gain its own flow. The semantics of this nested pageflow is: - when starts: provided a nested conversation from the parent pageflow. - when ends: go back do the state before the nesting. If the parent pageflow is not associated in any way to the nested, its flow goes without interfering with the nested. E.g.: Parent directed graph: startpage1->page1; page1->page2; page1->nested; nested->page2; page2->page3; page3->endpage1; Nested graph: startpage2->page5; page5->page6; page6->endpage2 Then we can have: parent: startpage1->page1; parent: page1->nested; nested: startpage2->page5; nested: page5->page6; parent: page1->page2; parent: page2>page3; nested: page6->endpage2 nested:endpage2->page2; parent: page3->endpage1; nested: page2>page3; nested: page3->endpage1; See that the nested pageflow gains his own flow, i.e. independent of the parent. -- 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, 7 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2940) upgrade to Hibernate 3.2.5

by Dan Allen (JIRA)

upgrade to Hibernate 3.2.5 -------------------------- Key: JBSEAM-2940 URL: http://jira.jboss.com/jira/browse/JBSEAM-2940 Project: Seam Issue Type: Task Affects Versions: 2.1.0.A1 Reporter: Dan Allen Assigned To: Pete Muir Priority: Minor Fix For: 2.1.0.GA Hibernate in JBoss AS 4.2.2.GA is 4.2.1.sp1. However, it is not the same JAR as what is in the JBoss Maven 2 repository. The JAR from the Maven 2 repository is a different build. It is missing the specialized Oracle dialects (8i, 9i, and 10g). That appears to be the only files that are missing, however it could be that some files differ as well. And according to this, the Hibernate in JBoss AS 4.2.2.GA is 3.2.0.GA! http://fisheye.jboss.org/browse/JBossAS/tags/JBoss_4_2_2_GA/build/build-t... We just need to upgrade to get to a clean build ;) -- 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, 7 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2746) Empty first search result page if (hits % pagesize == 0)?

by Nicklas Karlsson (JIRA)

Empty first search result page if (hits % pagesize == 0)? ---------------------------------------------------------- Key: JBSEAM-2746 URL: http://jira.jboss.com/jira/browse/JBSEAM-2746 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Nicklas Karlsson Assigned To: Christian Bauer I searched for "production" and got "1 to 15 of 60 hit(s)" but an empty list. Off by one pagination if hits mod results is 0? -- 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, 7 months

5
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1587) page parameters: option to bypass model-based validations

by Hung Tang (JIRA)

page parameters: option to bypass model-based validations --------------------------------------------------------- Key: JBSEAM-1587 URL: http://jira.jboss.com/jira/browse/JBSEAM-1587 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Hung Tang -- 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, 7 months

7
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3056) JPDL navigation and seam

by Florian Keusch (JIRA)

JPDL navigation and seam ------------------------ Key: JBSEAM-3056 URL: http://jira.jboss.com/jira/browse/JBSEAM-3056 Project: Seam Issue Type: Task Components: BPM Reporter: Florian Keusch hi In our applications we have a navigation menu. When we use seam and some jpdl pageflows we have the following problem: if we leave the pageflow with a <s:link propagation="end"> (e.g. clicking on the menu), then the pageflow conversation is ended but also an illegal navigation exception is thrown. This issue was described on the seam framework: http://www.seamframework.org/Community/ProblemWithJPDLIllegalNavigation but I could not find it in this Jira. It's not solved. In the code (PageFlow.java) there's a TODO where the illegal navigation ecxeption is thrown: //now check that the restored view id matches what we expect //from the pageflow node //TODO: we need some way to disable this check, since users // might want some adhoc nav in and out of a pageflow? String viewId = Pages.getViewId(facesContext); if ( !viewId.equals( getPage().getViewId() ) ) { illegalNavigationError(); } If we use <s:link propagation="none"> in our menu navigation then this will not cause a illegal navigation exception, but in the background the conversations are still there not ended. fke -- 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, 7 months

2
1
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 2008