Kohsuke Kawaguchi wrote:
>
> Thanks. It sounds like the bottom line is that my expectation and AMX
> is bit different. So maybe I should explain why I ended up looking at
> AMX.
>
> What I'm ultimately trying to do is to programatically control
> Glassfish from my program (for the purpose of testing the JAX-WS RI.)
> I sent an e-mail to this alias earlier (search for "Programatically
> control glassfish?" thread in the archive), and people kindly sent me
> a few leads that I should investigate.
>
> So I started by looking at JSR-88, since one of the things we wanted
> to do was to deploy and undeploy applications. This worked fine, but
> then I realized I needed to do a few more things. One of those was to
> identify the HTTP port number (so that I can access the application
> that I just deployed via HTTP.)
would
http://java.sun.com/javaee/5/docs/api/javax/enterprise/deploy/spi/TargetModuleID.html
help resolve this?
The port should be accessible through the JSR 77 MEjb....
vbk
>
> JSR-88 didn't offer this, and since I'm really not that interested in
> making this portable, I thought perhaps I should look at some
> Glassfish specific management interfaces. The assumption was that
> usually a portable API layer is harder to use (because it's more
> abstract) than the custom container-specific API.
>
> And of the leads people gave me (JSR-88, JSR-77, and AMX), AMX looked
> like the one that fits this profile, so that's why I tried it. I could
> have missed the warning sign somewhere that said this is a low-level
> API not meant for outside developers.
>
>