Hi,
On Sat, Dec 13, 2014 at 8:51 PM, Frank Caputo <frank_at_frankcaputo.de> wrote:
> Now the parsed parameters should be made available similar to query
> parameters:
> - Iterable<String> ServletRequest.getPathParameterNames()
> - String getPathParameter(String name)
> - Map<String, String> getPathParameterMap()
>
Something like that might be nice indeed. Possibly we only need the last
method, as the first ones are just shortcuts for it.
> We also need to know the mapping to map to the view or what MVC wants to
> map to:
> - ServletRequest.getMapping()
>
Do you mean the kind of mapping exposure that's requested here?
https://java.net/jira/browse/SERVLET_SPEC-73
Kind regards,
Arjan
>
> Ciao Frank
>
> Am 10.11.2014 um 23:51 schrieb Edward Burns <edward.burns_at_oracle.com>:
>
> >>>>>> On Mon, 3 Nov 2014 23:50:11 -0500, Leonardo Uribe <
> leonardo.uribe_at_irian.at> said:
> >
> > AT> I agree with this. The pattern where meta data is specified with the
> > AT> artifact to which it applies instead of in some central file
> certainly
> > AT> looks to be the most popular way now (see also my recent mail to this
> > AT> list regarding 1196-faceletTagConveniences). Just think of the URL
> > AT> specified in @WebServlet for Servlets or @Path for JAX-RS.
> >
> > LU> There are some problems with this I would like to mention:
> >
> > Leonardo, I share your skepticism of the merits of this proposal.
> > Especially when we consider that we could propose something to the
> > servlet EG, the broad changes included in this proposal require much
> > more refinement and discussion, and prototyping.
> >
> > My first impression is that this idea would be better served in the MVC
> > spec.
> >
> > Ed
> > --
> > | edward.burns_at_oracle.com | office: +1 407 458 0017
> > | 0 work days til Devoxx 2014
> >
>
>