View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060404025543Lbuild.101
BUILD COMPLETE-build.101Date of build:04/04/2006 02:55:43Time to build:37 minutes 44 secondsLast changed:03/31/2006 08:28:49Last log entry:Advice
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060404033514
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060404072618
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
Sounds good to me. My next question is how do we tell Hibernate to use
JBoss Cache as the first level cache?
On Mon, 2006-04-03 at 17:13 -0500, Scott M Stark wrote:
Yes, we should be defaulting to a single node, unclustered jboss cache
rather than having to supply yet another thirdparty jar to
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 ?
AFAIK, Steve
I have updated the remoting road map to reflect what I want to deliver
within the next quarter -
http://jira.jboss.com/jira/secure/BrowseProject.jspa?id=10031subset=-1.
In short:
2.0.0 (Boon) - mainly stability and performance release with minor
features and bug fixes. estimated release mid
So jboss-remoting 2.0.0 could come with the next version of jboss-as
2.0.5, unless there are other dependencies.
Why not putting dates on the remoting releases?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Tom Elrod
Sent: 04 April, 2006 17:04
Have not put a date in jira for jboss-remoting 2.0.0 yet, as need to
make sure nothing else needs to be added (by the other projects).
Assuming that nothing else is added to that release, expect GA release
to be end of May (which would then go into jboss-as 4.0.5).
Dimitris Andreadis wrote:
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
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).
Can I ask a dumb question:
Why?
-Andy
Max Rydahl Andersen 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
Can I ask a dumb question:
Why?
Why - as in why the first-level cache in Hibernate is not pluggable ?
Then the answer is:
The first-level cache is a very specialized context that is very crucial
for Hibernate
to work. first-level cache is also generic term used to explain people
*one*
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
Hi all,
When I run the test suite, it fails with the excpetion below. Is there a problem with head or is it just my env.?
Thanks,
Hany Mesha
==Begin===
20:28:08,943 INFO [Server] Starting JBoss (MX MicroKernel)...
20:28:08,944 INFO
14 matches
Mail list logo
