September 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2001) Use fast optimized API for reading annotations in Seam and Seam RHDS Tools

by Mikhail Grushinskiy (JIRA)

Use fast optimized API for reading annotations in Seam and Seam RHDS Tools -------------------------------------------------------------------------- Key: JBSEAM-2001 URL: http://jira.jboss.com/jira/browse/JBSEAM-2001 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Mikhail Grushinskiy Use fast optimized API for reading annotations. Seam is using calls to isAnnotationPresent() very frequently and it impacts overall performance and throughput backport175 from http://backport175.codehaus.org/ provides API for reading annotations faster than JDK5. (They claim in http://fisheye.codehaus.org/browse/backport175/backport175/src/main/org/c... as much as 5 times faster) Quote: // =========================================================================== // Implementation notes: // Parsing and annotation creation is made in two steps // // 1. The bytecode is parsed and the annotation content is put in elements, // which are stored for later processing // // 2. Upon annotation access the elements are processed and a dynamic proxy // for the annotation is created and cached. // // This gives much better performance than reflective access of Java 5 // annotations (reflective access is around 5 times slower) // =========================================================================== Provide optimizations in Seam for faster annotation reading. Apart from Seam application performance it also can help Seam tools (in RHDS), as well as application startup time. This behavior can be made optional similarly to hibernate's hibernate.jdbc.use_refection_optimizer -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1966) Code optimization in Component class

by Yannick Lazzari (JIRA)

Code optimization in Component class ------------------------------------ Key: JBSEAM-1966 URL: http://jira.jboss.com/jira/browse/JBSEAM-1966 Project: JBoss Seam Issue Type: Feature Request Reporter: Yannick Lazzari Priority: Minor During the execution of one JSF request, I noticed a lot of calls to the org.jboss.seam.Component.hasAnnotation method. Couldn't this information be cached somewhere? I know the reflection API is quite fast but in this particular context, couldn't all the "metadata" of a component be stored as class members of the Component class? I know some if already is but I found something that could be added. In the org.jboss.seam.contexts.ServerConversationContext class, the following method seems to be called hundreds of times per request: Code: private boolean isPerNestedConversation(String name) { Component component = Component.forName(name); return (component != null) && component.beanClassHasAnnotation(PerNestedConversation.class); } Could't a "perNestedConversation" class member be added on the org.jboss.seam.Component class and initialized when initializing the component instead of looking for the annotation every time? This is just one example. I haven't looked everywhere where the org.jboss.seam.Component.hasAnnotation is called but perhaps similar optimizations could be done elsewhere. -- 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, 6 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1535) Netbeans project file is not configured properly by seam-gen

by Dan Allen (JIRA)

Netbeans project file is not configured properly by seam-gen ------------------------------------------------------------ Key: JBSEAM-1535 URL: http://jira.jboss.com/jira/browse/JBSEAM-1535 Project: JBoss Seam Issue Type: Patch Components: Tools Affects Versions: 1.3.0.ALPHA Environment: seam CVS HEAD NetBeans 5.5.1 Reporter: Dan Allen The nbproject/project.xml file put in place by seam-gen is broken in more than three ways. Fortunately, I have a patch for you! So how is it broken? 1. It is configured to use "src" as the Java source folder. seam-gen, in fact, creates three source folders, src/action, src/model, and src/test (hence the broken in more than three ways comment) 2. The test package does not have any libraries, so it is impossible to start writing tests in NetBeans using TestNG and SeamTest 3. The xmlns on the java-data note should be upgraded to support NetBeans 5.5.1 (at least, that is what NetBeans 5.5.1 changed it to) 4. Take out testng.jar from the src/action and src/model compilation units -- 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, 6 months

2
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2009) message "In attribute requires non-null value" missing @

by Dan Allen (JIRA)

message "In attribute requires non-null value" missing @ -------------------------------------------------------- Key: JBSEAM-2009 URL: http://jira.jboss.com/jira/browse/JBSEAM-2009 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Priority: Minor Fix For: 2.0.0.CR2 Attachments: JBSEAM-2009-v1.txt This issue is ultra trivial to fix. When a non-null @In attribute is required, but not found, the following message is shown: "In attribute requires non-null value" However, when a non-null @Out attribute is required, but not found, the message is shown as: "@Out attribute requires non-null value" The @ sign is very important as it lets the developer know we are talking about an annotation. Otherwise, the word "In" is ambiguous. -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1993) Consider upgrade to Drools 4.0.1

by Pete Muir (JIRA)

Consider upgrade to Drools 4.0.1 -------------------------------- Key: JBSEAM-1993 URL: http://jira.jboss.com/jira/browse/JBSEAM-1993 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Shane Bryzak -- 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, 6 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2005) facelets comment out of place in icefaces web.xml

by Dan Allen (JIRA)

facelets comment out of place in icefaces web.xml ------------------------------------------------- Key: JBSEAM-2005 URL: http://jira.jboss.com/jira/browse/JBSEAM-2005 Project: JBoss Seam Issue Type: Task Components: ICE Faces Integration Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Assigned To: Gregory Dick Priority: Trivial Fix For: 2.0.0.CR2 This fix is trivial, but important if we are going to include a comment. The comment in the web.xml says "Facelets development mode (disable in production)" However, it is over the wrong element. -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1884) ui:include in PDF doesn't work in IE

by Natalia Ponomareva (JIRA)

ui:include in PDF doesn't work in IE ------------------------------------ Key: JBSEAM-1884 URL: http://jira.jboss.com/jira/browse/JBSEAM-1884 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: jboss-4.0.5.GA Reporter: Natalia Ponomareva Fix For: 2.0.0.GA <ui:include> tag doesn't work in pdf while opening pdf in IE (6 and 7.0). Thus <p:document xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:p="http://jboss.com/products/seam/pdf" xmlns:h="http://java.sun.com/jsf/html"> <h:panelGroup rendered="#{!pdfBean.defaultStyle}" > <ui:include src="/pdf/defaultPDF.xhtml"/> </h:panelGroup> <h:panelGroup rendered="#{pdfBean.defaultStyle}" > <ui:include src="/pdf/anotherStylePDF.xhtml"/> </h:panelGroup> </p:document> Will not be rendered in IE (nothing will be shown).However, Firefox displays that correctly. but this will work <f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html"> <h:panelGroup rendered="#{!pdfBean.defaultStyle}"> <ui:include src="/pdf/defaultPDF.xhtml"/> </h:panelGroup> <h:panelGroup rendered="#{pdfBean.defaultStyle}" > <ui:include src="/pdf/anotherStylePDF.xhtml"/> </h:panelGroup> </f:view> in both Firefox and IE (anotherStylePDF.xhtml and defaultPDF.xhtml are pdf pages as well). I am not sure whether it is bug or feature. -- 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, 6 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2004) Better docs for raiseTransactionSuccessEvent/raiseTransactionCompletionEvent

by Matt Drees (JIRA)

Better docs for raiseTransactionSuccessEvent/raiseTransactionCompletionEvent ---------------------------------------------------------------------------- Key: JBSEAM-2004 URL: http://jira.jboss.com/jira/browse/JBSEAM-2004 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Matt Drees Priority: Minor It'd be nice if the docs elaborated on these. -- 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, 6 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1937) Some EL Expressions in JPDL files now cause EL exceptions

by David Heggie (JIRA)

Some EL Expressions in JPDL files now cause EL exceptions --------------------------------------------------------- Key: JBSEAM-1937 URL: http://jira.jboss.com/jira/browse/JBSEAM-1937 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.CR1 Reporter: David Heggie See forum for full code details. Since upgrading to Seam 2.0.0 CR1 some of the EL expressions in the decision tags of my JPDL files cause exceptions. I found what I think is the problem in the org.jboss.seam.bpm.SeamExpressionResolver class. It tries to parse an expression as a method expression first and if it fails it throws an ELException and exits without trying to evalute it as a value expression. -- 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, 6 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1945) Bulgarian message bundle for seam-gen

by Adrian Mitev (JIRA)

Bulgarian message bundle for seam-gen ------------------------------------- Key: JBSEAM-1945 URL: http://jira.jboss.com/jira/browse/JBSEAM-1945 Project: JBoss Seam Issue Type: Feature Request Reporter: Adrian Mitev Attachments: messages_bg.properties Here is a _bg properties file -- 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, 6 months

2
3
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 September 2007