[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4864:
--------------------------------------------
It might be necessary to create a different editor (i.e. Riftsaw deployment editor or
something) that uses a subclass or delegation of the deployment model to realize it - also
to avoid any non-ODE compatible changes.
About packaging in ESB then if the ESB project links to a BPEL project then it should be
bundled just as it would if done standalone - with the version number. Either the version
number matters or it doesn't. Isn't consistency better here ?
BPEL Process Versioning
-----------------------
Key: JBIDE-4864
URL:
https://jira.jboss.org/jira/browse/JBIDE-4864
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: bpm
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Rob Stryker
The process versioning requirement is to support an optional 'version' attribute
on the top level 'deploy' element in the bpel-deploy.xml deployment descriptor,
and
provide:
1) Extension to ODE deployment descriptor editor to allow user to define the version.
2) When BPEL project is deployed to AS server, if a version has been specified, then it
should be used as the suffix of the jar name.
The version attribute should be defined in its own namespace - open to suggestions?
--
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