[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Gary Brown commented on JBIDE-4864:
-----------------------------------
It is my understanding from Denny, that in order to make the 'version' field
visible within the ODE deployment descriptor editor, it will be necessary to update the
EMF model.
Once this is done, then the only other functionality is for the WTP deployer to use that
version as a suffix on the BPEL jar name.
It is also my understanding that EMF is extendable, so should be able to support this.
In answer to Rob's question - I think if BPEL is nested in another project (e.g. ESB),
then it will be up to the ESB project to determine how it wants to bundle the BPEL. If it
wants to include multiple jar'ed versions of the same BPEL process then that is fine
as long as each jar is uniquely named (e.g. with a version number). However it is more
likely that when nested in an ESB project, the BPEL will be unpacked so deployed in an
unversioned way - which is consistent with the fact that ESB bundles (or any JEE archive)
are not versioned.
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