Exception sending context initialized event to listener instance of class org.grails.jaxrs.web.JaxrsListener

[budjb]

From @Blue-Head on June 12, 2014 17:30

I kind of figure out a work-around, however, I wanted to post it to be taken into consideration ..

I followed the installation guide and things were okay and valid but I didn't create any resources(Jax-RS), just included the maven -repo and installed the plugin to my Grails project but when trying to start the app, I get the below exception which fails the whole initiation.
Exception sending context initialized event to listener instance of class org.grails.jaxrs.web.JaxrsListener

then I create a resource using the command line: grails create-resource
and cleaned the app and tried to run again, and the error just gone. so that's illogical because you are forcing the app to run the command (grails create-resource) at least for one time !

Note: I am using GGTS 3.5.1 with Grails 2.3.9

Thank You

Copied from original issue: krasserm#51

[budjb]

From @davidecavestro on June 16, 2014 12:49

I see... there's some code in Jersey initialization that produces this behavior. I see no configuration props that could disable it. Maybe we could provide a way to completely disable jersey startup: it could be manually configured by users who applied the plugin but don't have any resource class (yet)

[budjb]

@Blue-Head This is something I'd like to add better error handling for. As @davidecavestro pointed out, this is an internal Jersey process that causes this if there are no root resources found at initialization. I think we can just skip initialising if no resource artefacts are found.