[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-4864:
-------------------------------------
So the version needs to be a new field in the deployment descriptor model and stored in
the XML file... Do we store it as an attribute on the "process" element? Do we
add it as a new element? How much leeway do we have in how this is stored?
<deploy
xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
xmlns:bpl="http://www.jboss.org/bpel/examples"
xmlns:intf="http://www.jboss.org/bpel/examples/wsdl">
<process name="bpl:HelloWorld" version="1"??>
<version>1</version>??
<active>true</active>
<provide partnerLink="helloPartnerLink">
<service name="intf:HelloService" port="HelloPort"/>
</provide>
</process>
</deploy>
Then once we have the deployment descriptor editor and descriptor xml file working... Rob,
where is the code to jar up the bundle to put it up on the runtime server?
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
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
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