On Fri, Apr 30, 2010 at 1:20 PM, Copeland, Bryan <[email protected]> wrote: >>I was only really thinking in terms of how we expose the API methods of the >>Wookie server, so things like "/wookie/widgets?format=atom" rather than the >>widgets themselves which should just use "normal" HTML, CSS and JS. So not as >>big a risk (or payoff) really. > > Oh, I thought it might be an option to use it to stick dynamic data into some > local widgets. If it's just intended for formatting API calls it almost > sounds like a case for using RESTlet or Jersey or something like that > instead? They tend to let you bind data models for many different formats, > with native support for XML, SOAP, RSS, Atom, JSON, etc; with URL-templating > and few, if any, other dependencies... > > RESTlet: http://www.restlet.org/ > Jersey (JAX-RS): https://jersey.dev.java.net/ > > Maybe I'm misunderstanding what you wanted to accomplish with the Template > Engine though? >
I don't know the full details about the requirements/scenarios, but if you are talking about REST/JAX-RS we also have Apache Wink and Apache CXF that are JAX-RS compliant. I'm also working in some REST features for Apache Tuscany, but I'm not sure if this applies here. > Also, maybe an obvious question if I dig through some previous email but do > you have a link for the Issue Tracker submissions? > > Thanks, > > Bryan BTW Brian, I'd be interested in looking into your widgets and how they are handling the cross-domain stuff if that is available somewhere. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
