| Summary: | confusing jUDDI documentation in Services Guide | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Dana Mison <dmison> |
| Component: | Documentation | Assignee: | Len DiMaggio <ldimaggi> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3 GA, 4.2 CP02 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.3 CP02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1107 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-09-21 17:40:12 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: | |
| Bug Depends On: | 777826 | ||
| Bug Blocks: | |||
|
Description
Dana Mison
2009-01-05 06:57:06 UTC
From the first part, juddi.war is included in the ESB server and is included within jbossesb.sar, and the datasource is preconfigured. I think we can remove that paragraph. Ultimately, we have a conflict between the juddi provided by juddi-service.sar and jbossesb, so we need to do something about it (https://jira.jboss.org/jira/browse/SOA-353) updated jUDDI-registry directory to point to jbossesb.sar/ removed reference to MySQL example rewrote slightly to make it clearer. note: juddi-server.sar is no longer included. Link: Added: This issue is related to SOA-1398 The text is still unclear The jbossesb.sar registers a RMI service for jUDDI. By default juddi.war only provides webservice access but can be configured to also provide a RMI Service with the following settings in the web.xml. So I do not understand what will happen if both jbossesb.sar and juddi.war is present and RMI service is enabled in war. Is it allowed? Will be there two services? Are those RMI services same? A developer needs to clarify what the intent of this content is Link: Added: This issue depends SOA-353 Is the RMI service registered by jbossesb.sar not really a service, but the MBean that which stops and starts the registry? So - there really is only one RMI service - that being the service in juddi.war that accepts requests? From Tom: My suggestion is to remove the section on providing RMI through the WAR. As Jiri says, RMI services are provided through jbossesb.sar, so while it is technically possible to configure RMI for juddi through the WAR, there's really no reason why you would want to running in SOA-P. As long as the services are registered with the same name, I think they'd be the same, but I think showing users this will be unnecessarily confusing and there's no real reason why a user would want to do this in SOA-P. Assigning back to Darrin to edit the doc - Darrin - can you edit the doc in time for CP02? no promises but its on the list after the JON item I've updated this in section, the pdf has been checked in & you can also look it at at: http://downtown.englab.bne.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/Services_Guide/index.html#sect-SOA_ESB_Services_Guide-Configuring_Examples-RMI_using_the_juddi.war_or_jbossesb.sar I noticed that once this was removed the only remaining reference to juddi.war was in Chapter 4. UDDI Browser. I don't know if that is a problem, we probably should have some content detailing what it is for, how to configure it etc. *need to fix the page anchor names too, they are way too long & in this case, confusing Closing as verified in CR4 1) juddi-service.sar was removed from the distribution in CR3 (SOA-353) 2) The confusing text was removed from the Services Guide 3) I think that we are all set with the references to the uddi browser and juddi.war - with CR4 installed, I was able to download the browser and just run it. |