Allow developers and/or deployers deactivate JMX setup
------------------------------------------------------
Key: AXIS-2643
URL: https://issues.apache.org/jira/browse/AXIS-2643
Project: Axis
Issue Type: Improvement
Components: Deployment / Registries
Affects Versions: 1.4
Environment: Any.
Reporter: Eduardo Costa
I'm trying to deploy an application (Liferay Portal) in a shared JBoss
instance, but I got a serious problem with Axis:
In org.apache.axis.transport.http.AxisServlet.init() there's a call to
org.apache.axis.management.ServiceAdmin.setEngine(...). It uses
org.apache.axis.management.Registrar to register 3 JMX beans with hardcoded
objectnames. If another web application is deployed on the same server, there's
an obvious name clash.
My suggestion: add an servlet context option "RegisterMBean", default false,
and an option "MBeanBaseObjectName", default "axis". This allows both developer
and deployer to setup MBeans according to their own naming rules. Developer can
use "RegisterMBean" and "MBeanBaseObjectName" to define it, and deployer can
use Application Server features (like JBoss SAR files).
I'll change code and attach a patch ASAP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
