Bug 779283 (SOA-1671)

Summary: jUDDI AuthenticatorFactory fails to correctly resolve the implementation.
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Marek Baluch <mbaluch>
Component: Deployment, jUDDI - within SOAAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0.0 ER4Keywords: TestBlocker
Target Milestone: ---   
Target Release: 5.0.0 GA, 5.0.0 ER6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1671
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-21 13:23:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marek Baluch 2009-12-04 12:40:35 UTC
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.

Comment 1 Kevin Conner 2009-12-04 12:50:28 UTC
Not possible, juddi-core must be scoped which is why it is in the current location.

Comment 2 Kevin Conner 2009-12-04 13:03:54 UTC
This is a bug in the juddi AuthenticatorFactory class, which is also in juddi-core.  The location of this jar is not the issue.

Comment 3 Kevin Conner 2009-12-04 13:04:33 UTC
Create a JBESB issue, citing the AuthenticatoryFactory issue, and I will work around it.

Comment 4 Marek Baluch 2009-12-04 13:36:09 UTC
Link: Added: This issue depends JBESB-3024


Comment 5 Kevin Conner 2009-12-06 06:32:43 UTC
Fixed in the project, will be in the next merge.

Comment 6 Marek Baluch 2009-12-16 13:49:35 UTC
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]


Comment 7 Kevin Conner 2009-12-16 14:04:25 UTC
Sorry, was the change for 'Blocked Tests' just house keeping or is this still an issue?

Comment 8 Marek Baluch 2009-12-21 13:23:51 UTC
Verified on ER6