February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-726) Log interpolation throws exception when toString() uses braces

by Luke Maurer (JIRA)

Log interpolation throws exception when toString() uses braces -------------------------------------------------------------- Key: JBSEAM-726 URL: http://jira.jboss.com/jira/browse/JBSEAM-726 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.1.GA Reporter: Luke Maurer For example, if you write: Map<String, String> map = new HashMap<String, String>(); map.put("apple", "orange"); map.put("pear", "banana"); log.debug("A map: #0", map); and map is a HashMap or any Map implementation that formats itself similarly, and debug logging is enabled, you get an IllegalArgumentException saying "can't parse argument number apple=orange,pear=banana". The problem appears to be in Interpolator: public String interpolate(String string, Object... params) { // ... if ( string.indexOf('#')>=0 ) { string = interpolateExpressions(string, params); } if (params.length>0 && string.indexOf('{')>=0 ) { string = new MessageFormat(string, Locale.instance()).format(params); } return string; } The first if test passes and interpolateExpressions() interpolates the Map object into the string. Since this particular object's toString() method happens to format it using braces (e.g. "{apple=orange,pear=banana}" above), the second if test also passes, and the same parameters get interpolated *again*. When the part of the toString() representation between the braces fails to parse as a MessageFormat argument specifier, the IAE gets thrown. My guess is that an "else" is intended before the second "if" above, since it must be rare that one wants the same parameters interpolated twice. Otherwise, either the IAE should be caught and the log message left alone if it doesn't parse as a format string, or the documentation should state clearly that logging an object that represents itself using braces will throw an exception at run time. -- 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, 9 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-750) invalid XML in chapter 5 pages.xml examples

by Stephan Bublava (JIRA)

invalid XML in chapter 5 pages.xml examples -------------------------------------------- Key: JBSEAM-750 URL: http://jira.jboss.com/jira/browse/JBSEAM-750 Project: JBoss Seam Issue Type: Patch Components: Documentation Affects Versions: 1.1.5.GA Reporter: Stephan Bublava Priority: Trivial Attachments: chapter5-patch.txt Some pages.xml examples in chapter 5 use don't close the XML tags properly. (This is probably a copy & paste error). -- 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, 9 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-751) NPE if password is null

by Peter Muir (JIRA)

NPE if password is null ----------------------- Key: JBSEAM-751 URL: http://jira.jboss.com/jira/browse/JBSEAM-751 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 1.1.5.GA Reporter: Peter Muir Priority: Minor If you have a null password (e.g. I misspelt #{identity.password} on the form you get an NPE, something more descriptive would be nice :) -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-345) correct ejb-jar.xml root node declaration in examples

by Norman Richards (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-345?page=all ] Norman Richards closed JBSEAM-345. ---------------------------------- Resolution: Out of Date This was fixed some time ago. > correct ejb-jar.xml root node declaration in examples > ----------------------------------------------------- > > Key: JBSEAM-345 > URL: http://jira.jboss.com/jira/browse/JBSEAM-345 > Project: JBoss Seam > Issue Type: Task > Components: Examples > Affects Versions: 1.0.1, 1.0, 1.0 beta 2, 1.0 beta 1, 1.1.0.BETA1 > Reporter: Maurice Zeijen > Priority: Minor > > Please correct the root node decleration in the seam examples. At this moment they only contain the <ejb-jar> node but this should be: > <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee > http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" > version="3.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

18 years, 9 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-661) s:selectDate dynamic for-id in facelets

by Bram Biesbrouck (JIRA)

s:selectDate dynamic for-id in facelets --------------------------------------- Key: JBSEAM-661 URL: http://jira.jboss.com/jira/browse/JBSEAM-661 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.0.GA Reporter: Bram Biesbrouck If I use s:selectDate in a facelets-template, with a "dynamic" component-id in the "for" attribute (set by <ui:param name="id" value="theComponenetId" />), I get an exception: java.lang.NullPointerException: expr at javax.faces.component.UIComponentBase.findComponent(UIComponentBase.java:387) at org.jboss.seam.ui.SelectDate.encodeBegin(SelectDate.java:63) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:232) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:580) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:101) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:222) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ... -- 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, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-724) test failure due to PojoCache

by Gavin King (JIRA)

test failure due to PojoCache ----------------------------- Key: JBSEAM-724 URL: http://jira.jboss.com/jira/browse/JBSEAM-724 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.5.GA Reporter: Gavin King Assigned To: Norman Richards Fix For: 1.2.0.BETA1 Due to the recent change in the PojoCache component, I now get this failure in the test suite: Caused by: javax.management.InstanceNotFoundException: jboss.system:service=ServiceController at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:804) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:194) at org.jboss.seam.core.PojoCache.start(PojoCache.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0 It's caused by PostAction.post() in the blog example. Anyway to make PojoCache work in the test suite? -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-745) BijectionInterceptor not serializable

by Gavin King (JIRA)

BijectionInterceptor not serializable ------------------------------------- Key: JBSEAM-745 URL: http://jira.jboss.com/jira/browse/JBSEAM-745 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.5.GA, 1.1.1.GA Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.6 Due to ThreadLocal -- 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, 9 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-727) checkPermission() and checkRole() methods on Identity

by Gavin King (JIRA)

checkPermission() and checkRole() methods on Identity ----------------------------------------------------- Key: JBSEAM-727 URL: http://jira.jboss.com/jira/browse/JBSEAM-727 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.1.5.GA Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.0.BETA1 To have the option of throwing an exception instead of returning a boolean value. -- 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, 9 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-736) Identity extends AbstractMutable

by Gavin King (JIRA)

Identity extends AbstractMutable -------------------------------- Key: JBSEAM-736 URL: http://jira.jboss.com/jira/browse/JBSEAM-736 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.1.5.GA For performance, Identity should extend AbstractMutable and do dirty checking -- 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, 9 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-215) Create an XML schema or DTD for pageflow

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-215?page=all ] Gavin King updated JBSEAM-215: ------------------------------ Fix Version/s: 1.1.6 (was: 1.2.0.BETA1) > Create an XML schema or DTD for pageflow > ---------------------------------------- > > Key: JBSEAM-215 > URL: http://jira.jboss.com/jira/browse/JBSEAM-215 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.6 > > Attachments: pageflow-1.0.xsd > > > like it says -- 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, 9 months

1
0
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 2007