July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1730) Injecting uiComponent with required = false fails with NPE if FacesContext is not available

by Daniel Young (JIRA)

Injecting uiComponent with required = false fails with NPE if FacesContext is not available ------------------------------------------------------------------------------------------- Key: JBSEAM-1730 URL: http://jira.jboss.com/jira/browse/JBSEAM-1730 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Daniel Young Assigned To: Gavin King Priority: Critical Fix For: 2.0.0.CR1 If you inject a UIComponent into a bean as follows: @In(required = false, value = "#{uiComponent['XXX']}") It fails for any method call that occurs on the bean at a time when the component is unavailable under the ViewRoot. An IllegalArgumentException is thrown by the Sun RI from UIComponentBase:588 if findComponent(id) is unsuccessful, whereas MyFaces simply returns null. This can be fixed by patching org.jboss.seam.faces.UIComponent to catch the IllegalArgumentException and return null. We were working around this by avoiding using @In for this and looking under the FacesContext.ViewRoot manually, but eventually decided to patch Seam ourselves until this issue is fixed in CVS. The above fix is working well for us. -- 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

18 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1733) A limitation in the expression language enhancements is not documented

by Wise Guy (JIRA)

A limitation in the expression language enhancements is not documented ---------------------------------------------------------------------- Key: JBSEAM-1733 URL: http://jira.jboss.com/jira/browse/JBSEAM-1733 Project: JBoss Seam Issue Type: Task Components: Documentation, EL, JSF Reporter: Wise Guy Priority: Minor There is a limitation in the expression language enhancements that is not documented. It would look like this: --- http://docs.jboss.com/seam/2.0.0.B1/reference/en/html/elenhancements.html Chapter 29. Expression language enhancements 29.1.2. Limitations 29.1.2.3. Cannot pass a variable to a MethodBinding You may not pass a variable to a MethodBinding, hence the following syntax is not valid: <ui:repeat var="curLocale" value="#{localeSelector.supportedLocales}"> <s:link value="#{curLocale.label}" action="#{localeSelector.selectLanguage(curLocale.value)}"/> </ui:repeat> Seam cannot evaluate "curLocale.value" in the rendering phase because it is a part of a MethodBinding. If you need to do implement the same functionality then use the f:param tag: <s:link value="#{curLocale.label}" action="#{localeProvider.updateLocale()}"> <f:param name="l" value="#{curLocale.value}"/> </s:link> Then, having the field variable "l" injected as a @RequestParameter, you would do this: public void updateLocale() { if (l != null && l.length() > 0) { localeSelector.selectLanguage(l); } } -- May I also point out that you should merge "29.1. Parameterized Method Bindings" and "29.2. Parameterized Value Bindings". (2.0.0.B1/reference) Thank you for the attention -- 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

18 years, 8 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1711) Allow variables to be passed into actions as parameters

by Wise Guy (JIRA)

Allow variables to be passed into actions as parameters ------------------------------------------------------- Key: JBSEAM-1711 URL: http://jira.jboss.com/jira/browse/JBSEAM-1711 Project: JBoss Seam Issue Type: Feature Request Components: EL, JSF Affects Versions: 2.0.0.BETA1 Environment: Seam 2.0.0.BETA1, Facelets Reporter: Wise Guy Priority: Minor There is a point missing in the enhancements made to the expression language. Because of this, to me, they look more like a patch than a fully functional feature. Seam allows to pass parameters to an action using EL: <s:commandButton action="#{hotelBooking.bookHotel(hotel, user)}" class="button" value="Book Hotel" /> Literal strings are also allowed: <h:commandLink action="#{printer.println('Hello world!')}" value="Hello"/> This is all specified in: Chapter 29. Expression language enhancements 29.1. Parameterized Method Bindings http://docs.jboss.com/seam/2.0.0.B1/reference/en/html/elenhancements.html This syntax, unfortunately, causes problems if you want to pass a variable created by Facelets' repeat tag. This makes it harder to create links dynamically. Let me give you the following example (same as the one in the JBoss Forum Reference): <ui:repeat var="locale" value="#{localeSelector.supportedLocales}"> <s:link value="#{locale.label}" action="#{localeSelector.selectLanguage('#{locale.value}')}"/> </ui:repeat> You cannot have an expression inside an expression so the code for the action is not valid. A workaround can be declared like this: <ui:repeat var="locale" value="#{localeSelector.supportedLocales}"> <s:link value="locale.value" action="#{localeProvider.updateLocale()}"> <f:param name="l" value="#{locale.value}"/> </s:link> </ui:repeat> public void updateLocale() { if (l != null && l.length() > 0) { localeSelector.selectLanguage(l); } } I think that a simple syntax can be elaborated in which something similar to the original idea can be used. Maybe if we use the dollar ($) sign: action="#{localeSelector.selectLanguage('${locale.value}')}" this would make sense, maybe not (Unified EL has another task assigned to that sign). But if the code is left like this, the url that is generated looks like this: http://localhost:8080/WebApp/login.seam?cid=1&actionMethod=login.xhtml%3A... -- 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

