December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2289) Provide no-arg constructor for SeamExpressionFactory

by Florent Guilllaume (JIRA)

Provide no-arg constructor for SeamExpressionFactory ---------------------------------------------------- Key: JBSEAM-2289 URL: http://jira.jboss.com/jira/browse/JBSEAM-2289 Project: JBoss Seam Issue Type: Feature Request Components: EL Affects Versions: 2.0.0.GA Reporter: Florent Guilllaume Priority: Minor I'd like a public no-arg constructor to SeamExpressionFactory: public SeamExpressionFactory() { super(INSTANCE); } The reason is that I want a facelet view handler extending FaceletViewHandler with the Seam expression factory. To do that I would use: @Override protected Compiler createCompiler() { Compiler compiler = super.createCompiler(); compiler.setFeature(Compiler.EXPRESSION_FACTORY, "org.jboss.seam.el.SeamExpressionFactory"); return compiler; } But a Compiler.EXPRESSION_FACTORY expects a class with a no-arg constructor (see com.sun.facelets.compiler.Compiler#createExpressionFactory and #featureInstance). As a workaround I can use my own subclass of SeamExpressionFactory but the super constructor SeamExpressionFactory(ExpressionFactory expressionFactory), which I need to call, is package-private. So I have to use the package org.jboss.seam.el just to call that constructor, which is not nice. Just having a no-arg constructor would simplify all this. -- 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2115) Better tests for NthBusinessDay

by Pete Muir (JIRA)

Better tests for NthBusinessDay ------------------------------- Key: JBSEAM-2115 URL: http://jira.jboss.com/jira/browse/JBSEAM-2115 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Minor Fix For: 2.0.x -- 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, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1371) Unable to use TestNG groups with SeamTest

by Samuel Mendenhall (JIRA)

Unable to use TestNG groups with SeamTest ----------------------------------------- Key: JBSEAM-1371 URL: http://jira.jboss.com/jira/browse/JBSEAM-1371 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 1.2.1.GA Reporter: Samuel Mendenhall Priority: Minor testng xml in build.xml ++++++++++++++++++++++++++++++ <testng outputdir="${basedir}/test-report" groups="SomeGroups"> <classfileset dir="classes" includes="**/*.class" /> <classpath path="${test.dir}" /> <classpath path="${embedded-ejb3.dir}" /> <classpath refid="build.classpath" /> </testng> ++++++++++++++++++++++++++++++ EmptyTest.java ++++++++++++++++++++++++++++++ public class EmptyTest extends SeamTest { @Test(groups = {"SomeGroups"}) public void testNothing() throws Exception { new FacesRequest() { @Override protected void invokeApplication() throws Exception { assert true; } }.run(); } @Test public void testNothingAgain() throws Exception { assert true; } } ++++++++++++++++++++++++++++++ command: ++++++++++++++++++++++++++++++ ant test ++++++++++++++++++++++++++++++ Exception: ++++++++++++++++++++++++++++++ [testng] java.lang.NullPointerException [testng] at org.jboss.seam.mock.SeamTest$Request.run(SeamTest.java:418) [testng] at com.mydomain.convotest.EmptyTest.testNothing(EmptyTest.java:10) .. ++++++++++++++++++++++++++++++ -- 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, 7 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2127) Need redirection back to current view after session timeout

by Samuel Mendenhall (JIRA)

Need redirection back to current view after session timeout ----------------------------------------------------------- Key: JBSEAM-2127 URL: http://jira.jboss.com/jira/browse/JBSEAM-2127 Project: JBoss Seam Issue Type: Feature Request Reporter: Samuel Mendenhall Priority: Minor When the session times out the user should be redirected back to the page he or she was last working 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, 7 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1858) Ability to avoid view path repetition in pages.xml

by Matt Drees (JIRA)

Ability to avoid view path repetition in pages.xml -------------------------------------------------- Key: JBSEAM-1858 URL: http://jira.jboss.com/jira/browse/JBSEAM-1858 Project: JBoss Seam Issue Type: Feature Request Reporter: Matt Drees Priority: Minor It would be fantastic if instead of this: <page view-id="/admin/modules/additionalExpenses/registrantTypeSettings.xhtml"> <navigation from-action="#{additionalExpensesAdminManager.newExpense}"> <redirect view-id="/admin/modules/additionalExpenses/editExpense.xhtml"/> </navigation> <navigation from-action="#{additionalExpensesAdminManager.newSectionHeader}"> <redirect view-id="/admin/modules/additionalExpenses/editSectionHeader.xhtml"/> </navigation> </page> I could do this: <pages view-scope="/admin/modules/additionalExpenses/"> <page view-id="registrantTypeSettings.xhtml"> <navigation from-action="#{additionalExpensesAdminManager.newExpense}"> <redirect view-id="editExpense.xhtml"/> </navigation> <navigation from-action="#{additionalExpensesAdminManager.newSectionHeader}"> <redirect view-id="editSectionHeader.xhtml"/> </navigation> </page> </pages> It would be best if <pages> could be nested in other <pages>, but there are probably some other ramifications of that, so maybe it'd be better to introduce another element. Maybe <view-scope> or something. -- 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, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2365) parametized page definitions

by koen handekyn (JIRA)

parametized page definitions ----------------------------- Key: JBSEAM-2365 URL: http://jira.jboss.com/jira/browse/JBSEAM-2365 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: koen handekyn Priority: Minor for typical administration pages one typicalle has a ' list + search ' with corresponding details page. for each of the details pages of all of the editable entities i'm repeating the below <page view-id="/up/admin/portalConfiguration.xhtml" conversation="portalConfigurationConversation" > <begin-conversation nested="true" /> <navigation from-action="#{backingBean['persist']"> <end-conversation /> <redirect view-id="/up/admin/portalConfigurationList.xhtml" /> </navigation> <navigation from-action="#{backingBean['update']}"> <end-conversation /> <redirect view-id="/up/admin/portalConfigurationList.xhtml" /> </navigation> <navigation from-action="#{backingBean['remove']"> <end-conversation /> <redirect view-id="/up/admin/portalConfigurationList.xhtml" /> </navigation> </page> as GK started of seam with DRY in mind, this repetion should be avoidable. i propose a solution like the following <page view-id="/up/admin/*.xhtml" conversation="%{page}Conversation" > <begin-conversation nested="true" /> <navigation from-action="#{backingBean['persist']"> <end-conversation /> <redirect view-id="/up/admin/%{page}List.xhtml" /> </navigation> <navigation from-action="#{backingBean['update']}"> <end-conversation /> <redirect view-id="/up/admin/%{page}List.xhtml" /> </navigation> <navigation from-action="#{backingBean['remove']"> <end-conversation /> <redirect view-id="/up/admin/%{page}List.xhtml" /> </navigation> </page> i.e. when a page matches " view-id="/up/admin/*.xhtml" " the * is matched and assigned to a variable " page " that can be used below. -- 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, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1990) Reloading app causes IllegalStateException when passivating session objects

by Matt Drees (JIRA)

Reloading app causes IllegalStateException when passivating session objects --------------------------------------------------------------------------- Key: JBSEAM-1990 URL: http://jira.jboss.com/jira/browse/JBSEAM-1990 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR1 Environment: Tomcat 5.5 Reporter: Matt Drees Priority: Minor I haven't tested in other appservers. Reloading the Hibernate example causes the following stacktrace: Sep 26, 2007 9:15:37 PM org.apache.catalina.session.StandardSession passivate SEVERE: Session attribute event listener threw exception java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36) at org.jboss.seam.contexts.Lifecycle.beginCall(Lifecycle.java:84) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:113) at org.jboss.seam.intercept.RootInterceptor.invokeAndHandle(RootInterceptor.java:84) at org.jboss.seam.intercept.JavaBeanInterceptor.callPrePassivate(JavaBeanInterceptor.java:135) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:77) at org.jboss.seam.example.hibernate.HotelSearchingAction_$$_javassist_2.sessionWillPassivate(HotelSearchingAction_$$_javassist_2.java) at org.apache.catalina.session.StandardSession.passivate(StandardSession.java:764) at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:515) at org.apache.catalina.session.StandardManager.unload(StandardManager.java:462) at org.apache.catalina.session.StandardManager.stop(StandardManager.java:666) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4345) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2984) at org.apache.catalina.manager.ManagerServlet.reload(ManagerServlet.java:906) at org.apache.catalina.manager.HTMLManagerServlet.reload(HTMLManagerServlet.java:473) -- 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, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2331) EntityHome throws "EntityManager is closed" when app marked <distributable/>

by Chris Fraser (JIRA)

EntityHome throws "EntityManager is closed" when app marked <distributable/> ---------------------------------------------------------------------------- Key: JBSEAM-2331 URL: http://jira.jboss.com/jira/browse/JBSEAM-2331 Project: JBoss Seam Issue Type: Bug Reporter: Chris Fraser Attachments: WidgetHome.java Please see my forum post for details on this matter: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=124779 Attached to this ticket is the source for my WidgetHome EntityHome class. I can upload additional files from the project if that will help, but this can be easily recreated by seam-genning a new project, and generating entities from a DB that's got a single table (Widget) with 2 columns (widgetId, widgetName). Once that's done, drop my WidgetHome in place of the seam-genned one, mark the app <distributable/> in web.xml, build/deploy/run the app and you'll see the problem when you create/update a widget. If this is not a bug, then it would at least be nice to have some best practices documented for using EntityHomes (and, as it turns out, EntityQuerys) in an application that has been marked <distributable/>. -- 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, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2362) from-action "equals" requires a textual match not a semantical

by koen handekyn (JIRA)

from-action "equals" requires a textual match not a semantical --------------------------------------------------------------- Key: JBSEAM-2362 URL: http://jira.jboss.com/jira/browse/JBSEAM-2362 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: koen handekyn in my facelets page i'm referring to an action as " backinBean['persist'] " ( where backingBean is a facelet tag parameter that has the value accountHome ) in pages.xml one needs to use the same litteral string within example from-action, ie DOES NOT WORK <navigation from-action="#{accountHome.persist}"> <end-conversation /> <redirect view-id="/up/admin/accountList.xhtml" /> </navigation> DOES WORK <navigation from-action="#{backingBean['persist']}"> <end-conversation /> <redirect view-id="/up/admin/accountList.xhtml" /> </navigation> this is very weird to understand from within the pages.xml as this backingBean variable does not have any specific meaning in the context. i propose that the "EQUALS" for from-action should be performed on ' evaluated EL expressions ' ( the actual method pointer on the class ). -- 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, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2314) Provide non-event triggering Context for use in MethodContextInterceptor as the method context

by Kahli Burke (JIRA)

Provide non-event triggering Context for use in MethodContextInterceptor as the method context ---------------------------------------------------------------------------------------------- Key: JBSEAM-2314 URL: http://jira.jboss.com/jira/browse/JBSEAM-2314 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Kahli Burke Some profiling has shown that in some cases Event triggering/handling can represent a significant chunk of page processing time. I found that Event triggering from the MethodContextInterceptor results in 10 events per method call, due to its use of the BasicContext which has pre and post set and remove events. Would a non-event triggering base class for BasicContext make sense for use as the method context? -- 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, 7 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007