Hi,
I'm doubtful that this will work for releases other than v3 Prelude.
According to v3 Prelude documentation for registering an event provider
<
http://download.oracle.com/docs/cd/E19776-01/820-6583/ghplz/index.html>:*
*
*Note –* The ProbeProviderFactory.getProbeProvider method is an
unstable interface and is subject to change.
And indeed it did change.
In v3 Prelude, users had to write a Java interface to define an event
provider and then use the ProbeProviderFactory.getProbeProvider method
to generate an implementation of the interface.
In releases v3, 3.0.1 and 3.1, users write a Java class
<
http://download.oracle.com/docs/cd/E18930_01/html/821-2415/ghopc.html#ghovq>,
not an interface, thereby obviating the need to generate an implementation.
Regards,
-Paul
On 04/04/11 07:28, forums_at_java.net wrote:
> Right the OSGI components will get automatically picked up by GlassFish
> monitoring - that's what the docs refer to. But a deployed app doesn't
> automatically get picked up. For a deployed application, you should
> be able
> to register the probes by calling
> probeProviderFactory.getProbeProvider(getClass());. See
> http://blogs.sun.com/foo/entry/mort_learns_how_to_use
>
>
>
>
> --
>
> [Message sent by forum member 'jc129909']
>
> View Post: http://forums.java.net/node/781136
>
>
--
Oracle <http://www.oracle.com>
Paul Davies| Principal Technical Writer| +1.408.276.3413
Oracle GlassFish Server Documentation
4140 Network Circle, Santa Clara CA 95054, USA
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment