manualmode-build.xml

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFLY-9778] generate necessary test module in test suite server image

  1. … 2 more files in changeset.
[WFLY-9122] Fixed Dwm servers not in manual mode

  1. … 5 more files in changeset.
WFLY-9598 Final cleanup: make arquillian.xml valid, drop unused XSLT transformations

  1. … 15 more files in changeset.
WFLY-7298 use slim build in testsuite

  1. … 64 more files in changeset.
[WFLY-9336] Extend Elytron security context propagation test coverage

  1. … 44 more files in changeset.
[WFLY-9172] Add Elytron security context propagation tests

  1. … 17 more files in changeset.
Merge pull request #10066 from LittleJohnII/eap7-495

[WFLY-8559] Implement test coverage for DWM

  1. … 1 more file in changeset.
[WFCORE-2095] Add AuthenticationContext references to RemoteOutboundConnectionResourceDefinition

* Adding test case pertaining to remote outbound connection authentication between two server instances using remote-outbound-connection management resource with Elytron authentication context.

  1. … 8 more files in changeset.
[WFLY-8559] Implement test coverage for DWM

  1. … 23 more files in changeset.
WFLY-8415 WFLY-8134 - rework testsuite to use CLI scripts for configuration

  1. … 130 more files in changeset.
[WFLY-6409]: Update default domain configuration to use remote+http

Updating default domain configurations.

Removing usage of deprecated http-remotting

  1. … 46 more files in changeset.
[WFLY-5138] Don't use ARQ for ParseAndMarshalModelsTestCase, plus ModelParserUtils now wants 'target' param to mean location

  1. … 1 more file in changeset.
[WFLY-4593] Model-only representation for messaging subsystem

* removed tests (and their configuration) that were using the messaging

subsystem runtime

JIRA: https://issues.jboss.org/browse/WFLY-4593

  1. … 7 more files in changeset.
[WFLY-4585] Provide JMS forward compatibility

* add support for JMS forward compatibility so that legacy JMS clients

(with HornetQ client libraries) can lookup HornetQ-based JMS resources

from JNDI and connect to the Artemis server using its HORNETQ

protocol.

* for JMS destinations (jms-queue and jms-topic), a new attribute

legacy-entries can be used to bind the HornetQ-based destinations to

JNDI.

* for connection factories, a new resource (legacy-connection-factory)

has been added. It is different from the connection-factory resource

used by Artemis client.

* add org.hornetq.client module. The messaging-activemq subsystem depends

on it to create HornetQ managed resources for forward interoperability.

* add test for legacy (HornetQ) clients connecting to resources managed

by the messaging-activemq subystem

JIRA: https://issues.jboss.org/browse/WFLY-4585

  1. … 36 more files in changeset.
[WFLY-4587] Messaging migrate management operation

add :migrate operation to legacy messaging subsystem

JIRA: https://issues.jboss.org/browse/WFLY-4587

  1. … 11 more files in changeset.
[WFLY-4584] new messaging-activemq subsystem

* add Maven GAVs for ActiveMQ Artemis artifacts

* add new messaging-activemq subsystem based on the legacy messaging

subsystem and using Artemis code instead of HornetQ

* update test to use urn:jboss:domain:messaging-activemq:1.0 namespace

* add ActiveMQ Artemis client artifacts to jms client

* add org.jboss.activemq.artemis.integration:activemq-wildfly-integration artifact

* use service extension to bind with Artemis's transaction manager locator and recovery manager

* add (core) queues addition/removal to JMSOperations

JIRA: https://issues.jboss.org/browse/WFLY-4584

  1. … 280 more files in changeset.
WFLY-4110 - EJBClientClusterConfigurationTestCase fails on JDK1.8 once -Dnode0 and -Dnode1 are used

WFLY-3720 Run manual mode integration tests with ip_ttl=0

  1. … 1 more file in changeset.
WFLY-2206 Don't copy the modules directory in the manualmode test suite

  1. … 1 more file in changeset.
[WFLY-456] Audit Logging - squashed the below commits since master has changed so much

[WFLY-456] Minor OperationContext impl cleanups

[WFLY-456] Bring in John Bailey's audit log classes

[WFLY-456] Add real audit loggers into the model controllers; integrate management handlers

[WFLY-456] Log the full set of information

[WFLY-456] Fix problems from rebase

[WFLY-456] Use SecurityContext when invoking JMX methods via remoting

[WFLY-456] Move core security classes into own module

[WFLY-456] Rework things and make the controller logger work

[WFLY-456] Include the access mechanism in the log, move some more classes to core-security

[WFLY-456] Make audit logger available to JMX

[WFLY-456] Pluggable MBeanServer delegate to audit logger, and loads of exception handling

[WFLY-456] Jmx audit log proxy

[WFLY-456] Separate the configuration for the core controller and jmx audit logs

[WFLY-456] Set the booting flag in the jmx layer

[WFLY-456] Integrate audit logging resource and ops into JMX extension so it can be configured there

[WFLY-456] Correct copyright notices in my new files

[WFLY-456] fix problems from rebase

[WFLY-456] Get rid of the original hashing implementation

[WFLY-456] Add missing originalResultTxControl from rebase

