October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1289) Conversation Propagation andTrinidad Dialogs

by Brian Smith (JIRA)

Conversation Propagation andTrinidad Dialogs -------------------------------------------- Key: JBSEAM-1289 URL: http://jira.jboss.com/jira/browse/JBSEAM-1289 Project: JBoss Seam Issue Type: Feature Request Environment: JBoss 4.0.4GA Reporter: Brian Smith Seam does not automatically support Trinidad's dialog feature in terms of propagating long running conversations to the dialog window. Forum User dajevtic has provided a custom phase listener and action listener to enable propagation but it requires a specific naming convention for the dialog page. It would be nice to enable support directly using standard Seam notation like the s:conversationPropagation tag or @Begin(join = true) Here are the relevant phase listener and action listener *Phase Listener* private static final String CONVERSATION_ID_SESSION_PARAMETER = "conversationId"; private Map createParameterMapForConversationRestore(String conversationId) { Map paramterMap = new Hashtable(); paramterMap.put(CONVERSATION_ID_SESSION_PARAMETER, conversationId); return paramterMap; } private void restoreConversation(Context context) { if (context.isSet(CONVERSATION_ID_SESSION_PARAMETER)) { String convId = context.get(CONVERSATION_ID_SESSION_PARAMETER).toString(); Manager.instance().restoreConversation(createParameterMapForConversationRestore(convId)); context.remove(CONVERSATION_ID_SESSION_PARAMETER); } } public void afterPhase(PhaseEvent event) { try { if (event.getPhaseId().equals(PhaseId.RESTORE_VIEW)) { UIViewRoot root = event.getFacesContext().getViewRoot(); if (root != null) { String viewId = root.getViewId(); if ((viewId != null) && viewId.endsWith("_dlg.jspx")) { restoreConversation(Contexts.getSessionContext()); } } } else { log.info("after " + event.getPhaseId()); } } catch (Exception e) { log.error("Could not restore Seam conversation", e); } } *Action Listener* public void processAction(ActionEvent actionEvent) throws AbortProcessingException { if (actionEvent.getComponent() instanceof CoreCommandLink) { CoreCommandLink link = (CoreCommandLink)actionEvent.getComponent(); if (link.isUseWindow()) { Contexts.getSessionContext().set("conversationId", Manager.instance().getCurrentConversationId()); } } super.processAction(actionEvent); } -- 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, 1 month

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1643) Complain when user tries to define the same view-id twice in pages.xml

by Matt Drees (JIRA)

Complain when user tries to define the same view-id twice in pages.xml ---------------------------------------------------------------------- Key: JBSEAM-1643 URL: http://jira.jboss.com/jira/browse/JBSEAM-1643 Project: JBoss Seam Issue Type: Feature Request Reporter: Matt Drees Priority: Minor Fix For: 2.0.0.CR1 If you define two page elements with the same view-id in pages.xml, Seam doesn't complain at all. This can be confusing. -- 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, 1 month

6
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml

by Pete Muir (JIRA)

Hotdeployed components can't be configured through components.xml ----------------------------------------------------------------- Key: JBSEAM-2143 URL: http://jira.jboss.com/jira/browse/JBSEAM-2143 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Critical Fix For: 2.0.1.GA he hot deployment scanner is isolated, using a URLClassloader that is not available once that method comes to a close. The only way to make this work would be to keep that classloader alive during the rest of the startup process. I can direct you to the line of code that you need to look at if you are curious about it. Check out lines 540 and 541 or org.jboss.seam.init.Initialiation. The scanForHotDeployableComponents uses the following logic to create a component scanner: URL[] urls = { url }; classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); paths = new File[] { directory }; Once it processes the classes, that classloader is discarded and obviously, since it is a URLclassloader, the classes aren't going to be found later on. -- 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, 1 month

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1909) ajax4jsf:command pageflow action rerender

by Tomislav Jakopec (JIRA)

