March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1782) Embed Hibernate Search 3.0.0.Beta4 and Lucene 2.2

by Emmanuel Bernard (JIRA)

Embed Hibernate Search 3.0.0.Beta4 and Lucene 2.2 ------------------------------------------------- Key: JBSEAM-1782 URL: http://jira.jboss.com/jira/browse/JBSEAM-1782 Project: JBoss Seam Issue Type: Feature Request Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard Priority: Minor Fix For: 2.0.0.CR1 -- 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

18 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1767) Allow adding own Hibernate Interceptor

by Petr Ferschmann (JIRA)

Allow adding own Hibernate Interceptor -------------------------------------- Key: JBSEAM-1767 URL: http://jira.jboss.com/jira/browse/JBSEAM-1767 Project: JBoss Seam Issue Type: Feature Request Reporter: Petr Ferschmann Currently I am not able to add my own Hibernate Interceptor using Configuration.setInterceptor(). I have to create my own HibernateSessionFactory (and that is not what I want). One way is to add parameter to HibernateSessionFactory for interceptor class. -- 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

18 years

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1857) ManagedEntityIdentityInterceptor nulls fields incorrectly in reentrant calls to conversation scoped components

by Kahli Burke (JIRA)

ManagedEntityIdentityInterceptor nulls fields incorrectly in reentrant calls to conversation scoped components -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1857 URL: http://jira.jboss.com/jira/browse/JBSEAM-1857 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: Seam 2.0.0.BETA1, also jboss-seam-CVS.2007-08-22_00-49-47 Reporter: Kahli Burke Priority: Blocker When a conversation component method is called in a reentrant fashion, entity fields are nulled incorrectly. The scenario is as follows: I. Component A method is called A. entityIdsToRefs(). (reinject entity fields) B. Method invoked C. Component A calls method in object B D. Object B calls method in Component A. i. entityIdsToRefs() ii. Method invoked iii. entityRefsToIds(). (disinject entity fields, set to null, save in conversation) E. entityRefsToIds(). (fields are already null, so clearWrapper is called, and the objects are removed from the conversation) II. Component A method is called, values are null, and cannot be retrieved from the conversation context (they are in the removals map) The solution seems to be the same as what was done with the BijectionInterceptor in JBSEAM-631. I wonder if this also might be related to JBSEAM-1840? I've attached a patch that fixes the problem for me, please review. 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

18 years

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1854) Context sensitive help system

by Christian Bauer (JIRA)

Context sensitive help system ----------------------------- Key: JBSEAM-1854 URL: http://jira.jboss.com/jira/browse/JBSEAM-1854 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Haven't decided yet if the help system is going to be based on separate data or if it's just some wiki documents in a specially named directory structure. -- 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

18 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1750) Accessing handledException through EL broken

by Samuel Mendenhall (JIRA)

Accessing handledException through EL broken -------------------------------------------- Key: JBSEAM-1750 URL: http://jira.jboss.com/jira/browse/JBSEAM-1750 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Reporter: Samuel Mendenhall Assigned To: Norman Richards Priority: Minor Bean: throw new HibernateException("Test"); pages.xml: <exception class="org.hibernate.HibernateException"> <end-conversation/> <redirect view-id="/error.xhtml"> <message severity="WARN">#{org.jboss.seam.handledException.message}</message> </redirect> </exception> I am correctly redirected to the error.seam page however the message is empty and in my console I have: 11:52:47,571 WARN [Interpolator] exception interpolating string: #{org.jboss.seam.handledException.message} javax.faces.el.PropertyNotFoundException: Bean: org.hibernate.HibernateException, property: message .... Furthermore, the documentation says to use #{handledException.message} which is incorrect, it should be #{org.jboss.seam.handledException.message}. -- 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

18 years

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1751) Remoting doesn't appear to work with GlassFish

by Samuel Doyle (JIRA)

