blocks|key|737079|text|WSO2+API管理器向发布和订阅等操作公开了REST+API。您可以在此处看到所有服务的列表：https://docs.wso2.com/display/AM200/Published%2BAPIs。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|737080|它还为这些API提供了Swagger定义文件：https://raw.githubusercontent.com/wso2/carbon-apimgt/v6.0.4/components/apimgt/org.wso2.carbon.apimgt.rest.api.publisher/src/main/resources/publisher-api.yaml。|737081|我还没有尝试过，但是考虑到在WSO2中发布托管应用编程接口所需要的只是一个Swagger文件和一个现有的端点，没有什么可以阻止您在WSO2内部创建一个API。|737082|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.wso2.com/display/AM200/Published%2BAPIs|1|https://raw.githubusercontent.com/wso2/carbon-apimgt/v6.0.4/components/apimgt/org.wso2.carbon.apimgt.rest.api.publisher/src/main/resources/publisher-api.yaml^0|1C|1E|0|0|N|4D|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

WSO2 API Manager exposes a REST API to for operations like publish and subscribe. You can see the list of all the services here: <a href="https://docs.wso2.com/display/AM200/Published+APIs" rel="nofollow noreferrer">https://docs.wso2.com/display/AM200/Published+APIs</a>.

It also offers Swagger definition files for those same APIs: <a href="https://raw.githubusercontent.com/wso2/carbon-apimgt/v6.0.4/components/apimgt/org.wso2.carbon.apimgt.rest.api.publisher/src/main/resources/publisher-api.yaml" rel="nofollow noreferrer">https://raw.githubusercontent.com/wso2/carbon-apimgt/v6.0.4/components/apimgt/org.wso2.carbon.apimgt.rest.api.publisher/src/main/resources/publisher-api.yaml</a>. 

I haven't tried it, but given the fact that all you need to publish a managed API in WSO2 is a Swagger file and an existing endpoint, there is nothing preventing you to create an API for WSO2 APIM inside itself.

blocks|key|737106|text|理论上，这应该没问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|737107|WSO2应用程序接口管理器为其自己的API充当中间件角色，就像对任何其他第三方API一样。|737108|假设您想要通过api管理器本身发布api管理器的任何Admin+api。您只需添加端点信息，就像对任何其他api所做的那样。然后，一旦用户想要访问api，他们必须首先通过调用令牌端点来获取访问令牌，然后使用该令牌来执行发布的api。|737109|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Theoretically, this should be fine. 

WSO2 API manger plays the middleware role for its own APIs just as for any other third party API.

Let's say that you want to publish any of the Admin APIs of the api manager through the api manager itself. You just need to add endpoint information just as you would do for any other api.
Then, once a user wants to access the api, they have to first get a access token by calling the token endpoint, then use that token to execute the published api.

blocks|key|969937|text|访问你的应用程序接口管理器：http://localhost:9443/publisher|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|969938|969939|单击您的|unordered-list-item|969940|在"Publish"|969941|上单击选项卡"Lifecycle"|969942|Click|969943|969944|entityMap|0|LINK|mutability|MUTABLE|url|http://localhost:9443/publisher^0|E|V|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|-4|5|6|7|10|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|11|8|@]|9|@]|C|$]]|$1|H|3|I|5|G|7|12|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@]|C|$]]|$1|L|3|M|5|G|7|14|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Access you API-Manager on: <a href="http://localhost:9443/publisher" rel="nofollow noreferrer">http://localhost:9443/publisher</a>

<ul>
<li>Click on your api</li>
<li>Click on tab "Lifecycle"</li>
<li>Click on "Publish"</li>
</ul>

blocks|key|737204|text|WS02+API是指Wso2+API管理器吗？因为您也可以使用Wso2企业服务总线来实现API。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|737205|您可以使用APIM对Wso2的代码进行更多的控制，但是您不能使用ESB进行节流和其他控制，必须使用APIM。|737206|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

WS02 API means are you referring to Wso2 API manager?
Because you can also implement API's using Wso2 ESB.

