Solomon Duskis wrote:
> I'm pretty happy with where the resteasy-spring integration is going.
> I'm trying to figure out what's next. Here are some ideas. Please
> confirm :
>
> 1) Change ResteasyProviderFactory to not be a singleton reference, but
> rather to be a ThreadLocal (or something else that won't break NIO
> servers). It's current singleton-ness prevents creating multiple
> instances of the ProviderFactory
+1. I've been meaning to do that. As you can probably guess from the
code, a few things were hacked together in prototype fashion. This was
one of them.
> 2) Documentation! (and a blog entry)
LOL! +1 Maybe a dzone article too describing our entire Spring integration?
> 3) Rename from resteasy-springwebmvc to resteasy-spring, and remove the
> spring dependencies from resteasy-jaxrs. This begs the question:
> Should the spring disptacher servlet or the resteasy dispatcher servlet
> be the "preferred" approach for spring integration?
Yes, all Spring stuff should be moved to a resteasy-spring module.
> 4) reduce the duplication in the Spring MVC classes (namely
> ResteasyHandlerAdapter) and SynchronousDispatcher.
Yes. I think this will help out Seam integration as well.
> 5) spring NamespaceHandlers for syntactic sugar
>
> Any other thoughts?
>
Only other thought is that I'm glad somebody is driving this! Thank you!
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
|
