March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2648) SeamTest running inside the IDE

by Rodrigo Yoshima (JIRA)

SeamTest running inside the IDE ------------------------------- Key: JBSEAM-2648 URL: http://jira.jboss.com/jira/browse/JBSEAM-2648 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 1.2.1.GA Environment: Jboss 4.0.5 / Seam 1.2.1.GA / Jboss IDE for Eclipse / Windows XP Reporter: Rodrigo Yoshima Priority: Minor My current 1.2.1 project based on seam-gen runs OK on 'test' ant target, but doesn't run via right-click on the IDE because Jboss MC doesn't find (deploy) the components on the IDE classpath. -- 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

18 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2630) Pageflow event type="node-enter" on start-page

by Krunoslav Samardzic (JIRA)

Pageflow event type="node-enter" on start-page ---------------------------------------------- Key: JBSEAM-2630 URL: http://jira.jboss.com/jira/browse/JBSEAM-2630 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Krunoslav Samardzic The problem is that actions in side event type="node-enter" on node start-page do not get called. but pageflow-2.0.xsd allows this on start-page. <?xml version="1.0"?> <pageflow-definition xmlns="http://jboss.com/products/seam/pageflow" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/pageflow http://jboss.com/products/seam/pageflow-2.0.xsd" name="kruno"> <start-page view-id="/Kruno.jsp" name="kruno"> <redirect/> <description> Kruno </description> <event type="node-enter"> <action name="start" expression="#{kruno.odradi}"></action> </event> -- 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

18 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2577) pageflow.hasTransition(...) throws NPE if not in process

by Matthew Lieder (JIRA)

pageflow.hasTransition(...) throws NPE if not in process -------------------------------------------------------- Key: JBSEAM-2577 URL: http://jira.jboss.com/jira/browse/JBSEAM-2577 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.1.GA Reporter: Matthew Lieder Priority: Minor I use pageflow.hasTransition(...) to determine which buttons to show on various pages. Some pages however may be gotten to outside of a pageflow, and in those cases merely calling that one method throws a NPE because getNode() returns null. Hence I'm having to check pageflow.isInProcess() at the beginning of those EL expressions. It would be nice if hasTransition(...) (and probably hasDefaultTransition() ) could be modified to just return false if processInstance is 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

18 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2362) from-action "equals" requires a textual match not a semantical

by koen handekyn (JIRA)

from-action "equals" requires a textual match not a semantical --------------------------------------------------------------- Key: JBSEAM-2362 URL: http://jira.jboss.com/jira/browse/JBSEAM-2362 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: koen handekyn in my facelets page i'm referring to an action as " backinBean['persist'] " ( where backingBean is a facelet tag parameter that has the value accountHome ) in pages.xml one needs to use the same litteral string within example from-action, ie DOES NOT WORK <navigation from-action="#{accountHome.persist}"> <end-conversation /> <redirect view-id="/up/admin/accountList.xhtml" /> </navigation> DOES WORK <navigation from-action="#{backingBean['persist']}"> <end-conversation /> <redirect view-id="/up/admin/accountList.xhtml" /> </navigation> this is very weird to understand from within the pages.xml as this backingBean variable does not have any specific meaning in the context. i propose that the "EQUALS" for from-action should be performed on ' evaluated EL expressions ' ( the actual method pointer on the class ). -- 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

18 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2314) Provide non-event triggering Context for use in MethodContextInterceptor as the method context

by Kahli Burke (JIRA)

Provide non-event triggering Context for use in MethodContextInterceptor as the method context ---------------------------------------------------------------------------------------------- Key: JBSEAM-2314 URL: http://jira.jboss.com/jira/browse/JBSEAM-2314 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Kahli Burke Some profiling has shown that in some cases Event triggering/handling can represent a significant chunk of page processing time. I found that Event triggering from the MethodContextInterceptor results in 10 events per method call, due to its use of the BasicContext which has pre and post set and remove events. Would a non-event triggering base class for BasicContext make sense for use as the method context? -- 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

18 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2307) Provide an integrated rich text editor control

by Shane Bryzak (JIRA)

Provide an integrated rich text editor control ---------------------------------------------- Key: JBSEAM-2307 URL: http://jira.jboss.com/jira/browse/JBSEAM-2307 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Currently we don't have one of these (and it seems that RichFaces doesn't either). We should be able to provide this easily by wrapping one of the many popular rich text editors - probably fckeditor as it supports inline image uploads (the only rich editor that does), and is available under LGPL. -- 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

18 years

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2278) Coverage targets in build.xml are instrumenting compiled classes

by Shane Bryzak (JIRA)

Coverage targets in build.xml are instrumenting compiled classes ---------------------------------------------------------------- Key: JBSEAM-2278 URL: http://jira.jboss.com/jira/browse/JBSEAM-2278 Project: JBoss Seam Issue Type: Task Reporter: Shane Bryzak The coverage targets seem to be in a bit of a mess now - I'm certain that we used to create a new, separate copy of the instrumented classes rather than overwrite the compiled classes. The way it is now is inconvenient because after running coverage you then need to run ant clean build again to build seam with non-instrumented classes. -- 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

18 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2263) Page-scoped components not accessible in jPDL page initial actions

by Matthew Lieder (JIRA)

Page-scoped components not accessible in jPDL page initial actions ------------------------------------------------------------------ Key: JBSEAM-2263 URL: http://jira.jboss.com/jira/browse/JBSEAM-2263 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.GA Reporter: Matthew Lieder See the following page declaration (selectEmployeePageBean is scoped to the page): <page name="selectEmployee" view-id="/selectEmployee.xhtml"> <action expression="#{selectEmployeePageBean.setShowDetails(true)}" /> <transition to="somewhere" /> </page> The problem is that when selectEmployee.xhtml is being rendered, selectEmployeePageBean.showDetails is false -- the bean is actually created twice, once for the action expression and again when accessed from the page renderer, and thus loses its state. I would think that the page scope should begin before the action expressions for that page are evaluated. That would allow me to easily customize pages from the pageflow definition (useful if in some places I want a "Next" button instead of "Finish", or want details to be shown in only one place, etc.) without having to make page-specific beans conversation-scoped. -- 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

18 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2211) NPE in SeamELResolver

by Pete Muir (JIRA)

NPE in SeamELResolver --------------------- Key: JBSEAM-2211 URL: http://jira.jboss.com/jira/browse/JBSEAM-2211 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR3 Reporter: Pete Muir Priority: Minor We should throw a nicer exception here -- 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

18 years

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1323) MultipartRequest class incorrectly parses form post when field boundary occurs near end of internal buffer

by ROB b (JIRA)

MultipartRequest class incorrectly parses form post when field boundary occurs near end of internal buffer ---------------------------------------------------------------------------------------------------------- Key: JBSEAM-1323 URL: http://jira.jboss.com/jira/browse/JBSEAM-1323 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA, 1.2.0.GA Environment: Windows Vista, Firefox 2.0.0, Java 1.6u1, JBoss AS 4.0.5.GA, JBoss Seam 1.2.1 Reporter: ROB b Fix For: 1.3.0.BETA1 When a form post is processed by a MultipartRequest class and it has a field boundary that occurs near the end of the internal buffer of the MultipartRequest class, it fails to recognize the field boundary and interprets the field boundary and the following header to be a part of the previous field's contents. This bug can most easily be reproduced by creating a form of enctype="multipart/form-data" with 30 <h:inputText> fields. The fields should be submitted empty. This provides form post data with lots of field boundaries and little in between. One of the field boundaries is likely to be near the end of the 2KB class buffer. When the bug occurs, one of the blank fields will be shown to contain part of the form boundary text. The form may have to be submitted 5 or 10 times, before the bug occurs. This same technique also occasionally causes the JBSEAM-1322 bug to occur (rarely, though). Sorry, I don't have a suggested fix. The class has been kind of hard for me to debug. Submitting the following XHTML source multiple times can be used to demonstrate the bug: <!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:rich="http://richfaces.ajax4jsf.org/rich" > <h:form enctype="multipart/form-data"> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:commandButton /> </h:form> </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

18 years

4
10
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 March 2008