On Thu, 22 Jun 2017 11:21:35 +0200, "Greg Wilkins" <gregw@...> said:

GW> what was finally decided about the named dispatchers? I think the null
GW> return is wrong, but I'm guessing too late to change??? Although it is
GW> still a draft?????

I realize that I gave you all very little time to review the null return
in the case of getNamedDispatcher():

On Wed, 14 Jun 2017 14:41:44 -0700, Edward Burns <edward.burns@...> said:

EB> ACTION: Since we are now after Pubilc Review, I would like to request a
EB> quick response on this. Please reply by COB GMT-0500 Friday 16 June
EB> 2017. No response indicates you accept this proposal.

However, Greg and then Mark's responses clearly came after my admittedly
fast deadline.

I would very much like to stick with the existing resolution. That
said, yes, it is a draft. I need to see if we can make a change like
this without having to do another Proposed Final Draft. Let me restate
Greg's counter proposal.

CounterProposal> If the servlet corresponding to this request was
CounterProposal> obtained using the getNamedDispatcherMethod method,
CounterProposal> this method returns the mapping last applied to this
CounterProposal> request to set the values of getServletPath and
CounterProposal> getPathInfo.

While I check on our ability to make this change without needing
to do another PFD, please take this opportunity to review Greg's above
CounterProposal. ACTION: If you really disagree with the null
resolution and would rather go with Greg's CounterProposal, please reply
with your thoughts by COB GMT-0500 Friday 23 June 2017.

GW> Can we have a tagged release of the API pushed to maven central that
GW> matches the PFD?

Yes, it's already there at GAV
"javax.servlet:javax.servlet-api:4.0.0-b07". I just checked
mvnrepository.com.

Thanks,

Ed

--
| edward.burns@... | office: +1 407 458 0017

On 22/06/17 10:21, Greg Wilkins wrote:

Ed,

what was finally decided about the named dispatchers? I think the null
return is wrong, but I'm guessing too late to change??? Although it is
still a draft?????

+1

Mark

Can we have a tagged release of the API pushed to maven central that
matches the PFD?

cheers





On 21 June 2017 at 22:56, Edward Burns <edward.burns@...
<mailto:edward.burns@...>> wrote:

The Proposed Final Draft has been posted to jcp.org <http://jcp.org>!

https://jcp.org/aboutJava/communityprocess/pfd/jsr369/
<https://jcp.org/aboutJava/communityprocess/pfd/jsr369/>

Congratulations everyone!

Ed






--
Greg Wilkins <gregw@... <mailto:gregw@...>> CTO
http://webtide.com

--

The Proposed Final Draft has been posted to jcp.org!

https://jcp.org/aboutJava/communityprocess/pfd/jsr369/

Congratulations everyone!

Ed

Hello Volunteers,

Here is a heads up that we have handed the Proposed Final Draft of the
spec to the JCP this week. The only difference between the Public
Review and the Proposed Final Draft is the item regarding
[73-MappingDiscovery] and ServletContext.getNamedDispatcher() discussed
last week.

Here is the tentative plan for the remainder of Servlet 4.0:

We will have a 21 day Proposed Final Draft phase, completing in early
July 2017.

We will start the Final Approval Ballot in late July 2017. The ballot
will run for 14 days, per JCP rules.

Thanks for all your effort on this long road.

Sincerely,

Ed and Shing-wai

--
| edward.burns@... | office: +1 407 458 0017