[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sainath Chowdary updated GERONIMODEVTOOLS-434:
----------------------------------------------
Attachment: jmx-dynamicserverinfo.patch
For example, to get a list of Credential Stores deployed on the server, call
GeronimoServerInfoUtil.getInstance().listCredentialStores()
This has a minor limitation as it queries all the servers that are running in
workspace. Suppose 2 Geronimo servers are running, this queries from both of
them which can potentially give raise to errors when dependencies from 2nd
server are added but deployed onto first server.
> Query Dynamic Information from Server using JMX
> -----------------------------------------------
>
> Key: GERONIMODEVTOOLS-434
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434
> Project: Geronimo-Devtools
> Issue Type: Sub-task
> Components: eclipse-plugin
> Affects Versions: 2.1.2, 2.1.x
> Reporter: Sainath Chowdary
> Assignee: Sainath Chowdary
> Fix For: 2.1.2, 2.1.x
>
> Attachments: jmx-dynamicserverinfo.patch
>
>
> Enabling GEP to query server for dynamic information on the lines of
> Plancreator using a JMXConnectionFactory.
> Querying dynamic information has already been done but having a Servlet on
> server side that sends data to GEP. This has severe exceptions when a old
> server is added or custom server assemblies are added to GEP which wont have
> the particular servlet added.
> Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local,
> JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS
> Destination references) from Server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