ajax4jsf:command pageflow action rerender ----------------------------------------- Key: JBSEAM-1909 URL: http://jira.jboss.com/jira/browse/JBSEAM-1909 Project: JBoss Seam Issue Type: Feature Request Reporter: Tomislav Jakopec When I use ajax4jsf:commandButton calling bean action rerender of components is working fine, but when I call pageflow action entire page is reloaded instead of rerender of particular component I created example application to show the problem. You could downloaded from: http://popovac.hr/orka/test.ear I reported this issue on RichFaces JIRA and they said that should be future request on SEAM, so here it is. -- 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, 1 month

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2035) Better handling of empty extended EL method expressions in pages.xml

by Pete Muir (JIRA)

Better handling of empty extended EL method expressions in pages.xml -------------------------------------------------------------------- Key: JBSEAM-2035 URL: http://jira.jboss.com/jira/browse/JBSEAM-2035 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Fix For: 2.0.x Currently you have to match a call to #{foo.bar()} with an from-action="#{foo.bar()}" - it probably makes sense to relax this restriction -- 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, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2090) Improve handling of h:selectManyXXX updating the mode with a new list

by Pete Muir (JIRA)

Improve handling of h:selectManyXXX updating the mode with a new list --------------------------------------------------------------------- Key: JBSEAM-2090 URL: http://jira.jboss.com/jira/browse/JBSEAM-2090 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.x Currently JSF sets a new list on the model which causes a load of deletes and inserts. Perhaps we can handle this better (dunno how) -- 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, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1266) Mathematical captcha & Email obfuscator

by Stephan Kleine (JIRA)

Mathematical captcha & Email obfuscator --------------------------------------- Key: JBSEAM-1266 URL: http://jira.jboss.com/jira/browse/JBSEAM-1266 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.3.0.BETA1 Environment: Tested with Seam CVS on JBoss AS 4.2.0CR2 Reporter: Stephan Kleine Hello, I would like to donate some stuff to seam: 1. A component that converts strings into (hexa)decimal html entities. 2. A tag to use this obfuscator (mainly a shortcut for h:outputText escape="false" ...). 3. A mathematical captcha that asks for the solutions of simple equations (like they use at jroller). The equation can be obuscated with the tag described at 2.. 4. A tag to obfuscate email addresses (see [url]http://www.seowebsitepromotion.com/obfuscate_email.asp[/url] for more details). Would be great if you include it in 1.3 ;) Regards Stephan -- 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, 1 month

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1531) Document pages.xsd and maybe other .xsds with xsd:documentation

by Michael Youngstrom (JIRA)

Document pages.xsd and maybe other .xsds with xsd:documentation --------------------------------------------------------------- Key: JBSEAM-1531 URL: http://jira.jboss.com/jira/browse/JBSEAM-1531 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Michael Youngstrom The pages.xsd is fairly vast. It could benefit greatly by some <xsd:documentation> elements. XML editors such as Eclipse WTP will pick up these xsd:documentation elements and provide context help. -- 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, 1 month

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1165) RGB color support for pdf

by Dustin Norlander (JIRA)

RGB color support for pdf ------------------------- Key: JBSEAM-1165 URL: http://jira.jboss.com/jira/browse/JBSEAM-1165 Project: JBoss Seam Issue Type: Feature Request Components: PDF Reporter: Dustin Norlander Support colors of the form: rgb(255,0,0) or rgb(100%, 0%, 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, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-683) Allow components.xml XSDs to be packaged in the jar with the components.

by Gavin King (JIRA)

Allow components.xml XSDs to be packaged in the jar with the components. ------------------------------------------------------------------------- Key: JBSEAM-683 URL: http://jira.jboss.com/jira/browse/JBSEAM-683 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Norman Richards Priority: Blocker Fix For: 1.1.5.GA Currently seam resolves XSDs in the path org/jboss/seam. But it would be better if the XSD for org.jboss.seam.core was located in the org/jboss/seam/core directory. This issue shows up with the mail stuff.... -- 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
6
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