October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2017) UI Build broken in CVS HEAD after facelets 1.1.14

by Diego Ballve (JIRA)

UI Build broken in CVS HEAD after facelets 1.1.14 ------------------------------------------------- Key: JBSEAM-2017 URL: http://jira.jboss.com/jira/browse/JBSEAM-2017 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Diego Ballve UI build from CVS HEAD is failing after change to facelets v1.1.14. Compilation failure message: /home/diego/cvs/sf/jboss/jboss-seam/ui/src/main/java/org/jboss/seam/ui/facelet/FaceletsRenderer.java:[26,29] cannot find symbol symbol : class DefaultResourceResolver location: package com.sun.facelets.impl /home/diego/cvs/sf/jboss/jboss-seam/ui/src/main/java/org/jboss/seam/ui/facelet/DecorateHandler.java:[26,4] method does not override a method from its superclass /home/diego/cvs/sf/jboss/jboss-seam/ui/src/main/java/org/jboss/seam/ui/handler/DecorateHandler.java:[26,4] method does not override a method from its superclass /home/diego/cvs/sf/jboss/jboss-seam/ui/src/main/java/org/jboss/seam/ui/facelet/FaceletsRenderer.java:[195,62] cannot find symbol symbol : class DefaultResourceResolver location: class org.jboss.seam.ui.facelet.FaceletsRenderer Anybody on these already? -- 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, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1515) Use = sign consistently in hibernate-console.properties

by Dan Allen (JIRA)

Use = sign consistently in hibernate-console.properties ------------------------------------------------------- Key: JBSEAM-1515 URL: http://jira.jboss.com/jira/browse/JBSEAM-1515 Project: JBoss Seam Issue Type: Patch Components: Tools Affects Versions: 1.3.0.ALPHA Environment: seam CVS HEAD Reporter: Dan Allen Priority: Trivial Attachments: JBSEAM-1515.txt Sorry, there was no priority level labeled "Ultra Trivial," so I just had to go with "Trivial." The hibernate-console.properties file uses the blank space delimiter for one of the properties, yet uses = for the rest. -- 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, 2 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2015) user transactions do not work with seam managed persistence context

by koen handekyn (JIRA)

user transactions do not work with seam managed persistence context ------------------------------------------------------------------- Key: JBSEAM-2015 URL: http://jira.jboss.com/jira/browse/JBSEAM-2015 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Reporter: koen handekyn Priority: Minor BMT do not work when using seam managed persistence context bean is marked as @TransactionManagement(TransactionManagementType.BEAN) user transaction is inject as @Resource private UserTransaction userTransaction; seam managed persistence context defined as for example <persistence:managed-persistence-context name="bookingDatabase" auto-create="true" persistence-unit-jndi-name="java:/EntityManagerFactories/bookingData"/> WHEN persistenceContext is injected as @PersistenceContext than user managed transaction WORK ! WHEN seam managed persistenceContext is injected with @In than user managed transaction DOES NOT WORK ! this is strange to me as the documentation states that in the normal case seam managed transactions use JPA !!! -- 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, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2013) Deprecate expression attribute on event's in components.xml in favour of execute

by Pete Muir (JIRA)

Deprecate expression attribute on event's in components.xml in favour of execute -------------------------------------------------------------------------------- Key: JBSEAM-2013 URL: http://jira.jboss.com/jira/browse/JBSEAM-2013 Project: JBoss Seam Issue Type: Task Components: Core Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Critical Fix For: 2.0.0.CR2 -- 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, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1988) AuthorizationException not redirected properly

by Samuel Mendenhall (JIRA)

AuthorizationException not redirected properly ---------------------------------------------- Key: JBSEAM-1988 URL: http://jira.jboss.com/jira/browse/JBSEAM-1988 Project: JBoss Seam Issue Type: Bug Components: Security Reporter: Samuel Mendenhall Assigned To: Shane Bryzak pages.xml: <exception class="org.jboss.seam.security.AuthorizationException"> <redirect> <message>You don't have permission to do this</message> </redirect> </exception> Should have: <redirect view-id="/error.xhtml"> Causes a redirect error in the browser otherwise. -- 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, 2 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1992) Upgrade MVEL library to 1.2.final

by Joshua Jackson (JIRA)

Upgrade MVEL library to 1.2.final --------------------------------- Key: JBSEAM-1992 URL: http://jira.jboss.com/jira/browse/JBSEAM-1992 Project: JBoss Seam Issue Type: Task Components: Drools Affects Versions: 2.0.0.CR1 Reporter: Joshua Jackson Fix For: 2.0.0.CR2 Upgrade the current mvel library that is used by drools to mvel 1.2.final as it has some fixes -- 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, 2 months

3
2
0 / 0

[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

17 years, 2 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

17 years, 2 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

17 years, 2 months

2
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2007