]
Brian Stansberry commented on WFLY-13771:
-----------------------------------------
[~fwelland] WFLY-13354 is to add layers for EJB3. As Emmanuel noted the ones that include
MDB would bring in what's needed without adding an embedded broker.
Create a Galleon layers for the messaging subsystem
---------------------------------------------------
Key: WFLY-13771
URL:
https://issues.redhat.com/browse/WFLY-13771
Project: WildFly
Issue Type: Feature Request
Components: Build System, JMS
Reporter: Yeray Borges Santana
Assignee: Emmanuel Hugonnet
Priority: Major
We have three possible messaging-activemq configuration options that should be supplied
via Galleon layers:
# messaging-activemq subsystem configuration ready to be used as an Embedded broker. This
configuration is useful to run quick demos only, it should not be used in production
environments or cloud environments.
# messaging-activemq subsystem configuration ready to be used with an external broker.
# An empty messaging-activemq subsystem configuration and capabilities to deploy a
Resource Adapter file to connect to an external broker. This .rar file has to be deployed
by the user.
The existing jms-activemq layer was meant to allow client-side JMS, it is almost covering
the third option, however, the user should be able to deploy .rar files. The analysis
document should clarify whether these capabilities should be included in a Galleon layer
itself or by contrast, users should add the resource-adapters Galleon layer to provide
it.
Another point to clear up is if the Galleon layers will supply capabilities to invoke
remote objects configured in the WildFly JNDI tree, hence the need for remoting naming.