November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2164) Improve exception chaining in SeamLoginModule

by Yannick Lazzari (JIRA)

Improve exception chaining in SeamLoginModule --------------------------------------------- Key: JBSEAM-2164 URL: http://jira.jboss.com/jira/browse/JBSEAM-2164 Project: JBoss Seam Issue Type: Feature Request Reporter: Yannick Lazzari Priority: Minor This an improvement request in the SeamLoginModule class to properly chain exceptions when throwing LoginExceptions in the login method. See code below: public boolean login() throws LoginException { try { NameCallback cbName = new NameCallback("Enter username"); PasswordCallback cbPassword = new PasswordCallback("Enter password", false); // Get the username and password from the callback handler callbackHandler.handle(new Callback[] { cbName, cbPassword }); username = cbName.getName(); } catch (Exception ex) { log.error("Error logging in", ex); throw new LoginException(ex.getMessage()); } MethodExpression mb = Identity.instance().getAuthenticateMethod(); if (mb==null) { throw new IllegalStateException("No authentication method defined - please define <security:authenticate-method/> for <security:identity/> in components.xml"); } try { return (Boolean) mb.invoke(); } catch (Exception ex) { log.error("Error invoking login method", ex); throw new LoginException(ex.getMessage()); } } In both instances where a LoginException is thrown, only the message is passed to the constructor of the LoginException. I know that the LoginException does not overload the constructor to pass a cause directly but we can use the initCause method instead: LoginException loginException = new LoginException(); loginException.initCause(originalException); throw loginException; If people use typed exceptions in their authenticator method to express different reasons why the login attempt failed, it's impossible right now to get that original 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

14 years, 3 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1687) Include GanttChart into Charting

by Samuel Mendenhall (JIRA)

Include GanttChart into Charting -------------------------------- Key: JBSEAM-1687 URL: http://jira.jboss.com/jira/browse/JBSEAM-1687 Project: JBoss Seam Issue Type: Feature Request Reporter: Samuel Mendenhall Priority: Minor Including GanttChart into Seams charting package. -- 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

14 years, 3 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-560) seam new-query

by Gavin King (JIRA)

seam new-query -------------- Key: JBSEAM-560 URL: http://jira.jboss.com/jira/browse/JBSEAM-560 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Assigned To: Norman Richards To generate a stub query page -- 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

14 years, 3 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2069) itext example tests

by Norman Richards (JIRA)

itext example tests ------------------- Key: JBSEAM-2069 URL: http://jira.jboss.com/jira/browse/JBSEAM-2069 Project: JBoss Seam Issue Type: Task Reporter: Norman Richards Assigned To: Norman Richards Priority: Minor Fix For: 2.0.0.GA -- 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

14 years, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1758) DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet

by Chris Rudd (JIRA)

DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet --------------------------------------------------------------------------------------------- Key: JBSEAM-1758 URL: http://jira.jboss.com/jira/browse/JBSEAM-1758 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd When the DocumentStorePhaseListener is installed before the SeamPhaseListener (this can happend when the jboss-seam.jar sits in the ear, and the jboss-seam-pdf.jar sits in the war) in a portlet environment, a "No active application context" exception is thrown during Portlet.render. This is becaus the SeamPhaseListener hasn't had a chance to setup the Seam contexts yet. I would suggest changing the code so that it responds to the Phase events that the SeamPhaseListener publishes ( org.jboss.seam.beforePhase ) so that its guaranteed to be executed after the SeamPhaseListener has property set things up. -- 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

14 years, 3 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2253) UIHeaderFooter should allow different elements than just Phrase

by Bolke de Bruin (JIRA)

UIHeaderFooter should allow different elements than just Phrase --------------------------------------------------------------- Key: JBSEAM-2253 URL: http://jira.jboss.com/jira/browse/JBSEAM-2253 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.0.GA Reporter: Bolke de Bruin Currently the UIHeaderFooter does not allow anything else than Text (Phrase). This makes it unusable to generate something with for example a company logo on every page. I am currently working on a alternative implementation and I'll will attach it it as soon as it is ready. -- 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

14 years, 3 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1625) <param> node in <exception> in pages.xml is not used

by Zalder R (JIRA)

<param> node in <exception> in pages.xml is not used ---------------------------------------------------- Key: JBSEAM-1625 URL: http://jira.jboss.com/jira/browse/JBSEAM-1625 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: jboss 4.2, seam 2.0.0.B1 Reporter: Zalder R The param option in an exception node in pages.xml is not used : <exception class="org.my.Exception"> <redirect view-id="/mypage.xhtml"> <param name="u" value="#{user.username}"/> <message severity="warn">#{messages['MSG.ERROR.MAX_TEXT_REACHED']}</message> </redirect> </exception> When the exception is triggered : redirect is done to mypage.xhtml ... not mypage.xhtml?u=whatever -- 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

14 years, 3 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1841) Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality

by steve tynor (JIRA)

Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1841 URL: http://jira.jboss.com/jira/browse/JBSEAM-1841 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: steve tynor Please add some documentation, perhaps an example project, that uses seamgen-generated EntityHome classes in order to demonstrate the intended use of the wire(), isWired(), createInstance(), getDefinedInstance(), setId(), etc. functions. Some discussion on how these related to <param> and <f:param> in XHTML is also needed. As it stands, these are completely undocumented without any explanation of their intended use, so those of us that have boostrapped a project with seamgen, have no guidance on how to maintian these classes as our application changes (new properties added to entities, etc.) -- 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

14 years, 3 months

5
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2301) JBoss EL bug handling overloaded methods with varargs mixed in

by Matthew Lieder (JIRA)

JBoss EL bug handling overloaded methods with varargs mixed in -------------------------------------------------------------- Key: JBSEAM-2301 URL: http://jira.jboss.com/jira/browse/JBSEAM-2301 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 2.0.0.GA Reporter: Matthew Lieder Doing facesMessages.add("Message") from an EL expression doesn't work, complaining about the String class not being compatible with the FacesMessage class. The problem is caused by a combination of two things: 1. There are two FacesMessages.add(...) that can accept one parameter: add(FacesMessage facesMessage) and add(String messageTemplate, Object... params) 2. The FacesMessages.add(...) that accepts a String as the first parameter can optionally accept additional parameters through a vararg If only one of those was the case, it'd work fine. However, having both at the same time triggers the error. -- 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

14 years, 3 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1505) Application-level log

by Christian Bauer (JIRA)

Application-level log --------------------- Key: JBSEAM-1505 URL: http://jira.jboss.com/jira/browse/JBSEAM-1505 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor Create a persistent LogEvent and raise a Seam event whenever anything interesting happens in the app (user registered, document deleted, notification stopped because of bounces, and so on). Show log in the admin interface and allow admin to set log level and clear the log. -- 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

14 years, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007