Paul Sandoz wrote:
> Nam Nguyen wrote:
>> This is already implemented by Peter. For example:
>> http://localhost:8085/WebApplication9//resources/customers/?start=0&max=10
>>
>
> Oops, i should keep more up to date. Very good! i just had a close
> look at the generated code :-)
>
> Is there a change log between updates and/or feature set docs that i
> should be looking at?
This is one I would love to know how jersey project infrastructure setup
for it. For now, roughly we have to rely on engineering plans:
http://wiki.netbeans.org/wiki/view/RESTFcsPlan
http://wiki.netbeans.org/wiki/view/RESTNb6.1Plan
>
> For the CustomerDB generated code I like the way you are using an
> anonymous inner class in the for the customers associated with a
> discount code.
On the other hand, I also like Jersey example Bookmark utility class
TransactionManager and abstract Transactional. It is neat and making
use of JTA as well as container-manager persistence. With a quick
comparison, one can see that the plugin generated resource transaction
code made assumption of local transaction which I think reasonable and
have better performance. We might need to somehow give user choice of
either transaction model.
>
> It would be nice if Jersey could help in the support of persistence,
> for example by perhaps providing its own persistence service like the
> one generated.
I think this would be cool as it will simplify application code.
> I think WebBeans could be a lot of help here to inject stuff
Could you please explain more.
> and have transacted HTTP methods.
Maybe I missed something. Wouldn't this be against the goal of
REST-style: achieve stateless accesses to resource?
-Nam