On Thu, Sep 19, 2013 at 4:19 AM, Alejandro Abdelnur <[email protected]> wrote: > The current model, all JARs in the WAR follows the J2EE deployment model. > An app (the WAR in this case) is self-contained. My J2EE background can be > blamed from this choice. > > While I like this model, in practice it seems people stumble up this quite > often. > > Maybe we should switch to a model closer to what Bigtop does, no > bundling/injecting Hadoop JARs, instead adding them to the classpath of > Tomcat, and the same for all the Oozie JARs. The WAR will have not classes > (you want all JARs in the same classloader).
I'd strongly ecourage you guys to go in that direction. A few apps that started as pure J2EE ones are now following this model and seem to be quite successful at it. > The only challenge here is that the Hadoop JARs available in the classpath > of the Hadoop client have tons of stuff that will break Ooize server > (servlet, jsp, jasper, jetty, .... JARs). We should first get a Hadoop > client with the 'client' JARs, then we could do that. Right. But this one is not hopeless. Today we've got a starting point for Hadoop client in Hadoop 2.x. Thanks, Roman.
