Paul Sandoz wrote:
> Hi Dan,
>
> Dan Diephouse wrote:
>> I have mixed feelings on this. I've done some integration between
>> Jersey and Mule, and the HTTP interfaces that are there worked quite
>> well.
>
> Good to know thanks for the feedback, please let us know if anything
> does not work or is problematic for you and we can try to resolve it.
>
Everything went very well so far. I have to say it was way way easier to
integrate than I thought it would be. My only gripe is that things
aren't in the Maven repository yet :-)
If anyone is interested the code is here:
https://svn.muleforge.org/mule-transport-jersey/trunk/
Would it be appropriate to announce integration like this on the
dev/user list once its ready for more general consumption?
>
>> For instance, has anyone thought about NIO support and implementing
>> some type of pause/resume functionality?
>
> Briefly, related to how can we support 100 (Continue) at the POJO-level.
> One solution is to return a 100 response with a Future that returns
> another response. As for the more general Async at the low-level i do
> not know, i need to understand better this area.
>
> Any ideas from yourself and others on the list on how we may support
> such a feature by extending the POJO model and low-level would be very
> welcome.
Another approach might be to handle some type of special exception. i.e.
something like throw new PauseInvocationException(callback); At this
point Jersey could stop the invocation. It could then resume upon some
event (of the user's triggering) and the user could use the callbackto
send the actual response.
Cheers,
- Dan
--
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog