| Summary: | Riftsaw cannot use hp systinet uddi registry for registering and looking up processes | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Sedlacek <jsedlace> |
| Component: | riftsaw | Assignee: | Len DiMaggio <ldimaggi> |
| Status: | VERIFIED --- | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.0.ER5 | CC: | atangrin, gary.pi4tech, kevin.conner, oskutka, tcunning |
| Target Milestone: | --- | ||
| Target Release: | 5.3.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2677 | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-15 17:07:42 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
Jiri Sedlacek
2010-12-13 14:33:00 UTC
Link: Added: This issue is related to SOA-2671 Link: Added: This issue is related to SOA-2676 This seems to be a consequence of the juddi-client issues, do we need a second issue for this? 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. 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. There is now an alternate transport in the ESB codebase. https://issues.apache.org/jira/browse/JUDDI-439 This is resolved in jUDDI-3.1.0 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. cannot be verified yet due to SOA-3560 Link: Added: This issue relates to SOA-3591 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. 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.
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.
verified that works in soa-p-5.3.0.ER4 |