[
https://jira.jboss.org/jira/browse/JBAS-6647?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-6647:
------------------------------------
Also, I think it may make more sense to key the templates off of the ManagedComponent type
names, rather than having separate template names, i.e.:
ManagementView.getTemplate(ComponentType componentType)
rather than:
ManagementView.getTemplate(String templateName)
Or if we need to support having multiple templates per component type, perhaps the notion
of a default template and a new getDefaultTemplate() method could be added, i.e.:
ManagementView.getDefaultTemplate(ComponentType componentType)
If we had either of these APIs, we wouldn't have to maintain a ProfileService template
name for each RHQ ResourceType in the jboss-as-5 plugin descriptor.
"XAConnectionFactoryTemplate" and possibly other templates
are missing from ManagementView
------------------------------------------------------------------------------------------
Key: JBAS-6647
URL:
https://jira.jboss.org/jira/browse/JBAS-6647
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Environment: Hudson AS 5.1 build from 3/19/09
Reporter: Ian Springer
Assignee: Scott M Stark
Fix For: JBossAS-5.1.0.CR1
The ManagedProperty in the template looks like this:
ManagementView.getTemplateNames() returns the following Strings:
[TopicTemplate, QueueTemplate, XADataSourceTemplate, TxConnectionFactoryTemplate,
NoTxDataSourceTemplate, NoTxConnectionFactoryTemplate, LocalTxDataSourceTemplate]
It seems to be missing at least the following template:
XAConnectionFactoryTemplate
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira