RE: URI matching question

igris.org > Objet : Re: URI matching question > > Thierry, > > It works nicely. I create a couple of routes for each > resource. Does it > make sense to move some of this back to the core. > > cheers > > Jim Alateras wrote: > > cool, i'll give it a go

Re: URI matching question

Thierry, It works nicely. I create a couple of routes for each resource. Does it make sense to move some of this back to the core. cheers Jim Alateras wrote: cool, i'll give it a go today. cheers Thierry Boileau wrote: Hi Jim, as a workaround, you can define 2 routes like this : //Serve

Re: URI matching question

cool, i'll give it a go today. cheers Thierry Boileau wrote: Hi Jim, as a workaround, you can define 2 routes like this : //Serves only http://localhost:6080/appcontext/version route = [...]attach("/version", <...>); route.getTemplate().setMatchingMode(Template.MODE_EQUALS) //Serves only htt

Re: URI matching question

Hi Jim, as a workaround, you can define 2 routes like this : //Serves only http://localhost:6080/appcontext/version route = [...]attach("/version", <...>); route.getTemplate().setMatchingMode(Template.MODE_EQUALS) //Serves only http://localhost:6080/appcontext/version? // andhttp://

RE: URI matching question

Hi Jim, >From an URI specification point of view, there is no difference between a URI with or without a query string. The query string can have a fixed format or use a common name/variable format. The general routing algo "respects" the initial URI submitted and tries to match the start of the r