[JBoss JIRA] Moved: (JBPM-1211) complete software logging
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1211?page=all ]
Thomas Diesler moved PVM-51 to JBPM-1211:
-----------------------------------------
Project: JBoss jBPM (was: The Process Virtual Machine)
Key: JBPM-1211 (was: PVM-51)
Component/s: PVM
(was: pvm)
> complete software logging
> -------------------------
>
> Key: JBPM-1211
> URL: http://jira.jboss.com/jira/browse/JBPM-1211
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: PVM
> Reporter: Tom Baeyens
>
> complete the docs and implementation for software logging.
> 1) review the defaults.
> 2) verify the correct operation of the exception logger. this is a log handler that will keep the last x-hundred logs in a circular buffer. when an exception occurs, it will flush it's buffer (+the exception report) in a file. this can definitely boost performance and improve the problem reports that we'll get in afterwards as users can specify a debug log level for this without a significant performance penalty (except for the string concatenations)
> See also java.util.logging.MemoryHandler, but I believe I have found that insufficient on a previous look.
--
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, 6 months
[JBoss JIRA] Moved: (JBPM-1210) spring configuration support
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1210?page=all ]
Thomas Diesler moved PVM-44 to JBPM-1210:
-----------------------------------------
Project: JBoss jBPM (was: The Process Virtual Machine)
Key: JBPM-1210 (was: PVM-44)
Component/s: PVM
(was: pvm)
> spring configuration support
> ----------------------------
>
> Key: JBPM-1210
> URL: http://jira.jboss.com/jira/browse/JBPM-1210
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: PVM
> Reporter: Tom Baeyens
> Assigned To: Mauricio Salatino
>
> The first goal is to create an EnvironmentFactory implementation that is based on spring configuration.
> The class to complete is org.jbpm.pvm.internal.env.SpringEnvironmentFactory
> The SpringEnvironmentFactory should relate to a spring ApplicationContext, I believe. The first thing to do is create a test that shows how a spring configuration can be used to create hibernate sessions.
> Something like this:
> static EnvironmentFactory environmentFactory = SpringEnvironmentFactory.parseResource("org/jbpm/pvm/spring/springbeans.xml");
> Environment environment = environmentFactory.openEnvironment();
> try {
> Session hibernateSession = environment.get(Session.class);
> assertNotNull(hibernateSession);
> } finally {
> environment.close();
> }
--
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, 6 months
[JBoss JIRA] Moved: (JBPM-1217) check collections if they need a presence boolean
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1217?page=all ]
Thomas Diesler moved PVM-8 to JBPM-1217:
----------------------------------------
Project: JBoss jBPM (was: The Process Virtual Machine)
Key: JBPM-1217 (was: PVM-8)
Component/s: PVM
(was: pvm)
> check collections if they need a presence boolean
> -------------------------------------------------
>
> Key: JBPM-1217
> URL: http://jira.jboss.com/jira/browse/JBPM-1217
> Project: JBoss jBPM
> Issue Type: Task
> Components: PVM
> Reporter: Tom Baeyens
>
> If in the code you need to know if there are elements in a collection, this will result into an extra query for the entities. If in most cases, the collection is empty, it might be an optimization to add a boolean pressence indicator next to the collection. The class could maintain that boolean to indicate if elements are available in the collection. That way, the extra query is saved if in the code you only need to do a collection-presence check.
> For sure this is useful for the ProcessChanges. But probably for a lot of the other collections as well.
> This shouldn't be applied blindfolded. Each case should be evaluated in terms of the number of times the presence check is executed in the code.
--
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, 6 months