August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2141) Support for EL without reflection for better JSF performance

by Mikhail Grushinskiy (JIRA)

Support for EL without reflection for better JSF performance ------------------------------------------------------------ Key: JBSEAM-2141 URL: http://jira.jboss.com/jira/browse/JBSEAM-2141 Project: JBoss Seam Issue Type: Feature Request Components: EL Reporter: Mikhail Grushinskiy Support for EL without reflection for better JSF performance. The idea is to add a new tag to declare types of the variables used on a page and use this type information to compile EL expressions into byte-code during initialization (deployment) Ex: If the page contains at the beginning <s:typedef var="myBean" class="com.company.package.Bean" /> then all EL expressions can be compiled into bytecode at initialization time (and no reflection will be used for myBean access. <h:outputText value="#{myBean.subBean.property}" rendered="#{myBean.renderText}" /> Some examples of implementation of compiled EL can be found here http://sixlegs.com/blog/java/compiled-el.html This should help much with JSF performance issues Thanks -- 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

17 years, 6 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2864) Injection not working with concurrent clients

by Marcell Barbacena (JIRA)

Injection not working with concurrent clients --------------------------------------------- Key: JBSEAM-2864 URL: http://jira.jboss.com/jira/browse/JBSEAM-2864 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1 Environment: Jboss AS 4.2.2.GA, Windows Reporter: Marcell Barbacena When I was loading testing my application I was getting some NPE. I narrowed down the error and created the example app based on a seam-gen one (just stripped the lib directory). Basically, what I want to execute the place GET at the following URLs: http://localhost:8080/myproject/performance/startsession.seam http://localhost:8080/myproject/performance/start.seam http://localhost:8080/myproject/performance/search.seam?parameter=1&cid=2 http://localhost:8080/myproject/performance/end.seam?cid=2 If after you start jboss you execute the above it goes ok. The debug page shows that the long-running conversation is gone and everything is ok. Then I created a JMeter test, just capturing the "cid" from start, and use it at search and end page (see attached jmeter test). If you run the script with 1 thread no loop, it goes ok. If you run with 5 (in my pc) it goes ok. But when you put more then 20, it starts to get NPE at SimpleAction#search when it calls the DAO. The log at search.xhtml shows the error and the sysos at SimpleAction#search shows it as well. Please, provide a workaround in 2.0.1.CR1. -- 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

17 years, 6 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2198) Hot deployment of Seam EJB3 components

by Pete Muir (JIRA)

Hot deployment of Seam EJB3 components -------------------------------------- Key: JBSEAM-2198 URL: http://jira.jboss.com/jira/browse/JBSEAM-2198 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR3 Reporter: Pete Muir -- 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

17 years, 6 months

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1596) Unique Constraint Validator

by Pete Muir (JIRA)

Unique Constraint Validator --------------------------- Key: JBSEAM-1596 URL: http://jira.jboss.com/jira/browse/JBSEAM-1596 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Priority: Blocker We could have a generic unique constrain validator as part of the model validation. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059691#4059691 -- 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

17 years, 6 months

8
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3005) Add flush attribute to @End annotation

by Dan Allen (JIRA)

Add flush attribute to @End annotation -------------------------------------- Key: JBSEAM-3005 URL: http://jira.jboss.com/jira/browse/JBSEAM-3005 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Priority: Minor Fix For: 2.1.0.GA The @End annotation should support the flush attribute to complement the flushMode attribute on the @Begin annotation. While there may be cases to perform bean-managed flushing, it makes sense to allow this to be specified declaratively, especially for simple cases. The flushing would need to occur in the ConversationInterceptor. -- 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

17 years, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2953) chatroom example allow users not connected to post messages as user "null>"

by Jay Balunas (JIRA)

chatroom example allow users not connected to post messages as user "null>" --------------------------------------------------------------------------- Key: JBSEAM-2953 URL: http://jira.jboss.com/jira/browse/JBSEAM-2953 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor Deploy the remoting/chatroom example. You can send a message even if not connected and it will show as user: "null>". -- 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

17 years, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2954) remoting/helloworld example still processes even if you select "cancel"

by Jay Balunas (JIRA)

remoting/helloworld example still processes even if you select "cancel" ----------------------------------------------------------------------- Key: JBSEAM-2954 URL: http://jira.jboss.com/jira/browse/JBSEAM-2954 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor When you launch the remoting helloworld example you have the option of selecting "ok" or "cancel" on the popup box. If you hit cancel it will still process but with "null" for a string. -- 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

17 years, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3352) New Permission annotations works only on method level

by Vinicius Carvalho (JIRA)

New Permission annotations works only on method level ------------------------------------------------------ Key: JBSEAM-3352 URL: https://jira.jboss.org/jira/browse/JBSEAM-3352 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.BETA1 Reporter: Vinicius Carvalho Priority: Minor The new permission annotations (@PermissionUser,@PermissionRole) are working only when methods gets annotated with them. The problem is on the AnnotatedBeanProperty class which checks for public static AnnotatedBeanProperty scanForProperty(Class cls, Class<? extends Annotation> annotation) { for (Field f : cls.getFields()) { if (f.isAnnotationPresent(annotation)) { return new AnnotatedBeanProperty(f, f.getAnnotation(annotation)); } } It should be cls.getDeclaredFields() since f.getFields only returns public fields. -- 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, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3354) ELException catched in lifecycle phase RENDER_RESPONSE about: the raised exception does not have a readable property

by Julien Kronegg (JIRA)

