[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-4864:
---------------------------------
"So <deploy .... rs:version="myver1" xmlns:rs="someurl" >,
contained in Eclipse project HelloWorldBPEL will result in a jar being deployed to the
server as HelloWorldBPEL-myver1.jar. "
If we would add a new attribute to the <deploy .../> tag, it seems that we have to
modify the schema of bpel-deploy.xml and generate the deploy
descriptor EMF model, we might have to maintain the emf model by ourselves instead of
Eclipse BPEL team.
btw, I believe we will have more and more difference from the original Eclipse BPEL in
future, but the eclipse bpel goes slowly very much for now,
if we continue trying to keep synchronization with them, it will become more and more
hard in the future. So I would suggest that we should just focus
on our current bpel plugins code and and and change any function as we need, to avoid the
conflict with Eclpse bpel plugins once the user install both,
we can change the plugin names and IDs to our own completely.
any ideas?
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