[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060201014338 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:96: 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: 02/01/2006 01:43:38Time to build: 33 minutes 37 secondsLast changed: 12/28/2005 10:48:11Last log entry: Add the 1.2.4SP1 changelog notes. Unit Tests: (1321) Total Errors and Failures: (36)testRemoveAndAddorg.jboss.cache.aop.collection.CachedSetAopTesttestIteratororg.jboss.cache.aop.collection.CachedSetAopTesttestCollectionWithCacheLoaderorg.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.Read75PercentTestwarningorg.jboss.cache.benchmark.support.Read90PercentTestwarningorg.jboss.cache.benchmark.tests.HashMapRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.HashMapRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.HashMapRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplAsyncPessRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplAsyncPessRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplAsyncPessRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplSyncPessRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplSyncPessRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplSyncPessRead90JRunitTesttestUpdateEvictionorg.jboss.cache.eviction.AopLRUPolicyTesttestOptSyncReplorg.jboss.cache.loader.CacheLoaderWithReplicationTesttestReadCommittedorg.jboss.cache.lock.LockTesttest2ReadersAnd1Writerorg.jboss.cache.lock.ReentrantWriterPreferenceReadWriteLockTestwarningorg.jboss.cache.optimistic.LocalCLTestwarningorg.jboss.cache.optimistic.LocalPessimisticCLTestwarningorg.jboss.cache.optimistic.LocalPessimisticTestwarningorg.jboss.cache.optimistic.LocalTesttestConcurrentUseSyncorg.jboss.cache.statetransfer.StateTransfer124TesttestConcurrentAccessWithRWLockorg.jboss.cache.transaction.ConcurrentTransactionalTesttestReadCommittedorg.jboss.cache.transaction.IsolationLevelReadCommittedTest Modifications since last build: (first 50 of 1286)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 to measure performance on basic operations with a cache loader1.1addedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaAdded a perf test to measure performance on basic operations with a cache loader1.2modifieddhuangtests/stress/org/jboss/cache/EvictionLocalStressTest.javaEviction policy refactoring to support 1 Policy per Region.Refactoring of Eviction Policies to allow for easier user extension.Introduce EvictionQueue and EvictionConfiguration interfaces.New Eviction Policies for MRU and LFU.Allow configuration of EvictionPolicies at runtime.References JIRA tasks:JBCACHE-314JBCACHE-313JBCACHE-312JBCACHE-286JBCACHE-225JBCACHE-2131.2modifieddhuangtests/stress/org/jboss/cache/LocalStressTest.javaEviction policy refactoring to support 1 Policy per Region.Refactoring of Eviction Policies to allow for easier user extension.Introduce EvictionQueue and EvictionConfiguration interfaces.New Eviction Policies for MRU and LFU.Allow configuration of EvictionPolicies at runtime.References JIRA tasks:JBCACHE-314JBCACHE-313JBCACHE-312JBCACHE-286JBCACHE-225JBCACHE-2131.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplAsyncPessRead50JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplAsyncPessRead75JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplAsyncPessRead90JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplSyncPessRead50JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplSyncPessRead75JRunitTest.javaAdded r
[JBoss-dev] ejb3-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060131223828 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details.Date of build: 01/31/2006 22:38:28Time to build: 26 minutes 2 secondsLast changed: 12/31/2005 16:46:08Last log entry: call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 3609)1.3modifiedbillsrc/test/org/jboss/ejb3/test/tableperinheritance/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.7modifiedbillsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.6modifiedbillsrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaEJBs and Persistence can now be within a .jar file1.3modifiedbillsrc/test/org/jboss/ejb3/test/xmlcfg/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.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.javabranches: 1.1.2;application-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorCheckedRollbackException.javabranches: 1.1.2;application-exception support1.5modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaapplication-exception support1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javabranches: 1.2.2;activateConfig to activationConfig1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javabranches: 1.2.2;activateConfig 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.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOLocal.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAORemote.javabranches: 1.1.2;test 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.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.4mo
RE: [JBoss-dev] EJB3StandaloneBootstrap implementation
How can the scanClasspath() step be optimized/skipped in say an embedded
ejb3 project in jbosside where the data obtained during the scan was
written out in an optimized metadata store as part of the project say?
I don't really follow adding aspects like clustering to deployments
based on the location in a filesystem, virtual or otherwise. Just seems
like too much meaning being linked to the deployment url/location.
I'm busy through tomorrow, but come thu I will just checkin the current
vfs stuff I have had sitting in the workspace for months and see what
start can be made on pushing this forward.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, January 31, 2006 9:28 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] EJB3StandaloneBootstrap implementation
I think going the E-EJB3 route to start is a good idea as it will force
us to implement bare-bones implementations that do not have the idea of
a classloader or j2ee deployment schemes within them. Once we have
e-ejb3 (really e-jboss) in place, it will force us to be careful about
adding things like classloading and j2ee packaging as to not break or
bloat e-jboss.
The way I envision it working is basically how it works with current
kernel
* This shit must be REALLY FAST. Remember, we're using it with junit
tests.
* embedded-jboss-beans.xml configures a MainDeployer, BeanDeployer,
AOPDeployer, EJB3Deployer, (etc.) and basic services like TM, JNDI, etc.
* EJB3StandaloneBootstrap still exists and has three methods:
- boot(): This loads embeddded-jboss-beans.xml
- scanClasspath(). The scans the entire classpath for deployments and
calls MainDeployer.deploy() for each jar/directory/config file it finds.
calling MainDeployer.deploy(URL).
- scanClasspath(String) comma delimited list of files that should be
deployed. These files are in the classpath (java.class.path)
- deployResource(String) deploys an individual Classpath resource.
("ejb3-interceptors-aop.xml") by calling MainDeployer.deploy(URL)
My second thought is that Scanners should be responsible for creating
the DeploymentUnit rather than the main deployer. This will allow the
scanner to add metadata about the deployment or to work with different
"filesystems", like a database or profile. For instance, I envision a
cluster/ directory where any deployment put in it that supports
clustering will be clustered. The scanner could also be configured for
default security domain. For this to work, the scanner needs to attach
metadata to the deploymentunit. Since the MainDeployer will not be
responsible for creating the deployment unit, this will make it easier.
If you look at the EJB3 code, you will also find that I have done a
kernel abstraction so that the EJB3 deployer and codebase does not have
to be concerned about whether you are deployment to JBoss4 or MC. If we
do the new deployers right, the new architecture can be used as an
abstraction for projects that need to work in both JBoss4 and MC.
Man, I want to help prototype this stuff. I was about to do it for the
last EJB3 release, but I ran out of time. I'll want to jump in and help
after I finish the EJB3 book.
Later,
Bill
Scott M Stark wrote:
> I browsed through the EJB3StandaloneBootstrap and embedded ejb3 usage
of the mc to see what extent the mc is being used. In browsing through
the conf/embedded-jboss-beans.xml for the mc config, I did not see
anything related to the ejb3 container or aop layer to load the
conf/ejb3-interceptors-aop.xml. The embedded ejb3 docs show this
prototype code block for setting up embedded ejb3:
>
>
>
> EJB3StandaloneBootstrap.boot(null);
>
> // initialize JBoss MQ core services
>
>
EJB3StandaloneBootstrap.deployXmlResource("jboss-jms-beans.xml");
>
> // initialize configured test queue and topic
>
> EJB3StandaloneBootstrap.deployXmlResource("testjms.xml");
>
> // scan classpath for ejbs and MDBs
>
> EJB3StandaloneBootstrap.scanClasspath();
>
>
>
> So a lot of configuration is being done outside of the mc
embedded-jboss-beans.xml. I guess this is due to missing implementation
details of the mc such as the vfs, virtual deployment impl, and class
loader configuration. I have been thinking about how to push the mc
forward by getting it more into jboss5, but maybe using the embedded
ejb3 setup would be a less disruptive way to drive these features to
completion.
>
>
>
> Does it make sense to organize the next set of mc releases around
getting the embedded ejb3 completely configured from a prototype
standalone mc bootstrap
(http://docs.jboss.org/nightly/microkernel/docs/gettingstarted/en/html/s
tandalone.html) which loads a more complete embedded-ejb3-beans.xml that
includes the ejb3 container and aop configuration?
>
>
>
>
>
--
Bill Burke
Chief Architect
JBoss Inc.
---
This
[JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
Yes, this is Branch_4_0. Thanks, Tom. -Original Message- From: Tom Elrod Sent: Tuesday, January 31, 2006 1:28 PM To: Tom Elrod Cc: Ryan Campbell; Tom Elrod; Kabir Khan; Bill Burke; jboss-development@lists.sourceforge.net Subject: Re: ejb3-4.0-testsuite Build Failed I think I get the mis-match now. This is being build out of JBoss 4.x branch, right? If so, then the code for jbossas-remoting.jar is not there. There is an issue for this (JBAS-2698), which I will work on today. Tom Elrod wrote: > The class that is not being found is within jbossas-remoting.jar. This > is part of JBossAS code base and not remoting. Only way this would be > called to be loaded is if was configured to use the JBossAS security > domain via configuration. So am guessing the jar was excluded from the > build? > > Ryan Campbell wrote: > >> >> >> The ejb3-ssl-advanced test server is broken: >> >> >> >> 2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] >> create operation failed for package >> file:/services/cruisecontrol/checkout/ejb3-4.0-testsuite/build/output/jb oss-4.0.4RC1/server/ejb3-ssl-advanced/deploy/ejb3.deployer/ >> >> >> org.jboss.deployment.DeploymentException: No ClassLoaders found for: >> org.jboss.remoting.security.domain.DomainServerSocketFactoryService; - >> nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders >> found for: >> org.jboss.remoting.security.domain.DomainServerSocketFactoryService) >> >> at >> org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:19 6) >> >> >> at >> org.jboss.system.ServiceController.install(ServiceController.java:226) >> >> >> >> >> >> >> >> >> >> *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >> *Sent:* Monday, January 30, 2006 7:12 PM >> *To:* Adrian Brock; Bill Decoste; Bill Burke; Gavin King; >> jboss-development@lists.sourceforge.net; Kabir Khan; QA; Ruel Loehr; >> Scott M Stark; Thomas Diesler >> *Subject:* ejb3-4.0-testsuite Build Failed >> *Importance:* High >> >> >> >> View results here -> >> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=lo g20060130193339 >> >> >> *BUILD FAILED* >> >> *Ant Error Message: >> */services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: >> Exit code: 1 See tests.log in Build Artifacts for details. >> >> *Date of build: *01/30/2006 19:33:39 >> >> *Time to build: *37 minutes 18 seconds >> >> *Last changed: *12/31/2005 16:46:08 >> >> *Last log entry: *call isOpen() when obtaining session so that HEM >> registers with EM with TXset cglib_use_reflection flag to false >> >> >> > > > --- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: ejb3-4.0-testsuite Build Failed
I think I get the mis-match now. This is being build out of JBoss 4.x branch, right? If so, then the code for jbossas-remoting.jar is not there. There is an issue for this (JBAS-2698), which I will work on today. Tom Elrod wrote: The class that is not being found is within jbossas-remoting.jar. This is part of JBossAS code base and not remoting. Only way this would be called to be loaded is if was configured to use the JBossAS security domain via configuration. So am guessing the jar was excluded from the build? Ryan Campbell wrote: The ejb3-ssl-advanced test server is broken: 2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/services/cruisecontrol/checkout/ejb3-4.0-testsuite/build/output/jboss-4.0.4RC1/server/ejb3-ssl-advanced/deploy/ejb3.deployer/ org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) at org.jboss.system.ServiceController.install(ServiceController.java:226) *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *Sent:* Monday, January 30, 2006 7:12 PM *To:* Adrian Brock; Bill Decoste; Bill Burke; Gavin King; jboss-development@lists.sourceforge.net; Kabir Khan; QA; Ruel Loehr; Scott M Stark; Thomas Diesler *Subject:* ejb3-4.0-testsuite Build Failed *Importance:* High View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060130193339 *BUILD FAILED* *Ant Error Message: */services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details. *Date of build: *01/30/2006 19:33:39 *Time to build: *37 minutes 18 seconds *Last changed: *12/31/2005 16:46:08 *Last log entry: *call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false --- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: ejb3-4.0-testsuite Build Failed
The class that is not being found is within jbossas-remoting.jar. This is part of JBossAS code base and not remoting. Only way this would be called to be loaded is if was configured to use the JBossAS security domain via configuration. So am guessing the jar was excluded from the build? Ryan Campbell wrote: The ejb3-ssl-advanced test server is broken: 2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/services/cruisecontrol/checkout/ejb3-4.0-testsuite/build/output/jboss-4.0.4RC1/server/ejb3-ssl-advanced/deploy/ejb3.deployer/ org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) at org.jboss.system.ServiceController.install(ServiceController.java:226) *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *Sent:* Monday, January 30, 2006 7:12 PM *To:* Adrian Brock; Bill Decoste; Bill Burke; Gavin King; jboss-development@lists.sourceforge.net; Kabir Khan; QA; Ruel Loehr; Scott M Stark; Thomas Diesler *Subject:* ejb3-4.0-testsuite Build Failed *Importance:* High View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060130193339 *BUILD FAILED* *Ant Error Message: */services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details. *Date of build: *01/30/2006 19:33:39 *Time to build: *37 minutes 18 seconds *Last changed: *12/31/2005 16:46:08 *Last log entry: *call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false --- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-cache build.136 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache?log=log20060131141912Lbuild.136 BUILD COMPLETE - build.136Date of build: 01/31/2006 14:19:12Time to build: 16 secondsLast changed: 01/31/2006 13:58:17Last log entry: Removed JDBCCacheLoaderMySQLDSTestCase because it requires a jdbc driver to be in the lib directory and that will cause the build to fail. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 11)1.2deletedhmeshatests/functional/org/jboss/cache/loader/JDBCCacheLoaderMySQLDSTestCase.javaRemoved JDBCCacheLoaderMySQLDSTestCase because it requires a jdbc driver to be in the lib directory and that will cause the build to fail.1.61modifiedmsurtani/build.xmlFixed JBCACHE-3851.60modifiedmsurtani/build.xmlFixed JBCACHE-3841.4modifiedhmeshaetc/cache-jdbc.propertiesAdded Derby config to run test cases as part of the test suite.1.1addedhmeshatests/functional/org/jboss/cache/loader/JDBCCacheLoaderDerbyDSTestCase.javaChanged JDBCCacheLoaderTest to run with Derby as part of the test suite. Added JDBCCacheLoaderxxxDSTestCase to run to run manually to test the use of DataSource object1.1addedhmeshatests/functional/org/jboss/cache/loader/JDBCCacheLoaderMySQLDSTestCase.javaChanged JDBCCacheLoaderTest to run with Derby as part of the test suite. Added JDBCCacheLoaderxxxDSTestCase to run to run manually to test the use of DataSource object1.5modifiedhmeshatests/functional/org/jboss/cache/loader/JDBCCacheLoaderTest.javaChanged JDBCCacheLoaderTest to run with Derby as part of the test suite. Added JDBCCacheLoaderxxxDSTestCase to run to run manually to test the use of DataSource object1.8modifiedhmeshasrc/org/jboss/cache/loader/JDBCCacheLoader.javaJBCACHE-346 changed prepare() to only prepare connection if the connection factory of type NonManagedConnectionFactory1.1addedhmeshalib/derby.jarDerby embedded engine release 10.1.2.1 to run JDBCCacheLoader test cases1.25modifiedmsurtanisrc/org/jboss/cache/interceptors/TxInterceptor.javafixed problem with swapping ongoing txs1.10modifiedmsurtanitests/functional/org/jboss/cache/optimistic/TxInterceptorTest.javaAdded stack trace print
[JBoss-dev] jboss-cache Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache?log=log20060131133622 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:41: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 01/31/2006 13:36:22Time to build: 14 secondsLast changed: 01/31/2006 13:29:22Last log entry: Changed JDBCCacheLoaderTest to run with Derby as part of the test suite. Added JDBCCacheLoaderxxxDSTestCase to run to run manually to test the use of DataSource object Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 7)1.1addedhmeshatests/functional/org/jboss/cache/loader/JDBCCacheLoaderDerbyDSTestCase.javaChanged JDBCCacheLoaderTest to run with Derby as part of the test suite. Added JDBCCacheLoaderxxxDSTestCase to run to run manually to test the use of DataSource object1.1addedhmeshatests/functional/org/jboss/cache/loader/JDBCCacheLoaderMySQLDSTestCase.javaChanged JDBCCacheLoaderTest to run with Derby as part of the test suite. Added JDBCCacheLoaderxxxDSTestCase to run to run manually to test the use of DataSource object1.5modifiedhmeshatests/functional/org/jboss/cache/loader/JDBCCacheLoaderTest.javaChanged JDBCCacheLoaderTest to run with Derby as part of the test suite. Added JDBCCacheLoaderxxxDSTestCase to run to run manually to test the use of DataSource object1.8modifiedhmeshasrc/org/jboss/cache/loader/JDBCCacheLoader.javaJBCACHE-346 changed prepare() to only prepare connection if the connection factory of type NonManagedConnectionFactory1.1addedhmeshalib/derby.jarDerby embedded engine release 10.1.2.1 to run JDBCCacheLoader test cases1.25modifiedmsurtanisrc/org/jboss/cache/interceptors/TxInterceptor.javafixed problem with swapping ongoing txs1.10modifiedmsurtanitests/functional/org/jboss/cache/optimistic/TxInterceptorTest.javaAdded stack trace print
[JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
The ejb3-ssl-advanced test server is broken: 2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/services/cruisecontrol/checkout/ejb3-4.0-testsuite/build/output/jboss-4.0.4RC1/server/ejb3-ssl-advanced/deploy/ejb3.deployer/org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.remoting.security.domain.DomainServerSocketFactoryService) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) at org.jboss.system.ServiceController.install(ServiceController.java:226) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 7:12 PM To: Adrian Brock; Bill Decoste; Bill Burke; Gavin King; jboss-development@lists.sourceforge.net; Kabir Khan; QA; Ruel Loehr; Scott M Stark; Thomas Diesler Subject: ejb3-4.0-testsuite Build Failed Importance: High View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060130193339 BUILD FAILED Ant Error Message: /services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details. Date of build: 01/30/2006 19:33:39 Time to build: 37 minutes 18 seconds Last changed: 12/31/2005 16:46:08 Last log entry: call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false
[JBoss-dev] jboss-head-jdk-matrix build.1323 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060131102532Lbuild.1323 BUILD COMPLETE - build.1323Date of build: 01/31/2006 10:25:32Time to build: 30 minutes 17 secondsLast changed: 01/31/2006 09:47:24Last log entry: Remove a stray System.out Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 263)1.1addedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/InjectionTestCase.java[JBMICROCONT-64] - Add missing test for inject element.1.3modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/XMLTestSuite.java[JBMICROCONT-64] - Add missing test for inject element.1.89modifiedtdieslerwebservice/build.xmlexclude ther server webservice meta data1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/AnnotationTestCase.java[JBMICROCONT-65] - Add validation to make sure the and makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/AttributeTestCase.java[JBMICROCONT-65] - Add validation to make sure the and makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/InstallTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.6modifiedadriankernel/src/resources/schema/bean-deployer_2_0.xsd[JBMICROCONT-65] - Add validation to make sure the makes sense.1.88modifiedtdieslerwebservice/build.xmlFix: JBWS-635Retrotranslate WS-Security1.2modifiedtdieslerwebservice/src/main/org/jboss/ws/utils/XMLPredefinedEntityReferenceResolver.java[retrotranslator] Method not found: java.lang.StringBuffer java.lang.StringBuffer.append(java.lang.CharSequence)1.1addedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/SupplyBadNoValue.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/DemandTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/DependencyTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/SupplyTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/PropertyTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/FactoryTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.51modifiedtdieslertools/etc/buildmagic/modules.entRemove 1.3modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/ConstructorTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/DeploymentTestCase.java[JBMICROCONT-64] - Add missing test for deployment with classloader.1.3modifiedtdieslertestsuite/src/resources/webservice/jbws643/WEB-INF/jaxrpc-mapping.xml The yahoo-research.wsdl contains invalid element names. The content of the name attribute must be an xs:NCName Replaced ns1:Market with ns1Market1.3modifiedtdieslertestsuite/src/resources/webservice/jbws643/WEB-INF/wsdl/yahoo-research.wsdl The yahoo-research.wsdl contains invalid element names. The content of the name attribute must be an xs:NCName Replaced ns1:Market with ns1Market1.3modifiedtdieslertestsuite/src/resources/webservice/jbws643/config.xml The yahoo-research.wsdl contains invalid element names. The content of the name attribute must be an xs:NCName Replaced ns1:Market with ns1Market1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/ClassLoaderTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/BeanFactoryTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.4modifiedaloubyanskytestsuite/src/main/org/jboss/test/xml/WildcardUnresolvedElementsUnitTestCase.javaproper DOM serialization1.6modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/validation/JaxrpcMappingValidator.javaRollback type change for xml-element-name, xml-attribute-name1.13modifiedtdieslerwebservice/src/main/org/jboss/ws/tools/helpers/MappingFileGeneratorHelper.javaRollback type change for xml-element-name, xml-attribute-name1.26modifiedtdieslerserver/src/main/org/jboss/webservice/metadata/jaxrpcmapping/JavaWsdlMappingFactory.javaRollback type change for xml-element-name, xml-attribute-name1.8modifiedtdieslerserver/src/main/org/jboss/webservice/metadata/
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060131083804 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:216: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 01/31/2006 08:38:04Time to build: 29 minutes 52 secondsLast changed: 01/31/2006 08:27:09Last log entry: [JBMICROCONT-65] - Add validation to make sure the makes sense. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 212)1.3modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/ConstructorTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/DeploymentTestCase.java[JBMICROCONT-64] - Add missing test for deployment with classloader.1.3modifiedtdieslertestsuite/src/resources/webservice/jbws643/WEB-INF/jaxrpc-mapping.xml The yahoo-research.wsdl contains invalid element names. The content of the name attribute must be an xs:NCName Replaced ns1:Market with ns1Market1.3modifiedtdieslertestsuite/src/resources/webservice/jbws643/WEB-INF/wsdl/yahoo-research.wsdl The yahoo-research.wsdl contains invalid element names. The content of the name attribute must be an xs:NCName Replaced ns1:Market with ns1Market1.3modifiedtdieslertestsuite/src/resources/webservice/jbws643/config.xml The yahoo-research.wsdl contains invalid element names. The content of the name attribute must be an xs:NCName Replaced ns1:Market with ns1Market1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/ClassLoaderTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/BeanFactoryTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.4modifiedaloubyanskytestsuite/src/main/org/jboss/test/xml/WildcardUnresolvedElementsUnitTestCase.javaproper DOM serialization1.6modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/validation/JaxrpcMappingValidator.javaRollback type change for xml-element-name, xml-attribute-name1.13modifiedtdieslerwebservice/src/main/org/jboss/ws/tools/helpers/MappingFileGeneratorHelper.javaRollback type change for xml-element-name, xml-attribute-name1.26modifiedtdieslerserver/src/main/org/jboss/webservice/metadata/jaxrpcmapping/JavaWsdlMappingFactory.javaRollback type change for xml-element-name, xml-attribute-name1.8modifiedtdieslerserver/src/main/org/jboss/webservice/metadata/jaxrpcmapping/VariableMapping.javaRollback type change for xml-element-name, xml-attribute-name1.3modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/AbstractXMLTest.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/BeanTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/deployment/xml/test/ConstructorTestCase.java[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/ParameterWithValue.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/ParameterWithWildcard.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/Property.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/PropertyWithAnnotation.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/PropertyWithAnnotations.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/PropertyWithArray.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/PropertyWithClass.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/PropertyWithCollection.xml[JBMICROCONT-65] - Add validation to make sure the makes sense.1.2modifiedadriankernel/src/resources/org/jboss/test/kernel/deployment/xml/test/PropertyWithInjection.xml[JBMICROCONT-65] - Add validation to mak
Re: [JBoss-dev] EJB3StandaloneBootstrap implementation
I think going the E-EJB3 route to start is a good idea as it will force
us to implement bare-bones implementations that do not have the idea of
a classloader or j2ee deployment schemes within them. Once we have
e-ejb3 (really e-jboss) in place, it will force us to be careful about
adding things like classloading and j2ee packaging as to not break or
bloat e-jboss.
The way I envision it working is basically how it works with current kernel
* This shit must be REALLY FAST. Remember, we're using it with junit tests.
* embedded-jboss-beans.xml configures a MainDeployer, BeanDeployer,
AOPDeployer, EJB3Deployer, (etc.) and basic services like TM, JNDI, etc.
* EJB3StandaloneBootstrap still exists and has three methods:
- boot(): This loads embeddded-jboss-beans.xml
- scanClasspath(). The scans the entire classpath for deployments and
calls MainDeployer.deploy() for each jar/directory/config file it finds.
calling MainDeployer.deploy(URL).
- scanClasspath(String) comma delimited list of files that should be
deployed. These files are in the classpath (java.class.path)
- deployResource(String) deploys an individual Classpath resource.
("ejb3-interceptors-aop.xml") by calling MainDeployer.deploy(URL)
My second thought is that Scanners should be responsible for creating
the DeploymentUnit rather than the main deployer. This will allow the
scanner to add metadata about the deployment or to work with different
"filesystems", like a database or profile. For instance, I envision a
cluster/ directory where any deployment put in it that supports
clustering will be clustered. The scanner could also be configured for
default security domain. For this to work, the scanner needs to attach
metadata to the deploymentunit. Since the MainDeployer will not be
responsible for creating the deployment unit, this will make it easier.
If you look at the EJB3 code, you will also find that I have done a
kernel abstraction so that the EJB3 deployer and codebase does not have
to be concerned about whether you are deployment to JBoss4 or MC. If we
do the new deployers right, the new architecture can be used as an
abstraction for projects that need to work in both JBoss4 and MC.
Man, I want to help prototype this stuff. I was about to do it for the
last EJB3 release, but I ran out of time. I'll want to jump in and help
after I finish the EJB3 book.
Later,
Bill
Scott M Stark wrote:
I browsed through the EJB3StandaloneBootstrap and embedded ejb3 usage of the mc
to see what extent the mc is being used. In browsing through the
conf/embedded-jboss-beans.xml for the mc config, I did not see anything related
to the ejb3 container or aop layer to load the conf/ejb3-interceptors-aop.xml.
The embedded ejb3 docs show this prototype code block for setting up embedded
ejb3:
EJB3StandaloneBootstrap.boot(null);
// initialize JBoss MQ core services
EJB3StandaloneBootstrap.deployXmlResource("jboss-jms-beans.xml");
// initialize configured test queue and topic
EJB3StandaloneBootstrap.deployXmlResource("testjms.xml");
// scan classpath for ejbs and MDBs
EJB3StandaloneBootstrap.scanClasspath();
So a lot of configuration is being done outside of the mc
embedded-jboss-beans.xml. I guess this is due to missing implementation details
of the mc such as the vfs, virtual deployment impl, and class loader
configuration. I have been thinking about how to push the mc forward by getting
it more into jboss5, but maybe using the embedded ejb3 setup would be a less
disruptive way to drive these features to completion.
Does it make sense to organize the next set of mc releases around getting the
embedded ejb3 completely configured from a prototype standalone mc bootstrap
(http://docs.jboss.org/nightly/microkernel/docs/gettingstarted/en/html/standalone.html)
which loads a more complete embedded-ejb3-beans.xml that includes the ejb3
container and aop configuration?
--
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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[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=log20060131072127 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: 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: 01/31/2006 07:21:27Time to build: 72 minutes 19 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (281) Total Errors and Failures: (5)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.transport.multiplex.BasicServerSocketTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization) Modifications since last build: (first 50 of 2026)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/ComplexObject.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServerImpl.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TransporterTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/SSLInvokerConstants.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.8modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleClient.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.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.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.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.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 w
[JBoss-dev] EJB3StandaloneBootstrap implementation
I browsed through the EJB3StandaloneBootstrap and embedded ejb3 usage of the mc to see what extent the mc is being used. In browsing through the conf/embedded-jboss-beans.xml for the mc config, I did not see anything related to the ejb3 container or aop layer to load the conf/ejb3-interceptors-aop.xml. The embedded ejb3 docs show this prototype code block for setting up embedded ejb3: EJB3StandaloneBootstrap.boot(null); // initialize JBoss MQ core services EJB3StandaloneBootstrap.deployXmlResource("jboss-jms-beans.xml"); // initialize configured test queue and topic EJB3StandaloneBootstrap.deployXmlResource("testjms.xml"); // scan classpath for ejbs and MDBs EJB3StandaloneBootstrap.scanClasspath(); So a lot of configuration is being done outside of the mc embedded-jboss-beans.xml. I guess this is due to missing implementation details of the mc such as the vfs, virtual deployment impl, and class loader configuration. I have been thinking about how to push the mc forward by getting it more into jboss5, but maybe using the embedded ejb3 setup would be a less disruptive way to drive these features to completion. Does it make sense to organize the next set of mc releases around getting the embedded ejb3 completely configured from a prototype standalone mc bootstrap (http://docs.jboss.org/nightly/microkernel/docs/gettingstarted/en/html/standalone.html) which loads a more complete embedded-ejb3-beans.xml that includes the ejb3 container and aop configuration?
[JBoss-dev] JBAS-2745 - Option C Broken
Yes, I wrote this test to stop people breaking it. That doesn't mean I am going to fix it when people do! My new years resolution is to stop wasting time cleaning up after the zoo animals. :-) Looking at CVS, Ben Wang was the last person to modify the instance cache in 4.0.x This is BMP so that rules out a change in the CMP engine. If you can't figure it out, then I will help! -- Adrian Brock Chief Scientist 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] microcontainer-head-testsuite build.56 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060131023917Lbuild.56 BUILD COMPLETE - build.56Date of build: 01/31/2006 02:39:17Time to build: 31 minutes 9 secondsLast changed: 01/30/2006 11:09:35Last log entry: Make a start on some raw xml for the microcontainer tests,like the javabean schema tests I wrote. Unit Tests: (332) Total Errors and Failures: (0)All Tests Passed Modifications since last build: (first 50 of 111)1.4modifiedadriansrc/resources/schema/bean-deployer_2_0.xsdMake a start on some raw xml for the microcontainer tests,like the javabean schema tests I wrote.1.7modifiedadriansrc/tests/org/jboss/test/kernel/KernelTestSuite.javaMake a start on some raw xml for the microcontainer tests,like the javabean schema tests I wrote.1.4modifiedadriansrc/main/org/jboss/kernel/spi/registry/KernelRegistryEntry.javaSourcecode tidyup1.4modifiedadriansrc/main/org/jboss/kernel/spi/registry/KernelRegistryEntryAlreadyRegisteredException.javaSourcecode tidyup1.4modifiedadriansrc/main/org/jboss/kernel/spi/registry/KernelRegistryEntryNotFoundException.javaSourcecode tidyup1.3deletedadriansrc/tests/org/jboss/test/classloading/test/ClassLoadingTestSuite.java[JBMICROCONT-63] - Remove the prototypical classloader impl1.4deletedadriansrc/tests/org/jboss/test/classloading/test/DomainTestCase.java[JBMICROCONT-63] - Remove the prototypical classloader impl1.4deletedadriansrc/main/org/jboss/util/ClassLoading.java[JBMICROCONT-63] - Remove the prototypical classloader impl1.2deletedadriansrc/main/org/jboss/util/package.html[JBMICROCONT-63] - Remove the prototypical classloader impl1.5modifiedadriansrc/tests/org/jboss/test/KernelAllTestSuite.java[JBMICROCONT-63] - Remove the prototypical classloader impl1.3deletedadriansrc/tests/org/jboss/test/classloading/support/ClassLoaderStats.java[JBMICROCONT-63] - Remove the prototypical classloader impl1.3deletedadriansrc/tests/org/jboss/test/classloading/support/SimpleClassLoader.java[JBMICROCONT-63] - Remove the prototypical classloader impl1.3modifiedadriansrc/resources/schema/bean-deployer_2_0.xsd[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.1addedadriansrc/tests/org/jboss/test/kernel/deployment/support/WildcardClassLoader.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.3modifiedadriansrc/main/org/jboss/util/ClassLoading.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.1addedadriansrc/resources/org/jboss/test/kernel/deployment/test/WildcardClassLoaderTestCase_NotAutomatic.xml[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.3modifiedadriansrc/resources/xml-test/org/jboss/test/kernel/config/test/testSimpleInstantiateFromFactoryWithIntegerParameter.xml[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.1addedadriansrc/tests/org/jboss/test/kernel/config/support/MyObject.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.6modifiedadriansrc/tests/org/jboss/test/kernel/config/test/ArrayTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.5modifiedadriansrc/tests/org/jboss/test/kernel/config/test/ArrayXMLTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.8modifiedadriansrc/tests/org/jboss/test/kernel/config/test/CollectionTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.7modifiedadriansrc/tests/org/jboss/test/kernel/config/test/CollectionXMLTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.8modifiedadriansrc/tests/org/jboss/test/kernel/config/test/FactoryXMLTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.5modifiedadriansrc/tests/org/jboss/test/kernel/config/test/ListTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.5modifiedadriansrc/tests/org/jboss/test/kernel/config/test/ListXMLTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard processing in the Microcontainer xml.1.5modifiedadriansrc/tests/org/jboss/test/kernel/config/test/MapTestCase.java[JBMICROCONT-34] - Use the WildcardHandler and complete testsfor any/wildcard process
[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=log20060131031155 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:278: 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: 01/31/2006 03:11:55Time to build: 2 minutes 15 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 build: (first 50 of 2315)1.24modifiedjulientools/etc/buildfragments/libraries.entbranches: 1.24.2; 1.24.4;update 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.7modifiedjulienthirdparty/jboss-j2ee/README.txtupdates jboss thirdparty to 4.0.3SP1fix the redeployment issue of jboss portal related to the dynamic proxy class loading issue1.6modifiedmholznertools/etc/buildfragments/modules.entadded security module1.22modifiedjulientools/etc/buildfragments/libraries.entadded the myfaces entry in the libraries1.3modifiedjulientools/etc/tagdiff.xsl- added dispatch() method on Invocation that delivers the invocation to the target- made the interceptor service citizen so we can apply on them management and dependency management- removed the relationship between the Server and the RequestController- removed the PortletDispatcherInterceptor and delegate to the portlet container the way the API call must be delivered to the target portlet- removed the ExecuteCommandInterceptor that is not necessary, same for the ControllerInterceptor1.5modifiedpalbertools/etc/buildfragm
