[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=log20060407221812 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: 04/07/2006 22:18:12Time to build: 106 minutes 50 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (350) Total Errors and Failures: (23)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(jboss_serialization)testStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.http.VersionHTTPInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.multiplex.VersionMultiplexInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.rmi.VersionRMIInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCasetestStartorg.jboss.test.remoting.versioning.transport.socket.VersionSocketInvokerTestCase Modifications since last build: (first 50 of 2354)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/ComplexObject.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServerImpl.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TransporterTestCase.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javabranches: 1.5.4;JBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleClient.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-253 - changed to use coyote connector by default instead
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407193805 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:78: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 04/07/2006 19:38:05Time to build: 18 minutes 57 secondsLast changed: 04/07/2006 19:08:38Last log entry: Disable until catalog support is fixed Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 61)1.2modifiedjgreenetestsuite/src/main/org/jboss/test/common/JBossEntityResolverTest.javaDisable until catalog support is fixed1.2modifiedjgreenetestsuite/src/main/org/jboss/test/common/ResolverTest.javaDisable until catalog support is fixed1.1addedbdecosteejb3/src/test/org/jboss/ejb3/test/naming/unit/BindingTestCase.javatest for removal of NamingContexts on undeploy1.44modifiedbdecostenaming/src/main/org/jnp/interfaces/NamingContext.javaimplemented destroySubcontext(...)1.3modifiedovidiujms/src/etc/server/default/deploy/jms-ds.xmlFix for http://jira.jboss.org/jira/browse/JBMESSAGING-3231.11modifiedovidiujms/tests/smoke/build.xmlsmoke test exits with error if detects errors in the server's log1.2modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javasmoke test exits with error if detects errors in the server's log1.2modifiedovidiujms/docs/examples/mdb/etc/META-INF/ejb-jar.xmlmade the MDB deployment descriptor spec compliant1.21modifieddimitristestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaJBAS-2774, make the DateEditor work with different Locales1.10modifiedovidiujms/tests/smoke/build.xmlThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.3modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/client/JChannelClient.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedtdieslertestsuite/src/main/org/jboss/test/common/JBossEntityResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/main/org/jboss/test/common/ResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_0.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_2.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/security_config.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslerserver/src/etc/conf/default/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogManager.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Resolver.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Version.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/package.html[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/ExtendedXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/OASISXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXParserHandler.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/TR9401CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslerc
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407185832 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:78: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 04/07/2006 18:58:32Time to build: 21 minutes 4 secondsLast changed: 04/07/2006 18:46:35Last log entry: test for removal of NamingContexts on undeploy Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 58)1.1addedbdecosteejb3/src/test/org/jboss/ejb3/test/naming/unit/BindingTestCase.javatest for removal of NamingContexts on undeploy1.44modifiedbdecostenaming/src/main/org/jnp/interfaces/NamingContext.javaimplemented destroySubcontext(...)1.3modifiedovidiujms/src/etc/server/default/deploy/jms-ds.xmlFix for http://jira.jboss.org/jira/browse/JBMESSAGING-3231.11modifiedovidiujms/tests/smoke/build.xmlsmoke test exits with error if detects errors in the server's log1.2modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javasmoke test exits with error if detects errors in the server's log1.2modifiedovidiujms/docs/examples/mdb/etc/META-INF/ejb-jar.xmlmade the MDB deployment descriptor spec compliant1.21modifieddimitristestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaJBAS-2774, make the DateEditor work with different Locales1.10modifiedovidiujms/tests/smoke/build.xmlThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.3modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/client/JChannelClient.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedtdieslertestsuite/src/main/org/jboss/test/common/JBossEntityResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/main/org/jboss/test/common/ResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_0.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_2.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/security_config.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslerserver/src/etc/conf/default/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogEntry.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogException.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogManager.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Resolver.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Version.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/package.html[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/ExtendedXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/OASISXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXParserHandler.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/TR9401CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407163521 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: 04/07/2006 16:35:21Time to build: 25 minutes 48 secondsLast changed: 04/07/2006 16:25:51Last log entry: JBADMCON-79 Added test cases for DeploymentServiceJmsHelper and fixed a class load problem in MBeanServerJmsHelperTest. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 56)1.11modifiedovidiujms/tests/smoke/build.xmlsmoke test exits with error if detects errors in the server's log1.2modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javasmoke test exits with error if detects errors in the server's log1.2modifiedovidiujms/docs/examples/mdb/etc/META-INF/ejb-jar.xmlmade the MDB deployment descriptor spec compliant1.2deletedjerrygauthnaming/src/main/org/jboss/naming/NamingDiscovery.javaRemoved interface added for JBAS-2957 as this issue is being reviewed1.21modifieddimitristestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaJBAS-2774, make the DateEditor work with different Locales1.10modifiedovidiujms/tests/smoke/build.xmlThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.3modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/client/JChannelClient.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedtdieslertestsuite/src/main/org/jboss/test/common/JBossEntityResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/main/org/jboss/test/common/ResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_0.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_2.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/security_config.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslerserver/src/etc/conf/default/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Catalog.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogEntry.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogException.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogManager.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Resolver.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Version.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/package.html[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/ExtendedXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/OASISXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXParserHandler.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/TR9401CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese
RE: [JBoss-dev] Unassigned for 4.0.4
Thanks to everyone that responded. I understand now. On Fri, 2006-04-07 at 08:07 -0500, Steve Ebersole wrote: > Just so it is perfectly clear: > > Hibernate does not use its cache providers in any way, shape or form for > implementing the "first level cache". As Max mentioned, the "first > level cache" is really just a particular aspect of the role fulfilled by > the org.hibernate.engine.PersistenceContext implementation which > internally uses a series of maps. > > Thus, no need to bundle ehcache at all unless a user wants to use that > as their second level cache. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Scott Marlow > Sent: Tuesday, April 04, 2006 10:12 AM > To: jboss-development@lists.sourceforge.net > Subject: Re: [JBoss-dev] Unassigned for 4.0.4 > > On Tue, 2006-04-04 at 15:56 +0200, Max Rydahl Andersen wrote: > > On Tue, 04 Apr 2006 15:44:51 +0200, Scott Marlow > > <[EMAIL PROTECTED]> wrote: > > > > > Sounds good to me. My next question is how do we tell Hibernate to > use > > > JBoss Cache as the first level cache? > > > > *first* level cache ? Why would you ever want that ? > > > > You mean second level cache, right ? > I mean first level cache, which by default is using ehcache-1.1.jar > (jira JBAS-2868). We don't include ehcache-1.1.jar with the 4.0.4 as > release which is why it cannot be resolved. I would like to use jboss > cache instead as the first level cache but am not sure if Hibernate > allows that. > > > > > > --- > 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 --- 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-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407134808 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: 04/07/2006 13:48:08Time to build: 25 minutes 51 secondsLast changed: 04/07/2006 13:37:54Last log entry: JBAS-2774, make the DateEditor work with different Locales Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 48)1.21modifieddimitristestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaJBAS-2774, make the DateEditor work with different Locales1.9modifieddimitriscommon/src/main/org/jboss/util/propertyeditor/DateEditor.javaJBAS-2774, make the DateEditor work with different Locales1.10modifiedovidiujms/tests/smoke/build.xmlThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.3modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/client/JChannelClient.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedtdieslertestsuite/src/main/org/jboss/test/common/JBossEntityResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/main/org/jboss/test/common/ResolverTest.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_0.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_2.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/security_config.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslerserver/src/etc/conf/default/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Catalog.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogEntry.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogException.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/CatalogManager.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Resolver.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/Version.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/package.html[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/DOMCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/ExtendedXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/OASISXMLCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogParser.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/SAXParserHandler.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/TR9401CatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/TextCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/XCatalogReader.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/catalog/readers/package.html[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/
[JBoss-dev] jboss-head-jdk-matrix Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060407125847 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: 04/07/2006 12:58:47Time to build: 15 minutes 14 secondsLast changed: 04/07/2006 12:50:16Last log entry: The smoke test detects and display WARN/ERROR entries in the tested server log. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 20)1.10modifiedovidiujms/tests/smoke/build.xmlThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedovidiujms/tests/src/org/jboss/test/messaging/tools/ant/DisplayWarningsAndErrors.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.3modifiedovidiujms/tests/src/org/jboss/test/messaging/tools/client/JChannelClient.javaThe smoke test detects and display WARN/ERROR entries in the tested server log.1.1addedtdieslertestsuite/src/resources/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_0.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/jboss_xmbean_1_2.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslertestsuite/src/resources/dtd/security_config.dtd[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslerserver/src/etc/conf/default/jax-ws-catalog.xml[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.1addedtdieslercommon/src/main/org/jboss/util/xml/CatalogLocation.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.40modifiedtdieslercommon/src/main/org/jboss/util/xml/JBossEntityResolver.java[JBWS-678] - OASIS Catalog supportThanks Daniel Wiese1.34modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCAbstractQueryCommand.java[JBAS-1296] EJB-QL CMR traversal returns wrong interface type1.31modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCCommandFactory.java[JBAS-1296] EJB-QL CMR traversal returns wrong interface type1.10modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCFindAllQuery.java[JBAS-1296] EJB-QL CMR traversal returns wrong interface type1.10modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCFindByQuery.java[JBAS-1296] EJB-QL CMR traversal returns wrong interface type1.24modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCQueryManager.java[JBAS-1296] EJB-QL CMR traversal returns wrong interface type1.16modifiedaloubyanskytestsuite/src/resources/cmp2/commerce/META-INF/ejb-jar.xmlcorrected abstract schema name in the finder1.33modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCAbstractQueryCommand.java[JBAS-1550] JDBCEJBQLCompiler generates a non valid query1.43modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCEJBQLCompiler.java[JBAS-1550] JDBCEJBQLCompiler generates a non valid query1.14modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCFindByPrimaryKeyQuery.java[JBAS-1550] JDBCEJBQLCompiler generates a non valid query1.18modifiedaloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/EJBQLToSQL92Compiler.javacleanup
[JBoss-dev] catalog does not work for remote clients
Hi Jason/Scott, the new catalog support in jboss-head does not work for remote clients. I need to look into it on monday. Have a good weekend -thomas
[JBoss-dev] Re: Toward JBoss v4.0.4.GA - Part 1 - JIRA tasks
That's what I was afraid of. Dimitris Andreadis wrote: It's not planned. Some do individual TCK testing (e.g. WS). -Original Message- From: Alexey Loubyansky Sent: 07 April, 2006 15:42 To: Dimitris Andreadis Cc: jboss-development Subject: Re: Toward JBoss v4.0.4.GA - Part 1 - JIRA tasks Are the J2EE TCK tests part of the QA procedure before the release? Dimitris Andreadis wrote: When we started work on 4.0.4 we had 300+ issues ahead of us, now after 2 candidate releases we are down to around 80, which is quite an achievement, but still a significant amount of work is left for the final (GA) release. The current target date is 26th/April which includes Easter and is just 3 weeks ahead of us. This gives roughly 2 weeks of bug fixing and 1 week of integration testing. New features shouldn't be introduced at this point. Please take a look at the issues assigned to you and resolve/defer in time: http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reques tI d=12310181 Take a look at the unassigned ones and help: http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reques tI d=12310482 The current breakout is roughly shown below. NoComponent 3 Build 2 Clustering 7 CMP 13 Deployment 3 Documentation 1 (+ 6 dependencies) EJB 10 (6 unassigned) Hibernate 1 IIOP2 Installer 5 (5 unassigned) JCA 1 JMX 5 (1 unassigned) Logging 1 Management 2 Naming 1 Other 1 Remoting6 Security6 (1 unassigned) System 1 Testsuite 5 (1 unassigned) Tomcat 6 WebServices 3 XML 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&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] RE: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues
Coincidence. > -Original Message- > From: Steve Ebersole > Sent: 07 April, 2006 16:00 > To: Dimitris Andreadis; 'jboss-development' > Cc: The Core > Subject: RE: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues > > Hibernate will stay at a CR; it will not go final until the > EBJ3 spec is final... > > BTW, what is with Javassist being at the same exact version? > Is that just coincidence? > > > -Original Message- > From: Dimitris Andreadis > Sent: Wednesday, April 05, 2006 5:33 AM > To: jboss-development > Cc: The Core > Subject: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues > Importance: High > > > Various Issues > -- > > - Breakage of jboss commons. Is this the right time, or > should do for 4.0.5. Aren't we already overloaded? Who & How? > > - Which thirdparty libs can be removed? So far I've noticed > apache-wss4j & apache-jaxme. > > - JBoss.Net is not even included in the docs/examples now. > Should it be removed from the 4.0.x module checkout? > > - The following jboss lists are *NOT* final (GA). What will > be updated for 4.0.4.GA? Project leads speak! > > > > > > > > > > > > > > > > > > -- > xxx > Dimitris Andreadis > Core Developer > JBoss Europe SàRL > xxx > --- 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] RE: Toward JBoss v4.0.4.GA - Part 1 - JIRA tasks
It's not planned. Some do individual TCK testing (e.g. WS). > -Original Message- > From: Alexey Loubyansky > Sent: 07 April, 2006 15:42 > To: Dimitris Andreadis > Cc: jboss-development > Subject: Re: Toward JBoss v4.0.4.GA - Part 1 - JIRA tasks > > Are the J2EE TCK tests part of the QA procedure before the release? > > Dimitris Andreadis wrote: > > When we started work on 4.0.4 we had 300+ issues ahead of us, now > > after > > 2 candidate releases we are down to around 80, which is quite an > > achievement, but still a significant amount of work is left for the > > final (GA) release. > > > > The current target date is 26th/April which includes Easter and is > > just > > 3 weeks ahead of us. This gives roughly 2 weeks of bug fixing and 1 > > week of integration testing. New features shouldn't be > introduced at > > this point. > > > > Please take a look at the issues assigned to you and > resolve/defer in > > time: > > > http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reques > > tI > > d=12310181 > > > > Take a look at the unassigned ones and help: > > > http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reques > > tI > > d=12310482 > > > > The current breakout is roughly shown below. > > > > NoComponent 3 > > Build 2 > > Clustering 7 > > CMP 13 > > Deployment 3 > > Documentation 1 (+ 6 dependencies) > > EJB 10 (6 unassigned) > > Hibernate 1 > > IIOP2 > > Installer 5 (5 unassigned) > > JCA 1 > > JMX 5 (1 unassigned) > > Logging 1 > > Management 2 > > Naming 1 > > Other 1 > > Remoting6 > > Security6 (1 unassigned) > > System 1 > > Testsuite 5 (1 unassigned) > > Tomcat 6 > > WebServices 3 > > XML 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] Unassigned for 4.0.4
Just so it is perfectly clear: Hibernate does not use its cache providers in any way, shape or form for implementing the "first level cache". As Max mentioned, the "first level cache" is really just a particular aspect of the role fulfilled by the org.hibernate.engine.PersistenceContext implementation which internally uses a series of maps. Thus, no need to bundle ehcache at all unless a user wants to use that as their second level cache. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Marlow Sent: Tuesday, April 04, 2006 10:12 AM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] Unassigned for 4.0.4 On Tue, 2006-04-04 at 15:56 +0200, Max Rydahl Andersen wrote: > On Tue, 04 Apr 2006 15:44:51 +0200, Scott Marlow > <[EMAIL PROTECTED]> wrote: > > > Sounds good to me. My next question is how do we tell Hibernate to use > > JBoss Cache as the first level cache? > > *first* level cache ? Why would you ever want that ? > > You mean second level cache, right ? I mean first level cache, which by default is using ehcache-1.1.jar (jira JBAS-2868). We don't include ehcache-1.1.jar with the 4.0.4 as release which is why it cannot be resolved. I would like to use jboss cache instead as the first level cache but am not sure if Hibernate allows that. --- 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] RE: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues
Hibernate will stay at a CR; it will not go final until the EBJ3 spec is final... BTW, what is with Javassist being at the same exact version? Is that just coincidence? -Original Message- From: Dimitris Andreadis Sent: Wednesday, April 05, 2006 5:33 AM To: jboss-development Cc: The Core Subject: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues Importance: High Various Issues -- - Breakage of jboss commons. Is this the right time, or should do for 4.0.5. Aren't we already overloaded? Who & How? - Which thirdparty libs can be removed? So far I've noticed apache-wss4j & apache-jaxme. - JBoss.Net is not even included in the docs/examples now. Should it be removed from the 4.0.x module checkout? - The following jboss lists are *NOT* final (GA). What will be updated for 4.0.4.GA? Project leads speak! -- xxx Dimitris Andreadis Core Developer JBoss Europe SàRL xxx --- 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] Re: Toward JBoss v4.0.4.GA - Part 1 - JIRA tasks
Are the J2EE TCK tests part of the QA procedure before the release? Dimitris Andreadis wrote: When we started work on 4.0.4 we had 300+ issues ahead of us, now after 2 candidate releases we are down to around 80, which is quite an achievement, but still a significant amount of work is left for the final (GA) release. The current target date is 26th/April which includes Easter and is just 3 weeks ahead of us. This gives roughly 2 weeks of bug fixing and 1 week of integration testing. New features shouldn't be introduced at this point. Please take a look at the issues assigned to you and resolve/defer in time: http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestI d=12310181 Take a look at the unassigned ones and help: http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestI d=12310482 The current breakout is roughly shown below. NoComponent 3 Build 2 Clustering 7 CMP 13 Deployment 3 Documentation 1 (+ 6 dependencies) EJB 10 (6 unassigned) Hibernate 1 IIOP2 Installer 5 (5 unassigned) JCA 1 JMX 5 (1 unassigned) Logging 1 Management 2 Naming 1 Other 1 Remoting6 Security6 (1 unassigned) System 1 Testsuite 5 (1 unassigned) Tomcat 6 WebServices 3 XML 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&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] JBossCache 1.3.0.SP1 (WAS: JBossCache 1.3.0.GA released)
I have created a new release in JIRA - 1.3.0.SP1Could you pls mark these JIRA tasks as targets for fixing in both 1.4.0 and 1.3.0.SP1 - makes it easy for me to create release notes for 1.3.0.SP1. Please do so even if you've already fixed and closed the JIRA tasks.Thanks!--Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 6 Apr 2006, at 19:02, Manik Surtani wrote:Ok, so I have created a branch - Branch_JBossCache_1_3_0Could we make sure any potential fixes for an SP release go here as well as in HEAD.From what I can tell, we have:* Ben's SFSB fixes* The fix to the examples build script* Potential problem with the TreeCache GUI* JBCACHE-531 (Forcing file encodings when reading properties)* JBCACHE-548 (to do with TxManagers in WebLogic and WebSphere)* JBCACHE-534 (documentation typo)What else is critical for this SP? Do we have JIRA tasks for the first 3?Cheers, --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 6 Apr 2006, at 15:55, Ben Wang wrote: What tutorial? It is not broken, AFAIK. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 8:16 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released Ok. Has the tutorial been fixed as well? -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 6 Apr 2006, at 12:36, Ben Wang wrote: Yes, it has. The other two are almost done. Scott Marlow and I need to verify JBCACHE-531 fix. I'd say let's go for QA next Monday then? -Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 5:51 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released This is a better case. The tutorial issue on its own was not strong enough, IMO. :) Ben, is this fixed in HEAD at the moment?Cheers,-- Manik Surtani [EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtaniOn 5 Apr 2006, at 21:55, Ryan Campbell wrote: Is this (and the tutorial issue) not a good reason for 1.3.1.CR1? And then 1 week later, once we have a bug free release, we just rename (and retag it) as 1.3.1.GA.From: Ben Wang Sent: Tuesday, April 04, 2006 8:42 PMTo: jboss-development@lists.sourceforge.netCc: QASubject: RE: [JBoss-dev] JBossCache 1.3.0.GA releasedI know this not good timing. :-) But during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500), I have discovered two bugs. And I will need these two fixed so I can check in my code in head. So first option is to create a patch and use that. Second option is use the snapshot in JBossCache and couting on that 1.4 release will be out soon.I am leaning towards the second option such that if there is any future bug fixes or enahncement then I can create another shapshot right away. What do people think? And how do I do that properly?Thanks,-Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rajesh RajasekaranSent: Tuesday, April 04, 2006 6:04 AMTo: jboss-development@lists.sourceforge.netCc: QASubject: [JBoss-dev] JBossCache 1.3.0.GA releasedJBossCache 1.3.0.GA “Wasabi” has been released and is available for download athttp://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920JBossCache 1.3.0.GA has also been updated in the repository.ThanksRajeshJBoss QA
RE: [JBoss-dev] JBossCache 1.3.0.GA released + a change to how we deal with java.util.properties
Is this related to http://jira.jboss.com/jira/browse/JBAS-1888 ?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Ben Wang
> Sent: 07 April, 2006 10:35
> To: jboss-development@lists.sourceforge.net
> Cc: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] JBossCache 1.3.0.GA released + a
> change to how we deal with java.util.properties
>
> I agree with Manik here. If it is user-specified, we mandate
> them to escape it themselves for Windows. But we need to do
> the same for our own AS path variable like ${jboss.server.data.dir}.
>
> I'd say let's open a Jira and fix this in jboss-head only
> since we are moving to 5.0, AFAIK.
>
> -Ben
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Manik Surtani
> Sent: Thursday, April 06, 2006 10:33 PM
> To: jboss-development@lists.sourceforge.net
> Cc: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] JBossCache 1.3.0.GA released + a
> change to how we deal with java.util.properties
>
> Escaping single backslashes is probably not a good idea.
> What if I want to pass in (for some obscure reason) a \n ?
> I'd expect this to be translated to a new line, not the string "\\n".
>
> I think we just mandate that users passing in backslashes as
> a part of a path construct use double-backslashes. Fair
> assumption I'd assume (it's what I'd do anyway if specifying
> Windows paths in a Java
> propfile.)
>
>
> --
> Manik Surtani
> [EMAIL PROTECTED]
>
> Lead, JBoss Cache
>
> Telephone: +44 7786 702 706
> MSN: [EMAIL PROTECTED]
> Yahoo: maniksurtani
> AIM: maniksurtani
> Skype: maniksurtani
>
>
> On 6 Apr 2006, at 14:12, Scott Marlow wrote:
>
> > It turns out that the root cause behind JBCACHE-531 is
> deeper than I
> > thought.
> >
> > After fixing a minor international character support issue in
> > org.jboss.cache.config.CacheLoaderConfig (we were calling
> > String.getBytes() without specifying an encoding). I then
> came across
> > the same issue in
> > org.jboss.util.propertyeditor.PropertiesEditor.getValue(). I fixed
> > the character encoding issue locally but I'm not sure of how to fix
> > the deeper issue.
> >
> > Before I move into the deeper issue, let me explain the
> problem with
> > calling String.getBytes() without specifying an encoding (before
> > someone flames me :). String.getBytes() will return a byte array
> > containing the character values converted into the default platform
> > encoding (perhaps
> > big5 or utf8 or perhaps latin1). In the two code sites mentioned
> > above, we are passing the byte array into
> java.util.properties which
> > always wants encoding "ISO8859_1".
> >
> > The deeper issue:
> >
> > org.jboss.util.propertyeditor.PropertiesEditor.getValue()
> is expected
> > to take a Java String value and parse it java.util.properties style.
> > However, we also support expanding JBoss system expressions
> that can
> > be invalid when passed into java.util.properties.load() as we do.
> >
> > For example, if the expression "${jboss.server.data.dir}"
> is passed in
> > and you are running on Windows, the intermediate result
> might be path
> > "c:\jboss\server\all\data". The output of
> java.util.properties.load
> > will be something like: "c: boss erver ll ata".
> >
> > This creates a blocking problem for our sfsb fine grained
> replication
> > project. :(
> >
> > Should we try to hack the expansion of jboss system expressions to
> > double escape the "\" escape character?
> >
> > This seems like a tricky path to follow as I'm not sure if
> we should
> > do the same for values that are simply passed in. For
> instance, are
> > users expected to hard code paths in configuration files like this?
> >
> > mytempdir=c:\temp
> >
> > or like this:
> >
> > mytempdir=c:\\temp
> >
> > In one case, they already hit the bug that requires "\" to
> be doubled.
> > If I add code that doubles their "\", then we might end up with
> > something like "mytempdir=c:temp" (assuming that they already
> > doubled them). I suppose we could detect if the "\" characters are
> > already escaped and don't escape them again if so.
> >
> > This also seems like a big change to make so near the end
> of the 4.0.4
> > release. I'll create a Jira for 4.0.4 unless someone talks
> me out of
> > making this change.
> >
> > What is the right thing to do here?
> >
> >
> > On Thu, 2006-04-06 at 06:36 -0500, Ben Wang wrote:
> >> Yes, it has. The other two are almost done. Scott Marlow
> and I need
> >> to verify JBCACHE-531 fix. I'd say let's go for QA next
> Monday then?
> >>
> >> -Ben
> >
> >
> >
> > ---
> > 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!
>
RE: [JBoss-dev] JBossCache 1.3.0.GA released + a change to how we deal with java.util.properties
I agree with Manik here. If it is user-specified, we mandate them to escape it
themselves for Windows. But we need to do the same for our own AS path variable
like ${jboss.server.data.dir}.
I'd say let's open a Jira and fix this in jboss-head only since we are moving
to 5.0, AFAIK.
-Ben
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manik Surtani
Sent: Thursday, April 06, 2006 10:33 PM
To: jboss-development@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossCache 1.3.0.GA released + a change to how we deal
with java.util.properties
Escaping single backslashes is probably not a good idea. What if I want to
pass in (for some obscure reason) a \n ? I'd expect this to be translated to a
new line, not the string "\\n".
I think we just mandate that users passing in backslashes as a part of a path
construct use double-backslashes. Fair assumption I'd assume (it's what I'd do
anyway if specifying Windows paths in a Java
propfile.)
--
Manik Surtani
[EMAIL PROTECTED]
Lead, JBoss Cache
Telephone: +44 7786 702 706
MSN: [EMAIL PROTECTED]
Yahoo: maniksurtani
AIM: maniksurtani
Skype: maniksurtani
On 6 Apr 2006, at 14:12, Scott Marlow wrote:
> It turns out that the root cause behind JBCACHE-531 is deeper than I
> thought.
>
> After fixing a minor international character support issue in
> org.jboss.cache.config.CacheLoaderConfig (we were calling
> String.getBytes() without specifying an encoding). I then came across
> the same issue in
> org.jboss.util.propertyeditor.PropertiesEditor.getValue(). I fixed
> the character encoding issue locally but I'm not sure of how to fix
> the deeper issue.
>
> Before I move into the deeper issue, let me explain the problem with
> calling String.getBytes() without specifying an encoding (before
> someone flames me :). String.getBytes() will return a byte array
> containing the character values converted into the default platform
> encoding (perhaps
> big5 or utf8 or perhaps latin1). In the two code sites mentioned
> above, we are passing the byte array into java.util.properties which
> always wants encoding "ISO8859_1".
>
> The deeper issue:
>
> org.jboss.util.propertyeditor.PropertiesEditor.getValue() is expected
> to take a Java String value and parse it java.util.properties style.
> However, we also support expanding JBoss system expressions that can
> be invalid when passed into java.util.properties.load() as we do.
>
> For example, if the expression "${jboss.server.data.dir}" is passed in
> and you are running on Windows, the intermediate result might be path
> "c:\jboss\server\all\data". The output of java.util.properties.load
> will be something like: "c: boss erver ll ata".
>
> This creates a blocking problem for our sfsb fine grained replication
> project. :(
>
> Should we try to hack the expansion of jboss system expressions to
> double escape the "\" escape character?
>
> This seems like a tricky path to follow as I'm not sure if we should
> do the same for values that are simply passed in. For instance, are
> users expected to hard code paths in configuration files like this?
>
> mytempdir=c:\temp
>
> or like this:
>
> mytempdir=c:\\temp
>
> In one case, they already hit the bug that requires "\" to be doubled.
> If I add code that doubles their "\", then we might end up with
> something like "mytempdir=c:temp" (assuming that they already
> doubled them). I suppose we could detect if the "\" characters are
> already escaped and don't escape them again if so.
>
> This also seems like a big change to make so near the end of the 4.0.4
> release. I'll create a Jira for 4.0.4 unless someone talks me out of
> making this change.
>
> What is the right thing to do here?
>
>
> On Thu, 2006-04-06 at 06:36 -0500, Ben Wang wrote:
>> Yes, it has. The other two are almost done. Scott Marlow and I need
>> to verify JBCACHE-531 fix. I'd say let's go for QA next Monday then?
>>
>> -Ben
>
>
>
> ---
> 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&kid=110944&bid=241720&dat=121642
___
JBoss-Dev
