Hi Bill,
>> REST is web. Why only offer XML and JSON, and not HTML?
> Because 30 million other frameworks already do this, including a few
> in Java EE (JSF, JSP). JSP integration sounds interesting, but beyond
> that we would be pretty much encroaching on the space of others.
We define an API for REST, but don't want support the root of REST?
That's illogical to me.
I don't want to build a new template framework, only easy integration of
existing one. IMO the best would be a generic resolution, where a JAX-RS
runtime developer could decide on it's own which template engines etc.
he want's to support, like the providers, where every JAX-RS runtime
developer could provide his own provider set, with some obligatory. But
there is a defined way to integrate them.
The same we should (IMO) do here. Define a way to use them, and leave it
to the runtime developer which to support. We could define JSP for
Servlet based JAX-RS runtimes obligatory, but IMO it is important to
have a standardized way to integrate and use HTML (and other mime types)
creating possibilities.
best regards
Stephan