June 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4250) Contexts are not in sync when using SeamResourceBundle and seam Log

by Ian Michell (JIRA)

Contexts are not in sync when using SeamResourceBundle and seam Log ------------------------------------------------------------------- Key: JBSEAM-4250 URL: https://jira.jboss.org/jira/browse/JBSEAM-4250 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Ian Michell Priority: Blocker Hi, Using Seam 2.1.1.GA I am injecting the messages map (@In Map<String, String> messages) and setting eventContext variables before using get on the map and I'm getting an exception that states that it cannot resolve the value... Code follows: Code for a single purchase order in my document history -------------------------------------------------------------------------------------------- Contexts.getEventContext().set("trn.viewTransactions.poDocument", poList.get(0)); Contexts.getEventContext().set("trn.viewTransactions.supplierName", poList.get(0).getSupplierOrgs().first().getCommonName()); Contexts.getEventContext().set("trn.viewTransactions.poList", messages.get("mytransactions.messages.generated.link")); Contexts.getEventContext().flush(); history.setActionDescription(messages.get("mytransactions.messages.generated.single")); -------------------------------------------------------------------------------------------- Expected output: This requisition also generated this order: Order 12345 - ACME Suppliers Expression: This requisition also generated this order: #{trn.viewTransactions.poList} It throws an exception saying viewTransactions cannot be resolved on the seam namespace, this generally means that it can't find the values in the expression. I have tried flushing the event context to see if it makes a difference (hence the flush above). Is this a bug, or am I doing the entire thing wrong? Any help would be appreciated. Ian -- 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, 6 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4252) Messages can be double-interpolated

by Norman Richards (JIRA)

Messages can be double-interpolated ----------------------------------- Key: JBSEAM-4252 URL: https://jira.jboss.org/jira/browse/JBSEAM-4252 Project: Seam Issue Type: Bug Reporter: Norman Richards Assignee: Norman Richards Priority: Minor Fix For: 2.2.0.GA -- 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, 6 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4201) Upgrade to newest Hibernate libraries (3.3.x series) and Hibernate Search to 3.1.1

by Sanne Grinovero (JIRA)

Upgrade to newest Hibernate libraries (3.3.x series) and Hibernate Search to 3.1.1 ---------------------------------------------------------------------------------- Key: JBSEAM-4201 URL: https://jira.jboss.org/jira/browse/JBSEAM-4201 Project: Seam Issue Type: Task Components: Core, Examples, Framework, Platform interoperability, Search Affects Versions: 2.1.2.CR2 Reporter: Sanne Grinovero Seam is still bundling the stable hibernate libraries found in JBoss AS 4.2, the series targetting hibernate core 3.2.4sp1. Many improvements and bugfixes are missing. -- 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, 6 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4244) fix for JBSEAM-4131 introduced a performance regression

by Pete Muir (JIRA)

fix for JBSEAM-4131 introduced a performance regression ------------------------------------------------------- Key: JBSEAM-4244 URL: https://jira.jboss.org/jira/browse/JBSEAM-4244 Project: Seam Issue Type: Bug Components: Core Reporter: Pete Muir Assignee: Norman Richards Fix For: 2.2.0.CR1 -- 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, 6 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4251) Query component is evaluating EL expressions defined in ejbql attribute incorrectly

by Jacob Orshalick (JIRA)

Query component is evaluating EL expressions defined in ejbql attribute incorrectly ----------------------------------------------------------------------------------- Key: JBSEAM-4251 URL: https://jira.jboss.org/jira/browse/JBSEAM-4251 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.1.2.GA Reporter: Jacob Orshalick Assignee: Jacob Orshalick Priority: Minor EL expressions defined in an EntityQuery definition in components.xml such as: <fwk:entity-query name="persons" max-results="5"> <fwk:ejbql>select p from Person as p where p.age > #{example.age}</fwk:ejbql> </fwk:entity-query> are being evaluated at the time the EntityQuery is created and the ejbql String is set to: select p from Person as p where p.age > 0 This is happening because the EntityQuery component defines the ejbql attribute as a String. This means the attribute is evaluated as a ValueExpression before being set into the component causing all EL to be resolved and returning the resulting String. The fix is to define the ejbql attribute as a ValueExpression and then use the getExpressionString() method to retrieve the original String when parsing the ejbql. -- 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, 6 months

1
0
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, 6 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4249) bug in glassfish-build.xml affects Windows hosts for seam-gen

by Chris Dunphy (JIRA)

bug in glassfish-build.xml affects Windows hosts for seam-gen ------------------------------------------------------------- Key: JBSEAM-4249 URL: https://jira.jboss.org/jira/browse/JBSEAM-4249 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA, 2.1.2.CR2 Environment: Windows XP SP3, GlassFish 2.1, Seam 2.1.2 Reporter: Chris Dunphy Line 176 of the glassfish-build.xml file has a condition tag, but its missing the clause for Windows hosts... it should resembe the condition clause that is found starting in line 14 of the glassfish-build.xml. -- 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, 6 months

1
0
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, 6 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, 6 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4131) Regression: EL expressions in messages not working anymore

by Jonas Buechel (JIRA)

Regression: EL expressions in messages not working anymore ---------------------------------------------------------- Key: JBSEAM-4131 URL: https://jira.jboss.org/jira/browse/JBSEAM-4131 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.CR1 Reporter: Jonas Buechel Since I upgraded to 2.1.2.CR1 I'm facing problems with EL expressions within messages files. Which means: The value of {code}controls_logout_user=#{identity.username} abmelden{code} won't be rendered anymore. Code: {code}<s:link action="#{identity.logout}" value="#{messages.controls_logout_user}" rendered="#{identity.loggedIn}" propagation="none" />{code} HTML Result: {code}<a id="fwcMenuForm:j_id51" href="http://localhost:80/home?actionMethod=modules%2Fhome.xhtml%3Aidentity.logout"/>{code} Expected HTML Result: {code}<a id="fwcMenuForm:j_id51" href="http://localhost:80/home?actionMethod=modules%2Fhome.xhtml%3Aidentity.logout">username abmelden</a>{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, 6 months

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