The WAR has everything under WEB-INF (class files, etc.). The jar has it all at top-level. It looks like a WAR can't be used as a JAR as I suggested in my previous mail so, yeah, stargate contrib would seem to have WAR and JAR targets (unless someone knows better).
St.Ack On Sun, Feb 7, 2010 at 5:23 PM, Andrew Purtell <apurt...@apache.org> wrote: > The Stargate WAR is meant for deployment into some totally seperate servlet > container -- Jetty, Tomcat, Glassfish, etc. The provided jetty.xml is just an > example and maybe should be named jetty.xml.template to clarify. We could use > examples for other servlet containers besides Jetty. > > The Stargate JAR embeds a Jetty servlet container so one can run Stargate as a > standalone daemon, either in the background as is typically done with other > HBase daemons: > > sh ./bin/hbase-daemon.sh start org.apache.hadoop.hbase.stargate.Main > > or in the foreground for debugging > > ./bin/hbase org.apache.hadoop.hbase.stargate.Main > > ... with optional argument "-p <port>" to change the listening port. > > - Andy > > > > ----- Original Message ---- >> From: Paul Smith >> To: hbase-dev@hadoop.apache.org >> Sent: Sat, February 6, 2010 7:03:10 PM >> Subject: Stargate War - jetty.xml and dependencies >> >> Just a question about the contrib/stargate module. As I read it, it's >> designed >> to be both a standalone WAR _and_ JAR artifact? Is that correct? I can do >> that >> (probably not without a directory move), but I'm scratching my head to work >> out >> what the conf/jetty.xml is used for, because it doesn't appear in the ivy >> generated 'binary' output (maybe it's just missing). >> >> If someone could comment on where the jetty.xml should end up in a stargate >> binary (and indeed, where it should appear in a general hbase binary tar >> ball) I >> would appreciate it. I'm guessing it's designed to be used with Jetty to >> kickstart a simple app server, and assume that the generated stargate WAR is >> supposed to live somewhere relative (ie. 'webapps') to be launched under the >> /api/ context. >> >> Any knowledgeable folk able to comment on how this gets used? >> >> cheers, >> >> Paul > > > > > >
