May 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2712) Document character encoding stuff

by Pete Muir (JIRA)

Document character encoding stuff ----------------------------------- Key: JBSEAM-2712 URL: http://jira.jboss.com/jira/browse/JBSEAM-2712 Project: JBoss Seam Issue Type: Task 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

16 years, 8 months

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2927) Ability to designate an existing RuntimeException as an ApplicationException

by Matt Drees (JIRA)

Ability to designate an existing RuntimeException as an ApplicationException ---------------------------------------------------------------------------- Key: JBSEAM-2927 URL: http://jira.jboss.com/jira/browse/JBSEAM-2927 Project: Seam Issue Type: Feature Request Components: Core, Exception Handling Reporter: Matt Drees Priority: Minor Currently, if you annotate a runtime exception with @ApplicationException and it propagates out of a component, Seam won't roll back the transaction. It'd be nice if we could indicate a third-party RuntimeException should be treated likewise. See forum for more details. Maybe it could be folded into existing exception handling setup in pages.xml: <exception class="javax.faces.ValidatorException"> <application-exception/> </exception> and <exception class="third.party.CheckedException"> <application-exception rollback="true" end="false"/> </exception> -- 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

16 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2970) In POJO mode, seam 2.0.2 performs a commit on the transaction even if the transaction si marked for rollback

by Denis Forveille (JIRA)

In POJO mode, seam 2.0.2 performs a commit on the transaction even if the transaction si marked for rollback ------------------------------------------------------------------------------------------------------------ Key: JBSEAM-2970 URL: http://jira.jboss.com/jira/browse/JBSEAM-2970 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR2 Reporter: Denis Forveille The logic for performing the commit on a transaction should take into account that the transaction is marked for rollback or not. In Work.java, the could should be: T result = work(); if (begin) { if (Transaction.instance().isMarkedRollback()) { log.debug("transaction isMarkedRollback. rolling back transaction"); userTransaction.rollback(); } else { log.debug("committing transaction"); userTransaction.commit(); } } return result; In the current code, the call to userTransaction.commit() is attempted even if Transaction.instance().isMarkedRollback() is true! See also the "TODO" marker in the code of this 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

16 years, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2723) Page fragment caching for plugin render

by Christian Bauer (JIRA)

Page fragment caching for plugin render --------------------------------------- Key: JBSEAM-2723 URL: http://jira.jboss.com/jira/browse/JBSEAM-2723 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Blocker The infrastructure for page fragment caching with EHCache is in place. We need to cache plugin-rendered HTML fragments with this strategy: - generate a unique cache key for each plugin, including the document ID and the macro hashcode (including position and parameters) - use a separate region for each plugin type, so that we can invalidate the cache for the whole region ("remove all cached fragments of a certain plugin no matter on what document it is rendered") - build cache regions on startup based on plugin metadata -- 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

16 years, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2730) Jetty reference guide chapter with and without Jboss Embedded

by Jay Balunas (JIRA)

Jetty reference guide chapter with and without Jboss Embedded ------------------------------------------------------------- Key: JBSEAM-2730 URL: http://jira.jboss.com/jira/browse/JBSEAM-2730 Project: JBoss Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Priority: Minor User requested reference guide chapter for Jetty with and without Jboss Embedded. Quote: "Jetty, with and without Jboss Embedded. Especially how to use mvn jetty:run to test stuff during development." Comment: http://in.relation.to/Bloggers/DeployingSeamToVariousApplicationServers#c... -- 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

16 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2976) Typo in ScopeType: "psUEdo" instead of "psEUdo"

by Kariem Hussein (JIRA)

Typo in ScopeType: "psUEdo" instead of "psEUdo" ----------------------------------------------- Key: JBSEAM-2976 URL: http://jira.jboss.com/jira/browse/JBSEAM-2976 Project: Seam Issue Type: Patch Components: Core Reporter: Kariem Hussein Priority: Trivial Typo in the word "pseudo" in two places in ScopeType.java: javadoc and message of a thrown exception -- 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

16 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2814) Upgrade to RichFaces 3.2.0.GA

by Pete Muir (JIRA)

Upgrade to RichFaces 3.2.0.GA ----------------------------- Key: JBSEAM-2814 URL: http://jira.jboss.com/jira/browse/JBSEAM-2814 Project: JBoss Seam Issue Type: Task Components: Examples, JSF Integration Affects Versions: 2.1.0.A1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.BETA1 -- 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

16 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1531) Document pages.xsd and maybe other .xsds with xsd:documentation

by Michael Youngstrom (JIRA)

Document pages.xsd and maybe other .xsds with xsd:documentation --------------------------------------------------------------- Key: JBSEAM-1531 URL: http://jira.jboss.com/jira/browse/JBSEAM-1531 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Michael Youngstrom The pages.xsd is fairly vast. It could benefit greatly by some <xsd:documentation> elements. XML editors such as Eclipse WTP will pick up these xsd:documentation elements and provide context help. -- 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

