Warning: file_get_contents(/data/phpspider/zhask/data//catemap/0/xml/14.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Webcommerce中wc-rest-dispatcher.xml的含义_Xml_Rest_Websphere Commerce - Fatal编程技术网

Webcommerce中wc-rest-dispatcher.xml的含义

Webcommerce中wc-rest-dispatcher.xml的含义,xml,rest,websphere-commerce,Xml,Rest,Websphere Commerce,在一个Websphere commerce项目中,我在com.ibm.commerce.rest文件夹中找到了一个名为wc-rest-dispatcher.xml的文件来处理rest调用。 它似乎不是一个自定义文件。但是,在HCL的文档中搜索时,我找不到该文件的任何引用 有人知道此文件的用途吗?此文件用于将与搜索相关的请求转发到v8中的搜索服务器,但不确定是否仍适用于v9或更高版本。 文件的版权部分有基本文档 This XML defines routing services related c

在一个Websphere commerce项目中,我在com.ibm.commerce.rest文件夹中找到了一个名为wc-rest-dispatcher.xml的文件来处理rest调用。 它似乎不是一个自定义文件。但是,在HCL的文档中搜索时,我找不到该文件的任何引用


有人知道此文件的用途吗?

此文件用于将与搜索相关的请求转发到v8中的搜索服务器,但不确定是否仍适用于v9或更高版本。 文件的版权部分有基本文档

This XML defines routing services related configuration data for REST services.
    
    remoteServerReference: WAS configured name binding for the URL to connect to the remote server.  For example,
                           server or cluster scope: com.ibm.commerce.foundation.server.services.search.url
                           cell scope: cell/persistent/com.ibm.commerce.foundation.server.services.search.url
    forwardHeader: defines whether to include the inbound http header in the outbound request; defaults to true
    forwardQueryString: defines whether to include the inbound query string in the outbound request; defaults to true
    
    inbound: the URI pattern of the inbound request; if matches, the outbound request will be issued instead
    outbound: can be a URI or a fully qualified URL for the outbound request for redirect
    
    Note: - variables can be used in inbound and outbound field - variables at runtime will be transferred "as is"
            to the outbound URI.
          - variables must be enclosed with curly brackets {}.