Changes to track in juddi ------------------------- Key: JBESB-358 URL: http://jira.jboss.com/jira/browse/JBESB-358 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 CR2 Reporter: Kevin Conner Assigned To: Mark Little The following isses need to be tracked in the juddi codebase (copied from email) There appear to be two juddi problems. - juddi is asking for the wrong resource, "/juddi.properties" instead of "juddi.properties". - juddi reinitialises every time it is called :-( The first issue explains why many people have been having problems with the QS IFF they have been deployed before starting the AS. This does not fail, however, if you deploy the empty jbossesb.xml first. The reason for this is that GatewayListenerControllerService overrides the juddi.propertiesFile to the absolute location of the config file, which it does not have the opportunity to do if there are listeners configured :-) The change that Kurt put in place yesterday will fix this although it should really be made in the juddi codebase. The second juddi issue results in an access to the config file, along with recreation of the registry engine, on every invocation. This is annoying, and a performance drag, but does not affect functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira