standard_003.html

最新推荐文章于 2024-03-02 17:35:13 发布
最新推荐文章于 2024-03-02 17:35:13 发布
阅读量94 收藏
点赞数
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/hexiaojiao/article/details/30486045
版权
<html>
<style>
table{background-image:none;background:#ffffff;font-family:arial,helvetica,sans-serif,kanji2;font-size:10pt;}
.stepHeading,pre{background-color:#ffffff;color:#293d6b;font-family:arial,helvetica,sans-serif,kanji2;font-size:10pt;font-weight:bold;padding-bottom:2px;padding-left:2px;padding-top:2px;text-decoration:none;border-top:1px dotted#cccccc;}
.thed{ border-bottom:windowtext 0.5pt solid;border-left:windowtext;background-color:#33cccc;border-top:windowtext 0.5pt solid;border-right:windowtext 0.5pt solid; }
.tdcontext{ border-bottom:windowtext 0.5pt solid;border-left:windowtext;background-color:transparent;border-top:windowtext;border-right:windowtext 0.5pt solid; }
</style>


<body>
<div>
<h2>Application Layer Checklist </h2>
<pre>
    <span style="color: #009900">[MANDATORY]</span> Only application specific (non-business) functionality is located within the application layer. 
    <span style="color: #009900">[MANDATORY]</span> All logic requirements are decomposed into a number of loosely-coupled, highly-cohesive application services.
    <span style="color: #009900">[MANDATORY]</span> All services within this layer expose a public API which can be called by the presentation layer components or other application services.  
    <span style="color: #009900">[MANDATORY]</span> All service interaction is through well-defined public APIs, and never directly with any service implementation.   
    <span style="color: #009900">[MANDATORY]</span> Services and APIs within this layer are not called from the service, integration or data access layers.  
    <span style="color: #009900">[MANDATORY]</span> Caches, where required, are implemented using the Cache Decorator Pattern.   
    <span style="color: #009900">[MANDATORY]</span> Service implementations within the application layer do not have any dependencies on the presentation layer(s).   
        Note that callback mechanisms may be employed, but the exposed callback API is actually provided by the caller and implemented by the callee.  This ensures that the presentation layer isn't being called directly, and the dependency tree doesn't contain circular references.
</pre>
</div>
<div>
<h2>Data Access Layer (DAL) Checklist</h2>
<pre>
    <span style="color: #009900">[MANDATORY]</span>Only data access services are exposed by the data access layer; only data access requirements is handled by the layer.  
    <span style="color: #009900">[MANDATORY]</span>All data access reuqirements are decomposed into a number of loosely-coupled, highly-cohesive DAOs based on the modelled data sources.  
    <span style="color: #009900">[MANDATORY]</span>All DAOs expose a data access API which is only called by business services in the service layer.  
    <span style="color: #009900">[MANDATORY]</span>All interaction with this layer is through public data access APIs, and not directly with any DAO implementation.  
    <span style="color: #009900">[MANDATORY]</span>DAOs never call application or business services in the layers above, nor does it interact with the integration and presentation layers.  
    <span style="color: #009900">[MANDATORY]</span>Caches, where required, are implemented using the Cache Decorator Pattern.  
</pre>
</div>
<div>
<h2>Integration Layer Checklist</h2>
<pre>
    <span style="color: #009900">[MANDATORY]</span>The integration layer doesn't provide any application or business services; it implements business service APIs only to provide remote access to those services.  
    <span style="color: #009900">[MANDATORY]</span>Integration layer components are never called directly; access is always via a business service API.  
    <span style="color: #009900">[MANDATORY]</span>Integration components are dependenct on service layer APIs, and never on other components or services with the service layer.  
    <span style="color: #009900">[MANDATORY]</span>Integration components do not have any dependencies on either the presentation, application or data access layers.  
    <span style="color: #009900">[MANDATORY]</span>Use of the integration layer must be invisible to the client of the APIs beign adapted by the integration layer.  
    <span style="color: #009900">[MANDATORY]</span>The integration layer is a technical implementation layer, which does not provide any form of application or business logic.  
    <span style="color: #009900">[MANDATORY]</span>Caches, where required, are implemented using the Cache Decorator Pattern in either the application or service layers.  
    <span style="color: #009900">[MANDATORY]</span>(ES) Host Adapter is used for all integration layer implementations.  
</pre>
</div>
<div>
<h2> Presentation Layer Checklist </h2>
<pre>
    <span style="color: #009900">[MANDATORY]</span> The presentation layer does not contain any data processing or business logic.  
    <span style="color: #009900">[MANDATORY]</span> The presentation layer does not directly interact with the integration or data access layers.  
    <span style="color: #009900">[MANDATORY]</span> The presentation layer interacts with services in the application and service layers only.  
    <span style="color: #009900">[MANDATORY]</span> All service interaction is through well-defined public APIs, and never directly with any service implementation.  
    <span style="color: #009900">[MANDATORY]</span> The presentation layer doesn't cache any data returned by the application and/or service layers.  
    <span style="color: #009900">[MANDATORY]</span> Execution Services Request Processing is used to handle all incoming requests.  
    <span style="color: #009900">[MANDATORY]</span> All request processing is undertaken in the context of page-flow.  
    <span style="color: #009900">[MANDATORY]</span> All events follow the event naming standards, including those events returned by processors.  
    <span style="color: #009900">[MANDATORY]</span> All processors are designed such that they undertake only a single atomic unit of work.  
    <span style="color: #009900">[MANDATORY]</span> Processor design uses instance variables to store configuration items only; all processors are stateless and reentrant.  
    <span style="color: #009900">[MANDATORY]</span> Processor design uses only persistent and transient work context, irrespective of the use of page-flow.  
    <span style="color: #009900">[MANDATORY]</span> With the exception of key data within the persistent work context, the presentation layer never caches or stores any other data.  
    <span style="color: #009900">[MANDATORY]</span> The presentation layer's data model(s) never contains invalid data; invalid data provided by the user is caught by the form processing or JHX components.  
    <span style="color: #009900">[MANDATORY]</span> All request processing is separated into two phases: action (request processing) phase, and render (response processing) phase.  
This applies irrespective of the channel.

    <span style="color: #009900">[MANDATORY]</span> The render event mapping configuration must be used to identify the render phase with the overall request processing lifecycle.  
This applies irrespective of the channel.


    <span style="color: #009900">[MANDATORY]</span> Data is supplied to the JSP through one or more form and/or view beans.  
    <span style="color: #009900">[MANDATORY]</span> The JSP is written using the ES JHX components.  
Exception: ES 5.x series applications, or 5-series applications which have subsequently been migrated into ES 6-series, are permitted to use raw HTML, with JTSL and the ES form processing tag libraries.


    <span style="color: #009900">[MANDATORY]</span> All input data is processed, validated and converted into a single form bean using ES JSF integration components.  
Exception: ES 5.x series applications, or 5-series applications which have subsequently been migrated into ES 6-series, are permitted to use ES Form Processing.


    <span style="color: #009900">[MANDATORY]</span> All localization enhancements are supported and implemented providing full localization/bundle support.  
Applications are permitted to provide and implement only a single core langauge (usually English, en_gb or en_us).
    <span style="color: #009900">[MANDATORY]</span> Error handling is undertaken in a common manner, using the published guidelines.  
     <span style="color:#009900">[Recommended]</span> The presentation layer contains only a single front-controller, with some permitted exceptions.  
The only permitted exceptions are where additional front-controllers are being used to support file upload/download and co-existence strategies with different version of the ES framework.


     <span style="color:#009900">[Recommended]</span> The presentation layer's data model(s) resuses object(s) exposed by the application and/or service layers.  
     <span style="color:#009900">[Recommended]</span> Cross-field validation is undertaken by a processor that accepts the field-level validated form bean, undertakes cross-field validation and throws the appropriate exceptions.  
     <span style="color:#cc9900">[Permitted]</span> Cross-field validation is undertaken by implementing the Validatable interface on the form bean.  
Acceptable only where ES form processing is being used; only in ES 5.x series applications, and ES 5.x series code which has subsequently been migrated into ES 6.x.


     <span style="color:#cc9900">[Permitted]</span> Data is supplied to the JSP through one or more form and/or view beans, flattened into an ES view map.  
Permitted only where ES form processing is being used in conjunction with the form processing tag library.
</pre>
</div>
<div>
<h2> Service Layer Checklist </h2>
<pre>
     <span style="color: #009900">[MANDATORY]</span> Only business process (as opposed to application specific or data access) functionality is located within the service layer.  
     <span style="color: #009900">[MANDATORY]</span> All logic requirements are decomposed into a number of loosely-coupled, highly-cohesive business services.  
     <span style="color: #009900">[MANDATORY]</span> All services within this layer expose a public API which can be called by the presentation or application layer components or other business services.  
     <span style="color: #009900">[MANDATORY]</span> All service interaction is through well-defined public APIs, and never directly with any service implementation.  
     <span style="color: #009900">[MANDATORY]</span> Services and APIs within this layer are not called from the integration or data access layers.  
     <span style="color: #009900">[MANDATORY]</span> Caches, where required, are implemented using the Cache Decorator Pattern.  
     <span style="color: #009900">[MANDATORY]</span> Service implementations within the service layer do not have any dependencies on the presentation and application layers.  
Note that callback mechanisms may be employed, but the exposed callback API is actually provided by the business service (caller) and implemented by the callee.  This ensures that the presentation or application layer isn't being called directly, and the dependency tree doesn't contain circular references.
</pre>
</div>
<div>
<table>
<thead><tr class="thed"><th colspan="2">Bloom's Level Cell</th><th>Learner</th><th>Proficient</th><th>Professional</th></tr></thead>
<tr><td>1</td><td>Knowledge</td><td>40%</td><td>30%</td><td>15%</td></tr>
<tr><td>2</td><td>Comprehension</td><td>40%</td><td>25%</td><td>20%</td></tr>
<tr><td>3</td><td>Application</td><td>10%</td><td>25%</td><td>35%</td></tr>
<tr><td>4</td><td>Analysis</td><td>10%</td><td>20%</td><td>30%</td></tr>
<tr><td></td><td>Total</td><td>100%</td><td>100%</td><td>100%</td></tr>
</table>
</div>
<div>
<h3>Notepad++ v6.3 plugin</h3>
<table>
<thead><tr class="thed"><th>Plugin</th><th>URL</th></tr></thead>
<tr><td>AnalysePlugin</td><td>http://analyseplugin.sourceforge.net/</td></tr>
<tr><td>Compare</td><td>http://sourceforge.net/projects/npp-compare/</td></tr>
<tr><td>Customize Toolbar</td><td>http://sourceforge.net/projects/npp-customize/</td></tr>
<tr><td>Explorer</td><td>http://sourceforge.net/projects/npp-explorer/</td></tr>
<tr><td>HTML Tag</td><td>http://sourceforge.net/projects/npp-plugins/files/HTMLTag/</td></tr>
<tr><td>JSLint</td><td>http://sourceforge.net/projects/jslintnpp/</td></tr>
<tr><td>JSMin</td><td>http://sourceforge.net/projects/jsminnpp/</td></tr>
<tr><td>MIME Tools</td><td>http://download.tuxfamily.org/nppplugins/MimeTools/</td></tr>
<tr><td>Converter</td><td>http://download.tuxfamily.org/nppplugins/Converter</td></tr>
<tr><td>NppExport</td><td>http://sourceforge.net/projects/npp-plugins/files/NppExport/</td></tr>
<tr><td>NppFTP</td><td>http://sourceforge.net/projects/nppftp/</td></tr>
<tr><td>Json Viewer</td><td> http://nppjsonviewer.sourceforge.net/</td></tr>
<tr><td>NppJumpList</td><td>http://sourceforge.net/projects/nppjumplist/</td></tr>
<tr><td>Plugin Marker Margin</td><td></td></tr>
<tr><td>Plugin Manager</td><td>http://sourceforge.net/projects/npppluginmgr/</td></tr>
<tr><td>RegRexPlace</td><td>http://f0dder.dcmembers.com/nppplugs/npp_plugins.zip</td></tr>
<tr><td>ReloadButton</td><td>http://www.jhaefner.de/Download/ReloadButton.zip</td></tr>
<tr><td>Spell-Checker</td><td>http://sourceforge.net/projects/npp-plugins/files/Spell-Checker/</td></tr>
<tr><td>Tidy2</td><td>https://code.google.com/p/npp-tidy2/</td></tr>
<tr><td>Xbrackets Lite</td><td>http://sourceforge.net/projects/npp-plugins/files/XBrackets%20Lite/</td></tr>
<tr><td>XML Tools</td><td>http://sourceforge.net/projects/npp-plugins/files/XML%20Tools/</td></tr>
</table>
</div>

<div>
<table width="80%" align="center">
    <tbody>
        <tr><th>Parent POM</th><th>Purpose</th><th>Used By</th></tr>
        <tr><td><tt>esf-app-parent</tt></td><td>Main ES parent POM for all ES development</td><td>All JARs</td></tr>
        <tr><td><tt>esf-app-portlet-parent</tt></td><td>ES parent POM for all portlet web applications</td><td>All portlet WARs</td></tr>
        <tr><td><tt>esf-app-servlet-parent</tt></td><td>ES parent POM for all servlet applications</td><td>All servlet WARs</td></tr>
        <tr><td>esf-app-war-parent</td><td>ES paraent POM for plain J2EE web applications</td><td>All standard WARs</td></tr>
        <tr><td>esf-app-ear-parent</td><td>ES parent POM for all enterprise applications</td><td>All EARs</td></tr>
        <tr><td>esf-app-ejb-parent</td><td>ES parent POM for EJB modules</td><td>All EJB modules</td></tr>
    </tbody>
</table>
<table width="80%" align="center">
<tbody>
<tr><th>Dependency</th><th>Purpose</th><th>Used By</th></tr>
<tr><td><tt>esf-app-core</tt></td><td>Standard ES support, with ES JARs and tracing features</td><td>All JARs and WARs</td></tr>
<tr><td><tt>esf-app-data-service</tt></td><td>Brings in Host Adapter support</td><td>All integration layer JARs</td></tr>
<tr><td><tt>esf-app-remote-service</tt></td><td>Brings in Host Adapter and Remote Service Provider support
</td><td>All remote services</td></tr>
<tr><td><tt>esf-app-portlet</tt></td><td>Brings in web and portlet support</td><td>All portlet WARs</td></tr>
<tr><td><tt>esf-app-servlet</tt></td><td>Brings in web and servlet support</td><td>All servlet WARs</td></tr>
<tr><td><tt>esf-app-web</tt></td><td>Basic ES web support</td><td>&nbsp;</td></tr>
</tbody>
</table>
<table width="80%" align="center">
<tbody>
<tr><th>Component type</th><th>Parent POM</th><th>Dependencies</th></tr>
<tr><td>Java utility JAR</td><td><tt>esf-app-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>Configuration JAR (non-J2EE)</td><td><tt>esf-app-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>ES utility JAR</td><td><tt>esf-app-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>Integration Layer JAR</td><td><tt>esf-app-parent</tt></td><td><tt>esf-app-data-service</tt></td></tr>
<tr><td>Data Access Layer JAR</td><td><tt>esf-app-parent</tt></td><td><tt>esf-app-data-service</tt> if Host Adapter used<br>
no support for ORM and JDBC if used</td></tr>
<tr><td>Service Layer JAR</td><td><tt>esf-app-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>Remote Service API JAR</td><td><tt>esf-app-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>Presentation Layer JAR</td><td><tt>esf-app-parent</tt></td><td><tt>esf-app-portlet</tt> if using portlet APIs<br> <tt>esf-app-servlet</tt>
if using servlet APIs</td></tr>
<tr><td>Configuration and JSR168 portlets WAR</td><td><tt>esf-app-portlet-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>Configuration and Jetspeed portlets WAR</td><td><tt>esf-app-portlet-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>Configuration and servlets WAR</td><td><tt>esf-app-servlet-parent</tt></td><td>&nbsp;</td></tr>
<tr><td>Configuration, JSR168 and servlets WAR</td><td><tt>esf-app-servlet-parent</tt></td><td><tt>esf-app-portlet</tt></td></tr>
<tr><td>Application EAR</td><td><tt>esf-app-ear-parent</tt></td><td>&nbsp;</td></tr>
</tbody>
</table>
</div>


</body>


</html>
乾朗
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
jupyter_notebook_config.py的配置详解
wujunlei1595848的博客
05-15 1万+
# Configuration file for jupyter-notebook. #------------------------------------------------------------------------------ # Application(SingletonConfigurable) configuration #-----------------------...
standard_jstl.jar
01-13
《标准JSTL库——standard_jstl.jar详解》 在Web开发领域，JSTL（JavaServer Pages Standard Tag Library）扮演着至关重要的角色。它为开发者提供了一系列预定义的标签，使得在JSP页面中处理逻辑变得简洁而高效。...
standard_init_linux.go:211: exec user process caused “exec format error“
shy_snow的专栏
08-22 1377
在 amd 和 arm 架构下构建的镜像很有可能不能互通。解决办法：针对不同的硬件架构构建不同的镜像，或者构建跨架构（multi-arch）的镜像。
docker run 失败 在logs中如下错误，standard_init_linux.go:211: exec user process caused “exec format error“
热门推荐
皮先生不皮的博客
09-02 1万+
standard_init_linux.go:211: exec user process caused “exec format error” 简述 此问题是在板件上二次dockerui项目遇到的，板件采用的是arm7l架构。镜像是基于x86_64的centos docker build 出来，之后通过docker save 将此镜像打包成tar文件，再通过docker load 压缩的tar 文件解压成本地镜像。这个镜像转移本身是没有问题，在此之前也进行多次操作。 在docker run的时候显示容器e
standard_init_linux.go:178: exec user process caused "no such file or directory"
weixin_30602505的博客
06-03 1248
golang docker build 制作完进项后运行报错 出现该问题的原因是编译的环境和运行的环境不同，可能有动态库的依赖 １．默认go使用静态链接，在docker的golang环境中默认是使用动态编译。 ２．如果想使用docker编译+alpine部署，可以通过禁用cgoCGO_ENABLED=0来解决。 ３．如果要使用cgo可以通过go build --ldflags "-extl...
Keil 丢失编译器版本5、内核文件core_cm3.c报错
qq_52804040的博客
03-02 2714
若用的是旧版本的core_cm3.c ，就使用编译器v5编译工程；若想用编译器v6，就更新4个相关的内核文件：（CMSIS：Cortex Microcontroller Software Interface Standard，ARM Cortex™ 微控制器软件接口标准）
stm32f4xx_fsmc.c出现很多不正常的error
pugao23的博客
04-21 3196
如果你的stm32单片机是f4系列的，就Remove掉stm32f4xx_fsmc.c这个文件。 如果你stm32单片机不是f4的，而且stm32f4xx_fmc.c文件出现很多错误，可以参考https://wenku.baidu.com/view/554173a064ce0508763231126edb6f1aff00711e.html的第七页。 ...
NEON_2_SSE.h 是个好东西
电声&声学信号处理
12-02 7837
简要介绍 NEON_2_SSE.h 是 Intel 官方在 Github 开源的一份代码，其基于 Intel 自身的 SSE 指令，对 Cortex-A 系列平台上的 NEON浮点加速指令进行了模拟实现，非常有价值，具体有两点如下： 此前基于 Cortex-A 系列用 NEON 指令开发的代码，可以直接无缝切换，在 Windows&Intel 平台运行； 利用 ARM CMSIS DSP 开源代码，可以对普通的浮点代码进行一定程度加速，本文档便针对此进行些许讨论。做几组时延对比，实测性能表现.
ALV的Excel方式显示缺少模板(请和系统管理员联系.缺少下列模板：sap_sm.xls)
王小磊
10-17 3482
转载自：http://blog.sina.com.cn/s/blog_701594f40100l8pg.html ALV的Excel方式显示缺少模板 有时候在ALV的Excel格式显示的时候，会提示：请和系统管理员联系,缺少下列模板:sap_sm.xls。 两种方式： 一、运行程序：BCALV_BDS_IMPORT_SAP_TEMPLATE，在Client000 Copy一个。 二、...
一步步CEF（1）之编译libcef_dll_wrapper.lib
随风动，心飞翔
12-07 8098
如果要从源码编译的话，估计硬盘和内存都有要求，这个我不想尝试，可以只能下载一份做c++的。（有空可以考虑源码编译的，不过目前这个必要）注意：下面工程为了简单，没有将lib的名字设置为libcef_dll_wrapper！ 下载地址：http://opensource.spotify.com/cefbuilds/index.html 最好选择Standard分发版本，如果要调试的话，可以下载...
java.lang.NoSuchFieldError: STANDARD_NUMBER_TYPES谁知道这个异常到底为什么啊
ydc201314的博客
06-25 2419
SEVERE: Servlet.service() for servlet [yuwan-manager-web] in context with path [] threw exception [Servlet execution threw an exception] with root causejava.lang.NoSuchFieldError: STANDARD_NUMBER_TYPE...
ckeditor_4.5.9_standard.zip
07-19
《ckeditor_4.5.9_standard.zip：深度解析富文本编辑器CKEditor 4.5.9标准版》 在互联网内容创作领域，富文本编辑器扮演着至关重要的角色，它们为用户提供了一种直观、易用的方式来创建和编辑带有格式的文本。...
jdk-13_linux-x64_bin.tar.gz
10-12
JDK 13是Java SE（Standard Edition）的一个重要版本，发布于2019年。每个Java版本都会引入新的特性和改进，JDK 13也不例外。在JDK 13中，我们可以看到以下主要更新和特性： 1. **Switch Expressions增强**：Java ...
store_v5.zip
04-06
Java Web通常涉及Servlet、JSP（JavaServer Pages）、JSTL（JavaServer Pages Standard Tag Library）等技术，这些技术是构建动态网站和企业级应用的基础。源代码意味着我们可以查看和学习整个系统的实现细节，这...
KVG__JSP.rar_.kvg文件
09-23
6. **JSTL（JavaServer Pages Standard Tag Library）**：一套标准标签库，提供了处理常见任务的标签，如循环、条件语句、XML处理等，提高了代码的可读性和可维护性。 7. **Servlet容器**：如Tomcat，负责解析JSP...
mediapipe-0.8.8.1-cp39-cp39-manylinux_2_17_x86_64.whl
08-11
mediapipe-0.8.8.1-cp39-cp39-manylinux_2_17_x86_64.whl
python爱心代码高级
08-11
1. 一行代码画爱心 print('\n'.join([''.join([('Love'[(x-y)%4]if((x*0.05)**2+(y*0.1)**2-1)**3-(x*0.05)**2*(y*0.1)**3<=0 else' ')for x in range(-30,30)])for y in range(15,-15,-1)])) 效果图 2. 用turtle库画爱心加文字 import turtle import math turtle.pen() t=turtle t.up() t.goto(0,150) t.down() t.color('red') t.begin_fill() t.fillcolor('red') t.speed(1) t.left(45) t.forward(150) t.right(45) t.forward(100) t.right(45) t.forward(100) t.right(45) t.forward(100) t.right(45) t.forward(250+math.sqrt(2)*100) t.right (90) t
mediapipe-0.8.9.1-cp38-cp38-win_amd64.whl
08-11
mediapipe-0.8.9.1-cp38-cp38-win_amd64.whl
开发资料技术资料USB设备驱动开发深度解析-宋宝华非常好的技术资料.zip
最新发布
08-11
开发资料技术资料USB设备驱动开发深度解析-宋宝华非常好的技术资料.zip
通过类继承，实现一个线程类， 从https://www.51voa.com/VOA_Standard_3.html (其中 "3"可被替换为其他数字，对应翻页操作)中获取新的链接地址列表。
05-15
soup = BeautifulSoup(response.content, "html.parser") for link in soup.find_all("a"): href = link.get("href") if href and href.endswith(".html"): self.links.append(href) def get_links(self): ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值