ApacheCon EU 2014

Nowadays, it is quite common to have build infrastructure that, on every change in a repository, builds your software and runs all your tests. However this is where most development teams stop. This talk demonstrates how you can consistently deploy systems from development to testing, staging and production.
With Bndtools we semantically version bundles in the Eclipse IDE. The continuous build is setup to automatically deploy to a bundle repository and create snapshots of changed bundles compared to a baselined version that is available in a release repository. By hooking up these repositories to Apache ACE, such updates can instantly be deployed to systems in different configurations, allowing you to deploy new features to QA systems, beta users and finally roll them out to all other customers.
We’ll also go into real life scenarios and pitfalls we have encountered setting this up.

Apache BatchEE is an implementation of the JSR-352 JBatch specification.

BatchEE is based on the original reference implementation but includes many bug-fixes and improvements.
In addition to the jbatch core module we also added many useful helpers which do make batch programming a breeze.
We did also add a few ways to control your batch jobs, e.g. via JAX-RS, a simple GUI or even as stand-alone command line client. That way you can use BatchEE in JavaEE 5, 6 and 7 environments and even in Java SE.

After an introduction to writing JBatch batches in general we will showcase fancy features of BatchEE and we surely have some best-practice tips to share.

In this talk I would like to present few recently discovered security vulnerabilities in the Apache Struts 2 web framework and based on that try to increase developers' awareness of the overall application security. In my opinion, nowadays developers don’t care about the security too much, they depend on what the framework gives them. Quite often, they even don’t check security bulletins to see if a new vulnerability wasn’t discovered recently in his/her famous framework. I would like show few web attacks and explain how it was possible to harm an application or even entire server, how to prevent such kind of attacks in the future and so on. Examples will base on the Apache Struts 2, but almost all the same problems were pointed out in the Spring MVC or in the Apache Wicket. Each framework has its own weaknesses :-)