4:54 a.m.
HI,
there have been recent changes to the deployment handling
so for /deployment there is now a sub element "content".
The same structure seems to exist for
/server-group=x/deployment=y too. When I :add I always get a duplicate entry exception
Is there an example available how this is supposed to work now?
Thanks
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
7:37 a.m.
Hmm. This code is working for me from the console:
ModelNode operation = new ModelNode();
operation.get(ADDRESS).add("server-group", serverGroup);
operation.get(ADDRESS).add("deployment", deployment.getName());
operation.get(OP).set("add");
But if I do this from the CLI:
[domain@localhost:9999 /]
/deployment=beanvalidation.war/server-group=main-server-group/:add
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" =>
"No
handler for add at address [
(\"deployment\" => \"beanvalidation.war\"),
(\"server-group\" => \"main-server-group\")
]"}
}
Quoting "Heiko W.Rupp" <hrupp(a)redhat.com>:
HI,
there have been recent changes to the deployment handling
so for /deployment there is now a sub element "content".
The same structure seems to exist for
/server-group=x/deployment=y too. When I :add I always get a
duplicate entry exception
Is there an example available how this is supposed to work now?
Thanks
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
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
8:45 a.m.
On 5/19/11 7:37 AM, ssilvert(a)redhat.com wrote:
Hmm. This code is working for me from the console:
ModelNode operation = new ModelNode();
operation.get(ADDRESS).add("server-group", serverGroup);
operation.get(ADDRESS).add("deployment", deployment.getName());
operation.get(OP).set("add");
But if I do this from the CLI:
[domain@localhost:9999 /]
/deployment=beanvalidation.war/server-group=main-server-group/:add
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description"
=> "No
handler for add at address [
(\"deployment\" => \"beanvalidation.war\"),
(\"server-group\" => \"main-server-group\")
]"}
}
Your CLI path is backwards. Should be
/server-group=main-server-group/deployment=beanvalidation.war:add
Quoting "Heiko W.Rupp"<hrupp(a)redhat.com>:
> HI,
>
> there have been recent changes to the deployment handling
> so for /deployment there is now a sub element "content".
>
> The same structure seems to exist for
>
> /server-group=x/deployment=y too. When I :add I always get a
> duplicate entry exception
>
> Is there an example available how this is supposed to work now?
>
> Thanks
> 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
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
8:59 a.m.
Quoting Brian Stansberry <brian.stansberry(a)redhat.com>:
On 5/19/11 7:37 AM, ssilvert(a)redhat.com wrote:
> Hmm. This code is working for me from the console:
>
> ModelNode operation = new ModelNode();
> operation.get(ADDRESS).add("server-group", serverGroup);
> operation.get(ADDRESS).add("deployment", deployment.getName());
> operation.get(OP).set("add");
>
> But if I do this from the CLI:
>
> [domain@localhost:9999 /]
> /deployment=beanvalidation.war/server-group=main-server-group/:add
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description"
=> "No
> handler for add at address [
> (\"deployment\" => \"beanvalidation.war\"),
> (\"server-group\" => \"main-server-group\")
> ]"}
> }
>
Your CLI path is backwards. Should be
/server-group=main-server-group/deployment=beanvalidation.war:add
This document
http://community.jboss.org/wiki/FormatOfADetypedOperationRequest
says, "The order in which the items appear in the request is not relevant."
Is order somehow important in the CLI but not in the API? Or is that
sentence referring to something other than the address?
In this case, how would I know the proper order?
In actuality, this really makes more sense:
/server-group=main-server-group/:add(deployment=beanvalidation.war)
>
> Quoting "Heiko W.Rupp"<hrupp(a)redhat.com>:
>
>> HI,
>>
>> there have been recent changes to the deployment handling
>> so for /deployment there is now a sub element "content".
>>
>> The same structure seems to exist for
>>
>> /server-group=x/deployment=y too. When I :add I always get a
>> duplicate entry exception
>>
>> Is there an example available how this is supposed to work now?
>>
>> Thanks
>> 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
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
9:09 a.m.
Am 19.05.2011 um 15:59 schrieb ssilvert(a)redhat.com:
In actuality, this really makes more sense:
/server-group=main-server-group/:add(deployment=beanvalidation.war)
All :add are
/x=y/z=newItem:add(params)
While not completely what people expect, it is working like that throughout the whole
tree.
My deployment issue is still fragile - even if I wrote differently a few moments ago
*sigh*.
This used to work (well).
--
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:23 a.m.
On 5/19/11 8:59 AM, ssilvert(a)redhat.com wrote:
Quoting Brian Stansberry<brian.stansberry(a)redhat.com>:
> On 5/19/11 7:37 AM, ssilvert(a)redhat.com wrote:
>> Hmm. This code is working for me from the console:
>>
>> ModelNode operation = new ModelNode();
>> operation.get(ADDRESS).add("server-group", serverGroup);
>> operation.get(ADDRESS).add("deployment", deployment.getName());
>> operation.get(OP).set("add");
>>
>> But if I do this from the CLI:
>>
>> [domain@localhost:9999 /]
>> /deployment=beanvalidation.war/server-group=main-server-group/:add
>> {
>> "outcome" => "failed",
>> "failure-description" =>
{"domain-failure-description" => "No
>> handler for add at address [
>> (\"deployment\" => \"beanvalidation.war\"),
>> (\"server-group\" => \"main-server-group\")
>> ]"}
>> }
>>
>
> Your CLI path is backwards. Should be
>
> /server-group=main-server-group/deployment=beanvalidation.war:add
This document
http://community.jboss.org/wiki/FormatOfADetypedOperationRequest
says, "The order in which the items appear in the request is not relevant."
Is order somehow important in the CLI but not in the API? Or is that
sentence referring to something other than the address?
I've revised the document. The order in which the outermost elements
appear is not relevant. Order is very important to an address, as the
whole structure of management resources is a tree.
In this case, how would I know the proper order?
Using the :read-resource-description command from the top of the tree
you can discover the entire structure.
In actuality, this really makes more sense:
/server-group=main-server-group/:add(deployment=beanvalidation.war)
>
>>
>> Quoting "Heiko W.Rupp"<hrupp(a)redhat.com>:
>>
>>> HI,
>>>
>>> there have been recent changes to the deployment handling
>>> so for /deployment there is now a sub element "content".
>>>
>>> The same structure seems to exist for
>>>
>>> /server-group=x/deployment=y too. When I :add I always get a
>>> duplicate entry exception
>>>
>>> Is there an example available how this is supposed to work now?
>>>
>>> Thanks
>>> 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
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
9:03 a.m.
Update to my issue
I was also sending the runtime-name which was fine previously,
but which now seems to indicate that I want to add the content to /deployment too
Am 19.05.2011 um 15:45 schrieb Brian Stansberry:
On 5/19/11 7:37 AM, ssilvert(a)redhat.com wrote:
> Hmm. This code is working for me from the console:
>
> ModelNode operation = new ModelNode();
> operation.get(ADDRESS).add("server-group", serverGroup);
> operation.get(ADDRESS).add("deployment", deployment.getName());
> operation.get(OP).set("add");
>
> But if I do this from the CLI:
>
> [domain@localhost:9999 /]
> /deployment=beanvalidation.war/server-group=main-server-group/:add
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description"
=> "No
> handler for add at address [
> (\"deployment\" => \"beanvalidation.war\"),
> (\"server-group\" => \"main-server-group\")
> ]"}
> }
>
Your CLI path is backwards. Should be
/server-group=main-server-group/deployment=beanvalidation.war:add
>
> Quoting "Heiko W.Rupp"<hrupp(a)redhat.com>:
>
>> HI,
>>
>> there have been recent changes to the deployment handling
>> so for /deployment there is now a sub element "content".
>>
>> The same structure seems to exist for
>>
>> /server-group=x/deployment=y too. When I :add I always get a
>> duplicate entry exception
>>
>> Is there an example available how this is supposed to work now?
>>
>> Thanks
>> 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
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
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
5023
days inactive
5023
days old
6 comments
3 participants
participants (3)
-
Brian Stansberry -
Heiko W.Rupp -
ssilvert＠redhat.com