[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060407005051
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 00:50:51Time to build: 110 minutes 49 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup.




    Unit Tests: (351)    Total Errors and Failures: (26)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.http.ssl.basic.HTTPSInvokerTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase(java_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.VersionSocketInvokerTestCaseunknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase(java_serialization) 
 Modifications since last build: (first 50 of 2349)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 l

RE: [JBoss-dev] 5.0..0 Release Schedule

2006-04-06 Thread Adrian Brock
Ok with me.

On Thu, 2006-04-06 at 20:22 -0500, Brian Stansberry wrote:
> Hi Adrian,
> 
> Can we try to schedule some time in the next couple weeks to have a call
> to go over clustering integration issues for 5.0?  Particularly with
> respect to the MC.  I'd like to get your input on what you think the key
> issues are so I can get JIRA issues raised, work started.  I don't want
> to be the one holding up planning for getting 5.0 out :)
> 
> Ivelin also would like to sit in on the call.
> 
> Key areas that I'm aware of:
> 
> Clustering aspects in the MC
> -- singleton deployment
> -- replicated metadata
> -- invoking configured POJO operations on all nodes across the cluster
> 
> Configuration/mgmt of clustering as related to Profile service
> 
> Farmed deployments
> 
> I found out today I'm doing a custom training all next week, but how do
> things look for you the week after?
> 
> Cheers,
> 
> Brian
> 
> [EMAIL PROTECTED] wrote:
> > We don't have those dates.
> > 
> > I've tried to set those dates about three times in the last
> > year by asking for the information you want to provide, but
> > very few people actually responded.
> > 
> > On Sun, 2006-03-05 at 18:55, Brian Stansberry wrote:
> >> Adrian,
> >> 
> >> Can you give me a rough estimate of the planned release dates for
> >> 5.0.0.Beta1 and 5.0.0.GA?  JIRA shows no dates beyond 5.0.0.Alpha.
> >> I'm trying to make an estimate of which release will have various
> >> features/fixes and don't have a clear picture of the schedule.
> >> 
> >> Thanks,
> >> 
> >> Brian Stansberry
> >> Lead, AS Clustering
> >> JBoss, Inc.
> >> callto://bstansberry
> >> 
> >> 
> >> ---
> >> 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
> 
-- 

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


[JBoss-dev] jboss-seam-testsuite build.33 Build Fixed

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060407004716Lbuild.33
BUILD COMPLETE - build.33Date of build: 04/07/2006 00:47:16Time to build: 3 minutes 7 secondsLast changed: 04/06/2006 23:16:03Last log entry: improved test data




    Unit Tests: (15)    Total Errors and Failures: (0)All Tests Passed 
 Modifications since last build: (first 50 of 162)1.5modifiedgavinexamples/hibernate/view/main.xhtmlminor1.4modifiedgavinexamples/hibernate/view/main.xhtmlsimplify1.2modifiedgavinexamples/hibernate/view/password.xhtmlsimplify1.2modifiedgavinexamples/hibernate/view/register.xhtmlsimplify1.11modifiedgavinsrc/main/org/jboss/seam/interceptors/ValidationInterceptor.javafix bug1.48modifiedgavinsrc/main/org/jboss/seam/core/Manager.javamake SEMPPL aware of the page actions1.10modifiedgavinsrc/main/org/jboss/seam/core/Pages.javamake SEMPPL aware of the page actions1.13modifiedgavinsrc/main/org/jboss/seam/jsf/SeamExtendedManagedPersistencePhaseListener.javamake SEMPPL aware of the page actions1.69modifiedgavinsrc/main/org/jboss/seam/jsf/SeamPhaseListener.javamake SEMPPL aware of the page actions1.2modifiedgavinsrc/ui/org/jboss/seam/ui/HtmlLink.javasupport linkStyle=button1.4modifiedgavinsrc/main/org/jboss/seam/core/Actor.javabugfixes1.12modifiedgavinsrc/main/org/jboss/seam/jsf/SeamExtendedManagedPersistencePhaseListener.javabugfixes1.21modifiedgavinsrc/main/org/jboss/seam/jsf/SeamTransactionManagedPersistencePhaseListener.javabugfixes1.2modifiedgavinsrc/main/org/jboss/seam/jsf/SeamViewHandler.javabugfixes1.50modifiedgavinsrc/main/org/jboss/seam/init/Initialization.javaadded isUserInRole1.19modifiedgavinsrc/test/misc/org/jboss/seam/test/InitializationTest.javaadded isUserInRole1.1addedgavinsrc/main/org/jboss/seam/core/IsUserInRole.javaadded isUserInRole1.2modifiedgavinsrc/ui/org/jboss/seam/ui/HTML.javaremoved accidental myfaces dependency1.68modifiedgavinsrc/main/org/jboss/seam/jsf/SeamPhaseListener.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.4modifiedgavinsrc/main/META-INF/faces-config.xmls:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.47modifiedgavinsrc/main/org/jboss/seam/core/Manager.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.6modifiedgavinsrc/ui/META-INF/faces-config.xmls:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.5modifiedgavinsrc/ui/META-INF/seam.taglib.xmls:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.5modifiedgavinsrc/ui/META-INF/taglib.tlds:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/HTML.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.3deletedgavinsrc/ui/org/jboss/seam/ui/HtmlActionLink.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/HtmlLink.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/UISelection.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/UITaskId.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.2modifiedgavinsrc/ui/org/jboss/seam/ui/HtmlActionLink.javaenhanced s:actionLink with propagation rules1.1addedgavinsrc/ui/org/jboss/seam/ui/UIConversationPropagation.javaenhanced s:actionLink with propagation rules1.46modifiedgavinsrc/main/org/jboss/seam/core/Manager.javaenhanced s:actionLink with propagation rules1.15modifiedgavinsrc/main/org/jboss/seam/core/Pageflow.javaenhanced s:actionLink with propagation rules1.36modifiedgavinsrc/main/org/jboss/seam/interceptors/ConversationInterceptor.javaenhanced s:actionLink with propagation rules1.67modifiedgavinsrc/main/org/jboss/seam/jsf/SeamPhaseListener.javaenhanced s:actionLink with propagation rules1.6modifiedgavinsrc/main/org/jboss/seam/servlet/SeamServletFilter.javaenhanced s:actionLink with propagation rules1.5modifiedgavinsrc/ui/META-INF/faces-config.xmlenhanced s:actionLink with propagation rules1.4modifiedgavinsrc/ui/META-INF/seam.taglib.xmlenhanced s:actionLink with propagation rules1.1addedgavinsrc/ui/org/jboss/seam/ui/HtmlActionLink.javaadded s:actionLink1.1addedgavinsrc/ui/org/jboss/seam/ui/UIConversationId.javaadded s:actionLink1.3modifiedgavinsrc/ui/META-INF/seam.taglib.xmladded s:actionLink1.4modifiedgavinsrc/ui/META-INF/faces-config.xmladded s:actionLink1.9modifiedgavinexamples/todo/build.xmlsupport ui jar in build scripts1.3modifiedgavinexamples/remoting/chatroom/build.xmlsupport ui jar in build scripts1.3modifiedgavinexamples/remoting/helloworld/build.xmlsupport ui jar in build scripts1.2modifiedgavinexamples/remoting/progressbar/build.xmlsupport ui jar in build scripts1.14modifiedgavinexamples/issues/build.xmlsupport ui jar in build scripts1.4modifiedgavinexamples/messages/build.xmlsupport ui 

[JBoss-dev] jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060406232548
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/06/2006 23:25:48Time to build: 44 minutes 2 secondsLast changed: 04/06/2006 22:32:41Last log entry: JBREM-408 - fixed bug for lease update changing lease window by mistake.




    Unit Tests: (183)    Total Errors and Failures: (20)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(java_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 98)1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-408 - fixed bug for lease update changing lease window by mistake.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/locator/InvokerLocatorTestCase.javaJBREM-406 - allow for : in the locator uri path1.1addedtelrodsrc/tests/org/jboss/test/remoting/detection/multicast/MulticastDetectorTestCase.javaJBREM-405 - fix for NPE when calling stop() more than once on multicast detector.1.2modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/ssl/.keystore.keystore and .truststore need to be in test src directory so they can get copied to test output directory.1.2modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/ssl/.truststore.keystore and .truststore need to be in test src directory so they can get copied to test output directory.1.3modifiedtimfoxsrc/main/org/jboss/remoting/util/TimerUtil.javaFixes to Connection pinging and leasing1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/connection/ConnectionValidationServer.javaJBREM-378 - fixed client connection ping so will properly indicate if server is dead and also not activate a new lease on the server side.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/connection/ConnectionValidatorClient.javaJBREM-378 - fixed client connection ping so will properly indicate if server is dead and also not activate a new lease on the server side.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.2modifiedtelrodsrc/main/org/jboss/remoting/util/TimerUtil.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.1addedtelrodsrc/main/org/jboss/remoting/util/TimerUtil.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-372 - fix for memory leak on leases (on the server side)1.6modifiedrsigalsrc/main/org/jboss/remoting/util/socket/RemotingSSLSocketFactory.javaFixed typo:"javax.net.ssl.trustStorePasswor"1.9modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/http/ssl/custo

[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060406224157
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: 04/06/2006 22:41:57Time to build: 36 minutes 12 secondsLast changed: 04/06/2006 14:22:22Last log entry: JBCACHE-548 - TxManager NPE issues when using with WebLogic and WebSphere




    Unit Tests: (1459)    Total Errors and Failures: (6)testTransactionGetNoKeysMethodorg.jboss.cache.optimistic.NodeInterceptorGetKeysTesttestTransactionGetKeysIteratorMethodorg.jboss.cache.optimistic.NodeInterceptorGetKeysTesttestGetorg.jboss.cache.loader.ClusteredCacheLoaderTesttestCacheLoaderMgmtorg.jboss.cache.mgmt.CacheLoaderTesttestNotificationsorg.jboss.cache.mgmt.NotificationTesttestPassivationMgmtorg.jboss.cache.mgmt.PassivationTest 
 Modifications since last build: (first 50 of 46)1.37modifiedmsurtanisrc/org/jboss/cache/interceptors/TxInterceptor.javaJBCACHE-548 - TxManager NPE issues when using with WebLogic and WebSphere1.8modifiedgenmantests/functional/org/jboss/cache/loader/CacheLoaderMethodCallCounterTest.javaJBCACHE-535Fix count; CacheLoader no longer does a get when we do a put1.5modifiedmsurtanitests/functional/org/jboss/cache/TreeCacheListenerTest.javaAdded more tree cache listener related tests1.25modifiedgenmansrc/org/jboss/cache/interceptors/ActivationInterceptor.javaJBCACHE-535Fix PassivationInterceptor which I did not fix; fix PassivationTestsBase toreflect how cache loader now behaves; add flag to change CacheLoaderInterceptorbehavior for sub-classes1.33modifiedgenmansrc/org/jboss/cache/interceptors/CacheLoaderInterceptor.javaJBCACHE-535Fix PassivationInterceptor which I did not fix; fix PassivationTestsBase toreflect how cache loader now behaves; add flag to change CacheLoaderInterceptorbehavior for sub-classes1.20modifiedgenmansrc/org/jboss/cache/interceptors/PassivationInterceptor.javaJBCACHE-535Fix PassivationInterceptor which I did not fix; fix PassivationTestsBase toreflect how cache loader now behaves; add flag to change CacheLoaderInterceptorbehavior for sub-classes1.12modifiedgenmantests/functional/org/jboss/cache/passivation/PassivationTestsBase.javaJBCACHE-535Fix PassivationInterceptor which I did not fix; fix PassivationTestsBase toreflect how cache loader now behaves; add flag to change CacheLoaderInterceptorbehavior for sub-classes1.1addedbwangtests/perf/org/jboss/cache/aop/ReplicatedSyncMapContentionAopTest.javano message1.19modifiedgenmansrc/org/jboss/cache/interceptors/PassivationInterceptor.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.6modifiedgenmantests/functional/org/jboss/cache/loader/AbstractCacheLoaderTestBase.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.20modifiedgenmantests/functional/org/jboss/cache/loader/CacheLoaderTestsBase.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.11modifiedgenmantests/functional/org/jboss/cache/passivation/PassivationTestsBase.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.24modifiedgenmansrc/org/jboss/cache/Fqn.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.4modifiedgenmansrc/org/jboss/cache/ReplicationQueue.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.145modifiedgenmansrc/org/jboss/cache/TreeCache.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.9modifiedgenmansrc/org/jboss/cache/aop/CollectionClassHandler.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere1.32modifiedgenmansrc/org/jboss/cache/interceptors/CacheLoaderInterceptor.javaAddress JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fix

RE: [JBoss-dev] 5.0..0 Release Schedule

2006-04-06 Thread Brian Stansberry
Hi Adrian,

Can we try to schedule some time in the next couple weeks to have a call
to go over clustering integration issues for 5.0?  Particularly with
respect to the MC.  I'd like to get your input on what you think the key
issues are so I can get JIRA issues raised, work started.  I don't want
to be the one holding up planning for getting 5.0 out :)

Ivelin also would like to sit in on the call.

Key areas that I'm aware of:

Clustering aspects in the MC
-- singleton deployment
-- replicated metadata
-- invoking configured POJO operations on all nodes across the cluster

Configuration/mgmt of clustering as related to Profile service

Farmed deployments

I found out today I'm doing a custom training all next week, but how do
things look for you the week after?

Cheers,

Brian

[EMAIL PROTECTED] wrote:
> We don't have those dates.
> 
> I've tried to set those dates about three times in the last
> year by asking for the information you want to provide, but
> very few people actually responded.
> 
> On Sun, 2006-03-05 at 18:55, Brian Stansberry wrote:
>> Adrian,
>> 
>> Can you give me a rough estimate of the planned release dates for
>> 5.0.0.Beta1 and 5.0.0.GA?  JIRA shows no dates beyond 5.0.0.Alpha.
>> I'm trying to make an estimate of which release will have various
>> features/fixes and don't have a clear picture of the schedule.
>> 
>> Thanks,
>> 
>> Brian Stansberry
>> Lead, AS Clustering
>> JBoss, Inc.
>> callto://bstansberry
>> 
>> 
>> ---
>> 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&kid0944&bid$1720&dat1642
___
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)

