Jax-ws is also a standard part of java se 6. It even contains an embedded http server. No need for any additional libraries.
-Neil On 2 Dec 2008, at 16:59, "Alexis Moussine-Pouchkine" <[EMAIL PROTECTED] > wrote: > > Speaking for the "standard" side of things: > JAX-WS is part of Java EE 5 and JAX-RS (1.0 shipped recently) is set > to be in EE 6. > Both heavily rely on POJOs and annotations such that, while doing > Web Services. > > Working on GlassFish I'm biased, but I'd suggest Metro > (http://metro.dev.java.net) especially for .Net interop for JAX-WS and > Jersey (http://jersey.dev.java.net) for JAX-RS. > > Of course, knowing more about your use-case and requirements would > help answer this rather generic question. > > cheers, > -Alexis > > On Tue, Dec 2, 2008 at 3:55 PM, Casper Bang <[EMAIL PROTECTED]> > wrote: >> >>> this - not a whole framework which I would have to adopt. >> >> This is Java, you are supposed to adopt frameworks every day. >> >> Kidding aside, have a look at XStream. It is not a framework as much >> as a generic serializer facility, which can be used in a REST style >> service layer, turning your DTO's into XML or JSON. Very very KISS: >> http://xstream.codehaus.org/json-tutorial.html >> >> /Casper >>> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
