UnmodifiableArray{VALUES0=RED, VALUES1=YELLO}

public class UnmodifiableArrayList {
      // 消除安全漏洞
     private static final String[] PRIVATE_VALUES = { "RED", "GREEN" };
     public static final List<String> PVALUES = Collections.unmodifiableList(Arrays.asList(PRIVATE_VALUES));
     public static void main(String[] args) {
         UnmodifiableArrayList UF = new UnmodifiableArrayList();
         UF.PVALUES.add(1, "YELLO"); //会抛出UnsupportedOperationException异常
         System.out.println(UF);
     }
     //使用Guava
     @Override
     public String toString() {
         return Objects.toStringHelper(this)
                         .add("PVALUES0", UnmodifiableArrayList.PVALUES.get(0))
                         .add("PVALUES1", UnmodifiableArrayList.PVALUES.get(1))
                         .toString();
     }
 }

ImmutableList mmutableList = ImmutableList.of(PRIVATE_VALUES);

curl: (7) couldn't connect to host 
ERROR:  While executing gem ... (GemFast::Util::ExecutionError)     Failure while executing: curl -f#LA rubygem-gemfast http://ruby.taobao.org/quick/Marshal.4.8/bundler-1.3.5.gemspec.rz --insecure -o /home/git/local/lib/ruby/gems/1.9.1/cache/bundler-1.3.5.gemspec.rz

//本例只用来说明第一大优势，请不要纠结其它问题 
public class Foo {
         Set<Bar> bars;
         List<Car> cars;
         //构造器1
         private Foo(Set<Bar> bars) {
                 this.bars = bars;
         }
         //构造器2
         private Foo(List<Car> cars) {
                 this.cars = cars;
         }
         //构造器3
         private Foo(Set<Bar> bars, List<Car> cars) {
                 this.bars = bars;
                 this.cars = cars;
         }
         //静态工厂方法1
         public static Foo newInstanceByBar(){
                 return new Foo(new HashSet<Bar>());
         }
         //静态工厂方法2
         public static Foo newInstanceByCar(){
                 return new Foo(new ArrayList<Car>());
         }
         //静态工厂方法3
         public static Foo newInstanceByAll(){
                 return new Foo(new HashSet<Bar>(),new ArrayList<Car>());
         }
         public static void main(String[] args) {
                 // 通过构造器创建实例，不好区分容易使用错误
                 Foo fbar = new Foo(new HashSet<Bar>());
                 Foo fcar = new Foo(new ArrayList<Car>());
                 Foo fall = new Foo(new HashSet<Bar>(),new ArrayList<Car>());
                  // 通过静态工厂方法可以清晰的用方法名识别
                 Foo fbar_static = Foo.newInstanceByBar();
                 Foo fcar_static = Foo.newInstanceByCar();
                 Foo fall_static = Foo.newInstanceByAll();
         }
  }
  class Bar {}
  class Car {} 

List<Type> exactly100 = Lists.newArrayListWithCapacity(100);
List<Type> approx100 = Lists.newArrayListWithExpectedSize(100); 
Set<Type> approx100Set = Sets.newHashSetWithExpectedSize(100);

// 服务提供框架示意模型 - 服务API 
public interface ServiceAPI {
         // 这里是服务指定的方法
 }
// 服务提供框架示意模型 - 服务SPI 
public interface ServiceSPI {
         ServiceAPI newService();
 }  
// 服务提供框架示意模型实现 
// 不可实例化的类，用来注册创建和提供访问 
public class ServiceFramework {
         private ServiceFramework() {
         }// 强制防止实例化（规则4）

         // 映射服务名到服务
         private static final ConcurrentMap<String, ServiceSPI> spis = new MapMaker().makeMap();//使用Guava创建
         public static final String DEFAULT_SPI_NAME = "<def>";

         // 默认SPI注册API
         public static void registerDefaultSPI(ServiceSPI spi) {
                 registerSPI(DEFAULT_SPI_NAME, spi);
         }

         // 指定SPI注册API
         public static void registerSPI(String name, ServiceSPI spi) {
                 spis.put(name, spi);
         }

         // 服务访问API
         public static ServiceAPI newInstance() {
                 return newInstance(DEFAULT_SPI_NAME);
         }
         public static ServiceAPI newInstance(String name) {
                 ServiceSPI spi = spis.get(name);
                 if(spi == null)
                         throw new IllegalArgumentException(
                                         "No provider registered with name: " + name);
                 return spi.newService();
         }
 }

// 简单的服务提供框架测试程序 
public class Test {
         public static void main(String[] args) {
                 // 服务提供商执行下面的注册
                 ServiceFramework.registerDefaultSPI(DEFAULT_PROVIDER);
                 ServiceFramework.registerSPI("comp", COMP_PROVIDER);
                 ServiceFramework.registerSPI("armed", ARMED_PROVIDER);
                  // 客户端执行下面的创建
                 ServiceAPI s1 = ServiceFramework.newInstance();
                 ServiceAPI s2 = ServiceFramework.newInstance("comp");
                 ServiceAPI s3 = ServiceFramework.newInstance("armed");
                 System.out.printf("%s, %s, %s%n", s1, s2, s3);
         }
          private static ServiceSPI DEFAULT_PROVIDER = new ServiceSPI() {
                 public ServiceAPI newService() {
                         return new ServiceAPI() {
                                 @Override
                                 public String toString() {
                                         return "默认服务";
                                 }
                         };
                 }
         };
          private static ServiceSPI COMP_PROVIDER = new ServiceSPI() {
                 public ServiceAPI newService() {
                         return new ServiceAPI() {
                                 @Override
                                 public String toString() {
                                         return "Complementary 服务";
                                 }
                         };
                 }
         };
          private static ServiceSPI ARMED_PROVIDER = new ServiceSPI() {
                 public ServiceAPI newService() {
                         return new ServiceAPI() {
                                 @Override
                                 public String toString() {
                                         return "Armed 服务";
                                 }
                         };
                 }
         };
 }
  
//输出如下 默认服务, Complementary 服务, Armed 服务

List<TypeThatsTooLongForItsOwnGood> list = new ArrayList<TypeThatsTooLongForItsOwnGood>();

List<TypeThatsTooLongForItsOwnGood> list = new ArrayList<>();

Set<Type> copySet = Sets.newHashSet(elements); 
List<String> theseElements = Lists.newArrayList("alpha", "beta", "gamma");

# su - root 
# cd /var/tmp/oracle 
# ls -1 oratool* 
oratoolkit-1.0.2.1.5-1.noarch.rpm 
# rpm -ivh oratoolkit-1.0.2.1.5-1.noarch.rpm 
Preparing...                ########################################### [100%]
    1:oratoolkit             ########################################### [100%]

# passwd oracle 
Changing password for user oracle. 
New UNIX password: 
BAD PASSWORD: it is based on a dictionary word 
Retype new UNIX password: 
passwd: all authentication tokens updated successfully.

# /opt/oracle/otk/current/bin/installManager swReqCheck osSetup11gR2.cfg 
...//省略大部分输出 
20130521_165122: Info: Action swReqCheck of installManager ended with 7 WARNINGS

//先拼装命令 
# REQ_FILE_DIR="/opt/oracle/otk/current/conf/installManager/requirement" 
# REQ_FILE_PATH="$REQ_FILE_DIR/ora11gR2-redhat-5-x86_64.pkg.lst" 
# YUM_COMMAND=$(echo "yum install") 
# YUM_COMMAND+=$(egrep -v "#" $REQ_FILE_PATH | grep 32-bit | awk '{ print " "$1".i[356]86" }') 
# YUM_COMMAND+=$(egrep -v "#" $REQ_FILE_PATH | grep 64-bit | awk '{ print " "$1".x86_64" }')  

//用echo看看最终拼装的命令是什么样 
# echo $YUM_COMMAND  

//执行命令 
# $YUM_COMMAND  

//再次执行环境检查 
# /opt/oracle/otk/current/bin/installManager swReqCheck osSetup11gR2.cfg 
... 
20130521_170131: Info: Action swReqCheck of installManager ended successfully //这次验证成功了，环境已经满足Oracle安装要求

# cd /opt/oracle/otk/current/tools/rlwrap/ 
# ./configure 
# make 
# make install 
# /usr/local/bin/rlwrap -v 
rlwrap 0.30

# cd /opt/oracle/otk/current/conf/installManager/ 
# vi osSetup11gR2.cfg 
# sdiff -s osSetup11gR2.cfg sample/osSetup11gR2.cfg //对比哪些参数修改过 
# /opt/oracle/otk/current/bin/installManager osSetup osSetup11gR2.cfg

# cd /var/tmp/oracle 
# chown oracle:oinstall * 
# mv linux.x64_11gR2_database_1of2.zip linux.x64_11gR2_database_2of2.zip /var/opt/oracle/repository/

