There are cases where MP stuff may clash with older apps, and we caught a 
couple of these cases in TomEE TCK.

For instance if a webapp is only using servlets and is exposing a servlet in 
the context root, because MP expose predefined REST endpoints for health, 
metrics, openapi, etc. the REST Service deployer is going to override the 
context root to be able to deploy the MP specific endpoints and the original 
servlet path is not going to work anymore, so you get a 404.

Another case is if you already have any kind of servlet or rest endpoint with 
the same path of the specific MP endpoints.

So the point is, there is a risk that when you upgrade to a TomEE version with 
MP support your older apps may clash and they will break and I believe no one 
would want that :)

Cheers,
Roberto

> On 16 Jan 2019, at 17:46, David Blevins <[email protected]> wrote:
> 
> Zooming back to the start of this thread, can you give some insight on why 
> anyone would want to disable MicroProfile support?  I.e. some perspective on 
> the cost we're attempting to avoid so we can evaluate that against the cost 
> of disabling/enabling.
> 
> 
> -- 
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
> 
>> On Jan 16, 2019, at 8:00 AM, Roberto Cortez <[email protected]> 
>> wrote:
>> 
>> Yes, I think I would prefer automatic of course. There might be some 
>> challenges to be able to achieve that.
>> 
>> When I was working on it, I was stuck into a point where I was not able to 
>> determine if metrics are needed due to their use of interceptors and they 
>> are set up with CDI. I probably need to spent some more time looking into it.
>> 
>>> On 16 Jan 2019, at 15:00, j4fm <[email protected]> wrote:
>>> 
>>> Happy to contribute if/where I can, for sure - how?
>>> 
>>> If the enabling/disabling of MP scans per-context can be done automatically
>>> - great. If it's a manual configuration that's workable but automatic is
>>> obviously preferred - then things would just work.
>>> 
>>> 
>>> 
>>> --
>>> Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> 
> 

Reply via email to