You can have more control over the code of API using Wso2 ESB but you cannot have throttling and other control using ESB you have to use APIM.

blocks|key|737286|text|你应该有一个端点来连接你的API。然后按照以下步骤操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|737287|在你的应用程序接口管理器(发布者)和新的API|737288|If中登录你有一个端点:点击Design+a+new+Rest+API|unordered-list-item|737289|
|737290|Fill+description.|737291|737292|Add+a+new+|737293|description.|ordered-list-item|737294|Add+a+new+API+Specification等值。(即:获取类型)REST+API单击Next:Implement|737295|Select+API+Managed+API|737296|Endpoint类型:+HTTP/REST+Endpoint|737297|Endpoint:在没有context.|737298|Click+on的情况下填充端点的url+Next:+Manage+subscription.|737299|If+/test填充值如类型of+|737300|如果您有一个公共|737301|，不要忘记更改规范资源的第二列。更改的值:None|offset|length|style|BOLD|737302|单击保存并发布|737303|转到WSO2商店并选中|737304|737305|737306|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|7|I|0|0|7|0|0|B|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1K|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1L|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1M|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|1N|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|1O|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1P|8|@]|9|@]|A|$]]|$1|Q|3|R|5|P|7|1Q|8|@]|9|@]|A|$]]|$1|S|3|T|5|P|7|1R|8|@]|9|@]|A|$]]|$1|U|3|V|5|P|7|1S|8|@]|9|@]|A|$]]|$1|W|3|X|5|P|7|1T|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|P|7|1U|8|@]|9|@]|A|$]]|$1|10|3|11|5|P|7|1V|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1W|8|@]|9|@]|A|$]]|$1|14|3|15|5|P|7|1X|8|@$16|1Y|17|1Z|18|19]]|9|@]|A|$]]|$1|1A|3|1B|5|P|7|20|8|@$16|21|17|22|18|19]]|9|@]|A|$]]|$1|1C|3|1D|5|P|7|23|8|@$16|24|17|25|18|19]]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|1F|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|28|8|@]|9|@]|A|$]]]|1H|$]]

You shoould have an endpoint to connect your API.
Then follow the below steps

<ol>
<li>Login in your API Manager (Publisher) Instance.</li>
<li>+ Add new API</li>
<li>If you have an endpoint: Click on Design a new Rest API</li>
<li>Fill the values like name, context, version and description.</li>
<li>Add a new API Specification. (i.e: GET /test)</li>
<li>Click on Next:Implement</li>
<li>Select Managed API</li>
<li>Endpoint Type: HTTP/REST Endpoint</li>
<li>Endpoint: Fill your endpoint's url without context.</li>
<li>Click on Next: Manage</li>
<li>Fill values like type of subscription.</li>
<li>If you have a public API, don't forget change the second column of your API specification resources. Change the value for: None</li>
<li>Click on Save &amp; Publish</li>
<li>Go to WSO2 Store and check</li>
</ol>

