[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21059: ------------------------------------- I spoke with Fred yesterday discussing some of these issues. I think it might fit better there, but it should also be possible for a user to handle it with a wildfly adapter. The issues with handling a 'docker' adapter is that the docker must be absolutely generic and extensible. The problem is deploying to a tomcat may just need a .war file deployed, while deploying to wf / eap requires a blah.war AND a blah.war.dodeploy. Basically, there's custom behavior all over the place that needs to be changeable... so it will require a lot of planning to make something generic enough that can still work for a wide array of usecases. Trying to get some minimal functionality that makes a simple wf docker container work with the existing wildfly server adapter is definitely useful. Either way, I'd say that this basically works as expected, as a debugger can connect to a simple wf inside a docker container after recent enhancements. The workflow may not be that convenient, but that can be improved through a generic docker container. -- This message was sent by Atlassian JIRA (v6.4.11#64026)