March 2010 - seam-issues - Jboss List Archives

[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

15 years, 3 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

15 years, 3 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

15 years, 3 months

7
24
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

15 years, 3 months

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

15 years, 3 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

15 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4461) small typo/mistake in reference manual

by Wolfgang Schwendt (JIRA)

small typo/mistake in reference manual -------------------------------------- Key: JBSEAM-4461 URL: https://jira.jboss.org/jira/browse/JBSEAM-4461 Project: Seam Issue Type: Patch Affects Versions: 2.2.0.GA Reporter: Wolfgang Schwendt Priority: Trivial just for the sake of correctness. In the reference manual, chapter 30 (configuring seam), it must read "public interface Authenticator", not "public class Authenticator" -- 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, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4590) Multiple war in ear - resources not isolated between wars

by Susanne Jarl (JIRA)

Multiple war in ear - resources not isolated between wars ---------------------------------------------------------- Key: JBSEAM-4590 URL: https://jira.jboss.org/jira/browse/JBSEAM-4590 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: JBoss 5.1.0.GA, Hot deployment. JDK 1.6 Reporter: Susanne Jarl If you have a.war and b.war in an ear and try to send an email using org.jboss.seam.faces.Renderer this will only work for b.war and in a.war you will get an exception saying that the resource in b.war could not be found. So the renderer called from a.war looks for resources in b.war. Kind of the same problem with s.graphicImage, only working in b.war, and when used in a.war the exception says it is looking for resources in b.war. I use hot deployment. If I start my application with only one of the war files at the time everything works perfectly fine. These issues did not exist in version 2.0.X, they appeared in 2.1. and has been around since then although changed a little between versions. I have also tried 2.2.1. nightly build #164, since I thought that JBSEAM-4316 might solve this, but unfortunatally it did not. I have in each war a jboss-web.xml looking like this example (with of course different unique names): <jboss-web> <class-loading java2ClassLoadingCompliance="false"> <loader-repository> org.jboss.seam:archive=uniquename <loader-repository-config>java2ParentDelegation=false</loader-repository-config> </loader-repository> </class-loading> </jboss-web> jboss-app.xml looks like this: <jboss-app> <loader-repository> org.jboss.seam:archive=myapp <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </jboss-app> Please solve this bug until next release. Thank you! -- 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, 3 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2512) Default configuration option for begins to use flushmode=MANUAL

by Jacob Orshalick (JIRA)

Default configuration option for begins to use flushmode=MANUAL --------------------------------------------------------------- Key: JBSEAM-2512 URL: http://jira.jboss.com/jira/browse/JBSEAM-2512 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick It would be nice to provide a way to globally configure the flushmode setting. Say, a way to configure begins to use flushmode=MANUAL by default. Maybe this could be configured in components.xml. This would save a lot of what is generally boilerplate configuration since this is common usage. Perhaps, I could specify: <core:manager conversation-flushmode="MANUAL" /> -- 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, 3 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3975) Load jBPM Process Def from the DB/Repo

by Burr Sutter (JIRA)

Load jBPM Process Def from the DB/Repo -------------------------------------- Key: JBSEAM-3975 URL: https://jira.jboss.org/jira/browse/JBSEAM-3975 Project: Seam Issue Type: Feature Request Components: BPM Reporter: Burr Sutter What about loading up process defs from their "normal" location, the database? jBPM has a "repository" that stores process instance state for long running processes as well as it versions the definitions, Seam should be able to load the process def not only from the .ear/classpath but also from the repo. -- 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, 3 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2010