Wildflyначало работы с wildfly

Using Eclipse

  1. Install the latest version of eclipse
  2. Make sure Xmx in eclipse.ini is at least 1280M, and it’s using Java 8
  3. In eclipse preferences Java->Compiler->Errors/Warnings->Deprecated and restricted
    set forbidden reference to WARNING
  4. In eclipse preferences Java->Code Style, import the cleanup, templates, and
    formatter configs in ide-configs/eclipse in the wildfly-core repository.
  5. In eclipse preferences Java->Editor->Save Actions enable «Additional Actions»,
    and deselect all actions except for «Remove trailing whitespace»
  6. Use import on the root pom, which will pull in all modules
  7. Wait (m2e takes a while on initial import)

wildfly-maven-plugin from group org.wildfly.plugins (version 1.2.1.Final)

A maven plugin that allows various management operations to be executed on WildFly Application
Server.

7 downloads

Artifact wildfly-maven-pluginGroup org.wildfly.pluginsVersion 1.2.1.FinalLast update 26. October 2017Newest version NoTags: executed that maven application allows various server operations wildfly management plugin Organization not specifiedURL http://www.wildfly.org License not specifiedDependencies amount 12Dependencies javax.inject, commons-compress, maven-core, maven-plugin-api, aether-api, stacks-client, wildfly-cli, jboss-logmanager, wildfly-controller-client, wildfly-launcher, wildfly-protocol, wildfly-plugin-core, There are maybe transitive dependencies!

wildfly-maven-plugin from group org.wildfly.plugins (version 1.2.0.Beta1)

A maven plugin that allows various management operations to be executed on WildFly Application
Server.

7 downloads

Artifact wildfly-maven-pluginGroup org.wildfly.pluginsVersion 1.2.0.Beta1Last update 09. August 2017Newest version NoTags: executed that maven application allows various server operations wildfly management plugin Organization not specifiedURL http://www.wildfly.org License not specifiedDependencies amount 12Dependencies javax.inject, commons-compress, maven-core, maven-plugin-api, aether-api, stacks-client, wildfly-cli, jboss-logmanager, wildfly-controller-client, wildfly-launcher, wildfly-protocol, wildfly-plugin-core, There are maybe transitive dependencies!

Building the images

Cloning the repository:

Building WildFly s2i builder image from scratch:

Building WildFly runtime image from scratch:

Building WildFly s2i builder image with a locally built WildFly server

script steps:

  • Builds WildFly () if is not set. If you have already build WildFly be sure to have used the maven argument.
  • Constructs and zip a local maven repository that contains all maven artifacts required by WildFly (JBoss module jars). NB during this phase an http server is started on port 7777 to serve maven local cache.
  • Creates the s2i builder docker image using the zipped repository.

Building your own application image

The script uses s2i command line tool and docker to create an image from your application src.

  • By default it uses and images. You can provide your own wildfly s2i builder and runtime images.

  • If no application name is provided, the image name is derived from the application src directory.

  • You can provide Galleon layers in order to build a trimmed-down server.

Structure of the Registry

The registry consists of two primary elements:

  • a single text file in the root of the repository, ‘registry.txt’ which is a simple alphabetically ordered list of capability names. This file provides a single location where users can quickly learn the names of available capabilities
  • a filesystem tree where the tree structure corresponds to the names of the capabilities. Each leaf in the tree is a ‘capability.adoc’ file which includes standard information describing a particular capability. The ‘template.adoc’ file in the root of the repository shows the standard format of a capability.adoc file.

wildfly-maven-plugin from group org.wildfly.plugins (version 2.0.1.Final)

A maven plugin that allows various management operations to be executed on WildFly Application
Server.

7 downloads

Artifact wildfly-maven-pluginGroup org.wildfly.pluginsVersion 2.0.1.FinalLast update 13. February 2019Newest version NoTags: executed that maven application allows various server operations wildfly management plugin Organization not specifiedURL http://www.wildfly.org License not specifiedDependencies amount 13Dependencies javax.inject, commons-compress, maven-core, maven-plugin-api, aether-api, stacks-client, jboss-modules, wildfly-cli, jboss-logmanager, wildfly-controller-client, wildfly-launcher, wildfly-protocol, wildfly-plugin-core, There are maybe transitive dependencies!

wildfly-maven-plugin from group org.wildfly.plugins (version 2.0.0.Final)

A maven plugin that allows various management operations to be executed on WildFly Application
Server.

7 downloads

