Hi,
You could use Rhino on the server and reuse any appropriate javascript (including GWT generated JS), but you would need a mapping script that gives the browser environment. For example:
http://ejohn.org/blog/bringing-the-browser-to-the-server/
But, perhaps you want to skip the java to js step for the server side and just use java on the server?
javascript page building = DOM manipulation and/or string concatenation: Fine for building pages in the browser on the client, but not on the server. But, perhaps enough for some needs and does make things simple.
How do you see Jackson working in this scenario?
Maybe you can use json to feed some *simplified* DOM implementation (and therefore would not be conformant, breaking browser compatibility) using Jackson for streaming transformations.
-Rob
On Jan 12, 2010, at 5:34 AM, Paul Sandoz wrote:
>
> On Jan 12, 2010, at 4:41 AM, Tatu Saloranta wrote:
>
>> On Tue, Mar 24, 2009 at 7:11 AM, James Strachan
>> <james.strachan_at_gmail.com> wrote:
>>> I'd love to see something like this too - though am a bit snowed for a
>>> few weeks to dive in and help just yet.
>>>
>>> My initial thoughts were that I wondered if we could wire in the GWT
>>> serialization on the server side; so we could on the client side do
>>> RESTful GET/PUT/POST operations using the regular JS/Java
>>> serialisation format from GWT? Failing that I was thinking of using
>>> Jackson
>>> http://www.cowtowncoder.com/hatchery/jackson/
>>>
>>> Using GWT generators we might be able to do some auto-proxy style
>>> client interface (like RESTeasy does) or maybe make a Jersey
>>> client-like API for use in GWT.
>>
>> I would also be interested, although right now I am focusing on
>> polymorphic deserialization aspects for Jackson. But after that (in 2
>> weeks or so) I might have more cycles. GWT is one of the things that
>> would be nice interoperate with.
>> I am not very familiar with GWT, but probably multiple not-so-experts
>> working together could patch together something usable. :-D
>>
>
> +1
>
> I think Jackson (or a sub-set of depending on capabilities) would be a nice fit for GWT.
>
> Paul.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>