That is the correct way, but the axis service is not following the normal service behavior. This is a bug that needs to be fixed.
In the JBoss 4 branch ( I did not look in the 3.2 branch), all 3 mentioned methods call the equivalent methods in super Which is the class SubDeployerSupport
This class is supposed to send notifications.
I am wondering if the notification is sent, but not correctly routed to a listener.
As far as I can see the method getServiceName() will not return anything useful for AxisService. Will this mean that when you register a listener, the Bean server will not be able to determine that you are interested in the notifications sent by the AxisService?
The notification contains the DeploymentInfo, so it is up to the receiver to make sense of that deployment information and extract the actual service name out of the included XML document.
If you want a simpler notification (not broadcasting the DeploymentInfo), I wrote a patch that creates a specific event with the web service name to be able to register a deployed webservice in UDDI. (see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=49094)
I should have been more specific in my post. I was going off of the 3.2.3 release. After getting Scott's reply, I added the calls to super.xxx() and I received the events that I was looking for.
I have fixed this for 3.2.4RC2.