You mentioned it breaks the config. Can you write up some before and after examples of that?
Note, we've never ever broken config without still supporting the previous version. We supported the OpenEJB 2.x config for years. Part of the reason I was on the conservative side when we were thinking about creating a new all-in-one descriptor. -David On Dec 31, 2012, at 1:35 AM, Romain Manni-Bucau <[email protected]> wrote: > Hi guys, > > i plan next year (hope to get it done for mid january) to change the > default rest deployment > > the idea is to deploy a jaxrs Application instead of deploying each > endpoint (== give the Application to cxf) > > the main reason is to simply reuse the rest routing instead of relying > on the servlet one > > example: > > given the following endpoints > -> /users > -> /user/1 > -> /foo > > we need 2 classes because we will bind /users/*, /user/* and /foo/*. > It is not so rezst compliant. > > > a side effect is to no more need @Path on class level :) > > > my plan is the following: by default if an application is provided use > it or if not create an internal one (like in wink IIRC). Then bind a > servlet for the application. The binding will be /* is nothing is > specified or the application path is provided (as always ;). > > i already talked about it but never had a case where it was blocking. > > here i have an app where i have to write too much classes because of > it (or add a routing filter which is stupid). > > think to a user management class: /login, /logout, /users....already 3 > classes :s > > i plan to switch to this deployment by default because this is the > only way to get something working the > > wdyt? > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau
