April 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-10) JSF API producers (FacesContext, ExternalContext, NavigationHandler, etc...)

by Lincoln Baxter III (JIRA)

JSF API producers (FacesContext, ExternalContext, NavigationHandler, etc...) ---------------------------------------------------------------------------- Key: SEAMFACES-10 URL: https://jira.jboss.org/jira/browse/SEAMFACES-10 Project: Seam Faces Issue Type: Feature Request Components: JSF CDI Integration Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 3.0.0.Alpha1 Provide @Inject support for JSF lifecycle artifacts. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFACES-13) Seam Faces module does not compile on Java 5

by Jozef Hartinger (JIRA)

Seam Faces module does not compile on Java 5 -------------------------------------------- Key: SEAMFACES-13 URL: https://jira.jboss.org/jira/browse/SEAMFACES-13 Project: Seam Faces Issue Type: Bug Environment: Java 1.5.0_19 Apache Maven 2.2.1 Reporter: Jozef Hartinger Fix For: 3.0.0.Alpha1 Besides that target specified in pom.xml, compilation fails with [INFO] Compilation failure /home/jharting/jboss/Seam_3/modules/faces/impl/src/main/java/org/jboss/seam/faces/cdi/JndiBeanManagerProvider.java:[46,4] method does not override a method from its superclass /home/jharting/jboss/Seam_3/modules/faces/impl/src/main/java/org/jboss/seam/faces/cdi/ServletContextBeanManagerProvider.java:[38,4] method does not override a method from its superclass -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3086) Allow unproxied components in components.xml

by Luke Maurer (JIRA)

Allow unproxied components in components.xml -------------------------------------------- Key: JBSEAM-3086 URL: http://jira.jboss.com/jira/browse/JBSEAM-3086 Project: Seam Issue Type: Feature Request Components: Core Reporter: Luke Maurer It would be very convenient to be able to define a "component" in components.xml without actually having it be wrapped in a proxy, in cases where I just want to have an object put into application context and have a few setters called on it, but don't need any interceptors installed. For a use case, see http://www.jasypt.org/hibernate3.html (the "Providing the encryptor to Hibernate" section) - instructions are given for a convenient way to configure the library using Spring, even though the classes in question (StandardPBEStringEncryptor and HibernatePBEStringEncryptor) were not written as Spring beans. The equivalent code in Seam components.xml does not work, since Seam attempts to proxy the objects, and the classes are final (Javassist throws a CannotCompileException). Since none of the functionality offered by proxies is required, in principle the only requirement to make this work would be a way to turn off proxying. (Presumably Spring does so automatically here.) Naturally, there is a perfectly good workaround, which would be to use a @Factory or @Unwrap method on a Seam component and include setter methods to do the configuration. But this is a lot of tedious glue code, and I find the idea of directly configuring the objects in components.xml to be much more elegant. -- 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

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2450) OWASP / New Session after Login

by ahus1 (JIRA)

OWASP / New Session after Login ------------------------------- Key: JBSEAM-2450 URL: http://jira.jboss.com/jira/browse/JBSEAM-2450 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Environment: Linux 2.6, jetty 6.1.5, java 6 Reporter: ahus1 Hello, OWASP has compiled a "top 10" vulnerablilities for web applications. One suggestion against session hijacking was the following: Start a new HTTP-Session after a successful login: "Consider regenerating a new session upon successful authentication or privilege level change." http://www.owasp.org/index.php/Top_10_2007-A7 Therefore there should be a (configurable?) switch to choose "continue with new session ID after successful log on" I have thought of invalidating the current HTTP session, creating a new one and copying all elements from the old session to the new session in my Authenticator. But Seam 2.0.0 doesn't allow this: When I use the lowlevel functions this is blocked by IllegalStateException("Please end the HttpSession via Seam.invalidateSession()") in Lifecyle. When I use Seam.invalidateSession(), the session is only destroyed at the end of the request and I am unable to copy any objects in my Authenticator as the new session doesn't exist yet. The workaround I have come up with is a filter, that destroys the complete session before the log in. This is not very elegant, but it works for me as I don't have i.e. a shoping basket that I'd like to preserve. A "nice" implementation in seam shouldn't have this limitation. shane.bryzak(a)jboss.com asked for this ticket to be assigned to her. The Java Class: Code: /** * This filter enforces a new session whenever there is a POST, should be mapped * to the URL of the login page in your web.xml * @author Alexander Schwartz 2007 */ public class NewSessionFilter implements Filter { private Log log = LogFactory.getLog(NewSessionFilter.class); private String url; public void destroy() { // empty. } public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException { if (request instanceof HttpServletRequest) { HttpServletRequest httpRequest = (HttpServletRequest) request; if (httpRequest.getMethod().equals("POST") && httpRequest.getSession() != null && !httpRequest.getSession().isNew() && httpRequest.getRequestURI().endsWith(url)) { httpRequest.getSession().invalidate(); httpRequest.getSession(true); log.info("new Session:" + httpRequest.getSession().getId()); } } chain.doFilter(request, response); } public void init(FilterConfig filterConfig) throws ServletException { url = filterConfig.getInitParameter("url"); if (url == null) { throw new ServletException( "please specify parameter 'url' with login URL"); } } } The web.xml: Code: <filter> <display-name>NewSessionFilter</display-name> <filter-name>NewSessionFilter</filter-name> <filter-class> NewSessionFilter </filter-class> <init-param> <param-name>url</param-name> <param-value>/iss/login.jsf</param-value> </init-param> </filter> <filter-mapping> <filter-name>NewSessionFilter</filter-name> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/iss/login.jsf</url-pattern> <dispatcher>REQUEST</dispatcher> </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

14 years, 8 months

11
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4371) [Excel exporter] Excel exporter error on header and xsl-force-type

by Yan Langlois (JIRA)

[Excel exporter] Excel exporter error on header and xsl-force-type ------------------------------------------------------------------ Key: JBSEAM-4371 URL: https://jira.jboss.org/jira/browse/JBSEAM-4371 Project: Seam Issue Type: Bug Components: Excel Affects Versions: 2.1.2.GA Reporter: Yan Langlois Priority: Blocker When a dataTable use a column with header and xsl-force-type the haeder is cast to the forced type. It should not. For exemple : <rich:dataTable id="idTable" value="#{myBean}" var="item"> <rich:column style="xls-force-type:date;"> <f:facet name="header"> <h:outputText styleClass="headerText" value="Day" /> </f:facet> <h:outputText value="#{item.date}" /> </rich:column> </rich:dataTable> The exporter try to cast the value "Day" into a java.util.Date. It should only cast #{item.date} into a java.util.Date. -- 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

2
4
0 / 0

[JBoss JIRA] Moved: (SEAMWICKET-11) numberguess-wicket example allows values outside of the current valid range

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/SEAMWICKET-11?page=com.atlassian.jira.... ] Pete Muir moved WELDX-14 to SEAMWICKET-11: ------------------------------------------ Project: Seam Wicket (was: Weld Extensions) Key: SEAMWICKET-11 (was: WELDX-14) Component/s: (was: Wicket support) Fix Version/s: 1.0.2.CR1 (was: Wicket 1.0.2.CR1) Affects Version/s: 1.0.0.Beta1 (was: Wicket 1.0.0.BETA1 ) > numberguess-wicket example allows values outside of the current valid range > --------------------------------------------------------------------------- > > Key: SEAMWICKET-11 > URL: https://jira.jboss.org/jira/browse/SEAMWICKET-11 > Project: Seam Wicket > Issue Type: Bug > Affects Versions: 1.0.0.Beta1 > Reporter: Jozef Hartinger > Assignee: Clint Popetz > Priority: Minor > Fix For: 1.0.2.CR1 > > > WBRI-80 should be ported to wicket example as well. -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (SEAMWICKET-10) webbeans-numberguess-wicket does not deploy on tomcat

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/SEAMWICKET-10?page=com.atlassian.jira.... ] Pete Muir moved WELDX-13 to SEAMWICKET-10: ------------------------------------------ Project: Seam Wicket (was: Weld Extensions) Key: SEAMWICKET-10 (was: WELDX-13) Component/s: (was: Wicket support) Fix Version/s: 1.0.2.CR1 (was: Wicket 1.0.2.CR1) Affects Version/s: 1.0.0.Beta1 (was: Wicket 1.0.0.BETA1 ) > webbeans-numberguess-wicket does not deploy on tomcat > ----------------------------------------------------- > > Key: SEAMWICKET-10 > URL: https://jira.jboss.org/jira/browse/SEAMWICKET-10 > Project: Seam Wicket > Issue Type: Bug > Affects Versions: 1.0.0.Beta1 > Environment: Tomcat 6.0.18 > JDK 5 update 16 > Reporter: Jozef Hartinger > Assignee: Clint Popetz > Fix For: 1.0.2.CR1 > > > Application throws the following exception during deployment: > Apr 24, 2009 10:45:39 AM org.apache.catalina.core.StandardContext filterStart > SEVERE: Exception starting filter wicket.numberguess-example > java.lang.NoClassDefFoundError: org/jboss/webbeans/manager/api/WebBeansManager > at org.jboss.webbeans.wicket.WebBeansApplication.<init>(WebBeansApplication.java:37) > at org.jboss.webbeans.examples.wicket.SampleApplication.<init>(SampleApplication.java:5) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at java.lang.Class.newInstance0(Class.java:355) > at java.lang.Class.newInstance(Class.java:308) > at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) > at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49) > at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:552) > at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) > at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) > at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108) > at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4363) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) > at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) > at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) > at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1217) > at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) > at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.ClassNotFoundException: org.jboss.webbeans.manager.api.WebBeansManager > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) > ... 30 more -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (SEAMWICKET-4) Dependence on portlet-api due to scanning of a class

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/SEAMWICKET-4?page=com.atlassian.jira.p... ] Pete Muir moved WELDX-36 to SEAMWICKET-4: ----------------------------------------- Project: Seam Wicket (was: Weld Extensions) Key: SEAMWICKET-4 (was: WELDX-36) Component/s: (was: Wicket support) Fix Version/s: 1.0.2.CR1 (was: Wicket 1.0.2.CR1) > Dependence on portlet-api due to scanning of a class > ---------------------------------------------------- > > Key: SEAMWICKET-4 > URL: https://jira.jboss.org/jira/browse/SEAMWICKET-4 > Project: Seam Wicket > Issue Type: Bug > Reporter: Pete Muir > Fix For: 1.0.2.CR1 > > -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (SEAMWICKET-5) Allow Wicket support to be used with any 299 impl

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/SEAMWICKET-5?page=com.atlassian.jira.p... ] Pete Muir moved WELDX-7 to SEAMWICKET-5: ---------------------------------------- Project: Seam Wicket (was: Weld Extensions) Key: SEAMWICKET-5 (was: WELDX-7) Component/s: (was: Wicket support) Fix Version/s: 1.0.2.CR1 (was: Wicket 1.0.2.CR1) > Allow Wicket support to be used with any 299 impl > ------------------------------------------------- > > Key: SEAMWICKET-5 > URL: https://jira.jboss.org/jira/browse/SEAMWICKET-5 > Project: Seam Wicket > Issue Type: Feature Request > Reporter: Pete Muir > Assignee: Clint Popetz > Priority: Blocker > Fix For: 1.0.2.CR1 > > -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (SEAMWICKET-3) Deployment issues with numberguess example

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/SEAMWICKET-3?page=com.atlassian.jira.p... ] Pete Muir moved WELDX-39 to SEAMWICKET-3: ----------------------------------------- Project: Seam Wicket (was: Weld Extensions) Key: SEAMWICKET-3 (was: WELDX-39) Component/s: (was: Wicket support) Fix Version/s: 1.0.2.CR1 (was: Wicket 1.0.2.CR1) > Deployment issues with numberguess example > ------------------------------------------ > > Key: SEAMWICKET-3 > URL: https://jira.jboss.org/jira/browse/SEAMWICKET-3 > Project: Seam Wicket > Issue Type: Bug > Environment: Using 'ant tomcat.deploy' with apache-tomcat-6.20 > Reporter: Christian Bauer > Assignee: Clint Popetz > Priority: Minor > Fix For: 1.0.2.CR1 > > > The CR1 release has the following issues with /examples/wicket/numberguess: > 1. There is an empty org/jboss/webbeans/examples/ directory in the src/ folder. > 2. slf4j is completely missing in the WAR, neither API nor implementation is deployed. > 3. The main Weld JARs are also missing, only weld-wicket.jar is being deployed. > 4. After copying slf4j, log4j, and weld-servlet.jar, I get this exception on startup: > Oct 19, 2009 4:17:20 PM org.apache.catalina.core.StandardContext filterStart > SEVERE: Exception starting filter wicket.numberguess-example > org.apache.wicket.WicketRuntimeException: There is no application attached to current thread main > at org.apache.wicket.Application.get(Application.java:179) > at org.jboss.weld.wicket.BeanManagerLookup.getBeanManager(BeanManagerLookup.java:76) > at org.jboss.weld.wicket.WeldApplication.<init>(WeldApplication.java:39) > at org.jboss.weld.examples.wicket.SampleApplication.<init>(SampleApplication.java:5) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at java.lang.Class.newInstance0(Class.java:355) > at java.lang.Class.newInstance(Class.java:308) > at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) > at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49) > at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:678) > at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) > at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) > at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108) > at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3800) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4450) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) > at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:987) > at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909) > at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495) > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206) > at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) > at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) > at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) > at org.apache.catalina.core.StandardService.start(StandardService.java:516) > at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) > at org.apache.catalina.startup.Catalina.start(Catalina.java:583) > 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:597) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) > (Which is btw the same I get in my own weld-wicket test app after upgrading from webbeans 10-day-old-SVN trunk.) -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2010