# su - oracle
 ------------------------------------------------------  
 oraToolKit environment variables
 ------------------------------------------------------  
 Installation directory :   /opt/oracle/otk  
 Release                :   1.0.2.1.5  
 $RUN directory         :   /opt/oracle/otk/1.0/bin  
 $LOG_BASE directory    :   /var/opt/oracle/otk/1.0/log  
 ------------------------------------------------------  
<SITE|COMPANY>:oracle@stquist1p:sidNotSet$ grep ^SITE .profile.custom.interactive 
SITE="<SITE|COMPANY>" 
<SITE|COMPANY>:oracle@stquist1p:sidNotSet$ vi .profile.custom.interactive 
<SITE|COMPANY>:oracle@stquist1p:sidNotSet$ grep ^SITE .profile.custom.interactive 
SITE="KuuYee"//修改这一行，可以显示你喜欢的内容 
<SITE|COMPANY>:oracle@stquist1p:sidNotSet$ exit 
# su - oracle 
KuuYee:oracle@stquist1p:sidNotSet$

$ bash 
$ cd $INSTALL_CONF 
$ cp sample/swInstEeSrv11gR2-Step1-linux-x86_64.cfg . 
$ installManager swInst swInstEeSrv11gR2-Step1-linux-x86_64.cfg 
$ su - 
# /opt/oracle/eesrv/11.2.0/db1/root.sh
# exit

$ cd $INSTALL_CONF 
$ ls -1 dbSetup*.cfg 
dbSetup-dev.cfg 
dbSetup-prod.cfg 
dbSetup-test.cfg 
$ vi dbSetup-prod.cfg //prod为生产模式 
$ sdiff -s dbSetup-prod.cfg sample/dbSetup-prod.cfg 
DB_NAME="idm_test"                                            | DB_NAME="prod" 
ORACLE_HOME="$ORACLE_BASE/eesrv/11.2.0/db1"                   | ORACLE_HOME="$ORACLE_BASE/sesrv/11.1.0/db1" 
NLS_LANG=".AL32UTF8"                                          | NLS_LANG=".UTF8" 
SYSTEM_SIZE=1G                                                | SYSTEM_SIZE=512M 
TEMP_SIZE=2G                                                  | TEMP_SIZE=512M 
UNDO_SIZE=2G                                                  | UNDO_SIZE=512M 
USERS_SIZE=100M                                               | USERS_SIZE=10M 
LISTENER_PORT="1541"                                          | LISTENER_PORT="1531" 
MEMORY_TARGET=7G                                              | MEMORY_TARGET=512M 
MEMORY_MAX_TARGET=7G                                          | MEMORY_MAX_TARGET=512M 
SGA_TARGET=3G                                                 | SGA_TARGET=256M 
PROCESSES=1000                                                | PROCESSES=100 
$ installManager dbSetup dbSetup-prod.cfg //执行这部之前最好先配置下/etc/hosts文件，看下面说明

127.0.0.1    你的hostname

---------------------------------------------------------------------------------------------------- 
20130522_091856: Info: Executing libmiscellaneous.getFooter function 
20130522_091856: Info: Terminating installManager execution 
20130522_091856: Info: Summary log file:  /var/opt/oracle/otk/1.0/log-old/installManager/../installManager.log 
20130522_091856: Info: Detailed log file: /var/opt/oracle/otk/1.0/log-old/installManager/dbsetup-20130522_090349.log 
20130522_091856: Info: Action dbSetup of installManager ended successfully 
----------------------------------------------------------------------------------------------------

$ bash 
$ sourceProdEnv 
$ sqlplus sys/manager@idm_dev as sysdba; 
或者 
$ sqlplus otk/otk@idm_dev  

SQL*Plus: Release 11.2.0.1.0 Production on Wed May 22 11:05:16 2013  

Copyright (c) 1982, 2009, Oracle.  All rights reserved.   


Connected to: 
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production 
With the Partitioning, OLAP, Data Mining and Real Application Testing options  

SQL>

$ ctl status all //查看当前状态 
$ ctl stop all   //停止数据库 
$ ctl start all  //启动数据库

$ cd $BACKUP_CONF 
$ vi prod.cfg 
$ sdiff -s prod.cfg sample/prod.cfg DISK_DEVICE_MOUNT_POINT="/" | DISK_DEVICE_MOUNT_POINT="/backup01" 
$ backupManager full prod.cfg

$ crontab -l|head -2 
# Example 1: Daily physical database backup 
# 0 2 * * * [ -d $HOME/../current ] && (ksh -c '. ./.profile >/dev/null; backupManager full <sid_1>.cfg <sid_2>.cfg <sid_n>.cfg >/dev/null') 
$ crontab -e 
$ crontab -l|head -2 
# Example 1: Daily physical database backup 
0 2 * * * [ -d $HOME/../current ] && (ksh -c '. ./.profile >/dev/null; backupManager full prod.cfg >/dev/null')

