Cactus Thinking

by JBoss Team

We’re happy to announce that as of today, Red Hat has become a key contributor to the Apache CXF, which is an open-source, fully featured, easy to use Web Services framework. It is the combination of two projects: Celtix developed by IONA and XFire developed at Codehaus working together at the Apache Software Foundation.

Apache CXF is a popular open source, standards based framework for developing (SOAs) Service Oriented Architectures. Our aim is to contribute to the framework’s continued development and to increase the interoperability and enterprise readiness of CXF.

Additionally, we’ll be providing full production and developer support for Apache CXF as a core component of our JBoss Enterprise Platforms. Enterprise architects, Java developers and IT operations personnel will now see the Apache CXF framework as fully supported component of our JBoss Enterprise Subscriptions.

Commonly accepted Web Service standards are vital to the continued adoption of SOA. The standard proprietary, closed source model is at odds with the open, consensus driven nature of SOAs and the standards that support them. By joining the Apache CXF project, our goal is help establish the framework as the de-facto open source Web Services Stack for Java, working together with other existing contributors like the FUSE team at Progress Software.

For more information on Red Hat’s work with the Apache CXF project please visit the JBoss Web Services project.

Jboss 团队宣布Redhat 将成为Apache CXF的关键贡献者。

编译测试类，但不执行

不编译测试类

Via http://maven.apache.org/surefire/maven-surefire-plugin/examples/skipping-test.html

1.StringUtils
2.IOUtils and FileUtils
3.Google collections
4.java.util.concurrent

by 丑鑫鑫

貌似从今以后我们需要为正在使用的spring框架的bug修复付费。Spring框架背后的公司SpringSource宣布了一项产品维护策略:

1.SpringSource 提供给 SpringSource Enterprise 的付费用户三年的当前版本如日常的维护版本样般的bug fix，安全隐患修复，快速的补丁修复。

2.针对免费的社区用户，当一个新的主版本发布后，为了找出开始的稳定性问题提供3周的bug fix等维护，过了三周以后SpringSource将不会把该版本的后续维护版本发布给社区的免费用户，而是将它提供给Enterprise的付费用户，Community user 只能从下一个Major Community Release 中得到上个版本的bug fix。

附上原文：http://www.springsource.com/products/enterprise/maintenancepolicy

SpringSource Enterprise Maintenance Policy

Effective September 2008, SpringSource has implemented a new maintenance policy for Spring. The policy provides Spring production users with a long-term, stable application platform to build, run and manage their Spring-powered applications.

Maintenance Policy:
Customers who are using SpringSource Enterprise, available under a subscription, will receive maintenance releases for three years from the general availability of a major new version. These customers receive ongoing, rapid patches as well as regular maintenance releases to address bugs, security vulnerabilities and usability issues, making SpringSource Enterprise the best option for production systems.

After a new major version of Spring is released, community maintenance updates will be issued for three months to address initial stability issues. Subsequent maintenance releases will be available to SpringSource Enterprise customers. Bug fixes will be folded into the open source development trunk and will be made available in the next major community release of the software.

by 丑鑫鑫

如果系统是采用acegi security,你不需要另外编写额外的代码来满足这个需求，硬生生的写个Listener,Filter去监听或者拦截session，实现这个功能不叫重造轮子，应该叫做用别人的轮子重造轮胎 😉

采用Acegi 的系统限制同一用户同一时间只能一次登录系统步骤如下：

1.改写web.xml加入如下的语句

<listener>
<listener-class>org.acegisecurity.ui.session.HttpSessionEventPublisher</listener-class>
</listener>

这个监听器用来监听session生命期的事件

2.在acegi相关的spring bean配置文件加入：

<bean id=“authenticationManager” class=“org.acegisecurity.providers.ProviderManager”>
<property name=“providers”>
<!– your providers go here –>
</property>

<property name=“sessionController”><ref bean=“concurrentSessionController”/></property>
</bean>

<bean id=“concurrentSessionController” class=“org.acegisecurity.concurrent.ConcurrentSessionControllerImpl”>

<property name=“maximumSessions”><value>1</value></property>
<property name=“sessionRegistry”><ref local=“sessionRegistry”/></property>
</bean>

<bean id=“sessionRegistry” class=“org.acegisecurity.concurrent.SessionRegistryImpl”/>

执行的过程为用户couxinxin登录到系统，在另一台机器上couxinxin这个用户又登录到系统，那么前一个用户couxinxin的Session将被后者冲掉（踢掉）

搞定Over ! 🙂

必须要使用acegi1.0.6及其以后的版本，不然会报出
java.lang.IllegalArgumentException: Authentication.getDetails() required
这是版本1.0.5的bug
描述为：

If concurrent session control is used with an authentication provider which doesn’t copy the authentication details object to the successful authentication (e.g. CasAuthenticationProvider) then the check with the concurrent session controller on whether access is allowed takes place before the copyDetails method of AbstractAuthenticationManager is called. This isn’t a problem with classes which extend AbstractUserDetailsAuthenticationProvider, as it copies the authentication details object itself.

The copyDetails method should probably be pulled down into ProviderManager and called before checkAuthenticationAllowed() is called. This will ensure that the details object is available even if the provider doesn’t set it.

It’s also not clear that we really need an AbstractAuthenticationManager at all, given how little there is in there.

参见：http://jira.springframework.org/browse/SEC-618

ps： blogger 的xml排版有点难看，呵呵

Some projects such as JBoss Web Services, JBoss ESB, and JBoss Rules use Subversion for their source code repositories. We have multiple svn repositories:

NOTE: THE URLs here are NOT YET READY for JBoss Rules, please do not use them at this time.

Anonymous Access is provided by the following url:

http://anonsvn.jboss.org/repos/

Committer Access is provided by:

https://svn.jboss.org/repos/

Note that the anonymous repository is a mirror of the committer repository that is synched every 5 minutes.

Committers will be prompted for their jboss.com id and password. There are no public and private keys for these repositories. All encryption is done via https. Each project maintains its own list of committers and there is directory level access controls in place.

Committer access requires agreement to one of the following contributor agreements:

… …

http://anonsvn.jboss.org/repos/中列出的项目里面没有jBPM,但是我们发现JBoss Portal的地址是http://anonsvn.jboss.org/repos/portal/ 通过猜测可以的到jbpm的SVN库地址为

http://anonsvn.jboss.org/repos/jbpm/

(+_+)#