18 years, 8 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1714) WebService and JBPM

by Stefano Zaccaria (JIRA)

WebService and JBPM ------------------- Key: JBSEAM-1714 URL: http://jira.jboss.com/jira/browse/JBSEAM-1714 Project: JBoss Seam Issue Type: Bug Components: WS Affects Versions: 2.0.0.BETA1 Environment: Windows Vista and Windows XP, pentium IVht and pentium D Reporter: Stefano Zaccaria Ok Shane, I just put the "deployable code sample in JIRA". I used jboss-4.2.0GA, SEAM2.0.0B and hsqldb to make the test. I wrote a jpdl where there are two tasks node. The first task node is for a human, while the second is for the ws client ( I put the code of this too ). I try with this ws client, and It do well until I try to call the JBPM contest from seam. The human user has as user: stefano and as password: password. Now in Italy are 7.00pm and I go to home... perhaps tonight I come back to watch the forum... for now thanks for any advice. -- 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

18 years, 8 months

3
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1588) Seam Component name "session" reserved keyword

by Christoph Aigner (JIRA)

Seam Component name "session" reserved keyword ---------------------------------------------- Key: JBSEAM-1588 URL: http://jira.jboss.com/jira/browse/JBSEAM-1588 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Christoph Aigner Priority: Minor after migrating from 1.2 to 2.0 Seam throws the following error: java.lang.IllegalArgumentException: value of context variable is not an instance of the component bound to the context variable: session the error occurs when I try to inject a class: @Name("session") @Scope(ScopeType.SESSION) public class Session implements java.io.Serializable { .. in: @Stateless @Name("remoting_desktop") public class Desktop implements DesktopInterface { @In(create=true,required=false) Session session; .. worked with 1.2 as "session" is reserved -- 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

18 years, 8 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1729) Progress bar for s:fileUpload

by Yenan Zhou (JIRA)

Progress bar for s:fileUpload ----------------------------- Key: JBSEAM-1729 URL: http://jira.jboss.com/jira/browse/JBSEAM-1729 Project: JBoss Seam Issue Type: Feature Request Components: Async Affects Versions: 2.0.0.BETA1 Reporter: Yenan Zhou This is the use case: The website has users to upload very large files (probably videos), I'm trying to trace the course of the uploading by representing in browser a progress bar. But I don't know if I can do that by using s:fileUpload and how. By my understanding, s:fileUpload tag uses a filter to store the input file, and map that file to an InputStream. My concern is, because UpdateModel jsf phase is very late in the lifecycle, at the time I have accessibility to the mapped InputStream, the file has already fully uploaded to some temporary place, and I can only use this InputStream to store the file elsewhere, and I lose the control in the course of the uploading. -- 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

18 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1609) Nested conversations - potential bug in Manager.beginNestedConversation

by Wolfgang Schwendt (JIRA)