16 years, 8 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2975) Using the same entityManager for Seam and jbpm

by stefan meyer (JIRA)

Using the same entityManager for Seam and jbpm ---------------------------------------------- Key: JBSEAM-2975 URL: http://jira.jboss.com/jira/browse/JBSEAM-2975 Project: Seam Issue Type: Feature Request Components: BPM Affects Versions: 2.0.1.GA Reporter: stefan meyer I wrote an entry in the forum and was asked to create a JIRA issue. Following is the forum entry and my code. The code is ugly whenever calls come via MDBs. ManagedPersistenceContext.beforeCompletion does not work nicely with this implementation. Because I cannot get the entityManager anymore. Even if the code was called in destroy the entitymanager would be gone. If ManagedJbpmContext was in conversation scope and depended on ManagedPersistenceContext and the dependency would lead to the destruction of managedJbpmContext first, then things would be better. The problem is actually only that Jbpm-DbLogging does not work. Maybe that should be fixed. Or Maybe the Jbpm people should work on it. " Jbpm and seam using the same entityManager makes sense, because storing entities in variable context and refernecing processInstance or token from entities is possible. I have the following problem though. My SeamPersistenceService Implementation of Jbpm's PersistenceService is closed with the destruction of the ManagedJbpmContext. Since ManagedJbpmContext is in scope EVENT and entityManager in scope CONVERSATION the entityManager is destroyed before. Jbpm tries to save the log entities upon close and thus fails because the seam managed entityManager is gone and even closed. In my scenario it would help to close JbpmContext in the destroy Method of managedJbpmContext. Transactions and Connections are managed by JbpmContext anyways. Unfortunately direct access to the entityManager will not be possiblle in destroy because the entityManager is removed from Contexts before the ManagedJbpmContext. Maybe ManagedJbpmContext should also be in the Conversation scope. Could you include an alternative version of ManagedJbpmContext that works with a SeamPersistenceService? " Here is my Implementation of Jbpm's PersistenceService that uses a seam managed EntityManager (actually the wrapped hibernate session): package xx.jbpm.persistence.seam; import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; import org.hibernate.Session; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.contexts.Contexts; import org.jbpm.persistence.db.DbPersistenceServiceFactory; import org.jbpm.persistence.jta.JtaDbPersistenceService; public class SeamPersistenceService extends JtaDbPersistenceService { private static Log log = LogFactory.getLog(SeamPersistenceService.class); public SeamPersistenceService(final DbPersistenceServiceFactory persistenceServiceFactory) { super(persistenceServiceFactory); } @Override public void close() { // session is not closed here. super.close(); } @Override public Session getSession() { boolean initialized = Contexts.isApplicationContextActive(); if (initialized) { Session hibernateSession = (Session) Component.getInstance("hibernateSession", ScopeType.EVENT); if (hibernateSession == null || !hibernateSession.isOpen()) { // see comment in else clause return new DummySession(); } else { return hibernateSession; } } else { // seam is not active any more but entityManager is closed in transaction synchronization. // unfortunately ManagedJbpmContext wants to flush the entityManager in beforeCompletion, but we can't get // it via seam anymore. This is probably happening right now. Also saving of instances might happen here. These // are all persistent entites - that is why seam ignores it. Except for the log entries - those get lost // when db logging is used. return Dummy Session return new DummySession(); } } } Extract from DummySession: ... public Serializable save(final Object object) throws HibernateException { try { Method getIdMethod = object.getClass().getMethod("getId", new Class[0]); Object value = getIdMethod.invoke(object, new Object[0]); if (value != null && ((Number) value).intValue() == 0) { Logger.getLogger("dummy session").warn("not saving transient entity " + object.getClass().getName()); } } catch (Exception e) { Logger.getLogger("dummy session").warn("cannot check state of entities " + object.getClass().getName(), e); } return null; } ... -- 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

16 years, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2951) Add ability to start jBPM in the wait-state instead of only the start-state

by Samuel Mendenhall (JIRA)

Add ability to start jBPM in the wait-state instead of only the start-state --------------------------------------------------------------------------- Key: JBSEAM-2951 URL: http://jira.jboss.com/jira/browse/JBSEAM-2951 Project: Seam Issue Type: Feature Request Components: BPM Reporter: Samuel Mendenhall Priority: Minor "jBPM itself does work as stated in the *jBPM docs*, i.e. start-state behaves as a wait state. It is Seam who signals the process instance right after it is created, effectively disabling the wait behavior of the start-state. The intent of giving the start-state a wait behavior is to allow the caller to set variables or complete a user task prior to executing any action in the process. Seam should offer a way to create a process instance without signaling it right away. Changing the behavior to leave the signal() out would break existing applications who assume that the process instance immediately moves to the next step. To deal with this, Seam could add a createProcess(ProcessDefinition, boolean) method to the BusinessProcess class. The boolean parameter tells whether the process instance is to be signaled." --Alejandro Guizar -- 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

16 years, 8 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2008