I got it to work by calling wrapper.registerJMX(context).
StandardWrapper.registerJMX() is a protected method. I extended the class
so that I can invoke StandardWrapper.registerJMX() from the subclass.
To me it appears like it is a bug. What is the point in letting a child be
added to an already
It's been a while since I looked at it, but once the context is started,
the only way to update mappings it to invoke an additional JMX call to
get the mapping registered with the connector.
Take a look at
org.apache.tomcat.util.http.mapper.Mapper
org.apache.tomcat.util.http.mapper.MapperListene
