edit: no *new* flag since we still have the old one
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-01-26 17:55 GMT+01:00 Romain Manni-Bucau <[email protected]>: > hehe, when we discussed it I said it will break eveything (even sent a > mail when did the change AFAIK) but some people said it was a must and > not a nice -> why there is no flag > > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.com > https://github.com/rmannibucau > > > 2015-01-26 17:52 GMT+01:00 Andy <[email protected]>: >> -1 >> >> Thiagos example should simply work out of the box: >> https://github.com/tveronezi/rssreader >> On the 1.7.x branch new functionality that breaks old concepts should really >> be a flagged option, even if the new feature is better. >> >> Andy. >> >> >> On 26/01/2015 10:19, Jonathan Gallimore wrote: >>> >>> I've started another the thread to discuss this - hope that's ok. Will >>> leave the vote open for a while longer in case there's further feedback. >>> >>> Thanks >>> >>> Jon >>> >>> On Mon, Jan 26, 2015 at 2:00 AM, Thiago Veronezi <[email protected]> >>> wrote: >>> >>>> -1 -> The default servlet is catching the RS requests. >>>> >>>> Basically, in single-page-applications, I need to map the default servlet >>>> in a special way... >>>> >>>> . >>>> . >>>> . >>>> <!-- The trick is to put all your static files under the same >>>> directory >>>> and map the "default" servlet to it --> >>>> <servlet-mapping> >>>> <servlet-name>default</servlet-name> >>>> <url-pattern>/app/*</url-pattern> >>>> </servlet-mapping> >>>> >>>> <!-- Any other request will point to the "index.jsp" page. This way >>>> YUI >>>> will be able to manage page transitions >>>> at the client side in case the user starts the application from >>>> a >>>> permalink. --> >>>> <servlet> >>>> <servlet-name>index</servlet-name> >>>> <jsp-file>/index.jsp</jsp-file> >>>> </servlet> >>>> <servlet-mapping> >>>> <servlet-name>index</servlet-name> >>>> <url-pattern>/*</url-pattern> >>>> </servlet-mapping> >>>> . >>>> . >>>> . >>>> >>>> TomEE 1.7.2 returns "index.jsp" for all my rest calls (GET >>>> http://localhost:8080/myapp/rest/users, for example). >>>> >>>> After reverting back these two commits, the system gets back to normal. >>>> >>>> >>>> https://git1-us-west.apache.org/repos/asf?p=tomee.git;a=commit;h=544806da419bc2f5ab8bc936a989ff99bc9d891b >>>> >>>> >>>> https://git1-us-west.apache.org/repos/asf?p=tomee.git;a=commit;h=cb135dd6344f93ed24888cafcc05d0cfbb0c62a9 >>>> >>>> @Romain, >>>> Can you take a look? I'm not sure what was the idea. >>>> >>>> []s, >>>> Thiago. >>>> >>>> >>>> On Sun, Jan 25, 2015 at 9:36 AM, Jonathan Gallimore < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> Sorry, should have added that. It's: >>>>> https://repository.apache.org/content/repositories/orgapachetomee-1045 >>>>> >>>>> Regards >>>>> >>>>> Jon >>>>> >>>>> >>>>> >>>>>> On 25 Jan 2015, at 14:19, jieryn <[email protected]> wrote: >>>>>> >>>>>> On Sat, Jan 24, 2015 at 4:20 PM, Jonathan Gallimore >>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> Maven Repo: >>>> >>>> https://dist.apache.org/repos/dist/dev/tomee/staging-1045/ >>>>>> >>>>>> Where is the actual Maven artifact staging repository for this? So my >>>>>> projects which depend on TomEE can be built and tested against the >>>>>> candidate. Thanks! >> >> >> -- >> Andy Gumbrecht >> https://twitter.com/AndyGeeDe >>
