REST related mods that loads an Application with an @ApplicationPath and does not require web.xml

merge changes required to load a web.xml and application named in the web.xml. Currently web.xml is hardcoded in ServingLayer.java but should probably be specified via a config param.
Hi Sean

It does look like OryxApplication with application-package may be the least complicated approach. Although somewhat frustrating, it was worth exploring the alternatives and attempting to minimize compile time dependencies. Minimally we all have a much better understanding of JAX-RS. A brief meeting in the near future makes sense.

> On Aug 12, 2014, at 10:42 AM, Sean Owen <notifications@github.com> wrote:
> 
> In oryx-ml-oryx-serving/src/main/resources/web.xml:
> 
> > @@ -0,0 +1,7 @@
> > +<web-app version="3.0"
> > +    xmlns="http://java.sun.com/xml/ns/javaee"
> > +    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > +    <servlet>
> > +        <servlet-name>com.cloudera.oryx.ml.serving.als.ALSApplication</servlet-name>
> (You can just push more commits to your work branch to update this PR, if you like. In this case it's your master.)
> 
> It's sounding like we need that OryxApplication back again, and go back to the application-package approach. That works, makes sense for end-users, and only unfortunately means a compile dependency on Jersey.
> 
> I think we don't need to worry about web.xml. If we need to write one for some reason to support a .war deployment, we'll just do that separately.
> 
> Packaging a .war seems possible here too as it's just a matter of bundling the same classes and leaving it to the user to edit web.xml if they must -- there's no way around that, it's just how JEE works. It's not a primary deployment model I am worried about anyhow, and I'm not concerned that there's a big reason this won't work elsewhere. Later we can tweak it if needed.
> 
> Shall we talk about this soon? and/or Kam feel free to fire again with a PR considering all of this discussion.
> 
> —
> Reply to this email directly or view it on GitHub.