2006-04-06 Thread Manik Surtani

Yup
--
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 19:30, Scott Marlow wrote:


Sure, is the following command correct for accessing it:

cvs  co -r Branch_JBossCache_1_3_0 JBossCache

Thanks,
Scott

On Thu, 2006-04-06 at 19:02 +0100, Manik Surtani wrote:

Ok, so I have created a branch -


Branch_JBossCache_1_3_0


Could 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 Cache


Telephone: +44 7786 702 706
MSN: [EMAIL PROTECTED]
Yahoo: maniksurtani
AIM: maniksurtani
Skype: 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 Surtani
Sent: Thursday, April 06, 2006 8:16 PM
To: jboss-development@lists.sourceforge.net
Subject: 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 Surtani
Sent: Thursday, April 06, 2006 5:51 PM
To: jboss-development@lists.sourceforge.net
Subject: 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 Cache


Telephone: +44 7786 702 706
MSN: [EMAIL PROTECTED]
Yahoo: maniksurtani
AIM: maniksurtani
Skype: maniksurtani



On 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 PM
To: jboss-development@lists.sourceforge.net
Cc: QA
Subject: RE: [JBoss-dev] JBossCache 1.3.0.GA released


I 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 Rajasekaran
Sent: Tuesday, April 04, 2006 6:04 AM
To: jboss-development@lists.sourceforge.net
Cc: QA
Subject: [JBoss-dev] JBossCache 1.3.0.GA released

