August 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1542) Identify process not only by root token, to allow for concurrency

by Gavin King (JIRA)

Identify process not only by root token, to allow for concurrency ----------------------------------------------------------------- Key: JBSEAM-1542 URL: http://jira.jboss.com/jira/browse/JBSEAM-1542 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.GA Currently we identify the process by the process id, and ignore the fact that jBPM allows fork-and-join using multiple Tokens. This is inflexible, especially for service orchestration. -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1585) Update portal example to JBoss AS 4.2.0.GA

by Pete Muir (JIRA)

Update portal example to JBoss AS 4.2.0.GA ------------------------------------------ Key: JBSEAM-1585 URL: http://jira.jboss.com/jira/browse/JBSEAM-1585 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir -- 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-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-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-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-1783) Add Hibernate Search support for JPA

by Emmanuel Bernard (JIRA)

Add Hibernate Search support for JPA ------------------------------------ Key: JBSEAM-1783 URL: http://jira.jboss.com/jira/browse/JBSEAM-1783 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-1851) Implement tags/topics for documents and topic plugin for blog view

by Christian Bauer (JIRA)

Implement tags/topics for documents and topic plugin for blog view ------------------------------------------------------------------ Key: JBSEAM-1851 URL: http://jira.jboss.com/jira/browse/JBSEAM-1851 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer -- 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-1853) Wiki diff is broken

by Christian Bauer (JIRA)

Wiki diff is broken ------------------- Key: JBSEAM-1853 URL: http://jira.jboss.com/jira/browse/JBSEAM-1853 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Some change broke the diff, the diff result looks wrong and there is one historical revision "too many" in the list. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2007