July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1653) excetpion handling in pageflow and end-conversation

by Michael Kozak (JIRA)

excetpion handling in pageflow and end-conversation --------------------------------------------------- Key: JBSEAM-1653 URL: http://jira.jboss.com/jira/browse/JBSEAM-1653 Project: JBoss Seam Issue Type: Bug Reporter: Michael Kozak The problem has been discussed <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&t=112982">here</a> I included sample application to reproduce the bug. I tested the application with IE as it behaves very badly with it. Try to invoke the action which throws exception multiple times using back button. The behaviour of seam is diffrent every time. Sometimes it ends coversation and sometimes it throws a lot of exceptions. -- 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

16 years, 1 month

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1428) Seam PDF does't do alignment inside cell

by Mikhail Grushinskiy (JIRA)

Seam PDF does't do alignment inside cell ---------------------------------------- Key: JBSEAM-1428 URL: http://jira.jboss.com/jira/browse/JBSEAM-1428 Project: JBoss Seam Issue Type: Bug Components: PDF Affects Versions: 1.3.0.ALPHA, 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Reporter: Mikhail Grushinskiy verticalAlignment, horizontalAlignment ignored -- 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

16 years, 2 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2513) Document IdentityStore

by Joshua Partogi (JIRA)

Document IdentityStore ---------------------- Key: JBSEAM-2513 URL: http://jira.jboss.com/jira/browse/JBSEAM-2513 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.1.CR1 Reporter: Joshua Partogi Priority: Minor Document on how to use IdentityStore and how to extend a custom IdentityStore. -- 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

16 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2732) Remove deprecated s:selectDate

by Pete Muir (JIRA)

Remove deprecated s:selectDate ------------------------------ Key: JBSEAM-2732 URL: http://jira.jboss.com/jira/browse/JBSEAM-2732 Project: JBoss Seam Issue Type: Task Components: JSF Controls Reporter: Pete Muir -- 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

16 years, 2 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2959) Spring example can't change password

by Jay Balunas (JIRA)

Spring example can't change password ------------------------------------ Key: JBSEAM-2959 URL: http://jira.jboss.com/jira/browse/JBSEAM-2959 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor When attempting to change a user password in the browser the change does not take effect. It shows a validation message of "verify" however the password should be valid. The log shows that the new values were received and does not show any errors. However the password is never actually set and the original is still used. This issue appears to duplicate JBPAPP-770 - however when I checked the "jboss-seam-ioc.jar" file for 2.0.2.CR2 it does contain spring.handlers and spring.schemas files. So this may be something different as the base cause. -- 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

16 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2465) Asynchronous method call from page action

by Pierre Ingmansson (JIRA)

Asynchronous method call from page action ----------------------------------------- Key: JBSEAM-2465 URL: http://jira.jboss.com/jira/browse/JBSEAM-2465 Project: JBoss Seam Issue Type: Bug Components: Framework, JSF Affects Versions: 2.0.0.GA Environment: Windows XP running Tomcat 5.5.25 using Seam 2.0.0.GA with POJO's (that is no EJB3 at all) Reporter: Pierre Ingmansson Priority: Minor If a page-tag in pages.xml includes a action that is asynchronous like this: <page action="#{myAction.doSomethingAsynchronously}" view-id="/myView.xhtml"> And if something goes wrong while executing the method "doSomethingAsynchronously", the error is not logged at all. In my case the call to the "myAction"-bean resulted in a RequiredException (due to some misconfiguration on my part), but the error was never logged so I had to debug the internal Seam-code to find out what went wrong. If the method "doSomethingAsynchronously" would have thrown a exception itself, I suspect that the behaviour would be the same (no stacktrace inte the log that is..). -- 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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2958) Spring example - no hotel checkout date is shown when booking a hotel

by Jay Balunas (JIRA)

Spring example - no hotel checkout date is shown when booking a hotel --------------------------------------------------------------------- Key: JBSEAM-2958 URL: http://jira.jboss.com/jira/browse/JBSEAM-2958 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor Deploy spring example to JBoss. Attempt to book a hotel and on the booking page there is no check out inputbox or calendar control. In the log : WARN [renderkit] Unable to find component with ID checkoutDate in view. But no exceptions, and you can still book the hotel - just can't change the checkout date. -- 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

16 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1747) SeamPhaseListener transaction debug log statements are misleading/confusing

by Matt Drees (JIRA)

SeamPhaseListener transaction debug log statements are misleading/confusing --------------------------------------------------------------------------- Key: JBSEAM-1747 URL: http://jira.jboss.com/jira/browse/JBSEAM-1747 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: 20070727.1142 Reporter: Matt Drees Priority: Trivial Debug logs from SeamPhaseListener look something like this on a non-faces request: DEBUG 31-07 11:34:31,467 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: RESTORE_VIEW 1 DEBUG 31-07 11:34:31,560 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: RESTORE_VIEW 1 DEBUG 31-07 11:34:31,560 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: RENDER_RESPONSE 6 DEBUG 31-07 11:34:31,576 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: INVOKE_APPLICATION 5 DEBUG 31-07 11:34:31,592 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: INVOKE_APPLICATION 5 DEBUG 31-07 11:34:33,731 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: RENDER_RESPONSE 6 It's misleading. For one thing, there is no "INVOKE_APPLICATION" phase; but that phaseid is used for logging before and after page actions. For another, the "before" and "after" statements are backwards (semantically). -- 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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2960) ui example <s:graphicImage> example shows no image

by Jay Balunas (JIRA)

ui example <s:graphicImage> example shows no image -------------------------------------------------- Key: JBSEAM-2960 URL: http://jira.jboss.com/jira/browse/JBSEAM-2960 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor Loaded into JBoss and the other items all seemed to work, but there was no image displayed for the <s:graphicImage> element. -- 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

16 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2610) Better feedback than "The conversation ended, timed out or was processing another request"

by Matt Drees (JIRA)

Better feedback than "The conversation ended, timed out or was processing another request" ------------------------------------------------------------------------------------------ Key: JBSEAM-2610 URL: http://jira.jboss.com/jira/browse/JBSEAM-2610 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.GA Reporter: Matt Drees Priority: Minor I've always felt this message was a bit lame. Could we inform the developer which of the three situations actually occurred? Also, it'd be cool if we could log (though probably not display in a facesMessage) some more context information, like which annotated method or pages.xml page (or exception) ended the conversation. -- 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

16 years, 2 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2008