Artifact wildfly-maven-pluginGroup org.wildfly.pluginsVersion 2.0.0.FinalLast update 02. November 2018Newest version NoTags: executed that maven application allows various server operations wildfly management plugin Organization not specifiedURL http://www.wildfly.org License not specifiedDependencies amount 13Dependencies javax.inject, commons-compress, maven-core, maven-plugin-api, aether-api, stacks-client, jboss-modules, wildfly-cli, jboss-logmanager, wildfly-controller-client, wildfly-launcher, wildfly-protocol, wildfly-plugin-core, There are maybe transitive dependencies!

GlassFish

GlassFish — это проект первоначально начатый Sun Microsystems для платформы Java EE, а теперь являющийся частью корпорации Oracle. Он доступен по двойной лицензии:

  • Общая лицензия на разработку и распространение (CDDL);
  • Стандартная общественная лицензия GNU (GPL) с исключением пути к классам.

Oracle больше не предоставляет коммерческую поддержку GlassFish Server.

GlassFish часто рассматривается как эталонная реализация Java EE и поэтому поддерживает Enterprise JavaBeans (управляемая серверная архитектура компонентов для модульного конструирования корпоративных приложений), JPA (Java Persistence API), JavaServer Faces, JMS (Java Message Service), RMI (Java Remote Method Invocation), JavaServer Pages, сервлеты и многое другое.

Glassfish позволяет создавать корпоративные приложения, которые являются переносимыми и масштабируемыми и которые интегрируются с устаревшими технологиями.

Он построен на модульном ядре на базе OSGi и работает прямо поверх реализации Apache Felix. Он также может работать с Equinox OSGi или Knopflerfish OSGi. HK2 абстрагирует систему модулей OSGi для предоставления компонентов, которые также можно просматривать как сервисы и внедрять во время выполнения, и использует производную Apache Tomcat в качестве контейнера сервлета для обслуживания веб-контента, с добавленным компонентом Grizzly, который использует Java New I/O (NIO) для масштабируемости и скорости.

Private capabilities

A capability can be private if the project that registers it does not wish its services or custom integration API to be depended upon by others. Any service or custom integration API exposed by the capability can be changed at any time and it is not necessary to record information in this registry about such services or integration API. However, the capability itself should be recorded, including descriptive information about what it does and what requirements it may have.

Private capabilities are useful because only a capability can depend upon another capability and use its services and integration API. «Anonymous» code cannot require capabilities because that would result in users not being able to determine what functionality would be lost if a required capability were removed. However, just because code wishes to use another capability and is willing to register itself as doing so doesn’t mean it is willing to publish a contract that other, unknown capabilities can rely upon.

Private capabilities are allowed to provide services or a custom integration API for use by other capabilities controlled by the maintainer of the private capability. However the private capability implementation is free to change those at any time. This kind of usage scenario is analogous to typical use of package-protected Java methods.

Немного официальной информации о 10 версии

  • Реализация сертифицирована на соответствие Full- и Web-профилям Java EE 7. Код WildFly распространяется под лицензией LGPL;
  • В отличие от коммерческого продукта JBoss Enterprise Application Platform, позиционируемого как полностью протестированная и сертифицированная платформа Java EE, WildFly ориентирован, прежде всего, на продвижение технологий. WildFly выступает в роли upstream-проекта для коммерческого продукта JBoss Enterprise. В качестве основной области использования WildFly рассматривается разработка и быстрое внедрение прототипов.

Основные особенности релиза

  • Прекращена поддержка Java 7, что позволило обеспечить более глубокую интеграцию с Java 8 Runtime. Добавлена поддержка текущих снапшотов Java 9;
  • Поставка ActiveMQ Artemis в качестве брокера рассылки сообщений (Java Message Service Broker), совместимого на уровне протокола и заменившего собой HornetQ;
  • Поддержка запуска хост-контроллера при помощи CLI. Новая команда embed-host-controller позволяет редактировать содержимое файлов domain.xml и host.xml без запуска дополнительных процессов или открытия сетевых сокетов;
  • Поддержка JavaScript в http-сервере Undertow.io, позволяющая создавать на языке JavaScript серверные скрипты, которые могут обращаться к CDI Beans и JPA Entity Beans. Указанную возможность удобно использовать для создания внешних обвязок или REST-обработчиков. Отредактированный код JavaScript становится доступен сразу и не требует перезапуска приложения;
  • Поддержка одиночного отказоустойчивого развёртывания приложения («singleton deployment»), при котором в случае использования группы кластеризованных серверов развёртывание будет произведено только на одном узле, но в случае выхода этого узла из строя, приложение будет автоматически перенесено на другой узел;
  • Поддержка одиночного отказоустойчивого брокера рассылки сообщений (Singleton MDB), запускающего доставку только на одном узле, но в случае сбоя использующего для обработки сообщений другой узел;
  • Автоматический выбор размера пула SLSB и MDB, в зависимости от имеющихся системных ресурсов;
  • Средства для миграции устаревших подсистем, таких как jbossweb (AS 7.1), jacorb (WildFly 8) и hornetq (WildFly 9), которые автоматизируют преобразование старых конфигураций в эквиваленты, работающие в WildFly 10;
  • В реализации Hibernate 5 значительно улучшено качество байткода, внесены оптимизации производительности и добавлены улучшения в API.

