JBossAS 5.1.0.GA no WebServer JMX Notifications

[ramses]

I want to migrate a following behavior from JBoss 4.0.3SP1 to JBoss 5, but it does not work.

A JMX notification listener is added at "jboss.web:service=WebServer" to be notified when a war file is deployed to get the context root from the WebMetaData of the notification.

The problems are:
1) The WebServer MBean did not send notifications any more.

2) The method getContextRoot() does not exist at WebMetaData.

Do you have any ideas, how to achieve this behavior with JBoss 5, too.
Maybe with "deployment callbacks" (if yes do you have a example for me)

br Ramses

[jaikiran]

Which specific version of JBoss AS-5? I remember seeing some similar thread earlier, although i am not able to locate it now.

[jaikiran]

Is this the notification you are talking about http://www.jboss.org/index.html?module=bb&op=viewtopic&t=150436

[jaikiran]

"ramses" wrote:


2) The method getContextRoot() does not exist at WebMetaData.

The WebMetaData you are talking about is the JBoss specific class, isn't it? How and where are you using that class in your code? Any specific reason why you relied on the JBoss specific class? Maybe we can recommend some other way.

[ramses]

"jaikiran" wrote:
Which specific version of JBoss AS-5?

JBossAS 5.1.0.GA

"jaikiran" wrote:
Is this the notification you are talking about http://www.jboss.org/index.html?module=bb&op=viewtopic&t=150436

No. The notification is from jboss.web:service=WebServer type is org.jboss.deployment.SubDeployer.init

The userdata of this notification are org.jboss.deployment.DeploymentInfo. A member of the DeploymentInfo is org.jboss.metadata.WebMetaData.

We use this to get infos from a war deployment (context root, env-entries, security roles) defined in web.xml

br Ramses

[jaikiran]

Looks like because of the changes to deployers in AS-5, the notifications are no longer generated. In AS-4.x, the deployers used to be supported by the SubDeployer which used to generate these notifications. However in AS-5, deployers are backed by the Virtual Deployer Framework and don't generate these notifications. Here's the other threads:

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=158120

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160122

Would you like to open a JIRA for this https://jira.jboss.org/jira/browse/JBAS? If not, i'll create one tomorrow.

[alesj]

"jaikiran" wrote:

Would you like to open a JIRA for this https://jira.jboss.org/jira/browse/JBAS? If not, i'll create one tomorrow.

There is no sense in porting/bringing this back.
* JMX will become optional
* The old deployment API doesn't exist anymore

What used to be notification+listener combo,
can now simply be replaced by a plain deployer pojo.

You should re-write your listener to be a AS5/MC deployer.
If you need some help on how to do that, open a new MC user forum post.

[jaikiran]

"alesj" wrote:

There is no sense in porting/bringing this back.
* JMX will become optional
* The old deployment API doesn't exist anymore

What used to be notification+listener combo,
can now simply be replaced by a plain deployer pojo.

It need not be based on the old deployment API. However, IMO, there should be some mechanism through which the end user applications can rely on notification/events of applications being deployed.

"alesj" wrote:

You should re-write your listener to be a AS5/MC deployer.

IMO, i think this should be provided by AS (deployer framework) instead of each individual application developer (/end user) coming up with their own versions. Once it's available, i guess the end user can just switch it on/off by configuring the appropriate MC beans. Thoughts?

[alesj]

"jaikiran" wrote:

It need not be based on the old deployment API. However, IMO, there should be some mechanism through which the end user applications can rely on notification/events of applications being deployed.

There already exists such mechanism, it's called VDF. ;-)

"jaikiran" wrote:

IMO, i think this should be provided by AS (deployer framework) instead of each individual application developer (/end user) coming up with their own versions. Once it's available, i guess the end user can just switch it on/off by configuring the appropriate MC beans. Thoughts?

Provide what?
Anything more exact/custom would be meaningless.

[jaikiran]

"alesj" wrote:

Provide what?

A callback which gets invoked when a deployment has been processed by all available deployers. I don't think we have that support right now, do we?

[alesj]

"jaikiran" wrote:

A callback which gets invoked when a deployment has been processed by all available deployers. I don't think we have that support right now, do we?

You could add a new deployment stage, after DeploymentStages.INSTALLED,
and have a deployer for that stage which would do what even final processing you like.

[ramses]

"alesj" wrote:
You should re-write your listener to be a AS5/MC deployer.
If you need some help on how to do that, open a new MC user forum post.

"alesj" wrote:
You could add a new deployment stage, after DeploymentStages.INSTALLED,
and have a deployer for that stage which would do what even final processing you like.

Sorry, but I need some initial hints, how I can do this. There are any examples, documents, links etc for this or similar purpose.

br Ramses

[alesj]

"ramses" wrote:

Sorry, but I need some initial hints, how I can do this. There are any examples, documents, links etc for this or similar purpose.

Check any of the numerous Deployers tests.
* http://anonsvn.jboss.org/repos/jbossas/projects/jboss-deployers/trunk