最近新项目上线，用了最新版本的JBOSS，现在改名叫wildfly了，本人部署过程中总结了以下几点比较关键的地方，看是否对大家有用处
JBoss服务器改成支持外网访问
在standalone.xml文件中找到
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
在这个下面加入
<interface name="any">
<any-ipv4-address/>
</interface>
另外把1改成2
1 <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
2 <socket-binding-group name="standard-sockets" default-interface="any" port-offset="${jboss.socket.binding.port-offset:0}">
访问端口的更改
<socket-binding name="http" port="${jboss.http.port:80}"/>
改为可以修改JSP页面不用重启
<servlet-container name="default">
<jsp-config development="true"/>
</servlet-container>
<jsp-config development="true"/>
</servlet-container>
部署的程序不用wildfly内置CXF包
在应用的WEB-INF目录下面增加该文件：jboss-deployment-structure.xml
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<!-- exclude-subsystem prevents a subsystems deployment unit processors running on a deployment -->
<!-- which gives basically the same effect as removing the subsystem, but it only affects single deployment -->
<exclude-subsystems>
<subsystem name="webservices" />
</exclude-subsystems>
</deployment>
</jboss-deployment-structure>
<deployment>
<!-- exclude-subsystem prevents a subsystems deployment unit processors running on a deployment -->
<!-- which gives basically the same effect as removing the subsystem, but it only affects single deployment -->
<exclude-subsystems>
<subsystem name="webservices" />
</exclude-subsystems>
</deployment>
</jboss-deployment-structure>