November 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3907) Exclude build directories in generated IntelliJ IDEA project

by Pawel Wrzeszcz (JIRA)

Exclude build directories in generated IntelliJ IDEA project ------------------------------------------------------------ Key: JBSEAM-3907 URL: https://jira.jboss.org/jira/browse/JBSEAM-3907 Project: Seam Issue Type: Patch Components: Tools Affects Versions: 2.1.1.GA Reporter: Pawel Wrzeszcz Assignee: Dan Allen Priority: Minor Directories 'dist' and 'exploded-archives' should be marked as excluded in the IntelliJ IDEA module file created by seam-gen. I realize this is minor, but saves a couple of clicks and prevents IDEA from 1) reloading a whole project during the build and 2) detecting facets in the build directories. Really short path attached. -- 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, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3933) Sibling inner class wicket component injection conflict

by Clint Popetz (JIRA)

Sibling inner class wicket component injection conflict ------------------------------------------------------- Key: JBSEAM-3933 URL: https://jira.jboss.org/jira/browse/JBSEAM-3933 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.1.1.GA Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.1.2.CR1 In a class hierarchy such as this: class Page { @In Needed needed; Page() { add(new ListView("foo") { /* anonymous...*/ }); add(new ListView("bar") { /* anonymous...*/ }); } } if "foo" makes reference to "bar", or vice versa, the injection of "needed" will be trampled upon, because we don't update the reentrancy count of the enclosing instance when injection/disinjecting. -- 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, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3821) seam-gen - entity is not mapped in war project on AS5

by Jozef Hartinger (JIRA)

seam-gen - entity is not mapped in war project on AS5 ----------------------------------------------------- Key: JBSEAM-3821 URL: https://jira.jboss.org/jira/browse/JBSEAM-3821 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.CR2 Environment: JDK5 JBoss AS 5.0.0.GA Reporter: Jozef Hartinger Fix For: 2.1.2.CR1 Attachments: genWarRich.txt When accessing generated entity page the application is failing on "org.hibernate.hql.ast.QuerySyntaxException: Vehicle is not mapped [select vehicle from Vehicle vehicle]" . I am using standard release-process.txt database tables. To reproduce the issue: 1.) Create new war project and generate entities. 2.) Log into the application and click PersonList or VehicleList -- 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, 11 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3782) allow callbacks to components that implement HttpSessionActivationListener interface

by Dan Allen (JIRA)

allow callbacks to components that implement HttpSessionActivationListener interface ------------------------------------------------------------------------------------ Key: JBSEAM-3782 URL: https://jira.jboss.org/jira/browse/JBSEAM-3782 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.CR1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.1.CR2 Seam adds the HttpSessionActivationListener interface to all non-EJB components to capture session passivation and activation events. Seam then channels these callbacks to the @PrePassivate and @PostActivate methods on the component, respectively. However, Seam is not honoring components which might have already implemented this interface. Allow calls to sessionWillPassivate and sessionDidActivate to proceed on to the component if the bean class implements HttpSessionActivationListener. -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3747) Boolean tests during Initialization consistent with JDK

by Anthony Whitford (JIRA)

Boolean tests during Initialization consistent with JDK ------------------------------------------------------- Key: JBSEAM-3747 URL: https://jira.jboss.org/jira/browse/JBSEAM-3747 Project: Seam Issue Type: Patch Components: Core Affects Versions: 2.1.1.CR1 Reporter: Anthony Whitford Priority: Minor I noticed code like: boolean autoCreate = "true".equals(factory.attributeValue("auto-create")); Java already has some boolean semantics that I would expect to be leveraged for consistency. The line could be replaced with: boolean autoCreate = Boolean.parseBoolean(factory.attributeValue("auto-create")); There is a subtle difference in that parseBoolean will do a case insensitive comparison, but at least this is consistent with core Java. See: http://java.sun.com/javase/6/docs/api/java/lang/Boolean.html#parseBoolean... and: http://java.sun.com/javase/6/docs/api/java/lang/Boolean.html#valueOf(java... The above change also removes "magic values" repeated ("true"). Very minor issue, but also easy to fix. -- 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, 11 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3700) Exclude xhtml files from those that trigger a redeploy

by Pete Muir (JIRA)

Exclude xhtml files from those that trigger a redeploy ------------------------------------------------------ Key: JBSEAM-3700 URL: https://jira.jboss.org/jira/browse/JBSEAM-3700 Project: Seam Issue Type: Bug Components: Core Reporter: Pete Muir Priority: Critical Fix For: 2.1.1.CR1 -- 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, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3696) Support testing of wicket/seam apps

