September 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-164) Kill all conversations

by Stuart Douglas (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-164?page=com.atlassian.jira.plu... ] Stuart Douglas updated JBSEAM-164: ---------------------------------- Attachment: seam-endall-patch-v1.diff I have attached a first attempt at a patch for this. It introduces a @EndAll annotation which destroys all current conversation contexts and then creates a new temporary one. The temporary one can be promoted to long running in the normal way. If people are happy with the then I can also do a pages.xml variant and doc updates. > Kill all conversations > ---------------------- > > Key: JBSEAM-164 > URL: https://jira.jboss.org/jira/browse/JBSEAM-164 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Fix For: The future > > Attachments: seam-endall-patch-v1.diff > > > Users want an operation to kill all conversations, and they want that to happen in the same action as beginning a new conversation. -- 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, 9 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3479) seam-gen - target "compilemodel" does not exist

by Jozef Hartinger (JIRA)

seam-gen - target "compilemodel" does not exist ----------------------------------------------- Key: JBSEAM-3479 URL: https://jira.jboss.org/jira/browse/JBSEAM-3479 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.CR1 Environment: JDK5 JBoss AS 4.2.3 Reporter: Jozef Hartinger Seam-gen generated build.xml contains javadoc target that depends on non-existing targets "compilemodel" and "compileactions". After commenting javadoc target generated projects work fine. Javadoc target should insted of non-existing targets depend on "compile" target. -- 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, 9 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3394) Reference guide on IE shows extra characters in headers

by Jay Balunas (JIRA)

Reference guide on IE shows extra characters in headers ------------------------------------------------------- Key: JBSEAM-3394 URL: https://jira.jboss.org/jira/browse/JBSEAM-3394 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.BETA1, 2.0.3.CR1 Environment: windows XP IE 7 Reporter: Jay Balunas Attachments: seam_ref_guide_IE_characters.JPG When viewing the reference guide using IE on windows extra characters are displayed in the chapter and section headers. This seems to only happen if the reference guide is local on disk. Browsing to the online versions on sfwk.org with the same browser does not show this. I will attach a screen shot. -- 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, 9 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3476) Mail example - 0 byte files are attached to email

by Jozef Hartinger (JIRA)

Mail example - 0 byte files are attached to email ------------------------------------------------- Key: JBSEAM-3476 URL: https://jira.jboss.org/jira/browse/JBSEAM-3476 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.CR1 Environment: JDK 5, 6 JBoss AS 4.2.3 Reporter: Jozef Hartinger When sending an email with attachments, instead of several pictures with different names, email with three empty JPEGs is delivered. All the files have the same name that consists of name values used when sending the e-mail. -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3465) Example Seam-Discs throws SEVERE Trinidad-Exception

by nimo stephan (JIRA)

Example Seam-Discs throws SEVERE Trinidad-Exception --------------------------------------------------- Key: JBSEAM-3465 URL: https://jira.jboss.org/jira/browse/JBSEAM-3465 Project: Seam Issue Type: Quality Risk Components: JSF Integration Affects Versions: 2.1.0.BETA1 Environment: EJB 3.0, JBOSS 4.2, SEAM 2.1, TRINIDAD (actual version), RichFaces (3.2) Reporter: nimo stephan Priority: Minor I have looked at the seam-disc-example and have run it. Though all the trinidad-components are rendered well, the following error occurs: org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit createResponseWriter SEVERE: No RenderingContext has been created. Maybe, the web.xml (faces-config.xml) are not well configured for Seam, Ajax4j (richfaces), Trinidad. -- 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, 9 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3478) Use CDK generation for the Excel module

by Daniel Roth (JIRA)

Use CDK generation for the Excel module --------------------------------------- Key: JBSEAM-3478 URL: https://jira.jboss.org/jira/browse/JBSEAM-3478 Project: Seam Issue Type: Task Components: Excel Affects Versions: 2.1.0.BETA1 Reporter: Daniel Roth Assignee: Daniel Roth Priority: Minor We should use CDK in the Excel module to avoid problems when refactoring etc. -- 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, 9 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Deleted: (JBSEAM-3467) Add conversation restart functionality

