Kim-'s-Blog.Object-Everything.I'm POJO.

使用Chrome瀏覽器，靜默打印 Silent Print，直接打印，全屏模式

同事遇到這樣一個需求:在Chrome瀏覽器中希望可以靜默打印，直接打印

查了些資料,發(fā)現(xiàn)Chrome本身的設(shè)置就可以滿足,

同時Chrome的一些其他設(shè)置可以用在軟件開發(fā)中.

在地址欄敲: about:flags ,打開設(shè)置界面:

停用:Enable Print Preview Registration Promos Windows, Linux, Chrome OS

Chrome快捷方式增加:

--kiosk-printing

這樣就可以靜默，打印，直接使用默認(rèn)打印機(jī)進(jìn)行打印。

另：如需是Chrome全屏+靜默打印: 使用 --kiosk --kiosk-printing

需要用svn cleanup上次關(guān)閉時的鎖定

NOSQL的優(yōu)勢
易擴(kuò)展

NoSQL數(shù)據(jù)庫種類繁多，但是一個共同的特點都是去掉關(guān)系數(shù)據(jù)庫的關(guān)系型特性。數(shù)據(jù)之間無關(guān)系，這樣就非常容易擴(kuò)展。也無形之間，在架構(gòu)的層面上帶來了可擴(kuò)展的能力。

大數(shù)據(jù)量，高性能

NoSQL數(shù)據(jù)庫都具有非常高的讀寫性能，尤其在大數(shù)據(jù)量下，同樣表現(xiàn)優(yōu)秀。這得益于它的無關(guān)系性，數(shù)據(jù)庫的結(jié)構(gòu)簡單。一般MySQL使用Query Cache，每次表的更新Cache就失效，是一種大粒度的Cache，在針對web2.0的交互頻繁的應(yīng)用，Cache性能不高。而NoSQL的Cache是記錄級的，是一種細(xì)粒度的Cache，所以NoSQL在這個層面上來說就要性能高很多了。

靈活的數(shù)據(jù)模型

NoSQL無需事先為要存儲的數(shù)據(jù)建立字段，隨時可以存儲自定義的數(shù)據(jù)格式。而在關(guān)系數(shù)據(jù)庫里，增刪字段是一件非常麻煩的事情。如果是非常大數(shù)據(jù)量的表，增加字段簡直就是一個噩夢。這點在大數(shù)據(jù)量的web2.0時代尤其明顯。

高可用

NoSQL在不太影響性能的情況，就可以方便的實現(xiàn)高可用的架構(gòu)。比如Cassandra，HBase模型，通過復(fù)制模型也能實現(xiàn)高可用。

使用Struts2 上傳 zip rar
使用的 MIME：
<interceptor-ref name="fileUpload">
 <param name="allowedTypes">application/zip,application/x-zip-compressed,application/rar,application/octet-stream</param>
 <param name="maximumSize">3145728</param>
</interceptor-ref>

通過Debug FileUploadInterceptor可知，
zip文件是[application/x-zip-compressed]
rar是[application/octet-stream]

使用Jbpm4.2 集成Spring 出現(xiàn)問題：
  
   2009-11-12 15:49:51,640 ERROR [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'processEngine' defined in file [......\WEB-INF\classes\spring\applicationContext-jbpm.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.jbpm.api.ProcessEngine org.jbpm.pvm.internal.cfg.SpringConfiguration.buildProcessEngine()] threw exception; nested exception is java.lang.NullPointerException

  Caused by: java.lang.NullPointerException
 at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:177)

 userCommandService 為null

  經(jīng)調(diào)試發(fā)現(xiàn)，使用Spring后userCommandService 確實是null，
  配置中缺少什么東西？未知。 文檔中并無特殊說明，
 4.1沒有出現(xiàn)問題~ 
 應(yīng)該是4.2的Bug

Jbpm4.1特性：
4.1與Tomcat集成的很好
4.1提供基于Web的流程編輯功能

在開發(fā)指南中有相關(guān)整合章節(jié)：

16.2. Configuration

Replace the standard-transaction-interceptor with the spring-transaction-interceptor. The hibernate session needs the attribute current=”true”. Also, the <transaction/> must be removed from the transaction-context if you want the transactions to be handled by Spring only. This forces jBPM to search for the current session, which will be provided by Spring.

<process-engine-context>
<command-service>
<spring-transaction-interceptor />
...
</command-service>
...
</process-engine-context>
<transaction-context>
...
<hibernate-session current="true"/>
</transaction-context>

 

The Spring integration provides a special context, which is added to the set of context where the jBPM engine will look for beans. Using this SpringContext, it is now possible to retrieve beans from the Spring Application Context. For the Spring context to be known, a SpringConfiguration must be created. This class extends the JbpmConfiguration but will add itself as a context. The single constructor take the location of the jBPM configuration.

<bean id="jbpmConfiguration" class="org.jbpm.pvm.internal.cfg.SpringConfiguration">
<constructor-arg value="be/inze/spring/demo/jbpm.cfg.xml" />
</bean>

 

The jBPM services can also be defined in the Spring applicationContext, as following:

<bean id="processEngine" factory-bean="jbpmConfiguration" factory-method="buildProcessEngine" />
<bean id="repositoryService" factory-bean="processEngine" factory-method="getRepositoryService" />
<bean id="executionService" factory-bean="processEngine" factory-method="getExecutionService" />

 

16.3. Usage

The previous section already showed how the jBPM services can be made accessible for other Spring services. The other use case is calling Spring beans from within a process. This can be done by using an expression which resolves to the name of a Spring bean.

<java name="echo" expr="#{echoService}" method="sayHello" >
<transition name="to accept" to="join1"/>
</java>

The scripting engine will look into all contexts from the bean named echoService. If you configured the ScriptManager as above, Spring will be the last context to search for. You can also add a Spring bean to the Spring Application context (eg IdentitySessionImpl with id identitySession) and use it in the jBPM config (eg by adding <env class="identitySession" />)

整合過程與 4 基本相同。
jbpm.cfg.xml

<?xml version="1.0" encoding="UTF-8"?>

<jbpm-configuration>

  <import resource="jbpm.default.cfg.xml" />
  <import resource="jbpm.tx.spring.cfg.xml" />
  <import resource="jbpm.jpdl.cfg.xml" />
  <import resource="jbpm.identity.cfg.xml" />
  <import resource="jbpm.businesscalendar.cfg.xml" />

  <!-- Job executor is excluded for running the example test cases. -->
  <!-- To enable timers and messages in production use, this should be included. -->
  <!--
  <import resource="jbpm.jobexecutor.cfg.xml" />
  -->
  <import resource="jbpm.jobexecutor.cfg.xml" />
  <import resource="jbpm/jbpm.mail.templates.examples.xml" />
  
</jbpm-configuration>

工作日歷從 default中分離
整合XML在原生的jbpm.tx.spring.cfg.xml 中