Clarify transactional behavior of clustered SFSB cache
------------------------------------------------------
Key: EJBTHREE-845
URL: http://jira.jboss.com/jira/browse/EJBTHREE-845
Project: EJB 3.0
Issue Type: Task
Components: Clustering
Affects Versions: EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: EJB 3.0 RC10 - FD
The ejb3-clustered-sfsb-service.xml is not declaring a TransactionManagerLookupClass, so the cache is not transactional. Need to clarify why this is and correct if there is no good reason. If it is valid, work with JBC team to eliminate the WARN JBC logs when no lookup is specified.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
State changes in @PrePassivate don't get replicated if passivate before replication is disabled
-----------------------------------------------------------------------------------------------
Key: EJBTHREE-1053
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1053
Project: EJB 3.0
Issue Type: Bug
Components: Clustering
Affects Versions: AS 4.2.2.GA
Reporter: Carlo de Wolf
Passivation doesn't trigger replication, so a bean might get passivated on 1 node and not on another. If the bean provider does state changes in pre-passivate these will not be visible on the other node.
By default replication does trigger passivation, so a bean first gets passivated and then replicated. Thus the problem only occurs if passivate before replication is explicitly disabled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Buddy replication can lead to a memory leak
-------------------------------------------
Key: EJBTHREE-1054
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1054
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.2.GA
Reporter: Carlo de Wolf
JBC passivation code is broken with buddy replication enabled.
Whenever a bean is replicated it's copied to a backup region. This backup region is never evicted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
dependency on JMSProviderAdapter
--------------------------------
Key: JBMESSAGING-1177
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1177
Project: JBoss Messaging
Issue Type: Sub-task
Components: Messaging Core
Affects Versions: 2.0.0 Alpha
Reporter: Andy Taylor
Assigned To: Andy Taylor
Fix For: 2.0.0 Alpha
currently we have a dependency on JMSProviderAdapter. This, at the present, is in jbossas core which we shouldnt be dependant on. This either needs moving to the integration project or we need to rethink how it works. This is currently used in The XAMessagingResourceWrapper
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Clustered EJB setting at the application level (EAR)
----------------------------------------------------
Key: JBCLUSTER-146
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-146
Project: JBoss Clustering
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Galder Zamarreno
Assigned To: Brian Stansberry
We are using clustering for tests. Our application is an ear-archive which has no information about clustering. If we will built up a cluster, we have to change the ejb-jar.xml to set the clustered-tag on True. This is very intricate. Out support team have to unpack the ear - set the clustered-tag for every bean and so on.
Is it possible to set the clustered-tag all beans in a ear-Archive?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Problem with DSL and espace caracters "\"
-----------------------------------------
Key: JBRULES-1222
URL: http://jira.jboss.com/jira/browse/JBRULES-1222
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.1
Reporter: Delbart Vincent
Assigned To: Mark Proctor
Priority: Minor
Hi,
In the DSL writting it's possible to use : "+", "." ... caracters with escape caracters "\"
But in the completion list of the rules editor and in the DSLMapping class the "\" stay :
http://www.nabble.com/file/p12874031/escapeCaracters.jpg
thks,
V.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
a typo in a dslr file does not always show up an error marker
-------------------------------------------------------------
Key: JBRULES-1192
URL: http://jira.jboss.com/jira/browse/JBRULES-1192
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 4.0.1
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Open the examples, go to TroubleTicketWithDSL.dslr
then make some type of the RHS of the rule. the file will get marked as having an error, but not the rule which caused it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Adding 'OR' constraints to fact's properties in DSL
---------------------------------------------------
Key: JBRULES-1186
URL: http://jira.jboss.com/jira/browse/JBRULES-1186
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 4.0.1
Environment: All OS platform
Reporter: Andy Mei
Assigned To: Mark Proctor
Priority: Critical
I would like to write something like this :
There is a Cheese with
( - age is less than 42
or
- age is more than 60 )
- type is 'stilton'
Unfortunately, It's the drools parser which manage "-" char.
Also this previous synthax don't work in the LHS.
Anyone could help me to do an equivalent condition in my DSL ? If possible with "-" sugar char.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add jboss-common 1.2.1.GA to the JBoss maven repository
-------------------------------------------------------
Key: JBCOMMON-37
URL: http://jira.jboss.com/jira/browse/JBCOMMON-37
Project: JBoss Common
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 1.2.1.GA
Environment: n/a
Reporter: Anders Hammar
Assigned To: Dimitris Andreadis
I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. I'm For the transitive dependency to work, the jboss-common artifact is needed.
Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Complete Retro Mavenization
---------------------------
Key: JBBUILD-383
URL: http://jira.jboss.com/jira/browse/JBBUILD-383
Project: JBoss Build System
Issue Type: Feature Request
Components: JBossRetro
Reporter: Paul Gier
Fix For: JBossRetro-1.1.1.GA
The mavenization can be completed when the next surefire plugin is released.
Also there needs to be a way to configure the manifest file for the runtime jar.
Look into breaking retro into three modules: weaver, retro-runtime, and maven-plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira