[ https://jira.jboss.org/jira/browse/JBAS-6768?page=com.atlassian.jira.plug... ] Jeff Zhang commented on JBAS-6768: ---------------------------------- from Anil: <asaldhan1> jizhang: the case when SubjectFactory is not injected into the DS handlers need to be handled gracefully <asaldhan1> jizhang: I am wondering if you would be able to add some null checks and handle it gracefully <asaldhan> jizhang: the changes are quite simple. Sometime the definitions can be via MBeans. Since we inject SubjectFactory in the mc beans - the Base2ConnectionFactory does not have the subject factory injected but has the other information <asaldhan> jizhang: so I overlooked the case when some old legacy mbean based defs may be present for DS <asaldhan> jizhang: one potential is to write a MBean class for JBossSubjectFactory and use the @JMX annotation in the config file and force users to add a <depends attribute in their mbean def -- 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

[ https://jira.jboss.org/jira/browse/JBAS-6768?page=com.atlassian.jira.plug... ] Jeff Zhang commented on JBAS-6768: ---------------------------------- @Anil, the user's issue was resolved. Please see forum comment. They use mbean to configure datasource directly instead of ds.xml. Our new Jca layer will be based on MC. For this case, I don't think we need expose the subjectFactory as JMX Mbean. It is a MC bean and work well. :) -- 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