RE: [JBoss-dev] 4.0.4
Just do a 4.0.5 soon after than. I don't want to push the 4.0.4.GA as Dimitris said people have been waiting on it for a while. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Monday, March 20, 2006 6:54 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] 4.0.4 It would be cool if we could push GA a bit further after CR2. I would like to do a big push for EJB3 final draft(and my book) compliance with 4.0.4 and need more than 2 weeks as I'm on vacation for 10 days in between. Scott M Stark wrote: > Ok. We want the 4.0.4.CR2 out this week and the GA two weeks latter. > > >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On >>Behalf Of Steve Ebersole >>Sent: Monday, March 20, 2006 2:17 PM >>To: jboss-development@lists.sourceforge.net >>Subject: RE: [JBoss-dev] 4.0.4 >> >>So provided we do not cause issues with portal, I say we go >>with a 3.2 final. Specific reasons: >>(1) Less issues with the version differences between AS and EJB3 >>(2) JBossCache optimistic locking support (only in 3.2) >>(3) Javassist support (only in 3.2) >>(4) Some performance enhancements relating to aggressive >>connection releasing on JBoss (although this is in 3.1.3 also). >> >>The only other real difference between 3.1.3 and 3.2 is the >>non-transactional stuff. >> >>The installer/build option seems a bit late in the game >>considering a release next week (#1). > > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060321002641 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2006 00:26:41Time to build: 50 minutes 53 seconds Unit Tests: (1851) Total Errors and Failures: (2)testFederatedorg.jboss.test.jbossnet.external.ExternalUnitTestCasetestFederatedorg.jboss.test.jbossnet.external.RedeployExternalUnitTestCase Modifications since last build: (first 50 of 0)
[JBoss-dev] jboss-cache-testsuite build.44 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060320223436Lbuild.44 BUILD COMPLETE - build.44Date of build: 03/20/2006 22:34:36Time to build: 35 minutes 5 secondsLast changed: 03/20/2006 12:35:16Last log entry: updated release notes Unit Tests: (1367) Total Errors and Failures: (0)All Tests Passed Modifications since last build: (first 50 of 61)1.4modifiedbstansberrytests/functional/org/jboss/cache/GlobalTransactionTest.javaAdd a test that equals() handles null properly1.6modifiedbstansberrytests/functional/org/jboss/cache/FqnTest.javaAdd a test that equals() handles null and other types properly1.12modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.13modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.14modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.4modifiedbwangtests/scripts/bench.txtupd1.4modifiedbwangsrc/org/jboss/cache/eviction/BaseEvictionAlgorithm.javaChanged the log output level from warn to debug in removeQueue1.9modifiedmsurtanisrc/org/jboss/cache/Version.javaUpdated version1.4modifiedmsurtanisrc/org/jboss/cache/aop/util/AopUtil.javaJBCACHE-5021.5modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/VersionedTestBase.javaDon't leak ref to 'this' to Thread from CacheUser c'tor1.11modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransferAopTestBase.javaDon't leak ref to 'this' to Thread from CacheUser c'tor1.2modifiedbwangtests/scripts/benchmark.shClean up1.15modifiedbwangtests/perf/org/jboss/cache/Server.javaOutput average as well1.16modifiedbwangtests/perf/org/jboss/cache/Server.javaadded more stats1.5modifiedbwangtests/scripts/bench.txtupd1.2modifiedbwangtests/scripts/readme.txtupd1.2modifiedbwangtests/scripts/bench.xmlupdated xml1.17modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.3modifiedbwangtests/scripts/benchmark.shupd1.132modifiedbwangsrc/org/jboss/cache/TreeCache.javaAdded commented out section forJGroups jmx1.3modifiedbwangtests/scripts/readme.txtupd1.18modifiedbwangtests/perf/org/jboss/cache/Server.javachecked members than specified now1.133modifiedbwangsrc/org/jboss/cache/TreeCache.javaCommented out jgroups 2.3 features1.6modifiedbwangtests/scripts/bench.txtadded random sleep1.3modifiedbwangtests/scripts/bench.xmladded random sleep1.19modifiedbwangtests/perf/org/jboss/cache/Server.javaadded random sleep1.4modifiedgenmansrc/org/jboss/cache/eviction/EvictionTimerTask.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.7modifiedgenmansrc/org/jboss/cache/eviction/Region.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.12modifiedgenmansrc/org/jboss/cache/interceptors/CacheMgmtInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.8modifiedgenmansrc/org/jboss/cache/interceptors/CreateIfNotExistsInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.21modifiedgenmansrc/org/jboss/cache/interceptors/OptimisticValidatorInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.17modifiedgenmansrc/org/jboss/cache/interceptors/PassivationInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.35modifiedgenmansrc/org/jboss/cache/interceptors/TxInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.10modifiedgenmansrc/org/jboss/cache/loader/AsyncCacheLoader.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.9modifiedgenmansrc/org/jboss/cache/loader/FileCacheLoader.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.7modifiedgenmansrc/org/jboss/cache/loader/rmi/RemoteTreeCacheImpl.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.13modifiedgenmansrc/org/jboss/cache/loader/tcp/TcpCacheServer.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.2modifiedgenmansrc/org/jboss/cache/optimistic/DefaultDataVersion.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.8modifiedgenmansrc/org/jboss/cache/eviction/Region.javaJBCACHE-484 - Fix wrong type conversion1.10modifiedmsurtanisrc/org/jboss/cache/Version.javaUpdated version1.14modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/StateTransferTestBase.javaPut newly created cache in the map before starting, so if it fails in start it can still be destroyed during test cleanup1.12modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransferAopTestBase.javaPut newly created cache in the map before starting, so if it fails in start it can still be destroyed during test c
[JBoss-dev] ejb3 should be ready for 4.0.4CR2
let me know if any issues come up. The backmerge has been completed. -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 4.0.4
It would be cool if we could push GA a bit further after CR2. I would like to do a big push for EJB3 final draft(and my book) compliance with 4.0.4 and need more than 2 weeks as I'm on vacation for 10 days in between. Scott M Stark wrote: Ok. We want the 4.0.4.CR2 out this week and the GA two weeks latter. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: Monday, March 20, 2006 2:17 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 So provided we do not cause issues with portal, I say we go with a 3.2 final. Specific reasons: (1) Less issues with the version differences between AS and EJB3 (2) JBossCache optimistic locking support (only in 3.2) (3) Javassist support (only in 3.2) (4) Some performance enhancements relating to aggressive connection releasing on JBoss (although this is in 3.1.3 also). The only other real difference between 3.1.3 and 3.2 is the non-transactional stuff. The installer/build option seems a bit late in the game considering a release next week (#1). --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060320181206 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build: 03/20/2006 18:12:06Time to build: 99 minutes 54 secondsLast changed: 03/20/2006 17:39:41Last log entry: backmerge Unit Tests: (2985) Total Errors and Failures: (59)testENCServletViaInvokerorg.jboss.test.jacc.test.WebIntegrationUnitTestCase(JACC+SecurityMgr)unknownorg.jboss.test.perf.test.PerfStressTestCasetestCreateRequiredCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiredCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiredCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiredCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestTimerRestoredForSessionBeanorg.jboss.test.txtimer.test.PersistentTimerTestCasetestNoExceptionorg.jboss.test.webservice.jbws251.JBWS251TestCasetestGetArrayorg.jboss.test.webservice.jbws626.JBWS626TestCasetestEndpointorg.jboss.test.webservice.jbws718.JBWS718TestCasetestEchoStringorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoIntegerorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoIntorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoLongorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoShortorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDecimalorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoFloatorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDoubleorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoBooleanorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoByteorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoQNameorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDateTimeCalendarorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDateTimeDateorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDateCalendarorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDateDateorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoBase64Binaryorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoHexBinaryorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoBeanorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoBeanNullPropertiesorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoStringArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoIntegerArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoIntArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoLongArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoShortArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDecimalArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoFloatArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDoubleArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoBooleanArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoByteArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoQNameArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestEchoDateTimeArrayorg.jboss.test.webservice.marshalltest.MarshallRpcLiteralTestCasetestWithTransportOptionsorg.jboss.test.webservice.secure.SimpleClientSecureTestCasetestWithTransportOptionsorg
RE: [JBoss-dev] 4.0.4
Ok. We want the 4.0.4.CR2 out this week and the GA two weeks latter. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: Monday, March 20, 2006 2:17 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > So provided we do not cause issues with portal, I say we go > with a 3.2 final. Specific reasons: > (1) Less issues with the version differences between AS and EJB3 > (2) JBossCache optimistic locking support (only in 3.2) > (3) Javassist support (only in 3.2) > (4) Some performance enhancements relating to aggressive > connection releasing on JBoss (although this is in 3.1.3 also). > > The only other real difference between 3.1.3 and 3.2 is the > non-transactional stuff. > > The installer/build option seems a bit late in the game > considering a release next week (#1). --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Struts error with current Tomcat version
Looks like there is already a similar issue logged against jboss-head… http://jira.jboss.org/jira/browse/JBAS-2072 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clebert Suconic Sent: Monday, March 20, 2006 5:06 PM To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] Struts error with current Tomcat version I’m seeing this error when starting JBossProfiler with JBoss-4.0 fresh install. It works with any other previous version. Any idea on what changed? (did we change any classLoader op here?) 18:01:48,986 ERROR [MainDeployer] Could not create deployment: file:/home/csuconic/jboss-4.0.x/build/output/jboss-4.0.4.CR2/server/all/deploy/jboss-profiler.war/ org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.struts.action.ActionServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159) at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:99) at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190) at $Proxy39.create(Unknown Source) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190) at $Proxy8.deploy(Unknown Source)
[JBoss-dev] Struts error with current Tomcat version
I’m seeing this error when starting JBossProfiler with JBoss-4.0 fresh install. It works with any other previous version. Any idea on what changed? (did we change any classLoader op here?) 18:01:48,986 ERROR [MainDeployer] Could not create deployment: file:/home/csuconic/jboss-4.0.x/build/output/jboss-4.0.4.CR2/server/all/deploy/jboss-profiler.war/ org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.struts.action.ActionServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159) at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:99) at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190) at $Proxy39.create(Unknown Source) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190) at $Proxy8.deploy(Unknown Source)
RE: [JBoss-dev] 4.0.4
So provided we do not cause issues with portal, I say we go with a 3.2 final. Specific reasons: (1) Less issues with the version differences between AS and EJB3 (2) JBossCache optimistic locking support (only in 3.2) (3) Javassist support (only in 3.2) (4) Some performance enhancements relating to aggressive connection releasing on JBoss (although this is in 3.1.3 also). The only other real difference between 3.1.3 and 3.2 is the non-transactional stuff. The installer/build option seems a bit late in the game considering a release next week (#1). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: Monday, March 20, 2006 3:19 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 Well the other piece to the puzzle is the differences between that Hibernate version you mentioned and 3.1.3. If the differences there are drastic enough, then I see even more of an argument to move to 3.2 for the AS bundle. Another thing to consider is portal (which AFAIK is still the only other "bundled" user of the deployer stuff). Specifically, will the non-transactional access changes cause them problems? Julien; Roy? I'll go back and analyze the changes made since the bundled 3.1rc2jboss. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Monday, March 20, 2006 2:37 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 Your input is a large factor as well since I don't really know how different the hibernate 3.1rc2jboss version that was shipped with 4.0.3SP1 and the current version needed for ejb3. The first question, is what do you want bundled in terms of stability/support? If this is not what is needed for ejb3 then we need to decouple the jbossas build from the ejb3 hibernate dependency and deal with ejb3 as a separate component integrated into the installer with a separate hibernate dependency that replaces/differs from the default/all version. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: Monday, March 20, 2006 12:11 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > It is up to y'all. I am fine with cutting a 3.2 final and > then continuing HEAD development as 3.3. But the 3.2 release > introduced some fairly different behavior in terms of > non-transactional access more in-line with what is defined in > the EJB3 spec. These changes are stricter than what > Hibernate had previously allowed in these scenarios. > I think everyone agrees that these are better behaviors, but > certainly there are probably some users relying on the old > "bad behaviors". > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Monday, March 20, 2006 1:39 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > It seems like ejb3 should only be brining in a latter > hibernate dependency via the installer and a custom build for > testing. The default/all should not be bumped up to track > ejb3 issues to an untested hibernate release. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Dimitris Andreadis > > Sent: Monday, March 20, 2006 10:54 AM > > To: jboss-development@lists.sourceforge.net > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > Exactly. Something stable, that can be tested with > 4.0.4.CR2 (which is > > delayed until Friday 24th or Monday 27th max), that satisfies Bill, > > and won't require an immediate 4.0.4.SP1 release for fixes :) > > > > There are many-many people waiting for 4.0.4 for quite some > time and > > we are already delayed, so please try to get a stable release out. > > Users won't like at all running jboss > > 4.0.4 on a hibernate alpha. > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Bill Burke > > > Sent: 20 March, 2006 20:45 > > > To: jboss-development@lists.sourceforge.net > > > Subject: Re: [JBoss-dev] 4.0.4 > > > > > > we just need something stable for hibernate in 4.0.4 GA. > > > > > > Steve Ebersole wrote: > > > > Well, its *possible* to have "a final" release whenever > I want ;) > > > > > > > > But at a bare minimum there is one more feature that EJB3 > > > will require > > > > which still needs to be implemented; and it is an ugly one. > > > I need to > > > > release 3.1.3 today/tomorrow (this needs to be done for reasons > > > > extraneous to this discussion). I can then come back to > > > work on this > > > > particular feature. All that I can get done by next week. > > > > > > > > But that is not all I had initially targeted for 3.2 final > > > (nor even > > > > beta). And I do not like leaving off planned features just > > > to get to > > > > a > > > >
RE: [JBoss-dev] 4.0.4
Well the other piece to the puzzle is the differences between that Hibernate version you mentioned and 3.1.3. If the differences there are drastic enough, then I see even more of an argument to move to 3.2 for the AS bundle. Another thing to consider is portal (which AFAIK is still the only other "bundled" user of the deployer stuff). Specifically, will the non-transactional access changes cause them problems? Julien; Roy? I'll go back and analyze the changes made since the bundled 3.1rc2jboss. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Monday, March 20, 2006 2:37 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 Your input is a large factor as well since I don't really know how different the hibernate 3.1rc2jboss version that was shipped with 4.0.3SP1 and the current version needed for ejb3. The first question, is what do you want bundled in terms of stability/support? If this is not what is needed for ejb3 then we need to decouple the jbossas build from the ejb3 hibernate dependency and deal with ejb3 as a separate component integrated into the installer with a separate hibernate dependency that replaces/differs from the default/all version. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: Monday, March 20, 2006 12:11 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > It is up to y'all. I am fine with cutting a 3.2 final and > then continuing HEAD development as 3.3. But the 3.2 release > introduced some fairly different behavior in terms of > non-transactional access more in-line with what is defined in > the EJB3 spec. These changes are stricter than what > Hibernate had previously allowed in these scenarios. > I think everyone agrees that these are better behaviors, but > certainly there are probably some users relying on the old > "bad behaviors". > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Monday, March 20, 2006 1:39 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > It seems like ejb3 should only be brining in a latter > hibernate dependency via the installer and a custom build for > testing. The default/all should not be bumped up to track > ejb3 issues to an untested hibernate release. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Dimitris Andreadis > > Sent: Monday, March 20, 2006 10:54 AM > > To: jboss-development@lists.sourceforge.net > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > Exactly. Something stable, that can be tested with > 4.0.4.CR2 (which is > > delayed until Friday 24th or Monday 27th max), that satisfies Bill, > > and won't require an immediate 4.0.4.SP1 release for fixes :) > > > > There are many-many people waiting for 4.0.4 for quite some > time and > > we are already delayed, so please try to get a stable release out. > > Users won't like at all running jboss > > 4.0.4 on a hibernate alpha. > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Bill Burke > > > Sent: 20 March, 2006 20:45 > > > To: jboss-development@lists.sourceforge.net > > > Subject: Re: [JBoss-dev] 4.0.4 > > > > > > we just need something stable for hibernate in 4.0.4 GA. > > > > > > Steve Ebersole wrote: > > > > Well, its *possible* to have "a final" release whenever > I want ;) > > > > > > > > But at a bare minimum there is one more feature that EJB3 > > > will require > > > > which still needs to be implemented; and it is an ugly one. > > > I need to > > > > release 3.1.3 today/tomorrow (this needs to be done for reasons > > > > extraneous to this discussion). I can then come back to > > > work on this > > > > particular feature. All that I can get done by next week. > > > > > > > > But that is not all I had initially targeted for 3.2 final > > > (nor even > > > > beta). And I do not like leaving off planned features just > > > to get to > > > > a > > > > 3.2 final. > > > > > > > > For me it comes down to whether this is a planned "final > > > release" for > > > > EJB3. If so, I guess I could be persuaded to cut a 3.2 > > final after > > > > implementing the above mentioned feature and then start > > on 3.2.1 or > > > > whatever. > > > > > > > > > > > > -Original Message- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] On > > Behalf Of > > > > Dimitris Andreadis > > > > Sent: Monday, March 20, 2006 11:42 AM > > > > To: jboss-development@lists.sourceforge.net > > > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > > > > > > > I love those dependencies ;) > > > > > > > > Is it possible to have a final next week ? > > > --- > This SF.Ne
RE: [JBoss-dev] 4.0.4
Your input is a large factor as well since I don't really know how different the hibernate 3.1rc2jboss version that was shipped with 4.0.3SP1 and the current version needed for ejb3. The first question, is what do you want bundled in terms of stability/support? If this is not what is needed for ejb3 then we need to decouple the jbossas build from the ejb3 hibernate dependency and deal with ejb3 as a separate component integrated into the installer with a separate hibernate dependency that replaces/differs from the default/all version. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: Monday, March 20, 2006 12:11 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > It is up to y'all. I am fine with cutting a 3.2 final and > then continuing HEAD development as 3.3. But the 3.2 release > introduced some fairly different behavior in terms of > non-transactional access more in-line with what is defined in > the EJB3 spec. These changes are stricter than what > Hibernate had previously allowed in these scenarios. > I think everyone agrees that these are better behaviors, but > certainly there are probably some users relying on the old > "bad behaviors". > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Monday, March 20, 2006 1:39 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > It seems like ejb3 should only be brining in a latter > hibernate dependency via the installer and a custom build for > testing. The default/all should not be bumped up to track > ejb3 issues to an untested hibernate release. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Dimitris Andreadis > > Sent: Monday, March 20, 2006 10:54 AM > > To: jboss-development@lists.sourceforge.net > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > Exactly. Something stable, that can be tested with > 4.0.4.CR2 (which is > > delayed until Friday 24th or Monday 27th max), that satisfies Bill, > > and won't require an immediate 4.0.4.SP1 release for fixes :) > > > > There are many-many people waiting for 4.0.4 for quite some > time and > > we are already delayed, so please try to get a stable release out. > > Users won't like at all running jboss > > 4.0.4 on a hibernate alpha. > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Bill Burke > > > Sent: 20 March, 2006 20:45 > > > To: jboss-development@lists.sourceforge.net > > > Subject: Re: [JBoss-dev] 4.0.4 > > > > > > we just need something stable for hibernate in 4.0.4 GA. > > > > > > Steve Ebersole wrote: > > > > Well, its *possible* to have "a final" release whenever > I want ;) > > > > > > > > But at a bare minimum there is one more feature that EJB3 > > > will require > > > > which still needs to be implemented; and it is an ugly one. > > > I need to > > > > release 3.1.3 today/tomorrow (this needs to be done for reasons > > > > extraneous to this discussion). I can then come back to > > > work on this > > > > particular feature. All that I can get done by next week. > > > > > > > > But that is not all I had initially targeted for 3.2 final > > > (nor even > > > > beta). And I do not like leaving off planned features just > > > to get to > > > > a > > > > 3.2 final. > > > > > > > > For me it comes down to whether this is a planned "final > > > release" for > > > > EJB3. If so, I guess I could be persuaded to cut a 3.2 > > final after > > > > implementing the above mentioned feature and then start > > on 3.2.1 or > > > > whatever. > > > > > > > > > > > > -Original Message- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] On > > Behalf Of > > > > Dimitris Andreadis > > > > Sent: Monday, March 20, 2006 11:42 AM > > > > To: jboss-development@lists.sourceforge.net > > > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > > > > > > > I love those dependencies ;) > > > > > > > > Is it possible to have a final next week ? > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the
[JBoss-dev] RE: jboss-4.0-testsuite Build Completed With Testsuite Errors
I don't see these txtimer errors running the tests by itself. I'll check the run logs to see if there is something obvious. [EMAIL PROTECTED] testsuite]$ run_tests.shant -Dtest=org.jboss.test.txtimer.test.CreateCancelTestCase -Dnojars=t -Djunit.timeout=180 -Djbosstest.cluster.node0=192.168.3.130 -Djbosstest.cluster.node1=192.168.3.120 one-testBuildfile: build.xmlOverriding previous definition of reference to xdoclet.task.classpath one-test: [mkdir] Created dir: C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\output\log [junit] Running org.jboss.test.txtimer.test.CreateCancelTestCase [junit] Tests run: 16, Failures: 0, Errors: 0, Time elapsed: 3.328 sec From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 20, 2006 11:00 AMTo: Bill Burke; Brian Stansberry; jboss-development@lists.sourceforge.net; QA; Scott M StarkSubject: jboss-4.0-testsuite Build Completed With Testsuite ErrorsImportance: High View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060320121502 TESTS FAILED Ant Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures. Date of build: 03/20/2006 12:15:02 Time to build: 99 minutes 55 seconds Last changed: 03/20/2006 12:08:02 Last log entry: JBAS-2744, Use the getServerHost() as the jnp.localAddress value Unit Tests: (2990) Total Errors and Failures: (62) testENCServletViaInvoker org.jboss.test.jacc.test.WebIntegrationUnitTestCase(JACC+SecurityMgr) testCreateRequiredCancelRequired org.jboss.test.txtimer.test.CreateCancelTestCase testCreateRequiredCancelRequiresNew org.jboss.test.txtimer.test.CreateCancelTestCase testCreateRequiredCancelNotSupported org.jboss.test.txtimer.test.CreateCancelTestCase testCreateRequiredCancelNever org.jboss.test.txtimer.test.CreateCancelTestCase testCreateRequiresNewCancelRequired org.jboss.test.txtimer.test.CreateCancelTestCase testCreateRequiresNewCancelRequiresNew org.jboss.test.txtimer.test.CreateCancelTestCase testCreateRequiresNewCancelNotSupported org.jboss.test.txtimer.test.CreateCancelTestCase testCreateRequiresNewCancelNever org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNotSupportedCancelRequired org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNotSupportedCancelRequiresNew org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNotSupportedCancelNotSupported org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNotSupportedCancelNever org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNeverCancelRequired org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNeverCancelRequiresNew org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNeverCancelNotSupported org.jboss.test.txtimer.test.CreateCancelTestCase testCreateNeverCancelNever org.jboss.test.txtimer.test.CreateCancelTestCase testSingleEventDuration org.jboss.test.txtimer.test.PersistenceTestCase testTimerRestoredForScopedSessionBean org.jboss.test.txtimer.test.ScopedPersistentTimerTestCase testEndpoint org.jboss.test.webservice.jbws68.JBWS68TestCase testEchoString org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase testEchoInteger org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase testEchoInt org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase testEchoLong org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase testEchoShort org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase testEchoDecimal org.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCase testEchoFloat org.jboss.test.webservice.marshalltest.Marsh
RE: [JBoss-dev] 4.0.4
It is up to y'all. I am fine with cutting a 3.2 final and then continuing HEAD development as 3.3. But the 3.2 release introduced some fairly different behavior in terms of non-transactional access more in-line with what is defined in the EJB3 spec. These changes are stricter than what Hibernate had previously allowed in these scenarios. I think everyone agrees that these are better behaviors, but certainly there are probably some users relying on the old "bad behaviors". -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Monday, March 20, 2006 1:39 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 It seems like ejb3 should only be brining in a latter hibernate dependency via the installer and a custom build for testing. The default/all should not be bumped up to track ejb3 issues to an untested hibernate release. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dimitris Andreadis > Sent: Monday, March 20, 2006 10:54 AM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > Exactly. Something stable, that can be tested with 4.0.4.CR2 > (which is delayed until Friday 24th or Monday 27th max), that > satisfies Bill, and won't require an immediate 4.0.4.SP1 > release for fixes :) > > There are many-many people waiting for 4.0.4 for quite some > time and we are already delayed, so please try to get a > stable release out. Users won't like at all running jboss > 4.0.4 on a hibernate alpha. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Bill Burke > > Sent: 20 March, 2006 20:45 > > To: jboss-development@lists.sourceforge.net > > Subject: Re: [JBoss-dev] 4.0.4 > > > > we just need something stable for hibernate in 4.0.4 GA. > > > > Steve Ebersole wrote: > > > Well, its *possible* to have "a final" release whenever I want ;) > > > > > > But at a bare minimum there is one more feature that EJB3 > > will require > > > which still needs to be implemented; and it is an ugly one. > > I need to > > > release 3.1.3 today/tomorrow (this needs to be done for reasons > > > extraneous to this discussion). I can then come back to > > work on this > > > particular feature. All that I can get done by next week. > > > > > > But that is not all I had initially targeted for 3.2 final > > (nor even > > > beta). And I do not like leaving off planned features just > > to get to > > > a > > > 3.2 final. > > > > > > For me it comes down to whether this is a planned "final > > release" for > > > EJB3. If so, I guess I could be persuaded to cut a 3.2 > final after > > > implementing the above mentioned feature and then start > on 3.2.1 or > > > whatever. > > > > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Dimitris Andreadis > > > Sent: Monday, March 20, 2006 11:42 AM > > > To: jboss-development@lists.sourceforge.net > > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > > > > I love those dependencies ;) > > > > > > Is it possible to have a final next week ? --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix build.1578 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060320142201Lbuild.1578 BUILD COMPLETE - build.1578Date of build: 03/20/2006 14:22:01Time to build: 28 minutes 2 secondsLast changed: 03/20/2006 13:03:40Last log entry: JBWS-719Enable schema validation on wstools config Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 155)1.103modifiedtdieslerwebservice/test/build.xmlRestore tests-toolsOther secions should be run likeant -Dtest=mysection test1.2modifiedhbraunwebservice/src/resources/jbossws-eventing.war/WEB-INF/wsdl/jbwse.wsdlupdate to new addressing impl.1.5modifiedhbraunwebservice/test/build-interop-artifacts.xmlW3C addressing test suite compliance1.9modifiedhbraunwebservice/test/etc/log4j.xmlW3C addressing test suite compliance1.2modifiedhbraunwebservice/test/java/org/jboss/test/ws/addressing/EndpointReferenceTestCase.javaW3C addressing test suite compliance1.4modifiedhbraunwebservice/test/java/org/jboss/test/ws/addressing/SOAPAddressingPropertiesTestCase.javaW3C addressing test suite compliance1.5modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/DIIClientTestCase.javaW3C addressing test suite compliance1.9modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/EventingSupport.javaW3C addressing test suite compliance1.7modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/EventingTestCase.javaW3C addressing test suite compliance1.5modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/NotificationTestCase.javaW3C addressing test suite compliance1.5modifiedhbraunwebservice/test/java/org/jboss/test/ws/interop/microsoft/addressing/wsa10/AddressingTestCase.javaW3C addressing test suite compliance1.3modifiedhbraunwebservice/test/java/org/jboss/test/ws/interop/microsoft/addressing/wsaTestService/WsaTestPortType_Impl.javaW3C addressing test suite compliance1.7modifiedhbraunwebservice/test/java/org/jboss/test/ws/samples/wsaddr/ClientHandler.javaW3C addressing test suite compliance1.3modifiedhbraunwebservice/test/resources/eventing/META-INF/application-client.xmlW3C addressing test suite compliance1.2modifiedhbraunwebservice/test/resources/eventing/WEB-INF/webservices.xmlW3C addressing test suite compliance1.4modifiedhbraunwebservice/test/resources/eventing/WEB-INF/wsdl/wind.wsdlW3C addressing test suite compliance1.3modifiedhbraunwebservice/test/resources/interop/microsoft/addressing/wsaTestService/WEB-INF/webservices.xmlW3C addressing test suite compliance1.10modifiedhbraunwebservice/test/etc/log4j.xmlrevert local changes1.2modifiedhbraunwebservice/test/java/org/jboss/test/ws/interop/microsoft/addressing/wsaTestService/ConstraintHandler.javaW3C test suite compliance1.25modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/JavaToWSDL20TestCase.javaUpdate tools output dir1.37modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToJavaTestCase.javaUpdate tools output dir1.16modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToWSDL20TestCase.javaUpdate tools output dir1.6modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSToolsTest.javaUpdate tools output dir1.11modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/doclit/ToolsDocLitTestCase.javaUpdate tools output dir1.11modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/testsuitefixture/webservice/holders/HoldersTestCase.javaUpdate tools output dir1.21modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xmlschema/XercesSchemaParserTestCase.javaUpdate tools output dir1.10modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/AnonymousTypesTestCase.javaUpdate tools output dir1.11modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/ComplexTypesTestCase.javaUpdate tools output dir1.9modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/NillableTypesTestCase.javaUpdate tools output dir1.10modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/ReferencesTestCase.javaUpdate tools output dir1.9modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/SimpleTypesTestCase.javaUpdate tools output dir1.22modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/clientside/ClientSideArtifactsTestCase.javaUpdate tools output dir1.10modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/config/globalconfig/GlobalConfigTestCase.javaUpdate tools output dir1.11modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/holders/StandardHoldersTestCase.javaUpdate tools output dir1.6modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/jbws_206/JBWS206Test.javaUpdate tools output dir1.7modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/jbws_211/tests/JBWS211Test.javaUpdate tools output dir1.16modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/testsui
[JBoss-dev] RE: unit test structure chaos
No arguments there. I would agree that keeping the file structure the
same initially makes sense.
The pom.xml for the testsuite would build all testsuite src as well as
creating the necessary jars for deployment.
During the testing a phase, a custom test plugin could for each series
of tests broken up by server config:
1) start the server/servers
2) execute the tests
3) stop the server/servers
After this has happened for each of the server configs, the reports
could compiled.
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-Original Message-
From: Scott M Stark
Sent: Saturday, March 18, 2006 11:57 AM
To: jboss-development@lists.sourceforge.net
Cc: QA
Subject: unit test structure chaos
The lack of correlation between a unit test in the jbossas/testsuite and
its associated deployment artifacts is rather severe. To pull together
everything in a given unit test currently requires:
1. Find the deployment artifacts in the test class
2. Look in testsuite/imports/sections/{org.jboss.test.package}-*.xml to
find how the deployment artifact is built.
3. Find the testsuite/src/resources/{org.jboss.test.package} resources
pulled in by the deployment ant fragment.
There is zero chance of this mapping to a structure mvn understands
since I can't. I can't find any docs on how a testsuite structure would
differ from any other mvn notion, so I guess this means a mvn pom.xml
per test artifact and associated test classes? Perhaps a unit test
plugin is in order as I don't see producing a canonical mvn structure
for the jbossas/testsuite happening anytime in the near future.
Scott Stark
VP Architecture & Technology
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
It seems like ejb3 should only be brining in a latter hibernate dependency via the installer and a custom build for testing. The default/all should not be bumped up to track ejb3 issues to an untested hibernate release. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dimitris Andreadis > Sent: Monday, March 20, 2006 10:54 AM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > Exactly. Something stable, that can be tested with 4.0.4.CR2 > (which is delayed until Friday 24th or Monday 27th max), that > satisfies Bill, and won't require an immediate 4.0.4.SP1 > release for fixes :) > > There are many-many people waiting for 4.0.4 for quite some > time and we are already delayed, so please try to get a > stable release out. Users won't like at all running jboss > 4.0.4 on a hibernate alpha. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Bill Burke > > Sent: 20 March, 2006 20:45 > > To: jboss-development@lists.sourceforge.net > > Subject: Re: [JBoss-dev] 4.0.4 > > > > we just need something stable for hibernate in 4.0.4 GA. > > > > Steve Ebersole wrote: > > > Well, its *possible* to have "a final" release whenever I want ;) > > > > > > But at a bare minimum there is one more feature that EJB3 > > will require > > > which still needs to be implemented; and it is an ugly one. > > I need to > > > release 3.1.3 today/tomorrow (this needs to be done for reasons > > > extraneous to this discussion). I can then come back to > > work on this > > > particular feature. All that I can get done by next week. > > > > > > But that is not all I had initially targeted for 3.2 final > > (nor even > > > beta). And I do not like leaving off planned features just > > to get to > > > a > > > 3.2 final. > > > > > > For me it comes down to whether this is a planned "final > > release" for > > > EJB3. If so, I guess I could be persuaded to cut a 3.2 > final after > > > implementing the above mentioned feature and then start > on 3.2.1 or > > > whatever. > > > > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Dimitris Andreadis > > > Sent: Monday, March 20, 2006 11:42 AM > > > To: jboss-development@lists.sourceforge.net > > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > > > > I love those dependencies ;) > > > > > > Is it possible to have a final next week ? --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
Sure, I do this also; but: (1) I prefer not adding brand new features in a point release, if possible. (2) The query parser re-work represents a significant change in the code-base, which I'd also prefer to not include in a point release. Another option, I guess, is to cut a 3.2 final after this last feature needed for EJB3, and then immediately start on 3.3... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Monday, March 20, 2006 1:21 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] 4.0.4 Steve Ebersole wrote: > This goes back to the previous discussion sometime last week. > > JBoss itself *should* keep bundling 3.1.x - preferably 3.1.3 as soon as > I release it today/tomorrow; that is the stable release cycle. But that > screws EJB3 for the previously mentioned reasons. > > So what's the solution? > > Here's the roadmap: > http://opensource2.atlassian.com/projects/hibernate/browse/HHH?report=co > m.atlassian.jira.plugin.system.project:roadmap-panel > > As you can see, I am nowhere near even a beta according to any known > definition of beta of which I am aware. > What exactly is preventing a 3.2 FINAL and deferring bugs/features until 3.2.1? I do this with EJB3 all the time. If there is a date I have to make, I drop bugs/features from the release to make the date, or move the date if this isn't possible. Bill > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Dimitris Andreadis > Sent: Monday, March 20, 2006 12:54 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > Exactly. Something stable, that can be tested with 4.0.4.CR2 (which is > delayed until Friday 24th or Monday 27th max), that satisfies Bill, and > won't require an immediate 4.0.4.SP1 release for fixes :) > > There are many-many people waiting for 4.0.4 for quite some time and we > are already delayed, so please try to get a stable release out. Users > won't like at all running jboss 4.0.4 on a hibernate alpha. > > >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On >>Behalf Of Bill Burke >>Sent: 20 March, 2006 20:45 >>To: jboss-development@lists.sourceforge.net >>Subject: Re: [JBoss-dev] 4.0.4 >> >>we just need something stable for hibernate in 4.0.4 GA. >> >>Steve Ebersole wrote: >> >>>Well, its *possible* to have "a final" release whenever I want ;) >>> >>>But at a bare minimum there is one more feature that EJB3 >> >>will require >> >>>which still needs to be implemented; and it is an ugly one. >> >> I need to >> >>>release 3.1.3 today/tomorrow (this needs to be done for reasons >>>extraneous to this discussion). I can then come back to >> >>work on this >> >>>particular feature. All that I can get done by next week. >>> >>>But that is not all I had initially targeted for 3.2 final >> >>(nor even >> >>>beta). And I do not like leaving off planned features just >> >>to get to >> >>>a >>>3.2 final. >>> >>>For me it comes down to whether this is a planned "final >> >>release" for >> >>>EJB3. If so, I guess I could be persuaded to cut a 3.2 final after >>>implementing the above mentioned feature and then start on 3.2.1 or >>>whatever. >>> >>> >>>-Original Message- >>>From: [EMAIL PROTECTED] >>>[mailto:[EMAIL PROTECTED] On Behalf Of >>>Dimitris Andreadis >>>Sent: Monday, March 20, 2006 11:42 AM >>>To: jboss-development@lists.sourceforge.net >>>Subject: RE: [JBoss-dev] 4.0.4 >>> >>> >>>I love those dependencies ;) >>> >>>Is it possible to have a final next week ? >>> >>> >>> -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: 20 March, 2006 19:33 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 No way I'll have a 3.2 final this week ;) And it is not a simple matter of re-target for 4.0.5. EJB3 >> >>relies on >> changes made in the current alphas of 3.2 due to the latest >> >>changes in >> the spec (specifically the joinTransaction() stuff)... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:24 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 But you need to get your changes with 4.0.4.CR2 (due out this week) so they get tested! After CR2 you'll need to target 4.0.5 >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On >> >>Behalf Of >> >Dimitris Andreadis >Sent: 20 March, 2006 19:09 >To: jboss-development@lists.sourceforge.net >Subject: RE: [JBoss-dev] 4.0.4 > > >3rd April (give or take) > > > >>-Original Message- >>From: [EMAIL PROTECTED] >>[ma
Re: [JBoss-dev] 4.0.4
Steve Ebersole wrote: This goes back to the previous discussion sometime last week. JBoss itself *should* keep bundling 3.1.x - preferably 3.1.3 as soon as I release it today/tomorrow; that is the stable release cycle. But that screws EJB3 for the previously mentioned reasons. So what's the solution? Here's the roadmap: http://opensource2.atlassian.com/projects/hibernate/browse/HHH?report=co m.atlassian.jira.plugin.system.project:roadmap-panel As you can see, I am nowhere near even a beta according to any known definition of beta of which I am aware. What exactly is preventing a 3.2 FINAL and deferring bugs/features until 3.2.1? I do this with EJB3 all the time. If there is a date I have to make, I drop bugs/features from the release to make the date, or move the date if this isn't possible. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 12:54 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 Exactly. Something stable, that can be tested with 4.0.4.CR2 (which is delayed until Friday 24th or Monday 27th max), that satisfies Bill, and won't require an immediate 4.0.4.SP1 release for fixes :) There are many-many people waiting for 4.0.4 for quite some time and we are already delayed, so please try to get a stable release out. Users won't like at all running jboss 4.0.4 on a hibernate alpha. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: 20 March, 2006 20:45 To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] 4.0.4 we just need something stable for hibernate in 4.0.4 GA. Steve Ebersole wrote: Well, its *possible* to have "a final" release whenever I want ;) But at a bare minimum there is one more feature that EJB3 will require which still needs to be implemented; and it is an ugly one. I need to release 3.1.3 today/tomorrow (this needs to be done for reasons extraneous to this discussion). I can then come back to work on this particular feature. All that I can get done by next week. But that is not all I had initially targeted for 3.2 final (nor even beta). And I do not like leaving off planned features just to get to a 3.2 final. For me it comes down to whether this is a planned "final release" for EJB3. If so, I guess I could be persuaded to cut a 3.2 final after implementing the above mentioned feature and then start on 3.2.1 or whatever. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:42 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 I love those dependencies ;) Is it possible to have a final next week ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: 20 March, 2006 19:33 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 No way I'll have a 3.2 final this week ;) And it is not a simple matter of re-target for 4.0.5. EJB3 relies on changes made in the current alphas of 3.2 due to the latest changes in the spec (specifically the joinTransaction() stuff)... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:24 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 But you need to get your changes with 4.0.4.CR2 (due out this week) so they get tested! After CR2 you'll need to target 4.0.5 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: 20 March, 2006 19:09 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 3rd April (give or take) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: 20 March, 2006 19:03 To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] 4.0.4 I am trying to nail down a short-term release schedule for Hibernate 3.2.x. Due to some of the changes made there specifically for EJB3 persistence support, I need to have a stable version of 3.2 done before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. Is there an anticipated release date for 4.0.4 GA at this point? --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourcefo
Re: [JBoss-dev] optional schema validation
yeah, this seems to work, but does anybody know if there is a better way?
Bill Burke wrote:
I'm looking at how we do parsing and looking at
XmlFileLoader.LocalErrorHandler.
It looks like errors are ignored if the schema wasn't resolved. Is this
the way to do it?
Bill Burke wrote:
How do you set up xml parsing to not validate if there is no schema
specified in the XML?
Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the
declaration of element 'persistence'.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
HEM is doing the following code and throwing an error:
private static Document loadURL(URL configURL, EntityResolver
resolver) throws Exception {
InputStream is = configURL != null ? configURL.openStream() :
null;
if ( is == null ) {
throw new IOException( "Failed to obtain InputStream from
url: " + configURL );
}
List errors = new ArrayList();
DocumentBuilderFactory docBuilderFactory = null;
docBuilderFactory = DocumentBuilderFactory.newInstance();
docBuilderFactory.setValidating( true );
docBuilderFactory.setNamespaceAware( true );
try {
//otherwise Xerces fails in validation
docBuilderFactory.setAttribute(
"http://apache.org/xml/features/validation/schema";, true);
}
catch (IllegalArgumentException e) {
docBuilderFactory.setValidating( false );
docBuilderFactory.setNamespaceAware( false );
}
InputSource source = new InputSource( is );
DocumentBuilder docBuilder =
docBuilderFactory.newDocumentBuilder();
docBuilder.setEntityResolver( resolver );
docBuilder.setErrorHandler( new ErrorLogger("XML InputStream",
errors) );
Document doc = docBuilder.parse( source );
if ( errors.size() != 0 ) {
throw new PersistenceException( "invalid persistence.xml",
(Throwable) errors.get( 0 ) );
}
return doc;
}
--
Bill Burke
Chief Architect
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
This goes back to the previous discussion sometime last week. JBoss itself *should* keep bundling 3.1.x - preferably 3.1.3 as soon as I release it today/tomorrow; that is the stable release cycle. But that screws EJB3 for the previously mentioned reasons. So what's the solution? Here's the roadmap: http://opensource2.atlassian.com/projects/hibernate/browse/HHH?report=co m.atlassian.jira.plugin.system.project:roadmap-panel As you can see, I am nowhere near even a beta according to any known definition of beta of which I am aware. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 12:54 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 Exactly. Something stable, that can be tested with 4.0.4.CR2 (which is delayed until Friday 24th or Monday 27th max), that satisfies Bill, and won't require an immediate 4.0.4.SP1 release for fixes :) There are many-many people waiting for 4.0.4 for quite some time and we are already delayed, so please try to get a stable release out. Users won't like at all running jboss 4.0.4 on a hibernate alpha. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Bill Burke > Sent: 20 March, 2006 20:45 > To: jboss-development@lists.sourceforge.net > Subject: Re: [JBoss-dev] 4.0.4 > > we just need something stable for hibernate in 4.0.4 GA. > > Steve Ebersole wrote: > > Well, its *possible* to have "a final" release whenever I want ;) > > > > But at a bare minimum there is one more feature that EJB3 > will require > > which still needs to be implemented; and it is an ugly one. > I need to > > release 3.1.3 today/tomorrow (this needs to be done for reasons > > extraneous to this discussion). I can then come back to > work on this > > particular feature. All that I can get done by next week. > > > > But that is not all I had initially targeted for 3.2 final > (nor even > > beta). And I do not like leaving off planned features just > to get to > > a > > 3.2 final. > > > > For me it comes down to whether this is a planned "final > release" for > > EJB3. If so, I guess I could be persuaded to cut a 3.2 final after > > implementing the above mentioned feature and then start on 3.2.1 or > > whatever. > > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Dimitris Andreadis > > Sent: Monday, March 20, 2006 11:42 AM > > To: jboss-development@lists.sourceforge.net > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > I love those dependencies ;) > > > > Is it possible to have a final next week ? > > > > > >>-Original Message- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of > >>Steve Ebersole > >>Sent: 20 March, 2006 19:33 > >>To: jboss-development@lists.sourceforge.net > >>Subject: RE: [JBoss-dev] 4.0.4 > >> > >>No way I'll have a 3.2 final this week ;) > >> > >>And it is not a simple matter of re-target for 4.0.5. EJB3 > relies on > >>changes made in the current alphas of 3.2 due to the latest > changes in > >>the spec (specifically the > >>joinTransaction() stuff)... > >> > >>-Original Message- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of > >>Dimitris Andreadis > >>Sent: Monday, March 20, 2006 11:24 AM > >>To: jboss-development@lists.sourceforge.net > >>Subject: RE: [JBoss-dev] 4.0.4 > >> > >> > >>But you need to get your changes with 4.0.4.CR2 (due out this > >>week) so they get tested! > >> > >>After CR2 you'll need to target 4.0.5 > >> > >> > >>>-Original Message- > >>>From: [EMAIL PROTECTED] > >>>[mailto:[EMAIL PROTECTED] On > Behalf Of > >>>Dimitris Andreadis > >>>Sent: 20 March, 2006 19:09 > >>>To: jboss-development@lists.sourceforge.net > >>>Subject: RE: [JBoss-dev] 4.0.4 > >>> > >>> > >>>3rd April (give or take) > >>> > >>> > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > >> > >>Behalf Of > >> > Steve Ebersole > Sent: 20 March, 2006 19:03 > To: jboss-development@lists.sourceforge.net > Subject: [JBoss-dev] 4.0.4 > > I am trying to nail down a short-term release schedule for > >>> > >>>Hibernate > >>> > 3.2.x. Due to some of the changes made there > >> > >>specifically for EJB3 > >> > persistence support, I need to have a stable version of 3.2 done > before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. > > Is there an anticipated release date for 4.0.4 GA at this point? > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > >> > >>scripting > >> > language that extends applications into web and mobile > >>> > >>>media. Attend > >>> > the live webcast and join the prime developer group > >>> > >>>breaking into this > >>> > new coding territory! >
[JBoss-dev] jboss-4.0-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060320121502 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build: 03/20/2006 12:15:02Time to build: 99 minutes 55 secondsLast changed: 03/20/2006 12:08:02Last log entry: JBAS-2744, Use the getServerHost() as the jnp.localAddress value Unit Tests: (2990) Total Errors and Failures: (62)testENCServletViaInvokerorg.jboss.test.jacc.test.WebIntegrationUnitTestCase(JACC+SecurityMgr)testCreateRequiredCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiredCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiredCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiredCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateRequiresNewCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNotSupportedCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelRequiredorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelRequiresNeworg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelNotSupportedorg.jboss.test.txtimer.test.CreateCancelTestCasetestCreateNeverCancelNeverorg.jboss.test.txtimer.test.CreateCancelTestCasetestSingleEventDurationorg.jboss.test.txtimer.test.PersistenceTestCasetestTimerRestoredForScopedSessionBeanorg.jboss.test.txtimer.test.ScopedPersistentTimerTestCasetestEndpointorg.jboss.test.webservice.jbws68.JBWS68TestCasetestEchoStringorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoIntegerorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoIntorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoLongorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoShortorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDecimalorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoFloatorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDoubleorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoBooleanorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoByteorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoQNameorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDateTimeCalendarorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDateTimeDateorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDateCalendarorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDateDateorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoBase64Binaryorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoHexBinaryorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoBeanorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoBeanNullPropertiesorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoStringArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoIntegerArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoIntArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoLongArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoShortArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDecimalArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoFloatArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDoubleArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoBooleanArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoByteArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoQNameArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestEchoDateTimeArrayorg.jboss.test.webservice.marshalltest.MarshallDocLiteralTestCasetestClientAccessJSEorg.jboss.test.webservice.samples.ClientSideEJBTestCasetestWithTransportOptionsorg.jboss.test.webservice.secure.SimpleClientSecureT
RE: [JBoss-dev] 4.0.4
Exactly. Something stable, that can be tested with 4.0.4.CR2 (which is delayed until Friday 24th or Monday 27th max), that satisfies Bill, and won't require an immediate 4.0.4.SP1 release for fixes :) There are many-many people waiting for 4.0.4 for quite some time and we are already delayed, so please try to get a stable release out. Users won't like at all running jboss 4.0.4 on a hibernate alpha. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Bill Burke > Sent: 20 March, 2006 20:45 > To: jboss-development@lists.sourceforge.net > Subject: Re: [JBoss-dev] 4.0.4 > > we just need something stable for hibernate in 4.0.4 GA. > > Steve Ebersole wrote: > > Well, its *possible* to have "a final" release whenever I want ;) > > > > But at a bare minimum there is one more feature that EJB3 > will require > > which still needs to be implemented; and it is an ugly one. > I need to > > release 3.1.3 today/tomorrow (this needs to be done for reasons > > extraneous to this discussion). I can then come back to > work on this > > particular feature. All that I can get done by next week. > > > > But that is not all I had initially targeted for 3.2 final > (nor even > > beta). And I do not like leaving off planned features just > to get to > > a > > 3.2 final. > > > > For me it comes down to whether this is a planned "final > release" for > > EJB3. If so, I guess I could be persuaded to cut a 3.2 final after > > implementing the above mentioned feature and then start on 3.2.1 or > > whatever. > > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Dimitris Andreadis > > Sent: Monday, March 20, 2006 11:42 AM > > To: jboss-development@lists.sourceforge.net > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > I love those dependencies ;) > > > > Is it possible to have a final next week ? > > > > > >>-Original Message- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of > >>Steve Ebersole > >>Sent: 20 March, 2006 19:33 > >>To: jboss-development@lists.sourceforge.net > >>Subject: RE: [JBoss-dev] 4.0.4 > >> > >>No way I'll have a 3.2 final this week ;) > >> > >>And it is not a simple matter of re-target for 4.0.5. EJB3 > relies on > >>changes made in the current alphas of 3.2 due to the latest > changes in > >>the spec (specifically the > >>joinTransaction() stuff)... > >> > >>-Original Message- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of > >>Dimitris Andreadis > >>Sent: Monday, March 20, 2006 11:24 AM > >>To: jboss-development@lists.sourceforge.net > >>Subject: RE: [JBoss-dev] 4.0.4 > >> > >> > >>But you need to get your changes with 4.0.4.CR2 (due out this > >>week) so they get tested! > >> > >>After CR2 you'll need to target 4.0.5 > >> > >> > >>>-Original Message- > >>>From: [EMAIL PROTECTED] > >>>[mailto:[EMAIL PROTECTED] On > Behalf Of > >>>Dimitris Andreadis > >>>Sent: 20 March, 2006 19:09 > >>>To: jboss-development@lists.sourceforge.net > >>>Subject: RE: [JBoss-dev] 4.0.4 > >>> > >>> > >>>3rd April (give or take) > >>> > >>> > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > >> > >>Behalf Of > >> > Steve Ebersole > Sent: 20 March, 2006 19:03 > To: jboss-development@lists.sourceforge.net > Subject: [JBoss-dev] 4.0.4 > > I am trying to nail down a short-term release schedule for > >>> > >>>Hibernate > >>> > 3.2.x. Due to some of the changes made there > >> > >>specifically for EJB3 > >> > persistence support, I need to have a stable version of 3.2 done > before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. > > Is there an anticipated release date for 4.0.4 GA at this point? > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > >> > >>scripting > >> > language that extends applications into web and mobile > >>> > >>>media. Attend > >>> > the live webcast and join the prime developer group > >>> > >>>breaking into this > >>> > new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > > >>> > >>> > >>>--- > >>>This SF.Net email is sponsored by xPML, a groundbreaking scripting > >>>language that extends applications into web and mobile > >> > >>media. Attend > >> > >>>the live webcast and join the prime developer group > >> > >>breaking into this > >> > >>>new coding territory! > >>>http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > >>>___ > >>>JBoss-
RE: [JBoss-dev] 4.0.4
Yep. Ok, so I'll implement that one mentioned feature and cut alpha3 which we can use in 4.0.4... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Monday, March 20, 2006 12:45 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] 4.0.4 we just need something stable for hibernate in 4.0.4 GA. Steve Ebersole wrote: > Well, its *possible* to have "a final" release whenever I want ;) > > But at a bare minimum there is one more feature that EJB3 will require > which still needs to be implemented; and it is an ugly one. I need to > release 3.1.3 today/tomorrow (this needs to be done for reasons > extraneous to this discussion). I can then come back to work on this > particular feature. All that I can get done by next week. > > But that is not all I had initially targeted for 3.2 final (nor even > beta). And I do not like leaving off planned features just to get to a > 3.2 final. > > For me it comes down to whether this is a planned "final release" for > EJB3. If so, I guess I could be persuaded to cut a 3.2 final after > implementing the above mentioned feature and then start on 3.2.1 or > whatever. > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Dimitris Andreadis > Sent: Monday, March 20, 2006 11:42 AM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > I love those dependencies ;) > > Is it possible to have a final next week ? > > >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On >>Behalf Of Steve Ebersole >>Sent: 20 March, 2006 19:33 >>To: jboss-development@lists.sourceforge.net >>Subject: RE: [JBoss-dev] 4.0.4 >> >>No way I'll have a 3.2 final this week ;) >> >>And it is not a simple matter of re-target for 4.0.5. EJB3 >>relies on changes made in the current alphas of 3.2 due to >>the latest changes in the spec (specifically the >>joinTransaction() stuff)... >> >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On >>Behalf Of Dimitris Andreadis >>Sent: Monday, March 20, 2006 11:24 AM >>To: jboss-development@lists.sourceforge.net >>Subject: RE: [JBoss-dev] 4.0.4 >> >> >>But you need to get your changes with 4.0.4.CR2 (due out this >>week) so they get tested! >> >>After CR2 you'll need to target 4.0.5 >> >> >>>-Original Message- >>>From: [EMAIL PROTECTED] >>>[mailto:[EMAIL PROTECTED] On Behalf Of >>>Dimitris Andreadis >>>Sent: 20 March, 2006 19:09 >>>To: jboss-development@lists.sourceforge.net >>>Subject: RE: [JBoss-dev] 4.0.4 >>> >>> >>>3rd April (give or take) >>> >>> -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >> >>Behalf Of >> Steve Ebersole Sent: 20 March, 2006 19:03 To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] 4.0.4 I am trying to nail down a short-term release schedule for >>> >>>Hibernate >>> 3.2.x. Due to some of the changes made there >> >>specifically for EJB3 >> persistence support, I need to have a stable version of 3.2 done before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. Is there an anticipated release date for 4.0.4 GA at this point? --- This SF.Net email is sponsored by xPML, a groundbreaking >> >>scripting >> language that extends applications into web and mobile >>> >>>media. Attend >>> the live webcast and join the prime developer group >>> >>>breaking into this >>> new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development >>> >>> >>>--- >>>This SF.Net email is sponsored by xPML, a groundbreaking scripting >>>language that extends applications into web and mobile >> >>media. Attend >> >>>the live webcast and join the prime developer group >> >>breaking into this >> >>>new coding territory! >>>http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 >>>___ >>>JBoss-Development mailing list >>>JBoss-Development@lists.sourceforge.net >>>https://lists.sourceforge.net/lists/listinfo/jboss-development >>> >> >> >>--- >>This SF.Net email is sponsored by xPML, a groundbreaking >>scripting language that extends applications into web and >>mobile media. Attend the live webcast and join the prime >>developer group breaking into this new coding territory! >>http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 >>___ >>JBoss-Development mailing list >>JBoss-Development@l
Re: [JBoss-dev] optional schema validation
On Mon, 2006-03-20 at 13:38 -0500, Bill Burke wrote:
> Tell me something I don't already know. I want validation if there is a
> schema specified, no validation if there is not.
>
And no default attributes, etc.
> Adrian Brock wrote:
> > The element declaration is required (from your error message)
> > http://www.w3.org/TR/xmlschema-1/#cvc-elt
> >
> > and validation is required for minimal conformance:
> > http://www.w3.org/TR/xmlschema-1/#concepts-conformance
> >
> > On Mon, 2006-03-20 at 13:20 -0500, Bill Burke wrote:
> >
> >>How do you set up xml parsing to not validate if there is no schema
> >>specified in the XML?
> >>
> >>Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the
> >>declaration of element 'persistence'.
> >> at
> >>org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> >>Source)
> >> at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
> >> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> >>Source)
> >>
> >>
> >>
> >>HEM is doing the following code and throwing an error:
> >>
> >>private static Document loadURL(URL configURL, EntityResolver resolver)
> >>throws Exception {
> >>InputStream is = configURL != null ? configURL.openStream() :
> >> null;
> >>if ( is == null ) {
> >>throw new IOException( "Failed to obtain InputStream
> >> from url: " +
> >>configURL );
> >>}
> >>List errors = new ArrayList();
> >>DocumentBuilderFactory docBuilderFactory = null;
> >>docBuilderFactory = DocumentBuilderFactory.newInstance();
> >>docBuilderFactory.setValidating( true );
> >>docBuilderFactory.setNamespaceAware( true );
> >>try {
> >>//otherwise Xerces fails in validation
> >>docBuilderFactory.setAttribute(
> >>"http://apache.org/xml/features/validation/schema";, true);
> >>}
> >>catch (IllegalArgumentException e) {
> >>docBuilderFactory.setValidating( false );
> >>docBuilderFactory.setNamespaceAware( false );
> >>}
> >>InputSource source = new InputSource( is );
> >>DocumentBuilder docBuilder =
> >> docBuilderFactory.newDocumentBuilder();
> >>docBuilder.setEntityResolver( resolver );
> >>docBuilder.setErrorHandler( new ErrorLogger("XML InputStream",
> >> errors) );
> >>Document doc = docBuilder.parse( source );
> >> if ( errors.size() != 0 ) {
> >>throw new PersistenceException( "invalid
> >> persistence.xml",
> >>(Throwable) errors.get( 0 ) );
> >>}
> >>return doc;
> >>}
> >>
> >>
>
--
Adrian Brock
Chief Scientist
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 4.0.4
we just need something stable for hibernate in 4.0.4 GA. Steve Ebersole wrote: Well, its *possible* to have "a final" release whenever I want ;) But at a bare minimum there is one more feature that EJB3 will require which still needs to be implemented; and it is an ugly one. I need to release 3.1.3 today/tomorrow (this needs to be done for reasons extraneous to this discussion). I can then come back to work on this particular feature. All that I can get done by next week. But that is not all I had initially targeted for 3.2 final (nor even beta). And I do not like leaving off planned features just to get to a 3.2 final. For me it comes down to whether this is a planned "final release" for EJB3. If so, I guess I could be persuaded to cut a 3.2 final after implementing the above mentioned feature and then start on 3.2.1 or whatever. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:42 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 I love those dependencies ;) Is it possible to have a final next week ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: 20 March, 2006 19:33 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 No way I'll have a 3.2 final this week ;) And it is not a simple matter of re-target for 4.0.5. EJB3 relies on changes made in the current alphas of 3.2 due to the latest changes in the spec (specifically the joinTransaction() stuff)... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:24 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 But you need to get your changes with 4.0.4.CR2 (due out this week) so they get tested! After CR2 you'll need to target 4.0.5 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: 20 March, 2006 19:09 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 3rd April (give or take) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: 20 March, 2006 19:03 To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] 4.0.4 I am trying to nail down a short-term release schedule for Hibernate 3.2.x. Due to some of the changes made there specifically for EJB3 persistence support, I need to have a stable version of 3.2 done before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. Is there an anticipated release date for 4.0.4 GA at this point? --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development -
RE: [JBoss-dev] 4.0.4
Well, its *possible* to have "a final" release whenever I want ;) But at a bare minimum there is one more feature that EJB3 will require which still needs to be implemented; and it is an ugly one. I need to release 3.1.3 today/tomorrow (this needs to be done for reasons extraneous to this discussion). I can then come back to work on this particular feature. All that I can get done by next week. But that is not all I had initially targeted for 3.2 final (nor even beta). And I do not like leaving off planned features just to get to a 3.2 final. For me it comes down to whether this is a planned "final release" for EJB3. If so, I guess I could be persuaded to cut a 3.2 final after implementing the above mentioned feature and then start on 3.2.1 or whatever. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:42 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 I love those dependencies ;) Is it possible to have a final next week ? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: 20 March, 2006 19:33 > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > No way I'll have a 3.2 final this week ;) > > And it is not a simple matter of re-target for 4.0.5. EJB3 > relies on changes made in the current alphas of 3.2 due to > the latest changes in the spec (specifically the > joinTransaction() stuff)... > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dimitris Andreadis > Sent: Monday, March 20, 2006 11:24 AM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > But you need to get your changes with 4.0.4.CR2 (due out this > week) so they get tested! > > After CR2 you'll need to target 4.0.5 > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Dimitris Andreadis > > Sent: 20 March, 2006 19:09 > > To: jboss-development@lists.sourceforge.net > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > 3rd April (give or take) > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Steve Ebersole > > > Sent: 20 March, 2006 19:03 > > > To: jboss-development@lists.sourceforge.net > > > Subject: [JBoss-dev] 4.0.4 > > > > > > I am trying to nail down a short-term release schedule for > > Hibernate > > > 3.2.x. Due to some of the changes made there > specifically for EJB3 > > > persistence support, I need to have a stable version of 3.2 done > > > before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. > > > > > > Is there an anticipated release date for 4.0.4 GA at this point? > > > > > > > > > --- > > > This SF.Net email is sponsored by xPML, a groundbreaking > scripting > > > language that extends applications into web and mobile > > media. Attend > > > the live webcast and join the prime developer group > > breaking into this > > > new coding territory! > > > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > > > ___ > > > JBoss-Development mailing list > > > JBoss-Development@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > --- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language that extends applications into web and mobile > media. Attend > > the live webcast and join the prime developer group > breaking into this > > new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bi
Re: [JBoss-dev] optional schema validation
Tell me something I don't already know. I want validation if there is a
schema specified, no validation if there is not.
Adrian Brock wrote:
The element declaration is required (from your error message)
http://www.w3.org/TR/xmlschema-1/#cvc-elt
and validation is required for minimal conformance:
http://www.w3.org/TR/xmlschema-1/#concepts-conformance
On Mon, 2006-03-20 at 13:20 -0500, Bill Burke wrote:
How do you set up xml parsing to not validate if there is no schema
specified in the XML?
Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the
declaration of element 'persistence'.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
HEM is doing the following code and throwing an error:
private static Document loadURL(URL configURL, EntityResolver resolver)
throws Exception {
InputStream is = configURL != null ? configURL.openStream() :
null;
if ( is == null ) {
throw new IOException( "Failed to obtain InputStream from url: " +
configURL );
}
List errors = new ArrayList();
DocumentBuilderFactory docBuilderFactory = null;
docBuilderFactory = DocumentBuilderFactory.newInstance();
docBuilderFactory.setValidating( true );
docBuilderFactory.setNamespaceAware( true );
try {
//otherwise Xerces fails in validation
docBuilderFactory.setAttribute(
"http://apache.org/xml/features/validation/schema";, true);
}
catch (IllegalArgumentException e) {
docBuilderFactory.setValidating( false );
docBuilderFactory.setNamespaceAware( false );
}
InputSource source = new InputSource( is );
DocumentBuilder docBuilder =
docBuilderFactory.newDocumentBuilder();
docBuilder.setEntityResolver( resolver );
docBuilder.setErrorHandler( new ErrorLogger("XML InputStream",
errors) );
Document doc = docBuilder.parse( source );
if ( errors.size() != 0 ) {
throw new PersistenceException( "invalid persistence.xml",
(Throwable) errors.get( 0 ) );
}
return doc;
}
--
Bill Burke
Chief Architect
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] optional schema validation
The element declaration is required (from your error message)
http://www.w3.org/TR/xmlschema-1/#cvc-elt
and validation is required for minimal conformance:
http://www.w3.org/TR/xmlschema-1/#concepts-conformance
On Mon, 2006-03-20 at 13:20 -0500, Bill Burke wrote:
> How do you set up xml parsing to not validate if there is no schema
> specified in the XML?
>
> Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the
> declaration of element 'persistence'.
> at
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> Source)
> at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> Source)
>
>
>
> HEM is doing the following code and throwing an error:
>
> private static Document loadURL(URL configURL, EntityResolver resolver)
> throws Exception {
> InputStream is = configURL != null ? configURL.openStream() :
> null;
> if ( is == null ) {
> throw new IOException( "Failed to obtain InputStream
> from url: " +
> configURL );
> }
> List errors = new ArrayList();
> DocumentBuilderFactory docBuilderFactory = null;
> docBuilderFactory = DocumentBuilderFactory.newInstance();
> docBuilderFactory.setValidating( true );
> docBuilderFactory.setNamespaceAware( true );
> try {
> //otherwise Xerces fails in validation
> docBuilderFactory.setAttribute(
> "http://apache.org/xml/features/validation/schema";, true);
> }
> catch (IllegalArgumentException e) {
> docBuilderFactory.setValidating( false );
> docBuilderFactory.setNamespaceAware( false );
> }
> InputSource source = new InputSource( is );
> DocumentBuilder docBuilder =
> docBuilderFactory.newDocumentBuilder();
> docBuilder.setEntityResolver( resolver );
> docBuilder.setErrorHandler( new ErrorLogger("XML InputStream",
> errors) );
> Document doc = docBuilder.parse( source );
>if ( errors.size() != 0 ) {
> throw new PersistenceException( "invalid
> persistence.xml",
> (Throwable) errors.get( 0 ) );
> }
> return doc;
> }
>
>
--
Adrian Brock
Chief Scientist
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] optional schema validation
I'm looking at how we do parsing and looking at
XmlFileLoader.LocalErrorHandler.
It looks like errors are ignored if the schema wasn't resolved. Is this
the way to do it?
Bill Burke wrote:
How do you set up xml parsing to not validate if there is no schema
specified in the XML?
Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the
declaration of element 'persistence'.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
HEM is doing the following code and throwing an error:
private static Document loadURL(URL configURL, EntityResolver
resolver) throws Exception {
InputStream is = configURL != null ? configURL.openStream() : null;
if ( is == null ) {
throw new IOException( "Failed to obtain InputStream from
url: " + configURL );
}
List errors = new ArrayList();
DocumentBuilderFactory docBuilderFactory = null;
docBuilderFactory = DocumentBuilderFactory.newInstance();
docBuilderFactory.setValidating( true );
docBuilderFactory.setNamespaceAware( true );
try {
//otherwise Xerces fails in validation
docBuilderFactory.setAttribute(
"http://apache.org/xml/features/validation/schema";, true);
}
catch (IllegalArgumentException e) {
docBuilderFactory.setValidating( false );
docBuilderFactory.setNamespaceAware( false );
}
InputSource source = new InputSource( is );
DocumentBuilder docBuilder =
docBuilderFactory.newDocumentBuilder();
docBuilder.setEntityResolver( resolver );
docBuilder.setErrorHandler( new ErrorLogger("XML InputStream",
errors) );
Document doc = docBuilder.parse( source );
if ( errors.size() != 0 ) {
throw new PersistenceException( "invalid persistence.xml",
(Throwable) errors.get( 0 ) );
}
return doc;
}
--
Bill Burke
Chief Architect
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] optional schema validation
How do you set up xml parsing to not validate if there is no schema
specified in the XML?
Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the
declaration of element 'persistence'.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
HEM is doing the following code and throwing an error:
private static Document loadURL(URL configURL, EntityResolver resolver)
throws Exception {
InputStream is = configURL != null ? configURL.openStream() :
null;
if ( is == null ) {
throw new IOException( "Failed to obtain InputStream from url: " +
configURL );
}
List errors = new ArrayList();
DocumentBuilderFactory docBuilderFactory = null;
docBuilderFactory = DocumentBuilderFactory.newInstance();
docBuilderFactory.setValidating( true );
docBuilderFactory.setNamespaceAware( true );
try {
//otherwise Xerces fails in validation
docBuilderFactory.setAttribute(
"http://apache.org/xml/features/validation/schema";, true);
}
catch (IllegalArgumentException e) {
docBuilderFactory.setValidating( false );
docBuilderFactory.setNamespaceAware( false );
}
InputSource source = new InputSource( is );
DocumentBuilder docBuilder =
docBuilderFactory.newDocumentBuilder();
docBuilder.setEntityResolver( resolver );
docBuilder.setErrorHandler( new ErrorLogger("XML InputStream",
errors) );
Document doc = docBuilder.parse( source );
if ( errors.size() != 0 ) {
throw new PersistenceException( "invalid persistence.xml",
(Throwable) errors.get( 0 ) );
}
return doc;
}
--
Bill Burke
Chief Architect
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
I love those dependencies ;) Is it possible to have a final next week ? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: 20 March, 2006 19:33 > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > No way I'll have a 3.2 final this week ;) > > And it is not a simple matter of re-target for 4.0.5. EJB3 > relies on changes made in the current alphas of 3.2 due to > the latest changes in the spec (specifically the > joinTransaction() stuff)... > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dimitris Andreadis > Sent: Monday, March 20, 2006 11:24 AM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > But you need to get your changes with 4.0.4.CR2 (due out this > week) so they get tested! > > After CR2 you'll need to target 4.0.5 > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Dimitris Andreadis > > Sent: 20 March, 2006 19:09 > > To: jboss-development@lists.sourceforge.net > > Subject: RE: [JBoss-dev] 4.0.4 > > > > > > 3rd April (give or take) > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Steve Ebersole > > > Sent: 20 March, 2006 19:03 > > > To: jboss-development@lists.sourceforge.net > > > Subject: [JBoss-dev] 4.0.4 > > > > > > I am trying to nail down a short-term release schedule for > > Hibernate > > > 3.2.x. Due to some of the changes made there > specifically for EJB3 > > > persistence support, I need to have a stable version of 3.2 done > > > before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. > > > > > > Is there an anticipated release date for 4.0.4 GA at this point? > > > > > > > > > --- > > > This SF.Net email is sponsored by xPML, a groundbreaking > scripting > > > language that extends applications into web and mobile > > media. Attend > > > the live webcast and join the prime developer group > > breaking into this > > > new coding territory! > > > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > > > ___ > > > JBoss-Development mailing list > > > JBoss-Development@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > --- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language that extends applications into web and mobile > media. Attend > > the live webcast and join the prime developer group > breaking into this > > new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 4.0.4
4.0.4CR2 is going to go out with 3.2.0alpha2 as next release of EJB3 requires it. Steve Ebersole wrote: No way I'll have a 3.2 final this week ;) And it is not a simple matter of re-target for 4.0.5. EJB3 relies on changes made in the current alphas of 3.2 due to the latest changes in the spec (specifically the joinTransaction() stuff)... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:24 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 But you need to get your changes with 4.0.4.CR2 (due out this week) so they get tested! After CR2 you'll need to target 4.0.5 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: 20 March, 2006 19:09 To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 3rd April (give or take) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: 20 March, 2006 19:03 To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] 4.0.4 I am trying to nail down a short-term release schedule for Hibernate 3.2.x. Due to some of the changes made there specifically for EJB3 persistence support, I need to have a stable version of 3.2 done before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. Is there an anticipated release date for 4.0.4 GA at this point? --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
No way I'll have a 3.2 final this week ;) And it is not a simple matter of re-target for 4.0.5. EJB3 relies on changes made in the current alphas of 3.2 due to the latest changes in the spec (specifically the joinTransaction() stuff)... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dimitris Andreadis Sent: Monday, March 20, 2006 11:24 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 But you need to get your changes with 4.0.4.CR2 (due out this week) so they get tested! After CR2 you'll need to target 4.0.5 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dimitris Andreadis > Sent: 20 March, 2006 19:09 > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > 3rd April (give or take) > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Steve Ebersole > > Sent: 20 March, 2006 19:03 > > To: jboss-development@lists.sourceforge.net > > Subject: [JBoss-dev] 4.0.4 > > > > I am trying to nail down a short-term release schedule for > Hibernate > > 3.2.x. Due to some of the changes made there specifically for EJB3 > > persistence support, I need to have a stable version of 3.2 done > > before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. > > > > Is there an anticipated release date for 4.0.4 GA at this point? > > > > > > --- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language that extends applications into web and mobile > media. Attend > > the live webcast and join the prime developer group > breaking into this > > new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
Since the CR2 is going to be on the order of a week late, the GA needs to be pushed back a week to give at least 2 weeks for feedback. The week of the 10th should be the new GA target. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dimitris Andreadis > Sent: Monday, March 20, 2006 9:09 AM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > 3rd April (give or take) > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Steve Ebersole > > Sent: 20 March, 2006 19:03 > > To: jboss-development@lists.sourceforge.net > > Subject: [JBoss-dev] 4.0.4 > > > > I am trying to nail down a short-term release schedule for > Hibernate > > 3.2.x. Due to some of the changes made there specifically for EJB3 > > persistence support, I need to have a stable version of 3.2 done > > before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. > > > > Is there an anticipated release date for 4.0.4 GA at this point? > > > > > > --- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language that extends applications into web and mobile > media. Attend > > the live webcast and join the prime developer group > breaking into this > > new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
But you need to get your changes with 4.0.4.CR2 (due out this week) so they get tested! After CR2 you'll need to target 4.0.5 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Dimitris Andreadis > Sent: 20 March, 2006 19:09 > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] 4.0.4 > > > 3rd April (give or take) > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Steve Ebersole > > Sent: 20 March, 2006 19:03 > > To: jboss-development@lists.sourceforge.net > > Subject: [JBoss-dev] 4.0.4 > > > > I am trying to nail down a short-term release schedule for > Hibernate > > 3.2.x. Due to some of the changes made there specifically for EJB3 > > persistence support, I need to have a stable version of 3.2 done > > before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. > > > > Is there an anticipated release date for 4.0.4 GA at this point? > > > > > > --- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language that extends applications into web and mobile > media. Attend > > the live webcast and join the prime developer group > breaking into this > > new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 4.0.4
3rd April (give or take) > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: 20 March, 2006 19:03 > To: jboss-development@lists.sourceforge.net > Subject: [JBoss-dev] 4.0.4 > > I am trying to nail down a short-term release schedule for > Hibernate 3.2.x. Due to some of the changes made there > specifically for EJB3 persistence support, I need to have a > stable version of 3.2 done before AS goes 4.0.4 as 4.0.4 will > ship with 3.2.x moving forward. > > Is there an anticipated release date for 4.0.4 GA at this point? > > > --- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060320112913 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: 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: 03/20/2006 11:29:13Time to build: 35 minutes 44 secondsLast changed: 03/19/2006 11:09:16Last log entry: Reduce logging level when releasing state transfer locks Unit Tests: (1376) Total Errors and Failures: (11)testPrintorg.jboss.cache.loader.TcpCacheLoaderTesttestPutorg.jboss.cache.loader.TcpCacheLoaderTesttestActiveTransactionorg.jboss.cache.statetransfer.ForcedStateTransferTesttestRollbackOnlyTransactionorg.jboss.cache.statetransfer.ForcedStateTransferTesttestHungThreadorg.jboss.cache.statetransfer.ForcedStateTransferTesttestBeforeCompletionLockorg.jboss.cache.statetransfer.ForcedStateTransferTesttestAfterCompletionLockorg.jboss.cache.statetransfer.ForcedStateTransferTesttestMultipleProblemsorg.jboss.cache.statetransfer.ForcedStateTransferTesttestSerializableIsolationorg.jboss.cache.statetransfer.ForcedStateTransferTesttestPartialStateTransferorg.jboss.cache.statetransfer.ForcedStateTransferTesttestReplSyncorg.jboss.cache.statetransfer.ForcedStateTransferTest Modifications since last build: (first 50 of 58)1.4modifiedbstansberrytests/functional/org/jboss/cache/GlobalTransactionTest.javaAdd a test that equals() handles null properly1.6modifiedbstansberrytests/functional/org/jboss/cache/FqnTest.javaAdd a test that equals() handles null and other types properly1.12modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.13modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.14modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.4modifiedbwangtests/scripts/bench.txtupd1.4modifiedbwangsrc/org/jboss/cache/eviction/BaseEvictionAlgorithm.javaChanged the log output level from warn to debug in removeQueue1.9modifiedmsurtanisrc/org/jboss/cache/Version.javaUpdated version1.4modifiedmsurtanisrc/org/jboss/cache/aop/util/AopUtil.javaJBCACHE-5021.5modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/VersionedTestBase.javaDon't leak ref to 'this' to Thread from CacheUser c'tor1.11modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransferAopTestBase.javaDon't leak ref to 'this' to Thread from CacheUser c'tor1.2modifiedbwangtests/scripts/benchmark.shClean up1.15modifiedbwangtests/perf/org/jboss/cache/Server.javaOutput average as well1.16modifiedbwangtests/perf/org/jboss/cache/Server.javaadded more stats1.5modifiedbwangtests/scripts/bench.txtupd1.2modifiedbwangtests/scripts/readme.txtupd1.2modifiedbwangtests/scripts/bench.xmlupdated xml1.17modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.3modifiedbwangtests/scripts/benchmark.shupd1.132modifiedbwangsrc/org/jboss/cache/TreeCache.javaAdded commented out section forJGroups jmx1.3modifiedbwangtests/scripts/readme.txtupd1.18modifiedbwangtests/perf/org/jboss/cache/Server.javachecked members than specified now1.133modifiedbwangsrc/org/jboss/cache/TreeCache.javaCommented out jgroups 2.3 features1.6modifiedbwangtests/scripts/bench.txtadded random sleep1.3modifiedbwangtests/scripts/bench.xmladded random sleep1.19modifiedbwangtests/perf/org/jboss/cache/Server.javaadded random sleep1.4modifiedgenmansrc/org/jboss/cache/eviction/EvictionTimerTask.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.7modifiedgenmansrc/org/jboss/cache/eviction/Region.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.12modifiedgenmansrc/org/jboss/cache/interceptors/CacheMgmtInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.8modifiedgenmansrc/org/jboss/cache/interceptors/CreateIfNotExistsInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.21modifiedgenmansrc/org/jboss/cache/interceptors/OptimisticValidatorInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.17modifiedgenmansrc/org/jboss/cache/interceptors/PassivationInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.35modifiedgenmansrc/org/jboss/cache/interceptors/TxInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.10modifiedgenmansrc/org/jboss/cache/loader/AsyncCacheLoader.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.9modifiedgenmansrc/org/jboss/cache/loader/FileCacheLoader.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.7modifiedgenmansrc/org/jboss/cache/loader/rmi/RemoteTreeCacheImpl.javaJBCACHE-484 - Clean up co
[JBoss-dev] 4.0.4
I am trying to nail down a short-term release schedule for Hibernate 3.2.x. Due to some of the changes made there specifically for EJB3 persistence support, I need to have a stable version of 3.2 done before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward. Is there an anticipated release date for 4.0.4 GA at this point? --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060320103744 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: 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: 03/20/2006 10:37:44Time to build: 20 minutes 23 secondsLast changed: 03/20/2006 09:55:35Last log entry: cleanup Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 130)1.103modifiedtdieslerwebservice/test/build.xmlRestore tests-toolsOther secions should be run likeant -Dtest=mysection test1.37modifiedhbraunwebservice/src/main/org/jboss/ws/metadata/wsdl/WSDL11Reader.javaW3C addressing test suite compliance1.31modifiedhbraunwebservice/src/main/org/jboss/ws/metadata/JSR109MetaDataBuilder.javaW3C addressing test suite compliance1.27modifiedhbraunwebservice/src/main/org/jboss/ws/metadata/OperationMetaData.javaW3C addressing test suite compliance1.2modifiedhbraunwebservice/src/resources/jbossws-eventing.war/WEB-INF/wsdl/jbwse.wsdlupdate to new addressing impl.1.5modifiedhbraunwebservice/test/build-interop-artifacts.xmlW3C addressing test suite compliance1.9modifiedhbraunwebservice/test/etc/log4j.xmlW3C addressing test suite compliance1.2modifiedhbraunwebservice/test/java/org/jboss/test/ws/addressing/EndpointReferenceTestCase.javaW3C addressing test suite compliance1.4modifiedhbraunwebservice/test/java/org/jboss/test/ws/addressing/SOAPAddressingPropertiesTestCase.javaW3C addressing test suite compliance1.5modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/DIIClientTestCase.javaW3C addressing test suite compliance1.9modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/EventingSupport.javaW3C addressing test suite compliance1.7modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/EventingTestCase.javaW3C addressing test suite compliance1.5modifiedhbraunwebservice/test/java/org/jboss/test/ws/eventing/NotificationTestCase.javaW3C addressing test suite compliance1.5modifiedhbraunwebservice/test/java/org/jboss/test/ws/interop/microsoft/addressing/wsa10/AddressingTestCase.javaW3C addressing test suite compliance1.3modifiedhbraunwebservice/test/java/org/jboss/test/ws/interop/microsoft/addressing/wsaTestService/WsaTestPortType_Impl.javaW3C addressing test suite compliance1.7modifiedhbraunwebservice/test/java/org/jboss/test/ws/samples/wsaddr/ClientHandler.javaW3C addressing test suite compliance1.3modifiedhbraunwebservice/test/resources/eventing/META-INF/application-client.xmlW3C addressing test suite compliance1.2modifiedhbraunwebservice/test/resources/eventing/WEB-INF/webservices.xmlW3C addressing test suite compliance1.4modifiedhbraunwebservice/test/resources/eventing/WEB-INF/wsdl/wind.wsdlW3C addressing test suite compliance1.3modifiedhbraunwebservice/test/resources/interop/microsoft/addressing/wsaTestService/WEB-INF/webservices.xmlW3C addressing test suite compliance1.1addedhbraunwebservice/src/main/org/jboss/ws/metadata/MetaDataExtension.javabase class for UMD extensions1.10modifiedhbraunwebservice/test/etc/log4j.xmlrevert local changes1.2modifiedhbraunwebservice/test/java/org/jboss/test/ws/interop/microsoft/addressing/wsaTestService/ConstraintHandler.javaW3C test suite compliance1.25modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/JavaToWSDL20TestCase.javaUpdate tools output dir1.37modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToJavaTestCase.javaUpdate tools output dir1.16modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToWSDL20TestCase.javaUpdate tools output dir1.6modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSToolsTest.javaUpdate tools output dir1.11modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/doclit/ToolsDocLitTestCase.javaUpdate tools output dir1.11modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/testsuitefixture/webservice/holders/HoldersTestCase.javaUpdate tools output dir1.21modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xmlschema/XercesSchemaParserTestCase.javaUpdate tools output dir1.10modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/AnonymousTypesTestCase.javaUpdate tools output dir1.11modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/ComplexTypesTestCase.javaUpdate tools output dir1.9modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/NillableTypesTestCase.javaUpdate tools output dir1.10modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/ReferencesTestCase.javaUpdate tools output dir1.9modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/xsdjava/SimpleTypesTestCase.javaUpdate tools output dir1.22modifiedtdieslerwebservice/test/jav
[JBoss-dev] jboss-seam-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060320102614 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:54: /services/cruisecontrol/work/scripts/test-output not found.Date of build: 03/20/2006 10:26:14Time to build: 1 minute 48 secondsLast changed: 03/20/2006 02:21:19Last log entry: Added support for StringBuilder/StringBuffer and Long types Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 169)1.1addedsbryzak2src/main/org/jboss/seam/remoting/BaseRequestHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.3modifiedsbryzak2src/main/org/jboss/seam/remoting/Call.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.2modifiedsbryzak2src/main/org/jboss/seam/remoting/CallContext.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.3modifiedsbryzak2src/main/org/jboss/seam/remoting/ExecutionHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.4modifiedsbryzak2src/main/org/jboss/seam/remoting/InterfaceGenerator.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/PollHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/RequestContext.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/RequestHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/RequestHandlerFactory.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.4modifiedsbryzak2src/main/org/jboss/seam/remoting/SeamRemotingServlet.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/SubscriptionHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.2modifiedsbryzak2src/main/org/jboss/seam/remoting/remote.jsRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/PollRequest.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/RemoteSubscriber.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/SubscriptionRegistry.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/SubscriptionRequest.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-
[JBoss-dev] microcontainer-head-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060320095930 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:41: Exit code: 1 See compilejbosshead.log in Build Artifacts for details.Date of build: 03/20/2006 09:59:30Time to build: 25 minutes 12 secondsLast changed: 03/20/2006 05:20:19Last log entry: Put BeanInfo.getDependencies() the way it was, i.e do not pass in the MetaDataContext Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 28)1.12modifiedkkhansrc/main/org/jboss/kernel/plugins/dependency/AbstractKernelControllerContext.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.23modifiedkkhansrc/main/org/jboss/kernel/plugins/dependency/KernelControllerContextActions.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.8modifiedkkhansrc/main/org/jboss/beans/info/plugins/AbstractBeanInfo.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.1addedkkhansrc/main/org/jboss/beans/info/plugins/AbstractInstanceBeanInfo.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.7modifiedkkhansrc/main/org/jboss/beans/info/spi/BeanInfo.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.4modifiedkkhansrc/main/org/jboss/classadapter/plugins/BasicClassAdapter.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.13modifiedkkhansrc/main/org/jboss/classadapter/spi/ClassAdapter.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.5modifiedkkhansrc/main/org/jboss/repository/spi/MetaDataContext.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the K
[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=log20060320083115 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: 03/20/2006 08:31:15Time to build: 78 minutes 38 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (356) Total Errors and Failures: (41)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)unknownorg.jboss.test.remoting.stream.StreamingTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(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 2211)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-276 - changed transporter client to throw origina
[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=log20060320080353 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: 03/20/2006 08:03:53Time to build: 20 minutes 11 secondsLast changed: 03/19/2006 21:55:40Last log entry: JBREM-346 - fix ConcurrentModificationException on cleanup Unit Tests: (176) Total Errors and Failures: (19)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization) Modifications since last build: (first 50 of 82)1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/http/timeout/TimeoutClientTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/http/timeout/TimeoutServerTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/http/timeout/TimeoutTestCase.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/timeout/TimeoutClientTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/timeout/TimeoutServerTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/timeout/TimeoutTestCase.javaJBREM-329 - added global timeout config property for all transports (client and server).1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexInvokerConfigTestClient.javaJBREM-329 - added global timeout config property for all transports (client and server).1.16modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexInvokerTestClient.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/rmi/timeout/TimeoutClientTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/rmi/timeout/TimeoutServerTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/rmi/timeout/TimeoutTestCase.javaJBREM-329 - added global timeout config property for all transports (client and server).1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-329 - added global timeout config pro
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060320072647 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: 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: 03/20/2006 07:26:47Time to build: 36 minutes 43 secondsLast changed: 03/19/2006 11:09:16Last log entry: Reduce logging level when releasing state transfer locks Unit Tests: (1376) Total Errors and Failures: (10)testSharedCacheLoadingWithReplicationorg.jboss.cache.optimistic.OptimisticWithCacheLoaderTesttestActiveTransactionorg.jboss.cache.statetransfer.ForcedStateTransferTesttestRollbackOnlyTransactionorg.jboss.cache.statetransfer.ForcedStateTransferTesttestHungThreadorg.jboss.cache.statetransfer.ForcedStateTransferTesttestBeforeCompletionLockorg.jboss.cache.statetransfer.ForcedStateTransferTesttestAfterCompletionLockorg.jboss.cache.statetransfer.ForcedStateTransferTesttestMultipleProblemsorg.jboss.cache.statetransfer.ForcedStateTransferTesttestSerializableIsolationorg.jboss.cache.statetransfer.ForcedStateTransferTesttestPartialStateTransferorg.jboss.cache.statetransfer.ForcedStateTransferTesttestReplSyncorg.jboss.cache.statetransfer.ForcedStateTransferTest Modifications since last build: (first 50 of 58)1.4modifiedbstansberrytests/functional/org/jboss/cache/GlobalTransactionTest.javaAdd a test that equals() handles null properly1.6modifiedbstansberrytests/functional/org/jboss/cache/FqnTest.javaAdd a test that equals() handles null and other types properly1.12modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.13modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.14modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.4modifiedbwangtests/scripts/bench.txtupd1.4modifiedbwangsrc/org/jboss/cache/eviction/BaseEvictionAlgorithm.javaChanged the log output level from warn to debug in removeQueue1.9modifiedmsurtanisrc/org/jboss/cache/Version.javaUpdated version1.4modifiedmsurtanisrc/org/jboss/cache/aop/util/AopUtil.javaJBCACHE-5021.5modifiedbstansberrytests/functional/org/jboss/cache/statetransfer/VersionedTestBase.javaDon't leak ref to 'this' to Thread from CacheUser c'tor1.11modifiedbstansberrytests/functional/org/jboss/cache/aop/statetransfer/StateTransferAopTestBase.javaDon't leak ref to 'this' to Thread from CacheUser c'tor1.2modifiedbwangtests/scripts/benchmark.shClean up1.15modifiedbwangtests/perf/org/jboss/cache/Server.javaOutput average as well1.16modifiedbwangtests/perf/org/jboss/cache/Server.javaadded more stats1.5modifiedbwangtests/scripts/bench.txtupd1.2modifiedbwangtests/scripts/readme.txtupd1.2modifiedbwangtests/scripts/bench.xmlupdated xml1.17modifiedbwangtests/perf/org/jboss/cache/Server.javaupd1.3modifiedbwangtests/scripts/benchmark.shupd1.132modifiedbwangsrc/org/jboss/cache/TreeCache.javaAdded commented out section forJGroups jmx1.3modifiedbwangtests/scripts/readme.txtupd1.18modifiedbwangtests/perf/org/jboss/cache/Server.javachecked members than specified now1.133modifiedbwangsrc/org/jboss/cache/TreeCache.javaCommented out jgroups 2.3 features1.6modifiedbwangtests/scripts/bench.txtadded random sleep1.3modifiedbwangtests/scripts/bench.xmladded random sleep1.19modifiedbwangtests/perf/org/jboss/cache/Server.javaadded random sleep1.4modifiedgenmansrc/org/jboss/cache/eviction/EvictionTimerTask.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.7modifiedgenmansrc/org/jboss/cache/eviction/Region.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.12modifiedgenmansrc/org/jboss/cache/interceptors/CacheMgmtInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.8modifiedgenmansrc/org/jboss/cache/interceptors/CreateIfNotExistsInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.21modifiedgenmansrc/org/jboss/cache/interceptors/OptimisticValidatorInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.17modifiedgenmansrc/org/jboss/cache/interceptors/PassivationInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.35modifiedgenmansrc/org/jboss/cache/interceptors/TxInterceptor.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.10modifiedgenmansrc/org/jboss/cache/loader/AsyncCacheLoader.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.9modifiedgenmansrc/org/jboss/cache/loader/FileCacheLoader.javaJBCACHE-484 - Clean up code Fix some race conditions and synchronization issues1.7modifiedgenmansrc/org/jboss/cache/loader/rmi/RemoteTreeCacheImpl.javaJBCACHE-484 - Clean up code F
RE: [JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4
Ryan, When you are ready with jbossretro, pls create a jira task for me to produce a snapshot that uses jbossretro. The jira task should conatin instructions on howto run the build using jbossretro. Cheers -thomas xxx Thomas Diesler Web Service Lead JBoss Inc. xxx >-Original Message- >From: Ryan Campbell >Sent: Saturday, March 18, 2006 18:46 >To: Jason T. Greene; Thomas Diesler >Cc: QA; 'jboss-development@lists.sourceforge.net' >Subject: RE: [JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4 > >I didn't realize they were versioned together, but this makes sense. > >So the question is, is webservices ready for a 1.0.0.CR4? > >I have tested webservices snapshot code with >jboss-4.0/testsuite (weaved with jbossretro and >retrotranslator) and got the following error: > >Suite: org.jboss.test.webservice.samples.ServerSideJMSTestCase >Test:testSOAPMessageToEndpointQueue >Type:error >Exception: javax.naming.NameNotFoundException >Message: MessageDrivenEndpointQueue not bound > >-Original Message- >From: Jason T. Greene >Sent: Saturday, March 18, 2006 12:07 AM >To: jboss-development@lists.sourceforge.net; Thomas Diesler >Cc: QA; Adrian Brock >Subject: RE: [JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4 > >Codewise, they are identical. The intention is to maintain one >codebase across both versions of the JDK. So there is no need >for another tag. > >-Jason > >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:jboss- >> [EMAIL PROTECTED] On Behalf Of Ryan Campbell >> Sent: Friday, March 17, 2006 11:19 AM >> To: Thomas Diesler >> Cc: QA; Adrian Brock; jboss-development >> Subject: [JBoss-dev] RE: JBossRetro, JBossWS and JDK1.4 >> >> Thomas, >> >> I noticed that you have tags for JBOSSWS_1_0_* but not specifically >> for JBossWS14. So do the versions for jbossws14 in the repository >> correspond to the JBOSSWS_1_0_* tags? >> >> http://repository.jboss.com/jboss/jbossws14/ >> >> I was planning on creating a JBossWS14_1_0_0_CR3, but I see >you have a >> JBOSSWS_1_0_RC3. >> >> What is the relationship between jbossws releases to >jbossws14 releases? >> > > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: repository.jboss.com checkout problem
FYI, svn is much better about this. It does not distinguish between txt and binary (i.e. it does not rewrite CR/LF) and uses a binary diff algorithm http://svnbook.red-bean.com/nightly/en/svn.forcvs.binary-and-trans.html xxx Thomas Diesler Web Service Lead JBoss Inc. xxx >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On >Behalf Of Jason T. Greene >Sent: Saturday, March 18, 2006 20:04 >To: Dimitris Andreadis; >jboss-development@lists.sourceforge.net; Anil Saldhana >Cc: QA >Subject: RE: [JBoss-dev] Re: repository.jboss.com checkout problem > >It uses one gigantic RCS file with markers to distinguish the versions. >So if you have 10 updates to a 100 meg file, you get a gig >file. So don't ever store iso files in CVS :) > >-Jason > >> -Original Message- >> From: Dimitris Andreadis >> Sent: Saturday, March 18, 2006 2:59 AM >> To: Jason T. Greene; 'jboss-development@lists.sourceforge.net'; Anil >> Saldhana >> Cc: QA >> Subject: RE: [JBoss-dev] Re: repository.jboss.com checkout problem >> >> >> Jason, for every binary file, does it make a new physical file, or is >it >> one big file with some sort of marking to distinguish the >entries? CVS >is >> really bad with binaries, more so big ones... >> >> > -Original Message- >> > From: Jason T. Greene >> > Sent: 18 March, 2006 08:16 >> > To: jboss-development@lists.sourceforge.net; Anil Saldhana >> > Cc: QA >> > Subject: RE: [JBoss-dev] Re: repository.jboss.com checkout problem >> > >> > Cvs doesn't actually have a diff algorithm for binary >files, what it >> > does is store an entire copy for every single change and branch >> > point in the same file. >> > >> > When we move to subversion this problem goes away because >it uses a >> > binary diff algorithm, reducing storage and network overhead. >> > >> > -Jason >> > >> > > -Original Message- >> > > From: [EMAIL PROTECTED] >[mailto:jboss- >> > > [EMAIL PROTECTED] On Behalf Of >Adrian Brock >> > > Sent: Friday, March 17, 2006 12:42 PM >> > > To: Anil Saldhana >> > > Cc: jboss-development; QA >> > > Subject: [JBoss-dev] Re: repository.jboss.com checkout problem >> > > >> > > On Fri, 2006-03-17 at 11:51 -0600, Anil Saldhana wrote: >> > > > Adrian Brock wrote: >> > > > >> > > > >Anybody else having problems checking out from cvs? >> > > > > >> > > > >It is getting stuck here: >> > > > >cvs update: Updating eclipse/sdk/3.1.1 U >> > > > >eclipse/sdk/3.1.1/eclipse-SDK-3.1.1-linux-gtk.tar.gz >> > > > > >> > > > >I tried cancelling it and restarting, but it still gets stuck? >> > > > > >> > > > > >> > > > Doesn't CVS do diffs on the server and need to have >> > atleast 10 times >> > > > RAM the size of the file? >> > > >> > > It looks like this is correct, it has got past eclipse now. >> > > It definitely stalled at one point though, unless 2 hours >> > is typical >> > > to download eclipse? :-) >> > > -- >> > > >> > > Adrian Brock >> > > Chief Scientist >> > > JBoss Inc. >> > > >> > > >> > > >> > > >> > > --- >> > > This SF.Net email is sponsored by xPML, a groundbreaking >scripting >> > > language that extends applications into web and mobile >> > media. Attend >> > > the live webcast and join the prime developer group >> > breaking into this >> > > new coding territory! >> > > >> > >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=1216 >> > > 42 ___ >> > > JBoss-Development mailing list >> > > JBoss-Development@lists.sourceforge.net >> > > https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > >--- >This SF.Net email is sponsored by xPML, a groundbreaking >scripting language that extends applications into web and >mobile media. Attend the live webcast and join the prime >developer group breaking into this new coding territory! >http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 >___ >JBoss-Development mailing list >JBoss-Development@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
