[ https://jira.jboss.org/jira/browse/JBESB-3198?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-3198: -------------------------------- Issue Type: Bug (was: Feature Request) -- 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/JBESB-3198?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-3198: ------------------------------------- While there was an issue with juddi assuming defaults, this really came about because *our* juddi configuration was not being loaded at the correct point. The ESB project base server contained a juddi-service.sar with its own configuration, now removed (did not affect SOA server). The juddi.war was invoking a servlet to initialise the configuration, again different from the standard (would affect SOA). The JuddiRMIService needed to initialise the configuration *before* the Registry was created. -- 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