Red Hat Bugzilla – Bug 996881
deploy.xml is not created automaticaly when using BPEL implementation for Component
Last modified: 2015-08-02 19:47:46 EDT
If I add BPEL Component to switchyard project, Process.bpel file is created, but deploy.xml file is important for deployment too, and this file isn't created.
User has to create it separately by creating plain xml file. Moreover, deploy.xml, Process.bpel, switchyard.xml should be linked somehow, to let user set these files in confortable way. Now you have to know exactly which namespaces and names to fill there and if you change it in switchyard.xml, propagation to other files has to be done manualy.
There is an outstanding enhancement request in JIRA to remove the requirement for deploy.xml altogether.
In addition to that, the issue with synchronizing switchyard.xml content with other artifacts in the project, in my opinion, falls under the broader scope of refactoring and is not solely limited to bpel. It applies to all the implementation types.
That said, I don't think refactoring support will be available in the 6.0 timeframe. Improved validation (for sure), and possibly "quick fix" support (hopefully) are probably as far as we'll get for 6.0. In any case, I think we need to split this issue into multiple issues:
This is an enhancement request and will not make it in the 6.0 timeframe.
I don't think this is going to make it into FSW 6.1
Nacking this bugzilla - this is an EAP issue and FSW 6.2 will not embed EAP.
This is low priority but is there anything we can do (doc, sample file) to make this easier?
Nacked in error! This is not an EAP issue.
A documented sample file would be a good solution.