June 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4636) tasks_jboss5.editTurtleTask fails

by Jozef Hartinger (JIRA)

tasks_jboss5.editTurtleTask fails --------------------------------- Key: JBSEAM-4636 URL: https://jira.jboss.org/jira/browse/JBSEAM-4636 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.1.CR1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.2.1.CR2 ERROR: Option with value 'School' not found Stacktrace com.thoughtworks.selenium.SeleniumException: ERROR: Option with value 'School' not found at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at com.thoughtworks.selenium.DefaultSelenium.select(DefaultSelenium.java:315) at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.editTask(SeleniumTasksTest.java:277) at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.editTurtleTask(SeleniumTasksTest.java:129) ... Removed 22 stack frames -- 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

14 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4666) QueueConnection.stop() can not be called from an EJB containrer as stated in JEE5 spec section EE 6.6

by Denis Forveille (JIRA)

QueueConnection.stop() can not be called from an EJB containrer as stated in JEE5 spec section EE 6.6 ----------------------------------------------------------------------------------------------------- Key: JBSEAM-4666 URL: https://jira.jboss.org/browse/JBSEAM-4666 Project: Seam Issue Type: Bug Components: Async Affects Versions: 2.2.1.CR1 Environment: WebSphere v7.0.0.9 Reporter: Denis Forveille Assignee: Denis Forveille Priority: Minor Fix For: 2.2.1.CR2 In WebSphere, when the application "shuts down", the method annotated by @Destroy is called on the QueueConnection seam component. This method raise an exception on the queueConnection.stop() call It is illegal to do so from an EJB container as specified in the JEE5 specs section EE 6.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4629) Disable default behaviour of auto-save for process instances

by Tihomir Surdilovic (JIRA)

Disable default behaviour of auto-save for process instances ------------------------------------------------------------ Key: JBSEAM-4629 URL: https://jira.jboss.org/jira/browse/JBSEAM-4629 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR1 Reporter: Tihomir Surdilovic When injecting org.jboss.seam.bpm.ProcessInstance in a Seam components the code ends up in the following code snipped of this class: ******** if (processId!=null) { //TODO: do we need to cache this?? return ManagedJbpmContext.instance().getProcessInstanceForUpdate(processId); } ******** the org.jbpm.JbpmContext#getProcessInstanceForUpdate(processId) method will get a process instance from the db and will register it for auto-save. It will then be saved automatically at the close() . Continuous registering for auto-save can cause performance issues as when the jbpmContext closes it will save all instances in the autoSaveProcessInstances list which can be huge. The proposed fix is to change to the code to: if (processId!=null) { return ManagedJbpmContext.instance().getProcessInstance(processId); } -- 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

14 years, 5 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2974) <s:fileUpload> doesnt work inside <h:dataTable>

by Denis Forveille (JIRA)

<s:fileUpload> doesnt work inside <h:dataTable> ----------------------------------------------- Key: JBSEAM-2974 URL: http://jira.jboss.com/jira/browse/JBSEAM-2974 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR2 Reporter: Denis Forveille (see the forum entry in ref) -- 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

14 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4583) Update Portlet Bridge and GateIn release instructions

by Karel Piwko (JIRA)

Update Portlet Bridge and GateIn release instructions ----------------------------------------------------- Key: JBSEAM-4583 URL: https://jira.jboss.org/jira/browse/JBSEAM-4583 Project: Seam Issue Type: Task Affects Versions: 2.2.0.GA Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 2.2.1.CR2 Update to match current status. -- 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

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4669) Major java deadlock between BijectionInterceptor and Component since the getInstanceFromFactory method is synchronized

by Denis Forveille (JIRA)

Major java deadlock between BijectionInterceptor and Component since the getInstanceFromFactory method is synchronized ----------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4669 URL: https://jira.jboss.org/browse/JBSEAM-4669 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.1.CR2 Reporter: Denis Forveille Assignee: Denis Forveille Priority: Blocker Fix For: 2.2.1.CR2 To address JBSEAM-2419, the Component.getInstanceFromFactory(String name) is now "synchronized" This causes java deadlocks under stress with the call to lock.lock() in BinjectionInterceptor ... For us our apps freezes after 10 minutes in production,,, I don't know why this method has been marked as synchronized but this is the cause of the deadlock... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBSEAM-4593) AbstractSeamTest.Request.run() should call "afterRequest()" before facesContext.release()

by Michael Youngstrom (JIRA)

