February 2008 - 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, 8 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2496) Allow customization of WEB-INF/dev/ location

by Christian Bauer (JIRA)

Allow customization of WEB-INF/dev/ location -------------------------------------------- Key: JBSEAM-2496 URL: http://jira.jboss.com/jira/browse/JBSEAM-2496 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Assigned To: Pete Muir Priority: Minor -- 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

3
5
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, 8 months

6
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2473) add container preInitialization event

by Dan Allen (JIRA)

add container preInitialization event ------------------------------------- Key: JBSEAM-2473 URL: http://jira.jboss.com/jira/browse/JBSEAM-2473 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.x It would be useful to be able to tap into the Seam container before it does an initialization run. This would give an opportunity to prep the Seam runtime by perhaps registering a custom converter or other such tasks without having to create a one-off servlet context listener. All the groundwork is in place...it is a very simple addition. -- 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

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2510) Warn when developer attempts @In(value="#{...}", create=false)

by Matt Drees (JIRA)

Warn when developer attempts @In(value="#{...}", create=false) -------------------------------------------------------------- Key: JBSEAM-2510 URL: http://jira.jboss.com/jira/browse/JBSEAM-2510 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Matt Drees Priority: Minor If a developer does something like this: @In(value="#{...}", create=false) the "create" attribute is silently ignored, because EL lookups always create components if necessary. This causes confusion. So, log a warning at startup. -- 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

3
5
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, 8 months

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2381) EntityQuery to stop fetching maxResults + 1 rows

by Brian Kalbfus (JIRA)

EntityQuery to stop fetching maxResults + 1 rows ------------------------------------------------ Key: JBSEAM-2381 URL: http://jira.jboss.com/jira/browse/JBSEAM-2381 Project: JBoss Seam Issue Type: Feature Request Components: EJB3 Affects Versions: 2.0.1.CR1, 2.0.0.GA Reporter: Brian Kalbfus In using a hibernate interceptor to audit instantiating entities, I noticed one extra record in excess of getMaxResults() is instantiated that isn't used - thus rendering a false audit. This was because of the following code in EntityQuery (copied from CVS head): <code> protected javax.persistence.Query createQuery() { parseEjbql(); evaluateAllParameters(); joinTransaction(); javax.persistence.Query query = getEntityManager().createQuery( getRenderedEjbql() ); setParameters( query, getQueryParameterValues(), 0 ); setParameters( query, getRestrictionParameterValues(), getQueryParameterValues().size() ); if ( getFirstResult()!=null) query.setFirstResult( getFirstResult() ); if ( getMaxResults()!=null) query.setMaxResults( getMaxResults()+1 ); //add one, so we can tell if there is another page if ( getHints()!=null ) { for ( Map.Entry<String, String> me: getHints().entrySet() ) { query.setHint(me.getKey(), me.getValue()); } } return query; } </code> Specifically: if ( getMaxResults()!=null) query.setMaxResults( getMaxResults()+1 ); //add one, so we can tell if there is another page The code says it is adding one so that it knows if there is another page. I see its use here: <code> public boolean isNextExists() { return resultList!=null && resultList.size() > getMaxResults(); } </code> I propose this for isNextExists(): <code> public boolean isNextExists() { return getResultCount() > (getFirstResult()!=null?getFirstResult():0) + getMaxResults(); } </code> Then we can change that line in createQuery() to: if ( getMaxResults()!=null) query.setMaxResults( getMaxResults() ); I did this in my subclass by overriding these two methods for my project; I had to copy in some of the private members of EntityQuery to do this. Thanks, Brian Kalbfus -- 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

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

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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2254) Wrong behaviour using a4j:include and pages.xml navigation

by Konstantin Grigoriev (JIRA)

Wrong behaviour using a4j:include and pages.xml navigation ---------------------------------------------------------- Key: JBSEAM-2254 URL: http://jira.jboss.com/jira/browse/JBSEAM-2254 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.GA Environment: JBoss Seam 2.0.0.G.A. RichFaces 3.1.2.G.A. JBossAS 4.2.2.G.A. Reporter: Konstantin Grigoriev Parent page includes firstTest.xhtml using a4j:include. firstTest.xhtml contains button: <a4j:commandButton action="next" value="next" /> Navigation in pages.xhtml: <page view-id="firstTest.xhtml"> <navigation> <rule if-outcome="next"> <redirect view-id="secondTest.xhtml" /> </rule> </navigation> </page> After pressing button whole page navigates to secondTest.xhtml, not only "a4j:include" element. In case of using faces-config.xml everything is ok. -- 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
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008