otk并没有帮我们创建EM控制台，对于习惯用Web管理的用户很不方便，我们需要手工创建：

OK！ 大功告成，相信各位童鞋都安装成功了，OTK的安装还是很稳健的，至少我安装了几十次都成功了！

最后祝各位童鞋好运！

EJB 3.2

Enterprise Java Bean 3.2 (JSR 345)

•  Enhancing EJB architecture to enable the PaaS model with features such as multi-tenancy
•  Factorization of container-managed transactions to use other component technologies of the Java EE platform
•  Enhanced use of annotations to simplify EJB programming model
•  Alignment and integration with other specifications related to JSRs within the Java EE 7 platform such asCDI , JMS, Bean Validation, etc

EL 3.0

Expression Language 3.0 (JSR 341)

•  Separate expression language context into parsing and evaluation contexts independent of the JSP specification
•  Introduction of new customizable expression language coercion rules
•  Reference static methods and members directly in EL expressions without having to define them in Tag Library Descriptor, similar to instance method invocation
•  Adding equality, string concatenation, and sizeof operators
•  CDI Integration so that +events+ can be generated before/during/after the expressions are evaluated

JMS 2.0

Java Messaging Service 2.0 (JSR 343) The new introduction will be an evolution of the previous version, JSR-914.

•  Enhanced JMS programming model to make application development easier, cleaning up ambiguities in the present specification
•  Enhanced integration with CDI for easier and more unified use of API
•  Make necessary changes to API in allowing any JMS provider to integrate with any Java EE containerinvocation
•  Make JSR more cloud-friendly, leveraging multi-tenancy and other cloud-related features from the platform

EL 3.0

Expression Language 3.0 (JSR 341)

•  Separate expression language context into parsing and evaluation contexts independent of the JSP specification
•  Introduction of new customizable expression language coercion rules
•  Reference static methods and members directly in EL expressions without having to define them in Tag Library Descriptor, similar to instance method invocation
•  Adding equality, string concatenation, and sizeof operators
•  CDI Integration so that events can be generated before/during/after the expressions are evaluated

Servlet 3.1

Java Servlet 3.2 (JSR 340) Servlet早在JavaEE6就已经无缝集成了 CDI

•  Optimize Java EE PaaS model, leveraging the cloud for Web applications
•  Optimizing PaaS model leveraging multi-tenancy. To support this into the Web container, the main areas of optimization will be security, session state, resources and
•  other multi-tenant awareness requirements for Web applications.
•  Enhance the asynchronous support of Servlet 3.0 and simplify further in building asynchronous applications
•  Utilize Java EE concurrency APIs for asynchronous support
•  Enhance the Servlet 3.0 built-in security features
•  Optimize the built-in plug-ability support of Servlet 3.0
•  Focus on providing necessary functionality for building easier-to-use, high-level protocol support for Web Sockets and other protocols that work with HTTP in the Servlet API

JAX-RS 2.0

Java API for RESTful Web Services 2.0 (JSR 339)

•  Define two client APIs, both REST-compatible -- a low-level API using builder pattern and a higher-level API leveraging the low-level APIs
•  Hypermedia, an important RESTful feature of Web applications, will be easy to create, and it will process links associated with resources in representation either as a header or as a links within the entity peripheral.
•  Make it possible to validate parameters of forms or query using bean validation and return a meaningful response on failure to validate
•  Closer integration CDI @Inject

JSF 2.2

Java Server Faces 2.2 (JSR 344)

•  Making configuration options dynamic, eliminate tag handler class even for non-composite JSP components, introduce shorthand URLs for Facelet Tag Libraries, make cc:interface in composite components optional, enhance deployment, integrate with CDI
•  Component identification and Ajax
•  Support implementation of Portlet Bridge 2.0
•  Support for HTML5 features, such as Forms, Heading, Metadata and Section content model, Flow management, Listener for page navigation events, and new components like FileUpload and BackButton

CDI 1.1

Context and Dependency Injection 1.1 (JSR 346)

•  Global ordering of interceptors and decorators,
•  API for managing built-in context,
•  Embedded mode to allow startup outside the Java EE container
•  Declarative control over which packages/classes are scanned in a bean archive
•  Bean declaration at constructor level
•  Injection for static members, such as loggers
•  Send CDI events for Servlet events
•  Better support for CDI in libraries when used in the Java EE platform

