[
https://jira.jboss.org/jira/browse/JBPM-1450?page=com.atlassian.jira.plug...
]
Thomas Diesler commented on JBPM-1450:
--------------------------------------
Thomas,
Resolving this issue simply requires a change in the jBPM configuration.
I understand SOA-P uses its own jBPM and Hibernate configuration files.
We should change those files directly.
Julian, can you confirm whether SOA-P uses a separate jBPM configuration
Thomas,
Resolving this issue simply requires a change in the jBPM configuration.
I understand SOA-P uses its own jBPM and Hibernate configuration files.
We should change those files directly.
Julian, can you confirm whether SOA-P uses a separate jBPM configuration
file? If so, please let me know how can I change it. Alternatively I can
post the required changes in a comment to the Jira issue.
-Alejandro
El lun, 24-11-2008 a las 09:08 +0100, Thomas Diesler escribió:
> Hi Alejandro,
>
> this issue
https://jira.jboss.org/jira/browse/JBPM-1450 is still open,
> but CP03 has been tagged already. What do we need to do about it?
>
> cheers
> -thomas
>
Disable jBPM logging
--------------------
Key: JBPM-1450
URL:
https://jira.jboss.org/jira/browse/JBPM-1450
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Mark Little
Assignee: Alejandro Guizar
Fix For: SOA 4.2 CP03, SOA 4.3
--
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