Q: Why does Membrane Service Registry not support UDDI?
A: Because the UDDI standard is not very popular. UDDI has some flaws e.g. it uses an unflexible objectoriented data model instead of using the ideas of XML and its extensibility.
Q: What is unique at Membrane SOA Registry? A: WSDL and XML schema are not only obscure documents. WSDL and the used schema is parsed and all the information about services, messages and data types is available for browsing in the directory.
Q: Can I use the Membrane SOA Registry software at my company for SOA governance?
A: Yes. Download the registry, double click onn run.bat and start registering services.
Q: What standards are supported?
A: At the moment we support WSDL 1.1, SOAP 1.1 and XML Schema.
Q: Why are you combining Enterprise Web Services technology with Web 2.0 features?
A: Because we think that tags and ratings are helpful even in the enterprise to find useful services.
Q: Does Membrane Service Registry read WSDL and Schema Documentation?
A: Yes. Documentation included in WSDL and Schema documents almost everywhere is read e.g. for the whole WSDL, for portTypes, operations and even for bindings. XML Schema provides the annotation element for the documentation of elements, complex Types, etc.
Q: My Web Service implemented with Apache Axis1 is not accepted at the service registration. What's Wrong?
A: The default message style in Axis1 is RPC/Encoded. The RPC/Encoded style is depricated and not compliant with the WS-I Basic Profile. Therefore we are not supporting RPC/Encoded services. But you can change the encoding of your service by configuration to the Wrapped style. Then Axis1 services are also working.