JBossCache 1.3.0.GA  “Wasabi” has been released and is available
for download at

http://sourceforge.net/project/showfiles.php? 
group_id=22866&package_id=102339&release_id=406920


JBossCache 1.3.0.GA  has also been updated in the repository.

Thanks

Rajesh

JBoss QA
















---
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
___

Re: [JBoss-dev] JBossCache 1.3.0.SP1 (WAS: JBossCache 1.3.0.GA released)

2006-04-06 Thread Scott Marlow
Sure, is the following command correct for accessing it:

cvs  co -r Branch_JBossCache_1_3_0 JBossCache

Thanks,
Scott

On Thu, 2006-04-06 at 19:02 +0100, Manik Surtani wrote:
> Ok, so I have created a branch - 
> 
> 
> Branch_JBossCache_1_3_0
> 
> 
> Could 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 Cache
> 
> 
> Telephone: +44 7786 702 706
> MSN: [EMAIL PROTECTED]
> Yahoo: maniksurtani
> AIM: maniksurtani
> Skype: 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 Surtani
> > Sent: Thursday, April 06, 2006 8:16 PM
> > To: jboss-development@lists.sourceforge.net
> > Subject: 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 Surtani
> > > Sent: Thursday, April 06, 2006 5:51 PM
> > > To: jboss-development@lists.sourceforge.net
> > > Subject: 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 Cache
> > > 
> > > 
> > > Telephone: +44 7786 702 706
> > > MSN: [EMAIL PROTECTED]
> > > Yahoo: maniksurtani
> > > AIM: maniksurtani
> > > Skype: maniksurtani
> > > 
> > > 
> > > 
> > > On 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 PM
> > > > To: jboss-development@lists.sourceforge.net
> > > > Cc: QA
> > > > Subject: RE: [JBoss-dev] JBossCache 1.3.0.GA released
> > > > 
> > > > 
> > > > I 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 Rajasekaran
> > > > Sent: Tuesday, April 04, 2006 6:04 AM
> > > > To: jboss-development@lists.sourceforge.net
> > > > Cc: QA
> > > > Subject: [JBoss-dev] JBossCache 1.3.0.GA released
> > > > 
> > > > JBossCache 1.3.0.GA  “Wasabi” has been released and is available
> > > > for download at
> > > > 
> > > > http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920
> > > > 
> > > > JBossCache 1.3.0.GA  has also been updated in the repository.
> > > > 
> > > > Thanks
> > > > 
> > > > Rajesh
> > > > 
> > > > JBoss QA
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> 
> 