JPA 2.1

Java Persistence API 2.1 (JSR 338)

•  Addition of the javax.persistence.StoredProcedureQuery interface to control stored procedure query execution. >Javax.persistence.EntityManager has added four variants of methods that return a StoredProcedureQuery for executing a stored procedure, including one allowing named stored procedure query. The newly introduced annotation @NamedStoredProcedureQuery can be specified on an entity or mapped class, similar to the @NamedQuery. The parameters IN, OUT and INOUT can be used to manipulate values from the stored procedure.
•  The javax.persistence.criteria.AbstractQuery interface has been refactored by CriteriaUpdate, CriteriaDelete and CommonAbstractQuery interfaces.
•  Added new identifiers for persistence query language (JPQL), such as FUNCTION for supporting JPQL built-in functions, TREAT for down casting within path expressions in the FROM and WHERE clauses, and ON for specifying the relationship between the tables.
•  CDI Integration Listener.The entity listeners can be annotated with @PostConstruct and @PostDestroy for their lifecycle. Also, the usual lifecycle callback methods, such as @PrePersist, @PostPersist, @PreUpdate and @PreRemove can be used for entities.
•  Added support for unsynchronized persistence context to create container-managed unsynchronized persistence context. For example, @PersistenceContext (synchronization=SynchronizationType.UNSYNCHRONIZED)

Bean Validation 1.1

Bean Validation 1.1 (JSR 349)

•  Integration with other Java EE specs， CDI etc.
•  APIs to validate parameters and return values of method calls.
•  Validate parameters and return values on HTTP calls
•  Ability to translate a group into another group while cascading the validation
•  APIs to validate parameters and return values of method calls
•  Apply constraints on group collection
•  Extend the model to support AND and OR style composition

首先进入oracle用户，使用rman工具执行命令rman target/：

竟然报错了，如果你的空间100%一点剩余都没有，那么就会报这个错，只能想办法让你的系统腾出一点空间，哪怕几百兆！然后重启数据库应该就可以登陆dba了。

重启数据库，再次rman

现在删除Archivelog归档文件，执行下面的命令来删除最近7天的归档：

也可以只保留最近7天的，其余的都删除：

但是过一段时间你的日志还是回满，对于开发环境这样的归档功能其实没什么必要，彻底解决办法是关闭这个功能，用dba登陆oracle：

然后执行下面的命令：

然后重启数据库就OK了！

Jenkins提供一个专注于Maven2项目的Job类型。这种Job类型深度集成Maven2并提供如下优于free-style software project Job类型的特性：

• Jenkins从Maven POM中获取更多信息来辅助构建工作，这样就大大减少了Job的配置工作。

• Jenkins监听Maven执行过程来决定如何处理Job。例如，Jenkins会在Maven测试阶段自动记录JUnit报告。如果你正在运行javadoc目标，Jenkins会自动记录javadoc。

因此你只需要为Job配置SCM信息和指定运行Maven项目的哪个目标就可以了，其它的Jenkins会帮你决定如何去做。

 TODO 谈论Maven modules在子项目中的表现，还有构建编号在子项目中是如何控制的。带有截屏。

用模块依赖链接自动构建

Maven集成插件

下面列出root目录下的文件结构

目的是除了目录subdir2和文件fileA.txt其它的都要删除，如果一个一个删就效率太低了，Shell命令可以轻松的解决

执行的效果如下

$ emca -config dbcontrol db -repos recreate

 SQL> SELECT * FROM DBA_DATA_FILES where TABLESPACE_NAME = 'SYSTEM'; 
FILE_NAME     FILE_ID TABLESPACE_NAME                    
 BYTES     BLOCKS STATUS  RELATIVE_FNO AUT   MAXBYTES  MAXBLOCKS INCREMENT_BY USER_BYTES USER_BLOCKS  
ONLINE_  /data01/rdbms/wcdb/datafile/wcdb_system_01.dbf          1 SYSTEM                          536870912      65536 AVAILABLE           
 1 NO           0          0            0  535822336       65408 
SYSTEM

SQL> ALTER TABLESPACE SYSTEM ADD DATAFILE '/data01/rdbms/wcdb/datafile/wcdb_system_02.dbf' SIZE 500M; Tablespace altered.

$ emca -repos drop

$ emca -config dbcontrol db

$ emca -deconfig dbcontrol db

$ emca -reconfig ports $ emca -reconfig ports -dbcontrol_http_port 1160 $ emca -reconfig ports -agent_port 3940

$ emctl start dbconsole

$ emctl stop dbconsole

$ emctl status dbconsole