99re热久久这里只有精品34,亚洲午夜精品久久久久久久久久久久,1769视频在线播放免费观看

nlog安装

Mon, 06 Jan 2020 08:10:00 GMT

Install-Package NLog.Config -Version 3.2.1

Install-Package NLog -Version 3.2.1

华梦�?/a> 2020-01-06 16:10 发表评论

Sun, 15 Sep 2019 14:02:00 GMT

mysql5.7以上版本在常会报关于only_full_group_by的错误，可以在sql_mode中关闭他�Q�网上查扄��?/span>
在[mysqld]中添加代�?/li>

sql_mode ='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'

重启mysql
sudo service mysql restart
mysql5.7以上版本在常会报关于only_full_group_by的错误，可以在sql_mode中关闭他�Q�网上查扄����?/span>
查看参数是否存在
mysql> SELECT @@sql_mode;
+------------------------------------------------------------------------------------------------------------------------+
| @@sql_mode                                                                                                             |
+------------------------------------------------------------------------------------------------------------------------+
| STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> SELECT @@GLOBAL.sql_mode;
+------------------------------------------------------------------------------------------------------------------------+
| @@GLOBAL.sql_mode                                                                                                      |
+------------------------------------------------------------------------------------------------------------------------+
| STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

华梦�?/a> 2019-09-15 22:02 发表评论

mysql zip 安装5.7

Sat, 14 Sep 2019 14:51:00 GMT

MYSQL_HOME 解压路径 C:\DevelopTool\MySQL\mysql-5.7.25-winx64

Path %MYSQL_HOME%\bin

>mysqld --initialize --user=mysql --console
mysqld -install

先启动服务：

net start MySQL【或者是MySQL57�?/code>


修改密码
mysqladmin -uroot -p123456 password 123 


sc delete 服务名例如： sc delete mysql




https://www.cnblogs.com/july7/p/11489029.html 

�q�程讉K��
use mysql;
GRANT ALL ON *.* TO root@'%' IDENTIFIED BY '密码' WITH GRANT OPTION;
flush privileges;


华梦�?/a> 2019-09-14 22:51 发表评论



Sat, 18 May 2019 03:11:00 GMT
 需要添加一个环境变量POSTMAN_DISABLE_GPU = true�?



华梦�?/a> 2019-05-18 11:11 发表评论