---
This SF.Net email is sponsored by xPML, a groundbreak

[JBoss-dev] JBossCache 1.3.0.SP1 (WAS: JBossCache 1.3.0.GA released)

2006-04-06 Thread Manik Surtani
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

[JBoss-dev] RE: jbossweb build.29 Build Fixed

2006-04-06 Thread Rajesh Rajasekaran








Please ignore this mail. We are still
working on getting the JBossWeb builds on different platforms.

 

 

Thanks

Rajesh

 









From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 06, 2006
11:01 AM
To:
jboss-development@lists.sourceforge.net; QA
Subject: jbossweb build.29 Build
Fixed



 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060406114538Lbuild.29




 
  
  BUILD
  COMPLETE -  build.29
  
 
 
  
  Date
  of build: 04/06/2006 11:45:38
  
 
 
  
  Time
  to build: 14 minutes 53 seconds
  
 




 




 
  
  
  
   

 Unit Tests:
(0)  Total Errors and Failures: (0) 

   
   



 
  
   
  
 





 


 


 

   
   

 


 


 


 

   
   

 


 


 

   
  
  
   
  
  
   

 Modifications
since last build:  (first 50 of 0) 

   
  
  
   
  
  
   

 

   
  
  
  
  
 




 








[JBoss-dev] jbossweb build.29 Build Fixed

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060406114538Lbuild.29
BUILD COMPLETE - build.29Date of build: 04/06/2006 11:45:38Time to build: 14 minutes 53 seconds




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (first 50 of 0)



