[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1041) Pages: isLoginRedirectRequired should be called before applying request parameter values
by Darryl Smith (JIRA)
Pages: isLoginRedirectRequired should be called before applying request parameter values
----------------------------------------------------------------------------------------
Key: JBSEAM-1041
URL: http://jira.jboss.com/jira/browse/JBSEAM-1041
Project: JBoss Seam
Issue Type: Bug
Components: Security
Affects Versions: 1.2.0.GA
Reporter: Darryl Smith
Seam will apply page parameters before it does the checks to see if login redirection is required.
This is problematic for applications rely on session scope information created in authenticator being present
e.g. using @In(scope=SESSION) currentUser, or using @In(scope=SESSION) Identity identity, or any factory that depends on identity information
12:16:53,383 ERROR [DebugPageHandler] redirecting to debug page
org.jboss.seam.RequiredException: In attribute requires non-null value: userBrowseQueryFactory.currentUser
at org.jboss.seam.Component.getValueToInject(Component.java:1887)
at org.jboss.seam.Component.injectAttributes(Component.java:1336)
at org.jboss.seam.Component.inject(Component.java:1163)
at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69)
at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:27)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:103)
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:154)
at org.jboss.seam.intercept.JavaBeanInterceptor.intercept(JavaBeanInterceptor.java:89)
at edu.uga.ais.piac.pva.action.user.UserBrowseQueryFactory$$EnhancerByCGLIB$$5ef43164.setFirstResult(<generated>)
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.apache.myfaces.el.PropertyResolverImpl.setProperty(PropertyResolverImpl.java:406)
at org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:173)
at org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:275)
at org.jboss.seam.core.Expressions$1.setValue(Expressions.java:67)
at org.jboss.seam.core.Pages.applyRequestParameterValues(Pages.java:608)
at org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:176)
at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:57)
at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70)
at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
--
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
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-947) Problem with seam component <s:fileUpload/> in JBoss Portal
by Pietro Passantini (JIRA)
Problem with seam component <s:fileUpload/> in JBoss Portal
-----------------------------------------------------------
Key: JBSEAM-947
URL: http://jira.jboss.com/jira/browse/JBSEAM-947
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.1.6.GA, 1.1.5.GA
Environment: Windows XP Pro service pack 2, I.E. and FireFox, JBossAS 4.0.5.GA, JBoss Portal 2.4.1
Reporter: Pietro Passantini
I need to upload a file to Jackrabbit Repository using Seam Framework running on Portlet, with the <s:fileUpload/> component.
It doesn't work.
I've tried different ways to solve the problem, but none worked.
It could be a bug.
It seams that when the enctype of h:form is ="multipart/form-data", the method upload of fileManager is not called; if I don't set the enctype of h:form the method upload is called, but the bean file is null.
I'm trying with this configutaration:
JSP
<h:form id="myForm" enctype="multipart/form-data" >
<s:fileUpload accept="" fileName="#{file.filename}" data="#{file.data}" />
<h:commandButton value="Upload" action="#{fileManager.upload}"/>
</h:form>
BEAN
"file" is the bean that represents the file uploaded
"fileManager" is the bean that use the file uploaded
WEB.XML
...
<filter-name>Seam Filter</filter-name>
<filter-class>org.jboss.seam.servlet.SeamMultipartFilter</filter-class>
<filter-mapping>
<filter-name>Seam Filter</filter-name>
<url-pattern>*.seam</url-pattern>
</filter-mapping>
...
--
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, 9 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-761) Modify the default interception practices
by Mike Quilleash (JIRA)
Modify the default interception practices
-----------------------------------------
Key: JBSEAM-761
URL: http://jira.jboss.com/jira/browse/JBSEAM-761
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.1.0.GA
Environment: Any.
Reporter: Mike Quilleash
Currently all methods on a Seam component will be intercepted. In some circumstances this can make debugging difficult as a lot of debuggers call toString() on objects visible from the breakpoint which executes all the Bijection incl the DisInjection which can damage the state of the object depending where the breakpoint is in the process.
Perhaps the interception logic could ignore calls to any method on the Object class so the default toString() doesn't cause problems.
Another complementary change would be to expand the @Intercept to be allowed on methods (and fields?) to allow the interception logic to be configured on individual methods (like a custom toString()) method.
--
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, 9 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1061) Support EL expressions in remoting calls
by Shane Bryzak (JIRA)
Support EL expressions in remoting calls
----------------------------------------
Key: JBSEAM-1061
URL: http://jira.jboss.com/jira/browse/JBSEAM-1061
Project: JBoss Seam
Issue Type: Feature Request
Components: Remoting
Reporter: Shane Bryzak
Assigned To: Shane Bryzak
Priority: Minor
It would be really cool to tie in EL expressions directly with Seam remoting. For example, take this method call:
Seam.Component.getInstance("helloAction").sayHello(nameValue, sayHelloCallback);
instead, this could be rewritten (and tied into the page context) like this:
Seam.Remoting.pageContext.set("name", nameValue);
Seam.Remoting.evaluate("#{helloAction.sayHello(name)}", sayHelloCallback);
This is not a perfect example, however it demonstrates the potential of this feature. Plus it makes remoting more consistent with the rest of Seam.
--
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, 9 months