> But I do not think this is done by proclaiming that since something is
> not REST, it can not be included in JAX-RS, unless this is what JAX-RS
> specification and reference implementation project state as the goal.
Well, actually JAX-RS means "Java API for RESTful WebServices", so I have to
disagree in that point. If JAX-RS would mean "anything useful that can be
done with http" (what it doesn't) then I would agree with you.
> So: developers involved with JAX-RS process: is there such strict
> relationship?
Actually this is not a question of what developers think but of what is
found on
https://jsr311.dev.java.net/ ("Summary: JAX-RS: Java API for
RESTful Web Services") and on
https://jersey.dev.java.net/ ("Jersey is the
open source (under dual CDDL+GPL license), production quality, JAX-RS (JSR
311) Reference Implementation for building RESTful Web services.").
> How does JSR-311 position itself here?
Look at above two links and you know the answer.
> Am I right to
> assume that it is more along "inspired by REST" ("that other web
> service thing that is not SOAP") than strictly defined by REST?
From what is found on those web sites, you are wrong, sorry.
>
> -+ Tatu +-
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net