Bug 779594 (SOA-1964) - jUDDI does not register all services received in GetSubscriptionResult.
Summary: jUDDI does not register all services received in GetSubscriptionResult.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1964
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Kurt Stam
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
: SOA-1986 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-26 13:39 UTC by Marek Baluch
Modified: 2011-02-11 06:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
jUDDI v 3.0.1
Last Closed: 2011-02-11 06:07:46 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1964 0 None None None Never

Description Marek Baluch 2010-02-26 13:39:01 UTC 
project_key: SOA

This issue depends on https://issues.apache.org/jira/browse/JUDDI-370.
Comment 1 Marek Baluch 2010-03-12 07:57:22 UTC 
Link: Added: This issue is a dependency of SOA-1986
Comment 2 Marek Baluch 2010-03-12 07:57:43 UTC 
Link: Removed: This issue is a dependency of SOA-1986
Comment 3 Marek Baluch 2010-03-12 07:58:02 UTC 
Link: Added: This issue is duplicated by SOA-1986
Comment 4 Kurt Stam 2010-10-01 16:47:00 UTC 
Actually this is resolved in jUDDI 3.0.2 and newer. Can we mark as resolved here?
Comment 5 Marek Baluch 2010-12-09 09:30:59 UTC 
Verified on SOA-P ER5.
Comment 6 David Le Sage 2011-02-11 06:06:07 UTC 
Temporarily reopening to update release note info.
Comment 7 David Le Sage 2011-02-11 06:07:31 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-1964

jUDDI was failing to register some of the services received via GetSubscriptionResult. This has been fixed by an upgrade of jUDDI to version 3.0.2.
Note You need to log in before you can comment on or make changes to this bug.