December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4358) Upgrade Metawidget to v0.8

by Richard Kennard (JIRA)

Upgrade Metawidget to v0.8 -------------------------- Key: JBSEAM-4358 URL: https://jira.jboss.org/jira/browse/JBSEAM-4358 Project: Seam Issue Type: Thirdparty Change Components: Examples Affects Versions: 2.2.0.GA Reporter: Richard Kennard Could you please update the JBoss Maven repository here... http://repository.jboss.com/maven2/org/metawidget/ ...to the v0.8 version of Metawidget. Main changes include support for ICEfaces. -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4374) GWT Example does not work with GWT from trunk.

by Sand Lee (JIRA)

GWT Example does not work with GWT from trunk. ---------------------------------------------- Key: JBSEAM-4374 URL: https://jira.jboss.org/jira/browse/JBSEAM-4374 Project: Seam Issue Type: Thirdparty Change Components: Remoting Affects Versions: 2.2.0.GA, 2.2.1.CR1 Environment: linux, jboss 4.2.3, seam 2.2.1-SNAPSHOT, GWT from trunk (r5989) Reporter: Sand Lee Assignee: Shane Bryzak way to reproduce: cd /tmp svn co http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2 seam svn checkout http://google-web-toolkit.googlecode.com/svn/tools/ tools svn checkout http://google-web-toolkit.googlecode.com/svn/trunk/ trunk export GWT_TOOLS=/tmp/tools cd /tmp/trunk ant cd /tmp/seam/examples/remoting/gwt sed -i 's/C:\/java\/gwt-windows-1.5.2/\/tmp\/trunk\/build\/lib\//g' build.properties ant clean gwt-compile deploy pressing ask on http://localhost:8080/seam-gwt/HelloWorld.html produces following output on the server side: 12:41:55,928 INFO [EARDeployer] Started J2EE application: file:/opt/jboss-4.2.3.GA/server/default/deploy/jboss-seam-gwt.ear |@LOCATION: org.jboss.deployment.EARDeployer.start(EARDeployer.java:368) 12:45:00,807 ERROR [[/seam-gwt]] Exception while dispatching incoming RPC call |@LOCATION: org.apache.catalina.core.ApplicationContext.log(ApplicationContext.java:660) java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract(ServerSerializationStreamReader.java:617) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt(ServerSerializationStreamReader.java:432) at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead(AbstractSerializationStreamReader.java:38) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead(ServerSerializationStreamReader.java:383) at org.jboss.seam.remoting.gwt.GWTService.RPC_decodeRequest(GWTService.java:376) at org.jboss.seam.remoting.gwt.GWTService.processCall(GWTService.java:203) at org.jboss.seam.remoting.gwt.GWTService$1.process(GWTService.java:120) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.remoting.gwt.GWTService.getResource(GWTService.java:105) at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) -- 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

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3661) ldapIdentityStore assumes roles are attributes of users - please support groupOfNames with attributes that identify users in that role

by Gerry Matte (JIRA)

ldapIdentityStore assumes roles are attributes of users - please support groupOfNames with attributes that identify users in that role -------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3661 URL: https://jira.jboss.org/jira/browse/JBSEAM-3661 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.SP1 Environment: All SEAM supported environments Reporter: Gerry Matte Please modify ldapIdentityStore to support the same (or equivalent) attributes as the Jboss login module LdapExtLoginModule. Currently the role attribute is assumed to be associated with the user object. -- 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

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4434) Broken wicket instrumentation instructions for Ant

by Christian Bauer (JIRA)

Broken wicket instrumentation instructions for Ant -------------------------------------------------- Key: JBSEAM-4434 URL: https://jira.jboss.org/jira/browse/JBSEAM-4434 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.2.0.GA Reporter: Christian Bauer Attachments: screenshot-1.jpg 1. The HTML documentation of the wicket chapter is broken, see attached screenshot. 2. The PDF documentation includes the following instructions for enhancing the Wicket components: <taskdef name="instrumentWicket" classname="org.jboss.seam.wicket.ioc.WicketInstrumentationTask"> <classpath> <pathelement location="lib/jboss-seam-wicket-ant.jar"/> <pathelement location="web/WEB-INF/lib/jboss-seam-wicket.jar"/> <pathelement location="lib/javassist.jar"/> <pathelement location="lib/jboss-seam.jar"/> </classpath> </taskdef> <instrumentWicket outputDirectory="${build.instrumented}" useAnnotations="true"> <classpath refid="build.classpath"/> <fileset dir="${build.classes}" includes="**/*.class"/> </instrumentWicket> What is "build.classpath"?Nobody can look at the examples/wicket/build.xml and figure that one out either. So it's a total mystery why an additional classpath needs to be referenced within the task, when the task definition already lists all (you'd think) required classes. Users will not know what should be defined on that classpath. Without this classpath setting or with just guessing what could/should be on that classpath, you will get "java.lang.RuntimeException: javassist.NotFoundException: HelloWorldApplication" (the only classes in build.classes are the ones for a Wicket HelloWorld, so this is just the first class file found). -- 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

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3018) Tomcat appending jsessionid to URLs breaks page fragment cache

by Christian Bauer (JIRA)

Tomcat appending jsessionid to URLs breaks page fragment cache -------------------------------------------------------------- Key: JBSEAM-3018 URL: http://jira.jboss.com/jira/browse/JBSEAM-3018 Project: Seam Issue Type: Task Components: JSF Integration Reporter: Christian Bauer Priority: Critical Tomcat/JSF encodes URLs and, even if cookies are enabled, sometimes appends a JSESSIONID parameter. If you request a page fragment, your session id is encoded into the rendered URLs. If I then later retrieve that fragment from the cache, I get your session. This is a critical issue, I'll look for a workaround, if that's not possible, we need to document it. -- 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

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3968) Integrate perf4j into Seam

by Daniel Roth (JIRA)

Integrate perf4j into Seam -------------------------- Key: JBSEAM-3968 URL: https://jira.jboss.org/jira/browse/JBSEAM-3968 Project: Seam Issue Type: Feature Request Components: Core Reporter: Daniel Roth Assignee: Daniel Roth Fix For: The future http://perf4j.codehaus.org/ seems to be a really cool thing to integrate into Seam -- 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

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2645) Promote forum thread to FAQ

by Gavin King (JIRA)

Promote forum thread to FAQ --------------------------- Key: JBSEAM-2645 URL: http://jira.jboss.com/jira/browse/JBSEAM-2645 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King Assigned To: Christian Bauer Easily promote a forum thread into the FAQ browser -- 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

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009