blocks|key|3053263|text|在浏览您提供的答案和回复时，我相信您知道如何将WSO2应用程序接口作为端点发布。然而，您关心的是如何处理授权，因为后端本身需要一个有效的OAuth令牌来调用？如果我的理解有误，请纠正我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3053264|如果是这样，我相信您可以在自定义中介的帮助下简单地实现它。下面的示例中介将调用令牌端点并生成令牌。生成令牌后，您可以简单地将其添加到请求头。|3053265|<?xml+version="1.0"+encoding="UTF-8"?>
<sequence+name="simple-token-gen"+trace="disable"+xmlns="http://ws.apache.org/ns/synapse">
++++<property+description="access_token"+expression="get-property('registry',+'local:/api-backend-credentials/pizzaOrderingAPI/access_Token')"+name="access_token"+scope="default"+type="STRING"/>
++++<property+description="generated_time"+expression="get-property('registry','local:/api-backend-credentials/pizzaOrderingAPI/generated_Time')"+name="generated-time"+scope="default"+type="LONG"/>
++++<property+description="client_credentials"+name="app-client-auth"+scope="default"+type="STRING"+value="{base64encoded(clientKey:clientSecret)}"/>
++++<property+expression="json-eval($)"+name="message-body"+scope="default"+type="STRING"/>
++++<property+expression="get-property('axis2','REST_URL_POSTFIX')"+name="resource"+scope="default"+type="STRING"/>
++++<filter+description=""+xpath="get-property('SYSTEM_TIME')+-+get-property('generated-time')+>+3600000+or+get-property('access_token')+=+''">
++++++++<then>
++++++++++++<payloadFactory+media-type="xml">
++++++++++++++++<format>
++++++++++++++++++++<soapenv:Envelope+xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
++++++++++++++++++++++++<soapenv:Body>
++++++++++++++++++++++++++++<root+xmlns="">
++++++++++++++++++++++++++++++++<grant_type>client_credentials</grant_type>
++++++++++++++++++++++++++++</root>
++++++++++++++++++++++++</soapenv:Body>
++++++++++++++++++++</soapenv:Envelope>
++++++++++++++++</format>
++++++++++++++++<args/>
++++++++++++</payloadFactory>
++++++++++++<header+expression="fn:concat('Basic+',+get-property('app-client-auth'))"+name="Authorization"+scope="transport"/>
++++++++++++<header+name="Content-Type"+scope="transport"+value="application/x-www-form-urlencoded"/>
++++++++++++<property+description="messageType"+name="messageType"+scope="axis2"+type="STRING"+value="application/x-www-form-urlencoded"/>
++++++++++++<property+description="REST_URL_POSTFIx"+name="REST_URL_POSTFIX"+scope="axis2"+type="STRING"+value=""/>
++++++++++++<call+blocking="true">
++++++++++++++++<endpoint+name="token">
++++++++++++++++++++<http+method="post"+uri-template="{token-endpoint-url}"/>
++++++++++++++++</endpoint>
++++++++++++</call>
++++++++++++<property+expression="get-property('resource')"+name="REST_URL_POSTFIX"+scope="axis2"+type="STRING"/>
++++++++++++<property+description="generated+Time+Setter"+expression="get-property('SYSTEM_TIME')"+name="local:/api-backend-credentials/pizzaOrderingAPI/generated_Time"+scope="registry"+type="LONG"/>
++++++++++++<property+description="generated_token"+expression="json-eval($.access_token)"+name="generated-access-token"+scope="default"+type="STRING"/>
++++++++++++<property+description="new+Token+setter"+expression="get-property('generated-access-token')"+name="local:/api-backend-credentials/pizzaOrderingAPI/access_Token"+scope="registry"+type="STRING"/>
++++++++++++<header+expression="fn:concat('Bearer+',+get-property('generated-access-token'))"+name="Authorization"+scope="transport"/>
++++++++++++<payloadFactory+media-type="json">
++++++++++++++++<format>
++++++++++++++++++++$1
++++++++++++++++</format>
++++++++++++++++<args>
++++++++++++++++++++<arg+evaluator="xml"+expression="get-property('message-body')"/>
++++++++++++++++</args>
++++++++++++</payloadFactory>
++++++++</then>
++++++++<else>
++++++++++++<header+expression="fn:concat('Bearer+',+get-property('access_token'))"+name="Authorization"+scope="transport"/>
++++++++</else>
++++</filter>
</sequence>|code-block|syntax|javascript|3053266|将占位符替换为相应的值。|3053267|3053268|{base64encoded(clientKey:clientSecret)}+-客户端密钥和客户端机密，由冒号和base64编码分隔。后端授权服务器的{token-endpoint-url}|unordered-list-item|3053269|The令牌终结点URL。|3053270|3053271|我相信这会帮助你解决你的问题。|3053272|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Y|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|N|7|11|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|13|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|U|$]]

While going through the answers and the replies that you have provided, I believe you know how to publish an API with a WSO2 API as an endpoint. However, your concern is how to handle the authorization since the backend itself needs a valid OAuth token to be invoked? Please correct me if my understanding is wrong.
If that is the case, I believe you can simply achieve it with a help of a custom mediation. The below sample mediation is to invoke the token endpoint and generate a token. Once the token is generated you can simply add that to the request header.
<pre><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;sequence name=&quot;simple-token-gen&quot; trace=&quot;disable&quot; xmlns=&quot;http://ws.apache.org/ns/synapse&quot;&gt;
 &lt;property description=&quot;access_token&quot; expression=&quot;get-property('registry', 'local:/api-backend-credentials/pizzaOrderingAPI/access_Token')&quot; name=&quot;access_token&quot; scope=&quot;default&quot; type=&quot;STRING&quot;/&gt;
 &lt;property description=&quot;generated_time&quot; expression=&quot;get-property('registry','local:/api-backend-credentials/pizzaOrderingAPI/generated_Time')&quot; name=&quot;generated-time&quot; scope=&quot;default&quot; type=&quot;LONG&quot;/&gt;
 &lt;property description=&quot;client_credentials&quot; name=&quot;app-client-auth&quot; scope=&quot;default&quot; type=&quot;STRING&quot; value=&quot;{base64encoded(clientKey:clientSecret)}&quot;/&gt;
 &lt;property expression=&quot;json-eval($)&quot; name=&quot;message-body&quot; scope=&quot;default&quot; type=&quot;STRING&quot;/&gt;
 &lt;property expression=&quot;get-property('axis2','REST_URL_POSTFIX')&quot; name=&quot;resource&quot; scope=&quot;default&quot; type=&quot;STRING&quot;/&gt;
 &lt;filter description=&quot;&quot; xpath=&quot;get-property('SYSTEM_TIME') - get-property('generated-time') &gt; 3600000 or get-property('access_token') = ''&quot;&gt;
 &lt;then&gt;
 &lt;payloadFactory media-type=&quot;xml&quot;&gt;
 &lt;format&gt;
 &lt;soapenv:Envelope xmlns:soapenv=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;&gt;
 &lt;soapenv:Body&gt;
 &lt;root xmlns=&quot;&quot;&gt;
 &lt;grant_type&gt;client_credentials&lt;/grant_type&gt;
 &lt;/root&gt;
 &lt;/soapenv:Body&gt;
 &lt;/soapenv:Envelope&gt;
 &lt;/format&gt;
 &lt;args/&gt;
 &lt;/payloadFactory&gt;
 &lt;header expression=&quot;fn:concat('Basic ', get-property('app-client-auth'))&quot; name=&quot;Authorization&quot; scope=&quot;transport&quot;/&gt;
 &lt;header name=&quot;Content-Type&quot; scope=&quot;transport&quot; value=&quot;application/x-www-form-urlencoded&quot;/&gt;
 &lt;property description=&quot;messageType&quot; name=&quot;messageType&quot; scope=&quot;axis2&quot; type=&quot;STRING&quot; value=&quot;application/x-www-form-urlencoded&quot;/&gt;
 &lt;property description=&quot;REST_URL_POSTFIx&quot; name=&quot;REST_URL_POSTFIX&quot; scope=&quot;axis2&quot; type=&quot;STRING&quot; value=&quot;&quot;/&gt;
 &lt;call blocking=&quot;true&quot;&gt;
 &lt;endpoint name=&quot;token&quot;&gt;
 &lt;http method=&quot;post&quot; uri-template=&quot;{token-endpoint-url}&quot;/&gt;
 &lt;/endpoint&gt;
 &lt;/call&gt;
 &lt;property expression=&quot;get-property('resource')&quot; name=&quot;REST_URL_POSTFIX&quot; scope=&quot;axis2&quot; type=&quot;STRING&quot;/&gt;
 &lt;property description=&quot;generated Time Setter&quot; expression=&quot;get-property('SYSTEM_TIME')&quot; name=&quot;local:/api-backend-credentials/pizzaOrderingAPI/generated_Time&quot; scope=&quot;registry&quot; type=&quot;LONG&quot;/&gt;
 &lt;property description=&quot;generated_token&quot; expression=&quot;json-eval($.access_token)&quot; name=&quot;generated-access-token&quot; scope=&quot;default&quot; type=&quot;STRING&quot;/&gt;
 &lt;property description=&quot;new Token setter&quot; expression=&quot;get-property('generated-access-token')&quot; name=&quot;local:/api-backend-credentials/pizzaOrderingAPI/access_Token&quot; scope=&quot;registry&quot; type=&quot;STRING&quot;/&gt;
 &lt;header expression=&quot;fn:concat('Bearer ', get-property('generated-access-token'))&quot; name=&quot;Authorization&quot; scope=&quot;transport&quot;/&gt;
 &lt;payloadFactory media-type=&quot;json&quot;&gt;
 &lt;format&gt;
 $1
 &lt;/format&gt;
 &lt;args&gt;
 &lt;arg evaluator=&quot;xml&quot; expression=&quot;get-property('message-body')&quot;/&gt;
 &lt;/args&gt;
 &lt;/payloadFactory&gt;
 &lt;/then&gt;
 &lt;else&gt;
 &lt;header expression=&quot;fn:concat('Bearer ', get-property('access_token'))&quot; name=&quot;Authorization&quot; scope=&quot;transport&quot;/&gt;
 &lt;/else&gt;
 &lt;/filter&gt;