AbstractSeamTest.Request.run() should call "afterRequest()" before facesContext.release() ----------------------------------------------------------------------------------------- Key: JBSEAM-4593 URL: https://jira.jboss.org/jira/browse/JBSEAM-4593 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Reporter: Michael Youngstrom Assignee: Michael Youngstrom Fix For: 2.2.1.CR2 AbstractSeamTest.Request.run() should call "afterRequest()" before facesContext.release() in case the afterRequest() wishes to assert on the state of the FacesContext. The only way for afterRequest to get access to the facesContext is through FacesContext.currentInstance(). Plus this would match the init()->beforeRequest() facesContext existence scoping. -- 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

14 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3769) org.jboss.seam.ui.facelet.RendererRequest replaces HttpServletXXX with MockHttpServletXXX

by Kenneth Christensen (JIRA)

org.jboss.seam.ui.facelet.RendererRequest replaces HttpServletXXX with MockHttpServletXXX ----------------------------------------------------------------------------------------- Key: JBSEAM-3769 URL: https://jira.jboss.org/jira/browse/JBSEAM-3769 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.1.CR1 Environment: Mac OS X 10.5.5 JBoss AS 4.2.3.GA JBoss Seam 2.1.1.CR1 Java 6 Reporter: Kenneth Christensen Seam 2.0.3: private void init() { // Make sure we are using the correct ClassLoader originalClassLoader = Thread.currentThread().getContextClassLoader(); Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader()); // If a FacesContext isn't available, set one up if (FacesContext.getCurrentInstance() == null) { MockFacesContext mockFacesContext = new MockFacesContext(new MockExternalContext(new MockServletContext())) .setCurrent(); mockFacesContext.createViewRoot(); } FacesContext facesContext = FacesContext.getCurrentInstance(); // Wrap the ResponseWriter originalResponseWriter = facesContext.getResponseWriter(); facesContext.setResponseWriter(facesContext.getRenderKit().createResponseWriter(writer, null, null)); // Create a new UIViewRoot originalViewRoot = facesContext.getViewRoot(); UIViewRoot viewRoot = new UIViewRoot(); viewRoot.setRenderKitId(facesContext.getApplication().getViewHandler().calculateRenderKitId(facesContext)); viewRoot.setViewId(viewId); viewRoot.setLocale(originalViewRoot.getLocale()); facesContext.setViewRoot(viewRoot); } Seam 2.1.1.CR1: private void init() { request = new MockHttpServletRequest(HttpSessionManager.instance()); response = new MockHttpServletResponse(); // Generate the FacesContext from the JSF FacesContextFactory originalFacesContext = FacesContext.getCurrentInstance(); facesContext = RendererFacesContextFactory.instance().getFacesContext(request, response); DelegatingFacesContext.setCurrentInstance(facesContext); // Create the viewRoot UIViewRoot newRoot = facesContext.getApplication().getViewHandler().createView(facesContext, viewId); facesContext.setViewRoot(newRoot); // Set the responseWriter to write to a buffer writer = new StringWriter(); facesContext.setResponseWriter(facesContext.getRenderKit().createResponseWriter(writer, null, null)); } As you can see, Seam 2.1.1.CR1 never checks for the original FacesContext, but creates a new FacesContext which includes the MockHttpServletXXX. It's a problem for the application I'm developing, because I need the external context (HttpServletResponse) when I'm using the renderer.render("/abc/xyz.xhtml"). It works fine with Seam 2.0.3, but not with Seam 2.1. -- 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

14 years, 5 months

7
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3035) upgrade to Spring JAR to version 2.5

by Dan Allen (JIRA)

upgrade to Spring JAR to version 2.5 ------------------------------------ Key: JBSEAM-3035 URL: http://jira.jboss.com/jira/browse/JBSEAM-3035 Project: Seam Issue Type: Feature Request Components: Build Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.2.SP1, 2.1.0.BETA1 Without the Spring 2.5 JAR, the org.springframework.web.jsf.el.SpringBeanFacesELResolver is not available. Spring 2.5 is backward compliant, so there should be no reason we are holding back. -- 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

14 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBSEAM-4592) jboss-seam-resteasy.jar not copied to a new seam-gen project

by Jozef Hartinger (JIRA)

jboss-seam-resteasy.jar not copied to a new seam-gen project ------------------------------------------------------------ Key: JBSEAM-4592 URL: https://jira.jboss.org/jira/browse/JBSEAM-4592 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.2.1.CR1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger jboss-seam-resteasy.jar is not copied to the lib folder of a newly created seam-gen project, while other related libraries are (resteasy-jaxrs.jar, etc...) -- 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

14 years, 5 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2010