[JBoss JIRA] Resolved: (JBCLUSTER-26) Clustered deployments should be atomic
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBCLUSTER-26?page=com.atlassian.jira.plug... ]
Brian Stansberry resolved JBCLUSTER-26.
---------------------------------------
Resolution: Out of Date
> Clustered deployments should be atomic
> --------------------------------------
>
> Key: JBCLUSTER-26
> URL: https://issues.jboss.org/browse/JBCLUSTER-26
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: Legacy
>
> Original Estimate: 8 weeks
> Remaining Estimate: 8 weeks
>
> Our current farm deployment is not automic, meaning that one cluster node failed, it won't rollback the rest within the cluster.
> One soultion is make the deployer XA resource so they can participate in sort of 2 phase commit.
> This can potentially be applied to MBean clustering as well.
> In addition, farming service has couple bugs outstanding. It needs an overhaul as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Resolved: (JBCLUSTER-23) Consolidate clustering configuration frontend for state replication
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBCLUSTER-23?page=com.atlassian.jira.plug... ]
Brian Stansberry resolved JBCLUSTER-23.
---------------------------------------
Resolution: Out of Date
> Consolidate clustering configuration frontend for state replication
> -------------------------------------------------------------------
>
> Key: JBCLUSTER-23
> URL: https://issues.jboss.org/browse/JBCLUSTER-23
> Project: JBoss Clustering
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: Legacy
>
> Original Estimate: 8 weeks
> Remaining Estimate: 8 weeks
>
> Currently we have cluster-service.xml, tc5-cluster-serviec.xml, and other tree-cache.xml to run on tops of JGroups for various replication and clustering purpose. In ejb3, we will run into this problem of SFSB and entity bean using JBossCache.
> There comes a need to consolidate all these configuration so to a end user it is consistent.
> Solution may be to put in another integration layer to hide JBossCache configuration somewhat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBRULES-3127) PackageBuilder should support an ordered iteration of added/merged packages
by Davide Sottara (JIRA)
PackageBuilder should support an ordered iteration of added/merged packages
----------------------------------------------------------------------------
Key: JBRULES-3127
URL: https://issues.jboss.org/browse/JBRULES-3127
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-compiler
Reporter: Davide Sottara
Assignee: Mark Proctor
Priority: Minor
The getPackages() method returns an array of packages which is based on the internal map's iteration order.
Instead, the order should depend on the package addition/merge sequence.
E.g. if a KnowledgeBuilder adds the following resources:
r1 -> package p1
r2 -> package p2
r3 -> package p2
r4 -> package p3
r5 -> package p1
the sequence in the array should be p1, p3, p2
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1185) Classpath issue break localization in Hibernate Validator
by Juergen Zimmermann (JIRA)
Classpath issue break localization in Hibernate Validator
---------------------------------------------------------
Key: AS7-1185
URL: https://issues.jboss.org/browse/AS7-1185
Project: Application Server 7
Issue Type: Bug
Components: Modules
Affects Versions: 7.0.0.CR1
Reporter: Juergen Zimmermann
If you want Hibernate Validator to produce internationalized / localized messages you need properties files like e.g. ValidatorMessages_en.properties or ValidatorMessages_de.properties. These properties files must be in the Classpath. Thus if you need them in an EJB module, they are placed in the root directory of the EAR.
According to the language the right file is picked up, and the right hand side has the localized message belonging to the key on the left hand side. However, if no key is found or if the properties file isn't found, then the localized message is just "{key}" aka the template message.
I'll attach a testcase to reproduce this issue that ValidatorMessage_xx.properties isn't found in the Classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months