Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334979 - [bpel] be able to add and remove pipelines thru JMX w/o having to restart the bpel bundle
Summary: [bpel] be able to add and remove pipelines thru JMX w/o having to restart the...
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Smila (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-21 03:27 EST by thomas menzel CLA
Modified: 2022-07-07 11:31 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description thomas menzel CLA 2011-01-21 03:27:54 EST 
ATM one needs to restart at least the BPEL bundle when wanting to add or remove workflows.

(actually i didnt test if that will be enough, but the pipelines are deployed as part of org.eclipse.smila.processing.bpel.ODEWorkflowProcessor.activate(ComponentContext))

hence it would be good to have JMX commands to add and remove workflows.


ADD
be able to specify a file, folder or a pattern to import BPEL definitions and have them deployed.

DEL
be able to remove BPEL definitions.
this case needs to be safegarded against undeploying pipelines that are currently in use by a crawl job.

addtional ideas
in that context it might also make sense to be able to structurally organize workflows in folders that belonging together, so we dont have to disambiguate them just by their file name.

before doing here anything a concept should be in place
Comment 1 Igor Novakovic CLA 2011-10-12 09:18:31 EDT 
This feature (via REST API) has been introduced in release 0.9.
Comment 2 Andreas Weber CLA 2013-04-15 11:49:17 EDT 
Closing this