Hi Doug Kohlert,
I will be one of the consumers of this Resource Model. I would like to
use this to model the WADL, so
that I can extend WADL document (ie add custom metadata to WADL for
consuming by Web 2.0 clients)
So in this regard I would like to have a Resource Model that can be used
across WADL or jersey. As well
having abstraction will help. I think this Resource Model should not be
tied to any Jersey API, rather
Jersey APIs should use this Resource Model.
What do you think?
Thanks
Ayub
Doug Kohlert wrote:
> All,
> I am working on a Resource model that can be used at tool time and
> runtime to model a resource.
> How tightly coupled should I make this to the jersey classes? For
> example, should I be storing
> a String[] or a MediaTypeList?
I prefer to have
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: dev-help_at_jersey.dev.java.net
>