Bug 1302874 - [GSS](6.4.z) HornetQ module should depend on optional module for user interceptors
Summary: [GSS](6.4.z) HornetQ module should depend on optional module for user interce...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Patching
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.11
Assignee: Ivo Studensky
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap6411-payload
TreeView+ depends on / blocked
 
Reported: 2016-01-28 20:46 UTC by Brad Maxwell
Modified: 2019-09-12 09:51 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 13:09:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brad Maxwell 2016-01-28 20:46:46 UTC
To configure a custom hornetq interceptor, it requires the interceptors be a dependency of the org.jboss.as.messaging module.  When a cumulative patch or one off patch is applied updating the module, it will revert the changes and require modification of the .overlays ... module.xml.

We should add a dependency in org.jboss.as.messaging module to depend on an optional dependency such as org.hornetq.interceptors.  The user could then create $JBOSS_HOME/modules/org/hornetq/interceptors/module.xml


<module xmlns="urn:jboss:module:1.1" name="org.jboss.as.messaging">
...
    <dependencies>
...
        <module name="org.hornetq.interceptors" optional="true"/>
...

The $JBOSS_HOME/modules/org/hornetq/interceptors/module.xml would look something like this: 

<module xmlns="urn:jboss:module:1.1" name="org.hornetq.interceptors">

    <resources>
        <resource-root path="custom-hornetq-interceptor.jar"/>
    </resources>

    <dependencies>
        <module name="javax.api"/>
        <module name="javax.jms.api"/>
        <module name="javax.transaction.api"/>
        <module name="org.hornetq"/>
    </dependencies>
</module>

Comment 4 Mike McCune 2016-03-28 22:44:25 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Peter Mackay 2016-10-03 15:23:52 UTC
Verified with EAP 6.4.11.CP.CR1

Comment 6 Petr Penicka 2017-01-17 13:09:14 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.


Note You need to log in before you can comment on or make changes to this bug.