&lt;/sequence&gt;
</code></pre>
Replace the placeholders with corresponding values.
<ul>
<li>{base64encoded(clientKey:clientSecret)} - The client key and client
secret, separated by a colon and base64 encoded. {token-endpoint-url}</li>
<li>The token endpoint URL of the backend authorization server.</li>
</ul>
I believe this helps you with your concern.

blocks|key|963862|text|如果我理解正确的话，在API管理器中发布WSO2+AM+API是没有意义的。第一个原因是，WSO2+AM+API是通过基本身份验证访问的，默认情况下在WSO2+AM中不会实施它API+en+WSO2的默认安全性是OAuth2，因此您必须为此做一个扩展。你可以在这里查看：https://docs.wso2.com/display/AM260/apidocs/publisher/#guide|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|963863|此外，这些用于WSO2+AM的内部API旨在由管理员或其他管理员访问，因此将这些API公开为供其他用户使用的API是没有意义的。|963864|无论如何，如果您实现了一个以基本身份验证运行的验证器，则可以在API+Manager中公开此API，或者公开这些禁用默认OAuth2安全性的API。|963865|BR|963866|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.wso2.com/display/AM260/apidocs/publisher/#guide^0|3R|1O|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

If I understood correctly, It has no sense to publish WSO2 AM APIs in the API Manager. First reason is that WSO2 AM APIs are accesed by Basic Auth, that it is not implemented by default in WSO2 AM. The default security for APIs en WSO2 is OAuth2, so you would have to do a extension for that. You may check here: <a href="https://docs.wso2.com/display/AM260/apidocs/publisher/#guide" rel="nofollow noreferrer">https://docs.wso2.com/display/AM260/apidocs/publisher/#guide</a>

Also, these internal APIs for WSO2 AM are meant to be accesed by an admin or so, so it has no sense to expose these as an API to be consumed for other suscriptors.

Anyway, if you implemented an authenticator to run with Basic Auth, you may expose this APIs in API Manager, or expose these APIs disabling default OAuth2 security.

BR

I have a special requirement.
I want to access WSO2 backen API.
So,I want to publish it on WSO2.
So that,my service can access WSO2'API.
Can someone tell me how to do it?

How to publish WSO2 API on WSO2?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个特殊的要求。我想访问WSO2 backen API。所以，我想把它发布到WSO2上。这样，我服务就可以访问WSO2的API。有人能告诉我怎么做吗？

问如何在WSO2上发布WSO2接口？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在WSO2上发布WSO2接口？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在WSO2上发布WSO2接口？
EN