根据调试信息学习jbpm(一):jbpmConfiguration
2008-06-10 16:09
148 查看
下面是调用JbpmServiceFactory.getInstance()时后台的debug信息,我们通过学习它
就可以理解JbpmConfiguration的运作方式:
15:11:33,403 DEBUG JbpmConfiguration : jBpm configuration:
//下面是hibernate的配置信息,您可以在jbpm.properties文件中进行修改
15:11:33,423 DEBUG JbpmConfiguration : [hibernate.connection.driver_class] org.hsqldb.jdbcDriver
15:11:33,423 DEBUG JbpmConfiguration : [hibernate.connection.password]
15:11:33,433 DEBUG JbpmConfiguration : [hibernate.connection.url] jdbc:hsqldb:.
15:11:33,433 DEBUG JbpmConfiguration : [hibernate.connection.username] sa
15:11:33,483 DEBUG JbpmConfiguration : [hibernate.dialect] net.sf.hibernate.dialect.HSQLDialect
15:11:33,483 DEBUG JbpmConfiguration : [jbpm.apply.transactions] yes
//如果没有表,则系统将自动建表
15:11:33,493 DEBUG JbpmConfiguration : [jbpm.create.tables] only-if-not-present
15:11:33,493 DEBUG JbpmConfiguration : [jbpm.create.tables.log] false
//如果是升级旧的流程定义,可以修改这里的配置
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.create.tables.query] SELECT ID FROM JBPM_DEFINITION WHERE ID = 1
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.execute.actions] true
//FileMgr的方式:数据库还是文件
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.file.mgr] database
//IDGenerator的配置
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.id.generator] default
//每次申请的大小为100
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.id.generator.block.size] 100
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.id.generator.configuration] same
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.id.generator.node.id] 0
//下面是LOG的配置
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.log.default] error
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.log.package.org.jbpm] info
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.log.package.org.jbpm.persistence.hibernate] info
15:11:33,523 DEBUG JbpmConfiguration : [jbpm.log.stdout] on
//持久化的方式配置
15:11:33,523 DEBUG JbpmConfiguration : [jbpm.persistence.session.factory] hibernate
15:11:33,523 DEBUG JbpmConfiguration : [jbpm.scheduler.wait.period] 5000
15:11:33,533 DEBUG JbpmConfiguration : [jbpm.service.factory] default
15:11:33,533 DEBUG JbpmConfiguration : [jbpm.validate.xml] true
15:11:33,553 DEBUG JbpmConfiguration : for key 'jbpm.file.mgr', an object of type 'org.jbpm.persistence.filemgr.DatabaseFileMgr' was instantiated
就可以理解JbpmConfiguration的运作方式:
15:11:33,403 DEBUG JbpmConfiguration : jBpm configuration:
//下面是hibernate的配置信息,您可以在jbpm.properties文件中进行修改
15:11:33,423 DEBUG JbpmConfiguration : [hibernate.connection.driver_class] org.hsqldb.jdbcDriver
15:11:33,423 DEBUG JbpmConfiguration : [hibernate.connection.password]
15:11:33,433 DEBUG JbpmConfiguration : [hibernate.connection.url] jdbc:hsqldb:.
15:11:33,433 DEBUG JbpmConfiguration : [hibernate.connection.username] sa
15:11:33,483 DEBUG JbpmConfiguration : [hibernate.dialect] net.sf.hibernate.dialect.HSQLDialect
15:11:33,483 DEBUG JbpmConfiguration : [jbpm.apply.transactions] yes
//如果没有表,则系统将自动建表
15:11:33,493 DEBUG JbpmConfiguration : [jbpm.create.tables] only-if-not-present
15:11:33,493 DEBUG JbpmConfiguration : [jbpm.create.tables.log] false
//如果是升级旧的流程定义,可以修改这里的配置
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.create.tables.query] SELECT ID FROM JBPM_DEFINITION WHERE ID = 1
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.execute.actions] true
//FileMgr的方式:数据库还是文件
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.file.mgr] database
//IDGenerator的配置
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.id.generator] default
//每次申请的大小为100
15:11:33,503 DEBUG JbpmConfiguration : [jbpm.id.generator.block.size] 100
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.id.generator.configuration] same
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.id.generator.node.id] 0
//下面是LOG的配置
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.log.default] error
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.log.package.org.jbpm] info
15:11:33,513 DEBUG JbpmConfiguration : [jbpm.log.package.org.jbpm.persistence.hibernate] info
15:11:33,523 DEBUG JbpmConfiguration : [jbpm.log.stdout] on
//持久化的方式配置
15:11:33,523 DEBUG JbpmConfiguration : [jbpm.persistence.session.factory] hibernate
15:11:33,523 DEBUG JbpmConfiguration : [jbpm.scheduler.wait.period] 5000
15:11:33,533 DEBUG JbpmConfiguration : [jbpm.service.factory] default
15:11:33,533 DEBUG JbpmConfiguration : [jbpm.validate.xml] true
15:11:33,553 DEBUG JbpmConfiguration : for key 'jbpm.file.mgr', an object of type 'org.jbpm.persistence.filemgr.DatabaseFileMgr' was instantiated
相关文章推荐
- 根据调试信息学习jbpm(一):jbpmConfiguration
- 根据调试信息学习jbpm(二):sessionFactory
- 根据调试信息学习jbpm(二):sessionFactory
- 根据调试信息学习jbpm(二):sessionFactory
- 根据调试信息学习jbpm(一):jbpmConfiguration
- 学习笔记 --- LINUX 驱动调试之根据栈信息来分析
- android底层驱动学习之如何通过debugfs创建文件的方式来调试内核信息
- Android及Robotium学习总结【环境变量,真机调试及根据id模拟按键】
- 学习笔记 --- LINUX应用调试之修改内核输出应用程序的段错误信息
- ibatis学习之--3、根据id查询对应的用户信息
- c++学习之:根据GetLastError()返回值获取错误信息
- 李航 统计学习 例5,1 根据信息增益选择最优特征
- android学习之android logat 调试及信息过滤
- Log4j 如何实现 根据不同的类 或者不同的包 输出的调试信息到不同的文件夹中
- 根据时间提取介于某个时间段的信息 分类: python基础学习 2013-08-16 17:26 311人阅读 评论(0) 收藏
- 根据Bjarne Stroustrup 的C++程序设计原理与实践学习时候调试12章以后的代码
- C++学习之:根据GetLastError()返回值获取错误信息
- 进程学习10--syslog记录调试信息
- chrome 调试基本信息学习
- linux驱动调试之段错误分析-根据栈信息分析函数调用过程