[
https://issues.apache.org/jira/browse/TOMEE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460376#comment-13460376
]
Romain Manni-Bucau commented on TOMEE-423:
------------------------------------------
I got the idea.
First transport of remote EJBs is currently vendor dependent (typically the
provider url is here for it)
Then the point is what do you expect as config? you'll need to provide a
context name + a path + (if mandatory) security
The question is now what is pexected as action for this issue:
1) just document the servlet
2) create a context for transport -> please try to show us the conf you expect
3) other
Thanks!
> Move TomEE's transport out of the tomee's management UI web app
> ---------------------------------------------------------------
>
> Key: TOMEE-423
> URL: https://issues.apache.org/jira/browse/TOMEE-423
> Project: TomEE
> Issue Type: Improvement
> Affects Versions: 1.0.0, 1.5.0
> Reporter: Alex the Rocker
>
> As a measure of security hardening, people want to delete the application
> server's management UI to prevent remote access to it ; especially for app
> servers exposed to Internet access.
> Problem with removing tomee from webapps directory is that it contains EE
> features such an EJB transport.
> This JIRA is to request a separation of TomEE transport features from TomEE
> management web app ; so that this later web app can safely deleted without
> risking any regression for web applications run-time features.
> Apache Tomcat supports with process, so it can be a showstopper for
> organizations considering a move from Tomcat to TomEE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