RE: [JBoss-dev] JBossCache 1.3.0.GA released

2006-04-06 Thread Ben Wang



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 Cache
  
  Telephone: +44 7786 702 706
  MSN: [EMAIL PROTECTED]
  Yahoo: maniksurtani
  AIM: maniksurtani
  Skype: maniksurtani
  
  On 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 released

I 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 released
JBossCache 1.3.0.GA  
“Wasabi” has been released and is available for download at
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920

JBossCache 1.3.0.GA  has 
also been updated in the repository.


Thanks
Rajesh
JBoss QA


Re: [JBoss-dev] JBossCache 1.3.0.GA released + a change to how we deal with java.util.properties

2006-04-06 Thread Manik Surtani
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-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060406072122
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/06/2006 07:21:22Time to build: 108 minutes 5 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup.




    Unit Tests: (346)    Total Errors and Failures: (24)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)testStartorg.jboss.test.remoting.transport.multiplex.BasicServerSocketTestCase(jboss_serialization)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.VersionSocketInvokerTestCasetestMultipleLeasesorg.jboss.test.remoting.lease.LeaseUnitTestCase(java_serialization)testMultipleLeasesorg.jboss.test.remoting.lease.LeaseUnitTestCase(jboss_serialization) 
 Modifications since last build: (first 50 of 2343)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/WebInvokerTestC

