wildfly

Hosting multiple domains with WildFly (Undertow)

微笑、不失礼 提交于 2019-12-05 06:25:34
For example I have two domains ( app1.com , app2.com ) and two ears ( app1.ear , app2.ear ). Each EAR file consists of ejb.jar and web.war. Also each WAR has context root: /app1 or /app2 . So if I start WildFly I will have two applications running on localhost:8080/app1 and localhost:8080/app2 . How I can bind app1.com to localhost:8080/app1 and app2.com to localhost:8080/app2 ? As I understand, I should modify Undertow subsystem configuration in standalone.xml. I tried: <server name="default-server"> <http-listener name="default" socket-binding="http"/> <host name="app1.com" default-web

WildFly 8 Logging Levels

痴心易碎 提交于 2019-12-05 06:13:38
How do I modify the WildFly 8 logging levels, specifically server.log. Currently I suspect they default to INFO and would like to change it to Debug or Error. For reference I've been exploring these articles https://docs.jboss.org/author/display/WFLY8/Logging+Configuration https://docs.jboss.org/author/display/WFLY8/How+To And suspect this is correct; <subsystem xmlns="urn:jboss:domain:logging:2.0"> <console-handler name="CONSOLE"> <level name="DEBUG"/> <formatter> <named-formatter name="COLOR-PATTERN"/> By default the console-handler is set to INFO and the FILE handler does not have a level

Activate JaxbAnnotationModule on Wildfly

北城余情 提交于 2019-12-05 06:02:16
I am trying to setup a REST service on Wildfly 8 that returns JSON with customized enum Values. I know that Wildfy uses Jackson 2.3 for the serialisation. I also know that when registering the JaxbAnnotationModule with the Jackson ObjectMapper the serializer produces the correct result. The question is, how do i configure my Wildfly Instance or my web-project to use this module. OK, to make this more clear, a simple example. First, this works properly and generates the result I need. @XmlEnum public enum TestEnum @XmlEnumValue("2") TWO; } public class Test { public static void main(String[]

Wildfly: Why I get only “Forbidden” if I call my Web application?

廉价感情. 提交于 2019-12-05 04:02:39
Yesterday our web application ran fine on WildFly 9. Since this morning I get only a "Forbidden" in the web browser. We don't use JAAS. There is also no difference if I set the following value to false in the standalone.xml : ... <subsystem xmlns="urn:jboss:domain:ejb3:3.0"> ... <default-missing-method-permissions-deny-access value="true"/> ... </subsystem> ... What can be the reasons that WildFly only shows the "Forbidden" page? EDIT If I set the log level for package org.jboss.security to TRACE I get the following message in the log file while calling the page: 2016-01-27 12:58:15,354 TRACE

What versions of libraries are shipped with WildFly 9.0.1.Final

大兔子大兔子 提交于 2019-12-05 03:46:48
I was looking in https://docs.jboss.org/author/display/WFLY9/Documentation , but there is no info. Especially I want't to know version of hibernate-entitymanager & hibernate-jpamodelgen. The easiest way is to look at the pom.xml file for the 9.0.1.Final build: https://github.com/wildfly/wildfly/blob/9.0.1.Final/pom.xml The relevant lines you are looking for are probably: <version.org.hibernate>4.3.10.Final</version.org.hibernate <version.org.hibernate.commons.annotations>4.0.5.Final</version.org.hibernate.commons.annotations <version.org.hibernate.validator>5.1.3.Final</version.org.hibernate

What is the purpose of javax.servlet.jsp-api

我只是一个虾纸丫 提交于 2019-12-05 02:45:01
问题 I'm learning how to make a servlet 3.1 compliant webapp, that will run on JBoss wildfly 10. I use maven for dependencies, and I'm unsure what the following dependencies do exactly, and if they are included/not included in the servlet container: <dependency> <groupId>javax.servlet</groupId> <artifactId>javax.servlet-api</artifactId> <version>${servlet.version}</version> <scope>provided</scope> </dependency> <dependency> <groupId>javax.servlet.jsp</groupId> <artifactId>javax.servlet.jsp-api<

WildFly running, project deployed, but 404

天涯浪子 提交于 2019-12-05 02:07:15
i cant understand why for the project it return 404 or cant connect to the host, since the wildfly start page open perfectly My web.xml <?xml version="1.0"?> <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"> <display-name>HelloWorld</display-name> <!-- <welcome-file-list> <welcome-file>index.html</welcome-file> </welcome-file-list> --> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp

How can i run wildfly 8 in port 80

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-05 00:54:38
问题 How can i run wildfly 8.2.1 in port 80? I can run wildfly in different ports by changing the offset as below. <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:100}"> But unable to run in port 80. 回答1: Offset adds that value to all ports. So if you had http set to the default port 8080, an offset of 100 would set it to 8180. You want to set the socket for http. <socket-binding-group name="standard-sockets" default

MyEclipse CI 2018.9.0正式发布(附下载)

北城余情 提交于 2019-12-04 22:57:25
MyEclipse线上特惠,在线立享专属折扣! 火热开启中>> 此MyEclipse版本增加了对较新的Wildfly服务器的支持,修复了与PDT等第三方工具的兼容性,并在IDE中包含了许多错误修复。 【 MyEclipse CI 2018.9.0安装包下载 】 Wildfly 11, 12 and 13 新版本通过对新的服务器连接器添加了对这些服务器的支持。如果在服务器配置中使用ee8.preview.mode=true设置,则在Wildfly 12和13都提供对Java EE 8的支持。 针对与旧版本WebSphere的兼容性,特别是未安装修订包的版本,修复了许多小问题。 Webtools 3.10 新版本已将Webtools的集成版本升级到与Photon一起发布的版本中,与其他插件(如PDT(PHP开发工具))的兼容性问题现已得到解决,现在可以轻松安装到MyEclipse 2018中。 Java EE 8 Form Editors 基于表单的编辑器现在可用于Java EE 8配置文件,如web.xml,application.xml,web-fragment.xml等。 主题修复 有些用户可能在启动MyEclipse后看到对话框错误地提示重启。 除主题滚动条外,原始水平滚动条还会出现在某些编辑器中。 树形控件中的图标未以200%缩放比例正确对齐HiDPI显示。

How to obtain JBoss Server Group Name programatically when deployed to a domain

瘦欲@ 提交于 2019-12-04 21:51:42
How can I obtain the jboss eap 6.x / wildfly server group name programmatically from within a java enterprise application deployed to a domain? Some of the other jboss values such as node name can be obtained via system property values but server-group-name does not appear to be exposed this way. I would like to be able to show the server group name (i.e. the cluster name) in a system diagnostics function for technical users to verify they are looking at the correct system... (npe, dev, prod etc) One other (and maybe better) way to do it is to use the management API https://docs.jboss.org