BEGIN:VCALENDAR
METHOD:REPLY
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:(GMT-06.00) Central Time (US Canada)
X-MICROSOFT-CDO-TZID:11
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
Especially Dimitris and the QA team for getting
3.2.8 - 4.0.x working!
On Tue, 2006-02-07 at 22:43, Bill Burke wrote:
Great job everyone!
Ruel Loehr wrote:
Two versions of JBossAS were released today. The released versions
include JBossAS 3.2.8 and JBossAS 4.0.4RC1.
These
Yes, congratulations to the QA team and Dimitris for his first jump in the
release-drama!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Adrian Brock
Sent: mercredi, 8. février 2006 10:46
To: jboss-development@lists.sourceforge.net
Subject: Re:
BEGIN:VCALENDAR
METHOD:REPLY
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:(GMT-06.00) Central Time (US Canada)
X-MICROSOFT-CDO-TZID:11
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
which it isn't afaik. the antlr version started to include
more data in the exception over time.
Including additional data is not an incompatible serialzable change
generally. Its optional data that will be ignored and cannot affect the
legacy implementation.
calling printStackTrace() on
The thing that we discussed (and I have just not yet had time to
implement) is actually converting QueryExceptions that contain antlr
stuff during serialization by either writeReplace() or writeObject().
Initially we had discussed just stripping the cause in the case of antrl
exception, but
Hi,
antlr exceptions can probably be contained by some of the methods
mentioned below - no problem.
I'm just wondering what to do with other exceptions ? They will have the
same/similar problem correct? e.g. a ocracle driver specific exception
occurs
which is pretty good to have as the
Well I think the distinction here is that Hibernate constitutes a hard
dependency on Antlr. The users choice to use Oracle is completely
within their control.
-Original Message-
From: Max Andersen
Sent: Wednesday, February 08, 2006 8:41 AM
To: Steve Ebersole; Scott M Stark;
On Wed, 08 Feb 2006 15:51:49 +0100, Steve Ebersole
[EMAIL PROTECTED] wrote:
Well I think the distinction here is that Hibernate constitutes a hard
dependency on Antlr. The users choice to use Oracle is completely
within their control.
Fair reasoning.
/max
-Original Message-
Right. The issue is we can't have the infinite web of project
implementation details leaking to users unncessarily. Hibernate is a
little different in that its used both in Java SE and Java EE profiles.
My concern is that a pure Java EE client should not care about that
antlr happens to be used
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060208214331
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details.Date of
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060209000517
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:96: The following error occurred while executing this line:
12 matches
Mail list logo
