November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-723) Performance improvements

by Shane Bryzak (JIRA)

Performance improvements ------------------------ Key: JBSEAM-723 URL: http://jira.jboss.com/jira/browse/JBSEAM-723 Project: JBoss Seam Issue Type: Task Affects Versions: 1.1.1.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Profile Seam to determine which interceptors are the most resource-consuming and optimize where possible. -- 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, 11 months

6
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-722) Add a component generator component that allows one to sub-type Component

by Bill Wallace (JIRA)

Add a component generator component that allows one to sub-type Component ------------------------------------------------------------------------- Key: JBSEAM-722 URL: http://jira.jboss.com/jira/browse/JBSEAM-722 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.1.GA Reporter: Bill Wallace It would be very nice to be able to specify what Component class is to be used within a package, so that one can, for instance, over-ride or extend the initialization code. Adding such over-riding would allow one to efficiently write annotations such as: @Property("#{property-setter-for-initialization-time}) instead of @In which would provide initialization time object injection. I know you can do this by specifying properties in the components.xml file, or seam.properties file, but it is rather a pain to have to create an xml file just to specify an extra property of that type. I know you can do this with @In, but that executes per-method call, and I'd like to see a version that only executes on instantiation. Of course, one can create an initializer class that gets called from an @Create that performs this same data, but I'd like to be able to store the rest of the meta-data at the class level and view it in the debug page automatically, the same as the rest of the properties. I also have some more complex applications for reading in initialization data. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-721) Lazy @In injector on get method

by Bill Wallace (JIRA)

Lazy @In injector on get method ------------------------------- Key: JBSEAM-721 URL: http://jira.jboss.com/jira/browse/JBSEAM-721 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.1.GA Reporter: Bill Wallace Priority: Minor It would be nice to have a lazy @In injection on a get method that only set the value if someone actually tried to retrieve it, eg: @In String getMyValue() { ... } where it would set either the field or call setMyValue the first time someone tried to retrieve the @In value. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-699) Allow packages to define their own default interceptors

by Gavin King (JIRA)

Allow packages to define their own default interceptors ------------------------------------------------------- Key: JBSEAM-699 URL: http://jira.jboss.com/jira/browse/JBSEAM-699 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.2.0.BETA1 Currently, all default interceptors get listed out in an ugly method on Component. This is extremely non-extensible. We need some way to externalize that code to the package that needs the interceptor. This would let us split out security to its own jar, for example. -- 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, 11 months

6
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-666) s:link and s:button don't work in a parameterized facelets source tag

by Guy Veraghtert (JIRA)

s:link and s:button don't work in a parameterized facelets source tag --------------------------------------------------------------------- Key: JBSEAM-666 URL: http://jira.jboss.com/jira/browse/JBSEAM-666 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.0.GA Reporter: Guy Veraghtert When you add <s:link> or <s:button> in a facelets source tag and you add an action attribute to these tags with a target bean passed in as a parameter to the source tag, the action isn't executed. (However, when using h:commandButton or h:commandLink the action is executed) -- 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, 11 months

9
25
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-587) Have Context handle unwrapping

by Gavin King (JIRA)

Have Context handle unwrapping ------------------------------ Key: JBSEAM-587 URL: http://jira.jboss.com/jira/browse/JBSEAM-587 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Pretty tricky to implement, but it would be much better if Contexts understood the @Unwrap annotation, as well as Component.getInstance(). That would also mean a better impl of EntityBean. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-578) @Property annotation to allow configuration of superclass by subclass

by Gavin King (JIRA)

@Property annotation to allow configuration of superclass by subclass --------------------------------------------------------------------- Key: JBSEAM-578 URL: http://jira.jboss.com/jira/browse/JBSEAM-578 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Minor For extension of framework components it might be nice to be able to do: @Property(name="maxResults", value="25") public class CustomerQuery extends EntityQuery { .... } -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-510) Embed pages.xml metadata in the page (like annotations for the view)

by Gavin King (JIRA)

Embed pages.xml metadata in the page (like annotations for the view) -------------------------------------------------------------------- Key: JBSEAM-510 URL: http://jira.jboss.com/jira/browse/JBSEAM-510 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Fix For: 1.1.1.GA Wouldn't it be great to be able to write: <html xmlns:p="http://jboss.com/products/seam/pages.xsd" xmlns:f="............" xmlns:h="............" xmlns:ui="............" xmlns="........."> <p:page action="#{....}"> <p:param name="..." value="#{...}"/> <p:begin-conversation pageflow="....."/> </p:page> <head>...</head> <body> <f:view>...</f:view> </body> </html> -- 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, 11 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-485) Add support to configure Scanner to ignore certain names

by jarkko Lietolahti (JIRA)

Add support to configure Scanner to ignore certain names -------------------------------------------------------- Key: JBSEAM-485 URL: http://jira.jboss.com/jira/browse/JBSEAM-485 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.0.CR1 Reporter: jarkko Lietolahti Priority: Trivial Make it possibe to configure Scanner to ignore certain files/directories. E.g. in development we're deploying Seam EAR as an exploded EAR with exploded WAR's and JAR's inside it and we use SVN for version control. SVN uses ".svn" directories to store metadata. Seam startup logs shows that scanning the .svn directories take some time and there're never going to be anything usefull for Seam in there anyways. Simple fix: private void handleDirectory(Set<Class<Object>> result, File file, String path) { log.debug("directory: " + file); for (File child : file.listFiles()) { String newPath = path == null ? child.getName() : path + '/' + child.getName(); if (child.getName().startsWith(".svn")) { continue; } if (child.isDirectory()) { handleDirectory(result, child, newPath); } else { handleItem(result, newPath); } } } -- 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, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-495) message-driven components, or components called via RMI, with no @Name annotation

by Gavin King (JIRA)

message-driven components, or components called via RMI, with no @Name annotation --------------------------------------------------------------------------------- Key: JBSEAM-495 URL: http://jira.jboss.com/jira/browse/JBSEAM-495 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.BETA2, 1.1.0.BETA1 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.CR1 SessionBeanInterceptor does not consider components defined in components.xml when searching for a Component in postConstruct. If there is no @Name annotation, it should have some heuristics..... -- 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, 11 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007