HTTP API Status & DMR GWT Prototype
by Jason T. Greene
Last week Brian merged my http api patch into his detyped2; however, the
most current iteration is here:
https://github.com/n1hility/jboss-as/tree/detyped2
Currently JSON read operations via GET are supported, POST is coming
soon, now that Jonathan Pearlin, a new contributor, recently completed
the JSON parser patch he was working on (Thanks Jonathan!). In addition
a special base64 encoded binary representation is also supported;
however, I will explain its purpose in another email.
The GET URL form is a mapping of operation addresses, with a few
supported read operations, and support for mapping top level values via
query parameters. The default operation is read-resource. So in
otherwords you can dump the whole management tree like so:
http://localhost:9990/domain-api?recursive
The lack of additional /'s defaults to the root node.
The lack of an "operation" defaults to the read-resource operation.
The "recursive" is mapped to the recursive as a boolean, a lack of an
assignment defaults to "true"
The attributes of the http web connector can be restrieved with:
http://localhost:9990/domain-api/subsystem/web/connector/http
A single attribute can be retrieved by specifying the attribute
operation and the attribute name:
http://localhost:9990/domain-api/subsystem/threads/bounded-queue-thread-p...
The full description of the mode can be retrieved using the
read-resource-description operation like so:
http://localhost:9990/domain-api?operation=resource-description&recursive....
--
Jason T. Greene
JBoss, a division of Red Hat
13 years, 9 months
JBoss AS 7 JMX Support
by Francesco Marchioni
Dear JBoss developers,
just wondering if JMX support will be changed in the release 7 of the application server.
I've tried running a basic JMX local (web) client:
Calculator cal = null;
MBeanServer server = MBeanServerLocator.locate();
cal = (CalculateInterest) MBeanProxyExt.create(
CalculateInterest.class,"sampleJMX:service=calculateInterest",server);However the MBeanProxyExt class cannot be found by the javac compiler. Do you know if earlier JMX based applications will be compatible with the AS 7 release ?
Thanks a lot
Francesco
13 years, 9 months
Compatibility with earlier JMX clients ?
by Marchioni Francesco
Dear JBoss developers,
just wondering if JMX support will be changed in the release 7 of the
application server.
I've tried running a basic JMX local (web) client:
Calculator cal = null;
MBeanServer server = MBeanServerLocator.locate();
cal = (CalculateInterest) MBeanProxyExt.create(
CalculateInterest.class,"sampleJMX:service=calculateInterest",server);
However the MBeanProxyExt class cannot be found by the javac compiler.
Do you know if earlier JMX based applications will be compatible with
the AS 7 release ?
Thanks a lot
Francesco
--------------------------------------------------------------------------------------------------------
Le informazioni trasmesse possono contenere documenti confidenziali e/o materiale riservato; sono
quindi da intendersi esclusivamente ad uso della persona e/o societa a cui sono indirizzate.
Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte
di persone e/o societa diversi dai destinatari indicati, e proibito ai sensi della legge 196/2003.
Qualora questa mail fosse stata ricevuta per errore, si prega di contattare il mittente e cancellarne
il contenuto.
--
Privileged/Confidential Information may be contained in this message. If you are not the addressee
indicated in this message (or responsible for delivery of the message to such person), you may not
copy or deliver this message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind. Opinions, conclusions and other information in this
message that do not relate to the official business of my firm shall be understood as neither given
nor endorsed by it.
--------------------------------------------------------------------------------------------------------
13 years, 9 months
Domain vs. ServerGroup Deployments
by Heiko Braun
Can somebody explain the relation between domain (a) and server group (b) deployments?
Is b) simply a reference to a)? Or are these two distinct sets?
Ike
13 years, 9 months
Re: [jboss-as7-dev] cli
by Kabir Khan
Sent from my Android phone using TouchDown (www.nitrodesk.com)
>>
>> On master, Kabir introduced a notion of different types of clients
>> (DOMAIN, HOST, STANDALONE) which are implemented by passing an enum to
>> ModelControllerClient.Factory.create(). We need to think through how
>> that relates to this; whether that distinction is required and how to
>> express it in the CLI.
>>
>> The actual core API is the same between DOMAIN, HOST, STANDALONE (i.e.
>> operations expressed in DMR and passed to the managed process and
>> operation results in DMR are passed back); the real difference is just
>> what the expected addresses and operations are. Right now the enum is
>> just used to check that the client is connecting to the expected kind of
>> process. Conceivably we don't need the DOMAIN/HOST/STANDALONE enum and
>> we just count on users knowing what they are doing.
>
> The reason I added that was the host management socket. If the DC is local, both HC and DC requests will come in on the same socket. We need some differentiator to know if a request should go to the HC or the DC.
Well any host management socket should know how to answer host changes,
domain changes, and server changes; it should be one protocol on one
socket with the only differentiator being the address in question.
>>>>> I agree the enum isn't the best way of doing it and that the connection is a good way. I still don't see how we will distinguish operations coming from outside, such as the cli, when the node is both the dc and dc. Addresses starting with host->* will be for the hc and currently routed via the proxies. But for less unique things like interface-> which exist in both I say we still need something else (it could be an extra parameter in the operation specifying the level) or some rule that if a hc is running a local dc, all outside connections are for the dc. Or did we ever decide that hc will only accept incoming commands via dc?
For host changes, that host's configuration change is effected
immediately. For domain changes, if the node is the DC it can handle it
locally, else it'd forward on (on the user's behalf, presumably). For
server changes, it'd require that the caller has the appropriate
credentials (some operations, like reads and most runtime-only changes,
can be carried out by users, while others, like server model changes,
may only be carried out by the HC).
--
- DML
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Sent from my Android phone using TouchDown (www.nitrodesk.com)
13 years, 9 months
Web UI: Profile & host sections mutable?
by Heiko Braun
I am wondering if it will be possible to create profiles from the web ui? Does it make sense? A similiar question arises for host configurations. How does the discovery work?
Can someone outline which parts of the model cannot be changed? I.e would require a controller restart?
For now i am assuming that profiles are immutable (the top level elements, not the subsystems).
Ike
13 years, 9 months
testsuite
by ssilvert＠redhat.com
I see that there's not that much in there right now. Am I free to add
a JSF test module to testsuite or are we putting component tests
somewhere else?
Also, is there any documentation on using the arquillian module that
is there in the as7 build?
Stan
13 years, 9 months
DMR GWT Prototype
by Jason T. Greene
I was able to port DMR so that it can be used with GWT to send and
receive DMR's native externalized binary format via client-side javascript.
https://github.com/n1hility/jboss-as/tree/detyped2
A pure binary protocol is not possible in all browsers, so the
implementation has to base64 encode the stream.
The main advantage to this approach is that there is essentially no loss
of information (all type info is preserved), and the API works very well
at dynamic access and is exactly the same as the management API used in
server code. In addition parsing requests on the server is much more
efficient since there is less transformation and pattern matching.
Lastly it has the potential to be much more space efficient.
However, due to Javascript's very poor binary handling, lack of
streaming, and lack of native floating point encoding, client side
execution is on average 2x+ slower than directly evaling JSON code. That
said, processing a dump of the entire model took on average 9ms (in
webkit based browsers), and in the worst case (firefox) took 20ms. So
the times are still somewhat reasonable.
In addition to being faster on the client side, eval'd JSON does not
require maintaining the DMR API. On the other hand JSON usage in GWT is
clumsy if you aren't using overlay types, and overlay types are not
helpful to dynamic client code (dynamic as in being able to discover and
manage resources based on resource descriptions as opposed to static code).
Lastly, JSON output, by its nature, loses type information. Although
this could be worked around if it's a problem by adding type identifiers
to all node values, at the cost of looking less JSON like (extra verbose).
So ultimately it's up to everyone working on the console as to which
direction this goes. I can easily support both mechanisms on the server.
--
Jason T. Greene
JBoss, a division of Red Hat
13 years, 9 months
Re: [jboss-as7-dev] EJB Container on AS 7
by Marchioni Francesco
>> Dear AS 7 developers,
>>
>> can anybody tell me about the EJB container- when will it be
available
>> on the AS 7 stack ?
>We are developing it even as we speak. Assuming all goes well we
should
>have most of the basic functionality working in 3-4 weeks, though there
>will be a number of small details that may not be functional right
away.
>As soon as we have the basics working we'll definitely be sending out a
>note to let everyone know.
Thanks for your kind reply David. Will have a look at docs in the next
days.
Regards
Francesco
--------------------------------------------------------------------------------------------------------
Le informazioni trasmesse possono contenere documenti confidenziali e/o materiale riservato; sono
quindi da intendersi esclusivamente ad uso della persona e/o societa a cui sono indirizzate.
Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte
di persone e/o societa diversi dai destinatari indicati, e proibito ai sensi della legge 196/2003.
Qualora questa mail fosse stata ricevuta per errore, si prega di contattare il mittente e cancellarne
il contenuto.
--
Privileged/Confidential Information may be contained in this message. If you are not the addressee
indicated in this message (or responsible for delivery of the message to such person), you may not
copy or deliver this message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind. Opinions, conclusions and other information in this
message that do not relate to the official business of my firm shall be understood as neither given
nor endorsed by it.
--------------------------------------------------------------------------------------------------------
13 years, 9 months
