My First Published plug-in on google code

I finally managed to write a (semi) useful plug-in  that helped me understand variables in the context of source provider in the Command Core Expressions Framework. The code is puvlished under the Apache 2.0 license and is available on google code @ http://code.google.com/p/rcprevealsourceprovider/. This plug-in will track all source provider variables and isplay their values in real-time. It took me a while to undersatnd how to work them and hopefully this plug-in or at least the code will be useful to someone. It's been a while since I published anything on this blog, but I have been real busy in the last 18 months, hopefully I am back on a roll and will keep posting more regularly.

Eclipse Training

I finally managed to put togeteher a web page about my upcoming training session on eclipse RCP. Doing so I found a number of resources for those willing to learn by themselves:

• the ECESIS eclipse project: a list of resources and open source training material
• Wayne Beaton post about Training
• and of course my own page

OWASP & tools

I just had an application security awarness training, and it was quite enlightening. Of course Owasp was mentioned, with the top ten list of vulnerabilities, along with the webGoat webapp. but also tools like

• fiddler: free win32 http proxy with scripting facilities, no ssl support and based on .net
• charles: shareware http proxy in java with ssl suport
• WebSleuth: an ie plugin to edit forms, suddenly hacking got so much simplier

Of course there are firefox plugins to achieve the same set of functionnalities.

WTP 1.0

Of course with each new release of WTP the process describe for WTP 0.7 is less and less successfull. But this comes with no surprise, as those were undocumented and temporary features. For those who wonders, the assembled webapp now resides under your workspace directory in .metadata/.plugins/org.eclipse.wst.server.core/tmpX where X is the number of your server starting at 0. Using this tmp folder clearly indicate that nobody should rely on the files at this location, as they will be regenrated with the build process. Those tmp folders also allows eclipse to build a separate assembly specific to each server, which make a lot more sense than the .deployables directory which was shared amongts all server instances. If you need to explicitely reference this directory, you should probably review your build process (but you are already using Maven, right?).

WTP 1.0M8 is out

