6:07 a.m.
Hi,
suppose I have a domain with 2 server groups A and B and two times a foo.war file in
version A and B.
Uploading to the domain works, and I get different hashes back
{"outcome":"success","result":{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="},"compensating-operation":null}
sha: 7jgpMVmynfxpqp8UDleKLmtgbrA=
ok.
As I understand next step is now to add this to /deploment/test.war:add(hash= .<from
above> , name="test.war")
And here I already have the previous version added, so that new add fails:
Json to send:
{"address":[{"deployment":"test.war"}],"operation":"add","hash":{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="},"name":"test.war"}
java.lang.AssertionError:
{"outcome":"failed","result":{"domain-failure-description":[{"java.lang.IllegalStateException":"Resource
at address [(\"deployment\" => \"test.war\")] already
exists"}]}
I think it should be allowed to have multiple files with the same name - especially as the
files can be identified via <name,hash>
Heiko
8:48 a.m.
On 4/8/11 6:07 AM, Heiko W.Rupp wrote:
Hi,
suppose I have a domain with 2 server groups A and B and two times a foo.war file in
version A and B.
Uploading to the domain works, and I get different hashes back
{"outcome":"success","result":{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="},"compensating-operation":null}
sha: 7jgpMVmynfxpqp8UDleKLmtgbrA=
ok.
As I understand next step is now to add this to /deploment/test.war:add(hash= .<from
above> , name="test.war")
And here I already have the previous version added, so that new add fails:
Json to send:
{"address":[{"deployment":"test.war"}],"operation":"add","hash":{"BYTES_VALUE":"7jgpMVmynfxpqp8UDleKLmtgbrA="},"name":"test.war"}
java.lang.AssertionError:
{"outcome":"failed","result":{"domain-failure-description":[{"java.lang.IllegalStateException":"Resource
at address [(\"deployment\" => \"test.war\")] already
exists"}]}
I think it should be allowed to have multiple files with the same name - especially as
the files can be identified via<name,hash>
This is what the runtime-name is for. I'm trying to make the hash
disappear as something the end-user cares about, e.g. the underlying
/deployment=foo.war:add operation can itself accept the content and
upload it, thus removing the need for the end user to care about the hash.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
8:53 a.m.
Am 08.04.2011 um 15:48 schrieb Brian Stansberry:
This is what the runtime-name is for. I'm trying to make the hash
disappear as something the end-user cares about, e.g. the underlying
/deployment=foo.war:add operation can itself accept the content and
upload it, thus removing the need for the end user to care about the hash.
I don't really care about the hash here.
If I upload test.war v1 and v2, both will be named at upload test.war and
as runtime name test.war, as they are supposed to go into different server groups.
Previously they would have been on two (physically) different clusters, but now
one can expect that users will want to set up one server group for test and another
for integration where they more or less deploy the same stuff into.
Heiko
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera
9:52 a.m.
On 4/8/11 8:53 AM, Heiko W.Rupp wrote:
Am 08.04.2011 um 15:48 schrieb Brian Stansberry:
> This is what the runtime-name is for. I'm trying to make the hash
> disappear as something the end-user cares about, e.g. the underlying
> /deployment=foo.war:add operation can itself accept the content and
> upload it, thus removing the need for the end user to care about the hash.
I don't really care about the hash here.
If I upload test.war v1 and v2, both will be named at upload test.war and
as runtime name test.war, as they are supposed to go into different server groups.
Previously they would have been on two (physically) different clusters, but now
one can expect that users will want to set up one server group for test and another
for integration where they more or less deploy the same stuff into.
So you upload them as test.war.v1 and test.war.v2 both with runtime-name
test.war. They are two distinct deployments that need to be managed
separately, and their name is their unique handle in the management
system. The runtime-name is how the non-management layers in the running
server (i.e. the deployment processors and subsystem services) see the
deployment.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
5009
days inactive
5009
days old
3 comments
2 participants
participants (2)
-
Brian Stansberry -
Heiko W.Rupp