December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3708) Only enable ManagedEntityInterceptor when needed

by Pete Muir (JIRA)

Only enable ManagedEntityInterceptor when needed ------------------------------------------------ Key: JBSEAM-3708 URL: https://jira.jboss.org/jira/browse/JBSEAM-3708 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Priority: Critical Fix For: 2.1.1.CR2 The MEI is only needed for: * JavaBeans in a cluster that are conversation scoped or * EJBs that are conversation scoped Add some configuration to <core:init /> to allow the user to enable clustering mode (or autodetect) and upgrade the isInterceptorEnabled method to take account of this. -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3714) Update release-process.txt to include the functional test execution

by Jay Balunas (JIRA)

Update release-process.txt to include the functional test execution ------------------------------------------------------------------- Key: JBSEAM-3714 URL: https://jira.jboss.org/jira/browse/JBSEAM-3714 Project: Seam Issue Type: Task Components: Build, Test Harness Affects Versions: 2.1.1.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.1.1.CR2 The release-process.txt needs to be updated to include steps and instructions for the functional tests using selenium. -- 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, 8 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3717) Use Indentity Management in seam-gen

by Pete Muir (JIRA)

Use Indentity Management in seam-gen ------------------------------------ Key: JBSEAM-3717 URL: https://jira.jboss.org/jira/browse/JBSEAM-3717 Project: Seam Issue Type: Feature Request Components: Security Reporter: Pete Muir Assignee: Shane Bryzak Priority: Critical Fix For: 2.1.1.CR2 -- 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, 8 months

4
13
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, 8 months

2
3
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, 8 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, 8 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3570) Update the WebSphere reference guide chapter to WebSphere 7.0

by Jay Balunas (JIRA)

Update the WebSphere reference guide chapter to WebSphere 7.0 ------------------------------------------------------------- Key: JBSEAM-3570 URL: https://jira.jboss.org/jira/browse/JBSEAM-3570 Project: Seam Issue Type: Task Components: Platform interoperability Affects Versions: 2.1.0.CR1 Reporter: Jay Balunas Assignee: Marek Novotny Fix For: 2.1.1.CR1 WebSphere 7.0 has gone GA and now fully supports jee5 with out the various issues before. This needs to be investigated, tested, and the reference guide needs to be updated. Search forum, and jira for related issues and notes. -- 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, 8 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3612) examples should demonstrate obtaining entity manager factory from JNDI via persistence unit reference

by Dan Allen (JIRA)

examples should demonstrate obtaining entity manager factory from JNDI via persistence unit reference ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3612 URL: https://jira.jboss.org/jira/browse/JBSEAM-3612 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.1.1.CR1 For any example that is deploying to a standard Java EE 5 environment (for instance the jpa example deploying to GlassFish or JBoss AS 5), the entity manager factory should be obtained through JNDI through a persistence unit reference. 5.3.1 of JPA spec: "Within a Java EE environment, an entity manager factory may be injected using the Persistence-Unit annotation or obtained through JNDI lookup." It would first need to be declared in web.xml: <persistence-unit-ref> <persistence-unit-ref-name>bookingDatabase/emf</persistence-unit-ref-name> <persistence-unit-name>bookingDatabase</persistence-unit-name> </persistence-unit-ref> Then the components.xml would look like this: <persistence:managed-persistence-context name="entityManager" auto-create="true" persistence-unit-jndi-name="java:comp/env/bookingDatabase/emf" /> The reason we should do this is to advocate the Java EE standard approach. -- 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, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3571) provide control to destroy a conversation on debug page

by Dan Allen (JIRA)

provide control to destroy a conversation on debug page ------------------------------------------------------- Key: JBSEAM-3571 URL: https://jira.jboss.org/jira/browse/JBSEAM-3571 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.CR1 Reporter: Dan Allen Assignee: Dan Allen Priority: Minor Fix For: 2.1.0.GA It would be convenient to be able to destroy a conversation from the debug page, in addition to inspect it. Also, it would be helpful if a column was added to show if a conversation is nested. I also noticed that on Firefox, when you click on an expanded context node the first time, it does nothing. There is a bug in how the "current style" is read in. -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3674) Custom parameter value in <redirect> is not being propagated (regression)

by Dan Allen (JIRA)

Custom parameter value in <redirect> is not being propagated (regression) ------------------------------------------------------------------------- Key: JBSEAM-3674 URL: https://jira.jboss.org/jira/browse/JBSEAM-3674 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.0.SP1 Reporter: Dan Allen Fix For: 2.1.1.CR1 I want to propagate a param so that it survives a redirect. This is what I have done until now. <navigation from-action="myaction"> <redirect view-id="/pages/page.hxtml" > <param name="category" value="#{param.name}"/> </redirect> </navigation> However, since 2.1, this doesn't work anymore. The param is still propagated but not the value. -- 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, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008