I have tried to applied the method descibed in my previous post de WTP 1.0M8 without must success.
First problem: the builder org.eclipse.wst.common.modulecore.DependencyGraphBuilder and the nature org.eclipse.jst.j2ee.web.WebNature have disappeared. It seems to enough to remove them from .project file
Second problem: my webapps which where deploying seemlessly on WTP 0.7 with Tomcat 5.5 are running like dogs under 1.0M8. Each time I edit a jsp file, it quicks in the builder, and wtp needs to republish the entire webapp to the server, reloading the context in the process. This renders quick editing almost impossible. and I don't event speak about modifying a java class on the fly.
Third problem: saving a jsp or java file is now really slow (probably linked to pb#2)
May be I screwed up my server settings or my projects settings. but I tried a clean eclipse install, a clean server definition, a clean projects checkout, with the same result.
I tried a demo app LowAirFare which works very well and doesn't republish on jsp editing, but does republish on class editing.
I really like to understand why my webapp gets republished when I edit a JSP.
I guess I'll have to revert to 0.7 until those issues are worked out.

Using Eclipse WTP 0.7RC2 with a maven project

When you want to develop web app on eclise, you have not many choices, but the picture is changing as the WTP project is reaching a stable build by the end of the month.
WTP is a very promising eclipse extension, that seems to have been very well though from the ground up, and from my point of view gives you better control than myEclipse (what I have been using so far).

It took me about a day to be able to use wtp 0.7rc2 with my maven projects. I couldn't find any relevant up to date documentation but some bugzilla entries and some outdated test plans. I am writing this post to not forget what I have been doing so far.

Basically a maven project is a project with the following features:

• separation of sources by topic java, test, webapp
• usage of external libraries with a variable (MAVEN_REPO)
• eclipse project dependency where needed (<eclipse.dependency>true</eclipse.dependency>)

This tutorial only describes how to setup your eclipse project to use WTP to build a deployable webapp using separation of sources, externals jar and project dependencies.

[ArtifactId] will denote the current project name as per maven standards

This is still a very manual process, hopefully either the eclipse maven plugin or the mevenide eclipse plugin will be enabled to generate/edit/synchronize those configuration files.

Setup: eclipse 3.1 + wtp 0.7 RC2 or RC3
Of course you also need to install EMF/GEF/JEM plugins. I highly recommend installing in an extension directory (a directory with an eclipse subfolder and an empty file named .eclipseextension), so it is easy to switch versions and update to the latest version without having to reinstall eclipse from scratch.

I have two kind of projects, libraries and webapps. Libraries are used by webapps. This setup looks exactly like what is described by Integrating existing maven projects in WTP and by Flexible project test plan. But following those instructions written for WTP-M3 won't work with the current release of WTP.

I assume the projects are already setup as standard eclipse projects and compiling. To edit configuration files, you should switch to the resource perspective and disable "build automatically".

Step 1: setup the library projects
Edit .project there should be 3 builders in the following order:

• org.eclipse.wst.common.modulecore.ComponentStructuralBuilder
• org.eclipse.jdt.core.javabuilder
• org.eclipse.wst.common.modulecore.ComponentStructuralBuilderDependencyResolver

Then 2 natures in the following order:

• org.eclipse.jdt.core.javanature
• org.eclipse.wst.common.modulecore.ModuleCoreNature

(This step is optional) Edit .classpath (you can also do this through the interface) Change the default output folder to .deployables/[artifactId] for src/java.

Create a .wtpmodules file that contains the following code

<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId">
 <wb-module name="[artifactId]">
  <module-type module-type-id="jst.utility"/>
  <wb-resource path="/"/>
 </wb-module>
</project-modules>

Step 2: setup the webapps
Edit .project and add the following builders

• org.eclipse.wst.common.modulecore.ComponentStructuralBuilder
• org.eclipse.jdt.core.javabuilder
• org.eclipse.wst.validation.validationbuilder
• org.eclipse.wst.common.modulecore.ComponentStructuralBuilderDependencyResolver
• org.eclipse.wst.common.modulecore.DependencyGraphBuilder

Add also the following natures:

• org.eclipse.jem.workbench.JavaEMFNature
• org.eclipse.jst.j2ee.web.WebNature
• org.eclipse.jdt.core.javanature
• org.eclipse.wst.common.modulecore.ModuleCoreNature

Edit .classpath so that your ouput folder for src/java is .deployables/[artifactId]/WEB-INF/classes.

Create a file .wtpmodules which reads

<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId">
 <wb-module deploy-name="[artifactId]">
  <module-type module-type-id="jst.web">
   <version>2.3</version>
   <property name="context-root" value="[artifactId]"/>
   <property name="java-output-path" value="/bin/"/>
  </module-type>
  <wb-resource source-path="/src/java" deploy-path="/WEB-INF/classes"/>
  <wb-resource source-path="/src/webapp" deploy-path="/"/>

  <dependent-module deploy-path="/WEB-INF/lib"
    handle="module:/resource/[libArtifactId]/[libArtifactId]">
   <dependency-type>uses</dependency-type>
  </dependent-module>
  <dependent-module deploy-path="/WEB-INF/lib"
    handle="module:/classpath/var/MAVEN_REPO/[groupId]/jars/[artifactId]-[version].jar"/>
 </wb-module>
</project-modules>

The handle protocol is as follow:

• classpath is a classpath reference, the second item on the path can be lib or var (as the kind attribute in the .classpath file)
• resource is an eclipse flexible project reference, the second item being the project name, and the third item a module within the project. dependency-type can be uses which build the jar for you or consumes which copy the files across.

To generate your .wtpmodules file you can copy/paste the section of .classpath which contains references to external jars and replace [classpathentry kind="var" path="] by [dependent-module deploy-path="/WEB-INF/lib" handle="module:/classpath/var/]

You can now enable "automatic building", and your webapp should be assembled in the .deployables directory. You can then rigth-click your webapp project icon and Run it on the server of your choice.

This is a very error prone process, as there is no error or warning if you provide a broken .wtpmodules file.

Any comments appreciated.

Inversion of Control Containers and the Dependency Injection pattern

Inversion of Control Containers and the Dependency Injection pattern

DevelopingJdbcApplicationsTestFirst - MockObjects

I Should read this DevelopingJdbcApplicationsTestFirst - MockObjects

HotSwap Client Tool

How to change a class at runtime ...