7:46 a.m.
Heiko,
This sounds cool - I haven't followed the development of this - can you
talk about what you did to implement this:
https://jira.jboss.org/jira/browse/JOPR-39
https://jira.jboss.org/jira/browse/JOPR-37
Does this utilize the content subsystem in some way?
8:01 a.m.
Mazz,
This sounds cool - I haven't followed the development of this - can
you talk about what you did to implement this:
https://jira.jboss.org/jira/browse/JOPR-39
https://jira.jboss.org/jira/browse/JOPR-37
I still need to write documentation.
Basically:
- the create ear/war in inventory got an option to select if a backup
should be
created. If so, the original file will be moved to <file>.bak and the
new one deployed
- to roll back I added an operation that first moves file to
<file>.tmp.bak and tries then
to move <file>.bak to <file>. If this fails it moves <file>.tmp.bak
back to <file>
Does this utilize the content subsystem in some way?
No - especially as the ear/war create is tied in the inventory and not
in the content subsystem.
Heiko
--
Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei
Muenchen
Handelsregister: Amtsgericht Muenchen HRB 153243
Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham,
Werner Knoblich
9:27 a.m.
We should discuss this further. As per the status call, I get the
feeling this is a one-off implementation via a custom operation in order
to implement rollback for a specific resource type.
Instead, what we should do is look into implementing this kind of
feature across all resource types by enhancing the content subsystem
(and "create resource using packages" feature).
Was this on the roadmap? AFAIK, this feature was not triaged nor on the
release schedule. That's why I was surprised when I saw it come over the
wire. But I could be wrong.
Heiko W.Rupp wrote:
Mazz,
>
> This sounds cool - I haven't followed the development of this - can
> you talk about what you did to implement this:
>
> https://jira.jboss.org/jira/browse/JOPR-39
> https://jira.jboss.org/jira/browse/JOPR-37
I still need to write documentation.
Basically:
- the create ear/war in inventory got an option to select if a backup
should be
created. If so, the original file will be moved to <file>.bak and the
new one deployed
- to roll back I added an operation that first moves file to
<file>.tmp.bak and tries then
to move <file>.bak to <file>. If this fails it moves <file>.tmp.bak
back to <file>
> Does this utilize the content subsystem in some way?
No - especially as the ear/war create is tied in the inventory and not
in the content subsystem.
Heiko
1:37 p.m.
Mazz,
Am 13.02.2009 um 16:27 schrieb John Mazzitelli:
We should discuss this further. As per the status call, I get the
feeling this is a one-off implementation via a custom operation in
order to implement rollback for a specific resource type.
Yes. ear/war for now. It was a quick implementation and is helping
users.
Instead, what we should do is look into implementing this kind of
feature across all resource types by enhancing the content subsystem
(and "create resource using packages" feature).
I think the content subsystem needs some love - you know a lot about
it, but for Joe User, it
is not obvious what it does - especially as .war files are not content
of a AS resource but of a
not yet existing .war resource. We need to think how to optimize this.
Heiko
--
Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei
Muenchen
Handelsregister: Amtsgericht Muenchen HRB 153243
Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham,
Werner Knoblich
5795
days inactive
5795
days old
3 comments
2 participants
participants (2)
-
Heiko W.Rupp -
John Mazzitelli