REST API URI设计
Mon, 26 Jun 2017 01:50:00 GMT
在了解REST API URI设计的规则之前，让我们快速浏览一些我们将要讨论的术语�?/p>
URIs
REST API使用�l�一资源标识�W�（URI�Q�来��d��资源。在当今互联�|�上�Q�充斥着各种各样的URI设计规则�Q�既有像//api.example.com/louvre/leonardo-da-vinci/mona-lisa�q�样能够清楚的传达API资源模型的文章，也有很难理解的文章，例如�Q?a  style="box-sizing: border-box; background-color: transparent; color: #337ab7; text-decoration: none;">//api.example.com/68dd0-a9d3-11e0-9f1c-0800200c9a66 �Q�Tim Berners-Lee在他�?#8220;Axioms of Web Architecture”一文中���URI的不透明度�ȝ��成一句话�Q?/p>
唯一可以使用标识�W�的是引用对象。在不取消引用时�Q�就不应该查看URI字符串的内容以获取其他信息�?nbsp;
——蒂姆·伯纳�?- �?/a>
客户端必��遵循Web的链接范例，���URI视�ؓ不透明标识�W��?/p>
REST API设计人员应该在考虑���REST API资源模型传达�l�潜在的客户端开发者的前提下，创造URI。在�q�篇文章中，我将���试为REST API URI 引入一�?a  style="box-sizing: border-box; background-color: transparent; color: #337ab7; text-decoration: none;">设计规则�?/p>
先蟩�q�规则，URI的通用语法也适用与本文中的URI�?a  style="box-sizing: border-box; background-color: transparent; color: #337ab7; text-decoration: none;">RFC 3986定义了通用URI语法�Q�如下所�C�：
URI = scheme “://” authority “/” path [ “?” query ][ “#” fragment ]
规则1�Q�URI�l�尾不应包含�Q?�Q?/h2>�q�是作�ؓURI路径中处理中最重要的规则之一�Q�正斜杠�Q?�Q�不会增加语义��|��且可能导致�؜淆。REST API不允�怸�个尾部的斜杠�Q�不应该���它们包含在提供�l�客��L��的链接的�l�尾处�?/p>
许多Web�l��g和框架将�q�等对待以下两个URI�Q?nbsp;
http://api.canvas.com/shapes/ 
http://api.canvas.com/shapes
但是�Q�实际上URI中的每个字符都会计入资源的唯一�w�䆾的识别中�?/span>
两个不同的URI映射��C��个不同的资源。如果URI不同�Q�那么资源也是如此，反之亦然。因此，REST API必须生成和传递精���的URI�Q�不能容忍�Q何的客户端尝试不�_����的资源定位�?/p>
有些API���到�q�种情况�Q�可能设计�ؓ让客��L��重定向到相应没有���斜杠的URI�Q�也有可能会�q�回301 - 用来资源重定向）�?/p>
规则2�Q�正斜杠分隔�W�（/�Q�必��ȝ��来指�C�层�U�关�p?/h2>URI的�\径中的正斜杠�Q?�Q�字�W�用于指�C����源之间的层次关系�?/p>
例如�Q?nbsp;
(http://api.canvas.com/shapes/polygons/quadrilaterals/squares �Q?/p>
规则3�Q�应使用�q�字�W�（ - �Q�来提高URI的可��L�?/h2>��Z��使您的URI�Ҏ��让�h们理解，请��用连字符�Q?- �Q�字�W�来提高长�\径中名称的可��L��。在路径中，应该使用�q�字�W�代�I�格�q�接两个单词 �?/p>
例如�Q?nbsp;
http://api.example.com/blogs/guy-levin/posts/this-is-my-first-post
规则4�Q�不得在URI中��用下划线�Q�_�Q?/h2>一些文本查看器��Z��区分�����URI�Q�常�怼�在URI下加上下划线。这样下划线�Q�_�Q�字�W�可能被文本查看器中默认的下划线部分地遮蔽或完全隐藏�?/p>
为避免这�U��؜淆，请��用连字符�Q?- �Q�而不是下划线
规则5�Q�URI路径中首选小写字�?/h2>方便�Ӟ��URI路径中首选小写字母，因�ؓ大写字母有时会导致一些问题。RFC 3986���URI定义为区分大���写�Q�但scheme �?host components除外�?/p>
例如�Q?nbsp;
http://api.example.com/my-folder/my-doc
HTTP://API.EXAMPLE.COM/my-folder/my-doc 
�q�个URI很好。URI格式规范�Q�RFC 3986�Q�认�����URI与URI�Q?相同�?/p>
http://api.example.com/My-Folder/my-doc 
而这个URI与URI 1�?不同�Q�这可能会导致不必要的�؜淆�?/p>
规则6�Q�文件扩展名不应包含在URI�?/h2>在Web上，�Q?�Q�字�W�通常用于分隔URI的文件名和扩展名�?nbsp;
REST API不应在URI中包含�h造文件扩展名�Q�来指示邮�g实体的格式。相反，他们应该依赖通过Content-Type中的header传递media type�Q�来���定如何处理正文的内宏V�?/p>
http://api.college.com/students/3248234/courses/2005/fall.json 
http://api.college.com/students/3248234/courses/2005/fall
如上所�C�：不应使用文�g扩展名来表示格式�?/p>
应鼓励REST API客户端��用HTTP提供的格式选择机制Accept request header�?/p>
��Z��是链接和调试更简单，REST API应该支持通过查询参数来支持媒体类型的选择�?/p>
规则7�Q�端点名�U�是单数�q�是复数�Q?/h2>keep-it-simple的原则在�q�里同样适用。虽然一�?#8221;语法学家”会告诉你使用复数来描�q�资源的单个实例是错误的�Q�但实际上�ؓ了保持URI格式的一致性徏议��用复数�Ş式�?/p>
本着API提供商更�Ҏ��实施和API使用者更�Ҏ��操作的原则，可以不必�U�结一些奇怪的复数�Q�person/people�Q�goose/geese�Q��?/p>
但是应该怎么处理层��关系呢？如果一个关�p�d��能存在于另一个资源中�Q�RESTful原则��׃��提供有用的指对{��我们来看一下这个例子。学生有一些课�E�。这些课�E�在逻辑上映���到学生�l�端�Q�如下所�C�：
http://api.college.com/students/3248234/courses - ���索id�?248234的学生学习的所有课�E�的清单�?nbsp;
http://api.college.com/students/3248234/courses/physics -���索该学生的物理课�E?/p>
�l�论
当你�?a  style="box-sizing: border-box; background-color: transparent; color: #337ab7; text-decoration: none;">设计REST API服务�Ӟ��您必���L��意这些由URI定义的资源�?/p>
正在构徏的服务中的每个资源将臛_��有一个URI标识它。这个URI最好是有意义的�Q�且能充分描�q�资源。URI应遵循可预测的层�ơ结构，用来提高其可理解性，可用性：可预���的意义在于它们是一致的�Q�它的层�ơ结构在数据关系上是有意义的�?/p>
RESTful API是�ؓ使用者编写的。URI的名�U�和�l�构应该能够向��用者传达更清晰的含义。通过遵��@上述规则�Q�您���创��Z��个更清晰的的REST API与更友好的客��L��。这些�ƈ不是REST的规则或�U�束�Q�仅仅是API的增强和补充�?/p>
我也�����你来看看http://blog.restcase.com/5-basic-rest-api-design-guidelines/�q�篇文章�?/p>
最后，望大家牢讎ͼ�你在��Z��的客��L��设计API URI�Q�而不仅仅是�ؓ你的数据�?/p>

华梦�?/a> 2017-06-26 09:50 发表评论


Mon, 19 Jun 2017 06:45:00 GMT
* this.getClass().getClassLoader().getResourceAsStream("testVariables.bpmn")
         �?/span>classpath根目录下加蝲指定名称的文�?/span>
   * this.getClass().getResourceAsStream("testVariables.bpmn")    
         从当前包下加载指定名�U�的文�g
   * this.getClass().getResourceAsStream("/testVariables.bpmn")  
         �?/span>classpath根目录下加蝲指定名称的文�?/span>


华梦�?/a> 2017-06-19 14:45 发表评论


restful
Fri, 26 May 2017 00:01:00 GMT
package org.gdharley.activiti.integration.rest;

import com.fasterxml.jackson.annotation.JsonProperty;
import com.fasterxml.jackson.databind.JsonNode;
import com.fasterxml.jackson.databind.ObjectMapper;
import org.activiti.engine.ActivitiException;
import org.activiti.engine.delegate.DelegateExecution;
import org.activiti.engine.delegate.Expression;
import org.activiti.engine.delegate.JavaDelegate;
import org.apache.commons.lang3.StringUtils;
import org.apache.http.HttpResponse;
import org.apache.http.NameValuePair;
import org.apache.http.client.methods.*;
import org.apache.http.client.utils.URIBuilder;
import org.apache.http.client.utils.URLEncodedUtils;
import org.apache.http.conn.ssl.SSLConnectionSocketFactory;
import org.apache.http.conn.ssl.SSLContextBuilder;
import org.apache.http.conn.ssl.TrustSelfSignedStrategy;
import org.apache.http.entity.StringEntity;
import org.apache.http.impl.client.CloseableHttpClient;
import org.apache.http.impl.client.HttpClientBuilder;
import org.apache.http.message.BasicNameValuePair;
import org.apache.http.protocol.HTTP;
import org.apache.http.util.EntityUtils;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.http.HttpMethod;

import java.io.IOException;
import java.net.URI;
import java.net.URISyntaxException;
import java.util.List;


/**
 * Created by gharley on 5/2/17.
 */
public class SimpleRestDelegate implements JavaDelegate {
    private static final Logger logger = LoggerFactory.getLogger(SimpleRestDelegate.class);

    protected Expression endpointUrl;
    protected Expression httpMethod;
    protected Expression isSecure;
    protected Expression payload;

//    一个Content-Type是application/json的请求，具体看�v来是�q�样的：
//    POST /some-path HTTP/1.1
//    Content-Type: application/json
//
//    { "foo" : "bar", "name" : "John" }
//
//
//    { "foo" : "bar", "name" : "John" } ���是�q�个��h��的payload



    protected Expression headers;
    protected Expression responseMapping;

    protected ObjectMapper objectMapper = new ObjectMapper();

    // Create a mixin to force the BasicNameValuePair constructor
    protected static abstract class BasicNameValuePairMixIn {
        private BasicNameValuePairMixIn(@JsonProperty("name") String name, @JsonProperty("value") String value) {
        }
    }

    public void execute(DelegateExecution execution) throws Exception {
        logger.info("Started Generic REST call delegate");

        if (endpointUrl == null || httpMethod == null) {
            throw new IllegalArgumentException("An endpoint URL and http method are required");
        }

        String restUrl = getExpressionAsString(endpointUrl, execution);
        String payloadStr = getExpressionAsString(payload, execution);
        String headersJSON = getExpressionAsString(headers, execution); // [{"name":"headerName", "value":"headerValue"}]
        String method = getExpressionAsString(httpMethod, execution);
        String rMapping = getExpressionAsString(responseMapping, execution);
        String secure = getExpressionAsString(isSecure, execution);
        String scheme = secure == "true" ? "https" : "http";

        // validate URI and create create request
        URI restEndpointURI = composeURI(restUrl, execution);

        logger.info("Using Generic REST URI " + restEndpointURI.toString());

        HttpRequestBase httpRequest = createHttpRequest(restEndpointURI, scheme, method, headersJSON, payloadStr, rMapping);

        // create http client
        CloseableHttpClient httpClient = createHttpClient(httpRequest, scheme, execution);

        // execute request
        HttpResponse response = executeHttpRequest(httpClient, httpRequest);

        // map response to process instance variables
        if (responseMapping != null) {
            mapResponse(response, rMapping, execution);
        }

        logger.info("Ended Generic REST call delegate");

    }

    protected URI composeURI(String restUrl, DelegateExecution execution)
            throws URISyntaxException {

        URIBuilder uriBuilder = null;
        uriBuilder = encodePath(restUrl, uriBuilder);
        return uriBuilder.build();
    }

    protected URIBuilder encodePath(String restUrl, URIBuilder uriBuilder) throws URISyntaxException {

        if (StringUtils.isNotEmpty(restUrl)) {

            // check if there are URL params
            if (restUrl.indexOf('?') > -1) {

                List params = URLEncodedUtils.parse(new URI(restUrl), "UTF-8");

                if (params != null && !params.isEmpty()) {
                    restUrl = restUrl.substring(0, restUrl.indexOf('?'));
                    uriBuilder = new URIBuilder(restUrl);
                    uriBuilder.addParameters(params);

                }
            } else {
                uriBuilder = new URIBuilder(restUrl);
            }
        }

        return uriBuilder;
    }

    protected HttpRequestBase createHttpRequest(URI restEndpointURI, String scheme, String httpMethod, String headers, String payload, String responseMapping) {

        if (StringUtils.isEmpty(httpMethod)) {
            throw new ActivitiException("no HTTP method provided");
        }
        if (restEndpointURI == null) {
            throw new ActivitiException("no REST endpoint URI provided");
        }

        HttpRequestBase httpRequest = null;
        HttpMethod parsedMethod = HttpMethod.valueOf(httpMethod.toUpperCase());
        StringEntity input;
        URIBuilder builder = new URIBuilder(restEndpointURI);

        switch (parsedMethod) {
            case GET:
                try {
                    httpRequest = new HttpGet(builder.build());
                    httpRequest = addHeadersToRequest(httpRequest, headers);
                } catch (URISyntaxException use) {
                    throw new ActivitiException("Error while building GET request", use);
                }
                break;
            case POST:
                try {
                    httpRequest = new HttpPost(builder.build());
                    input = new StringEntity(payload);
//                input.setContentType(new BasicHeader(HTTP.CONTENT_TYPE, "application/json"));
                    ((HttpPost) httpRequest).setEntity(input);
                    httpRequest = addHeadersToRequest(httpRequest, headers);
                    break;
                } catch (Exception e) {
                    throw new ActivitiException("Error while building POST request", e);
                }
            case PUT:
                try {
                    httpRequest = new HttpPut(builder.build());
                    input = new StringEntity(payload);
//                input.setContentType(new BasicHeader(HTTP.CONTENT_TYPE, "application/json"));
                    ((HttpPut) httpRequest).setEntity(input);
                    httpRequest = addHeadersToRequest(httpRequest, headers);
                    break;
                } catch (Exception e) {
                    throw new ActivitiException("Error while building PUT request", e);
                }
            case DELETE:
                try {
                    httpRequest = new HttpDelete(builder.build());
                    httpRequest = addHeadersToRequest(httpRequest, headers);
                } catch (URISyntaxException use) {
                    throw new ActivitiException("Error while building DELETE request", use);
                }
                break;
            default:
                throw new ActivitiException("unknown HTTP method provided");
        }

        return httpRequest;
    }


    protected CloseableHttpClient createHttpClient(HttpRequestBase request, String scheme, DelegateExecution execution) {

        SSLConnectionSocketFactory sslsf = null;

        // Allow self signed certificates and hostname mismatches.
        if (StringUtils.equalsIgnoreCase(scheme, "https")) {
            try {
                SSLContextBuilder builder = new SSLContextBuilder();
                builder.loadTrustMaterial(null, new TrustSelfSignedStrategy());
                sslsf = new SSLConnectionSocketFactory(builder.build(), SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER);
            } catch (Exception e) {
                logger.warn("Could not configure HTTP client to use SSL", e);
            }
        }

        HttpClientBuilder httpClientBuilder = HttpClientBuilder.create();

        if (sslsf != null) {
            httpClientBuilder.setSSLSocketFactory(sslsf);
        }

        return httpClientBuilder.build();
    }

    protected HttpResponse executeHttpRequest(CloseableHttpClient httpClient, HttpRequestBase httpRequest) {

        CloseableHttpResponse response = null;
        try {
            response = httpClient.execute(httpRequest);
        } catch (IOException e) {
            throw new ActivitiException("error while executing http request: " + httpRequest.getURI(), e);
        }

        if (response.getStatusLine().getStatusCode() >= 400) {
            throw new ActivitiException("error while executing http request " + httpRequest.getURI() + " with status code: "
                    + response.getStatusLine().getStatusCode());
        }

        return response;
    }

    protected void mapResponse(HttpResponse response, String responseMapping, DelegateExecution execution) {

        if (responseMapping == null || responseMapping.trim().length() == 0) {
            return;
        }

        JsonNode jsonNode = null;
        try {
            String jsonString = EntityUtils.toString(response.getEntity());
            jsonNode = objectMapper.readTree(jsonString);

        } catch (Exception e) {
            throw new ActivitiException("error while parsing response", e);
        }

        if (jsonNode == null) {
            throw new ActivitiException("didn't expect an empty response body");
        }
        execution.setVariable(responseMapping, jsonNode.toString());
    }

    protected HttpRequestBase addHeadersToRequest(HttpRequestBase httpRequest, String headerJSON) {
        Boolean contentTypeDetected = false;
        if (headerJSON != null) {
            // Convert JSON to array
            try {
                // configuration for Jackson/fasterxml
                objectMapper.addMixInAnnotations(BasicNameValuePair.class, BasicNameValuePairMixIn.class);
                NameValuePair[] headers = objectMapper.readValue(headerJSON, BasicNameValuePair[].class);
                for (NameValuePair header : headers) {
                    httpRequest.addHeader(header.getName(), header.getValue());
                    if (header.getName().equals(HTTP.CONTENT_TYPE)) {
                        contentTypeDetected = true;
                    }
                }
            } catch (Exception e) {
                throw new ActivitiException("Unable to parse JSON header array", e);
            }
        }
        // Now add content type if necessary
        if (!contentTypeDetected) {
            httpRequest.addHeader(HTTP.CONTENT_TYPE, "application/json");
        }
        return httpRequest;
    }

    /**
     * @return string value of expression.
     * @throws {@link IllegalArgumentException} when the expression resolves to a value which is not a string
     *                or if the value is null.
     */
    protected String getExpressionAsString(Expression expression, DelegateExecution execution) {
        if (expression == null) {
            return null;
        } else {
            Object value = expression.getValue(execution);
            if (value instanceof String) {
                return (String) value;
            } else {
                throw new IllegalArgumentException("Expression does not resolve to a string or is null: " + expression.getExpressionText());
            }
        }
    }
}


华梦�?/a> 2017-05-26 08:01 发表评论


Tue, 16 May 2017 08:31:00 GMT
1、概�q?/h2>activiti�pȝ��一共有23个表�Q�包括流�E�定义表、一般数据信息表、流�E�运行实例表、流�E�历史记录表、用��L����L��表�?/p>
2、Activiti ���程定义�?/h2>���程定义表，���程定义表也可以叫做是静态资源库�Q�静态资源包括图片、定义规则等。它有部�|�信息表、流�E�模型表、流�E�定义表
1、ACT_RE_DEPLOYMENT�Q�部�|�信息表�Q?/p>
包括�Q�部�|�流�E�名�U�、类型、部�|�时�?/p>
2、ACT_RE_MODEL�Q�模型表�Q?/p>
名称,key、类型、创建时间、最后修�Ҏ��间、版本、数据源信息、部�|�ID、编辑源值ID、编辑源额外值ID�Q�外键ACT_GE_BYTEARRAY �Q?/p>
3、ACT_RE_PROCDEF�Q�流�E�定义表�Q?nbsp;
包括���程定义、类型、流�E�名�U�、流�E�key、版本号、部�|�ID、资源名�U�、图片资源名�U�、描�q�C��息、是否从key启动、暂停状态�?/p>
3、Activiti �q�行实例�?/h2>�q�行实例表记录流�E�流转过�E�中产生的数据，一般数据分��Z��个部分流�E�数据、业务数据。流�E�数据是指activiti���程引擎����{�q�程中的数据�Q�包括流�E�执行实例数据接、�Q务数据、执行�Q务�h员信息、变量信息。业务数据则是流�E�过�E�中保存的表单数据，例如�Q�如请假的请假单数据、报销单数据、审�Ҏ��见信息等�Q�此部分数据一般需要自己徏数据表进行保存，在之前的jbpm4中没有保存业务数据�?/p>
1、ACT_RU_EVENT_SUBSCR�Q�事件子脚本�Q�作用未�?/p>
事�g名称�Q�EVENT_NAME_�Q�、事件类�?EVENT_TYPE_)、流�E�执行ID(EXECUTION_ID_)、流�E�实例ID(PROC_INST_ID_)、活动ID(ACTIVITY_ID_)、配�|�信�?CONFIGURATION_)、创建时��_��CREATED_�Q?/p>
2、ACT_RU_EXECUTION�Q�执行中���程执行�Q�核心我的代办�Q务查询表
���程实例ID�Q�PROC_INST_ID_�Q�，业务key�Q�BUSINESS_KEY_�Q�、父执行���程�Q�PARENT_ID_�Q�、流�E�定义Id�Q�外键PROC_DEF_ID_�Q�、实例id�Q�ACT_ID_�Q�、激�zȝ��态（IS_ACTIVE_�Q�、�ƈ发状态（is_concurrent�Q�、is_scope、is_evnet_scope、暂停状态（suspension_state�Q�、缓存结束状态（cached_end_state�Q?/p>
3、ACT_RU_IDENTITYLINK�Q���n份联�p�）
用户�l�ﾃ�Q�（GROUP_ID_�Q�、用��L���c�d��(TYPE_)、用户ID(USER_ID_)、�Q务Id�Q�外键：TASK_ID_�Q�、流�E�实例ID�Q�外键：PROC_INST_ID_�Q�、流�E�定义Id�Q�外�?PROC_DEF_ID_�Q?/p>
4、ACT_RU_JOB(�q�行中的��d��)
5、ACT_RU_TASK�Q�执行中实时��d���Q�代办�Q务查询表
实例id�Q�外键EXECUTION_ID_�Q�、流�E�实例ID�Q�外键PROC_INST_ID_�Q�、流�E�定义ID�Q�PROC_DEF_ID_�Q�、�Q务名�U�ͼ�NAME_�Q�、父节�Q务ID�Q�PARENT_TASK_ID_�Q?/p>
、�Q务描�q�ͼ�DESCRIPTION_�Q�、�Q务定义key�Q�TASK_DEF_KEY_�Q�、所属�h�Q�OWNER_�Q�、代理�h�?(ASSIGNEE_)、代理团�Q�DELEGATION_�Q�、优先权�Q�PRIORITY_�Q�、创建时��_��CREATE_TIME_�Q�、执行时��_��DUE_DATE_�Q�、暂停状态（SUSPENSION_STATE_�Q?/p>
6、ACT_RU_VARIABLE�Q�实时变量）
变量名称�Q�NAME_�Q�、编码类�?TYPE_)、执行实例ID(EXECUTION_ID_)、流�E�实例Id(PROC_INST_ID_)、�Q务id(TASK_ID_)、字节组ID�Q�BYTEARRAY_ID_�Q�、DOUBLE_、LONG_、TEXT_、TEXT2_
3、流�E�历史记�?/h2>���程历史信息表，activiti历史记录表包括节点信息表、附件信息表、历史审批记录表、理惌����l�信息表、历史��n份信息表、流�E�实例历史表、�Q务历史表、历史变量表。（节点信息表、附件信息表、历史审批记录表、理惌����l�信息表、历史��n份信息表�Q�这些表目前�q�未知是如何用的。（���程实例历史表、�Q务历史表、历史变量）三个表可以查询我已完成�Q务、�Q务追�t�等�?/p>
1、ACT_HI_ACTINST�Q�活动实例信息）
���程定义ID�Q�PROC_DEF_ID_�Q�、流�E�实例ID�Q�PROC_INST_ID_�Q�、流�E�执行ID�Q�EXECUTION_ID_�Q�、活动ID�Q�ACT_ID_�Q�、活动名�U�ͼ�TASK_ID_�Q�、活动类型（ACT_TYPE_�Q�、�Q务ID、（TASK_ID_�Q�、请求流�E�实例ID�Q�CALL_PROC_INST_ID_�Q�、代理�h员（ASSIGNEE_�Q�、开始时��_��START_TIME_�Q�、结束时�?END_TIME_)、时长（DURATION_�Q?/p>
2、ACT_HI_ATTACHMENT�Q�附件信息）
用户id�Q�USER_ID_�Q�、名�U�ͼ�NAME_�Q�、描�q�ͼ�DESCRIPTION_�Q�、类型（TYPE_�Q�、�Q务Id�Q�TASK_ID_�Q�、流�E�实例ID�Q�PROC_INST_ID_�Q�、连接（URL_�Q�、内容Id�Q�CONTENT_ID_�Q?/p>
3、ACT_HI_COMMENT�Q�历史审批信息）
�c�d���Q�TYPE_�Q�、时��_��TIME_�Q�、用户Id�Q�USER_ID_�Q�、�Q务Id�Q�TASK_ID_�Q�、流�E�实例Id�Q�PROC_INST_ID_�Q�、活动（ACTION_�Q�、消息（MESSAGE_�Q�、全部消息（FULL_MSG_�Q?/p>
4、ACT_HI_DETAIL�Q�历史详�l�信息）
数据�c�d���Q�TYPE_�Q�、创建时�?TIME_)、名�U?NAME_)、流�E�实例ID�Q�PROC_INST_ID_�Q�、执行实例Id(EXECUTION_ID_)、�Q务Id(TASK_ID_)、活动实例Id(ACT_INST_ID_)、变量类�?VAR_TYPE_)、字节数�l�Id、DOUBLE_、LONG_、��|��TEXT_�Q�、�?�Q�TEXT2_�Q?/p>
5、ACT_HI_IDENTITYLINK�Q�历史��n份信息）
��d��Id�Q�TASK_ID_�Q�、流�E�实例Id�Q�PROC_INST_ID_�Q�、userId�Q�USER_ID_�Q�、用��L���c�d��Type�Q�TYPE_�Q�、用��L��ID�Q�GROUP_ID_�Q?/p>
6、ACT_HI_PROCINST�Q�历史流�E�实例信息）核心�?/p>
���程实例ID�Q�PROC_INST_ID_�Q�、业务Key�Q�BUSINESS_KEY_�Q�、流�E�定义Id�Q�PROC_DEF_ID_�Q�、开始时��_��START_TIME_�Q�、结束时��_��END_TIME_�Q�、时长（DURATION_�Q�、发起�h员Id�Q�START_USER_ID_�Q�、开始节点（START_ACT_ID_�Q�、结束节点（END_ACT_ID_�Q�、超�U�流�E�实例Id�Q�SUPER_PROCESS_INSTANCE_ID_�Q�、删除理由（DELETE_REASON_�Q?/p>
7、ACT_HI_TASKINST�Q�历史�Q务流�E�实例信息）核心�?/p>
���程实例ID�Q�PROC_INST_ID_�Q�、�Q务定义Key�Q�BUSINESS_KEY_�Q�、流�E�定义Id�Q�PROC_DEF_ID_�Q�、执行ID�Q�EXECUTION_ID_�Q�、名�U�ͼ�NAME_�Q�、父��d��iD�Q�PARENT_TASK_ID_�Q�、描�q�ͼ�DESCRIPTION_�Q�、所属�h�Q�OWNER_�Q�、代理�h�Q�ASSIGNEE_�Q�、开始时��_��START_TIME_�Q�、结束时��_��END_TIME_�Q�、时长（DURATION_�Q�、删除理由（DELETE_REASON__�Q�、优先���Q�PRIORITY_�Q�、应完成旉����Q�DUE_DATE_�Q�、表单key�Q�FORM_KEY_�Q?/p>
8、ACT_HI_VARINST�Q�历史变量信息）
���程实例ID�Q�PROC_INST_ID_�Q�、执行ID�Q�EXECUTION_ID_�Q�、�Q务Id、名�U�ͼ�NAME_�Q�、变量（TASK_ID_�Q�、类型（VAR_TYPE_�Q�、字节数�l�ID�Q�BYTEARRAY_ID_�Q�、DOUBLE_、LONG_、TEXT_、TEXT2_
4、一般数�?/h2>1、ACT_GE_BYTEARRAY�Q�字节数据表�Q?/p>
名称�Q�NAME_�Q�、部�|�Id�Q�DEPLOYMENT_ID_�Q�、字节数据（BYTES_�Q�、发生的�Q�GENERATED_�Q?/p>
2、ACT_GE_PROPERTY�Q�一般属性表�Q?/p>
名称�Q�NAMe_�Q�、�?VALUe_)
5、用��L����L���?/h2>Activit 的用��L����L��表，包括用户信息、用��L��信息、用户与用户�l�间的关�p�R��用户信息与用户之间的关�p�R��在实际开发中未采用，用的实际�pȝ��中用戗��?/p>
1、ACT_ID_GROUP�Q�用��L��表）
名称�Q�NAME_�Q�、类�?TYPE_)
2、ACT_ID_USER�Q�用戯����Q?/p>
�?FIRST_)、名�U?LAST_)、邮�?EMAIL_)、密�?PWD_)、头像Id (PICTURE_ID_)
3、ACT_ID_INFO�Q�用户信息表�Q?/p>
用户Id(USER_ID_)、类�?TYPE_)、formINPut名称(KEY_)、�?VALUE_)、密�?PASSWORD_)、父节点(PARENT_ID_)
4、ACT_ID_MEMBERSHIP�Q�用��L����L��兌���表）
用户Id(user_ID_)、用��L��Id�Q�group_Id�Q?/p>
Activiti表结构分析完成，�׃��5个小�Ӟ���q�有很多问题不明白。后�l�慢慢开发过�E�中再理一�ơ表之间关系吧，初步��x��在系�l�中需要扩������Q�把业务数据和流�E�数据分开�?/p>


