Hello,
while going through the steps details in the ADT SDK tutorial, I noticed some unexpected workspace entries in the results returned by my own discovery application (/mycompany/discovery in the tutorial):
<app:workspace>
<atom:title>Enterprise Services</atom:title>
<app:collection href="/sap/bc/esproxy/semanticcontracts">
<atom:title>Semantic Contract</atom:title>
<atom:category term="SemanticContract" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/contracts">
<atom:title>Contract</atom:title>
<atom:category term="Contract" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/contractimplementations">
<atom:title>Contract Implementation</atom:title>
<atom:category term="ContractImplementation" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/integrationscenariodefns">
<atom:title>Integration Scenario Definition</atom:title>
<atom:category term="IntegrationScenarioDefinition" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/datatypes">
<atom:title>Proxy Data Type</atom:title>
<atom:category term="ProxyDataType" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/messagetypes">
<atom:title>Proxy Message Type</atom:title>
<atom:category term="ProxyMessageType" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/serviceconsumers">
<atom:title>Service Consumer</atom:title>
<atom:category term="ServiceConsumer" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/serviceproviders">
<atom:title>Service Provider</atom:title>
<atom:category term="ServiceProvider" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/operationmappings">
<atom:title>Operation Mapping</atom:title>
<atom:category term="OperationMapping" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/consumermappings">
<atom:title>Consumer Mapping</atom:title>
<atom:category term="ConsumerMapping" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/consumerfactories">
<atom:title>Consumer Factory</atom:title>
<atom:category term="ConsumerFactory" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/search">
<atom:title>Proxy Generic Search</atom:title>
<atom:category term="ProxyGenericSearch" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/proxysearch">
<atom:title>Proxy Specific Browse Search</atom:title>
<atom:category term="ProxySpecificBrowseSearch" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/validate">
<atom:title>Validate Proxy Name</atom:title>
<atom:category term="ValidateProxyName" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/soamanager">
<atom:title>SOA Manager</atom:title>
<atom:category term="SoaManager" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/esrsearch">
<atom:title>Enterprise Services Repository Search</atom:title>
<atom:category term="EsrSearch" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/esrscv">
<atom:title>ESR SCV Search</atom:title>
<atom:category term="EsrScvSearch" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/srsearch">
<atom:title>Services Registry Search</atom:title>
<atom:category term="SrSearch" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
<app:collection href="/sap/bc/esproxy/activation">
<atom:title>Proxy Activation</atom:title>
<atom:category term="ProxyActivation" scheme="http://www.sap.com/adt/categories/enterpriseservices"/>
</app:collection>
</app:workspace>
<app:workspace>
<atom:title>InfoProvider</atom:title>
</app:workspace>
<app:workspace>
<atom:title>Composite Provider</atom:title>
</app:workspace>
I suppose these entries appear because in the following Enhancement Implementations, the BAdI implementation does not have a filter value assigned:
Enhancement Implementation | BAdI Implementation |
---|
EI_MTS_PROXY_RES_APPLICATION | SMTS_ADT_REST_REF_APP_DISCOVER |
RSO_RES_IPROV_DISCOVERY | RSO_RES_IPROV_DISCOVERY |
RS_RSO_RES_HCPR_RESOURCE_APP | RS_RSO_RES_HCPR_DISCOVERY |
Is my assumption correct, and if so, will this be corrected or will I just have to filter out these values on the client side?
Thanks
Volker Wegert