RE: [JBoss-dev] JBossCache 1.3.0.GA released + a change to how we deal with java.util.properties

2006-04-06 Thread Scott Marlow
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


Re: [JBoss-dev] JBossCache 1.3.0.GA released

2006-04-06 Thread Manik Surtani
Also, we need to branch 1.3.0 for this.  Let me create one and I'll send you the branch tag.  Too many half baked 1.4.0 features in HEAD now. --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: 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 Cache  Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani  On 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

2006-04-06 Thread Manik Surtani
Ok.  Has the tutorial been fixed as well?   --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: 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 Cache  Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani  On 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

2006-04-06 Thread Ben Wang



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 Cache

Telephone: +44 7786 702 706
MSN: [EMAIL PROTECTED]
Yahoo: maniksurtani
AIM: maniksurtani
Skype: maniksurtani

On 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 released
  
  I 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 released
  JBossCache 1.3.0.GA  “Wasabi” 
  has been released and is available for download at
  http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920
  
  JBossCache 1.3.0.GA  has also 
  been updated in the repository.
  
  
  Thanks
  Rajesh
  JBoss QA


[JBoss-dev] jboss-seam-testsuite Build Completed With Testsuite Errors

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060406064614
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:138: 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/06/2006 06:46:14Time to build: 3 minutes 2 secondsLast changed: 04/05/2006 18:16:22Last log entry: simplify




    Unit Tests: (15)    Total Errors and Failures: (0)All Tests Passed 
 Modifications since last build: (first 50 of 157)1.2modifiedgavinexamples/hibernate/view/hotel.xhtmlsimplify1.4modifiedgavinexamples/hibernate/view/main.xhtmlsimplify1.2modifiedgavinexamples/hibernate/view/password.xhtmlsimplify1.2modifiedgavinexamples/hibernate/view/register.xhtmlsimplify1.11modifiedgavinsrc/main/org/jboss/seam/interceptors/ValidationInterceptor.javafix bug1.48modifiedgavinsrc/main/org/jboss/seam/core/Manager.javamake SEMPPL aware of the page actions1.10modifiedgavinsrc/main/org/jboss/seam/core/Pages.javamake SEMPPL aware of the page actions1.13modifiedgavinsrc/main/org/jboss/seam/jsf/SeamExtendedManagedPersistencePhaseListener.javamake SEMPPL aware of the page actions1.69modifiedgavinsrc/main/org/jboss/seam/jsf/SeamPhaseListener.javamake SEMPPL aware of the page actions1.2modifiedgavinsrc/ui/org/jboss/seam/ui/HtmlLink.javasupport linkStyle=button1.4modifiedgavinsrc/main/org/jboss/seam/core/Actor.javabugfixes1.12modifiedgavinsrc/main/org/jboss/seam/jsf/SeamExtendedManagedPersistencePhaseListener.javabugfixes1.21modifiedgavinsrc/main/org/jboss/seam/jsf/SeamTransactionManagedPersistencePhaseListener.javabugfixes1.2modifiedgavinsrc/main/org/jboss/seam/jsf/SeamViewHandler.javabugfixes1.50modifiedgavinsrc/main/org/jboss/seam/init/Initialization.javaadded isUserInRole1.19modifiedgavinsrc/test/misc/org/jboss/seam/test/InitializationTest.javaadded isUserInRole1.1addedgavinsrc/main/org/jboss/seam/core/IsUserInRole.javaadded isUserInRole1.2modifiedgavinsrc/ui/org/jboss/seam/ui/HTML.javaremoved accidental myfaces dependency1.68modifiedgavinsrc/main/org/jboss/seam/jsf/SeamPhaseListener.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.4modifiedgavinsrc/main/META-INF/faces-config.xmls:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.47modifiedgavinsrc/main/org/jboss/seam/core/Manager.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.6modifiedgavinsrc/ui/META-INF/faces-config.xmls:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.5modifiedgavinsrc/ui/META-INF/seam.taglib.xmls:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.5modifiedgavinsrc/ui/META-INF/taglib.tlds:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/HTML.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.3deletedgavinsrc/ui/org/jboss/seam/ui/HtmlActionLink.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/HtmlLink.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/UISelection.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.1addedgavinsrc/ui/org/jboss/seam/ui/UITaskId.javas:actionLink renamed to s:linkenhanced s:linkadded s:taskId1.2modifiedgavinsrc/ui/org/jboss/seam/ui/HtmlActionLink.javaenhanced s:actionLink with propagation rules1.1addedgavinsrc/ui/org/jboss/seam/ui/UIConversationPropagation.javaenhanced s:actionLink with propagation rules1.46modifiedgavinsrc/main/org/jboss/seam/core/Manager.javaenhanced s:actionLink with propagation rules1.15modifiedgavinsrc/main/org/jboss/seam/core/Pageflow.javaenhanced s:actionLink with propagation rules1.36modifiedgavinsrc/main/org/jboss/seam/interceptors/ConversationInterceptor.javaenhanced s:actionLink with propagation rules1.67modifiedgavinsrc/main/org/jboss/seam/jsf/SeamPhaseListener.javaenhanced s:actionLink with propagation rules1.6modifiedgavinsrc/main/org/jboss/seam/servlet/SeamServletFilter.javaenhanced s:actionLink with propagation rules1.5modifiedgavinsrc/ui/META-INF/faces-config.xmlenhanced s:actionLink with propagation rules1.4modifiedgavinsrc/ui/META-INF/seam.taglib.xmlenhanced s:actionLink with propagation rules1.1addedgavinsrc/ui/org/jboss/seam/ui/HtmlActionLink.javaadded s:actionLink1.1addedgavinsrc/ui/org/jboss/seam/ui/UIConversationId.javaadded s:actionLink1.3modifiedgavinsrc/ui/META-INF/seam.taglib.xmladded s:actionLink1.4modifiedgavinsrc/ui/META-INF/faces-config.xmladded s:actionLink1.9modifiedgavinexamples/todo/build.xmlsupport ui jar in build scripts1.3modifiedgavinexamples/remoting/chatroom/build.xmlsupport ui jar in build scripts1.3modifiedgavinexamples/remoting/helloworld/build.xmlsupport ui jar in b

