EuroAP is a middleware platform based on open standards. Our solutions include two leading versions: EuroAP 6.x compliant with the Java™ EE 6 specification and EuroAP 7.x compliant with the Java™ EE 7 specification.

EuroAP has a modular design, making it extremely flexible. You can choose a predefined set of components (profiles) or create your own – unique set, tailored for your applications. Below is a list of components available in EuroAP.  Additionally you can add your own modules if required.

EuroAP components and their application:

  • Wildfly Core – creates the core of EuroAP operation. It provides CLI (Command Line Interface, which enables automatic collaboration with EuroAP), modular class loading, and unified EuroAP management even in the Domain mode.
  • JBoss® Management Console (HAL) – a graphical console to manage EuroAP in both Standalone and Domain modes. From this level, we can intuitively and conveniently apply a server patch, manage deployments or access control, and also see how the server works when it is running (in "runtime").
  • ActiveMQ Artemis – the implementation of Java™ Message Service 2.0 standard. It is the HornetQ code handed over to the Apache ActiveMQ team. It features an increased performance in comparison to similar products. It is present in EuroAP/JBoss® EAP from version 7 onwards.
  • WELD – reference implementation of CDI (Contex and Dependency Injection) for Java™ EE. Provides injection of dependencies and lifecycle management.
  • Undertow – a web site server, which replaced JBoss® Web Server in EuroAP 7. Undertow supports Java™ EE 7 requirements, such as web sockets, HTTP/2 or json-p. In addition, it includes many improvements, such as: NIO network container, load balancing, HTTP port reduction (EuroAP 7 uses only two - 9990 and 8080) or session management.
  • WildFly Elytron – a project that will eventually replace PicketBox and JAAS, present in EuroAP since version 7.1. Its main advantage is that it is a single framework that ensures security for both the application server and the applications installed on it. Thanks to its modular architecture – it consists of many small components – you can easily adapt it to your needs. You can exchange default components for other implementations, even your own ones. Additionally, various components are treated as capabilities within the server, so that they can be mixed and merged with each other.
  • PicketBox – a set of components (PicketBox, PicketBox Commons, Picketlink Federation) providing security in EuroAP 6x. It is present in version 7 to maintain compatibility, it is recommended to use Elytron.
  • mod_cluster – load-balancer based on httpd. It has the ability to dynamically change its configuration. In addition to the standard communication channels used to forward requests from httpd to the appropriate application server nodes, it uses an additional channel for feedback, which enables to balance load and react to changes in the application lifespan with certain intelligence.
  • JBoss® XNIO – an alternative to NIO, providing, among other things, APIs for combining blocking and non-blocking operations, even within a single channel.
  • Hibernate – a framework for Java™ environment used to map Java™ objects to the relational database and vice versa (ORM – Object-relational mapping). There are the following components as standard in EuroAP: Hibernate Core, Hibernate Infinispan (2LC), Hibernate Envers, Hibernate Validator, Hibernate JPA 2.0 API.
  • Infinispan – a distributed warehouse storing data in the form of a key-value pair in the main memory.
  • IronJacamar (JCA 1.7) – implements Java EE Connector Architecture 1.7, which defines how the Enterprise Information System is to integrate with Java™ EE. In other words, for example, how databases or messaging systems are able to communicate with the application server.
  • JGroups – a set of tools enabling reliable messaging. First of all, it enables cluster management (creating, destroying, joining and leaving clusters, detecting and reporting that a node has broken down/joined/left the cluster), as well as sending and receiving point-to-point and point-to-multipoint messages, i.e. it enables sending a message between nodes and also between a node and a cluster.
  • JBoss® Transactions (Narayana) – transaction manager, provides support for application using transactional protocols, e.g. JTA, JTS, Web-Service Transactions or Rest Transactions.
  • JBoss® EJB – support for Enterprise Java™ Beans (EJB) 3.0, implemented in EuroAP via components: JBoss® EJB Client and JBoss® EJB3 EXT API.
  • JBoss® WS – a web services framework that provides all services necessary to ensure compliance with Java™ EE 7. The components present in EuroAP right out of the box are: JBoss® WS API, JBoss® WS SPI, JBoss® WS Common, JBoss® WS Common Tools, JBoss® WS-CXF. The last of the listed components provides excellent integration with Apache® CXF.
  • JBoss® VFS – a component responsible for the Virtual File System used by the deployment framework. Thanks to it, every implemented application is visible as a hierarchical file system, which is read-only, regardless of whether the application is actually packed or not.
  • JBoss® Marshalling – provides the API for serialization, includes improvements to the standard API, while remaining fully compatible with
  • JBoss® Logging – a component responsible for logging.
  • Apache® CXF – the framework supporting developers in building network services. It provides, among others clear separation of the frontend part of the code, e.g. JAX-RS or JAX-WS from business logic, as well as the ease and simplicity of creating new clients and endpoints.
  • JBeret – provides support for batch processing in the Java™ EE environment.

EuroAP also includes many libraries directly supporting the creation of WebServices, such as: RestEasy, JAXB, Xalan, and Xerces