January 2009 - 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

14 years, 7 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

14 years, 7 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, 7 months

4
10
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

14 years, 7 months

3
8
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

14 years, 7 months

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

14 years, 8 months

6
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2186) RichFaces loses skin with login-required="true" in pages.xml

by Justin C (JIRA)

RichFaces loses skin with login-required="true" in pages.xml ------------------------------------------------------------ Key: JBSEAM-2186 URL: http://jira.jboss.com/jira/browse/JBSEAM-2186 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR3 Environment: Windows XP Professional, Java 1.6_03, JBoss 4.2.1 Reporter: Justin C Create a new project via seam-gen. Generate some GRUD screens using generate-entities. Folow the seam-gen section in the Reference manual to do this. Edit pages.xml and set attribute login-required="true" for the <page view-id="*"> node. Do a seam explode and start the appserver. Access the url for the app, this will direct to the login screen, to say that login is required. Login, and access the CRUD screens. Logout. Access a CRUD List screen from the menu. This will show a cached screen, not the login screen, as is expected. Refresh the screen from the browser. This directs to the login screen, but the RichFaces CSS skin is gone permamently. -- 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, 8 months

11
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2613) Allow to save Seam generated PDF to a file on the server side

by Terry (JIRA)

Allow to save Seam generated PDF to a file on the server side ------------------------------------------------------------- Key: JBSEAM-2613 URL: http://jira.jboss.com/jira/browse/JBSEAM-2613 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.1.GA Reporter: Terry Priority: Minor Fix For: 2.1.x Currently there is no easy way to save PDF generated by Seam template to store in a file on the server side. Perhaps Seam can provide access to prepared PDF stream, which can be be used in a user bean to write to a path/file as needed. -- 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, 8 months

8
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3629) Since Seam v2.1.0, httpServletRequest.getUserPrincipal() is always returning null when using plain J2EE security

by Denis Forveille (JIRA)

Since Seam v2.1.0, httpServletRequest.getUserPrincipal() is always returning null when using plain J2EE security ---------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3629 URL: https://jira.jboss.org/jira/browse/JBSEAM-3629 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.GA Environment: Seam v2.1.0GA, WebSphere v6.1.0.17 (Without EJB3 FP), RF v3.2.2, facelets 1.1.14, JSF RI 1.2_09 Reporter: Denis Forveille Priority: Critical Since v2.1.GA, it is not possible to use plain J2EE security. Now, httpServletRequest.getUserPrincipal() always return null and also @In UserPrincipal principal; does not work This is not working because the http request is wrapped in IdentityRequestWrapper (in IdentityFilter) and its getUserPrincipal() method is reading principal variable on Identity component. httpServletRequest.getUserPrincipal() should work when seam security is not use, and so we should have a way to "disable" Seam security -- 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, 8 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-977) Invoking Seam Email render from a page containing Icefaces tags creates render exception

by Karthikeyan Pattabiraman (JIRA)

Invoking Seam Email render from a page containing Icefaces tags creates render exception ---------------------------------------------------------------------------------------- Key: JBSEAM-977 URL: http://jira.jboss.com/jira/browse/JBSEAM-977 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Environment: Windows XP, JDk 5.0, JBoss AP, JBoss Seam, Facelets, IceFaces Reporter: Karthikeyan Pattabiraman Assigned To: Gregory Dick When I invoke Seam E-mail functionality from an Iceface page containing menu Items to the child level (to any level) causes the following exception: Error send mail java.lang.NullPointerException: at com.icesoft.faces.component.menubar.MenuItemRenderer.renderChildrenRecursive(MenuItemRenderer.java:382) at com.icesoft.faces.component.menubar.MenuItemRenderer.encodeBegin(MenuItemRenderer.java:185) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:512) at com.icesoft.faces.renderkit.dom_html_basic.DomBasicRenderer.encodeParentAndChildren(DomBasicRenderer.java:339) at com.icesoft.faces.component.menubar.MenuBarRenderer.encodeChildren(MenuBarRenderer.java:94) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:524) at com.icesoft.faces.renderkit.dom_html_basic.DomBasicRenderer.encodeParentAndChildren(DomBasicRenderer.java:341) at com.icesoft.faces.renderkit.dom_html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:97) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:524) at org.jboss.seam.ui.JSF.renderChild(JSF.java:174) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.JSF.renderChild(JSF.java:177) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.facelet.FaceletsRenderer.renderFacelet(FaceletsRenderer.java:106) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:54) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:38) When I remove the child Items (the page still contains other iceFaces tags), the issue leads me staright to issue # JBSEAM-827. Hence I am not able to use Seam E-mail with ICEFaces together. Things I used: ============ mail Template (same as it is in Seam Examples): <m:message xmlns="http://www.w3.org/1999/xhtml" xmlns:m="http://jboss.com/products/seam/mail" xmlns:h="http://java.sun.com/jsf/html"> <m:from name="Peter" address="peter(a)example.com" /> <m:to name="#{person.firstname} #{person.lastname}">#{person.address}</m:to> <m:subject>Try out Seam!</m:subject> <m:body> <h:outputText value="Dear #{person.firstname}" />, You can try out Seam by visiting <a href="http://labs.jboss.com/jbossseam">http://labs.jboss.com/jbossseam</a>. Regards Peter </m:body> </m:message> menu Items: ============= <ice:form id="menu" xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:ice="http://www.icesoft.com/icefaces/component"> <ice:panelGroup id="menupanel" styleClass="formBorderHighlight"> <ice:menuBar id="menubar" orientation="horizontal"> <ice:menuItem value="Parent 1"> <ice:menuItem value="Child 1" /> </ice:menuItem> </ice:menuBar> </ice:panelGroup> </ice:form> -- 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, 9 months

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2009