无码一区二区三区视频,亚洲一区二三区,亚洲精品大片

�|��\��L��@BlogJava — Tue, 08 Mar 2011 13:40:00 GMT

Extend the migration logic

扩展�q�移逻辑

The migration logic is written in such a way, that it is easy to extend to suit your needs. The source code is available as a Maven 2 project in the srcsubfolder of the downloaded zip file. To build a new zip file, after having changed or extended the logic, simply execute a

�q�移逻辑可以�~�写�Q�以便轻村֜�满��你的需求。源代码在所下蝲zip文�g里src子文件夹里作一个Maven 2��目来��用。�ؓ了构��Z��个新的zip文�g�Q�在已经改变或者扩展逻辑之后�Q�简单执行下面指�?/p>

mvn clean install

to produce a new zip file in the target folder.

在target文�g下��生一个新的zip文�g�?

Following picture gives a high-level overview of the classes in the migration logic.

下图提供了在�q�移逻辑里类的高层次概貌�?

Both the ProcessConversion and ProcessDataMigration classes have a main method that directly is called from the ant build script in the root of the migration zip.
ProcessConversion and ProcessDataMigration �q�两个类都有在迁�U�zip的根目录下的ant构徏脚本里调用的main�Ҏ��?
These classes construct a ServiceFactory based on the two properties files, using a static factory method
通过使用静态的工厂�Ҏ��Q�基于两个properties文�g�q�些�c�L��Z��?strong>ServiceFactory

ServiceFactory.configureFromProperties(jbpmDbProperties, activitiDbProperties);

The services are constructed by the ServiceFactory (eg. getProcessConversionService()) and are used to execute the migration logic:
通过ServiceFactory (eg. getProcessConversionService())构徏�q�些服务�Q�这些服务被用来执行�q�移逻辑�Q?/li>

 1 public void execute() throws IOException {

 2     

 3   // convert processes

 4   ServiceFactory serviceFactory = createServiceFactory();

 5   ProcessConversionService processConversionService = serviceFactory.getProcessConversionService();

 6   Map<String, Document> migratedProcesses = processConversionService.convertAllProcessDefinitions();

 7   

 8   // write results to bpmn20.xml files

 9   writeConvertedProcesses(migratedProcesses, workingDir);

10     

11   // Deploy processes to Activiti

12   ActivitiService activitiService = serviceFactory.getActivitiService();

13   activitiService.deployConvertedProcesses(migratedProcesses);

14     

15   // data migration

16   

17 }

The ProcessConversionService is an interface that contains process conversion and process definition data retrievel operations. It uses an implementation of Jbpm3Dao. The default implementation of this class uses a Hibernate SessionFactory to retrieve all the data from jBPM 3 tables.

The ActivitiService offers operation needed to get the migrated data in the Activiti tables. For example, deploying the converted process definitions is such an operation