by Clint Popetz (JIRA)

Support testing of wicket/seam apps ----------------------------------- Key: JBSEAM-3696 URL: https://jira.jboss.org/jira/browse/JBSEAM-3696 Project: Seam Issue Type: Feature Request Reporter: Clint Popetz Assignee: Clint Popetz We need to provide an AbstractSeamTest subclass that integrates the context creation/destruction into the lifecycle of WicketTester and formTester. -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3729) Recognize HotDeployFilter as a configurable filter in web.xsd

by Dan Allen (JIRA)

Recognize HotDeployFilter as a configurable filter in web.xsd ------------------------------------------------------------- Key: JBSEAM-3729 URL: https://jira.jboss.org/jira/browse/JBSEAM-3729 Project: Seam Issue Type: Feature Request Components: Hot Deploy Affects Versions: 2.1.0.SP1 Reporter: Dan Allen Fix For: 2.1.1.CR2 It's absolutely critical that the HotDeployFilter only be applied to JSF requests or else the scanning that it does occurs for every related requested by the page. However, currently none of the XML schemas for the component descriptor recognize this filter as a configurable element. Here is how it has to be configured now: <component name="org.jboss.seam.debug.hotDeployFilter"> <property name="urlPattern">*.seam</property> </component> I would like to do one of two things. #1 Change the component name from org.jboss.seam.debug.hotDeployFilter to org.jboss.seam.web.hotDeployFilter (but still keep it in jboss-seam-debug.jar), then add the hot-deploy-filter element to web.xsd. We would get this: <web:hot-deploy-filter url-pattern="*.seam"/> We could even consider moving this filter into jboss-seam.jar because honestly it is so lightweight and really has everything to do with the core and is already controlled by the debug mode flag in Seam. #2 Keep the component name as is and introduce a new namespace http://jboss.org/products/seam/debug and a corresponding package-info.java and debug.xsd. Then add the hot-deploy-filter to debug.xsd. We would get this: <debug:hot-deploy-filter url-pattern="*.seam"/> I really hate solution #2. The only redeeming quality is that it doesn't break applications that might rely on this component name. But then again, it would only affect debug mode, not production apps. -- 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, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3742) pages.xsd cannot use static navigation

by Gonzalez Adrian (JIRA)

pages.xsd cannot use static navigation -------------------------------------- Key: JBSEAM-3742 URL: https://jira.jboss.org/jira/browse/JBSEAM-3742 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.SP1 Reporter: Gonzalez Adrian pages-2.1.xsd is too restrictive, I cannot write anymore : <navigation from-action="goBack"> >From pages.xsd definition, 'from-action' value must always be an El expression (so called 'dynamic navigation'). This shouldn't be the case, web should be able to use static navigation. Here's the pages-2.1.xsd showing the restriction : <xs:simpleType name="view-id"> <xs:restriction base="xs:string"> <xs:pattern value="(/.*)|\*"/> </xs:restriction> </xs:simpleType> <xs:attributeGroup name="attlist.navigation"> <xs:attribute name="from-action" type="pages:method-expression" /> <xs:attribute name="evaluate" type="pages:method-expression" /> </xs:attributeGroup> -- 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, 11 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3728) not clearing EntityManager in ManagedPersistenceContext#sessionWillPassivate breaks session replication

by Dan Allen (JIRA)

not clearing EntityManager in ManagedPersistenceContext#sessionWillPassivate breaks session replication ------------------------------------------------------------------------------------------------------- Key: JBSEAM-3728 URL: https://jira.jboss.org/jira/browse/JBSEAM-3728 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.SP1 Reporter: Dan Allen Fix For: 2.1.1.CR2 Commit 8372 broke the clustering because EntityManager is not being cleared before session passivation. The EntityManager cannot be serialized and therefore to leave it in the conversation context (and hence the session context) prevents the HTTP session from being restored properly. Two ways to fix is either set the EntityManager it to null in the ManagedPersistenceContext#sessionWillPassivate method (the old behavior, which gives us a chance to clean things up) or mark the field as transient. Making the field transient solves the problem that commit 8372 was attempting to fix, which was that the entities were being reloaded from the database on each request in a clustered environment. The problem with using transient is that we don't get an opportunity to formally close the EntityManager (but then again, it might be hard to tell when the session being used jumps a node in the cluster, which is the only time you want to destroy the EntityManager). -- 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, 11 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2009