Re: [JBoss-dev] JBossCache 1.3.0.GA released

2006-04-06 Thread Manik Surtani
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 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 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 released I 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=406920 JBossCache 1.3.0.GA  has also been updated in the repository.  ThanksRajeshJBoss QA

[JBoss-dev] jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060406041924
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/06/2006 04:19:24Time to build: 43 minutes 55 secondsLast changed: 04/04/2006 01:20:10Last log entry: JBREM-404:In configureSocketGroupInfo(), add information to SocketGroupInfo only after doing parameter consistency checks.




    Unit Tests: (181)    Total Errors and Failures: (20)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.VersionSocketInvokerTestCasetestMultipleLeasesorg.jboss.test.remoting.lease.LeaseUnitTestCase(java_serialization) 
 Modifications since last build: (first 50 of 92)1.2modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/ssl/.keystore.keystore and .truststore need to be in test src directory so they can get copied to test output directory.1.2modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/multiplex/ssl/.truststore.keystore and .truststore need to be in test src directory so they can get copied to test output directory.1.3modifiedtimfoxsrc/main/org/jboss/remoting/util/TimerUtil.javaFixes to Connection pinging and leasing1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/connection/ConnectionValidationServer.javaJBREM-378 - fixed client connection ping so will properly indicate if server is dead and also not activate a new lease on the server side.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/connection/ConnectionValidatorClient.javaJBREM-378 - fixed client connection ping so will properly indicate if server is dead and also not activate a new lease on the server side.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.2modifiedtelrodsrc/main/org/jboss/remoting/util/TimerUtil.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.1addedtelrodsrc/main/org/jboss/remoting/util/TimerUtil.javaJBREM-374 - updated to use singleton like approach to allow for only one timer thread for leasing.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/lease/LeaseUnitTestCase.javaJBREM-372 - fix for memory leak on leases (on the server side)1.6modifiedrsigalsrc/main/org/jboss/remoting/util/socket/RemotingSSLSocketFactory.javaFixed typo:"javax.net.ssl.trustStorePasswor"1.9modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/http/ssl/custom/HTTPSInvokerTestClient.java*** empty log message ***1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-330 - added assert for callback1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-330 - fix for ssl callback1.10modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.ja

