January 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, 8 months

4
9
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, 8 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

15 years, 8 months

4
10
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, 8 months

3
4
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, 8 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, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4039) Seam component cannot serve as a JAX-RS subresource

by Jozef Hartinger (JIRA)

Seam component cannot serve as a JAX-RS subresource --------------------------------------------------- Key: JBSEAM-4039 URL: https://jira.jboss.org/jira/browse/JBSEAM-4039 Project: Seam Issue Type: Bug Components: WS Reporter: Jozef Hartinger Assignee: Christian Bauer When Seam component is returned as a subresource, RESTEasy scans it's javassist proxy for JAX-RS annotations. It should however scan the actual component's class instead. Following snippet: @Path("/{username}/{context}") public ContextResource getContextResource(@PathParam("username")String username) { ... return (ContextResource) Component.getInstance("contextResource"); } causes LoggableException with message: Subresource for target class has no jax-rs annotations.: org.jboss.seam.example.rest.resource.ContextResource_$$_javassist_seam_9 -- 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, 8 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2419) IAE: factory method with defined scope outjected a value: guestRole

by Christian Bauer (JIRA)

IAE: factory method with defined scope outjected a value: guestRole ------------------------------------------------------------------- Key: JBSEAM-2419 URL: http://jira.jboss.com/jira/browse/JBSEAM-2419 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Christian Bauer Priority: Minor I can see this on the log on seamframework.org but can't reproduce it: java.lang.IllegalArgumentException: factory method with defined scope outjected a value: guestRole at org.jboss.seam.Component.handleFactoryMethodResult(Component.java:1953) at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1927) at org.jboss.seam.Component.getInstance(Component.java:1863) at org.jboss.seam.Component.getInstance(Component.java:1840) at org.jboss.seam.Component.getInstance(Component.java:1834) at org.jboss.seam.wiki.core.action.Authenticator.getGuestAccessLevel(Authenticator.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.seam.wiki.core.action.Authenticator_$$_javassist_9.getGuestAccessLevel(Authenticator_$$_javassist_9.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2082) at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1926) at org.jboss.seam.Component.getInstance(Component.java:1863) at org.jboss.seam.Component.getInstance(Component.java:1840) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:111) at org.jboss.seam.persistence.HibernatePersistenceProvider.enableFilter(HibernatePersistenceProvider.java:205) at org.jboss.seam.persistence.ManagedPersistenceContext.initEntityManager(ManagedPersistenceContext.java:88) at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManager(ManagedPersistenceContext.java:108) This is thrown from the FeedServlet. The code doesn't do what the exception says it is doing: /** * Assigns the context variable 'currentAccessLevel' when no user is logged in. * @return Integer Guest access level. */ @Factory(value = "currentAccessLevel", scope = ScopeType.SESSION, autoCreate = true) public Integer getGuestAccessLevel() { return ((Role)Component.getInstance("guestRole")).getAccessLevel(); } This has to be investigated further. -- 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, 8 months

10
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4273) edit.xhtml.ftl template cause duplicate id changeParent and selectParent

by Julien Kronegg (JIRA)

edit.xhtml.ftl template cause duplicate id changeParent and selectParent ------------------------------------------------------------------------ Key: JBSEAM-4273 URL: https://jira.jboss.org/jira/browse/JBSEAM-4273 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.2.GA Environment: SEAM_HOME/seam-gen/view/edit.xhtml.ftl Reporter: Julien Kronegg When a MyEntityEdit.xhtml page with more than one foreign key is generated, the "Select" / "Change" button is generated with an id "changeParent" or "selectParent" for each foreign key. This causes "duplicate id" errors when displaying the page. The button id must be changed to be unique, e.g. by suffixing with the property name. The line 136: <s:button id="${'#'}{${homeName}.instance.${property.name} != null ? 'changeParent' : 'selectParent'}" value="${'#'}{${homeName}.instance.${property.name} != null ? 'Change' : 'Select'} ${property.name}" must be replaced by: <s:button id="${'#'}{${homeName}.instance.${property.name} != null ? 'changeParent${property.name?cap_first} ' : 'selectParent${property.name?cap_first}'}" value="${'#'}{${homeName}.instance.${property.name} != null ? 'Change' : 'Select'} ${property.name}" I did not find references to the button id elsewhere, so it seems that no side effect will appear. -- 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, 8 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2504) define different login-view-ids on page element of pages.xml

by Phil Haigh (JIRA)

define different login-view-ids on page element of pages.xml ------------------------------------------------------------ Key: JBSEAM-2504 URL: http://jira.jboss.com/jira/browse/JBSEAM-2504 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Phil Haigh Allowing specification of different login view ids for page elements in pages.xml There must be many examples of applications where this would be of use - for example, a system that has a customer facing front end, and a staff-only backend: Code: <page view-id="/backend/*" login-required="true" login-view-id="/backendlogin.xhtml" > </page> <page view-id="/members/*" login-required="true" login-view-id="/login.xhtml" > </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

15 years, 8 months

6
10
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 January 2010