++ This bug is a clone of bug 779436 ++

Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2010-02-21 23:11:46
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=382098&gid=1354
project_key: SOA

SOA-P 4.3.0_CP02
http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/Services_Guide/index.html#chap-SOA_ESB_Services_Guide-What_is_the_Registry

AND

SOA-P 5 Beta
http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.0-Beta1/html-single/Services_Guide/index.html#sect-What_is_the_Registry

We try to address the registry/repository differences in section 1.1.1.3  here.  
"A registry allows one to register of services, discover meta-data and classify entities into pre-defined categories. Unlike a repository, it does not have the ability to store business process definitions or WSDLs or any other documents that are required for trade agreements. A registry is essentially a catalogue of items, whereas a repository is a storage area that actually contains those items."

But, by saying that we contradict what we said in 1.1.1.1:  
"A service registry will hold meta-data entries for all of the artifacts within the SOA-P that are used at both run-time and design time. Items inside a service registry may include service description artifacts such as WSDLs, Service Policy descriptions, various Extensible Mark-Up Language (XML) schema used by services, artifacts representing different versions of services, governance and security artifacts (such as certificates and audit trail data) and so forth."

Do registries store WSDLs or not?

Think we need to make this section a bit more consistent.  Maybe I'm just mis-reading it?

This is reported by a solutions architect in the case attached