Hello,
Apologies if a similar question has been asked before.
What is the recommended way (now or once it becomes supported) to add custom extensions to Jersey ?
For example. It's a hypothetical example but hopefully it will clarify what I'm looking for.
Suppose I'd like to support the following request :
GET /myresources?$filter[id > 1]
That is I'd like to get back the collection of resources with ids > 1 only. This is a feature which I'm going to say my service runtime will support automatically, without an application code having to deal with it.
To automatically support a feature like this one on top of Jersey, I'd need an access to an actual resource class so that I could figure out few things about the actual collection class and its individual members. I this case I'd need my extension be invoked after the actual invocation on the resource class occurs.
Another possible example. Just for fun, I'd like to generate a WSDL 2.0 representation (even though I like WADL :-)) for my resource known to support just GEt & POST. Once again I need an access to the resource class, but in this case before the invocation occurs.
Can you please advise me on how one can provide such extensions in Jersey ? If it's not possible now, are there any plans in Jersey to let users plugin custom extensions in the future ?
Many thanks, Sergey
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland