| Summary: | riftsaw needs uddi clerk configured in jbossesb.sar/esb.juddi.client.xml to register EPRs into uddi registry | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Sedlacek <jsedlace> | ||||
| Component: | riftsaw | Assignee: | Julian Coleman <jcoleman> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 5.1.0.dev2 | CC: | jsedlace, kevin.conner, oskutka | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.1.0 GA, 5.1.0.ER6 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-2238 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-01-12 13:13:55 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: | |||||
| Attachments: |
|
||||||
|
Description
Jiri Sedlacek
2010-08-25 12:49:11 UTC
It's probably not a bug, but a configuration issue. In Riftsaw user guide, there is written, that registering processes in uddi registry can be enabled in riftsaw configuration file. Juddi client, which is used by riftsaw for comunication with registry, by default uses configuration in jbossesb.sar/esb.juddi.client.xml (the file can be specified in riftsaw config file) and configuration in jbossesb.sar/esb.juddi.client.xml does not contain setup for uddi clerk, which is needed for riftsaw to register and lookup endpoints in registry. The configuration change should be done as part of the SOA build process. need to ensure "deploy.esb.uddi.config" target in the RiftSaw installer is run and handle any resulting ESB/RiftSaw inconsistencies (i.e, use "uddi-portlet-manager" everywhere instead of "esb-registry"). Resolveded with revision 6901 of: build-tools/builders/riftsaw/build.xml build-tools/builders/riftsaw/pom.xml Commit message: SOA-2238 Use a fake installation root so that the extra RiftSaw configuration changes can be picked up in the SOA build. As far as I can see in bits we've got, there is no clerk configured in soa-p.5.1.0.ER3 uddi clerk for riftsaw is still not configured in ER5 There are a number of files that are overlayed by the riftsaw installation, however not all are applied to the SOA build. We need to cleanly separate the riftsaw configuration from the esb configuration and have the SOA build handle any specific merging on behalf of both projects. The following overlays separate the riftsaw configuration from the ESB configuration, with only one file now requiring modifications as part of the build (esb.juddi.client.xml). Will ask Kurt to look over the changes. Attachment: Added: updated.zip Kurt has checked the changes and can see no issues, will reassign to Julian after Jiri also agrees. Verified and it's working. Triaged Dec 7 as a blocker. Resolved with revision 7631 of: build-tools/builders/riftsaw/post-patch/patch_esb_files.xml build-tools/builders/riftsaw/resource/riftsaw_tModels.xml build-tools/builders/riftsaw/resource/riftsaw_BusinessEntity.xml build-tools/builders/riftsaw/resource/patch_esb_juddi_client.xsl build-tools/builders/riftsaw/resource/riftsaw_Publisher.xml build-tools/builders/riftsaw/build.xml Commit message: SOA-2238 SOA-2655 Remove ESB files from RiftSaw install. Add files from SOA-2238 to configure jUDDI for RiftSaw. Patch esb.juddi.client.xml for RiftSaw. Labels: Added: rn-not-needed Release Notes Docs Status: Added: Not Required Writer: Added: dlesage verified in 5.1.0.ER6 |