March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-718) Make exception object available in redirected/rendered view

by Peter Muir (JIRA)

Make exception object available in redirected/rendered view ----------------------------------------------------------- Key: JBSEAM-718 URL: http://jira.jboss.com/jira/browse/JBSEAM-718 Project: JBoss Seam Issue Type: Feature Request Reporter: Peter Muir -- 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

18 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1050) Enhanced EL working for all <s:> tags

by Greg Zoller (JIRA)

Enhanced EL working for all <s:> tags ------------------------------------- Key: JBSEAM-1050 URL: http://jira.jboss.com/jira/browse/JBSEAM-1050 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.0.GA Environment: n/a Reporter: Greg Zoller Priority: Minor Seam improves EL, notably the ability to call methods w/parameters, for its own attributes. For example <s:link action="#{foo.bar(a,b,c)}"> is valid and the correct method/parameters will be used. But... It seems that non-Seam attributes of these same tags are merely passed through to JSF. For example if I add a rendered attributed to <s:link> and try to use a method call w/parameters it chokes w/an exception complaining about the '('. I'm not advocating that Seam correct JSF's lost opportunity by redoing all JSF tags (unless you are really motivated), but certainly all the attributes of the <s:> tags Seam does support should handle the improved EL uniformly. Apologies if this is a dup. Nothing like this jumped out at me when I searched Jira. -- 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

18 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1015) Cannot disable built-in components

by Leszek Kowalski (JIRA)

Cannot disable built-in components ---------------------------------- Key: JBSEAM-1015 URL: http://jira.jboss.com/jira/browse/JBSEAM-1015 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Environment: Seam 1.2.0Patch1, Jetty 5.1.12 Reporter: Leszek Kowalski Since rev 1.152 of Initialization.java (JIRA-897) it is not possible to disable built-in Seam component in components.xml (using <ns:componentName installed="false"). Here is problematic code: //if this class already has the @Name annotation, the XML element //is just adding configuration to the existing component, don't //add another ComponentDescriptor (this is super-important to //allow overriding!) if ( nameAnnotation!=null && nameAnnotation.value().equals(name) ) { Install install = clazz.getAnnotation(Install.class); if ( install.value() ) { className = null; } } For all components with @Install annotation className is set to null and installComponentFromXmlElement() cannot create "not-installed ComponentDescriptor". -- 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

18 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-898) s:hasRole, etc in EL in pages.xml and other places

by Gavin King (JIRA)

s:hasRole, etc in EL in pages.xml and other places -------------------------------------------------- Key: JBSEAM-898 URL: http://jira.jboss.com/jira/browse/JBSEAM-898 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.7.GA Because of MyFaces inability to implement the JSF spec correctly, EL functions are not supported in lots of places they are useful. We need to find a better way. -- 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

18 years, 10 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1089) Allow extended EL method expression construction programmatically

by Mike Quilleash (JIRA)

Allow extended EL method expression construction programmatically ----------------------------------------------------------------- Key: JBSEAM-1089 URL: http://jira.jboss.com/jira/browse/JBSEAM-1089 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash The enhanced EL parser for method parameters is not available programmatically. e.g. facesContext.getApplication().getExpressionFactory().createMethodExpression( "#{bean.func( param )}" ); This is because the expression factory is only loaded into the facelets compiler not the JSF application. As Seam already has an overriden Application implementation (SeamApplication12) it should be trivial to change this so getExpressionFactory() returns the SeamExpressionFactory which would delegate down to the default getExpressionFactory(). Then the enhanced EL would be available in the API as well as facelets files. (Facelets just calls Application.getExpressionFactory() so this should work as it did before). This would be extremely useful for me as I do a fair bit of dynamic component/EL generation. -- 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

18 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-842) s:hasRole() in jBPM EL.

by Gavin King (JIRA)

s:hasRole() in jBPM EL. ----------------------- Key: JBSEAM-842 URL: http://jira.jboss.com/jira/browse/JBSEAM-842 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Shane Bryzak Priority: Critical Currently, jBPM uses its own forked EL (which is a problem to begin with....). This means that it can't see the s: functions. We need to fix this problem ASAP. -- 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

18 years, 10 months

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1114) EntitySecurityListener problem in unit tests

by Artur Chyzy (JIRA)

EntitySecurityListener problem in unit tests -------------------------------------------- Key: JBSEAM-1114 URL: http://jira.jboss.com/jira/browse/JBSEAM-1114 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.0.GA Environment: Windows XP SP2, JBoss AS EJB3 profile 4.0.5.GA Reporter: Artur Chyzy When putting to orm.xml config for EntitySecurityListener <persistence-unit-metadata> <persistence-unit-defaults> <entity-listeners> <entity-listener class="org.jboss.seam.security.EntitySecurityListener"/> </entity-listeners> </persistence-unit-defaults> </persistence-unit-metadata> and trying to run unit tests the following exception is thrown java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.hibernate.ejb.event.ListenerCallback.invoke(ListenerCallback.java:33) at org.hibernate.ejb.event.EntityCallbackHandler.callback(EntityCallbackHandler.java:78) at org.hibernate.ejb.event.EntityCallbackHandler.postLoad(EntityCallbackHandler.java:71) at org.hibernate.ejb.event.EJB3PostLoadEventListener.onPostLoad(EJB3PostLoadEventListener.java:35) at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:201) at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842) at org.hibernate.loader.Loader.doQuery(Loader.java:717) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2821) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.jav a:370) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:351) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:122) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:808) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:801) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:155) at pl.alternativ.med.pacjent.DeklaracjaPOZUnitTest.utworz(DeklaracjaPOZUnitTest.java:78) at org.hibernate.ejb.event.ListenerCallback.invoke(ListenerCallback.java:30) ... 42 more Caused by: java.lang.IllegalStateException: No active session context at org.jboss.seam.security.Identity.instance(Identity.java:108) at org.jboss.seam.security.EntitySecurityListener.postLoad(EntitySecurityListener.java:24) ... 47 more ... Removed 26 stack frames Without EntitySecurityListener config in orm.xml tests runs fine. -- 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

18 years, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1115) Conversation propagation problem in integration tests

by Artur Chyzy (JIRA)

Conversation propagation problem in integration tests ----------------------------------------------------- Key: JBSEAM-1115 URL: http://jira.jboss.com/jira/browse/JBSEAM-1115 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.0.GA Environment: Windows XP SP2, JBoss 4.0.5GA Reporter: Artur Chyzy When trying to run integration test with following config in edit.page.xml <navigation from-action="#{someBean.select}"> <begin-conversation nested="true"/> <redirect view-id="/edit.jspx" /> </navigation> after invoking of select method the conversation is not long running (the object added using Contexts.getConversationContext().set() is not put to the conversation) and Manager.instance().isLongRunningConversation() return false Using @Begin on select method works fine. -- 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

18 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-668) method bindings with a parameter don't work in facelets tag source files

by Guy Veraghtert (JIRA)

method bindings with a parameter don't work in facelets tag source files ------------------------------------------------------------------------ Key: JBSEAM-668 URL: http://jira.jboss.com/jira/browse/JBSEAM-668 Project: JBoss Seam Issue Type: Bug Reporter: Guy Veraghtert Attachments: seam-bug-method-parameter.zip Method bindings with a parameter on a parameterized target bean don't work in a facelets tag source file. java.lang.NullPointerException at org.jboss.seam.ui.facelet.MethodExpressionHelper.findParamTypes(MethodExpressionHelper.java:146) at org.jboss.seam.ui.facelet.MethodExpressionHelper.invokeTheExpression(MethodExpressionHelper.java:98) at org.jboss.seam.ui.facelet.ParamMethodExpression.invoke(ParamMethodExpression.java:62) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96) -- 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

18 years, 10 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1121) exception instantiating model validator is very difficult to debug

by Keith Naas (JIRA)

exception instantiating model validator is very difficult to debug ------------------------------------------------------------------ Key: JBSEAM-1121 URL: http://jira.jboss.com/jira/browse/JBSEAM-1121 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.1.GA Reporter: Keith Naas Within the ModelValidator, if an exception is thrown while validating the value, the original exception is neither nested in the ValidatorException nor is it logged. It turns out that one of our validators was causing the Hibernate validator to throw an IllegalArgumentException. We have since fixed it, but we would like to see the code changed in the ModelValidator to make it a bit easier to debug in the future.. catch (Exception e) { throw new ValidatorException( new FacesMessage(FacesMessage.SEVERITY_ERROR, "model validation failed:" + e.getMessage(), null) ); } -- 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

18 years, 10 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2007