[JBoss JIRA] Created: (JBPM-1978) configure pvm2 user for hudson job jbpm4-load
by Tom Baeyens (JIRA)
configure pvm2 user for hudson job jbpm4-load
---------------------------------------------
Key: JBPM-1978
URL: https://jira.jboss.org/jira/browse/JBPM-1978
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Priority: Minor
Fix For: jBPM 4.0.0 Alpha2
currently, both the jbpm4-db and the jbpm4-load hudson jobs run on the same user.
if those would be run concurrently, the one would wipe out the other's database.
so they both need to run with their own user. jbpm-db should keep using user PVM1
jbpm-load should be configured to use PVM2. this is done by providing a second profiles-load.xml in the resources repo and copying that to profiles.xml in the jbpm4 working copy.
--
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
15 years, 11 months
[JBoss JIRA] Created: (JBPM-1163) Bad property format of hibernate.cfg.xml snippet in the user guide "Persistence" chapter
by Julien Kronegg (JIRA)
Bad property format of hibernate.cfg.xml snippet in the user guide "Persistence" chapter
----------------------------------------------------------------------------------------
Key: JBPM-1163
URL: http://jira.jboss.com/jira/browse/JBPM-1163
Project: JBoss jBPM
Issue Type: Bug
Components: Documentation
Affects Versions: jBPM jPDL 3.2.2
Environment: CVS code JBPM 3.2.2 downloaded on 2008.04.18.
Reporter: Julien Kronegg
Assigned To: Tom Baeyens
Priority: Optional
Fix For: jBPM 3.3
In "/jbpm.3/jpdl/userguide/en/modules/persistence.xml" (CVS version 1.11), the "Managed transactions" section describe the most important configuration property from the "hibernate.cfg.xml" file as follow:
"hibernate.connection.datasource= --datasource JNDI name-- like e.g. java:/DefaultDS"
This property should be described using a XML format because the "hibernate.cfg.xml" in in XML format, for example:
<property name="hibernate.connection.datasource"> --datasource JNDI name-- like e.g. java:/DefaultDS </property>
Note: not tested on the german documentation.
--
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
15 years, 11 months
[JBoss JIRA] Created: (JBPM-1161) Bad references to property "jbpm.hibernate.cfg.xml" from the "jbpm.properties" file removed in JBPM 3.1
by Julien Kronegg (JIRA)
Bad references to property "jbpm.hibernate.cfg.xml" from the "jbpm.properties" file removed in JBPM 3.1
-------------------------------------------------------------------------------------------------------
Key: JBPM-1161
URL: http://jira.jboss.com/jira/browse/JBPM-1161
Project: JBoss jBPM
Issue Type: Bug
Components: Documentation
Affects Versions: jBPM jPDL 3.2.2
Environment: CVS code of JBPM 3.2.2 obtained on 2008.04.18
Reporter: Julien Kronegg
Assigned To: Tom Baeyens
Priority: Minor
The JBPM 3.2.2 user guide refers to the file "jbpm.properties", which was replaced by "jbpm.cfg.xml" in version JBPM 3.1 (see http://sourceforge.net/project/shownotes.php?release_id=383725&group_id=7... ).
While references to "jbpm.properties" may be valid in a change log or a migration guide, they are not valid in the following files.
/jbpm.3/jpdl/userguide/en/modules/persistence.xml (CVS version 1.11):
In the sentence "Note that the hibernate configuration file resource is mapped in the property 'jbpm.hibernate.cfg.xml' and can be customized in the jbpm.cfg.xml", the "jbpm.hibernate.cfg.xml" property name should be replaced by "resource.hibernate.cfg.xml" (i.e. the property of the file snippet shown just below that sentence).
/jbpm.3/jpdl/userguide/en/modules/configuration.xml (CVS version 1.7):
The sentence
"Location: <literal>hibernate.cfg.xml</literal> unless specified otherwise in the jbpm.hibernate.cfg.xml property in the jbpm.properties file."
should be replaced by:
"Location: <literal>hibernate.cfg.xml</literal> unless specified otherwise in the resource.hibernate.cfg.xml property in the jbpm.cfg.xml file."
--
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
15 years, 11 months
[JBoss JIRA] Created: (JBPM-1897) Unable to Login in JBPM console
by Santayan Biswas (JIRA)
Unable to Login in JBPM console
-------------------------------
Key: JBPM-1897
URL: https://jira.jboss.org/jira/browse/JBPM-1897
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.3.0 GA
Reporter: Santayan Biswas
I am very new in JBPM. By default JBPM uses Hypersonic database. But in my application I need to connect to SQL Server, so I changes the related files accordingly. But I can not find the table name and script from where it picks the login user information. So I am unable to login in JBPM console. Can anyone please help me regarding this. I am using JBOSS 4.2.3 and JBPM 3.3.0...Please help
--
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
15 years, 11 months
[JBoss JIRA] Created: (JBPM-1244) hardcoded keys for standard definitions map in class ProcessDefinition
by Hauke Rabe (JIRA)
hardcoded keys for standard definitions map in class ProcessDefinition
----------------------------------------------------------------------
Key: JBPM-1244
URL: http://jira.jboss.com/jira/browse/JBPM-1244
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Reporter: Hauke Rabe
in case you replace the "resource.default.modules" to define different definition classes, such as
#org.jbpm.taskmgmt.def.TaskMgmtDefinition
.........jbpm.taskmgmt.def.ExtendedTaskMgmtDefinition (extends TaskMgmtDefinition)
ProcessDefinition#addDefinition(final ModuleDefinition moduleDefinition) uses the classname as definition map key, but for example the accessor ProcessDefinition#getTaskMgmtDefinition() uses hardcoded TaskMgmtDefinition.class as key.
conclusion: the defined ExtendedTaskMgmtDefinition instance must use the TaskMgmtDefinition.class as key.
--
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
15 years, 11 months