mvn wildfly:deploymvn wildfly:undeploymvn wildfly:redeploy-Plocalhost-Pdev

./standalone.sh -b=0.0.0.0 -bmanagement=0.0.0.0

  1. Иногда перезапуск WildFLy затягивается и долго подтягивается localhost:9990 — консоль.
  2. При запуске из Jenkins на Maven 3.3.9 с тэгом redeploy происходит утекание памяти и приложение удаляет обе версии war и ругается на дубликат. (Воспроизводится не всегда)

mvn wildfly:undeploy mvn wildfly:deploy

Supporting runtime-only requirements

Not all capabilities are usable as a runtime-only requirement, and the capability.adoc entry for a capability should express this.

Any dynamically named capability is not usable as a runtime-only requirement.

For a capability to support use as a runtime-only requirement, it must guarantee that a configuration change to a running process the removes the capability will not impact currently running capabilities that have a runtime-only requirement for it. This means:

  • A capability that supports runtime-only usage must ensure that it never removes its runtime service except via a full process reload.
  • A capability that exposes a custom integration API generally is not usable as a runtime-only requirement. If such a capability does support use as a runtime-only requirement, it must ensure that any functionality provided via its integration API remains available as long as a full process reload has not occurred.

Note that declaring support for use as a runtime-only requirement is part of the permanent contract of a capability, so it not should be done lightly. For example, the current implementation of a particular provider of a capability may require a full process reload in order to remove it, but other providers may not. Or, the particular provider requiring reload may be a current implementation detail but one that could be changed in the future. Declaring the capability supports runtime-only use precludes these possibilities.

wildfly-maven-plugin from group org.wildfly.plugins (version 1.2.0.Alpha6)

A maven plugin that allows various management operations to be executed on WildFly Application
Server.

7 downloads

Artifact wildfly-maven-pluginGroup org.wildfly.pluginsVersion 1.2.0.Alpha6Last update 23. June 2017Newest version NoTags: executed that maven application allows various server operations wildfly management plugin Organization not specifiedURL http://www.wildfly.org License not specifiedDependencies amount 12Dependencies javax.inject, commons-compress, maven-core, maven-plugin-api, aether-api, stacks-client, wildfly-cli, jboss-logmanager, wildfly-controller-client, wildfly-launcher, wildfly-protocol, wildfly-plugin-core, There are maybe transitive dependencies!

Usage

The plugins are configured in the «plugins» section of the pom.

<plugins>
  <plugin>
    <groupId>org.wildfly.build</groupId>
    <artifactId>wildfly-feature-pack-build-maven-plugin</artifactId>
    <executions>
      <execution>
        <id>feature-pack-build</id>
        <goals>
          <goal>build</goal>
        </goals>
        <phase>compile</phase>
        <configuration>
          <config-file>feature-pack-build.xml</config-file>
        </configuration>
      </execution>
    </executions>
  </plugin>
</plugins>
<plugins>
  <plugin>
    <groupId>org.wildfly.build</groupId>
    <artifactId>wildfly-server-provisioning-maven-plugin</artifactId>
    <executions>
      <execution>
        <id>server-provisioning</id>
        <goals>
          <goal>build</goal>
        </goals>
        <phase>compile</phase>
        <configuration>
          <config-file>server-provisioning.xml</config-file>
        </configuration>
      </execution>
    </executions>
  </plugin>
</plugins>

Config Parameters

Most of the configuration for each plugin is contained in a separate configuration
file defined by the parameter config-file.

The schema for the config file for the wildfly-feature-pack-build-maven-plugin can be found in the sources here:
https://github.com/wildfly/wildfly-build-tools/blob/master/feature-pack-build-maven-plugin/src/main/resources/

