[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4864:
------------------------------------
Questions:
1) Can BPEL archives be nested inside any others?
2) If yes, does this version situation need to be done for both standalone-publishing and
nested publishing?
If the answer to 2 is yes, then that might be a bit difficult. This is because the spec on
nested names has never been specc'd out at all, for JBT or for WTP. Sometimes the
getName() on a virtual component returns with a suffix, sometimes it doesn't. Some
blocks of code add suffixes, some check for suffixes, some don't. Sometimes the
behaviour is different randomly. It's a very very bad part of the WTP code and I'm
not sure how we can get around that.
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