Update jboss-common-core to 2.8.1.GA
------------------------------------
Key: JBMDR-40
URL: https://jira.jboss.org/jira/browse/JBMDR-40
Project: JBoss MetaData Repository
Issue Type: Component Upgrade
Components: Release
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: JBossMDR-2.0.0.CR1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Fix ValidConnectionChecker serialization
----------------------------------------
Key: JBAS-5047
URL: http://jira.jboss.com/jira/browse/JBAS-5047
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.Beta3, JBossAS-5.0.0.CR1
Some of the ValidConnectionChecker implementations are caching Method objects
which means they are not serialiazble. This needs fixing.
--
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
Change default diagnostics address to 224.0.75.75
-------------------------------------------------
Key: JGRP-820
URL: https://jira.jboss.org/jira/browse/JGRP-820
Project: JGroups
Issue Type: Task
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 2.4.4, 2.6.4, 2.7
Change default diagnostics multicast address from 224.0.0.75 to
224.0.75.75. Some routers, like Cisco, are known to not allow
joins on 224.0.0.x addresses and have secondary effects where
multicast joins on other addresses after that do not join either.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Fix org.jboss.test.timer.test.BasicTimerUnitTestCase.testMDBTimer
-----------------------------------------------------------------
Key: JBAS-5866
URL: https://jira.jboss.org/jira/browse/JBAS-5866
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Dimitris Andreadis
Assignee: Jesper Pedersen
Priority: Critical
Fix For: JBossAS-5.0.0.CR2
This is the oldest failure at this point. I think the test needs to be better writen:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Can you take care of or reassign to someone from your team?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/GPD-211?page=com.atlassian.jira.plugin... ]
Thomas Diesler reassigned GPD-211:
----------------------------------
Assignee: Koen Aers (was: Tom Baeyens)
The GPD should generate namespace qualified descriptors. Is that the case?
> Followup questions on removal of jpdl namespace ref in SOA-P quickstarts - SOA-344,JBESB-1503
> ----------------------------------------------------------------------------------------------
>
> Key: GPD-211
> URL: https://jira.jboss.org/jira/browse/GPD-211
> Project: JBoss jBPM GPD
> Issue Type: Bug
> Environment: jpdl 3.2.2 - SOA Platform build beta2
> Reporter: Len DiMaggio
> Assignee: Koen Aers
>
> Followup questions on this removal of the XML namespace reference - see SOA-344,JBESB-1503 - in processdefinition.xml files in SOA-P jBPM quickstarts:
> http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbossesb/branches/JB...
> Was this change made between SOA-P beta1 and beta2 - and if so in response to which JIRA?
> Or, was the change in beta1 and we missed it in our testing?
> Also - what's the reason for this change?
> Another side-effect of this change is that JBDS 1.0 - in creating a new jBPM project - creates a processdefinition file with this (the old) syntax:
> <?xml version="1.0" encoding="UTF-8"?>
> <process-definition
> xmlns="urn:jbpm.org:jpdl-3.2"
> name="simple">
> Should we recommend that users manually remove the namespace reference?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Need to refactor AbstractManagedObjectFactory
---------------------------------------------
Key: JBMICROCONT-237
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-237
Project: JBoss MicroContainer
Issue Type: Task
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossMC-2.0.0.CR1
The current org.jboss.managed.plugins.factory.AbstractManagedObjectFactory has too much going on to be reusable. In particular, the InstanceClassFactory(Serializable), ManagedObjectPopulator(Serializable) parameterized interfaces cannot be changed by subclasse.
--
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
Do some maven refactoring for the microcontainer build
------------------------------------------------------
Key: JBBUILD-484
URL: https://jira.jboss.org/jira/browse/JBBUILD-484
Project: JBoss Build System
Issue Type: Task
Components: Maven
Reporter: Paul Gier
Priority: Minor
Fix For: Maven Build - Maint 2008
Change pom structure and directory names in the microcontainer build to better match maven conventions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira