October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1912) Incorrect graphicImage attribute in validation.xml

by Ali Sadik Kumlali (JIRA)

Incorrect graphicImage attribute in validation.xml -------------------------------------------------- Key: JBSEAM-1912 URL: http://jira.jboss.com/jira/browse/JBSEAM-1912 Project: JBoss Seam Issue Type: Patch Components: Documentation Affects Versions: 2.0.0.BETA1 Environment: Does not matter Reporter: Ali Sadik Kumlali Priority: Trivial Hi, <h:graphicImage/> does not have "src" attribute as shown in http://docs.jboss.com/seam/2.0.0.B1/reference/en/html/validation.html and it must be replaced by "value". Incorrect: <h:graphicImage src="img/error.gif" rendered="#{invalid}"/> Correct: <h:graphicImage value="/img/error.gif" rendered="#{invalid}"/> Please also note that "/" character preceding "img". An extra information that explains where to put "img" folder would be useful, as well. Regards, Ali Sadik Kumlali -- 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, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1385) Use ELResolver instead of Namespace extends Map for namespaces

by Gavin King (JIRA)

Use ELResolver instead of Namespace extends Map for namespaces -------------------------------------------------------------- Key: JBSEAM-1385 URL: http://jira.jboss.com/jira/browse/JBSEAM-1385 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Minor Fix For: 1.3.0.ALPHA That's more elegant. -- 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, 1 month

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1939) Only the first action is executed inside a page node in a jPDL pageflow

by Matthew Lieder (JIRA)

Only the first action is executed inside a page node in a jPDL pageflow ----------------------------------------------------------------------- Key: JBSEAM-1939 URL: http://jira.jboss.com/jira/browse/JBSEAM-1939 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.CR1 Environment: JRE 1.5, Tomcat 5.5.23 Reporter: Matthew Lieder Multiple <action> elements are allowed as children of <page> and <start-page> elements in a jPDL pageflow, but only the first <action> is executed. Please fix it so that all <action> elements are executed (like they are when children of <transition> elements). Example: <page name="page1" view-id="/page1.xhtml"> <action expression="#{someMethodThatIsExecuted} /> <action expression="#{someMethodThatIsNotExecuted} /> <transition name="save" to="terminate"> <action expression="#{someMethodThatIsExecuted} /> <action expression="#{someMethodThatIsExecuted} /> </transition> </page> -- 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, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-716) <core:transactionListener/> documentation

by Stephan Bublava (JIRA)

<core:transactionListener/> documentation ----------------------------------------- Key: JBSEAM-716 URL: http://jira.jboss.com/jira/browse/JBSEAM-716 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.1.1.GA Reporter: Stephan Bublava Could you please add <core:transactionListener/> (as used in the booking example components.xml) to the reference documentation? (What does it do? In which cases is it needed?) -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2163) When an exception in a converter is thrown, it in not properly handled by <exception...> in pages.xml

by Adam Warski (JIRA)

When an exception in a converter is thrown, it in not properly handled by <exception...> in pages.xml ----------------------------------------------------------------------------------------------------- Key: JBSEAM-2163 URL: http://jira.jboss.com/jira/browse/JBSEAM-2163 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Adam Warski Suppose we have an page parameter, which uses a converter: <page view-id="/test.xhtml"> <param name="param1" value="#{testBean.param1}" converterId="conv1" /> </page> and that during conversion an exception is thrown. It is declared as handled in pages.xml: <exception class="org.jboss.seam.test3.ConverterTestException"> <redirect view-id="/error.xhtml"> <message>Error: converter</message> </redirect> </exception> But the message "Error: converter" is not shown by <h:messages> on error.xhtml. Attached is a testcase for this, both with sources and binaries. -- 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, 1 month

2
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-843) Seam-gen Enchancement

by Kent Lam (JIRA)

Seam-gen Enchancement --------------------- Key: JBSEAM-843 URL: http://jira.jboss.com/jira/browse/JBSEAM-843 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.1.6.GA Reporter: Kent Lam Priority: Minor Would it be great that seam-gen will generate crud pages and classes for an existing Entity class,just like seam-gen generate the crud pages,classes and entity classes from database. Thanks -- 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, 1 month

9
26
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1166) seam-gen should be able to generate views from entity class

by Wenhu Guan (JIRA)

seam-gen should be able to generate views from entity class ----------------------------------------------------------- Key: JBSEAM-1166 URL: http://jira.jboss.com/jira/browse/JBSEAM-1166 Project: JBoss Seam Issue Type: Feature Request Reporter: Wenhu Guan The function should be same as generate views from database schema -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1801) Add attribute to <s:selectItems> allowing arbitrary values to be used as form "value"'s

by Matthew Lieder (JIRA)

Add attribute to <s:selectItems> allowing arbitrary values to be used as form "value"'s --------------------------------------------------------------------------------------- Key: JBSEAM-1801 URL: http://jira.jboss.com/jira/browse/JBSEAM-1801 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Matthew Lieder Say we have the following: <h:selectOneMenu value="#{curPerson.favoritePerson}"> <s:selectItems value="#{people}" var="person" label="#{person.fullName}" /> </h:selectOneMenu> The problem is that when the form is submitted, the value of "person.toString()" is stored in curPerson.favoritePerson. In some situations that might be acceptable, but not if the class doesn't have a guaranteed unique toString implementation. In this specific example, person.SSN would be the wanted field. To solve this problem, I recommend adding an "index" attribute functioning like the "label" attribute, except that the evaluated value is used for the "value" attribute in the generated HTML (the value that is submitted by the form). Should be pretty easy, I'm guessing? -- 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, 1 month

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2173) enableFilter: for ( Map.Entry<String, ValueExpression> me: f.getParameters().entrySet() ) throws NPE if there're no parameters

by jarkko Lietolahti (JIRA)

enableFilter: for ( Map.Entry<String, ValueExpression> me: f.getParameters().entrySet() ) throws NPE if there're no parameters ------------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-2173 URL: http://jira.jboss.com/jira/browse/JBSEAM-2173 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: jarkko Lietolahti Fix For: 1.2.1.GA HibernatePersistenceProvider: @Override public void enableFilter(Filter f, EntityManager entityManager) { try { org.hibernate.Filter filter = getSession(entityManager).enableFilter( f.getName() ); for ( Map.Entry<String, ValueExpression> me: f.getParameters().entrySet() ) { filter.setParameter( me.getKey(), me.getValue().getValue() ); } filter.validate(); } catch (NotHibernateException nhe) { super.enableFilter(f, entityManager); } } -- 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, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2174) ELResolvers added by BaseSeamTest are not usable as property resolvers (as opposed to base/variable resolvers)

by Matt Drees (JIRA)

ELResolvers added by BaseSeamTest are not usable as property resolvers (as opposed to base/variable resolvers) -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2174 URL: http://jira.jboss.com/jira/browse/JBSEAM-2174 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.0.0.CR3 Reporter: Matt Drees When you add an ELResolver by overriding BaseSeamTest.getELResolvers(), your resolver is added (in MockApplication) after the default CompositeELResolver, which includes a BeanELResolver. BeanELResolver throws a PropertyNotFoundException when it can't resolve a property, which prevents your custom resolver from being consulted. Therefore, BeanELResolver really should be placed at the very end of the chain, not your custom resolver(s). -- 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, 1 month

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2007