December 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-560) seam new-query

by Gavin King (JIRA)

seam new-query -------------- Key: JBSEAM-560 URL: http://jira.jboss.com/jira/browse/JBSEAM-560 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Assigned To: Norman Richards To generate a stub query page -- 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, 10 months

5
8
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-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

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

14 years, 11 months

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-541) ConversationEntry reports the wrong description

by Norman Richards (JIRA)

ConversationEntry reports the wrong description ----------------------------------------------- Key: JBSEAM-541 URL: http://jira.jboss.com/jira/browse/JBSEAM-541 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.CR1 Reporter: Norman Richards Assigned To: Gavin King The linked forum post shows one example of this bug, though it is not directly the issue the poster is complaining of. Using the forum application as a guide, start a conversation and then start a nested conversation. End the nested conversation. The description of the parent conversation in the converstion list on will be incorrect. (it will have the name of the current conversation that just ended) This happens because of the following code: public String getDescription() { if ( isCurrent() ) { String desc = Conversation.instance().description; if (desc!=null) return desc; } return description; } public boolean isCurrent() { Manager manager = Manager.instance(); if ( manager.isLongRunningConversation() ) { return id.equals( manager.getCurrentConversationId() ); } else if ( manager.isNestedConversation() ) { return id.equals( manager.getParentConversationId() ); } else { return false; } } The parent conversation entry is considered "current". (isLongRunning() is false and isNestedConversation() is true) Because of this, the ConversationEntry description is ignored in favor of Conversation.instance().description. (Again, Conversation.instance(), is the nested conversation that just ended) Subsequent requests display the conversation description correctly since they are done in the context of the correct conversation. The isNestedConversation() check looks to be the source of the problem. I can't figure out what case that would make sense for. -- 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
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-629) support actionListener on s:link

by Norman Richards (JIRA)

support actionListener on s:link -------------------------------- Key: JBSEAM-629 URL: http://jira.jboss.com/jira/browse/JBSEAM-629 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards Users have requested actionListener support on s:link and s:button. -- 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, 8 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-620) Make the booking work on WLS 10.0 Preview

by Michael Yuan (JIRA)

Make the booking work on WLS 10.0 Preview ----------------------------------------- Key: JBSEAM-620 URL: http://jira.jboss.com/jira/browse/JBSEAM-620 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.0.GA Reporter: Michael Yuan Priority: Minor WebLogic 10.0 -- 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, 9 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 December 2006