Hi Bill
I'm not going to advocate any specific language but WADL To Java
generation works fine, all the type info is deduced either from grammars
or native XSD types.
It is very hard to have a universal language that would offer an
adequate description for both XML and JSON grammars, though some tricks
with WADL at least are possible (WADL in JSON, etc)
On 22/01/15 22:10, Bill Burke wrote:
> Last I saw WADL doesn't understand Java methods, types, etc. Would be
> similar to <servlet-mapping> except would have java method declations
> (like ejb.xml).
>
> JPA started as annotation only, then added an external (XML) metadata
> descriptor. One reason for this was so that you could override settings
> without recompiling code.
We've had a no annotations extension for years now (external model is
attached to a non annotated interface).
I thought you would like to have a model only, no even specific Java
classes... (FYI, having a generic handler is one way to deal with such
cases in routing engines, etc)
Sergey
>
> On 1/22/2015 10:22 AM, Sergey Beryozkin wrote:
>> Is that going to be a new WADL, Swagger plus some new policy like
>> extensions ?
>> On 21/01/15 21:07, Bill Burke wrote:
>>> This is sort of on the same level as my Servlet.nextgen comment in an
>>> earlier thread. The idea here is that there would be a new deployable
>>> jaxrs archive type in Java EE. There would need to be a way to describe
>>> metadata in XML:
>>>
>>> * all JAX-RS annotations could instead be specific in XML
>>> * JAX-RS annotatiosn could be overriden in XML
>>> * Would need a way to define security constraints like in servlet spec
>>> * Would need to define authentication mechanisms and how they are
>>> configured.
>>> * Would need some APIs to come into JAX-RS. (i.e. being able to find
>>> Client IP Address, some kind of Servlet Context equivalent to get info
>>> about the deployment.
>>>
>>> An alternative reaction to all this could be to get some JAX-RS
>>> extensions to Servlet spec so that you could define JAX-RS metadata
>>> within web.xml, etc..
>>>
>>> I'm just throwing this out there for discussion.
>>>
>>
>>
>