The schema for the config file for the wildfly-server-provisioning-maven-plugin can
be found in the sources here:
https://github.com/wildfly/wildfly-build-tools/tree/master/provisioning/src/main/resources

Example Config Files

Some example configurations can be found in the wildfly-core and wildfly sources:

  • https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/feature-pack-build.xml
  • https://github.com/wildfly/wildfly-core/blob/master/dist-legacy/server-provisioning.xml
  • https://github.com/wildfly/wildfly/blob/master/feature-pack/feature-pack-build.xml
  • https://github.com/wildfly/wildfly/blob/master/dist-legacy/server-provisioning.xml

Provisioning configuration attributes

  • copy-module-artifacts — whether should be WildFly modules resources (JARs) copied from artifacts into , next to their .
  • extract-schemas — whether should be XSD files extracted from WildFly modules artifacts into
  • extract-schemas-groups — groupId of artifacts, from which should be XSD files extracted (delimited by space)

Example Server Provisioning Filter

When provisioning a server from a feature pack, it’s can be useful to exclude certain
files from the resulting distribution. This can be done using the config.
The following example will exclude the files «copyright.txt» and «README.txt» and
also the directory «docs/contrib».

<server-provisioning xmlns="urn:wildfly:server-provisioning:1.1" extract-schemas="true" copy-module-artifacts="true"
                     extract-schemas-groups="org.jboss.as org.wildfly org.wildfly.core org.jboss.metadata">
  <feature-packs>
    <feature-pack groupId="org.wildfly" artifactId="wildfly-feature-pack" version="${project.version}">
      <contents>
        <filter pattern="copyright.txt" include="false"/>
        <filter pattern="README.txt" include="false"/>
        <filter pattern="docs/contrib/*" include="false"/>
      </contents>
    </feature-pack>
  </feature-packs>
</server-provisioning>

Capability Requirements

A capability may rely on other capabilities in order to provide its functionality at runtime. The management operation handlers that register capabilities are also required to register their requirements.

There are three basic types of requirements a capability may have:

  • Hard requirements. The required capability must always be present for the dependent capability to function.
  • Optional requirements. Some aspect of the configuration of the dependent capability controls whether the depended on capability is actually necessary. So the requirement cannot be known until the running configuration is analyzed.
  • Runtime-only requirements. The dependent capability will check for the presence of the depended upon capability at runtime, and if present it will utilize it, but if it is not present it will function properly without the capability. There is nothing in the dependent capability’s configuration that controls whether the depended on capability must be present. Only capabilities that declare themselves as being suitable for use as a runtime-only requirement should be depended upon in this manner.

Hard and optional requirements may be for either statically named or dynamically named capabilities. Runtime-only requirements can only be for statically named capabilities, as such a requirement cannot be specified via configuration, and without configuration the dynamic part of the required capability name is unknown.

The capability.adoc entry for a capability should provide information about capability requirements, if there are any.

Description

The task will download and install a WildFly server to the target directory, while
upgrading the two Hibernate ORM libraries and replacing the JPA 2.1 API with the standard JPA 2.2 API.

N.B. this example is not replacing all Hibernate ORM libraries so it wouldn’t provide a reliable server!
Doing such an upgrade properly shouldn’t be done via version overrides but using an appropriate
feature pack — using the more powerful ‘configuration’ property.
The overrides capability is meant for developers experimenting with changes to the WildFly server.

Thin server

The created server will be of the «thin» kind: almost no jars and will take minimal space,
but the necessary jars will be stored in your local maven repository.

Custom server

You can use a to pick and choose only the feature packs you need;
this way you can materialize a slim server which only has the features you need.

Currently there isn’t a large collection of feature packs but this will improve soon.

An example could be:

The above will materialize a «full» WildFly 11.0.0.Final in the target directory.

A more complex example:

The above example will materialize a smaller WildFly server (the «servlet» edition), but then
include as well the Apache Lucene libraries appropriately packaged as modules.

Thin vs Full servers

By default the element produces a thin server:
that’s a very small server as it doesn’t include a copy of all jar files,
rather referencing them from your local Maven repository.

(Yes it will use the Maven repository even during a Gradle build)

This is ideal for integration tests which need to produce and delete servers regularly,
and will transparently benefit from the Maven cache.

If you don’t want to rely on the Maven cache you can produce a full copy
of the WildFly server by setting the attribute
in the top element.

For example:

For a full list of the options supported by , see also the
Maven version of this plugin.