[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors

2006-04-06 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060406034325
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: 04/06/2006 03:43:25Time to build: 35 minutes 19 secondsLast changed: 04/05/2006 18:37:08Last log entry: Address JBCACHE-352,  JBCACHE-535Clean up the CacheLoaderInterceptor to not load so vigorouslyClean up JavaDoc for TreeCache which seems like it needs themMinor fixes elsewhere




    Unit Tests: (1456)    Total Errors and Failures: (62)testTransactionGetNoKeysMethodorg.jboss.cache.optimistic.NodeInterceptorGetKeysTesttestTransactionGetKeysIteratorMethodorg.jboss.cache.optimistic.NodeInterceptorGetKeysTesttestSharedCacheLoadingWithReplicationorg.jboss.cache.optimistic.OptimisticWithCacheLoaderTesttestGetChildrenWithEvictionPassivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestRemoveDataorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestRemoveData2Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestRemoveData3Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestRemoveKeyorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildrenWithEvictionPassivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestRemoveDataorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestRemoveData2Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestRemoveData3Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestRemoveKeyorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildrenWithEvictionPassivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestRemoveDataorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestRemoveData2Passivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestRemoveData3Passivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestRemoveKeyorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestLoopedGetsorg.jboss.cache.loader.CacheLoaderMethodCallCounterTesttestGetorg.jboss.cache.loader.ClusteredCacheLoaderTesttestCacheLoaderMgmtorg.jboss.cache.mgmt.CacheLoaderTesttestNotificationsorg.jboss.cache.mgmt.NotificationTesttestPassivationMgmtorg.jboss.cache.mgmt.PassivationTesttestPrintPassivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestPutPassivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestPut2Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestPreloadingPassivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestCacheLoading2org.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildrenorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildren2org.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildren3org.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildren5org.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildren9Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildren10Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestRemoveKey3Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestTxPutCommitorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestPrintPassivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestPutPassivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestPut2Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestPreloadingPassivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestCacheLoading2org.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildrenorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildren2org.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildren3org.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildren5org.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildren9Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildren10Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestRemoveKey3Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestTxPutCommitorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestPrintPassivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestPutPassivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestPut2Passivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCa