Disable the message servlet by default#2000
Conversation
|
Does this mean that we're essentially dropping support for the REST messaging API? |
cshannon
force-pushed
the
disable-message-servlet
branch
from
ad8ac87 to
15d8d60
Compare
|
|
||
| <display-name>Apache ActiveMQ REST API</display-name> | ||
|
|
||
| <servlet> |
There was a problem hiding this comment.
Maybe worth to keep in the file, but commented, just in case the user absolutely wants to use it.
There was a problem hiding this comment.
I originally just commented it out but then removed it entirely (it's still the demo project). I can go either way though. @mattrpav what do you think?
There was a problem hiding this comment.
This was my original commit before force pushing: ad8ac87
There was a problem hiding this comment.
I'm good with comment it out as a good step here. It'll surface questions from users needing to reanble it and we'll get a sense of how it is used.
Going forward (v7) there is probably a modernization task for this.
No. This is a security stance of being more “locked down” by default. Administrators are then encouraged to enable features and service they need |
cshannon
force-pushed
the
disable-message-servlet
branch
from
15d8d60 to
ad8ac87
Compare
4 participants
The servlet will still be enabled by default in the web demo project
Edit: I marked the servlet as deprecated and also added comments about why