June 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1277) ServerConversationContext does not process removals / additions when an exception propagates up

by Chris Rudd (JIRA)

ServerConversationContext does not process removals / additions when an exception propagates up ----------------------------------------------------------------------------------------------- Key: JBSEAM-1277 URL: http://jira.jboss.com/jira/browse/JBSEAM-1277 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Reporter: Chris Rudd I have an Stateful EJB Component that throws an exception (this is expected, im testing that the system can recover from that error). This causes the component to be removed from the seam contexts (via the RemoveInterceptor). Then the exception floats up and is caught by the ExceptionFilter, and is redirected to a new view. All that works correctly. BUT when I return to the conversation that contained the EJB component, the component is still in it (even though the RemoveInterceptor removed it). Ive traced it down to this : ServerConversationContext.remove -- this adds the removal to the removals list, but does not update the session.attributes (the real storage for the context). ServerConversationContext.flush -- this applies the removals / additions to the session attributes map. The problem is that flush is never called when an exception propagates out. Thus the changes to that context are never flushed to the session attributes. -- 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

17 years, 6 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-808) StatckOverflowError if factory specifies it's component

by John Ray (JIRA)

StatckOverflowError if factory specifies it's component ------------------------------------------------------- Key: JBSEAM-808 URL: http://jira.jboss.com/jira/browse/JBSEAM-808 Project: JBoss Seam Issue Type: Bug Environment: Latest from CVS Reporter: John Ray I accidently specified the name of my component instead of a context variable and this resulted in a StatckOverflowError. For example @Stateful @Name("foo") @Scope(ScopeType.EVENT) public class FooAction implements Foo { @Out("bar") private String bar; @Factory("foo") public void initBar() { ... } } I'd sugest changing the code in org.jboss.seam.Component at line 490 to include an if/throw. I highlighted the 2 new lines with an asterisk if ( method.isAnnotationPresent(org.jboss.seam.annotations.Factory.class) ) { Init init = (Init) applicationContext.get( Seam.getComponentName(Init.class) ); //can't use Init.instance() here 'cos of unit tests String contextVariable = toName( method.getAnnotation(org.jboss.seam.annotations.Factory.class).value(), method ); * if (contextVariable.equals(name)) * throw new IllegalStateException("@Factory method can not be for it's own component: " + name); init.addFactoryMethod(contextVariable, method, 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

17 years, 6 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1428) Seam PDF does't do alignment inside cell

by Mikhail Grushinskiy (JIRA)

Seam PDF does't do alignment inside cell ---------------------------------------- Key: JBSEAM-1428 URL: http://jira.jboss.com/jira/browse/JBSEAM-1428 Project: JBoss Seam Issue Type: Bug Components: PDF Affects Versions: 1.3.0.ALPHA, 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Reporter: Mikhail Grushinskiy verticalAlignment, horizontalAlignment ignored -- 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

17 years, 7 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1183) Allow custom ExceptionHandler implementations to be inserted

by Mike Quilleash (JIRA)

Allow custom ExceptionHandler implementations to be inserted ------------------------------------------------------------ Key: JBSEAM-1183 URL: http://jira.jboss.com/jira/browse/JBSEAM-1183 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Currently you can only configure a small subset of actions to occur on an exception (redirect, http-error etc). Enhancing the exception configuration xml to allow pluggable ExceptionHandler implementations would make this a lot more flexible. e.g. pages.xml <pages>  <exception class="javax.persistence.EntityNotFoundException"> <http-error error-code="404"/> </exception>  <exception handlerClass="com.xxx.seam.CustomExceptionHandler"/> </pages> These should probably have higher precedence than standard configure-by-exception-class handlers. -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1485) Configure Default Interceptors

by Bruno E. Grossi (JIRA)

Configure Default Interceptors ------------------------------ Key: JBSEAM-1485 URL: http://jira.jboss.com/jira/browse/JBSEAM-1485 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: Linux with only Tomcat, not JBoss Reporter: Bruno E. Grossi Create an configuration option to disable some default interceptors that there are never used, improving the application's performance. On some systems there are no necessity of some interceptors, for example, the transactional ones (RollbackInterceptor, TransactionInterceptor and ManagedEntityIdentityInterceptor) that degrade performance. -- 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

17 years, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1146) Include optional Ant build-${profile}.xml in seam-gen/build-scripts

by Stephan Heffner (JIRA)

Include optional Ant build-${profile}.xml in seam-gen/build-scripts ------------------------------------------------------------------- Key: JBSEAM-1146 URL: http://jira.jboss.com/jira/browse/JBSEAM-1146 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.2.1.GA Reporter: Stephan Heffner Attachments: build.xml  <import file="build-${profile}.xml" optional="true"/> -- 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

17 years, 8 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1228) Add sort option to <s:selectItems>

by Stephan Bublava (JIRA)

Add sort option to <s:selectItems> ---------------------------------- Key: JBSEAM-1228 URL: http://jira.jboss.com/jira/browse/JBSEAM-1228 Project: JBoss Seam Issue Type: Patch Components: JSF Affects Versions: 1.2.1.GA Reporter: Stephan Bublava Attachments: sort-selectitems-patch.txt The attached patch adds a sort option to <s:selectItems>, that allows the entries to be sorted by their label. Example: <h:selectOneMenu value="#{person.honorific}"> <s:selectItems value="#{honorifics}" var="honorific" label="#{honorific.label}" noSelectionLabel="Please select" sort="ascending" /> <s:convertEnum /> </h:selectOneMenu> This version has not been tested in depth (especially interactions with "noSelectionLabel"), but I've been using similar code in our project (based upon Seam SelectItems 1.1.1beta1) for some time now and not encountered any problems. -- 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

17 years, 8 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1387) Support for overriding .cfg.xml properties in HibernateFactory (patch included)

by Przemyslaw Jaskierski (JIRA)

Support for overriding .cfg.xml properties in HibernateFactory (patch included) -------------------------------------------------------------------------------- Key: JBSEAM-1387 URL: http://jira.jboss.com/jira/browse/JBSEAM-1387 Project: JBoss Seam Issue Type: Feature Request Environment: Microcontainer Reporter: Przemyslaw Jaskierski Fix For: 1.3.0.ALPHA Attachments: HibernateFactory-patch.diff.zip Currently HibernateFactory supports only one type of configuration at a time: .cfg.xml file or "programmatic" one passed by the cfgProperties property. It would be great to have the ability to override individual properties from the specified .cfg.xml file using cfgProperties property. For example, when you want to have special value for hibernate.hbm2ddl.auto in case of tests only, and normal one in case of production environment. Applying my patch makes the following thing possible (instead of maintaing two almost identicall hibernate.cfg.xml files): <bean name="pecpHibernateSessionFactoryFactory" class="pecp.core.seam.HibernateFactory"> <property name="cfgResourceName"> <inject bean="pecpHibernateConfigurationLocation"/> </property> <property name="namingStrategy"> <inject bean="underscoreAwareNamingStrategy"/> </property> <property name="cfgProperties"> <map class="java.util.Hashtable" keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>hibernate.hbm2ddl.auto</key> <value>create-drop</value> </entry> </map> </property> </bean> I've kept original logical code flow intact, so when there is no cfgResourceName and no cfgProperties set, Seam (as in original case) tries to call configuration.configure() and try to configure from hibernate.cfg.xml file. To make override functionality work you need to specify cfgResourceName property. -- 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

17 years, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-905) Using the debug page without exceptions

by Christian Bauer (JIRA)

Using the debug page without exceptions --------------------------------------- Key: JBSEAM-905 URL: http://jira.jboss.com/jira/browse/JBSEAM-905 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer Priority: Minor I'd like to call /debug.seam manually to look into my conversations. I usually don't enable it because I don't like being redirected to it from an exception. Why? It hides the URL that caused the exception and it fills my log with hundreds of lines after the exception stacktrace. -- 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

17 years, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1457) ui example doesnt work in tomcat 5.5.23

by Bieth Bruno (JIRA)

ui example doesnt work in tomcat 5.5.23 --------------------------------------- Key: JBSEAM-1457 URL: http://jira.jboss.com/jira/browse/JBSEAM-1457 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Tomcat 5.5.23 Reporter: Bieth Bruno Can't run the ui example with tomcat 5.5.23 : After clicking one of the link on the main page I get : 15:10:49,124 ERROR [ExceptionFilter] could not roll back transaction javax.naming.NamingException: Local server is not initialized at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45) ... 15:10:50,265 ERROR [SeamPhaseListener] uncaught exception javax.faces.el.EvaluationException: Cannot set value for expression '#{personHome.id}' to a new valu e of type java.lang.Integer at org.apache.myfaces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:310) -- 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

17 years, 8 months

2
5
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 June 2007