ELException catched in lifecycle phase RENDER_RESPONSE about: the raised exception does not have a readable property -------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3354 URL: https://jira.jboss.org/jira/browse/JBSEAM-3354 Project: Seam Issue Type: Bug Components: EL Affects Versions: 2.0.0.GA Environment: Jboss 4.2.1.GA, JDK 1.5.0_11 Reporter: Julien Kronegg When an Exception with a specific getter pattern is raised in the ".page.xml" page, the Seam debug page is not displayed, but instead gives a 404 error and the log contains the follow trace: 22:17:09,328 WARN [lifecycle] phase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@2f1e34) threw exception: javax.el.ELException: /file:/C:/Workspace/jboss-4.2.1.GA/server/default/deploy/networking20.ear/networking20.war/WEB-INF/lib/jboss-seam-debug.jar!/META-INF/debug.xhtml: The class 'org.hibernate.exception.NestableRuntimeException' does not have a readable property 'message'. /file:/C:/Workspace/jboss-4.2.1.GA/server/default/deploy/networking20.ear/networking20.war/WEB-INF/lib/jboss-seam-debug.jar!/META-INF/debug.xhtml: The class 'org.hibernate.exception.NestableRuntimeException' does not have a readable property 'message'. com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:48) com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) com.sun.facelets.component.RepeatRenderer.encodeChildren(RepeatRenderer.java:50) com.sun.facelets.component.UIRepeat.process(UIRepeat.java:357) com.sun.facelets.component.UIRepeat.encodeChildren(UIRepeat.java:617) com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:244) com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249) com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249) org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:51) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) 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:68) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) 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:44) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:260) org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:366) org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:493) org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) 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.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:179) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) 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:241) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:595) This can be reproduced with the following test case: ------------------------------------------------ class A -------------------------------------- import javax.ejb.Local; @Local public interface A { public String getMessage(); public String getMessage(int num); public String getMessage2(); public String getMessage3(); public void destroy(); } ------------------------------------------------------------------------------------------------- --------------------------------- class AAction (extends A) ---------------------------- import javax.ejb.Remove; import javax.ejb.Stateful; import org.hibernate.exception.NestableRuntimeException; import org.jboss.seam.annotations.Destroy; import org.jboss.seam.annotations.Name; @Stateful @Name("a") public class AAction implements A { public String getMessage1() { return "foobar"; } public String getMessage1(int i) { return ""+i; } public String getMessage2() { throw new NestableRuntimeException("xxx"); } public String getMessage3() { throw new IndexOutOfBoundsException("xxx"); } @Destroy @Remove public void destroy() {} } -------------------------------------------------------------------------------------------- --------------------------------------- a.xhtml ------------------------------------------ <!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets"> </ui:composition> ------------------------------------------------------------------------------------------- ---------------------------------------a.page.xml ------------------------------------- <page> <action execute="#{a.getMessage2}"/> </page> -------------------------------------------------------------------------------------------- Depending on the "execute" field in the "a.page.xml" page, the result is not the same: - "#{a.getMessage1}" => the A.getMessage1() method is executed normally - "#{a.getMessage2}" => the stacktrace above is displayed in the log files and the page is breaked (error 404?) - "#{a.getMessage3}" => the Seam debug page is displayed with a description of the exception (here, an IndexOutOfBoundsException was chosen) The excepted behavior would be that all exceptions lead to displaying the Seam debug page. The short story about why the "a.getMessage2" test case displays the stacktrace is the following: to generate the Seam debug page, exception message must be obtained. The raised exception (NestableRuntimeException) has a getter getMessage() and another getMessage(int), and javax.el.BeanELResolver (used to execute the EL) which uses java.beans.Introspector (the builder used to compute the list of properties) cannot recognize the getMessage() getter because the Introspector merges getMessage() and getMessage(int) into getMessage(int). Consequently, the exception appears to have no getMessage() method (from the BeanELResolver viewpoint), which causes the Seam debug page to break. The long story is here: http://seamframework.org/Community/AnybodyHitThisBugInSeam#comment35710 IMHO, this is a problem in the javax.el.BeanELResolver (from el-api.jar), which uses the very generic and complicated java.beans.Introspector class for a very simple use of obtaining the getters and setters. I know that its a JDK/javax.el issue, but Pete Muir suggested me to file a JIRA issue, so there it is. The difficulty behind that issue is that the BeanELResolver and Introspector are used for multiple purposes and that correcting them could imply large side effects, so it is probably why the issue has not yet been corrected in the BeanELResolver. -- 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, 6 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2955) seambay example throws an exception when viewing "Whistler's Mother" item

by Jay Balunas (JIRA)

seambay example throws an exception when viewing "Whistler's Mother" item ------------------------------------------------------------------------- Key: JBSEAM-2955 URL: http://jira.jboss.com/jira/browse/JBSEAM-2955 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor When attempting to view the "Whistler's Mother" item the browser shows a JSF error page, and the exception below is in the logs: Caused by: line 1:346: unexpected char: 0xFFFD at org.jboss.seam.text.SeamTextLexer.nextToken(SeamTextLexer.java:230) at antlr.TokenBuffer.fill(Unknown Source) at antlr.TokenBuffer.LA(Unknown Source) at antlr.LLkParser.LA(Unknown Source) at org.jboss.seam.text.SeamTextParser.line(SeamTextParser.java:651) at org.jboss.seam.text.SeamTextParser.paragraph(SeamTextParser.java:401) -- 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

17 years, 6 months

4
8
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 August 2008