November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2280) Include the ability to use @Asynchronous with @Observer

by Damian Harvey (JIRA)

Include the ability to use @Asynchronous with @Observer ------------------------------------------------------- Key: JBSEAM-2280 URL: http://jira.jboss.com/jira/browse/JBSEAM-2280 Project: JBoss Seam Issue Type: Feature Request Components: Async Environment: Mac OSX, Jboss 4.2.1 Reporter: Damian Harvey @Asynchronous and @Observer cannot be used in conjunction in the current release. It results in the following error: Caused by: java.lang.NoSuchMethodException: java.util.ArrayList.rebuildTradeRoute() at java.lang.Class.getMethod(Class.java:1581) at org.jboss.seam.async.AsynchronousInvocation.call(AsynchronousInvocation.java:45) Events.raiseAsynchronousEvent is an option but using annotations is cleaner. Cheers, Damian. -- 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, 6 months

2
1
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

16 years, 6 months

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

16 years, 6 months

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

16 years, 6 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2246) Seam 2.0.0.GA docs for seam-gen are out of date

by Polly McEldowney (JIRA)

Seam 2.0.0.GA docs for seam-gen are out of date ----------------------------------------------- Key: JBSEAM-2246 URL: http://jira.jboss.com/jira/browse/JBSEAM-2246 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.0.GA Environment: firefox 2.0.0.9 Reporter: Polly McEldowney Priority: Minor The online seam-gen docs in the GA release here: http://docs.jboss.com/seam/2.0.0.GA/reference/en/html/gettingstarted.html refer to an older version of seam-gen - the screen output for 'seam setup' in section 2.2 doesn't have the new stuff about integrating ICEFaces, RichFaces skins etc. -- 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, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2260) <navigation if-outcome="xxx"> => <rule if-outcome="xxx">

by Tobias Kilian (JIRA)

<navigation if-outcome="xxx"> => <rule if-outcome="xxx"> ----------------------------------------------------------- Key: JBSEAM-2260 URL: http://jira.jboss.com/jira/browse/JBSEAM-2260 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Tobias Kilian Priority: Minor http://docs.jboss.com/seam/2.0.0.GA/reference/en/html/events.html section 5.1.1.2. at the bottom <page view-id="/editDocument.xhtml"> <navigation if-outcome="success"> <redirect view-id="/#{userAgent}/displayDocument.xhtml"/> </navigation> </page> should be changed to <page view-id="/editDocument.xhtml"> <navigation> <rule if-outcome="success"> <redirect view-id="/#{userAgent}/displayDocument.xhtml"/> </rule> </navigation> </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

16 years, 6 months

2
3
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

16 years, 6 months

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

16 years, 6 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2276) rich:messages is broken when FacesMessages is used from an action that returns an outcome

by Gavin King (JIRA)

rich:messages is broken when FacesMessages is used from an action that returns an outcome ----------------------------------------------------------------------------------------- Key: JBSEAM-2276 URL: http://jira.jboss.com/jira/browse/JBSEAM-2276 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Gavin King Priority: Critical 1. Create a project using JBoss Tools 2. Create an action called "hello" 3. Test it (works) 4. Change /home.xhtml to use rich:messages instead of h:messages 5. Changle Hello.java as follows: public String hello() { //implement your business logic here log.info("hello.hello() action called by #{identity.username}"); facesMessages.add("hello"); return "/home.xhtml"; } 6. Test it (the message is not displayed correctly) -- 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, 6 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2273) DocumentStoreServlet causes java.lang.IllegalStateException: No active event context

by Joshua Partogi (JIRA)

DocumentStoreServlet causes java.lang.IllegalStateException: No active event context ------------------------------------------------------------------------------------ Key: JBSEAM-2273 URL: http://jira.jboss.com/jira/browse/JBSEAM-2273 Project: JBoss Seam Issue Type: Bug Components: PDF Affects Versions: 2.0.0.GA Environment: JBoss 4.2.1 GA Reporter: Joshua Partogi Fix For: 2.0.1.GA If we add the DocumentStoreServlet to web.xml and add the pdf component to components.xml it will cause java.lang.IllegalStateException: No active event 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, 6 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007