GitHub PushEvent at 2014-07-29 01:20:43
Repository: emb-jetty-webservice-eval
Actor: korena
Payload: {"shas":[["1cdf5288267ec5b8621d011f4799f5caaf6ac1ab","171efcdbb89667bc54bbc6ba1fc0828e79c4e514@gmail.com","So the issue of the weird war structure is resolved by removing the archive classes thingy from the maven war plugin, so that's that.\n\nAfter this change, the server logs state that weld is properly managing the CDI beans that are meant to be injected, after having them implement Serializable that is.\n\nThe issue of the injection null pointer exception still persists, and the exception seems to be too short to be useful, I am still working on reducing the application to a\nreasonable setup. Mainly, I need to deal with the WEB-INF/lib directory containing jetty specific jars, that should only be present outside the webapp's WEB-INF.\nAfter resolving this issue, I will pay a closer attention to the null pointer's legendary nuisance.","moaz korena",true],["b8545ba4e6a38110299cfb85dad6874497911b20","171efcdbb89667bc54bbc6ba1fc0828e79c4e514@gmail.com","So I got rid of the jetty specific classes being packed into the webapp's lib directory, some might suggest that giving those dependencies a provided scope\nwould suffice, but that seems to exclude them from being unpacked into the root of the war, causing the whole thing to fail, so the package exclusing in the\nconfiguration of the maven war plugin was necessary.\n\nNow is the time to deal with the annoying null exception at the injection point in the sevlet.","moaz korena",true]],"size":2,"ref":"refs/heads/master","head":"b8545ba4e6a38110299cfb85dad6874497911b20"}