Bug 780276 (SOA-2677) - Riftsaw cannot use hp systinet uddi registry for registering and looking up processes
Summary: Riftsaw cannot use hp systinet uddi registry for registering and looking up p...
Keywords:
Status: VERIFIED
Alias: SOA-2677
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: riftsaw
Version: 5.1.0.ER5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.3.0 GA
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-13 14:33 UTC by Jiri Sedlacek
Modified: 2021-09-15 11:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The BPEL engine could not use the HP Systinet UDDI registry to register and locate processes. To fix this problem, an alternative JAX-WS transport has been added to the ESB codebase. As a result, users should now be able to use the HP Systinet Registry.
Clone Of:
Environment:
Last Closed: 2011-11-15 17:07:42 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 Bugzilla 780273 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 780275 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 781099 0 urgent VERIFIED Wrong tModelKey for tModel named uddi-org:types 2021-09-15 11:50:35 UTC
Red Hat Issue Tracker SOA-2677 0 Critical Closed Riftsaw cannot use hp systinet uddi registry for registering and looking up processes 2012-11-27 19:27:51 UTC

Internal Links: 780273 780275 781099

Description Jiri Sedlacek 2010-12-13 14:33:00 UTC 
project_key: SOA

It's caused by problem with juddi-client.
Comment 1 Jiri Sedlacek 2010-12-13 14:33:52 UTC 
Link: Added: This issue is related to SOA-2671
Comment 2 Jiri Sedlacek 2010-12-13 14:33:52 UTC 
Link: Added: This issue is related to SOA-2676
Comment 3 Kevin Conner 2010-12-14 09:08:54 UTC 
This seems to be a consequence of the juddi-client issues, do we need a second issue for this?
Comment 4 Gary Brown 2011-01-05 15:17:31 UTC 
Assigning to Kurt, as it is a UDDI issue, although as Kevin suggests it looks like a duplicate of SOA-2671 so could maybe be closed.
Comment 5 Kevin Conner 2011-01-05 15:20:26 UTC 
I am currently writing our own jaxws transport to replace the juddi one, until we can pull in a new version of juddi.  I would suggest holding off until SOA-2671/SOA-2676 are completed.
Comment 6 Kevin Conner 2011-01-06 14:43:20 UTC 
There is now an alternate transport in the ESB codebase.
Comment 7 Kurt Stam 2011-06-10 17:39:47 UTC 
https://issues.apache.org/jira/browse/JUDDI-439

This is resolved in jUDDI-3.1.0
Comment 8 David Le Sage 2011-09-02 06:04:46 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2677

The BPEL engine could not use the HP Systinet UDDI registry to register and locate processes.  To fix this problem, an alternative JAX-WS transport has been added to the ESB codebase.  As a result, users should now be able to use the HP Systinet Registry.
Comment 9 Jiri Sedlacek 2011-11-07 09:48:48 UTC 
cannot be verified yet due to SOA-3560
Comment 10 Jiri Sedlacek 2011-11-16 08:20:32 UTC 
Link: Added: This issue relates to SOA-3591
Comment 11 Jiri Sedlacek 2011-11-16 19:13:54 UTC 
when SOA-3591 will be fixed, can be marked as verified and set to CLOSED.

The needed setup of HP Systinet should be properly documented for customers, Kurt can provide the information what should be added to Systinet.
Comment 12 tcunning 2012-01-31 19:58:32 UTC 
The last two issues that Jiri mentions (SOA-3560 and SOA-3591) appear to be closed.     It'd probably be good to retest and close this.
Comment 13 David Le Sage 2012-07-02 04:57:55 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The BPEL engine could not use the HP Systinet UDDI registry to register and locate processes.  To fix this problem, an alternative JAX-WS transport has been added to the ESB codebase.  As a result, users should now be able to use the HP Systinet Registry.
Comment 14 Jiri Sedlacek 2012-07-13 11:02:17 UTC 
verified that works in soa-p-5.3.0.ER4
Note You need to log in before you can comment on or make changes to this bug.