February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2591) page actions fail under load testing

by Samuel Mendenhall (JIRA)

page actions fail under load testing ------------------------------------ Key: JBSEAM-2591 URL: http://jira.jboss.com/jira/browse/JBSEAM-2591 Project: JBoss Seam Issue Type: Bug Reporter: Samuel Mendenhall Priority: Critical Page actions fail to be invoked when load testing multiple requests simultaneously. Pages actions do correctly get processed when those requests are given an interval between executions, thus not concurrent. Code for reproduction: <page view-id="/home.xhtml" login-required="false"> <action execute="#{someComponent.someMethod}"/> </page> @Name("someComponent") public class SomeComponent { @Logger private Log log; @In FacesMessages facesMessages; public void someMethod() { log.info("someComponent:someMethod invoked at " + Calendar.getInstance().getTime()); facesMessages.add("someComponent:someMethod invoked at " + Calendar.getInstance().getTime()); } } There is on average of between 1-3 failed actions per 20 concurrent requests from initial analysis. The failed action presents absolutely no exception, the method is just not called, no log message in the console, and no FacesMessage added. jMeter script and screens attached. -- 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, 8 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2500) <p:html> does not work as a child of a <p:cell>

by Darryl Smith (JIRA)

<p:html> does not work as a child of a <p:cell> ----------------------------------------------- Key: JBSEAM-2500 URL: http://jira.jboss.com/jira/browse/JBSEAM-2500 Project: JBoss Seam Issue Type: Bug Components: PDF Affects Versions: 2.0.1.CR1 Reporter: Darryl Smith order / unordered list and tables do not work when added as a child of <p:cell> UIHTMLText places the collection of HTML elements within a Paragraph. UICell 's handleAdd method adds it as a phrase. The correct way would to be add each HTML element to cell e.g. for each element from HTMLWorker.parse pcell.addElement(element) In addition, italicized Seam Text does not work regardless of where it is put. -- 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, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1165) RGB color support for pdf

by Dustin Norlander (JIRA)

RGB color support for pdf ------------------------- Key: JBSEAM-1165 URL: http://jira.jboss.com/jira/browse/JBSEAM-1165 Project: JBoss Seam Issue Type: Feature Request Components: PDF Reporter: Dustin Norlander Support colors of the form: rgb(255,0,0) or rgb(100%, 0%, 0%) -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-683) Allow components.xml XSDs to be packaged in the jar with the components.

by Gavin King (JIRA)

Allow components.xml XSDs to be packaged in the jar with the components. ------------------------------------------------------------------------- Key: JBSEAM-683 URL: http://jira.jboss.com/jira/browse/JBSEAM-683 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Norman Richards Priority: Blocker Fix For: 1.1.5.GA Currently seam resolves XSDs in the path org/jboss/seam. But it would be better if the XSD for org.jboss.seam.core was located in the org/jboss/seam/core directory. This issue shows up with the mail stuff.... -- 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, 8 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2587) XSD cleanup

by Norman Richards (JIRA)

XSD cleanup ----------- Key: JBSEAM-2587 URL: http://jira.jboss.com/jira/browse/JBSEAM-2587 Project: JBoss Seam Issue Type: Task Reporter: Norman Richards Assigned To: Norman Richards Priority: Minor Fix For: 2.1.0.GA With 2.1, we can fix up the schemas a bit. The schemas could use some documentation, and there are places where the type info could be better. (xs:boolean being one example) -- 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, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1370) Turn "JBoss Seam Debug Page" heading into a link

by Dan Allen (JIRA)

Turn "JBoss Seam Debug Page" heading into a link ------------------------------------------------ Key: JBSEAM-1370 URL: http://jira.jboss.com/jira/browse/JBSEAM-1370 Project: JBoss Seam Issue Type: Patch Components: JSF Affects Versions: 1.2.1.GA Environment: n/a Reporter: Dan Allen Priority: Minor The first-level heading of the Seam debug page should be a link. This link would clear any selections and show the page in its initial state. I find myself constantly having to rip the query string off of the debug page URL in the location bar of my browser to return to the initial state. This link would be a convenient way to go to the debug page "home." -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-629) support actionListener on s:link

by Norman Richards (JIRA)

support actionListener on s:link -------------------------------- Key: JBSEAM-629 URL: http://jira.jboss.com/jira/browse/JBSEAM-629 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards Users have requested actionListener support on s:link and s:button. -- 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, 8 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2309) UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback()

by Denis Forveille (JIRA)

UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback() ------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-2309 URL: http://jira.jboss.com/jira/browse/JBSEAM-2309 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA, 1.2.1.GA Reporter: Denis Forveille In the org.jboss.seam.util.Work class, the call to userTransaction.commit() is surrounded by a try/catch(Exception). In the catch block, if an exception occurs during the commit, a UserTransaction.rollback() is attempted. This may fail as the UserTransaction.commit() may throw a RollbackException, and in that case the UserTransaction ihas already been rollbacked. So an attempt to perform a rollback on the UserTransaction result in an illegalstate exception. This happens to us when something goes wrong in the beforeCommit() methods and hibernate throws a StaleObjectStateException() We use seam 1.2.1 + POJO + WebSphere v61.0..13 The code could be something like this (Class Work.java): try { T result = work(); if (begin) { log.debug("committing transaction"); userTransaction.commit(); } return result; } catch (Exception e) { if (begin) { log.debug("rolling back transaction"); if (userTransaction.getStatus() != STATUS_NO_TRANSACTION) { userTransaction.rollback(); } } throw e; } Or the code could explicitely catch the RollbackException This could be applied at any place in the code when a UserTransaction.commit() is called. -- 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, 9 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-884) ICEFaces dataPaginator causes duplicate ID exception

by henrik lindberg (JIRA)

ICEFaces dataPaginator causes duplicate ID exception ---------------------------------------------------- Key: JBSEAM-884 URL: http://jira.jboss.com/jira/browse/JBSEAM-884 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 1.1.6.GA Environment: Seam 1.1.6.GA, ICEFaces 1.5.3 Reporter: henrik lindberg Assigned To: Gregory Dick Priority: Critical When using a data paginator with a data table duplicate ids are created for all paginator facets except the first added facet. The attached code illustrates the problem. Use the facelet to add test data, a duplicate id exception is thrown when a new test data is added. Refresh the page (using browser) to see that data was added, try to add another (refresh again). Editing out all facets for the paginator except one makes the code work. -- 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, 9 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-832) ICEfaces demonstration application

by Gregory Dick (JIRA)

ICEfaces demonstration application ----------------------------------- Key: JBSEAM-832 URL: http://jira.jboss.com/jira/browse/JBSEAM-832 Project: JBoss Seam Issue Type: Feature Request Components: ICE Faces Integration Environment: Seam+ICEfaces Reporter: Gregory Dick Assigned To: Gregory Dick Priority: Minor Create an example application with a more compelling ICEfaces feature set properly illustrating Seam and ICEfaces capabilities. -- 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, 9 months

5
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008