September 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3903) CRUD is conversational, but seam-gen apps are not conversational enough

by Francisco Jose Peredo Noguez (JIRA)

CRUD is conversational, but seam-gen apps are not conversational enough ----------------------------------------------------------------------- Key: JBSEAM-3903 URL: https://jira.jboss.org/jira/browse/JBSEAM-3903 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.SP1 Reporter: Francisco Jose Peredo Noguez Lets say you have 2 classes: class Parent{ private Long id; private Integer version; private String name; private Set <Child> children; } and class Child{ private Long id;private Integer version; private String name; private Parent parent; } with a typical one to many / many to one relationship (Parent.children.Child/Child.parent.Parent) So you want them to become @Entities and add the required @Annotations. Then you run seam-gen on them, and run you generated application: 1. You click the Parent List menu option. 2. You are presented with the page ParentList.seam that allows you search parents, or to create a new one. 3. You click the Create parent button. 4. You write a name for the parent: "Peter". 5. You click "Save". 6. You are presented with the page Parent.seam, that displays you newly persisted entity in a "read-only way" 7. You click "Done" so far so good... but then 1. You click the Child List menu option. 2. You are presented with the page ChildList.seam that allows you search children, or to create a new one 3. You click the Create child button. 4. You are presented with the page ChildEdit.seam. 5. You write a name for your new Child entity: "John" 6. You decide that you want connect this new Child entity with a parent entity, and then you click "Select parent". 7. You are presented again with ParentList.seam that allows you to "select" a parent. 8. So, you select "Peter" by clicking in the "Select" link 9. And you return to ChildEdit.seam, but the value for the name property of the Child is now LOST. I think seam-gen should be able to do this correctly (without losing the values in ChildEdit.seam). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2050) reorganize modules

by Dan Allen (JIRA)

reorganize modules ------------------ Key: JBSEAM-2050 URL: http://jira.jboss.com/jira/browse/JBSEAM-2050 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Fix For: 2.0.x I would like to make "modules" a first order directory (renamed from "src") and also organize tests so they are per-module. This will encourage per-module tests and also prevent circular dependencies (because the folders are treated as modules and not one big lump of source code). The ui module also once again finds itself adjacent to the other modules. jboss-seam/ examples/ <-- showing this just as a reference point modules/ core/ main/java test/java ui/ main/java test/java (continue for debug, ioc, gen, pdf, mail, remoting) Although Eclipse doesn't know the first think about multi-modules, this will be idea for setting up a module-aware IDE like IntelliJ IDEA (and to some degree, NetBeans). -- 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

14 years, 10 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1670) allow multiple scopes for @In annotation

by Dan Allen (JIRA)

allow multiple scopes for @In annotation ---------------------------------------- Key: JBSEAM-1670 URL: http://jira.jboss.com/jira/browse/JBSEAM-1670 Project: JBoss Seam Issue Type: Patch Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Dan Allen Priority: Minor Fix For: 2.0.0.CR1, 2.0.0.GA, 2.0.1.GA Right now, your only option for the scope on the @In annotation is an explicit scope or a hierarchical search of all the scopes. I can imagine that there are times when you want to look in a handful of scopes, but not all of them. For instance, anything within a conversation, but not above. Additionally, by making this a multi-value attribute, the developer can override the order in which the scopes are searched. They are searched in the order specified. ScopeType[] scope() default {}; This would also eliminate the need for the UNSPECIFIED scope since no scopes would assume a hierarchical search. The logic that would have to change is Component#getValueToInject() -- 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

14 years, 10 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1710) Support multiple life cycle methods (per inheritance) on JavaBean classes

by Dan Allen (JIRA)

Support multiple life cycle methods (per inheritance) on JavaBean classes ------------------------------------------------------------------------- Key: JBSEAM-1710 URL: http://jira.jboss.com/jira/browse/JBSEAM-1710 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1, 2.0.0.CR1 Reporter: Dan Allen Priority: Minor EJB supports multiple life cycle methods for a bean, as long as two life cycle methods do not appear in the same class in the inheritance hierarchy. Thus, you can define a @PostConstruct method on the concrete class, and a different @PostConstruct method on its superclass. As per the EJB specification (with minor corrections for clarity): "Life cycle callback interceptor methods may be defined on super classes of the bean class, the bean class itself, or interceptor classes. However, a given class may not have more than one life cycle callback interceptor method for the same life cycle event." The following comment is found in Component.java regarding this issue: // TODO: check the EJB3 spec, I think you are allowed to have multiple life cycle methods on a bean! The comment is correct in that multiple life cycle methods are not allowed on a single bean class. However, through inheritance, it is possible to have two different life cycle methods for the same Seam component. Currently, Component#initMembers() works backwards up the inheritance chain while scanning methods. Therefore, the life cycle method on the highest member of the hierarchy currently wins. So, as it stands now, the handling of life cycle callbacks for JavaBeans is inconsistent with how they are handled by the EJB container on session and message-driven beans. I was able to verify this with a simple demonstration I conducted. This incompatibility shouldn't be too difficult to fix. Just switch the life cycle method properties to an array and ensure that superclass methods are called first. -- 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

14 years, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1389) Please make the methods parse and createPage protected instead of private.

by Chris Rudd (JIRA)

Please make the methods parse and createPage protected instead of private. -------------------------------------------------------------------------- Key: JBSEAM-1389 URL: http://jira.jboss.com/jira/browse/JBSEAM-1389 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Chris Rudd We have a dynamic routine that locates pages xml files from multiple locations. Since parse and createPage are private methods we cannot override and extend the Pages component without lifting the entire source and replicating it, or using reflection to get at those methods. Neither of these are good long term aproaches. In general it seems that lots of the core components that one might want to extend to hook in additional functionality cannot be due to the use of private instead of protected methods. The extended funtionality provided by the resolution to JBSEAM-715 does not rectify my issue as that relies on explitly defining the pages xml files. I believe there are several other people who are looking for a way to use an algorithm to locate them rather than a fixed list. Making those methods protected solves the problem as it allows anyone to extend the functionaliry of the Pages component to provide extended rules / algorithms for locating pages xml files, while not affecting the functionality of the core at all. -- 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

