JNDI availability not correctly detected in Google App Engine

[omnifaces]

JNDI availability not correctly detected in Google App Engine

[BalusC]

This is strange. There's a Class.forName("javax.naming.InitialContext") test beforehand which should avoid exactly this exception. https://github.com/omnifaces/omnifaces/blob/1.7/src/org/omnifaces/config/BeanManager.java#L69

[BalusC]

I solved it differently, by a JNDI.lookup("java:comp") test beforehand. Works at least in JBoss EAP 6.2, WildFly 8.0.0, TomEE 1.6.0.2 and Tomcat 7.0.53 + Weld 2.2.0.

It's in today's 1.8 snapshot. https://oss.sonatype.org/content/repositories/snapshots/org/omnifaces/omnifaces/1.8-SNAPSHOT/ Please give it a try on your GAE and let me know.

[rmartony]

Hi BalusC, thanks for the quick reply.
I didn't realize at first sight that it is a warning:

WARNING: /search.jsf
java.lang.NoClassDefFoundError: javax.naming.InitialContext is a restricted class. Please see the Google  App Engine developer's guide for more details.
    at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:51)

As you commented earlier, It's strange because even there is a test using Class.forName("javax.naming.InitialContext"), the Exception does not get caught.

I tried with omnifaces 1.8 snapshot and I get the same result.
Also I'm using App Engine development enviroment, maybe I should check what happens in production.

Appreciate your help, regards,
Rafael.

[BalusC]

A warning? So your webapp continues to work normally? I understood that you couldn't get your webapp to deploy.

[rmartony]

That's right, the webapp apparently works fine in development besides the warning. Sorry that I misreported. Didn't try it in production already.
Thanks.