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
- 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.