January 2008 - seam-issues - Jboss List Archives

[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

17 years, 7 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

17 years, 7 months

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

17 years, 7 months

3
5
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

17 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1832) Use of <a:support> tag breaks conversation in Seam-gen (and elsewhere)

by Vincent Latombe (JIRA)

Use of <a:support> tag breaks conversation in Seam-gen (and elsewhere) ---------------------------------------------------------------------- Key: JBSEAM-1832 URL: http://jira.jboss.com/jira/browse/JBSEAM-1832 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.BETA1 Environment: Jboss 4.2.0.GA Reporter: Vincent Latombe I've seen the problem from BETA1 to HEAD To reproduce the bug, try the following : Create some seam-gen based project and generate-entities. Go to an edit page, fill some data, and click on the submit button, without clicking elsewhere (the focus must be on an edited field just before submit). Instead of validation error, or adding the new data, you should get the "The conversation ended, timed out or was processing another request" message. It seems that the validation triggered by the onblur event messes up with the validation. I have also seen the bug occuring while I was switching from one field to another quite fast (fast enough to have many validation on queue in ajax4jsf). It seems that adding <s:conversationId/> to the a:support solves this part. Here is the snippet I currently use <a:support event="onblur" bypassUpdates="true" reRender="cityCodeDecoration"> <s:conversationId/> </a:support> I tried to upgrade ajax4jsf + richfaces 3.0.1 to richfaces 3.1.0 rc2, but it didn't change anything. -- 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

17 years, 7 months

13
38
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2480) Important META tags missing from HTML generated email

by Terry (JIRA)

Important META tags missing from HTML generated email ----------------------------------------------------- Key: JBSEAM-2480 URL: http://jira.jboss.com/jira/browse/JBSEAM-2480 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.0.GA Environment: Windows, Outlook, JBoss 4.2 EAP Reporter: Terry Assigned To: Pete Muir Fix For: 2.0.1.GA When sending seam mail in HTML, the head tag and some important meta tags are misssing. I think it should at least contain this tag: <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"/> </head> Clicking links in email sent to MS Outlook doesn't recognise them as URL, it opens windows dialog box asking to find executable to run the links. I think problem is due to missing above meta tag. Also see: http://jira.jboss.org/jira/browse/JBSEAM-2479 -- 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

17 years, 7 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2479) META Tags added to HTML HEAD in Seam HTML mail get removed

by Terry (JIRA)

META Tags added to HTML HEAD in Seam HTML mail get removed ---------------------------------------------------------- Key: JBSEAM-2479 URL: http://jira.jboss.com/jira/browse/JBSEAM-2479 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.0.GA Environment: Windows, Outlook, Reporter: Terry Assigned To: Pete Muir Fix For: 2.0.1.GA the META tags added to HTML Head tag when sending Seam email in HTML get removed from the generated HTML. absence of META tags and not being able to add one causes issues in applications like outlook. <m:message> <m:from name="TISC Online" address="info(a)tisc.edu.au" /> <m:to name="#{subscriptionAdmin.recipient[0]}">#{subscriptionAdmin.recipient[1]}</m:to> <m:subject>#{subscriptionAdmin.subscriptionConfig.massMailSubject}</m:subject> <m:body> <html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"/> </head> <body> <h:outputText value="#{subscriptionAdmin.massMailMessageInterpolated}" escape="false"/> </body> </html> </m:body> </m:message> come out like: <html> <head> </head> <body> ... body contents ... </body> <html> -- 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

17 years, 7 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1183) Allow custom ExceptionHandler implementations to be inserted

by Mike Quilleash (JIRA)

Allow custom ExceptionHandler implementations to be inserted ------------------------------------------------------------ Key: JBSEAM-1183 URL: http://jira.jboss.com/jira/browse/JBSEAM-1183 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Currently you can only configure a small subset of actions to occur on an exception (redirect, http-error etc). Enhancing the exception configuration xml to allow pluggable ExceptionHandler implementations would make this a lot more flexible. e.g. pages.xml <pages>  <exception class="javax.persistence.EntityNotFoundException"> <http-error error-code="404"/> </exception>  <exception handlerClass="com.xxx.seam.CustomExceptionHandler"/> </pages> These should probably have higher precedence than standard configure-by-exception-class handlers. -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2522) Update to JBoss Cache 2.1

by Pete Muir (JIRA)

Update to JBoss Cache 2.1 ------------------------- Key: JBSEAM-2522 URL: http://jira.jboss.com/jira/browse/JBSEAM-2522 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.GA This should sort out our dependencies a bit I hope. -- 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

17 years, 7 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2508) openId support components

by koen handekyn (JIRA)

openId support components ------------------------- Key: JBSEAM-2508 URL: http://jira.jboss.com/jira/browse/JBSEAM-2508 Project: JBoss Seam Issue Type: Feature Request Reporter: koen handekyn Priority: Optional provide standard components to allow easy setup for openId support in a seam application. the seam identity contains both username and password fields. an openId identity consist soly of an identity string. ideally an openId authenticator takes in just a single openId identity, performs the openId logn procedures and concludes (in case of succesful authentication in a logged in session, with the identifier confirmed. -- 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

17 years, 7 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008