14 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1194) Pageflow/Process documentation improvements

by Pete Muir (JIRA)

Pageflow/Process documentation improvements ------------------------------------------- Key: JBSEAM-1194 URL: http://jira.jboss.com/jira/browse/JBSEAM-1194 Project: JBoss Seam Issue Type: Bug Components: BPM, Documentation Reporter: Pete Muir Assigned To: Pete Muir The JBPM integration chapter is a constant source of confusion to me. -- 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

14 years, 10 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-664) transactionListener component should be implemented like Hibernate TMLookup

by Gavin King (JIRA)

transactionListener component should be implemented like Hibernate TMLookup --------------------------------------------------------------------------- Key: JBSEAM-664 URL: http://jira.jboss.com/jira/browse/JBSEAM-664 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.5.GA It would be MUCH better if we did not have an EJB sitting in jboss-seam.jar. -- 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

14 years, 10 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4413) Date format error in .page.xml params when having custom date pattern

by Julien Kronegg (JIRA)

Date format error in .page.xml params when having custom date pattern --------------------------------------------------------------------- Key: JBSEAM-4413 URL: https://jira.jboss.org/jira/browse/JBSEAM-4413 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Environment: Seam 2.1.2.GA, DB2 http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_1/src/main... Reporter: Julien Kronegg Priority: Minor The java.util.Date passed by <param> tags in the .page.xml file are converted from Date to String for the GET request, using the date format defined in the last used rich:calendar. Then, the GET parameters are converted back from String to Date using the default date format which may not be the same as the one defined in the rich:calendar. This results in date conversion errors such as "value must be a date, eg. 10/13/2008". The issue is fully described with an example in http://seamframework.org/Community/DateFormatErrorInPagexmlParamsASeamIssue To correct this issue, the org.jboss.seam.navigation.Param should use its own date converter instead of sharing the converter with other JSF components (in other words, the Param class should use a technical date converter). This requires the following steps: 1) define a org.jboss.seam.faces.DateParamConverter date converter with a selectable date format defaulted to "yyyyMMddHHmmssSSS" 2) change the org.jboss.seam.navigation.Param class to use a the DateParamConverter converter if the param value is java.util.Date, else, use the converters registered in JSF. This is done by changing: Class<?> type = valueExpression.getType(); if (type==null) { return null; } return FacesContext.getCurrentInstance().getApplication().createConverter(type); by Class<?> type = valueExpression.getType(); if (type==null) { return null; } + if (type.equals(Date.class)) { + return org.jboss.seam.faces.DateParamConverter.getInstance(); // return an instance of the technical converter, to be created + } else { return FacesContext.getCurrentInstance().getApplication().createConverter(type); + } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4325) ResourceLoader, moving from JBoss 4 to JBoss 5, page level messages.properties not workin any more.

by Riccardo Serafin (JIRA)

ResourceLoader, moving from JBoss 4 to JBoss 5, page level messages.properties not workin any more. --------------------------------------------------------------------------------------------------- Key: JBSEAM-4325 URL: https://jira.jboss.org/jira/browse/JBSEAM-4325 Project: Seam Issue Type: Feature Request Components: Core, Documentation Issues Reporter: Riccardo Serafin Fix For: 2.2.1.CR1 We have moved our app from JBoss 4.2.3 to 5.1 and our page level messages.properties stopped to work correctly. After analyzing the issue, we traced the problem to the ResourceLoader loadBundle method which uses the getContextClassloader to load the bundles. In out app, the .properties files where located in the WAR root along with the faceltes .xhtml and the .page.xml, which use to work fine on 4.2.3. It is my understanding that with 5.1 the classloader has changed, and the one retrieved via getContextClassloader does not have access to the ServletContext anymore, hence our properties file are not found any more. So, I suggest two things: 1) The documentation makes it explicit that the messages.properties file should be localed in WEB-INF/classes. The explanation for the page level messages.properties is instead a bit more open to interpretation. It could be good to reiterate there that also page level files need to go into WEB-INF/classes 2) Or, modify ResourceLoader to scan also the ServletContext for bundle files, which would make it compatible with apps that used to work on JBoss 4.2.3. Notice that the other ResourceLoader methods already use ServletLifecycle.getServletContext(), that is why .page.xml files can be nicely placed along .xhtml file in the context root. Thanks, Riccardo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4203) Interpolator swallows all exceptions

by Yuriy Lazarev (JIRA)

Interpolator swallows all exceptions ------------------------------------ Key: JBSEAM-4203 URL: https://jira.jboss.org/jira/browse/JBSEAM-4203 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.CR1 Environment: Any Reporter: Yuriy Lazarev org.jboss.seam.core.Interpolator swallows all exceptions, so if I have #{entityHome.instance.name} somewere in the page, and entityHome has id which is missed from database - I expect that org.jboss.seam.framework.EntityNotFoundException will be handled by this block in pages.xml <exception class = "org.jboss.seam.framework.EntityNotFoundException"> <redirect view-id = "/error.xhtml"> <message severity = "warn">#{messages['org.jboss.seam.framework.EntityNotFoundException']}</message> </redirect> </exception> but, instead I got [WARN] exception interpolating string: #{entityHome.instance.name} This is due Interpolator.java:131 } catch (Exception e) { log.warn("exception interpolating string: " + string, e); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2009