November 2006 - seam-issues - Jboss List Archives

[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, 3 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, 3 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, 3 months

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

15 years, 7 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-513) Contextual Events for Seam Framework

by Peter Muir (JIRA)

Contextual Events for Seam Framework ------------------------------------ Key: JBSEAM-513 URL: http://jira.jboss.com/jira/browse/JBSEAM-513 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.BETA2 Reporter: Peter Muir It would be good if the framework raised events when actions occurred e.g.org.jboss.seam.framework.persist.<myEntityHomeName> org.jboss.seam.framework.update.<myEntityHomeName> My use case is a 'Activity History' which records a text-history performed by users. -- 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, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-439) Allow nested conversations when navigating between CRUD entities

by James Salt (JIRA)

Allow nested conversations when navigating between CRUD entities ---------------------------------------------------------------- Key: JBSEAM-439 URL: http://jira.jboss.com/jira/browse/JBSEAM-439 Project: JBoss Seam Issue Type: Feature Request Components: Framework Environment: All Reporter: James Salt Priority: Minor Enhance the current entityHome pattern to allow the navigation between entities (i.e. linked entities customer to order link), via a navigation commandlink/slink etc. This would then allow you to navigate through a graph of interalated entities and to simply close the current entity editor and POP back to the entity editor you navigated from. This would allow a conversation tree effect so that you could go down three levels of links and then slowly pop back up to the original object, as you press each close button. would need two extra functions in the entityHome: close -> Closes current entity (ends conversation) and pop back to the parent conversation. You could also extend the close to remember any page that called via the view id, and return to that (i.e. customer list page). navigate -> invokes the entityHome for the linked entity (i.e. order), and begins the nested conversation. -- 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, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-492) NPE in ParamMethodExpression

by Stas Garifulin (JIRA)

NPE in ParamMethodExpression ---------------------------- Key: JBSEAM-492 URL: http://jira.jboss.com/jira/browse/JBSEAM-492 Project: JBoss Seam Issue Type: Bug Environment: jboss seam cvs head jsf-ri 1.2.03 facelets 1.1.11 Reporter: Stas Garifulin Forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985161#3985161 -- 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, 5 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-474) Extending the framework using EJB3 components

by Gavin King (JIRA)

Extending the framework using EJB3 components --------------------------------------------- Key: JBSEAM-474 URL: http://jira.jboss.com/jira/browse/JBSEAM-474 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.BETA1, 1.1.0.BETA2 Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.0.CR1 The documentation claims that it is possible to inherit EJB3 components from the framework, but in practice it turns out to not be so easy :-( -- 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, 6 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-505) Seam/WS

by Gavin King (JIRA)

Seam/WS ------- Key: JBSEAM-505 URL: http://jira.jboss.com/jira/browse/JBSEAM-505 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.2.0.BETA1 Seam/WS will allow Seam components to receive WS calls and: * participate in a WS conversation which is * orchestrated by jBPM * recoverable, when services come back online -- 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, 10 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2006