February 2009 - seam-issues - Jboss List Archives

[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-3948) Excel attachment should be more user-friendly to create

by Zoltan Tiringer (JIRA)

Excel attachment should be more user-friendly to create ------------------------------------------------------- Key: JBSEAM-3948 URL: https://jira.jboss.org/jira/browse/JBSEAM-3948 Project: Seam Issue Type: Feature Request Components: Excel Affects Versions: 2.1.1.GA Reporter: Zoltan Tiringer Excel attachments should be easy to create with syntax similar to that of PDF. I would like a syntax like this to work: <m:attachment fileName="people.xls"><ui:include src="/mail-xls.xhtml" /> </m:attachment> Workaround exists (thanks, Daniel): Define exportKey in <e:workbook> and then look it up from context after rendering excel content, then render mail content: FaceletsRenderer.instance().render("/mail-xls.xhtml"); DocumentData excelData = (DocumentData) Contexts.getEventContext().get("excelKey"); FaceletsRenderer.instance().render("/mailExcel.xhtml"); In mail definition the looked up DocumentData has to be referenced in the value property: <m:attachment fileName="people.xls" value="#{excelData}" contentType="application/vnd.ms-excel"/> For testing purposes I attach a template that uses the Person class from the mail example: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:e="http://jboss.com/products/seam/excel" xmlns:f="http://java.sun.com/jsf/core"> <e:workbook type="jxl"> <e:worksheet name="People" value="#{people}" var="p"> <e:header> <f:facet name="left"> The date is #date# and the time is #time# </f:facet> </e:header> <e:column style="xls-column-autosize: true"> <f:facet name="header"> <e:cell value="First name" style="xls-font: red bold 10 Verdana"/> </f:facet> <e:cell value="#{p.firstname}" /> </e:column> <e:column style="xls-column-autosize: true"> <f:facet name="header"> <e:cell value="Last name" style="xls-font: red bold 10 Verdana"/> </f:facet> <e:cell value="#{p.lastname}" forceType="text"/> </e:column> <e:column style="xls-column-autosize: true"> <f:facet name="header"> <e:cell value="Email" style="xls-font: red bold 10 Verdana"/> </f:facet> <e:cell value="#{p.address}"/> </e:column> </e:worksheet> </e:workbook> </html> -- 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, 7 months

3
2
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-3891) openid fails on port 80

by Norman Richards (JIRA)

openid fails on port 80 ----------------------- Key: JBSEAM-3891 URL: https://jira.jboss.org/jira/browse/JBSEAM-3891 Project: Seam Issue Type: Feature Request Reporter: Norman Richards Fix For: 2.1.2.CR1 See forum posting -- 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, 7 months

2
7
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-3767) Italian translation of Seam manual

by Nicola Benaglia (JIRA)

Italian translation of Seam manual ---------------------------------- Key: JBSEAM-3767 URL: https://jira.jboss.org/jira/browse/JBSEAM-3767 Project: Seam Issue Type: Release Reporter: Nicola Benaglia Priority: Optional This Jira Issue is for coordinating the actity of translation of Seam manual in italian. -- 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, 7 months

4
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3698) Error during rendering of an EMail in an event listener causes failure in rendering of next page

by Wayne Bagguley (JIRA)

Error during rendering of an EMail in an event listener causes failure in rendering of next page ------------------------------------------------------------------------------------------------ Key: JBSEAM-3698 URL: https://jira.jboss.org/jira/browse/JBSEAM-3698 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1 Environment: Windows XP, Java 6, 2GB RAM, JBoss 4.2.2.GA Reporter: Wayne Bagguley Assignee: Pete Muir I have a method that is defined as a listener like this : @Observer(JpaIdentityStore.EVENT_USER_CREATED) This attempts to send an email to the user when he registers but if the email rendering fails for some reason the exception is caught and the method returns normally. However, instead of the next page being rendered, the original page gets rendered incorrectly, with parts of the form in the wrong place. The failure of rendering the EMail should not affect the progress of the rendering of the next page if the exception is caught. -- 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, 7 months

8
16
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2009