There are some plans after discussion with Young:
1. For the code structure, we will create 3 sub packages for implementation of embedded admin console, AS7 domain mode, AS7 standalone mode separately. The most common functions will be abstracted to the package: org.jboss.jca.rhq.core,
And the build process will create 3 jars like:
- ironjacamar-rhq-plugin-local.jar // used in embedded admin console
- ironjacamar-rhq-plugin-domain.jar // used in AS 7 domain mode
- ironjacamar-rhq-plugin-standalone.jar // used in AS 7 standalone mode
except we can find a way to know which situation the current runtime environment is in.
2. If the org.jboss.jca.core.api.management.ManagementRepository can be transferred to RHQ plugin in all situations, we can use it directly without abstracting our own model for this RHQ plugin. This class is used only for RHQ to discover JCA resources.
We suggest some changes on jca management model to remove the WeakReference to the real JCA objects, instead using a string to indicate where we can find the JCA objects, take the org.jboss.jca.core.api.management.ResourceAdapter as an example:
public class ResourceAdapter{
/** This is used as resource meta data, displayed in the navigation tree **/
private String raClassName;
/** This is the location where we can find the real javax.resource.spi.ResourceAdapter
* It will be a ObjectName string in standalone and local situation
* It will be a URI string in AS 7 domain mode to the associated ManagedResource
**/
private String raLocation;
private List<ConfigProperty> configProperties;
}
All config-properties in the JCA objects are needed when user wants to see them(by clicking configuration tab in the RHQ UI page), the value should be retrieved at this time to keep up-to-date. Current design of jca management model works fine in situation of embedded admon console, you get the object reference directly, so that can call the getter methods to get information whenever you want. But in situation of AS 7 domain mode, the objects are transferred from remote to RHQ together with ManagementRepository, when RHQ discovers JCA resources to compse the navigation tree in left pane. The data will not be fresh enough if we retrieve them using their getter methods when user clicks on the configuration tab because the data has been composed already.