[WFLY-456] Add config for appenders

[WFLY-456] Basic file appender and json formatter. The output needs cleaning up and everything is currently hardcoded

[WFLY-456] Back up the previous log file. Basic syslog appender (awaiting the improved logmanager SyslogHandler)

[WFLY-456] Use the org.wildfly:wildfly-xxx names. Start configuring file appenders

[WFLY-456] Configure model for syslog appender

[WFLY-456] Log audit log records for ParallelBootOperationContext and ReadOnlyContext

[WFLY-456] Make whether to log on boot configurable

[WFLY-456] Be able to add/remove appender references at runtime and update the appenders at runtime

[WFLY-456] Add boot-log to jmx audit-log as well and update xsd's for both core and jmx

[WFLY-456] Make additive changes to appenders take effect right away, and delay changes/removals until the current audit record has been written

[WFLY-456] Add schema support and parsing for managed server path overrides, and clean up the handlers

[WFLY-456] Use 'handler' rather than 'appender'

[WFLY-456] Pass in audit log operations to managed servers on boot

[WFLY-456] Separate handler chains for host and managed server audit logs

[WFLY-456] i18n and get rid of code no longer needed

[WFLY-456] Fix problems from rebase, revisit security after moved WildFlySecurityManager

[WFLY-456] Flesh out the syslog handler, tried with UDP

[WFLY-456] Start testing the handlers and ops

[WFLY-456] Set up proper syslog host and app names

[WFLY-456] More tests

[WFLY-456] Complete renaming appender->handler. Really

[WFLY-456] Nicer separate configuration for JMX

[WFLY-456] Better testing for enabled and log-read-only audit log write attribute handlers

[WFLY-456] Separate handlers for JMX subsystem audit logging, and tests

[WFLY-456] Maintan a failure count per appender

[WFLY-456] Configure the json formatter and reference from the audit log handlers

Expose 'max-length' and 'truncate' for the syslog handler

[WFLY-456] Make audit logging work in admin-only mode

Fix bug not enabling the appender in domain mode

[WFLY-456] Fixes to tls syslog handler having tried it out against rsyslog

[WFLY-456] don't enable log by default

[WFLY-456] Test jmx audit log transformation

[WFLY-456] Test audit logging in testsuite

[WFLY-456] Move new i18n bits into domain-management, rather than using the ones from controller

[WFLY-456] Recycle handler operation, make max-failure-count configurable per handler, expose runtime attributes for handler failure counts

[WFLY-456] Use strings instead of byte[] for the formatters for now. We can revisit the byte[] part if more tamper detecting formatters are used in the future

[WFLY-456] Use platform independent line terminator

[WFLY-456] Changes to work with latest logmanager following a squash

  1. … 208 more files in changeset.
Revert "Revert "Initial HTTP Upgrade support for remoting naming and EJB invocations""

This reverts commit 8fedd0f07ee2bfe8fd526e09daa84e62e0b036ce.

  1. … 107 more files in changeset.
Revert "Initial HTTP Upgrade support for remoting naming and EJB invocations"

This reverts commit e44b2ae0f1354eb82766f15b0ae06906b00ae0b4.

  1. … 106 more files in changeset.
Initial HTTP Upgrade support for remoting naming and EJB invocations

  1. … 106 more files in changeset.
delete manualmode's jbossas-messaging-failover before copy

HornetQ failover is depending on the file system to lock a file.

I have seen PRs be aborted because HornetQ live server can not lock this

file to start (there is no timeout on this lock operation).

Deleting the directory ensures that the file system's lock (from previous

runs) is removed.

[AS7-6699] HornetQ backup mode

When HornetQ is configured to be a backup, it will start and remain

passive (its resources are not deployed, it does not accept any

connections, etc.)

For AS7 hornetq-server's children resources, that means that:

* read-attribute on runtime attributes is a no-op (returns undefined)

* execute an operation on a queue will throw an exception warning the

user that HornetQ is in backup mode

* add active runtime r/o attribute to hornetq-server

For AS7 services, there are some substantial changes too.

HornetQService default does *not* start the HornetQ server. This is done

by JMSService. This means that any service must not depend on

HornetQService but JMSService to make sure that the server is

effectively started.

JMSService is started asynchronously and the server start is completed

when:

* the HornetQ server has been activated (immediately when it is a live

node, or after failover if it is a backup)

* and the JMSServerManager is started (and can deploy JMS resources)

It is important for other services depending on messaging services

(queue, jms-queue, topic, connection-factory &

pooled-connection-factory) that these services must NOT be started

until a backup hornetq-server fails over.

* refactor messaging's SecurityActions (based on ExtensionAddHandler

snippet)

  1. … 35 more files in changeset.
Added LayeredDistributionTestCase.

Updated.

  1. … 6 more files in changeset.
AS7-4140 Unify mcast params to just one -Dmcast

  1. … 5 more files in changeset.
AS7-4140 Unify mcast params to just one -Dmcast

  1. … 5 more files in changeset.
Fix manualmode. I really hope this is the last one

AS7-3820 Add a testcase to ensure that deployment succeeds for a EJB client context whose remoting receiver's server isn't up and reconnects when the server is up

  1. … 17 more files in changeset.