Remoting doesn't appear to work with GlassFish ---------------------------------------------- Key: JBSEAM-1751 URL: http://jira.jboss.com/jira/browse/JBSEAM-1751 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.0.BETA1 Environment: GlassFish V2 build 56 using IE Version 7 and Firefox 2.0 for testing Reporter: Samuel Doyle Assigned To: Shane Bryzak Hi there, I was trying to get remoting working with a project I am working on it was constantly failing without any indication of error in the Seam debug window or the server logs. The Seam debug window indicates that the server side request is being invoked and looks fine but when testing the debug window just says response packet followed by nothing. My server method code never gets hit. After playing around with my existing project for a bit I decided just to try the bare bones and the HelloWorld example in your head branch in cvs produced the same results. I have been using DWR up to this point and has proven to be reliable. Since I'm using Seam I would like to be able to use it for all the interactions including the JavaScript AJAX interactions with introducing additional frameworks. I posted a lot more information on the forum. Please see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=114820 for more details. -- 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

18 years

4
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1704) Allow customizable loading of instances in EntityHome and HibernateEntityHome

by Darryl Smith (JIRA)

Allow customizable loading of instances in EntityHome and HibernateEntityHome ----------------------------------------------------------------------------- Key: JBSEAM-1704 URL: http://jira.jboss.com/jira/browse/JBSEAM-1704 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.0.BETA1 Reporter: Darryl Smith To support eager loading of associations -- 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

18 years

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1656) passivated entities in parent conversations cause version problems when they're updated

by Matt Drees (JIRA)

passivated entities in parent conversations cause version problems when they're updated --------------------------------------------------------------------------------------- Key: JBSEAM-1656 URL: http://jira.jboss.com/jira/browse/JBSEAM-1656 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: current cvs Reporter: Matt Drees If an entity in a parent conversation is updated and the persitence context is flushed, it gets a new version. However, the passivatedEntity in its EntityBean wrapper still has the old version. The wrapper is not passivate()ed at the end of the request, because it's not in the current conversation. So, when the nested conversation ends and the wrapper is activate()ed at the beginning of a request, the version mismatch causes a StaleStateException. See the forum post for more details. -- 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

18 years

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1650) NPE thrown when attempting to configure pojo as Seam component

by Michael Youngstrom (JIRA)

NPE thrown when attempting to configure pojo as Seam component -------------------------------------------------------------- Key: JBSEAM-1650 URL: http://jira.jboss.com/jira/browse/JBSEAM-1650 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR1 Reporter: Michael Youngstrom Fix For: 2.0.0.CR1 NPE thrown when attempting to configure pojo as Seam component. <component name="expanderState" class="java.util.HashMap" auto-create="true" scope="conversation"/> throws: java.lang.RuntimeException: Could not create Component: expanderState at org.jboss.seam.init.Initialization.addComponent(Initialization.java:910) at org.jboss.seam.init.Initialization.installComponents(Initialization.java:841) at org.jboss.seam.init.Initialization.init(Initialization.java:508) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: java.lang.NullPointerException at org.jboss.seam.init.DeploymentDescriptor.<init>(DeploymentDescriptor.java:33) at org.jboss.seam.Seam.getEjbDescriptor(Seam.java:51) at org.jboss.seam.Seam.getComponentType(Seam.java:102) at org.jboss.seam.Component.<init>(Component.java:216) at org.jboss.seam.Component.<init>(Component.java:207) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:896) -- 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

18 years

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1646) don't read external DTDs if we don't have to

by Norman Richards (JIRA)

don't read external DTDs if we don't have to -------------------------------------------- Key: JBSEAM-1646 URL: http://jira.jboss.com/jira/browse/JBSEAM-1646 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards When parsing XML files that we don't control, like ejb-jar.xml it's possible for the parser to make network connections to resolve DTDs. Rather than trying to maintain a local cache, I am adding a safe parsing mode which will completely ignore external references. If the external DTD is critical to parsing (default attributes, for example), the DTD still can be cached and the document parsed normally. -- 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

18 years

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2008