Output directory

The default is to unpack a copy of the server in the «provisioned-wildfly» subdirectory of your build
directory.

Set the property to any other directory to change this.

If you choose a which is not in your build directory you might want to explicitly add a clean task:

Transaction Support

Request Messages

Transaction Begin

Method

POST

URI

/txn/v1/ut/begin

Additional Required Headers

Accept: application/x-wf-jbmar-exception;version=1,application/x-wf-jbmar-new-txn;version=1
x-wf-txn-timeout: {timeout}

Additional Optional Headers

Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

The request body is empty.

User Transaction Commit

Method

POST

Message Type

application/x-wf-jbmar-xid;version=1

URI

/txn/v1/ut/commit

Additional Required Headers

Accept: application/x-wf-jbmar-exception;version=1
Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

JBoss marshalling representation of formatId, global ID and branch ID (the components of an XID).

Transaction Rollback

Method

POST

Message Type

application/x-wf-jbmar-xid;version=1

URI

/txn/v1/\{type}/rollback

Additional Required Headers

Accept: application/x-wf-jbmar-exception;version=1
Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

JBoss marshalling representation of formatId, global ID and branch ID (the components of an XID).

Transaction before completion

Method

POST

Message Type

application/x-wf-jbmar-xid;version=1

URI

/txn/v1/xa/bc

Additional Required Headers

Accept: application/x-wf-jbmar-exception;version=1
Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

JBoss marshalling representation of formatId, global ID and branch ID (the components of an XID).

Distributed Transaction Prepare

Method

POST

Message Type

application/x-wf-jbmar-xid;version=1

URI

/txn/v1/xa/prep

Additional Required Headers

Accept: application/x-wf-jbmar-exception;version=1
Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

JBoss marshalling representation of formatId, global ID and branch ID (the components of an XID).

The response to this message can contain the x-wf-txn-read-only header, which is used to indicate the
read only status of the result. If it is missing it is assumed to not be read only.

Distributed Transaction Commit

Method

POST

Message Type

application/x-wf-jbmar-xid;version=1

URI

/txn/v1/xa/commit(?opc=true)?

Additional Required Headers

Accept: application/x-wf-jbmar-exception;version=1
Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

The request body is empty.

Notes

JBoss marshalling representation of formatId, global ID and branch ID (the components of an XID).
If the opc request parameter is present then a one phase commit is done.

Distributed Transaction Forget

Method

POST

Message Type

application/x-wf-jbmar-xid;version=1

URI

/txn/v1/xa/forget

Additional Required Headers

Accept: application/x-wf-jbmar-exception;version=1

Additional Optional Headers

Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

JBoss marshalling representation of formatId, global ID and branch ID (the components of an XID).

Distributed Transaction Recovery

Method

GET

URI

/txn/v1/xa/recover

Additional Required Headers

Accept: text/x-wf-txn-jbmar-xid-list;version=1,application/x-wf-jbmar-exception;version=1
x-wf-txn-parent-name: The parent node name
x-wf-txn-recovery-flags: The recovery flags as a base 10 integer

Additional Optional Headers

Cookie: JSESSIONID=\{sessionAffinityKey}

Request Body

The request body is empty.

Transaction Responses

Begin Transaction

Message Type

application/x-wf-jbmar-new-txn;version=1

Required Headers

x-wf-txn-jbmar-id: \{transactionId}

Optional Headers

Set-Cookie: JSESSIONID=\{sessionAffinityKey}

Response Body

Jboss marshalling representation of formatId, global ID and branch ID (the components of an XID).

Response Codes

New Transaction

Required Headers

x-wf-txn-jbmar-id: \{transactionId}

Optional Headers

Set-Cookie: JSESSIONID=\{sessionAffinityKey}

Response Body

None

Response Codes

Transaction Result

Response Body

Empty

Response Codes
x-wf-txn-jbmar-xa-read-only:true

If this is present then the XA result was read only (only relevant for the prepare operation)

Notes

This response is used to indicate operation success

Transaction XIDS

Message Type

text/x-wf-txn-jbmar-xid-list

Optional Headers

Set-Cookie: JSESSIONID=\{sessionAffinityKey}

Response Body

Newline separated list of prepared but not submitted transactions

Response Codes

Blazix

