July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3005) Add flush attribute to @End annotation

by Dan Allen (JIRA)

Add flush attribute to @End annotation -------------------------------------- Key: JBSEAM-3005 URL: http://jira.jboss.com/jira/browse/JBSEAM-3005 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Priority: Minor Fix For: 2.1.0.GA The @End annotation should support the flush attribute to complement the flushMode attribute on the @Begin annotation. While there may be cases to perform bean-managed flushing, it makes sense to allow this to be specified declaratively, especially for simple cases. The flushing would need to occur in the ConversationInterceptor. -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2953) chatroom example allow users not connected to post messages as user "null>"

by Jay Balunas (JIRA)

chatroom example allow users not connected to post messages as user "null>" --------------------------------------------------------------------------- Key: JBSEAM-2953 URL: http://jira.jboss.com/jira/browse/JBSEAM-2953 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor Deploy the remoting/chatroom example. You can send a message even if not connected and it will show as user: "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

16 years, 1 month

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2954) remoting/helloworld example still processes even if you select "cancel"

by Jay Balunas (JIRA)

remoting/helloworld example still processes even if you select "cancel" ----------------------------------------------------------------------- Key: JBSEAM-2954 URL: http://jira.jboss.com/jira/browse/JBSEAM-2954 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor When you launch the remoting helloworld example you have the option of selecting "ok" or "cancel" on the popup box. If you hit cancel it will still process but with "null" for a string. -- 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

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

16 years, 1 month

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3016) Make s:selectItems work with rich:comboBox

by Daniel Roth (JIRA)

Make s:selectItems work with rich:comboBox ------------------------------------------ Key: JBSEAM-3016 URL: http://jira.jboss.com/jira/browse/JBSEAM-3016 Project: Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.0.2.GA Environment: Linux Ubuntu, Jboss 4.2.2, Seam 2.0.2.GA, Firefox 2. Reporter: Daniel Roth Priority: Minor Fix For: The future rich:comboBox takes SelectItems as suggestions. However, using it together with s:selectItems doesn't work. See attached sample. -- 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

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1954) JDK 1.6 tests failing

by Pete Muir (JIRA)

JDK 1.6 tests failing --------------------- Key: JBSEAM-1954 URL: http://jira.jboss.com/jira/browse/JBSEAM-1954 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Running Seam testsuite with JDK 1.6 is giving errors (not surprisingly). http://hudson.jboss.org/hudson/job/JBossSeam-sun16/ -- 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

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2339) add javadoc target to seam-gen project

by Dan Allen (JIRA)

add javadoc target to seam-gen project -------------------------------------- Key: JBSEAM-2339 URL: http://jira.jboss.com/jira/browse/JBSEAM-2339 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.0.x We have just about every other standard Ant target configured, why not have one to generate JavaDoc? This would really impress managers as well as developers. Besides, who doesn't generated JavaDoc at some point these days? -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2033) style h:messages (perhaps using rich:messages)

by Dan Allen (JIRA)

style h:messages (perhaps using rich:messages) ---------------------------------------------- Key: JBSEAM-2033 URL: http://jira.jboss.com/jira/browse/JBSEAM-2033 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.1.GA The styles used for the h:messages still use the old style before RichFaces was added (It is beige and orange). This looks really bad. RichFaces just added a sweet looking message style in 3.1. Let's use that! -- 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

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2133) inline EL in component property value not properly detected

by Dan Allen (JIRA)

inline EL in component property value not properly detected ----------------------------------------------------------- Key: JBSEAM-2133 URL: http://jira.jboss.com/jira/browse/JBSEAM-2133 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Dan Allen Assigned To: Dan Allen Priority: Critical Fix For: 2.0.1.GA Currently, the EL notation in a property is only being evaluated if the property starts with "#{". There are two problems with this assumption. 1. Inline EL can only be used if the property starts with an expression (i.e. <property name="message">#{applicationName} is a cool application</property>) 2. There is no way to escape EL so that is is evaluated by the property accepting the string (rather than when the value is assigned). The correct behavior would be to treat the property value as a value expression if it CONTAINS "#{". The benefits are two fold: 1. A property value can use inline EL that is evaluated when the property value is set (see above) 2. The resolved value of the property can be EL (delayed EL) that is to be interpreted by the component as needed. This is done by escaping the EL per the unified EL spec (i.e. <property name="created-message">The user \#{user.name} has been created!</property) Surprisingly, everything is already in place. All that needs to happen is the check for EL needs to change from "startsWith" to "contains". -- 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

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2520) EL Expressions in JPDL files cause EL exceptions AGAIN

by David Heggie (JIRA)

EL Expressions in JPDL files cause EL exceptions AGAIN ------------------------------------------------------ Key: JBSEAM-2520 URL: http://jira.jboss.com/jira/browse/JBSEAM-2520 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.1.CR1 Reporter: David Heggie The same thing that happened in the linked issue JBSEAM-1937 is happening again. This time it is only causing exceptions when evaluating a simple value expression eg. #{someComponent}. Looking through the code the problem is happening again in the org.jboss.seam.bpm.SeamExpressionEvaluator where it "Successfully" creates a MethodExpression and then tries to invoke it which causes a ELException which is not caught (only MethodNotFoundException is caught) and the call exits without trying to evaluate the expression as a ValueExpression. -- 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
11
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