Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Having trouble using Embedded Jetty and WebApplicationInitializer with a WarFile deployment

On 09/23/2014 08:07 PM, David Kowis wrote:
> On 09/23/2014 04:52 PM, Joakim Erdfelt wrote:
>> Here ya go

Unfortunately, I'm not a winner :(

On master of my project, I have incorporated the changes in your commit,
albeit, I'm using log4j2, but I've translated the logback config to a
log4j2 config, so all the logfiles exist.

I moved dependencies around so that they matched the example here, and I
split up the servlet-style vs the war-style into separate projects, so
that their classpaths are nice and separate. (Rather than the
experimentation in the same project) I'm pretty sure I covered
everything in your commit, because it was relatively simple, but it
doesn't seem to run.

I've cleaned and reorganized the projects a bit to make it easier to
experiment with these things:

To run it using the embedded jetty servlet config:
* gradle :valve:run

To run the war with embedded webapp context (which I still can't get
working :( ):
* gradle :valveWar:run

To run the war file in standalone jetty:
* gradle jettyEclipseRun

I'm watching the logs in the valveWar project, and I don't see it ever
try detection of the WebApplicationInitializer :(

I could pastebin the entire debug log but it's super huge.

I have success in jettyEclipseRun, and gradle :valve:run, but not in
gradle :valveWar:run.

Thanks again,
David Kowis

<snipping old stuff>

Back to the top