Blazix — это полнофункциональный сервер приложений Java и веб-сервер (обслуживающий HTML-файлы и изображения в дополнение к стандартной рабочей нагрузке сервера приложений). В настоящее время Blazix предоставляет Servlet 2.3, JSP 1.2, EJB 1.1 и JMS 1.0.2. Он также реализует HTTP / 1.1 и полностью написан на Java, и может использоваться кроссплатформенно. Он может использоваться в качестве полноценного веб-сервера сам по себе, особенно при большом объеме трафика.

Некоторые из включенных функций имеют поддержку кластеризации без единой точки отказа для балансировки нагрузки и восстановления после сбоя, развертывания и обновления EJB и веб-архива, веб-сервисы Secure Socket Layer, управление транзакциями, безопасность.

Оцени статью

Оценить

Средняя оценка / 5. Количество голосов:

Видим, что вы не нашли ответ на свой вопрос.

Помогите улучшить статью.

Спасибо за ваши отзыв!

Environment variables to be used when running application

Java env variables

  • The Java env variables you can set are documented in this document
  • , set to true to enable debug on port 8787, disabled by default.
  • , to append to options to

WildFly server env variables

  • Access Log env vars

  • Admin user env vars

  • Deployment scanner env var

  • set to true to disable shutdown.

  • defaut to or or or

  • Elytron security env vars

  • default to

  • Filters (Undertow) env vars

  • HTTPS config env vars

  • JSON logging env vars

  • Keycloak env var

  • Logger categories env vars

  • Microprofiles config env vars

  • If set, WildFly will attempt to define a MySQL datasource based on the assumption you have an OpenShift service named «mysql» defined.
    It will attempt to reference the following environment variables which are automatically defined if the «mysql» service exists:

    • , default to MySQLDS, is used as the JNDI name of the datasource
  • default to

  • If set, WildFly will attempt to define a PostgreSQL datasource based on the assumption you have an OpenShift service named «postgresql» defined.
    It will attempt to reference the following environment variables which are automatically defined if the «postgresql» service exists:

    • , default to PostgreSQLDS, is used as the JNDI name of the datasource
  • Port offset env vars

  • Resource adapters env vars

  • set to true to enable launch script debug.

  • name of standalone XML configuration file. Default to

  • default to

  • default to

  • default to the value returned by

  • in default server configuration microprofile opentracing is not enabled. Set this env variable to to enable it. In case your configuration contains
    opentracing (eg: cloud-profile), you can disable it by setting this env variable to .

  • Adding new datasources can be done by using env variables defined in this document

Jolokia env variables

The Jolokia env variables you can set are documented in this document

Capabilities

A capability is a piece of functionality used in a WildFly Core based process that is exposed via the WildFly Core management layer. Capabilities may depend on other capabilities, and this interaction between capabilities is mediated by the WildFly Core management layer.

Some capabilities are automatically part of a WildFly Core based process, but in most cases the configuration provided by the end user (i.e. in standalone.xml, domain.xml and host.xml) determines what capabilities are present at runtime. It is the responsibility of the handlers for management operations to register capabilities and to register any requirements those capabilities may have for the presence of other capabilities.

  • Capabilities vs modules: A JBoss Modules module is the means of making resources available to the classloading system of a WildFly Core based process. To make a capability available, you must package its resources in one or more modules and make them available to the classloading system. But a module is not a capability in and of itself, and simply copying a module to a WildFly installation does not mean a capability is available. Modules can include resources completely unrelated to management capabilities.
  • Capabilities vs Extensions: An extension is the means by which the WildFly Core management layer is made aware of manageable functionality that is not part of the WildFly Core kernel. The extension registers with the kernel new management resource types and handlers for operations on those resources. One of the things a handler can do is register or unregister a capability and its requirements. An extension may register a single capability, multiple capabilities, or possibly none at all. Further, not all capabilities are registered by extensions; the WildFly Core kernel itself may register a number of different capabilities.

Repository organization

  • doc/ some documentation content referenced from this README file.

  • imagestreams/ contains image streams registered in openshift library

  • make/ contains make scripts

  • templates templates you can add to a local openshift cluster (eg: )

    • builder image stream
    • runtime image stream
    • template that build an application using s2i and copy the WildFly server and deployed app inside the WildFly runtime image.
  • test/ contains test applications and make test script

  • wildfly-builder-image/ contains builder image yaml file

  • wildfly-modules/ contains cekit modules specific to wildfly. NB: These modules are progressively removed and added to the wildfly-cekit-modules repository.

  • wildfly-runtime-image contains runtime image yaml file

Оцените статью
Рейтинг автора
5
Материал подготовил
Андрей Измаилов
Наш эксперт
Написано статей
116
Добавить комментарий