Before, when we discussed the JMX option, and the potential for a
API, I was working under the assumption that tools only needed a basic
set of operations.
List deployed apps/modules/resources
Once this thread started talking about JSR-77 management functions,
this to me says the profile service is the way forward.
Because we don't know
of any other API we can use to get information.
As to the tomcat API, I don't see how it provides anything close
The tomcat API provides the 3 things from above afaics.
> Neither JSR-77 or JSR-88 are going to be part of EE in the future.
> The profileservice certainly is available remotely, but I thought we
> were focusing on the hotdeployment jmx based api as discussed in:
I have asked *many* times now and
*noone* have been able to show me
Profileservice being available remotely without a very *tight* dependency
on the exact version of AS plus noone have been able to tell us the
dependencies we need (except a very fuzzy maven dependency set which
and unique per version).
If the tools have to be updated every time there is a minor release then
this is a very fragile system to depend on.
> If we want this mapped into a resty type api ala the tomcat then
> needs to be defined.
If there is some other API we can use great, but a resty
type API sounds
to me like the best and only option that would not be fragile.
> Max Rydahl Andersen wrote:
>> Anyone out there listening ?
>> Should we just drop this idea of having good remote control over AS
>> from tooling ?
>> Max Rydahl Andersen wrote:
>>>>> Is JSR-77 supported ? Will it be in EAP 5 ?
>>>>> JSR-288 had similar issues earlier - are they fixed ? will they
>>>>> be fixed ?
>>>> JSR-77 is required for EE, but it is very out of date, and will
>>>> likely get killed in a future release. JSR-88 is already scheduled
>>>> for removal in EE7.
>>> So we should not even consider using it for remote access ?
>>>>> What are the alternatives, if any ?
>>>> If you guys need advanced management functionality, it sounds like
>>>> the Profile Service is going to be what you need.
>>> Sure, but profile service is not available to us remotely.
>>> Btw. I don't consider any of the things we want to do very advanced
>>> - we don't want to be another JON.
>>> Something basic and simple as i.e. Tomcat Management API would be
>>> enough for us afaics.
>>> It provides a simple http api to list, start/stop/undeploy
>>> applications/resources (both local and remote resources)
>>> btw. this is not just for *us* this is for the greater good of AS :)
> jboss-development mailing list