Thanks Adrian, I will leave the notification content as is and make
DeploymentInfo accessible from MainDeployer via a managed-operation.
(Less work, too;-)
Thanks
david
On 2002.04.13 20:26:31 -0400 Adrian Brock wrote:
> Hi,
>
> Just a heads up.
>
> I realise this notification was originally
Hi,
Just a heads up.
I realise this notification was originally only used
by the farm service, and is only used locally.
But ideally all JMX notifications should contain
Serializable data, for people who want to monitor
remotely.
Currently, the DeploymentInfo isn't Serializable.
Regards,
Adrian
On 2002.04.13 15:39:37 -0400 Frederick N. Brier wrote:
> You know I read your MBean deployment message back on 10Sep2001, but it
> didn't really penetrate because we had already added the
> DeploymentNotification mechanism to 2.4x. I think I could re-engineer my
>
> code to fit within the .sar
You know I read your MBean deployment message back on 10Sep2001, but it
didn't really penetrate because we had already added the
DeploymentNotification mechanism to 2.4x. I think I could re-engineer my
code to fit within the .sar approach. What I called "creating MBeans
instances" associated
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 12, 2002 7:04 PM
Subject: Re: [JBoss-dev] Deployment Notifications in JBoss 3.0 changed
> Looks OK to me. I'll check with Andy about the FarmService. Do you need
> notifications of each step (there are actuall
Looks OK to me. I'll check with Andy about the FarmService. Do you need
notifications of each step (there are actually 5 or 6) or are the deploy
and undeploy notifications enough?
I'm not sure exactly what you are using the notifications for, but I assume
you know about the *-service.xml files
I had submitted some JMX deployment notification code
(DeploymentNotification class and mods to the J2eeDeployer class) which was
incorporated into JBoss 2.4x. I've just started migrating to JBoss 3.0 and
noticed that the DeploymentInfo object is not passed in the Notification
anymore, only t
