[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20051230002049 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:94: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/30/2005 00:20:49Time to build: 65 minutes 17 secondsLast changed: 12/29/2005 21:30:25Last log entry: JBREM-270:Replaced "," with "&" Unit Tests: (163) Total Errors and Failures: (4)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)testStartorg.jboss.test.remoting.marshall.dynamic.remote.http.HTTPMarshallerLoadingTestCasetestStartorg.jboss.test.remoting.marshall.dynamic.remote.socket.SocketMarshallerLoadingTestCase Modifications since last builds: (first 50 of 1159)1.7modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/PrimeScenarioServer.javaEliminated unnecessary import of MultiplexingManager.1.19modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexServer.javaJBREM-172, JBREM-262:1. The RUN_LONG_MESSAGES_TEST behavior was strengthened increase the likelyhood that all relevant paths in OutputMultiplexor are exercised.2. A new behavior, RUN_MULTIPLE_READERS_TEST, has been added.1.1addedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/utility/GrowableStreamTestCase.javaJBREM-172:Added JUnit tests for the newly introduced classes GrowablePipedInputStream, GrowablePipedOutputStream, and ShrinkableByteArrayOutputStream.1.1addedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/utility/ShrinkableByteArrayOutputStreamTestCase.javaJBREM-172:Added JUnit tests for the newly introduced classes GrowablePipedInputStream, GrowablePipedOutputStream, and ShrinkableByteArrayOutputStream.1.1addedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/utility/SuccessCountingTestCase.javaJBREM-172:Added JUnit tests for the newly introduced classes GrowablePipedInputStream, GrowablePipedOutputStream, and ShrinkableByteArrayOutputStream.1.18modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexServer.javaJBREM-172:Added new behavior to behavior test thread to test decomposition of long messages.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-253 - changed to use coyote connector by default instead of http server invoker. Also adding many fixes so now only ssl related http tests are failing within the tests suite.1.4modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/invoker/MultiplexInvokerTestCase.javaJBREM-254:Overrode getJVMArguments() to call super.getJVMArguments() and then pick up remoting.metadata.callback system parameter.1.4modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/invoker/MultiplexInvokerClientTest.javaJBREM-254:Eliminated getCallbackPort(), since it can work with default value, -1, which causes InvokerClientTest to get a random port.1.17modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexServer.javaJBREM-244:Added separate logging appender.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.keystoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.truststoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/invoker/MultiplexInvokerClientTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-214 - fixes for test failures (includ
[JBoss-dev] jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20051229233438 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:94: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/29/2005 23:34:38Time to build: 16 minutes 40 secondsLast changed: 12/29/2005 21:30:25Last log entry: JBREM-270:Replaced "," with "&" Unit Tests: (81) Total Errors and Failures: (11)testSameLocatororg.jboss.test.remoting.deploy.DualDeploymentTestCase(java_serialization)testSameSubsystemorg.jboss.test.remoting.deploy.DualDeploymentTestCase(java_serialization)testNoSubsystemorg.jboss.test.remoting.deploy.DualDeploymentTestCase(java_serialization)testStartorg.jboss.test.remoting.detection.jndi.JNDIDetectorTestCase(java_serialization)testDetectorsorg.jboss.test.remoting.detection.metadata.MetadataTestCase(java_serialization)testDetectorsorg.jboss.test.remoting.detection.multicast.MulticastUnitTestCase(java_serialization)testStartorg.jboss.test.remoting.handler.mbean.MBeanHandlerTestCase(java_serialization)testStartorg.jboss.test.remoting.marshall.dynamic.remote.http.HTTPMarshallerLoadingTestCasetestStartorg.jboss.test.remoting.marshall.dynamic.remote.socket.SocketMarshallerLoadingTestCasetestStartorg.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.http.ssl.custom.HTTPSInvokerTestCase(java_serialization) Modifications since last builds: (first 50 of 1159)1.7modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/PrimeScenarioServer.javaEliminated unnecessary import of MultiplexingManager.1.19modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexServer.javaJBREM-172, JBREM-262:1. The RUN_LONG_MESSAGES_TEST behavior was strengthened increase the likelyhood that all relevant paths in OutputMultiplexor are exercised.2. A new behavior, RUN_MULTIPLE_READERS_TEST, has been added.1.1addedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/utility/GrowableStreamTestCase.javaJBREM-172:Added JUnit tests for the newly introduced classes GrowablePipedInputStream, GrowablePipedOutputStream, and ShrinkableByteArrayOutputStream.1.1addedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/utility/ShrinkableByteArrayOutputStreamTestCase.javaJBREM-172:Added JUnit tests for the newly introduced classes GrowablePipedInputStream, GrowablePipedOutputStream, and ShrinkableByteArrayOutputStream.1.1addedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/utility/SuccessCountingTestCase.javaJBREM-172:Added JUnit tests for the newly introduced classes GrowablePipedInputStream, GrowablePipedOutputStream, and ShrinkableByteArrayOutputStream.1.18modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexServer.javaJBREM-172:Added new behavior to behavior test thread to test decomposition of long messages.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-253 - changed to use coyote connector by default instead of http server invoker. Also adding many fixes so now only ssl related http tests are failing within the tests suite.1.4modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/invoker/MultiplexInvokerTestCase.javaJBREM-254:Overrode getJVMArguments() to call super.getJVMArguments() and then pick up remoting.metadata.callback system parameter.1.4modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/invoker/MultiplexInvokerClientTest.javaJBREM-254:Eliminated getCallbackPort(), since it can work with default value, -1, which causes InvokerClientTest to get a random port.1.17modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexServer.javaJBREM-244:Added separate logging appender.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.keystoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.truststoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/invoker/MultiplexInvokerClientTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20051229230208 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:95: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/29/2005 23:02:08Time to build: 32 minutes 9 secondsLast changed: 12/28/2005 10:48:11Last log entry: Add the 1.2.4SP1 changelog notes. Unit Tests: (1171) Total Errors and Failures: (58)unknownorg.jboss.cache.ReadWriteLockWithUpgradeStressTestunknownorg.jboss.cache.aop.ReplicatedAopTesttestRefCountCheckReplorg.jboss.cache.aop.ReplicatedObjectGraphAopTesttestRemoveObject1org.jboss.cache.aop.ReplicatedObjectGraphAopTesttestRemoveObject2org.jboss.cache.aop.ReplicatedObjectGraphAopTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead50JRunitTesttestRead75PercentMultiorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead75JRunitTesttestRead90PercentMultiorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead90JRunitTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead50JRunitTesttestRead75PercentMultiorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead75JRunitTesttestRead90PercentMultiorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead90JRunitTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.ReplAsyncPessRead50JRunitTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.ReplAsyncPessRead75JRunitTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.ReplAsyncPessRead90JRunitTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.ReplSyncPessRead50JRunitTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.ReplSyncPessRead75JRunitTesttestRead50PercentMultiorg.jboss.cache.benchmark.tests.ReplSyncPessRead90JRunitTestunknownorg.jboss.cache.marshall.SyncReplTestunknownorg.jboss.cache.replicated.SyncReplTxTestunknownorg.jboss.cache.statetransfer.StateTransfer1241Testunknownorg.jboss.cache.statetransfer.StateTransfer124Testunknownorg.jboss.cache.statetransfer.StateTransfer130TesttestRemoveKeyRollbackorg.jboss.cache.transaction.TransactionTesttestBareConfigorg.jboss.cache.InterceptorConfigurationTesttestTxConfigorg.jboss.cache.InterceptorConfigurationTesttestSharedCacheLoaderConfigorg.jboss.cache.InterceptorConfigurationTesttestUnsharedCacheLoaderConfigorg.jboss.cache.InterceptorConfigurationTesttestTxAndReplorg.jboss.cache.InterceptorConfigurationTesttestOptimisticChainorg.jboss.cache.InterceptorConfigurationTesttestOptimisticReplicatedChainorg.jboss.cache.InterceptorConfigurationTesttestOptimisticCacheLoaderChainorg.jboss.cache.InterceptorConfigurationTesttestOptimisticPassivationCacheLoaderChainorg.jboss.cache.InterceptorConfigurationTesttestInvalidationInterceptorChainorg.jboss.cache.InterceptorConfigurationTesttestCollectionWithCacheLoaderorg.jboss.cache.aop.loader.FileCacheLoaderAopTesttestConcurrentUseSyncorg.jboss.cache.aop.statetransfer.StateTransfer1241AopTesttestConcurrentUseSyncorg.jboss.cache.aop.statetransfer.StateTransfer124AopTesttestConcurrentUseSyncorg.jboss.cache.aop.statetransfer.StateTransfer130AopTestwarningorg.jboss.cache.benchmark.support.BaseTestwarningorg.jboss.cache.benchmark.support.Read50PercentTestwarningorg.jboss.cache.benchmark.support.Read50PercentTestwarningorg.jboss.cache.benchmark.support.Read75PercentTestwarningorg.jboss.cache.benchmark.support.Read75PercentTestwarningorg.jboss.cache.benchmark.support.Read90PercentTestwarningorg.jboss.cache.benchmark.support.Read90PercentTesttestUpdateEvictionorg.jboss.cache.eviction.AopLRUPolicyTesttestReadCommittedorg.jboss.cache.lock.LockTesttest2ReadersAnd1Writerorg.jboss.cache.lock.ReentrantWriterPreferenceReadWriteLockTesttestTransactionalBehaviourorg.jboss.cache.options.cachemodelocal.AsyncReplPessLocksTesttestPutKeyValueorg.jboss.cache.options.cachemodelocal.SyncReplOptLocksTesttestPutDataorg.jboss.cache.options.cachemodelocal.SyncReplOptLocksTesttestRemoveNodeorg.jboss.cache.options.cachemodelocal.SyncReplOptLocksTesttestRemoveKeyorg.jboss.cache.options.cachemodelocal.SyncReplOptLocksTesttestTransactionalBehaviourorg.jboss.cache.options.cachemodelocal.SyncReplOptLocksTesttestReadCommittedorg.jboss.cache.transaction.IsolationLevelReadCommittedTesttestRemoveorg.jboss.cache.transaction.TransactionTesttestRemoveAndRollbackorg.jboss.cache.transaction.TransactionTesttestRemoveKeyRollback2org.jboss.cache.transaction.TransactionTesttestRemoveKeyRollback3org.jboss.cache.transaction.TransactionTest Modifications since last builds: (first 50 of 950)1.3modifiedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaFixes rating to JBCACHE-118 - optimising cache loader functionality.1.2modifiedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaAdded a perf test
[JBoss-dev] jboss-portal-2.2-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.2-testsuite?log=log20051229225915 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:66: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:92: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:277: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/29/2005 22:59:15Time to build: 2 minutes 28 secondsLast changed: 12/28/2005 00:15:42Last log entry: - targetWindowRef rename Unit Tests: (92) Total Errors and Failures: (50)testCreateRepositoryorg.jboss.portal.test.cms.TestAlltestFileDeleteorg.jboss.portal.test.cms.TestAlltestFileCreateorg.jboss.portal.test.cms.TestAlltestFileGetorg.jboss.portal.test.cms.TestAlltestFileUpdateorg.jboss.portal.test.cms.TestAlltestFileGetVersionorg.jboss.portal.test.cms.TestAlltestFileListorg.jboss.portal.test.cms.TestAlltestFileCopyorg.jboss.portal.test.cms.TestAlltestArchiveUploadorg.jboss.portal.test.cms.TestAlltestFolderDeleteorg.jboss.portal.test.cms.TestAlltestFolderCreateorg.jboss.portal.test.cms.TestAlltestFolderGetorg.jboss.portal.test.cms.TestAlltestFolderUpdateorg.jboss.portal.test.cms.TestAlltestFolderCopyorg.jboss.portal.test.cms.TestAlltestFolderListorg.jboss.portal.test.cms.TestAlltestIfFalseorg.jboss.portal.test.core.IfTagTestCasetestIfTrueorg.jboss.portal.test.core.IfTagTestCasetestNullKeyThrowsIllegalArgumentExceptionorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestReadorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestWriteorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestNullWriteorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestIsReadOnlyorg.jboss.portal.test.portlet.PortletPreferencesTestCasetestMaporg.jboss.portal.test.portlet.PortletPreferencesTestCasetestPreferencesCanBeSetToNullorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestPreferencesMapModificationDoesNotModifyPreferencesValuesorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestResetPreferenceHavingNoDefaultValueDeletesItorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestReadOnlyPreferenceCannotBeModifiedorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestStoreMustPersistAllChangesorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestStoreMethodMustBeAtomicorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestChangesMadeButNotStoredAreDiscardedorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestStoreCalledDuringRenderThrowsIllegalArgumentExceptionorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestPortletPreferencesObjectMustReflectCurrentValuesOfThePersistentStoreorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestCanModifyNonReadOnlyPreferenceorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestDynamicPreferenceTreatedLikeModifiablePreferenceorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestCreateASingleInstanceOfValidatororg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestInvokeValidatorValidateBeforeWritingChangesorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestInvalidationCancelsStoreorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestValidationStoresorg.jboss.portal.test.portlet.preferences.spec.PreferencesSpecTestCasetestGetRepositoryAndLoginorg.jboss.portal.test.cms.TestAll Modifications since last builds: (first 50 of 1920)1.6modifiedrussothirdparty/apache-jackrabbit/lib/jackrabbit-core.jar- updated jackrabbit jar- converted jdbc PM to us hibernate- default repository configured to use hibernatePM1.3modifiedjulienthirdparty/jboss-cache/README.txtupdate jboss cache jars to those of 4.0.3SP11.6modifiedjulienthirdparty/jboss-cache/lib/jboss-cache.jarupdate jboss cache jars to those of 4.0.3SP11.5deletedjulienthirdparty/jboss-cache/lib/jboss-remoting.jarupdate jboss cache jars to those of 4.0.3SP11.5modifiedjulienthirdparty/jboss-cache/lib/jgroups.jarupdate jboss cache jars to those of 4.0.3SP11.24modifiedjulientools/etc/buildfragments/libraries.entupdate jboss cache jars to those of 4.0.3SP11.12modifiedjulientheme/src/main/org/jboss/portal/theme/impl/render/DivRegionRenderer.java- better handle various errors : security, not found, internal errors1.2modifiedjulienthirdparty/sun-facelets/lib/jsf-facelets.jaradded the portlet view handler for facelets in the jar1.23modifiedjulientools/etc/buildfragments/libraries.entswitching to facelets that
[JBoss-dev] jboss-portal-2.0-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20051229225632 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:66: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:92: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:277: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/29/2005 22:56:32Time to build: 2 minutes 14 secondsLast changed: 12/28/2005 00:15:42Last log entry: - targetWindowRef rename Unit Tests: (67) Total Errors and Failures: (25)testAorg.jboss.portal.test.cms.stress.ConcurrentTestCasetestIfFalseorg.jboss.portal.test.core.IfTagTestCasetestIfTrueorg.jboss.portal.test.core.IfTagTestCasetestFindUser1org.jboss.portal.test.core.RoleModelTestCasetestFindUser2org.jboss.portal.test.core.RoleModelTestCasetestFindUsersorg.jboss.portal.test.core.RoleModelTestCasetestCreateUserorg.jboss.portal.test.core.RoleModelTestCasetestCreateRoleorg.jboss.portal.test.core.RoleModelTestCasetestCountUserorg.jboss.portal.test.core.RoleModelTestCasetestRemoveNonExistingRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveRoleorg.jboss.portal.test.core.RoleModelTestCasetestRemoveUserorg.jboss.portal.test.core.RoleModelTestCasetestFindRolesorg.jboss.portal.test.core.RoleModelTestCasetestFindRoleMembersorg.jboss.portal.test.core.RoleModelTestCasetestResourceBundleorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestResourceBundleCascadeorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCasetestGetResourceBundleDuringInitorg.jboss.portal.test.portlet.portletconfig.PortletConfigTestCase Modifications since last builds: (first 50 of 1506)1.3modifiedjulienthirdparty/jboss-cache/README.txtupdate jboss cache jars to those of 4.0.3SP11.6modifiedjulienthirdparty/jboss-cache/lib/jboss-cache.jarupdate jboss cache jars to those of 4.0.3SP11.5deletedjulienthirdparty/jboss-cache/lib/jboss-remoting.jarupdate jboss cache jars to those of 4.0.3SP11.5modifiedjulienthirdparty/jboss-cache/lib/jgroups.jarupdate jboss cache jars to those of 4.0.3SP11.24modifiedjulientools/etc/buildfragments/libraries.entupdate jboss cache jars to those of 4.0.3SP11.23modifiedjulientools/etc/buildfragments/libraries.entswitching to facelets that provide a decent support for inclusion and thus enable reusability of JSF sub trees1.7modifiedjulientools/etc/buildfragments/modules.entadded the faces modules to the build1.7modifiedjulienthirdparty/jboss-system/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-system/lib/jboss-common.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-system/lib/jboss-jmx.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-system/lib/jboss-system.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-j2ee/lib/jboss-j2ee.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-server/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedjulienthirdparty/jboss-server/lib/jboss.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-sx/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-sx/lib/jbosssx.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.5modifiedjulienthirdparty/jboss-client/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.5modifiedjulienthirdparty/jboss-client/lib/jbossall-client.jarupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.7modifiedjulienthirdparty/jboss-j2ee/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loadin
[JBoss-dev] EJB3 dependency on deployer ordering
I just implemented being able to deploy ejb3 archives in a .jar. To make this work, I have to guarantee that the EJB3 deployer runs accepts() before the old EJB2.1 deployer. It seems, whoever is added to the MainDeployer last, runs first when accepts is called. So, I added an EJBDeployer dependency to the EJB3Deployer. SO DON'T CHANGE THIS BEHAVIOR IN BRANCH 4.0 PLEASE -- Bill Burke Chief Architect JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Assigning JIRA tasks to non-committers
Scott M Stark wrote: The Community Task was instead of creating a new group. If there is a non-committer group it’s a mute point. For the following I don’t see the point of a contributor assignment as the task should not even be created until the issue is to the point of the artifact being ready: - proof of concept. This has to be discussed in the design forum so I don’t see why a jira issue is needed in addition. Because there is a lot of noise in the forums. I have limited control over how discussion threads are being created and how they evolve. A forum thread is an open conversation that hopefully helps define and distill a very clear set of issues that need to be executed. Ex: proof of concept that must do this and that. In my opinion, a design forum thread must end with one (or more) JIRA issues or be wiped out as irrelevant. I would like to be able to control more tightly the tasks that are being generated this way, and associate names with them. (by the way, associated a JIRA task with a trhead this is a forum feature I suggested long ago. JIRA can point to a thread, why not a design thread point to a JIRA issue, but now I am diverging). To conclude the "proof of concept" point, there is an issue (the JIRA task), a deliverable (the prototype or some amount of functionality that has to be implemented) and a person that does the work and doesn't necessarily have to be a contributor. - Testing. What functionality exists for which no testcase exists? If you are just wanting to punt the work of testcase to the community, ok to the extent that this does not mean a test is not written. This is border line broken development in that untested features are being released. Correct. However, I can create a JIRA task for a testcase I thought about but I didn't not implement yet. Another type of testing JIRA tasks I can think of "test X feature on the Y platform while interoperating with the Z thirdparty entity and generate a configuration file tuned for X/Y/Z that will be added to the pre-packaged set of alternate configuration files. The task and the deliverable are clearly defined, and they can be executed by a non-committer. - Provide code examples. Unless this is making it into the project docbook, what use is it? It’s just going to be out of date as time goes by. Messaging comes with a set of "examples", each of them containing a README file and a small number of classes that demonstrate a simple feature: sending/receiving a message to a queue, sending/receiving a message to a topic, deploying an MDB, etc. These examples serve two purposes: give a novice user a starting point with the and serve as a second layer of integration tests, as they can be automated and they are run and must pass on each release. Each "example" has a standard format, and I would be happy to get some of these from the community to include them with the release. Since there are contributors asking "how can I start contributing", I would put a set of this kind of tasks out, ready and up for grabs. They can be assigned immediately and do not imply a significant learning curve to produce. No CVS access is required and there is a very well defined deliverable produced by the task. For a patch, I can see assigning it to someone just so that there is a notion of ownership to prevent duplicate work. Same for a wiki page or article. A patch (in this case is a JIRA "Bug" that sits out there in the open) can be assigned to a non-committer and then be applied to the code base. A more basic jira question is, can jira be setup such that a contributor can assign a task to anyone, but only the contributors show up in the drop down list? If that is allowed let’s set this up and forget the community task and separate contributor group as the distinction and maintenance of the group is questionable to me. The maintentance of the group is the biggest issue, I agree. I don't know what this implies, but if it's a lot of trouble, I guess we can live without it From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ovidiu Feodorov Sent: Thursday, December 29, 2005 10:35 AM To: JBoss Development Subject: [JBoss-dev] Assigning JIRA tasks to non-committers Sometimes it is probably appropriate to assign a JIRA task to somebody who is not a CVS committer. These are cases in which I find this useful: - Creating a proof of concept or a prototype that most likely won't make it into the main code base in its actual form. - Providing patches that will be ultimately applied by a committer to the code base - Testing functionality and specific configurations. - Provide code examples - Write a wiki documentation page or other type of article None of these tasks require their assignee to have committer access since they don't imply CVS write access. However they would help a project l
RE: [JBoss-dev] Assigning JIRA tasks to non-committers
The Community Task was instead of creating
a new group. If there is a non-committer group it’s a mute point. For the
following I don’t see the point of a contributor assignment as the task
should not even be created until the issue is to the point of the artifact
being ready:
-
proof of
concept. This has to be discussed in the design forum so I don’t see why
a jira issue is needed in addition.
-
Testing.
What functionality exists for which no testcase exists? If you are just wanting
to punt the work of testcase to the community, ok to the extent that this does
not mean a test is not written. This is border line broken development in that
untested features are being released.
-
Provide
code examples. Unless this is making it into the project docbook, what use is
it? It’s just going to be out of date as time goes by.
For a patch, I can see assigning it to
someone just so that there is a notion of ownership to prevent duplicate work.
Same for a wiki page or article.
A more basic jira question is, can jira be
setup such that a contributor can assign a task to anyone, but only the contributors
show up in the drop down list? If that is allowed let’s set this up and
forget the community task and separate contributor group as the distinction and
maintenance of the group is questionable to me.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ovidiu Feodorov
Sent: Thursday, December 29, 2005
10:35 AM
To: JBoss Development
Subject: [JBoss-dev] Assigning
JIRA tasks to non-committers
Sometimes it is probably appropriate to assign a JIRA task to somebody who is
not a CVS committer. These are cases in which I find this useful:
- Creating a proof of concept or a prototype that most likely won't make it
into the main code base in its actual form.
- Providing patches that will be ultimately applied by a committer to the code
base
- Testing functionality and specific configurations.
- Provide code examples
- Write a wiki documentation page or other type of article
None of these tasks require their assignee to have committer access since they
don't imply CVS write access. However they would help a project lead to keep
track of who is doing what and administer more easily work that is done by
non-JBoss volunteers.
The current JIRA setup doesn't allow this. In order to enable it, we will need
to add a new group to JIRA ("Contributor" or similar) and probably a
new task type "Community Task" (Scott's idea). Personally I
don't see the usefulness of the last one, I think the existing "Task"
is sufficient. Following the same logic, a "Contributor" can report
an (existing type) "Bug" or can suggest an (existing type)
"Feature Request" and he can be also assigned to it, pending a patch
submission. The patch will be be applied to CVS by a committer, usually the one
who assigned the task to the contributor.
A project lead should be able to include an user in the project's
"Contributor" group. Again, this DOES NOT implies that the user will
be granted CVS access.
This arrangement could also be a good motivator for volunteers, as they see
their contributions publicly recognized and documented. Being a
"Contributor" should be prerequisite of becoming a
"Committer".
Please let me know if you find this useful.
Regards,
Ovidiu
[JBoss-dev] Assigning JIRA tasks to non-committers
Sometimes it is probably appropriate to assign a JIRA task to somebody
who is
not a CVS committer. These are cases in which I find this useful:
- Creating a proof of concept or a
prototype that most likely won't make it into the main code base in its
actual form.
- Providing patches that will be ultimately
applied by a committer to the code base
- Testing functionality and specific
configurations.
- Provide code examples
- Write a wiki documentation page or other
type of article
None of these tasks require their assignee to have committer access
since they don't imply CVS write access. However they would help a
project lead to keep track of who is doing what and administer more
easily work that is done by non-JBoss volunteers.
The current JIRA setup doesn't allow this. In order to enable it, we
will need to add a new group to JIRA ("Contributor" or similar) and
probably a new task type "Community Task" (Scott's idea). Personally I
don't see the usefulness of the last one, I think the existing "Task"
is sufficient. Following the same logic, a "Contributor"
can report an (existing type) "Bug" or can suggest an (existing type)
"Feature Request" and he can be
also assigned to it, pending a patch submission. The patch will be be
applied to CVS by a committer, usually the one who assigned the task to
the contributor.
A project lead should be able to include an user in the project's
"Contributor" group. Again, this DOES NOT implies that the user will be
granted CVS access.
This arrangement could also be a good motivator for volunteers, as they
see their contributions publicly recognized and documented. Being a "Contributor" should be prerequisite of becoming a
"Committer".
Please let me know if you find this useful.
Regards,
Ovidiu
[JBoss-dev] jboss-head-jdk-matrix build.1108 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20051229110043Lbuild.1108 BUILD COMPLETE - build.1108Date of build: 12/29/2005 11:00:43Time to build: 10 minutes 18 secondsLast changed: 12/29/2005 10:36:58Last log entry: [JBAS-2608] added configuration file based on working sample provided by Bison Schweiz Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 97)1.2modifiedltexiermessaging/src/etc/server/examples/deploy/derby-jdbc2-service.xml[JBAS-2608] added configuration file based on working sample provided by Bison Schweiz1.2modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/JMSXDeliveryCountTest.javaFix problem with message redelivery, plus some more work on XA recovery1.10modifiedtimfoxjms/src/main/org/jboss/jms/client/state/ConnectionState.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/BytesMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.38modifiedtimfoxjms/src/main/org/jboss/jms/message/JBossMessage.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/MapMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/message/MessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/ObjectMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/StreamMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/TextMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.57modifiedtimfoxjms/src/main/org/jboss/jms/server/ServerPeer.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/BrowserEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConnectionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConnectionFactoryEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConsumerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.10modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/DeliveryRunnable.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ProducerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.6modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerBrowserEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.7modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConnectionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.7modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConnectionFactoryEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.8modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConsumerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerProducerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.8modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerSessionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.6modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/SessionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.7modifiedtimfoxjms/src/main/org/jboss/messaging/core/tx/TransactionRepository.javaFix problem with message redelivery, plus some more work on XA recovery1.2modifiedtimfoxjms/src/main/org/jboss/messaging/core/tx/XidImpl.javaFix problem with message redelivery, plus some more work on XA recovery1.75modifiedtimfoxjms/tests/build.xmlFix problem with message redelivery, plus some more work on XA recovery1.24modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/AcknowledgmentTest.javaFix problem with message redelivery, plus some more work on XA recovery1.14modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/ConnectionClosedTest.javaFix problem with message redelivery, plus some more work on XA recovery1.19modifiedtimfoxj
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20051229092356 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:50: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 12/29/2005 09:23:56Time to build: 3 minutes 52 secondsLast changed: 12/29/2005 09:09:57Last log entry: Fix problem with message redelivery, plus some more work on XA recovery Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 96)1.2modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/message/JMSXDeliveryCountTest.javaFix problem with message redelivery, plus some more work on XA recovery1.10modifiedtimfoxjms/src/main/org/jboss/jms/client/state/ConnectionState.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/BytesMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.38modifiedtimfoxjms/src/main/org/jboss/jms/message/JBossMessage.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/MapMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/message/MessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/ObjectMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/StreamMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/message/TextMessageDelegate.javaFix problem with message redelivery, plus some more work on XA recovery1.57modifiedtimfoxjms/src/main/org/jboss/jms/server/ServerPeer.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/BrowserEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConnectionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConnectionFactoryEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.4modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ConsumerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.10modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/DeliveryRunnable.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ProducerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.6modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerBrowserEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.7modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConnectionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.7modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConnectionFactoryEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.8modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerConsumerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.5modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerProducerEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.8modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/ServerSessionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.6modifiedtimfoxjms/src/main/org/jboss/jms/server/endpoint/SessionEndpoint.javaFix problem with message redelivery, plus some more work on XA recovery1.7modifiedtimfoxjms/src/main/org/jboss/messaging/core/tx/TransactionRepository.javaFix problem with message redelivery, plus some more work on XA recovery1.2modifiedtimfoxjms/src/main/org/jboss/messaging/core/tx/XidImpl.javaFix problem with message redelivery, plus some more work on XA recovery1.75modifiedtimfoxjms/tests/build.xmlFix problem with message redelivery, plus some more work on XA recovery1.24modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/AcknowledgmentTest.javaFix problem with message redelivery, plus some more work on XA recovery1.14modifiedtimfoxjms/tests/src/org/jboss/test/messaging/jms/ConnectionClosedTest.javaFix problem with message redelivery, plus some
[JBoss-dev] jboss-3.2-testsuite build.204 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20051229050152Lbuild.204 BUILD COMPLETE - build.204Date of build: 12/29/2005 05:01:52Time to build: 46 minutes 22 seconds Unit Tests: (1821) Total Errors and Failures: (0)All Tests Passed Modifications since last builds: (first 50 of 0)
[JBoss-dev] ejb3-head-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-head-testsuite?log=log20051229025447 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-ejb3-head-testsuite.xml:82: Exit code: 1 See tests.log in Build Artifacts for details.Date of build: 12/29/2005 02:54:47Time to build: 16 minutes 10 secondsLast changed: 12/28/2005 22:18:36Last log entry: compilation problems with HB 3.1 upgrade Unit Tests: (0) Total Errors and Failures: (0) Modifications since last builds: (first 50 of 3208)1.4modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaapplication-exception support1.7modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaapplication-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorAppException.javaapplication-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorCheckedRollbackException.javaapplication-exception support1.5modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaapplication-exception support1.8modifiedbdecostesrc/test/org/jboss/ejb3/test/strictpool/StrictlyPooledMDB.javaactivateConfig to activationConfig1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javaactivateConfig to activationConfig1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javaactivateConfig to activationConfig1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/unit/EmbeddedEjb3TestCase.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/Customer.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOBean.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOLocal.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAORemote.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/EmbeddedEJB3.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/JndiTest.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javatest for embedded EJB3 in WLS1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/Customer.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTest.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTestBean.javaUpdate the jboss LGPL headers1.5modifiedstarksmsrc/test/org/jboss/ejb3/test/tableperinheritance/Customer.javaUpdate the jboss LGPL headers1.5modifiedstarksmsrc/test/org/jboss/ejb3/test/tableperinheritance/Employee.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/tableperinheritance/EntityTest.javaUpdate the jboss LGPL headers1.9modifiedstarksmsrc/test/org/jboss/ejb3/test/tableperinheritance/EntityTestBean.javaUpdate the jboss LGPL headers1.5modifiedstarksmsrc/test/org/jboss/ejb3/test/tableperinheritance/Person.javaUpdate the jboss LGPL headers1.4modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTester.javaUpdate the jboss LGPL headers1.9modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean21.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AnnotatedAppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/CheckedRollbackException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRuntimeException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRuntimeException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/SimpleEntity.javaUpdate the jboss LGPL headers1.4modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/un
