Hide Forgot
Date of First Response: 2009-12-04 07:50:28 project_key: SOA Change the location of juddi-core-x.y.z.aop.jar to ${server.config}/lib please. When configuring jUDDI client to use RMI then the server is unable to find JUDDIAuthenticator class: 13:36:53,119 ERROR [AuthenticatorFactory] The specified Authenticator class 'org.apache.juddi.v3.auth.JUDDIAuthenticator' was not found in classpath. 13:36:53,119 ERROR [AuthenticatorFactory] java.lang.ClassNotFoundException: org.apache.juddi.v3.auth.JUDDIAuthenticator For more information see linked issue.
Not possible, juddi-core must be scoped which is why it is in the current location.
This is a bug in the juddi AuthenticatorFactory class, which is also in juddi-core. The location of this jar is not the issue.
Create a JBESB issue, citing the AuthenticatoryFactory issue, and I will work around it.
Link: Added: This issue depends JBESB-3024
Fixed in the project, will be in the next merge.
Blocked Tests: Added: Since juddi-core must be scoped I am unable to get around the ClassNotFoundException, thus I am unable to configure juddi client to use RMI to connect to another instance of juddi (e.g. shared registry scenario) Affects Testing: Added: [Blocks Testing]
Sorry, was the change for 'Blocked Tests' just house keeping or is this still an issue?
Verified on ER6