On 2. Dec 2008, at 20:10, Kedar Mhaswade wrote:
> I'll take the responsibility of the fact that this document is out-
> of-date,
> though the situation has not changed much ;).
>
> This is something that I still want to do because RMI is not
> something that
> people like. We did have an HTTP/S based internal communication
> channel that
> implemented JSR-160, but it is/was not exposed such that it can be
> used via
> JConsole. It is limited only to NetBeans and asadmin as of now.
>
> Do you have sufficient interest in this? We can work on resurrecting
> this work.
Honestly, I am more interested in the new WS-JMX connector, which is
based on Wiseman and JAX-WS. That is because I am looking to manage
Metro/JAX-WS web services and a connector based on JAX-WS feels just
right in that case. :-) The HTTP/S connector could be an option for
people that e.g. don't want the complexity of web services and need to
deal with HTTP proxies. But we don't have any concrete requests for
that kind of thing and most HTTP proxies deal with SOAP messages just
fine. In other words, the interest is probably not sufficient.
It would be good to stick a creation date on that page.
Fabian
> Fabian Ritzmann wrote:
>> Hi,
>> I bumped into this page:
>> https://glassfish.dev.java.net/javaee5/admin-infra/http-jmx-connector.html
>> It says: "It will soon be possible to connect to Glassfish
>> Administration Infrastructure over HTTP/S using JConsole. Watch out
>> for the details ..."
>> The page gives no indication how recent that information is. Has
>> the HTTP/S connector ever been implemented? Is there any
>> documentation how to use it with JConsole? If the implementation is
>> not done, are there plans to finish it and when?
>> Fabian
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net