by Christian Bauer (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-3467?page=com.atlassian.jira.pl... ] Christian Bauer deleted JBSEAM-3467: ------------------------------------ > Add conversation restart functionality > -------------------------------------- > > Key: JBSEAM-3467 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3467 > Project: Seam > Issue Type: Feature Request > Environment: Windows Server 2003 > JBoss EAP 4.3.0.CP02_FP01 > JRockit 1.5 JVM > Reporter: asookazian > > need functionality that will restart conversation (via endBeforeRirect() and begin() methods in Conversation API or similar). suggested solution from JBoss dev sppt did not work (see forum URL below). workaround was to create a private method in SFSB that set instance variables to null and continue with existing LRC. a more elegant solution is preferred (Seam ending current LRC, creating new LRC and transferring state from old conversation variables to new one via restart() api call). > Scenario: conversation begin demarcation is driven by selection of a drop-down (h:selectOneMenu) value. when user selects the new value the second time, the conversation should end and start a new LRC. Solution from dev sppt did not work b/c the endBeforeRedirect() method was being called in action binding method for drop-down in SFSB and subsequently, in pages.xml, <begin-conversation> was coded prior to redirect to same xhtml. > Result: after the JSF was re-rendered after 2nd drop-down selection, the value in the drop-down was set to "select value" which is the default value. It should have been set to the 2nd selection. The reason this is happening is b/c the instance variables are conversation-scoped (b/c the SFSB is conversation-scoped) and thus are presumably no longer available to the second LRC (which strangely enough is still showing the original cid in the debug.seam page after refresh!) -- 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, 9 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3467) Add conversation restart functionality

by asookazian (JIRA)

Add conversation restart functionality -------------------------------------- Key: JBSEAM-3467 URL: https://jira.jboss.org/jira/browse/JBSEAM-3467 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.2.SP1 Environment: Windows Server 2003 JBoss EAP 4.3.0.CP02_FP01 JRockit 1.5 JVM Reporter: asookazian need functionality that will restart conversation (via endBeforeRirect() and begin() methods in Conversation API or similar). suggested solution from JBoss dev sppt did not work (see forum URL below). workaround was to create a private method in SFSB that set instance variables to null and continue with existing LRC. a more elegant solution is preferred (Seam ending current LRC, creating new LRC and transferring state from old conversation variables to new one via restart() api call). Scenario: conversation begin demarcation is driven by selection of a drop-down (h:selectOneMenu) value. when user selects the new value the second time, the conversation should end and start a new LRC. Solution from dev sppt did not work b/c the endBeforeRedirect() method was being called in action binding method for drop-down in SFSB and subsequently, in pages.xml, <begin-conversation> was coded prior to redirect to same xhtml. Result: after the JSF was re-rendered after 2nd drop-down selection, the value in the drop-down was set to "select value" which is the default value. It should have been set to the 2nd selection. The reason this is happening is b/c the instance variables are conversation-scoped (b/c the SFSB is conversation-scoped) and thus are presumably no longer available to the second LRC (which strangely enough is still showing the original cid in the debug.seam page after refresh!) -- 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, 9 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2955) seambay example throws an exception when viewing "Whistler's Mother" item

by Jay Balunas (JIRA)

seambay example throws an exception when viewing "Whistler's Mother" item ------------------------------------------------------------------------- Key: JBSEAM-2955 URL: http://jira.jboss.com/jira/browse/JBSEAM-2955 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor When attempting to view the "Whistler's Mother" item the browser shows a JSF error page, and the exception below is in the logs: Caused by: line 1:346: unexpected char: 0xFFFD at org.jboss.seam.text.SeamTextLexer.nextToken(SeamTextLexer.java:230) at antlr.TokenBuffer.fill(Unknown Source) at antlr.TokenBuffer.LA(Unknown Source) at antlr.LLkParser.LA(Unknown Source) at org.jboss.seam.text.SeamTextParser.line(SeamTextParser.java:651) at org.jboss.seam.text.SeamTextParser.paragraph(SeamTextParser.java:401) -- 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, 9 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3471) Decorate overwriting attributes invalid and required in event scope

by Nicklas Karlsson (JIRA)

Decorate overwriting attributes invalid and required in event scope ------------------------------------------------------------------- Key: JBSEAM-3471 URL: https://jira.jboss.org/jira/browse/JBSEAM-3471 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.0.BETA1 Reporter: Nicklas Karlsson Looking at the code in org.jboss.seam.ui.renderkit.DecorateRendererBase, doEncodeBegin sets the attributes "required" and "invalid" and removes them in doEncodeEnd without making an attempt to store away/restore existing values. This appears to happens with every use of decorate, whether the user refers to the attributes or not, possibly confusing application logic if attributes with same name have been placed in the event scope. -- 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, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2008