ServerTopLevelAction ignores ABORT_ONLY state in rollback
---------------------------------------------------------
Key: JBTM-210
URL: http://jira.jboss.com/jira/browse/JBTM-210
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.2
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.3
When executing a rollback, ServerTopLevelAction will execute the rollback if the transaction is in state RUNNING. This ignores the ABORT_ONLY state which should also result in execution of the rollback.
--
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
Support configuring decision handler from decision's context menu
-----------------------------------------------------------------
Key: GPD-66
URL: http://jira.jboss.com/jira/browse/GPD-66
Project: JBoss jBPM GPD
Issue Type: Feature Request
Reporter: John Ruud
Assigned To: Koen Aers
Priority: Minor
It's currently possible to configure a node's action handler from a node's context menu (by choosing 'properties'). It would be very useful to be able to configure a decision's decision handler in a similar fashion.
--
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
Update JBossRemoting to version 2.2.0
-------------------------------------
Key: JBAS-3856
URL: http://jira.jboss.com/jira/browse/JBAS-3856
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Remoting
Reporter: Dimitris Andreadis
Assigned To: Tom Elrod
Fix For: JBossAS-5.0.0.Beta2
JBAS-3273 brought JBossAS Beta1 to remoting 2.2.0.Alpha2. This task is to track the upgrade to a stable 2.2.0 release.
--
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
PojoCache jmx test case failure
-------------------------------
Key: JBCACHE-849
URL: http://jira.jboss.com/jira/browse/JBCACHE-849
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Brian Stansberry
Fix For: 2.0.0.GA
Current pojo.jmx test is failing so I have commented them out. But we need to fix them before GA.
--
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
[ http://jira.jboss.com/jira/browse/JBAS-3170?page=all ]
Scott M Stark updated JBAS-3170:
--------------------------------
Fix Version/s: JBossAS-5.0.0.Beta3
(was: JBossAS-5.0.0.Beta2)
Delayed the full completion to Beta3.
> ProfileService Bootstrapping of the MC
> --------------------------------------
>
> Key: JBAS-3170
> URL: http://jira.jboss.com/jira/browse/JBAS-3170
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: MicroContainer bus
> Reporter: Scott M Stark
> Assigned To: Scott M Stark
> Priority: Blocker
> Fix For: JBossAS-5.0.0.Beta3
>
>
> Tasks for bootstrapping the mc using the profile service.
--
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
AOP integration
---------------
Key: JBAS-4054
URL: http://jira.jboss.com/jira/browse/JBAS-4054
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Scott M Stark
Track the aop integration issues that prevent aspects from being applied
--
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
Document the Beta2 profileservice architecture
----------------------------------------------
Key: JBAS-4112
URL: http://jira.jboss.com/jira/browse/JBAS-4112
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta2
--
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
modify hbm.xml files in jpdl and identity to include auto-import=false
----------------------------------------------------------------------
Key: JBPM-911
URL: http://jira.jboss.com/jira/browse/JBPM-911
Project: JBoss jBPM
Issue Type: Sub-task
Components: Core Engine
Reporter: Kevin Klinemeier
Assigned To: Tom Baeyens
There are mapping files in three locations, jpdl, identity, and bpel. This is for the first two locations.
--
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