April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-831) ICEfaces needs to be able to redirect from SeamExceptionFilter

by Gregory Dick (JIRA)

ICEfaces needs to be able to redirect from SeamExceptionFilter -------------------------------------------------------------- Key: JBSEAM-831 URL: http://jira.jboss.com/jira/browse/JBSEAM-831 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Environment: Seam+ICEfaces Reporter: Gregory Dick Assigned To: Gregory Dick Currently, there's no way for an ICEfaces application to integrate with the SeamExceptionFilter's redirection capability. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-834) FileUpload (Progress bar cannot with this be used as it does not seem to pass on the Conversation)

by Tony Herstell (JIRA)

FileUpload (Progress bar cannot with this be used as it does not seem to pass on the Conversation) -------------------------------------------------------------------------------------------------- Key: JBSEAM-834 URL: http://jira.jboss.com/jira/browse/JBSEAM-834 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 1.1.6.GA Reporter: Tony Herstell Assigned To: Gregory Dick Priority: Minor Don't use the progressListener  as it throws a "no long running conversation" exception in seam in the backing bean. <ice:panelGrid columns="1"> <ice:inputFile style="border:none; width:400px; height:70px;" actionListener="#{uploadController.action}"/>  <ice:outputProgress id="progress" value="#{uploadController.percent}"/> </ice:panelGrid> -- 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, 11 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-828) ICEfaces request scope behaviour needs verification

by Gregory Dick (JIRA)

ICEfaces request scope behaviour needs verification --------------------------------------------------- Key: JBSEAM-828 URL: http://jira.jboss.com/jira/browse/JBSEAM-828 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Environment: SEAM+ICEfaces Reporter: Gregory Dick Assigned To: Gregory Dick ICEfaces core behaviour needs to be verified with respect to Seam Request scope. ICEfaces application support requires, and was written to use a 'conversation like' preservation of state between requests. This can interfere with Seam's expected request scoping. Work has been done in this area, but this needs to be verified. An approach for ICEfaces in both a Seam and non-Seam environment needs to be developed -- 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, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-833) Create Seam-gen template for ICEfaces application

by Gregory Dick (JIRA)

Create Seam-gen template for ICEfaces application -------------------------------------------------- Key: JBSEAM-833 URL: http://jira.jboss.com/jira/browse/JBSEAM-833 Project: JBoss Seam Issue Type: Feature Request Components: ICE Faces Integration Environment: Seam+ICEfaces Reporter: Gregory Dick Assigned To: Gregory Dick Priority: Minor Provide an ICEfaces template for Seam-gen. -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Deleted: (JBSEAM-2898) Seam opensymphony quartz implementation doesn't offer stateful job and queue jobs!

by Christian Bauer (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2898?page=all ] Christian Bauer deleted JBSEAM-2898: ------------------------------------ > Seam opensymphony quartz implementation doesn't offer stateful job and queue jobs! > ----------------------------------------------------------------------------------- > > Key: JBSEAM-2898 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2898 > Project: Seam > Issue Type: Feature Request > Environment: JBoss 4.2.1 AS > Reporter: Stateless Bean > Priority: Critical > > I try to implement opensymphony stateful job whitch offer misfire/queue jobs and Seam hybrid doesn't offer that! > Is there any possible to implement that to next seam release? > for now I made this example but this isn't good idea: > @Asynchronous > @Transactional > public QuartzTriggerHandle scheduleMoves(@Expiration Date when, @IntervalDuration Long interval, > @FinalExpiration Date stoptime, Person person) { > try { > synchronized (EntityManager.class) { > calculatesomethink(); > > } > } > catch (EJBException e) { > log.error("processor -> scheduler(): " + e.getMessage()); > } > return 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

17 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2898) Seam opensymphony quartz implementation doesn't offer stateful job and queue jobs!

by Stateless Bean (JIRA)

Seam opensymphony quartz implementation doesn't offer stateful job and queue jobs! ----------------------------------------------------------------------------------- Key: JBSEAM-2898 URL: http://jira.jboss.com/jira/browse/JBSEAM-2898 Project: Seam Issue Type: Feature Request Components: Async Affects Versions: 2.0.1.GA Environment: JBoss 4.2.1 AS Reporter: Stateless Bean Priority: Critical Fix For: 2.0.2.GA I try to implement opensymphony stateful job whitch offer misfire/queue jobs and Seam hybrid doesn't offer that! Is there any possible to implement that to next seam release? for now I made this example but this isn't good idea: @Asynchronous @Transactional public QuartzTriggerHandle scheduleMoves(@Expiration Date when, @IntervalDuration Long interval, @FinalExpiration Date stoptime, Person person) { try { synchronized (EntityManager.class) { calculatesomethink(); } } catch (EJBException e) { log.error("processor -> scheduler(): " + e.getMessage()); } return 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

17 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-655) Control log levels from debug page

by Gavin King (JIRA)

Control log levels from debug page ---------------------------------- Key: JBSEAM-655 URL: http://jira.jboss.com/jira/browse/JBSEAM-655 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Priority: Minor It would be good to be able to dynamically control log categories from the seam debug page. -- 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, 12 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2894) In the SeamPhaseListener raise an event for the jsf RESTORE_VIEW phase after initializing the seam contexts

by pieter martin (JIRA)

In the SeamPhaseListener raise an event for the jsf RESTORE_VIEW phase after initializing the seam contexts ----------------------------------------------------------------------------------------------------------- Key: JBSEAM-2894 URL: http://jira.jboss.com/jira/browse/JBSEAM-2894 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1 Environment: linux jboss Reporter: pieter martin Currently the "org.jboss.seam.afterPhase" event is raised before the seam contexts are initialized which means that seam components can not observe the event. I.e. In SeamPhaseListerner public void afterPhase(PhaseEvent event) { log.trace( "after phase: " + event.getPhaseId() ); try { raiseEventsAfterPhase(event); if ( isPortletRequest(event) ) { afterPortletPhase(event); } else { //The seam contexts get init here afterServletPhase(event); } //RAISE ANOTHER EVENT HERE raiseEventsAfterPhaseAfterInitContext(event); } catch (Exception e) ..... -- 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, 12 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2821) Page two of hotels list is empty when page size is 20 on all Booking examples

by Jay Balunas (JIRA)

Page two of hotels list is empty when page size is 20 on all Booking examples ----------------------------------------------------------------------------- Key: JBSEAM-2821 URL: http://jira.jboss.com/jira/browse/JBSEAM-2821 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Priority: Minor When on the main search page of any of the booking examples (Booking, JPA, hibernate, etc...) - change the page size to 20 and click "find hotels" with no search. - You should see a full listing of hotels. - Click on "More results" and the next page will show "No matching hotels". This is probably a minor tweak to the way the page counts are determined. -- 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, 12 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2892) Bad usage of List.get() in EntityBeanList.class

by Benjamin Graf (JIRA)

Bad usage of List.get() in EntityBeanList.class ----------------------------------------------- Key: JBSEAM-2892 URL: http://jira.jboss.com/jira/browse/JBSEAM-2892 Project: Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Benjamin Graf The passivateAll() method does an iteration over a list of to passivated entities. But the implementation uses the get-method of the list interface which has very bad performance on LinkedList. It should better use the list-iterator instead! -- 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, 12 months

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