+1 on the documentation for the new code. Many thanks to Michael & John for your help!!! Han
From: Henry Saputra <[email protected]> To: [email protected] Date: 03/28/2011 03:29 PM Subject: Re: What happened to the JsHandler? It would be nice to have some kind of wiki entry about how the new JS processing flow works. - Henry On Mon, Mar 28, 2011 at 12:20 PM, John Hjelmstad <[email protected]> wrote: > Yes, it has. > > It's been split into three JsProcessor classes. In order: > 1. GetJsContentProcessor, which previously delegated to JsHandler. Now it > does what it says: gets all the "raw" feature JS to process. > 2. ConfigInjectionProcessor, which collects and injects > gadgets.config.init({ ... }); information. > 3. CompilationProcessor, which calls JsCompiler. > > All these classes are available in: > http://svn.apache.org/repos/asf/shindig/trunk/java/gadgets/src/main/java/org/apache/shindig/gadgets/js/ > > The change was done to better isolate logic (underlying code is now pretty > fully tested), get to consistency between debug and compiled JS (compiled = > debug + compilation rather than a mixture), and to have consistency w/ > metadata-served JS and HTTP-served. > > [edit: thanks Michael for the updated code snippet] > > --j > > On Mon, Mar 28, 2011 at 12:09 PM, Han Nguyen <[email protected]> wrote: > >> I just pulled down shindig trunk and found that package >> org.apache.shindig.gadgets.servlet.JsHandler is gone. Has it been evolved >> into some other class(es)? >> How does the new code work? >> Thanks! > -- Thanks, Henry
