Win a copy of Rust Web Development this week in the Other Languages forum!

Charlie Fineman

+ Follow
since Sep 02, 2005
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Charlie Fineman

One of my frustrations with the WebTools project is that there does not seem to be a way to deploy an exploded WAR... it seems to way for about 15 seconds and then rebuilds the entire war and redeploys (as opposed to doing a hot swap of incrementally built artifacts into the exploded war)... very anoying when you are changing several files. MyEclipse seems to have the edge on this front.

Is there a way for me to configure WebTools (or some other plugin) to support exploded wars?
We are about to embark on choosing a new controller after a couple of unhappy years with something that one of our guys built in house. There are two main goals we have:

1) Avoid XML hell
2) Easily integrate with Spring interfaces
3) Really clean view separation (we have a CMS we pull a lot of stuff from and make heavy use of XSL)

One of my guys did a quick prototype of one of our Apps using Wicket and I was really pleased with the results. Next I'm gonna have him do the same thing in Spring WebFlow.

I'm sure we will come up with our own pros/cons but I'd be interested in everyone else's perspective since obviously a POC will not touch on all potential issues.
Would very much like to play around with GlassFish in it's own VM. Has anyone made this available as an appliance yet?
I, like many others, have drifted away from EJB after some early experience. Even before the advent of lightweight containers, I found myself finding other mechanisms for putting together distributed systems (largely because of the number of pieces I had to manage with the EJBs). I understand that EJB3 has made inroads into the number of artifacts required (via extensive use of annotations) but is it enough to make me take another look at EJB?

I'm curious what arguments the authors of EJB In Action would make to developers who have other options now. What does EJB offer over the competition these days? Why should I consider looking at it again?