Joe Lauer

Just wondering what you ended up doing? The library attempts to recover from bad data -- although it may think in this case that the session is hosed -- e.g....

Sometimes I think Netty4 should have taken a new project name due to its massive backwards incompatibility. Have you dug into what you think the underlying problem is?

Built a simple project that helps publish jars of the native code and extracts it at runtime. https://github.com/fizzed/jacob

Built a simple project that helps publish jars of the native code and extracts it at runtime. https://github.com/fizzed/jacob

Built a simple project that helps publish jars of the native code and extracts it at runtime. https://github.com/fizzed/jacob

If gauva is on the classpath, I believe that becomes the default used.

Hmm.. it appears the Guava activation was commented out at some point. In RockerStringify: ```java static public final RockerStringify RAW = new RawStringify(); //static public final RockerStringify HTML = RockerRuntime.createDefaultHtmlStringify();...

Actually, I just fixed a unit test that was failing if i re-activated it, and it seems to work well now. I pushed up to master fixing this guava issue....

Made some headway. On the page in our app that works, it's a very complicated page and the user would only see the Select component if they were already on...

@ryanrombough Unfortunately no. Only workaround is what i mentioned above -- you have to delay rendering of the widget so it doesn't occur on the first react render().