ProcessConversionService 是一个包含流�E��{换和数据��索的��程定义借口。它使用�?Jbpm3Dao.的实现。这个类的缺省实��C��用了Hibernate�?strong>SessionFactory从jBPM 3的数据库表里��索所有的数据�?

ActivitiService 提供需要从Activiti数据库表�q�移数据的操作。例如，部��v转换之后的流�E�定义就是如此的操作�?

All these dependencies, ProcessConversionService, Jbpm3Dao, Sessionfactory, ActivitiService and ProcessEngine, are interfaces and can be implemented by your own implementation. You can inject them into the ServiceFactory using regular JavaBean setters. When no such custom implementation is set, the ServiceFactory will fall back to creating the default implementation:
所有这些依赖， ProcessConversionService, Jbpm3Dao, Sessionfactory, ActivitiService �?ProcessEngine都是接口�Q��ƈ能由你自己实现。采用正常的JavaBean讄��器，能将它们注入到ServiceFactory。当没有讄��q�些实现�Q�ServiceFactory��后退一步，建立�~�省的实玎ͼ�

    1 public ProcessConversionService getProcessConversionService() {
 2   if (processConversionService == null) {

 3     this.processConversionService = createDefaultProcessConversionService();

 4   } 

 5   return processConversionService;

 6 }

 7 

 8 protected ProcessConversionService createDefaultProcessConversionService() {

 9   ProcessConversionServiceImpl service = new ProcessConversionServiceImpl(getJbpm3Dao());

10   return service;

11 }

�|��\��L��@BlogJava 2011-03-08 21:40 发表评论

�|��\��L��@BlogJava — Mon, 07 Mar 2011 15:23:00 GMT

Chapter 18. JBPM Migration�Q�JBPM �q�移�Q?/strong>

Table of Contents

目录�?

Database migration

数据�q�移

Process conversion

��程转换

Extend the migration logic

扩展�q�移逻辑

The jBPM migration is considered [EXPERIMENTAL].

jBPM�q�移仅作[EXPERIMENTAL]之用�?

It is possible to migrate an existing installation of jBPM version 3 to Activiti. The migration includes both process definition conversion (ie. from JPDL 3 to BPMN 2.0) and data migration.

��一个已安装的jBPM 版本3�q�移到Activiti是有可能的。迁�U�d��括流�E�定义�{换（例如从JPDL3到BPMN 2.0�Q�和数据�q�移�?

The migration tool is currently offered as a 'preview' only! The migration coverage is at this point in time not sufficient to be usable on production process definitions and databases. Also note that the migration is a 'best effort', which means that you may need to extend the migration logic to cover all your use cases.

�q�移工具目前只作�?#8216;预览’之用�Q?/strong>当前�q�移不能覆盖��C�品的��程定义和数据。也要注意迁�U�L��‘最大的努力’�Q�这意味着你可以需�?#8216;扩展�q�移逻辑’来控制你所有的用例�?

The migration tool is separately availbale as a zip file from the activiti.org download site. Once you have unzipped this file, you will see following files and folders:

�q�移工具�?a >activiti.org下蝲站点以zip文�g方式分开下蝲。一旦加压这个文�Ӟ��文�g和文件夹如下所�C�：

build.xml: This ant buildfile contains the targets to execute the process definition conversion and database migration.

build.xml: �q�个ant构徏文�g包含了执行流�E�定义�{换和数据库迁�Uȝ��目标�?

activiti.db.properties and jbpm3.db.properties: these properties files contain the database connection parameters for the jBPM 3 and Activiti database. These properties files must be changed when executing a database migration.

activiti.db.properties and jbpm3.db.properties:�q�个�Ҏ��文件包含了jBPM和Activiti数据库的数据库连接参数。当执行数据库迁�U�L��Q�必��L��变这些特性文件�?

processes: when running a process definition conversion, the jBPM 3 process definition files must be placed in this folder.

processes:当运�?a href="file:///G:/index.html#processConversion">��程定义转换�Ӟ��jBPM3��程定义文�g必须攄��到这个文件夹�?

src: this folder contains the source code of the migration tool. Read the extension section if you want to tailor or extend the migration code to your needs.

src:�q�个文�g包含�q�移工具的源代码。如果希望裁剪或者扩展迁�U�M��码满��你自己的需求，请阅�?a href="file:///G:/index.html#extendMigration">扩展部分�?

lib: this folder contains all jars required to execute the migration logic.

lib:�q�个文�g夹包含执行迁�U�逻辑的全部jar包�?/li>

Database migration

数据库迁�U?/strong>

It is possible to migrate the data in the jBPM 3 database tables to the Activiti database schema. To do this, following properties files must be changed to point at the right database:

��jBPM3数据库表�q�移到Activiti数据库schema是有可能的。�ؓ了完成这个�Q务，必须改变下面的properties文�g�Q�指向正��的数据库：

jbpm3.db.properties: contains the parameters to connect to the jBPM 3 database. Also the Hibernate dialect must be provided.

jbpm3.db.properties:包含了连接jBPM3数据库的参数。也必须提供Hibernate方言�?

activiti.db.properties: contains the parameters to connect to database to which the migrated data will be written. This can be the same database schema as the jBPM schema (ie. there are no name-clashes between jBPM and Activiti tables, indexes, foreign keyes, etc).

activiti.db.properties: 包含了迁�U�d��要写入数据库的连接参数。这个可能是和jBPM相同数据库schema�Q�例如，在jBPM和Activiti数据库表名，索引名，外键名等�{�没有冲�H�）.

The database migration will use the data in the jBPM 3 tables to:

数据�q�移��用jBPM3数据库表的数据来做：

Convert the process definition to the BPMN 2.0 counterpart. This means that the converted process definition will be deployed to the Activiti tables as part of the migration. As a side-effect, it will also produce the BPMN 2.0 XML files, similar to what happens when executing theprocess conversion.

转换��程定义为BPMN 2.0对应物。这意味着转换之后的流�E�定义将作�ؓ�q�移的一部分被部�|�到Activiti的数据库表。作为副作用�Q�它也��生BPMN 2.0 XML文�g�Q�这和当执行��程转换时所发生的事�怼��?

Migrate runtime and history data of the processes to the Activiti tables. In this release, this is not yet implemented!

�q�移��程的运行时和历史数据到Activiti数据库表�?strong>本次发布�Q�这没有实现�Q?/strong>

The data is retrieved from the jBPM 3 tables using Hibernate queries and the Hibernate mappings of jBPM itself.

使用Hibernate查询和jBPM自��n的Hibernate�?

��，可以从jBPM 3数据库表里检索到�q�些数据�?

Process conversion

��程转换

It is possible to only convert the process definitions xml from JPDL to BPMN 2.0 that can be executed on the Activiti engine. To do this, place the jBPM 3 processes inside the processes folder. There can be any number of (nested) subfolders, the tool will scan every (sub)folder inside processes to discover processdefinition.xml files (file name must be processdefinition.xml!).

只将JPDL的流�E�定义xml转换��在Activiti引擎执行的BPMN 2.0是有可能的。�ؓ了完成这个�Q务，请将jBPM 3攄��到process 文�g夏V��可以有��M��数量�Q�内�|�）子文件夹�Q�工具将扫描process每个�Q�子�Q�文件夹�Q�来发现processdefinition.xml文�g�Q�文件名必须是processfinition.xml!�Q��?

The discovered processes will be parsed and deployed to an in-memory databse, such that the logic of reverse engineering the process definition from the jBPM deployment tables contained in the database migration is used for both cases.

被发现的��程��被解析�q��|�到一个内存数据库�Q�以便对包含在数据库�q�移的jBPM部��v数据库表的流�E�定义进行反向工�E�，以�ؓ解析和部�|�之用�?

Once the jBPM 3 processes are placed in the processes folder, execute the convert.processes target in the root of the unzipped migration tool folder:

一旦jBPM 3��程被放�|�到process文�g夹，那么执行在解压之后的�q�移工具文�g�Ҏ��目录下的convert.processes目标�?

ant convert.processes

During conversion, you will see plenty logging passing by describing where and how the process conversion is being executed. At the end of the conversion, you will see following logging appear:

在�{换过�E�中�Q�通过描述��程转换执行是何地和何时转换的方式，可以观察到大量的日志。在转换的末��，��观察到下列日志出现�Q?

As shown in the logging, the resulting BPMN 2.0 processes can be find in the converted-process-xxxx folder, where the xxxx is the timestamp of the conversion.

正如日志所�C�，BPMN 2.0��程的结果可以在converted-process-xxxx文�g多w��扑ֈ��Q�这里xxxx是�{换的旉��戟�?

In this release, only limited support for start, end, wait state and task-nodes is implemented. In the future, this coverage will expand.

在本�ơ发布里�Q�只实现了对开始，�l�束�Q�等待和��d��节点的有限支持。在��来�Q�这个覆盖范围将要扩充�?

�|��\��L��@BlogJava 2011-03-07 23:23 发表评论

[转]架构师的素质

�|��\��L��@BlogJava — Mon, 07 Mar 2011 15:18:00 GMT
     摘要: 架构师的基本素质  阅读全文

�|��\��L��@BlogJava 2011-03-07 23:18 发表评论

Grails 1.3.7 Release Notes

�|��\��L��@BlogJava — Thu, 17 Feb 2011 16:00:00 GMT

Grails 1.3.7 Release Notes

Grails is a dynamic web application framework built on Java and Groovy, leveraging best of breed APIs from the Java EE sphere including Spring, Hibernate and SiteMesh. Grails brings to Java and Groovy developers the joys of convention-based rapid development while allowing them to leverage their existing knowledge and capitalize on the proven and performant APIs Java developers have been using for years.

Changelog: See JIRA

Download: http://grails.org/Download .

Documentation: http://grails.org/doc/1.3.x

New Features & Improvements

Updated Groovy

Grails 1.3.7 now bundles Groovy 1.7.8.

Masking Request Parameters From Stacktrace Logs

When Grails logs a stacktrace, the log message may include the names and values of all of the request parameters for the current request. To mask out the values of secure request parameters, specify the parameter names in the grails.exceptionresolver.params.excludeconfig property:

grails.exceptionresolver.params.exclude = ['password', 'creditCard']

Request parameter logging may be turned off altogether by setting thegrails.exceptionresolver.logRequestParameters config property to false . The default value is true when the application is running in DEVELOPMENT mode and false for all other modes.

grails.exceptionresolver.logRequestParameters = false

�|��\��L��@BlogJava 2011-02-18 00:00 发表评论

Activiti User Guide�Q�Activiti用户指南)-Chapter 17. Activiti KickStart

�|��\��L��@BlogJava — Mon, 10 Jan 2011 12:58:00 GMT

Chapter 17. Activiti KickStart

Table of Contents

Overview�Q�概�q�ͼ�

Changing the database�Q�变更数据库�Q?

Overview�Q�概�q�ͼ�

Activiti KickStart is a webbased tool to quickly create 'adhoc' business processes using a subset of constructs available to the Activiti engine. KickStart provides a simple UI that doesn't require to learn BPMN or any modeling environment, as it works with concepts that are familiar to every business user. However, the processes that are created using KickStart, are fully BPMN 2.0 compliant and can be used as a starting point for more complex BPM endeavours.

Activiti KickStart的是一个基于Web的工��P��用Activiti引擎可用的构�Ӟ��constructs�Q�的子集提供�l�快速创�?#8220;卛_��Q�adhoc�Q?#8221;的业务流�E�。Kickstart提供了不必学习BPMN或者�Q何徏模环境的��单UI�Q�因为它树立了每个业务用户都熟悉的概��c��但是，通过KickStart创徏的的��程�Q�是和BPMN 2.0兼容�Q��ƈ可作为更为复杂BPM努力的�v炏V�?

KickStart integrates perfectly with the Activiti engine. As such, processes created with KickStart are immediataly usable in Activiti Explorer and are visible in Probe.

KickStart能和Activiti引擎完美集成。因此，采用KickStart创徏的流�E�在Activiti Explorer立即可用�Q��ƈ在Probe里面可见�?

KickStart serves many business cases, but the following three are probably the most common:

KickStart服务许多商业案例�Q�但以下三个可能是最常见�Q?

Simple business processes: some processes are just simple by nature, and every company has them. Think about an expense process, a holiday leave process, a hiring process, etc... These kind of processes are probably already being done using paper or e-mail. KickStart allows to model these processes quickly and change them whenever it is needed. As such, KickStart really lowers the threshold to automate these business processes.

��单的业务��程�Q�一些流�E�天然简单，�q�且每个公司都有。考虑��C��Ҏ��E�，请假��程�Q�雇佣流�E�，�{�等…�q�些��程用书面或者e-mail的方式已�l�完成。Kickstart�q�行快速对�q�些��程建模�Q�每当需要时改变它们。因此，Kickstart真正地降低了门槛�Q��ƈ让这些业务流�E�自动化�?

Prototyping: before diving into complex BPMN 2.0 modeling and thinking about the corner cases of the process, it is often wise to get all people involved aligned and work out a prototype that shows the vision of what needs to be done. KickStart allows to do exatcly that: create a business process prototype on the fly, to get your ideas visible for everyone.

原型�Q�在�ȝ��复杂的BPMN 2.0建模和考虑��程的偏例之前，它往往是明智的�Q�让所有参与的人��^�{�，制定一个原型来展示所要完成的愿景。KickStart的允许恰恰如此：创徏一个业务流�E�的原型�Q�让大家看到你的��x��?

Adhoc work: in some cases, coordination is required between different people or groups in a company. You know how it normally goes: sending an email here, doing a telephone there ... which often ends up in a tar pit of nobody knowing what or when something needs to be done. However, a business process management platform such as Activiti is an excellent way of distributing and follow-up everything, as it is intended to track exactly such things. KickStart allows you to create processes for adhoc work in a matter of minutes, and distribute and coordinate tasks between people easily.

卛_��工作�Q�在一些情况，在一个公叔R��Q�不同的人员或组之间的协作是必要的。您知道正常时如何运作的�Q�在�q�里发送邮�Ӟ��在那里打电话…�q�经常终止于没有人知道需要完成什么或者何时完成这��L��焦��a坑。但是，诸如Activiti�q�样的业务流�E�管理��^台是解决分发和后�l�事情的卓越解决之道�Q�因为它的目的是准确跟踪�q�些事情。Kickstart允许您在数分钟之内创建即席工作的��程�Q��ƈ在�h们之间分发和协调��d��?/li>

Following screenshots show the capabilities of Activiti KickStart. Take for example the next picture. It shows how an expense process is created in a matter of a few minutes.

下列屏幕截图展示了Activiti KickStart的能力。下图作为示例。它展示如何在几分钟之内创徏一个付�Ҏ��E��?

After clicking the save button, the process is immediately usable in Activiti Explorer:

在点�?#8220;保存”按钮之后�Q�这个流�E�立卛_��Activiti Explorer可用�?

KickStart also allows to define forms for every task:

KickStart也允��ؓ每个��d��定义表单�Q?

Which are obviously directly usable in Activiti Explorer:

�q�些明显直接在Activiti Explorer可用�Q?

At any time during process creation, it is possible to view the corresponding BPMN 2.0 diagram of the business process:

在流�E�徏立的��L��旉��Q�它可以查看相应的BPMN2.0业务��程图�?

Whenever it is required, the processes defined with KickStart can be opened up and modified:

每当它是必需�Q�与KickStart的定义的��程可被打开和修改：

Processes created with KickStart are fully compliant with the BPMN 2.0 XML, which means that the process can be imported into any BPMN 2.0 editor:

用KickStart的创建的��程是完全符合BPMN2.0的XML�Q�这意味着该流�E�可以由��M��兼容的BPMN2.0�~�辑器输入：

Changing the database�Q�变更数据库�Q?/strong>

Activiti KickStart is currently not yet using the REST API, but uses the service API by including the Activiti engine as a library. While Explorer, Probe and Cycle use the same mechanism for changing the database (see here), the same does not yet apply for KickStart.

Activiti KickStart当前�q�没有��用REST API�Q�而是通过包括了Activiti引擎作�ؓ�c�d��使用服务API。虽然Explorer�Q�Probe和Cycle使用相同的机制改变数据（参见�q�里�Q�，但这不适于KickStart�?

To change the database that KickStart uses in the demo setup, generate a new activiti.cfg.jar, and place it in the apps/apache-tomcat-6.x/webapps/activiti-kickstart/WEB-INF/lib folder.

��Z��改变演示安装里KickStart使用的数据库�Q��生一个新的activiti.cfg.jar,�q�将它放�|�到apps/apache-tomcat-6.x/webapps/activiti-kickstart/WEB-INF/lib文�g夏V�?

�|��\��L��@BlogJava 2011-01-10 20:58 发表评论

�|��\��L��@BlogJava — Sat, 08 Jan 2011 03:49:00 GMT
     摘要: 随着�W�合BPMN 2.0标准的BPMS��程引擎Activiti 5.0正式版推出，由Tijs Rademakers �?Ron Van Liempd�~�写的‘实战Activiti’书�c�昨天在“Manning Early Access Program”现�w�。目前第一章释出，可以先睹为快。呵呵，真棒�Q�本��是�W�一章之�Q?1�Q?nbsp; 阅读全文

�|��\��L��@BlogJava 2011-01-08 11:49 发表评论

�|��\��L��@BlogJava — Thu, 06 Jan 2011 13:26:00 GMT
     摘要: 随着�W�合BPMN 2.0标准的BPMS��程引擎Activiti 5.0正式版推出，由Tijs Rademakers �?Ron Van Liempd�~�写的‘实战Activiti’书�c�昨天在“Manning Early Access Program”现�w�。目前第一章释出，可以先睹为快。呵呵，真棒�Q�本��是�W�一章之�Q?0�Q?nbsp; 阅读全文

�|��\��L��@BlogJava 2011-01-06 21:26 发表评论

�|��\��L��@BlogJava — Wed, 05 Jan 2011 13:01:00 GMT
     摘要: 随着�W�合BPMN 2.0标准的BPMS��程引擎Activiti 5.0正式版推出，由Tijs Rademakers �?Ron Van Liempd�~�写的‘实战Activiti’书�c�昨天在“Manning Early Access Program”现�w�。目前第一章释出，可以先睹为快。呵呵，真棒�Q�本��是�W�一章之�Q?�Q?nbsp; 阅读全文

�|��\��L��@BlogJava 2011-01-05 21:01 发表评论

�|��\��L��@BlogJava — Tue, 04 Jan 2011 15:12:00 GMT
     摘要: 随着�W�合BPMN 2.0标准的BPMS��程引擎Activiti 5.0正式版推出，由Tijs Rademakers �?Ron Van Liempd�~�写的‘实战Activiti’书�c�昨天在“Manning Early Access Program”现�w�。目前第一章释出，可以先睹为快。呵呵，真棒�Q�本��是�W�一章之�Q?�Q?nbsp; 阅读全文

�|��\��L��@BlogJava 2011-01-04 23:12 发表评论

�|��\��L��@BlogJava — Tue, 04 Jan 2011 12:43:00 GMT
     摘要: 随着�W�合BPMN 2.0标准的BPMS��程引擎Activiti 5.0正式版推出，由Tijs Rademakers �?Ron Van Liempd�~�写的‘实战Activiti’书�c�昨天在“Manning Early Access Program”现�w�。目前第一章释出，可以先睹为快。呵呵，真棒�Q�本��是�W�一章之�Q?�Q?nbsp; 阅读全文

�|��\��L��@BlogJava 2011-01-04 20:43 发表评论