6:10 p.m.
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: Denny Xu
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
6:12 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-4864:
------------------------------------------
This came from a set of e-mail conversations with Kurt Stam, Gary Brown, and John Graham.
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: Denny Xu
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
6:12 p.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick reassigned JBIDE-4864:
----------------------------------------
Assignee: Rob Stryker (was: Denny Xu)
Max suggested assigning this to you Rob so we can get it on the schedule.
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
6:28 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4864:
--------------------------------------------
Point 1 is about the BPEL editor which is not our area. Something that should be done
separately.
Brian, For Point 2, what exactly is going to be in the descriptor to indicate it ? Please
state file name and location and example of content (even if just a suggestion)
And what kind of versioning is intended here ? just something like "myproject"
becomes myproject-<versionstring>.jar ?
Rob, for Point 2 - would you say this naming of the deployment unit will be the work of
the server or of the module factory ?
Is it compatible with how WTP models its projects ? i.e. I assume the dependency will be
"myproject" but the actual generated filename will be myproject-1.2.3.jar ?
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
6:51 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-4864:
------------------------------------------
This is from one of Gary's e-mails:
Having the separate versions of a BPEL deployment stored in
different jars (with the version number suffix), can be supported
immediately with a simple change to the M1 codebase - I've ran some
tests and it works fine. This is because this is basically how the ODE
versioning mechanism is intended to work.
So this option leverages the current ODE ProcessStore, does not require
any further development in the runtime, and means that the more
comprehensive versioning solution based around a repository can be
scheduled for the BPM platform.
The implication of taking this option is slightly more work in the
Eclipse WTP deployer for the BPEL project - it will need to take a
version number from the ODE deployment descriptor, and use this in the
name of the jar being deployed into the AS.
Although in general I don't think this is the best solution, I prefer
this route as the repository approach needs to really be developed in
conjunction with the SOA Repository - which will hopefully be available
for the BPM platform. This short term solution has the merit that it is
available immediately, and can continue to be supported in the BPM
platform as a versioning technique in a single server environment - but
the repository approach used in a multi-server (clustered) environment.
The other benefit is that we should have the current ERD functionality
available a lot earlier than we initially thought - and so more time can
be dedicated to examples, documentation, testing and possibly
contributing back bug fixes into the ODE project.
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
8:02 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Gary Brown commented on JBIDE-4864:
-----------------------------------
Just to provide some more details, the BPEL project will contain an ODE deployment
descriptor file called bpel-deploy.xml, which has content such as:
<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">
<active>true</active>
<provide partnerLink="helloPartnerLink">
<service name="intf:HelloService" port="HelloPort"/>
</provide>
</process>
</deploy>
What is required is the association of a 'version' string with the overall
deployment, so probably on the <deploy> element. This version information will
purely be used by the Eclipse WTP deployment mechanism - the RiftSaw runtime will not use
this information - it is only to be used to name the jar placed in the AS deploy folder.
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.
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
11:58 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4864:
--------------------------------------------
so there wont be *any* connection between this version element and the version
shown/stored inside the apache ode runtime ?
Just checking to be sure I understand it ;)
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
7:40 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-4864:
---------------------------------
yes. because the BPEL project is WTP utility project, all bpel project are Utility
projects but it doesn't mean all utility project are BPEL project,
so when server publish a bpel project, it should know which utility project is for bpel
and which one is not.
Rob, you might distinguish it by checking if the project contains bpel facet, just a
suggestion.
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
9:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4864:
--------------------------------------------
bpel projects are just utility project for now - going forward that will most likely
change (see email thread on mailing list)
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
9:25 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
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
1:38 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
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
9:04 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4864:
--------------------------------------------
Does the editor ever need to know the rs:version part ? If not, why does the EMF need to
know ?
If EMF need to know, then I thought EMF were supposed to be extendable without causing big
changes ?
Especially for such a thing as a namespaced xml element it should be possible one would
think ?
If this is the only change we do - then we should be fine.
But others are just bugfixes, right ? No new features beyond this field or has time shown
otherwise?
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
9:09 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-4864:
------------------------------------------
Hey Gary...
Can you answer Max's question about versioning?
--Fitz
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
10:38 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
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
8:52 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
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
10:32 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-4864:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Hey Rob... Any progress on this one? I thought you had a possible solution worked out last
we chatted about it, but we got sidetracked with some of the testing and deployment
descriptor issues.
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
8:48 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-4864:
---------------------------------
I will look into this task, we might have to create a new plugin and new model to support
bpel versioning without break original Eclipse BPEL editor
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
11:11 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4864) BPEL Process Versioning
[
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
11:13 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-4864:
-------------------------------------
Attachment: HelloWorldQuickstart.zip
Rob, this is an Eclipse project without any version modifications. It's based on the
Hello World Quickstart from Riftsaw - includes the .bpel, the *.wsdl, and the
bpel-deploy.xml file.
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
Attachments: HelloWorldQuickstart.zip
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
3:20 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-4864:
-------------------------------
Attachment: JBIDE-4864.patch
Denny:
This patch is for you. I want you to look it over, clean it up a little bit, play with it,
and see if you think this will satisify all requirements. I think it does a pretty good
job but it needs some cleanup.
Thanks for being ready to receive it =]
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
Attachments: HelloWorldQuickstart.zip, JBIDE-4864.patch
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
3:22 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Rob Stryker reassigned JBIDE-4864:
----------------------------------
Assignee: Denny Xu (was: Rob Stryker)
Passing over to Denny
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: Denny Xu
Attachments: HelloWorldQuickstart.zip, JBIDE-4864.patch
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
7:10 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4864:
------------------------------------
Denny:
Did you apply this patch? Did you change anything in this patch? Did you clean it up and
add icons? You haven't commented here or closed the issue so I assume it's still
opened....
Please update the status of this bug
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: Denny Xu
Attachments: HelloWorldQuickstart.zip, JBIDE-4864.patch
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
10:48 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Gary Brown commented on JBIDE-4864:
-----------------------------------
Can you update the format of the version number generated on deployment to be:
yyyymmddHHMMSS
This will be easier for people to understand (i.e. when the deployment occurred) and also
help to match against the deployed Jar in the JBoss AS deploy folder based on easier
recognition of the date/time.
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: Denny Xu
Attachments: HelloWorldQuickstart.zip, JBIDE-4864.patch
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
11:03 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-4864:
---------------------------------
I created a new jira for version number format: JBIDE-5363
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: Denny Xu
Attachments: HelloWorldQuickstart.zip, JBIDE-4864.patch
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
11:45 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-4864:
---------------------------------
The patch applied, I didn't do any change, just have done some changes in my local
workspace, it seems that the patch can satisfy requirements, so I will discard any
changes in my workspace.
about the icons, do you mean icons for children of bpel module in server view? I use the
bpel module icon, but it can not display since the whole server view can not display icons
and label correctly as said before.
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: Denny Xu
Attachments: HelloWorldQuickstart.zip, JBIDE-4864.patch
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
11:27 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4864) BPEL Process Versioning
[
https://jira.jboss.org/jira/browse/JBIDE-4864?page=com.atlassian.jira.plu...
]
Denny Xu resolved JBIDE-4864.
-----------------------------
Fix Version/s: 3.1.0.CR1
Resolution: Done
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: Denny Xu
Fix For: 3.1.0.CR1
Attachments: HelloWorldQuickstart.zip, JBIDE-4864.patch
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
5318
days inactive
5406
days old
jbosstools-issues@lists.jboss.org
25 comments
5 participants
participants (5)
-
Brian Fitzpatrick (JIRA) -
Denny Xu (JIRA)
-
Gary Brown (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)