[JBoss JIRA] (AS7-5922) Grouping-handler's type attribute does not support expressions
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-5922?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil updated AS7-5922:
-----------------------------
Fix Version/s: 7.1.4.Final (EAP)
> Grouping-handler's type attribute does not support expressions
> --------------------------------------------------------------
>
> Key: AS7-5922
> URL: https://issues.jboss.org/browse/AS7-5922
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.1.3.Final (EAP)
> Environment: JBoss EAP 6.x
> Reporter: Tom Ross
> Assignee: Jeff Mesnil
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> When creating messaging grouping in cluster mode it is necessary to provide <type> for <group-id> for each node. In a cluster there could only one node with group-id <type>LOCAL</type> and remaining nodes have to be of type REMOTE. In JBoss EAP 6 in domain cluster there is only one profile for each node so it is necessary to be able to specify type as an expression i.e <type>${type.name}</type>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5927) Minimal AS7 build pulls in many non-optional dependencies
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5927:
-----------------------------------
Summary: Minimal AS7 build pulls in many non-optional dependencies
Key: AS7-5927
URL: https://issues.jboss.org/browse/AS7-5927
Project: Application Server 7
Issue Type: Bug
Components: Build System, OSGi
Reporter: Thomas Diesler
Assignee: Paul Gier
Fix For: 7.2.0.Alpha1
A minimal AS7 modular build pulls in almost every module making it a monolithic beast.
{code}
build-standalone-server:
[mkdir] Created dir: /home/tdiesler/git/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT
[copy] Copying 231 files to /home/tdiesler/git/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT
[copy] Copied 40 empty directories to 2 empty directories under /home/tdiesler/git/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT
[copy] Copying 1 file to /home/tdiesler/git/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/configuration
[copy] Copying 739 files to /home/tdiesler/git/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/modules
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBRULES-3677) Buplicated main agenda group on session reset
by Maciej Swiderski (JIRA)
Maciej Swiderski created JBRULES-3677:
-----------------------------------------
Summary: Buplicated main agenda group on session reset
Key: JBRULES-3677
URL: https://issues.jboss.org/browse/JBRULES-3677
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.3.0.Final
Reporter: Maciej Swiderski
Assignee: Mark Proctor
In case knowledge session is reset (for instance due to transaction rollback) main agenda group is duplicated. First time is added by clear method in DefaultAgenda and then right after by the marshaller
Consequence of it is that rules are not fired after session reset.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month