January 2008 - seam-issues - Jboss List Archives

[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

16 years, 2 months

2
1
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

16 years, 2 months

2
1
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

16 years, 2 months

3
7
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

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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-460) Get rid of SeamStateManager

by Gavin King (JIRA)

Get rid of SeamStateManager --------------------------- Key: JBSEAM-460 URL: http://jira.jboss.com/jira/browse/JBSEAM-460 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.0.BETA1 Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.1.0.BETA2 This is causing just too many problems for integration with other JSF addons. -- 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

16 years, 2 months

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2209) Improve ways to transfer state information from a nested conversation to the parent conversation context

by Wolfgang Schwendt (JIRA)

Improve ways to transfer state information from a nested conversation to the parent conversation context -------------------------------------------------------------------------------------------------------- Key: JBSEAM-2209 URL: http://jira.jboss.com/jira/browse/JBSEAM-2209 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Wolfgang Schwendt Priority: Critical When a nested conversation ends, it is difficult to transfer an ending result back to the parent conversation. The following approach is currently not viable with Seam: We cannot simply access a component from the parent conversation and call a property Setter of this component with the ending result of the nested conversation supplied as argument for this Setter. The reason is that when a component from the parent conversation is called while the nested conversation is still in progress, the ManagedEntityIdentityInterceptor saves wrappers for the called component in the scope of the nested conversation (!) and not the scope of the parent conversation. So once the nested conversation scope gets destroyed at the end of the nested conversation, the saved wrappers for the component from the parent conversation get destroyed as well. Scenario: Suppose that we have a component AA in the conversation context with a field reference named 'bb' to an another component Q. At some point of time this reference is moved by the ManagedEntityIdentityInterceptor to a conversation-scoped context variable with the name "AA.bb". Then we start a nested conversation. While the nested conversation is in progress, we can call a method of component AA and successfully access the field bb because at the time of the method invocation, the ManagedEntityIdentityInterceptor can retrieve the saved wrapper for field bb from the parent conversation context and put the contained reference into the component AA. But then we call a method of component AA which changes the field bb. At the end of this method invocation, the ManagedEntityIdentityInterceptor moves the new value of reference field bb to a wrapper saved in the nested (!) conversation context. Afterwards we end the nested conversation and the parent conversation resumes again. When we then call a method of component AA again, the ManagedEntityIdentityInterceptor retrieves the wrapper for field bb from the conversation context. But this wrapper contains the old value for field bb, not the new value. Note that the wrapper with the new value for field bb got destroyed already at the time when the nested conversation context was destroyed. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118936&start=30 Feature request regarding nested conversations Tue Sep 18, 2007 00:28 AM http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121852 Nested Conversations (tricky interceptor) Mon Oct 22, 2007 11:03 AM -- 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

16 years, 2 months

4
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2338) allow seam-gen to manage multiple projects

by Dan Allen (JIRA)

allow seam-gen to manage multiple projects ------------------------------------------ Key: JBSEAM-2338 URL: http://jira.jboss.com/jira/browse/JBSEAM-2338 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.1.GA Currently seam-gen only has the ability to manage one project at a time. This limitation is due to the fact that it sources build.properties from the seam-gen directory to read settings about the managed project. I propose that we make the name of the settings file dynamic so that it is possible for seam-gen to select it based on the name of a property supplied to the command line. Example: ./seam -Dbuild=projecta explode ./seam explode The first command would source build-projecta.properties. The second command would fall back to the existing behavior and source build.properties. -- 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

16 years, 2 months

4
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2082) JMS Topic subscriptions never released

by Scott McNab (JIRA)

JMS Topic subscriptions never released -------------------------------------- Key: JBSEAM-2082 URL: http://jira.jboss.com/jira/browse/JBSEAM-2082 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.0.CR2, 2.0.0.CR1, 1.2.1.GA, 1.2.0.GA, 2.0.0.GA Environment: JBossAS 4.2.0.GA, All platforms. Reporter: Scott McNab Assigned To: Shane Bryzak In the current Seam remoting implementation, there is no mechanism to clean up and release JMS topic subscriptions for clients that may have subscribed to a JMS topic, but who do not explicitly unsubscribe() (e.g. due to a coding error or if the client simply disappears) Unless a web-client specifically calls Seam.Remoting.unsubscribe(), the RemoteSubscriber object is never released, and the corresponding TopicSession and TopicSubscriber resources will be held open indefinitely. This will cause the JMS provider to store an ever-growing list of undelivered topic messages, which will eventually result in an out of memory crash. Seam Remoting needs to be able to correctly identify situations whereby a RemoteSubscriber is no longer in use, and release resources accordingly. One possible solution might be to periodically check all subscriptions in the SubscriptionRegistry and release any which have not had a recent poll request beyond a certain time limit. -- 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

16 years, 2 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2399) Document no-conversation-view-id and conversation-required

by Christian Bauer (JIRA)

Document no-conversation-view-id and conversation-required ---------------------------------------------------------- Key: JBSEAM-2399 URL: http://jira.jboss.com/jira/browse/JBSEAM-2399 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Christian Bauer These two options are mentioned only in passing in the Seam reference and the behavior they trigger is unclear. -- 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

16 years, 2 months

5
7
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 January 2008