Nested conversations - potential bug in Manager.beginNestedConversation ----------------------------------------------------------------------- Key: JBSEAM-1609 URL: http://jira.jboss.com/jira/browse/JBSEAM-1609 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Wolfgang Schwendt See thread in JBoss Forum http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112414 very short summary of above thread: if @Begin(nested=true) is encountered and there is no long-running conversation in progress, Seam creates a new nested conversation which is not a long-running, but instead a temporary conversation. This behavior does not look like intended, given that beginNestedConversation() of org.jboss.seam.core.Manager contains a guard that tries to check whether a long-running conversation is in progress. The potential bug is that this guard condition is too weak, as described in JBoss forum thread mentioned above. -- 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

18 years, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1721) JSF RI wrapped commons-logging disables Hibernate commons-logging

by Christian Bauer (JIRA)

JSF RI wrapped commons-logging disables Hibernate commons-logging ----------------------------------------------------------------- Key: JBSEAM-1721 URL: http://jira.jboss.com/jira/browse/JBSEAM-1721 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Christian Bauer Hibernate uses this to log stuff: import org.apache.commons.logging.LogFactory; private static final org.apache.commons.logging.Log commonsLog = LogFactory.getLog(...); The JSF RI has a wrapped commons-logging: import com.sun.org.apache.commons.logging.LogFactory; private static final com.sun.org.apache.commons.logging.Log commonsLog = LogFactory.getLog(...); If both are on the classpath (in my case, a SeamTest unit - problem does not appear with regular WAR/EAR deployment on AS), Hibernate doesn't log anything anymore to log4j. In other words, try to get Hibernate log output in a Seam test - no go. Same if you try to use commons-logging directly in your application/unit test: it doesn't work with the normal commons-logging LogFactory, but it works if you take the com.sun wrapped LogFactory. -- 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

18 years, 8 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1718) Client Tracking within Seam, or Double Click Like Tracking with Seam

by Jim Tyrrell (JIRA)

Client Tracking within Seam, or Double Click Like Tracking with Seam -------------------------------------------------------------------- Key: JBSEAM-1718 URL: http://jira.jboss.com/jira/browse/JBSEAM-1718 Project: JBoss Seam Issue Type: Feature Request Environment: All Reporter: Jim Tyrrell I have been poking around Seam and have not found an API that would allow me to manage what Cold Fusion called Client Management. I of course found the "Remember Me" functionality, but that only creates a user with active participation of the Remote User. I am looking for a feature that would smartly manage: The Users IP address. A Client Cookie. Credentials or User Specified Information. I would then have to tie the above things and a few other things to logging of pages views, search criteria, and maybe even results counts or other things for business intelligence and user customization. >From the real world I am thinking about technology that would enable you to use Seam to write Double Click like technology to track users; Orwhen I go to Amazon even if I have never logged into the site, they giveme past search results, this allows ..."super user spyware", or as I would call it the ultimate in user personalization. I know there are scalability issues with something like this, issues with Conversations with multiple windows going on, and host of other problems. Just looking to see if anyone has some thoughts on this. -- 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

18 years, 8 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1717) Examples build.properties should have two more lines added to it

by Jim Tyrrell (JIRA)

Examples build.properties should have two more lines added to it ---------------------------------------------------------------- Key: JBSEAM-1717 URL: http://jira.jboss.com/jira/browse/JBSEAM-1717 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Environment: Linux FC 6 Seam 1.2.1.GA and JBAS 4.2.1.GA Reporter: Jim Tyrrell When running the examples I had to add in the following lines to the build.properties: jboss.ejb3.home = /home/jtyrrell/servers/jboss-4.2.1.GA jboss.ejb3.config = default Shouldn't intelligent defaults be configured in the file? Or should jboss.home now be used as the default since 4.2..onwards ships EJB 3.0? with an override for and jboss.ejb3.home if it is needed for 4.0.5 environments. We should still have a server home like the jboss.ejb3.config where you can point to default, all, etc... -- 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

18 years, 8 months

2
1
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 July 2007