[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3224) RememberMe autologin mode is broken
by Stefano (JIRA)
RememberMe autologin mode is broken
-----------------------------------
Key: JBSEAM-3224
URL: https://jira.jboss.org/jira/browse/JBSEAM-3224
Project: Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.1.0.A1
Environment: Ubuntu 8.04, JBoss 4.2.2, JVM 1.6.0_04, Seam 2.1 trunk as of Aug 6th 2008.
Reporter: Stefano
Setting remember-me autologin mode doesn't work.
To reproduce the problem:
- take the Seam Space example and apply the steps described in chapter 15.3.5.1 of the reference documentation.
- login with "Remember me" set
- force the autologin mechanism by deleting the JSESSIONID cookie and clicking refresh on the browser.
The following exception is logged:
org.jboss.seam.security.AuthorizationException: Authorization check failed for permission[seam.user,read]
at org.jboss.seam.security.Identity.checkPermission(Identity.java:563)
at org.jboss.seam.security.management.IdentityManager.isUserEnabled(IdentityManager.java:127)
at org.jboss.seam.security.RememberMe$1.execute(RememberMe.java:282)
at org.jboss.seam.security.Identity.runAs(Identity.java:711)
at org.jboss.seam.security.RunAsOperation.run(RunAsOperation.java:84)
at org.jboss.seam.security.RememberMe.quietLogin(RememberMe.java:278)
The problem is originated from what seems to me a typo in RunAsOperation class constructor, where the 'systemOp' flag is never set to true, regardless of the value passed.
public RunAsOperation(boolean systemOp)
{
this();
systemOp = true;
}
It should be:
this.systemOp = systemOp;
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3199) seam-gen test readme.txt jar listing needs to be updated
by Jay Balunas (JIRA)
seam-gen test readme.txt jar listing needs to be updated
--------------------------------------------------------
Key: JBSEAM-3199
URL: https://jira.jboss.org/jira/browse/JBSEAM-3199
Project: Seam
Issue Type: Task
Components: Documentation Issues
Affects Versions: 2.0.2.CR2
Reporter: Jay Balunas
Assignee: Pete Muir
Fix For: 2.0.2.GA
The readme.txt file that gets put in the seam-gen test source directory contains out of date jar files. Below is the complete readme.
Changes need (from what I can see):
- embedded-api.jar --> jboss-embedded-api.jar
- jboss-deployers.jar --> jboss-deployers-client-spi.jar, jboss-deployers-core-spi.jar
readme.txt
If you want to run tests using the Eclipse TestNG plugin, you'll need to add
these jars to the top of your TestNG classpath. Using the Run Dialog, select
xml suite to run, and add /lib/test/jboss-embedded-all.jar,
/lib/test/hibernate-all.jar, /lib/test/thirdparty-all.jar, /lib/embedded-api.jar,
/lib/jboss-deployers.jar and /bootstrap as the first entries in the User
classpath.
To add tests to your project create a TestNG xml descriptor called *Test.xml e.g.
FooTest.xml next to your test classes and run ant test.
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3309) CSV export broken
by Nicklas Karlsson (JIRA)
CSV export broken
-----------------
Key: JBSEAM-3309
URL: https://jira.jboss.org/jira/browse/JBSEAM-3309
Project: Seam
Issue Type: Bug
Components: Excel
Reporter: Nicklas Karlsson
Assignee: Daniel Roth
Fix For: 2.1.0.BETA1
Example produces:
People
Name,"Last name","Age",
Janne,"Andersson 0","0",
Janne,"Andersson 1","1",
Janne,"Andersson 2","2",
Janne,"Andersson 3","3",
Janne,"Andersson 4","4",
Janne,"Andersson 5","5",
Janne,"Andersson 6","6",
Janne,"Andersson 7","7",
Janne,"Andersson 8","8",
all in column A
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3335) port fix to trunk for glassfish jee5 example throws IllegalStateException: EJB is already associated with an incomplete transaction
by Jay Balunas (JIRA)
port fix to trunk for glassfish jee5 example throws IllegalStateException: EJB is already associated with an incomplete transaction
-----------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3335
URL: https://jira.jboss.org/jira/browse/JBSEAM-3335
Project: Seam
Issue Type: Bug
Components: Examples, Platform interoperability
Affects Versions: 2.0.2.CR2
Environment: Glassfish V2
Reporter: Jay Balunas
Assignee: Jay Balunas
Fix For: 2.0.2.GA
The app seemed to deploy fine, I could register new users, and login, change password, click the search button and book hotels.
However if I enter a character in the input box for searching hotels I would get the exception below (See attachment for full stack).
Caused by: javax.ejb.EJBException: nested exception is: java.lang.IllegalStateException: EJB is already associated with an incomplete transaction
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1266)
at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:195)
at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:83)
at $Proxy111.isNextPageAvailable(Unknown Source)
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.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:41)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
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.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54)
at org.javassist.tmp.java.lang.Object_$$_javassist_3.isNextPageAvailable(Obje
--
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
17 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3304) Blog example throws NullPointerException with message: "Argument Error: Parameter message is null"
by Jay Balunas (JIRA)
Blog example throws NullPointerException with message: "Argument Error: Parameter message is null"
--------------------------------------------------------------------------------------------------
Key: JBSEAM-3304
URL: https://jira.jboss.org/jira/browse/JBSEAM-3304
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.1.0.BETA1
Environment: windows XP and fedora
JDK5 (not tested with JDK6 yet)
jboss 4.2.3
Reporter: Jay Balunas
Fix For: 2.1.0.BETA1
Deploy the blog example and attempt to log in and you will see a seam debug message with the exception below. Everything else seems to work fine right up until this is seen. After that pretty much everything results in the same error page.
The exception is swallowed by something and is only visible if you are using DEBUG level.
Exception during request processing:
Caused by java.lang.NullPointerException with message: "Argument Error: Parameter message is null"
com.sun.faces.util.Util.notNull(Util.java:241)
com.sun.faces.context.FacesContextImpl.addMessage(FacesContextImpl.java:322)
org.jboss.seam.faces.FacesMessages.beforeRenderResponse(FacesMessages.java:48)
org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:485)
org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146)
org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116)
com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:73)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
java.lang.Thread.run(Thread.java:595)
--
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
17 years, 7 months