华梦�?/a> 2017-05-16 16:31 发表评论


Mon, 15 May 2017 14:23:00 GMT
     摘要: Activiti工作���引擎数据库表结�?数据库表的命�?Acitiviti数据库中表的命名都是以ACT_开头的。第二部分是一个两个字�W�用例表的标识。此用例大体与服务API是匹配的�?l  ACT_RE_*:’RE’表示repository。带此前�~�的表包含的是静态信息，如，���程定义�Q�流�E�的资源�Q�图片，规则�{�）�?l  ACT_RU_*:̵...  阅读全文

华梦�?/a> 2017-05-15 22:23 发表评论


jpa 字段不要映射
Wed, 10 May 2017 08:59:00 GMT
 @Transient 
可�?
@Transient表示该属性�ƈ非一个到数据库表的字�D늚�映射,ORM框架���忽略该属�? 
如果一个属性�ƈ非数据库表的字段映射,���务必将其标�C�Zؓ@Transient,否则,ORM框架默认其注解�ؓ@Basic 
�C�Z��: 
//�Ҏ��birth计算出age属�?
@Transient 
public int getAge() { 
return getYear(new Date()) - getYear(birth); 

} 

注意是加在get�Ҏ��上的


华梦�?/a> 2017-05-10 16:59 发表评论


SNMP 相关
Wed, 22 Mar 2017 07:28:00 GMT
Snmpwalk –v 2 –c public 192.168.20.114 1.3.6.1.2.1.2.2.1.3
snmpget -r:127.0.0.1 -o:.1.3.6.1.2.1.25.3.3.1.2
E:\>snmpget -r:127.0.0.1 -o:.1.3.6.1.2.1.1.1.0
SnmpGet v1.01 - Copyright (C) 2009 SnmpSoft Company
[ More useful network tools on http://www.snmpsoft.com ]
OID=.1.3.6.1.2.1.1.1.0
Type=OctetString
Value=Hardware: Intel64 Family 6 Model 60 Stepping 3 AT/AT COMPATIBLE - Software
: Windows Version 6.1 (Build 7601 Multiprocessor Free)
snmpwalk -v:2c -c:public -r:127.0.0.1


华梦�?/a> 2017-03-22 15:28 发表评论


Druid 介绍
Mon, 20 Mar 2017 16:11:00 GMT
Druid是什么？ 
Druid是一个JDBC�l��g�Q�它包括四个部分�Q?/p>
http://download.csdn.net/download/feelnature/1580901
http://tomcat.apache.org/tomcat-8.5-doc/monitoring.html#Enabling_JMX_Remote

http://download.csdn.net/detail/qq_21163257/9695557
 

DruidDriver 代理Driver�Q�能够提供基于Filter�Q�Chain模式的插件体�p�R�?/div>

DruidDataSource 高效可管理的数据库连接池�?/div>

SQLParser

扩展�l��g

Binary: http://code.alibabatech.com/mvn/releases/com/alibaba/druid/0.1.2/druid-0.1.2.jar

Source: http://code.alibabatech.com/mvn/releases/com/alibaba/druid/0.1.2/druid-0.1.2-sources.jar
Druid可以做什么？

可以监控数据库访问性能�Q�Druid内置提供了一个功能强大的StatFilter插�g�Q�能够详�l�统计SQL的执行性能�Q�这对于�U�上分析数据库访问性能有帮助�?/div>

替换DBCP和C3P0。Druid提供了一个高效、功能强大、可扩展性好的数据库�q�接池�?/div>

数据库密码加密。直接把数据库密码写在配�|�文件中�Q�这是不好的行�ؓ�Q�容易导致安全问题。DruidDruiver和DruidDataSource都支持PasswordCallback�?/div>

SQL执行日志�Q�Druid提供了不同的LogFilter�Q�能够支持Common-Logging、Log4j和JdkLog�Q�你可以按需要选择相应的LogFilter�Q�监控你应用的数据库讉K��情况�?/div>

扩展JDBC�Q�如果你要对JDBC层有�~�程的需求，可以通过Druid提供的Filter机制�Q�很方便�~�写JDBC层的扩展插�g�?/div>


DruidDriver�Q�是一个ProxyJdbcDriver�Q�它提供了Filter-Chain模式的扩展机�Ӟ��使得在Jdbc扩展�~�程特别方便�?/p>
Druid提供了一些内�|�的扩展机制�Q�包�?u>Stat�?u>Log�?u>Trace、HA�{�扩展�?/p>



DruidDataSource是一个数据库�q�接池的实现�Q�它的设计目标是提供一个当前最好的数据库连接池�Q�在性能、扩展性等斚w��取得最合适的�q�����Q�取代DBCP、C3P0�{�连接池�?/p>

高性能。测试数据表明，Druid比DBCP、C3P0、BoneCP的性能都好很多。具体请�?u>���试数据

可管理性，DruidDataSource本��n提供了很多监控属性，具体�?u>�q�里。DruidDataSource支持StatFilter�Q�具体配�|�看 �q�里

可扩展性，提供��Z��Filter-Chain模式的扩展机制。具体自定义扩展的例子看�q�里�?/div>

替换DBCP�Q�配�|�和DBCP兼容�Q�可以方便替换DBCP�?/div>

适合大规模应用。结合Alibaba使用数据库连接池的经验，避免一些已知问题，例如数据库不可用恢复之后产生的连接风暴问题等�?/div>
设计
�q�是DruidDataSource的设计图�C�： 
http://code.alibabatech.com/svn/druid/trunk/doc/druid-pool.txt 
如果发现有�ؕ码，请选择utf-8的编码方式查看�?/p>


Druid提供一个手工编写的高性能的方便扩展的SQL Parser。将会支持MySQL、Oracle�{�流行关�p�L��据库的SQL Parser�?/p>
Parser�l��g包括如下几个部分�Q?/p>

Lexer 词法解析

Parser�Q�Parser包括ExprParser�Q�各�U�StatementParser�?/div>

AST, Abstract Syntax Tree。ParserParse出来的结果就是AST�?/div>

Visitor。对AST做各�U�处理，比如FormatOutput�Q�遍历等�{��?/div>


����?/h3>
 
Druid提供了强大的监控功能�Q�能够监控连接池行�ؓ和SQL执行情况�Q�让你能够详�l�了解应用的数据库访问行为�?/p>
监控对象

Druid的统计信息定义代码实现在com/alibaba/druid/stat下。所有的Stat都全局静态变量的方式保存�Q�这样做使得外部获取监控信息更容易�?/div>

获取Druid监控信息的入口是com.alibaba.druid.stat.JdbcStatManager

Druid的监控统计信息都是通过StatFilter来实现的�Q�如果你需要数据源�q�行监控�Q�那你需要启用StatFilter

 


华梦�?/a> 2017-03-21 00:11 发表评论


spring 相关�|�站介绍
Sun, 19 Mar 2017 14:39:00 GMT
http://repo.spring.io/release/org/springframework/spring/4.3.6.RELEASE/



http://spring.io/tools/sts

http://www.loveweir.com/posts/view/19 
 
https://github.com/rahulyewale/springmvcjpa 

http://download.csdn.net/download/jiuqiyuliang/8640621 


http://blog.csdn.net/suzunshou/article/details/49949005

https://repo1.maven.org/maven2/org/mybatis/mybatis/ 


http://blog.csdn.net/jiuqiyuliang/article/details/45132493/ 


https://github.com/mybatis/generator/releases

华梦�?/a> 2017-03-19 22:39 发表评论


mysql导入��q��
Thu, 21 Jul 2016 05:33:00 GMT
今天从windows上导��Z��个sql执行文�g�Q�再倒入到unbutn中，�l�果出现��q���Q�折�?-8分钟�Q?nbsp;
解决方式 
在导出mysql sql执行文�g的时候，指定一下编码格式： 
复制代码 代码如下:
mysqldump -uroot -p --default-character-set=utf8 mo�Q�dbname�Q?> E://xxxx.sql 
导入的时候OK�?nbsp;
执行如下 
复制代码 代码如下:
mysql -u root -p --default-character-set=utf8 
use dbname 
source /root/newsdata.sql 


华梦�?/a> 2016-07-21 13:33 发表评论


Mon, 27 Jun 2016 09:42:00 GMT
CentOS
1、备�?/div>
mv /etc/yum.repos.d/CentOS-Base.repo /etc/yum.repos.d/CentOS-Base.repo.backup 
2、下载新的CentOS-Base.repo �?etc/yum.repos.d/
CentOS 5
 wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-5.repo  
CentOS 6
 wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-6.repo  
CentOS 7
 wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-7.repo  
3、之后运行yum makecache生成�~�存
相关链接
##官方主页: http://www.centos.org/
##邮�g列表: http://www.centos.org/modules/tinycontent/index.php?id=16
##论坛: http://www.centos.org/modules/newbb/
##文档: http://www.centos.org/docs/
##Wiki: http://wiki.centos.org/


华梦�?/a> 2016-06-27 17:42 发表评论


输入数据�q�行正态化
Wed, 11 May 2016 10:27:00 GMT
对输入数据进行正态化
 
��Z��使神�l�网�l�有效，我们必须�Ҏ��据进行正态化。这是激�z�d��数的正确计算所需要的。正态化是一�U�数学处理，���数据�{换�ؓ 0..1 �?-1..1 的范围。正态化后的数据可以�q�行��L��态化�Q�即转换回原来的范围�?br />
要将���经�|�络输出解码��Z�h�c�d���ȝ��形式�Q�需要对数据�q�行��L��态化。谢天谢圎ͼ�负责标准化和��L��准化�Q�因此不需要实施它。如果您对它的工作原理感到好奇，您可以分析以下代码：  


public static double INPUT_LOW = -20;
    public static double INPUT_HIGH = 20;
    public static double OUTPUT_HIGH = 1;
    public static double OUTPUT_LOW = -1;
    public static double normalize(final double value) {
        return ((value - INPUT_LOW) / (INPUT_HIGH - INPUT_LOW))
                * (OUTPUT_HIGH - OUTPUT_LOW) + OUTPUT_LOW;
        // return ((10f + 20f) / (40f)) * (2f) + OUTPUT_LOW;
    }
    public static double deNormalize(final double data) {
        double result = ((INPUT_LOW - INPUT_HIGH) * data - OUTPUT_HIGH
                * INPUT_LOW + INPUT_HIGH * OUTPUT_LOW)
                / (OUTPUT_LOW - OUTPUT_HIGH);
        return result;
    }

x=-5:.01:5;
   plot(x,tanh(x)),grid on;


华梦�?/a> 2016-05-11 18:27 发表评论


cron4j使用说明
Sat, 07 May 2016 07:39:00 GMT
1. Quickstart
The cron4j main entity is the scheduler. With a it.sauronsoftware.cron4j.Scheduler instance you can execute tasks at fixed moments, during all the year. A scheduler can execute a task once a minute, once every five minutes, Friday at 10:00, on February the 16th at 12:30 but only if it is Saturday, and so on.
The use of the cron4j scheduler is a four steps operation:
Create your Scheduler instance.
Schedule your actions. To schedule an action you have to tell	the scheduler what it has to do and when. You can	specify what using a java.lang.Runnable or a it.sauronsoftware.cron4j.Task	instance, and you can specify when using a scheduling pattern,	which can be represented with a string or with a it.sauronsoftware.cron4j.SchedulingPattern	instance.
Starts the scheduler.
Stops the scheduler, when you don't need it anymore.
Consider this simple example:
import it.sauronsoftware.cron4j.Scheduler;  public class Quickstart {  	public static void main(String[] args) { 		// Creates a Scheduler instance. 		Scheduler s = new Scheduler(); 		// Schedule a once-a-minute task. 		s.schedule("* * * * *", new Runnable() { 			public void run() { 				System.out.println("Another minute ticked away..."); 			} 		}); 		// Starts the scheduler. 		s.start(); 		// Will run for ten minutes. 		try { 			Thread.sleep(1000L * 60L * 10L); 		} catch (InterruptedException e) { 			; 		} 		// Stops the scheduler. 		s.stop(); 	}  }
This example runs for ten minutes. At every minute change it will print the sad (but true) message "Another minute ticked away...".
Some other key concepts:
You can schedule how many tasks you want.
You can schedule a task when you want, also after the	scheduler has been started.
You can change the scheduling pattern of an already scheduled	task, also while the scheduler is running (reschedule	operation).
You can remove a previously scheduled task, also while the	scheduler is running (deschedule operation).
You can start and stop a scheduler how many times you want.
You can schedule from a file.
You can schedule from any source you want.
You can supply listeners to the scheduler in order to receive	events about the executed task.
You can control any ongoing task.
You can manually launch a task, without using a scheduling	pattern.
You can change the scheduler working Time Zone.
You can validate your scheduling patterns before using them	with the scheduler.
You can predict when a scheduling pattern will cause a task	execution.
Back to index
 2. Scheduling patterns
A UNIX crontab-like pattern is a string split in five space separated parts. Each part is intended as:
Minutes sub-pattern. During which minutes of	the hour should the task been launched? The values range is from 0 to	59.
Hours sub-pattern. During which hours of the	day should the task been launched? The values range is from 0 to 23.
Days of month sub-pattern. During which days	of the month should the task been launched? The values range is from 1	to 31. The special value "L" can be used to recognize the	last day of month.
Months sub-pattern. During which months of	the year should the task been launched? The values range is from 1	(January) to 12 (December), otherwise this sub-pattern allows the	aliases "jan", "feb", "mar",	"apr", "may", "jun", "jul",	"aug", "sep", "oct", "nov" and	"dec".
Days of week sub-pattern. During which days	of the week should the task been launched? The values range is from 0	(Sunday) to 6 (Saturday), otherwise this sub-pattern allows the aliases	"sun", "mon", "tue", "wed",	"thu", "fri" and "sat".
The star wildcard character is also admitted, indicating "every minute of the hour", "every hour of the day", "every day of the month", "every month of the year" and "every day of the week", according to the sub-pattern in which it is used.
Once the scheduler is started, a task will be launched when the five parts in its scheduling pattern will be true at the same time.
Scheduling patterns can be represented with it.sauronsoftware.cron4j.SchedulingPattern instances. Invalid scheduling patterns are cause of it.sauronsoftware.cron4j.InvalidPatternExceptions. The SchedulingPattern class offers also a static validate(String) method, that can be used to validate a string before using it as a scheduling pattern.
Some examples:
5 * * * *
 This pattern causes a task to be launched once every hour, at the begin of the fifth minute (00:05, 01:05, 02:05 etc.).
* * * * *
 This pattern causes a task to be launched every minute.
* 12 * * Mon
 This pattern causes a task to be launched every minute during the 12th hour of Monday.
* 12 16 * Mon
 This pattern causes a task to be launched every minute during the 12th hour of Monday, 16th, but only if the day is the 16th of the month.
Every sub-pattern can contain two or more comma separated values.
59 11 * * 1,2,3,4,5
 This pattern causes a task to be launched at 11:59AM on Monday, Tuesday, Wednesday, Thursday and Friday.
Values intervals are admitted and defined using the minus character.
59 11 * * 1-5
 This pattern is equivalent to the previous one.
The slash character can be used to identify step values within a range. It can be used both in the form */c and a-b/c. The subpattern is matched every c values of the range 0,maxvalue or  a-b.
*/5 * * * *
 This pattern causes a task to be launched every 5 minutes (0:00, 0:05, 0:10, 0:15 and so on).
3-18/5 * * * *
 This pattern causes a task to be launched every 5 minutes starting from the third minute of the hour, up to the 18th (0:03, 0:08, 0:13, 0:18, 1:03, 1:08 and so on).
*/15 9-17 * * *
 This pattern causes a task to be launched every 15 minutes between the 9th and 17th hour of the day (9:00, 9:15, 9:30, 9:45 and so on... note that the last execution will be at 17:45).
All the fresh described syntax rules can be used together.
* 12 10-16/2 * *
 This pattern causes a task to be launched every minute during the 12th hour of the day, but only if the day is the 10th, the 12th, the 14th or the 16th of the month.
* 12 1-15,17,20-25 * *
 This pattern causes a task to be launched every minute during the 12th hour of the day, but the day of the month must be between the 1st and the 15th, the 20th and the 25, or at least it must be the 17th.
Finally cron4j lets you combine more scheduling patterns into one, with the pipe character:
0 5 * * *|8 10 * * *|22 17 * * *
 This pattern causes a task to be launched every day at 05:00, 10:08 and 17:22.
Back to index
 3. How to schedule, reschedule and deschedule a task
The simplest manner to build a task is to implement the well-known java.lang.Runnable interface. Once the task is ready, it can be scheduled with the it.sauronsoftware.cron4j.Scheduler.schedule(String, Runnable) method. This method throws an it.sauronsoftware.cron4j.InvalidPatternException when the supplied string does not represent a valid scheduling pattern.
Another way to build a task is to extend the it.sauronsoftware.cron4j.Task abstract class, which is more powerful and let the developer access some other cron4j features. This is better discussed in the "Building your own task" paragraph. Task instances can be scheduled with the schedule(String, Task) and the schedule(SchedulingPattern, Task) methods.
Scheduling methods available in the scheduler always return an ID used to recognize and retrieve the scheduled operation. This ID can be used later to reschedule the task (changing its scheduling pattern) with the reschedule(String, String) or the reschedule(String, SchedulingPattern) methods, and to deschedule the task (remove the task from the scheduler) with the deschedule(String) method.
The same ID can also be used to retrieve the scheduling pattern associated with a scheduled task, with the getSchedulingPattern(String) method, or to retrieve the task itself, with the getTask(String) method.
Back to index
 4. How to schedule a system process
System processes can be easily scheduled using the ProcessTask class:
ProcessTask task = new ProcessTask("C:\\Windows\\System32\\notepad.exe"); Scheduler scheduler = new Scheduler(); scheduler.schedule("* * * * *", task); scheduler.start(); // ... 
Arguments for the process can be supplied by using a string array instead of a single command string:
String[] command = { "C:\\Windows\\System32\\notepad.exe", "C:\\File.txt" }; ProcessTask task = new ProcessTask(command); // ...
Environment variables for the process can be supplied using a second string array, whose elements have to be in the NAME=VALUE form:
String[] command = { "C:\\tomcat\\bin\\catalina.bat", "start" }; String[] envs = { "CATALINA_HOME=C:\\tomcat", "JAVA_HOME=C:\\jdks\\jdk5" }; ProcessTask task = new ProcessTask(command, envs); // ...
The default working directory for the process can be changed using a third parameter in the constructor:
String[] command = { "C:\\tomcat\\bin\\catalina.bat", "start" }; String[] envs = { "CATALINA_HOME=C:\\tomcat", "JAVA_HOME=C:\\jdks\\jdk5" }; File directory = "C:\\MyDirectory"; ProcessTask task = new ProcessTask(command, envs, directory); // ...
If you want to change the default working directory but you have not any environment variable, the envs parameter of the constructor can be set to null:
ProcessTask task = new ProcessTask(command, null, directory);
When envs is null the process inherits every environment variable of the current JVM:
Environment variables and the working directory can also be set by calling the setEnvs(String[]) and setDirectory(java.io.File) methods.
The process standard output and standard error channels can be redirected to files by using the setStdoutFile(java.io.File) and setStderrFile(java.io.File) methods:
ProcessTask task = new ProcessTask(command, envs, directory); task.setStdoutFile(new File("out.txt")); task.setStderrFile(new File("err.txt"));
In a siminal manner, the standard input channel can be read from an existing file, calling the setStdinFile(java.io.File) method:
ProcessTask task = new ProcessTask(command, envs, directory); task.setStdinFile(new File("in.txt"));
 5. How to schedule processes from a file
The cron4j scheduler can also schedule a set of processes from a file.
You have to prepare a file, very similar to the ones used by the UNIX crontab, and register it in the scheduler calling the scheduleFile(File) method. The file can be descheduled by calling the descheduleFile(File) method. Scheduled files can be retrieved by calling the getScheduledFiles() method.
Scheduled files are parsed every minute. The scheduler will launch every process declared in the file whose scheduling pattern matches the current system time.
Syntax rules for cron4j scheduling files are reported in the "Cron parser" paragraph.
Back to index
 6. Building your own task
A java.lang.Runnable object is the simplest task ever possible, but to gain control you need to extend the it.sauronsoftware.cron4j.Task class. In the plainest form, implementing Runnable or extending Task are very similar operations: while the first requires a run() method, the latter requires the implementation of execute(TaskExecutionContext). The execute(TaskExecutionContext) method provides a it.sauronsoftware.cron4j.TaskExecutionContext instance, which the Runnable.run() method does not provide. The context can be used in the following ways:
A task can communicate with its executor, by notifying its	internal state with a textual description. This is called status	tracking. If you are interested in supporting status tracking in your	task, you have to override the supportsStatusTracking()	method, which should return true. Once this has been done,	within the execute(TaskExecutionContext) method you are	enabled to call the context setStatusMessage(String)	method. This will propagate your task status message to its executor.	The status message, through the executor, can be retrieved by an	external user (see the "
A task can communicate with its executor, by notifying its	completeness level with a numeric value. This is called completeness	tracking. If you are interested in supporting completeness tracking in	your task, you have to override the supportsCompletenessTracking()	method, which should return true. Once this has been done,	within the execute(TaskExecutionContext) method you are	enabled to call the context setCompleteness(double)	method, with a value between 0 and 1. This will propagate your task	completeness level to its executor. The completeness level, through the	executor, can be retrieved by an external user (see the "
A task can be optionally paused. If you are interested in	supporting pausing and resuming in your task, you have to override the	 canBePaused()	method, which should return true. Once this has been done,	within the execute(TaskExecutionContext) method you have to	periodically call the context pauseIfRequested()	method. This will pause the task execution until it will be resumed (or	stopped) by an external user (see the "
A task can be optionally stopped. If you are interested in	supporting stopping in your task, you have to override the canBeStopped()	method, which should return true. Once this has been done,	within the execute(TaskExecutionContext) method you have to	periodically call the context isStopped()	method. This will return true when the execution has be	demanded to be stopped by an external user (see the "
Through the context, the task can retrieve the scheduler,	calling getScheduler().
Through the context, the task can retrieve its executor, calling	 getTaskExecutor().
A custom task can be scheduled, launched immediately or returned by a task collector.
Back to index
 7. Building your own collector
You can build and plug within the scheduler your own task source, via the task collector API.
The cron4j scheduler supports the registration of one or more it.sauronsoftware.cron4j.TaskCollector instances, with the addTaskCollector(TaskCollector) method. Registered collectors can be retrieved with the scheduler getTaskCollectors() method. A previously registered collector can be removed from the scheduler with the removeTaskCollector(TaskCollector) method. Collectors can be added, queried or removed at every moment, also when the scheduler is started and it is running.
Each registered task collector is queried by the scheduler once a minute. The scheduler calls the collector getTasks() method. The implementation must return a it.sauronsoftware.cron4j.TaskTable instance. A TaskTable is a table that associates tasks and scheduling patterns. The scheduler, once the table has been retrieved, will examine the reported entries, and it will execute every task whose scheduling pattern matches the current system time.
A custom collector can be used to tie the scheduler with an external task source, i.e. a database or a XML file, which can be managed and changed in its contents also at run time.
Back to index
 8. Building your own scheduler listener
The it.sauronsoftware.cron4j.SchedulerListener API can be used to listen to scheduler events.
The SchedulerListener interface requires the implementation of the following methods:
taskLaunching(TaskExecutor)
	This one is called every time a task is launched by the scheduler.
taskSucceeded(TaskExecutor)
	This one is called every time a task execution has been successfully	completed.
taskFailed(TaskExecutor,	Throwable)
	This one is called every time a task execution fails due to an uncaught	exception.
See the "
Once your SchedulerListener instance is ready, you can register it on a Scheduler object by calling its addSchedulerListener(SchedulerListener) method. Already registered listeners can be removed by calling the removeSchedulerListener(SchedulerListener) method. The scheduler can also give back any registered listener, with the getSchedulerListeners() method.
SchedulerListeners can be added and removed at every moment, also while the scheduler is running.
Back to index
 9. Executors
The scheduler, once it has been started and it is running, can be queried to give back its executors. An executor is similar to a thread. Executors is used by the scheduler to execute tasks.
By calling the Scheduler.getExecutingTasks() method you can obtain the currently ongoing executors.
You can also obtain an executor through a SchedulerListener instance (see the "Building your own scheduler listener" paragraph).
Each executor, represented by a it.sauronsoftware.cron4j.TaskExecutor instance, performs a different task execution.
The task can be retrieved with the getTask() method.
The executor status can be checked with the isAlive() method: it returns true if the executor is currently running.
If the executor is running, the current thread can be paused until the execution will be completed, calling the join() method.
The supportsStatusTracking() method returns true if the currently executing task supports status tracking. It means that the task communicates to the executor its status, represented by a string. The current status message can be retrieved by calling the executor getStatusMessage() method.
The supportsCompletenessTracking() method returns true if the currently executing task supports completeness tracking. It means that the task communicates to the executor its own completeness level. The current completeness level can be retrieved by calling the executor getCompleteness() method. Returned values are between 0 (task just started and still nothing done) and 1 (task completed).
The canBePaused() method returns true if the currently executing task supports execution pausing. It means that the task execution can be paused by calling the executor pause() method. The pause status of the executor can be checked with the isPaused() method. A paused executor can be resumed by calling its resume() method.
The canBeStopped() method returns true if the currently executing task supports execution interruption. It means that the task execution can be stopped by calling the executor stop() method. The interruption status of the executor can be checked with the isStopped() method. Stopped executors cannot be resumed.
The getStartTime() method returns a time stamp reporting the start time of the executor, or a value less than 0 if the executor has not been yet started.
The getScheduler() method returns the scheduler which is the owner of the executor.
The getGuid() method returns a textual GUID for the executor.
Executors offer also an event-driven API, through the it.sauronsoftware.cron4j.TaskExecutorListener class. A TaskExecutorListener can be added to a TaskExecutor with its addTaskExecutorListener(TaskExecutorListener) method. Listeners can be removed with the removeTaskExecutorListener(TaskExecutorListener) method, and they can also be retrieved with the getTaskExecutorListeners() method. A TaskExecutorListener must implement the following methods:
executionPausing(TaskExecutor)
	Called when the executor is requested to pause the ongoing task. The	given parameter represents the source TaskExecutor instance.
executionResuming(TaskExecutor)
	Called when the executor is requested to resume the execution of the	previously paused task. The given parameter represents the source TaskExecutor	instance.
executionStopping(TaskExecutor)
	Called when the executor is requested to stop the task execution. The	given parameter represents the source TaskExecutor instance.
executionTerminated(TaskExecutor,	Throwable)
	Called when the executor has completed the task execution. The first	parameter represents the source TaskExecutor instance, while	the second is the optional exception that has caused the task to be	terminated. If the task has been completed successfully, the given	value is null.
statusMessageChanged(TaskExecutor,	String)
	Called every time the execution status message changes. The first	parameter represents the source TaskExecutor instance, while	the second is the new message issued by the task.
completenessValueChanged(TaskExecutor,	double)
	Called every time the execution completeness value changes. The first	parameter represents the source TaskExecutor instance, while	the second is the new completeness value (between 0 and 1) issued by	the task.
Back to index
 10. Manual task launch
If the scheduler is started and running, it is possible to manually launch a task, without scheduling it with a pattern. The method is Scheduler.launch(Task). The task will be immediately launched, and a TaskExecutor instace is returned to the caller. The returned object can be used to control the task execution (see the "
Back to index
 11. Working with Time Zones
Scheduler instances, by default, work with the system default Time Zone. I.e. a scheduling pattern whose value is 0 2 * * * will activate its task at 02:00 AM according to the default system Time Zone. The scheduler can be requested to work with a different Time Zone, which is not the system default one. Call Scheduler.setTimeZone(TimeZone) and Scheduler.getTimeZone() to control this feature.
Once the default Time Zone has been changed, system current time is adapted to the supplied zone before comparing it with registered scheduling patterns. The result is that any supplied scheduling pattern is treated according to the specified Time Zone. Suppose this situation:
System time: 10:00
System time zone: GMT+1
Scheduler time zone: GMT+3
The scheduler, before comparing system time with patterns, translates 10:00 from GMT+1 to GMT+3. It means that 10:00 becomes 12:00. The resulted time is then used by the scheduler to activate tasks. So, in the given configuration at the given moment, any task scheduled as 0 12 * * * will be executed, while any 0 10 * * * will not.
Back to index
 12. Daemon threads
The Java Virtual Machine exits when the only threads running are all daemon threads. The cron4j scheduler can be configured to spawn only daemon threads. To control this feature call the Scheduler.setDaemon(boolean) method. This method must be called before the scheduler is started. Default value is false. To check the scheduler current daemon status call the Scheduler.isDaemon() method.
Back to index
 13. Predictor
The it.sauronsoftware.cron4j.Predictor class is able to predict when a scheduling pattern will be matched.
Suppose you want to know when the scheduler will execute a task scheduled with the pattern 0 3 * jan-jun,sep-dec mon-fri. You can predict the next n execution of the task using a Predictor instance:
String pattern = "0 3 * jan-jun,sep-dec mon-fri"; Predictor p = new Predictor(pattern); for (int i = 0; i < n; i++) { 	System.out.println(p.nextMatchingDate()); }
Back to index
 14. Cron parser
The it.sauronsoftware.cron4j.CronParser class can be used to parse crontab-like formatted file and character streams.
If you want to schedule a list of tasks declared in a crontab-like file you don't need the CronParser, since you can do it by adding the file to the scheduler, with the Scheduler.scheduleFile(File) method.
Consider to use the CronParser if the Scheduler.scheduleFile(File) method is not enough for you. In example, you may need to fetch the task list from a remote source which is not representable as a java.io.File object (a document on a remote server, a DBMS result set and so on). To solve the problem you can implement your own it.sauronsoftware.cron4j.TaskCollector, getting the advantage of the CronParser to easily parse any crontab-like content.
You can parse a whole file/stream, but you can also parse a single line.
A line can be empty, can contain a comment or it can be a scheduling line.
A line containing no characters or a line with only space characters is considered an empty line.
A line whose first non-space character is a number sign (#) is considered a comment.
Empty lines and comment lines are ignored by the parser.
Any other kind of line is parsed as a scheduling line.
A valid scheduling line respects the following structure:
scheduling-pattern [options] command [args]
scheduling-pattern is a valid scheduling pattern,	according with the definition given by the it.sauronsoftware.cron4j.SchedulingPattern	class.
options is a list of optional information used by	cron4j to prepare the task execution environment. See below for a more	detailed description.
command is a system valid command, such an executable	call.
args is a list of optional arguments for the command.
After the scheduling pattern item, other tokens in each line are space separated or delimited with double quotation marks (").
Double quotation marks delimited items can take advantage of the following escape sequences:
\" - quotation mark
\\ - back slash
\/ - slash
\b - back space
\f - form feed
\n - new line
\r - carriage return
\t - horizontal tab
\ufour-hex-digits - the character at the given	Unicode index
The options token collection can include one or more of the following elements:
IN:file-path - Redirects the command standard input	channel to the specified file.
OUT:file-path - Redirects the command standard output	channel to the specified file.
ERR:file-path - Redirects the command standard error	channel to the specified file.
ENV:name=value - Defines an environment	variable in the scope of the command.
DIR:directory-path - Sets the path of the working	directory for the command. This feature is not supported if the	executing JVM is less than 1.3.
It is also possible to schedule the invocation of a method of a Java class in the scope of the parser ClassLoader. The method has to be static and it must accept an array of strings as its sole argument. To invoke a method of this kind the syntax is:
scheduling-pattern java:className#methodName [args]
The #methodName part can be omitted: in this case the main(String[]) method will be assumed.
Please note that static methods are invoked within the scheduler same JVM, without spawning any external process. Thus IN, OUT, ERR, ENV and DIR options can't be applied.
Invalid scheduling lines are discarded without blocking the parsing procedure, but an error message is sent to the application standard error channel.
Valid examples:
0 5 * * * sol.exe 0,30 * * * * OUT:C:\ping.txt ping 10.9.43.55 0,30 4 * * * "OUT:C:\Documents and Settings\Carlo\ping.txt" ping 10.9.43.55 0 3 * * * ENV:JAVA_HOME=C:\jdks\1.4.2_15 DIR:C:\myproject OUT:C:\myproject\build.log C:\myproject\build.bat "Nightly Build" 0 4 * * * java:mypackage.MyClass#startApplication myOption1 myOption2


华梦�?/a> 2016-05-07 15:39 发表评论


Sat, 30 Apr 2016 13:11:00 GMT
阉K��云Linux安装软�g镜像�?/span>
阉K��云是最�q�新出的一个镜像源。得益与阉K��云的高速发展，�q�么大的需求，肯定会推�������q��镜像源�?br style="padding: 0px; margin: 0px;" />阉K��云Linux安装镜像源地址�Q�http://mirrors.aliyun.com/
CentOS�pȝ��更换软�g安装�?br style="padding: 0px; margin: 0px;" />�W�一步：备䆾你的原镜像文�Ӟ��以免出错后可以恢复�?/p>
mv /etc/yum.repos.d/CentOS-Base.repo /etc/yum.repos.d/CentOS-Base.repo.backup
�W�二步：下蝲新的CentOS-Base.repo �?etc/yum.repos.d/
CentOS 5
wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-5.repo
CentOS 6
wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-6.repo
�W�三步：�q�行yum makecache生成�~�存
yum clean all
yum makecache


华梦�?/a> 2016-04-30 21:11 发表评论


Wed, 23 Mar 2016 07:15:00 GMT
 yum -y update
centos6 mysql5.5 yum安装
  
 
默认使用centos yum安装的mysql不是5.5版本的，我们需要增加两个新的repo
rpm -Uvh http://mirror.steadfast.net/epel/6/i386/epel-release-6-8.noarch.rpm
rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
centos6下php php-fpm的yum安装
查看一下是不是有mysql 5.5�?/div>
yum --enablerepo=remi,remi-test list mysql mysql-server
安装mysql5.5
yum --enablerepo=remi,remi-test install mysql mysql-server
启动mysql5.5
/etc/init.d/mysqld start
讄���开机启�?/div>
chkconfig --levels 345 mysqld on
要启用MySQL 安全讄���误���入以下命�?/div>
/usr/bin/mysql_secure_installation


CentOS/RHEL 7.x:
rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm rpm -Uvh https://mirror.webtatic.com/yum/el7/webtatic-release.rpm
CentOS/RHEL 6.x:
rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm rpm -Uvh https://mirror.webtatic.com/yum/el6/latest.rpm
CentOS/RHEL 5.x:
rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-5.noarch.rpm rpm -Uvh http://mirror.webtatic.com/yum/el5/latest.rpm
Now you can install PHP 5.5’s mod_php SAPI (along with an opcode cache) by doing:
yum install php55w php55w-opcache
You can alternatively install PHP 5.5’s php-fpm SAPI (along with an opcode cache by doing:




  rpm -Uvh http://mirror.webtatic.com/yum/el6/latest.rpm
  

rpm -Uvh https://mirror.webtatic.com/yum/el7/epel-release.rpm
rpm -Uvh https://mirror.webtatic.com/yum/el7/webtatic-release.rpm
如果惛_��除上面安装的包，重新安装
rpm -qa | grep webstatic
rpm -e  上面搜烦到的包即�?/div>
3.�q�行yum install
  yum install php55w php55w-cli php55w-common php55w-gd php55w-ldap php55w-mbstring php55w-mcrypt php55w-mysql php55w-pdo php55w-xml
yum install php56w php56w-cli php56w-common php56w-gd php56w-ldap php56w-mbstring php56w-mcrypt php56w-mysql php56w-pdo php56w-xml

php 另外一�U�方�?br /> Remi官方�|�站�Q�http://rpms.famillecollet.com/
��d��Remi源，不管32位还�?4位的�pȝ���Q�运行下面命令：
rpm -ivh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
 Remi源默认是没有启用的，我们来启用Remi源，修改 /etc/yum.repos.d/remi.repo 文�g�Q�把文�g内的 enabled=0 改�ؓ enabled=1 �Q�注意：�Ҏ��件内�?�?enabled=0 我们修改 [remi]下面的，不要修改[remi-test]下面的�?/div>
 到这里yum源的配置�l�束�Q�下面安装��Y件就���单了。安装时候有询问y/n的时候都是y
安装php,php-fpm以及php扩展�Q?/div>
yum install php php-fpm php-bcmatch php-gd php-mbstring php-mcrypt php-mysql php-pdo   php-dom


wget https://files.phpmyadmin.net/phpMyAdmin/4.0.10.15/phpMyAdmin-4.0.10.15-english.zip
 


华梦�?/a> 2016-03-23 15:15 发表评论

99re热久久这里只有精品34,亚洲午夜精品久久久久久久久久久久,1769视频在线播放免费观看

nlog安装

mysql zip 安装5.7

REST API URI设计

URIs

规则2�Q�正斜杠分隔�W�（/�Q�必��ȝ��来指�C�层�U�关�p?/h2>
URI的�\径中的正斜杠�Q?�Q�字�W�用于指�C��源之间的层次关系�?/p>
例如�Q?nbsp;
(http://api.canvas.com/shapes/polygons/quadrilaterals/squares �Q?/p>

�l�论

restful

1、概�q?/h2>
activiti�pȝ��一共有23个表�Q�包括流�E�定义表、一般数据信息表、流�E�运行实例表、流�E�历史记录表、用��L��L��表�?/p>

4、一般数�?/h2>
1、ACT_GE_BYTEARRAY�Q�字节数据表�Q?/p>
名称�Q�NAME_�Q�、部�|�Id�Q�DEPLOYMENT_ID_�Q�、字节数据（BYTES_�Q�、发生的�Q�GENERATED_�Q?/p>
2、ACT_GE_PROPERTY�Q�一般属性表�Q?/p>
名称�Q�NAMe_�Q�、�?VALUe_)

jpa 字段不要映射

SNMP 相关

Druid 介绍

Druid可以做什么？

设计

��?/h3>

Druid提供了强大的监控功能�Q�能够监控连接池行�ؓ和SQL执行情况�Q�让你能够详�l�了解应用的数据库访问行为�?/p>

监控对象

spring 相关�|�站介绍

mysql导入��q��

输入数据�q�行正态化

对输入数据进行正态化

cron4j使用说明

1. Quickstart

2. Scheduling patterns

3. How to schedule, reschedule and deschedule a task

4. How to schedule a system process

5. How to schedule processes from a file

6. Building your own task

7. Building your own collector

8. Building your own scheduler listener

9. Executors

10. Manual task launch

11. Working with Time Zones

12. Daemon threads

13. Predictor

14. Cron parser

99re热久久这里只有精品34,亚洲午夜精品久久久久久久久久久久,1769视频在线播放免费观看

nlog安装

mysql zip 安装5.7

REST API URI设计

URIs

规则2�Q�正斜杠分隔�W�（/�Q�必��ȝ��来指�C�层�U�关�p?/h2>URI的�\径中的正斜杠�Q?�Q�字�W�用于指�C����源之间的层次关系�?/p>例如�Q?nbsp;(http://api.canvas.com/shapes/polygons/quadrilaterals/squares �Q?/p>

�l�论

restful

1、概�q?/h2>activiti�pȝ��一共有23个表�Q�包括流�E�定义表、一般数据信息表、流�E�运行实例表、流�E�历史记录表、用��L����L��表�?/p>

4、一般数�?/h2>1、ACT_GE_BYTEARRAY�Q�字节数据表�Q?/p>名称�Q�NAME_�Q�、部�|�Id�Q�DEPLOYMENT_ID_�Q�、字节数据（BYTES_�Q�、发生的�Q�GENERATED_�Q?/p>2、ACT_GE_PROPERTY�Q�一般属性表�Q?/p>名称�Q�NAMe_�Q�、�?VALUe_)

jpa 字段不要映射

SNMP 相关

Druid 介绍

Druid可以做什么？

设计

����?/h3> Druid提供了强大的监控功能�Q�能够监控连接池行�ؓ和SQL执行情况�Q�让你能够详�l�了解应用的数据库访问行为�?/p>

监控对象

spring 相关�|�站介绍

mysql导入��q��

输入数据�q�行正态化

对输入数据进行正态化

cron4j使用说明

1. Quickstart

2. Scheduling patterns

3. How to schedule, reschedule and deschedule a task

4. How to schedule a system process

5. How to schedule processes from a file

6. Building your own task

7. Building your own collector

8. Building your own scheduler listener

9. Executors

10. Manual task launch

11. Working with Time Zones

12. Daemon threads

13. Predictor

14. Cron parser

规则2�Q�正斜杠分隔�W�（/�Q�必��ȝ��来指�C�层�U�关�p?/h2>
URI的�\径中的正斜杠�Q?�Q�字�W�用于指�C��源之间的层次关系�?/p>
例如�Q?nbsp;
(http://api.canvas.com/shapes/polygons/quadrilaterals/squares �Q?/p>

1、概�q?/h2>
activiti�pȝ��一共有23个表�Q�包括流�E�定义表、一般数据信息表、流�E�运行实例表、流�E�历史记录表、用��L��L��表�?/p>

4、一般数�?/h2>
1、ACT_GE_BYTEARRAY�Q�字节数据表�Q?/p>
名称�Q�NAME_�Q�、部�|�Id�Q�DEPLOYMENT_ID_�Q�、字节数据（BYTES_�Q�、发生的�Q�GENERATED_�Q?/p>
2、ACT_GE_PROPERTY�Q�一般属性表�Q?/p>
名称�Q�NAMe_�Q�、�?VALUe_)

��?/h3>

Druid提供了强大的监控功能�Q�能够监控连接池行�ؓ和SQL执行情况�Q�让你能够详�l�了解应用的数据库访问行为�?/p>