[JBoss JIRA] Created: (JBAS-3473) Fix DistributedStateImpl.nodeRemove
by Brian Stansberry (JIRA)
Fix DistributedStateImpl.nodeRemove
-----------------------------------
Key: JBAS-3473
URL: http://jira.jboss.com/jira/browse/JBAS-3473
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta
AFAICT, this is not correct. Key/value pairs are stored in the category node's data map; nodeRemoved treats things as if each key is its own node.
Actually, I think the node per key approach is correct, until TreeCacheListener can provide info on what data was changed.
Also, remove() itself notifies listeners of a removal, and then the listener does as well. Needs to be one or the other; probably nodeRemoved() as that gets called for both local and remote removes.
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBPM-698) gpd is not working with latest version of commons-fileupload jar.
by Olivier Debels (JIRA)
gpd is not working with latest version of commons-fileupload jar.
-----------------------------------------------------------------
Key: JBPM-698
URL: http://jira.jboss.com/jira/browse/JBPM-698
Project: JBoss jBPM
Issue Type: Bug
Components: Graphical Process Designer
Reporter: Olivier Debels
Assigned To: Tom Baeyens
When trying to used the graphical process designer with the latest version of commons-upload (version 1.1.1) it is not longer possible to deploy process definitions. You get the exception 'The process definition was rejected because no multiplart boundary was found'.
The reason is that the gpd is using a ',' to separate its content type (in the url used to trigger the upload servlet) where it must be a ';' according to RFC1341. So instead of 'multipart/form-data,boundary=AaB03x' it must be 'multipart/form-data;boundary=AaB03x'.
The webapp must work with the latest version of commons-fileupload.
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBPM-699) build.xml needs to be modified for jbpm to build successfully
by Prabhat Jha (JIRA)
build.xml needs to be modified for jbpm to build successfully
-------------------------------------------------------------
Key: JBPM-699
URL: http://jira.jboss.com/jira/browse/JBPM-699
Project: JBoss jBPM
Issue Type: Task
Reporter: Prabhat Jha
Assigned To: Koen Aers
Priority: Minor
To build jBPM successfully, I had to make the following changes.
A. Add the constructs to create missing directories under target "download-eclipse" in jbpm.dist\build.xml
<mkdir dir="${local-repository}/${eclipse-folder}"/>
<mkdir dir="${local-repository}/${webtools-folder}"/>
<mkdir dir="${local-repository}/${emf-folder}"/>
<mkdir dir="${local-repository}/${gef-folder}"/>
<mkdir dir="${local-repository}/${jem-folder}"/>
B. Modify the <import file > under jbpm.dist\build\projects\docs\gpd.userguide as
<import file="../../docbook-support/support.xml" />
Can you check in these changes in CVS? I am not sure if you are the right person.
Thanks,
Prabhat
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBPM-727) add support for adding Action to Nodes without adding Event
by mehmet bozok (JIRA)
add support for adding Action to Nodes without adding Event
-----------------------------------------------------------
Key: JBPM-727
URL: http://jira.jboss.com/jira/browse/JBPM-727
Project: JBoss jBPM
Issue Type: Feature Request
Components: Graphical Process Designer
Reporter: mehmet bozok
Assigned To: Tom Baeyens
We are extending some parts of GDP in our project, and we need to add Action to Node without adding an Event then show this Aciton on outline tree view. Althought there is a mechanism to add a single Action to Nodes(not in GDP menu but implemented in
org.jbpm.ui.model.Node), it is not shown at outline tree view. In order to make Action appear on tree view as a Node child we needed to
add a menu option, and handle ActionTreeEditPart and NodeTreeEditpart relation in a different way. (not by changing GPD code, but instantiating editparts then reflecting org.eclipse.gef.AbstractEditPart and calling its protected methods which is not a very safe way.)
Therefore it seems neccesary to change iplementation so that single Action (also providing which Action to add) can be added to Node and shown in outline tree view.
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBPM-755) streamline designer build
by Tom Baeyens (JIRA)
streamline designer build
-------------------------
Key: JBPM-755
URL: http://jira.jboss.com/jira/browse/JBPM-755
Project: JBoss jBPM
Issue Type: Task
Components: Graphical Process Designer
Reporter: Tom Baeyens
Assigned To: Koen Aers
Priority: Critical
1) Remove usage of jbpm.version.
* The docs should not be included directly in the designer plugin. Instead, in the help docs, a reference should be published to the docs of the configured runtimes.
* The jbpm version constant should be removed cause it's not used any more.
When fixing this, make sure to do a search for jbpm.version.
2) Rename jbpm.gpd.version to module.version so that it is in sync with all other jbpm subprojects. Make sure that the used definition is located in the version.properties file and that the property definition in the build.xml is removed.
3) Remove all CVS checkout stuff. Have the build fail in case one of the submodules is not present. No cvs checkout should be done in case a module is missing. Later we'll define a cvs checkout script in the overall build.
--
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
19 years, 4 months