January 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3880) Wicket interception doesn't throw error on missing required injections

by Clint Popetz (JIRA)

Wicket interception doesn't throw error on missing required injections ----------------------------------------------------------------------- Key: JBSEAM-3880 URL: https://jira.jboss.org/jira/browse/JBSEAM-3880 Project: Seam Issue Type: Bug Reporter: Clint Popetz Assignee: Clint Popetz -- 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, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3797) ConversationInterceptor.aroundInvoke broken stacktrace

by Francisco Jose Peredo Noguez (JIRA)

ConversationInterceptor.aroundInvoke broken stacktrace ------------------------------------------------------ Key: JBSEAM-3797 URL: https://jira.jboss.org/jira/browse/JBSEAM-3797 Project: Seam Issue Type: Bug Reporter: Francisco Jose Peredo Noguez catch (Exception e) { if ( isEndConversationRequired(e) ) { endConversation(false, false); } throw e; //<---HERE! } -- 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, 4 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3881) Typo in XML in Getting_Started_With_JBoss_Tools.xml

by Ian Darwin (JIRA)

Typo in XML in Getting_Started_With_JBoss_Tools.xml --------------------------------------------------- Key: JBSEAM-3881 URL: https://jira.jboss.org/jira/browse/JBSEAM-3881 Project: Seam Issue Type: Patch Components: Documentation Issues Affects Versions: 2.1.1.GA Environment: N/A Reporter: Ian Darwin Typo in XML element. Patch attached. -- 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, 4 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3424) Support Hibernate in IdentityManager

by Scott Olcott (JIRA)

Support Hibernate in IdentityManager ------------------------------------ Key: JBSEAM-3424 URL: https://jira.jboss.org/jira/browse/JBSEAM-3424 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.BETA1 Reporter: Scott Olcott Attachments: seamspaceChanges.txt, securityChanges.txt, securityXsdChanges.txt The JpaIdentityStore could easily work with hibernate also. If you abstracted out the EntityManager and the hiberate Session from the JpaIdentityStore kind of like the AbstractEntityLoader does for the EntityConverter, you could continue to use the JpaIdentityStore for both JPA and Hibernate. Although you would probably want to rename JpaIdentityStore -- 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, 4 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3887) Allow configuration of seam components from System properties

by Clint Popetz (JIRA)

Allow configuration of seam components from System properties ------------------------------------------------------------- Key: JBSEAM-3887 URL: https://jira.jboss.org/jira/browse/JBSEAM-3887 Project: Seam Issue Type: Patch Components: Core Reporter: Clint Popetz Assignee: Clint Popetz Priority: Minor Attachments: Initialization.java.patch It is often required to push a single deployment to multiple types of servers (different testing servers, mirrors, backups, etc.), and so it would be nice to be able to configure seam components with -D on startup of the container. The attached patch looks for system properties with names like "org.jboss.seam.properties.NAME" for component NAME and treats them just like NAME=value in seam.properties. -- 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, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3000) Conversation leak with UIChart

by Tom Goring (JIRA)

Conversation leak with UIChart ------------------------------ Key: JBSEAM-3000 URL: http://jira.jboss.com/jira/browse/JBSEAM-3000 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.1.CR2 Environment: NA Reporter: Tom Goring Priority: Minor Added a chart on a page generates a long running conversation due to a bug in UIChart: UIChart public void encodeEnd(FacesContext context) .. Manager.instance().beforeRedirect(); beforeRedirect is creating a redirect conversation.. however I don't see why it needs todo this. The chart is rendered to the graphic store and then is pulled out when requiested from the browser. I think Manager.instance().beforeRedirect(); should be deleted ... but I'm not sure. -- 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, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3785) Nullcheck too soon in UIChartSeries.encodeEnd

by Francisco Jose Peredo Noguez (JIRA)

Nullcheck too soon in UIChartSeries.encodeEnd --------------------------------------------- Key: JBSEAM-3785 URL: https://jira.jboss.org/jira/browse/JBSEAM-3785 Project: Seam Issue Type: Bug Reporter: Francisco Jose Peredo Noguez Nullcheck of chart at line 144 of value previously dereferenced in org.jboss.seam.pdf.ui.UIChartSeries.encodeEnd(FacesContext) jboss-seam/src -- 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, 5 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3786) Nullcheck too late in SpringTaskExecutorDispatcher.scheduleDispatcher

by Francisco Jose Peredo Noguez (JIRA)

Nullcheck too late in SpringTaskExecutorDispatcher.scheduleDispatcher ---------------------------------------------------------------------- Key: JBSEAM-3786 URL: https://jira.jboss.org/jira/browse/JBSEAM-3786 Project: Seam Issue Type: Bug Reporter: Francisco Jose Peredo Noguez Nullcheck of SpringTaskExecutorDispatcher.scheduleDispatcher at line 64 of value previously dereferenced in org.jboss.seam.ioc.spring.SpringTaskExecutorDispatcher.getScheduleDispatcher() -- 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, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3884) Seam file upload 100% CPU in MultipartRequest

by Takayoshi Kimura (JIRA)

Seam file upload 100% CPU in MultipartRequest --------------------------------------------- Key: JBSEAM-3884 URL: https://jira.jboss.org/jira/browse/JBSEAM-3884 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: JBoss EAP 4.3.0.GA (no CP) Java VM: Java HotSpot(TM) Server VM 1.5.0_13-b05,Sun Microsystems Inc. OS-System: Linux 2.6.9-67.EL,i386 and JBoss EAP 4.2.0.GA (no CP) Java VM: Java HotSpot(TM) 64-Bit Server VM 1.5.0_12-b04,Sun Microsystems Inc. OS-System: Linux 2.6.9-34.ELsmp,amd64 Reporter: Takayoshi Kimura Sometimes org.jboss.seam.web.MultipartRequest#parseRequest() goes into an endless loop and takes 100% CPU when uploading a large file. The root cause is most likely due to the HttpServletRequest#getInputStream()#read() always returns 0. The API docs for InputStream state: "If the first byte cannot be read for any reason other than end of file, then an |IOException| is thrown. In particular, an |IOException| is thrown if the input stream has been closed." It's similar problem to RF-3746: https://jira.jboss.org/jira/browse/RF-3746 -- 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, 5 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3795) ControllerNotificationComponent.create broken stacktrace

by Francisco Jose Peredo Noguez (JIRA)

ControllerNotificationComponent.create broken stacktrace -------------------------------------------------------- Key: JBSEAM-3795 URL: https://jira.jboss.org/jira/browse/JBSEAM-3795 Project: Seam Issue Type: Bug Reporter: Francisco Jose Peredo Noguez catch (Throwable t) { throw new IllegalArgumentException("Exception installing ControllerNotificationComponent: " + t); } -- 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, 5 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2009