Assertions could also help debug server problems and generally improve
the quality of the code too. 1.4 is good, just too bad not everyone
has it yet. Still waiting for a final for Mac OS X :(
--jason
On Saturday, March 1, 2003, at 01:08 PM, Ricardo Argüello wrote:
I was planning to use the
I was planning to use the new non-blocking I/O API for JBoss Media.
I'm already using the new Java Image I/O available only in 1.4 and above.
So it's not only a nested exceptions problem...
Ricardo Argüello
- Original Message -
From: "Bill Burke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTE
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standar
JBoss daily test results
SUMMARY
Number of tests run: 1120
Successful tests:
Errors:9
Failures: 0
[time of test: 2003-03-01.01-13 GMT]
[java.version: 1.4.1_
JBoss daily test results
SUMMARY
Number of tests run: 1116
Successful tests: 1098
Errors:11
Failures: 7
[time of test: 2003-02-28.23-41 GMT]
[java.version: 1.3.1
I hope we're not going to have pre-compile directives everywhere just so
that people can use nested Runtime, Remote, and regular Exceptions.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Scott
> M Stark
> Sent: Friday, February 28, 2003 6:49 PM
> To:
I have had a few developers ask that 1.4.1 be required for compiling 4.0 to simplify
the
use of 1.4.1 features while still supporting JDK 1.3.1 for runtime for features
backward
compatible with 3.2. That seems like a reasonable comprimise given that 4.0 is a
major release. The challenge is how to
Bugs item #693861, was opened at 2003-02-26 19:43
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=693861&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Bob Cotton (bcotton969)
Assigned to: Nobody/A
Bugs item #693861, was opened at 2003-02-26 14:43
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=693861&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Bob Cotton (bcotton969)
Assigned to: Nobody/A
Bugs item #693861, was opened at 2003-02-26 19:43
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=693861&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Bob Cotton (bcotton969)
Assigned to: Nobody/A
JBoss daily test results
SUMMARY
Number of tests run: 1049
Successful tests: 1045
Errors:1
Failures: 3
[time of test: 2003-02-28.12-05 GMT]
[java.version: 1.3.1]
Not in jb4 you don't, it's been quite rewritten. What exactly are you
having problems with?
You pretty much need to use the *-ds.xml files with jb4: if you want to use
a *-service.xml file to deploy a datasource you need to include an xmbean
configuration to deploy the ManagedConnectionFactory in
What happened to the RARDeployment class that was in the
org.jboss.resource.connectionmanager package? Needed it for connection pooling in data
source xml.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkg
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version "1.3.1_06"
Java(TM) 2 Runtime Environment, Standar
They should be, but aren't in SUN JDK 1.3.x and others. There is a test
case for this on Bill Pugh website at
http://www.cs.umd.edu/~pugh/java/memoryModel/
Stefan
On Friday, Feb 28, 2003, at 07:41 US/Pacific, Kevin Conner wrote:
Unlike longs, integer assignments are atomic. If we keep the
statis
Bugs item #689562, was opened at 2003-02-19 12:22
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=689562&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: James Higginbotham (jwhigginbotha
Bugs item #692157, was opened at 2003-02-24 02:53
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=692157&group_id=22866
Category: JBossMX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Laurent Wozniak (lwozniak)
>Assigned
Bugs item #694148, was opened at 2003-02-26 19:44
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=694148&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 6
Submitted By: John Cleary (insert_id)
>Assigned
Bugs item #693326, was opened at 2003-02-25 17:04
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=693326&group_id=22866
Category: JBossMX
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Brian Wallis (bwallis42)
>
The jnet.jar is available and used in the build since it currently compiles with 1.3.
If you are adding a new feature using javax.net.ServerSocketFactory then you
may have to modify the corresponding build to include this jar to ensure that the
code compiles with 1.3.
We have no plans on dropping
Have you considered setting up the target and bootclasspath attributes
on the javac ant tasks to force 1.3 compatibility?
Steve
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
I meant to say "not" perfect.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Bill
> Burke
> Sent: Friday, February 28, 2003 11:27 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] stop using JDK 1.4 for development
>
>
> chris kimptons builds are p
On Fri, 2003-02-28 at 15:44, Adrian Brock wrote:
> Hi Peter,
>
> The MBeanRegistry is easy,
> there is already a ManagedMBeanRegistry implementation in 3.0.x, it
> should be simple to expose the classloader through an operation.
>
> The harder part is changing InvokerAdaptorServiceMBean
> to be a
chris kimptons builds are perfect, but definately not useless. I'll be
setting up a nightly build as soon as I get my new machine.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jason
> Dillon
> Sent: Friday, February 28, 2003 10:53 AM
> To: [EMAIL PR
Bugs item #691673, was opened at 2003-02-23 06:32
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=691673&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
>Status: Closed
Resolution: Later
Priority: 5
Submitted By: Irakli (idumali)
Assigned to:
Any automated build and reporting system would be valuable... just
depends on the implementation as to whether it is useful or not.
--jason
On Friday, February 28, 2003, at 10:36 PM, David Jencks wrote:
On 2003.02.28 10:23 Jeff Haynie wrote:
The problem really is with me - I fess up. Bill's ma
This actually brings up another question. In using the JNP for JNDI
detector (invoker stuff), it requires javax.net.ServerSocketFactory, which
is in JDK 1.4 by default (and not in JDK 1.3). Therefore I compile and test
using JDK 1.4 while doing my initial development locally. So when this is
rea
David,
This is probably none of my business, but...
> I'd prefer to have a reliable way to report these problems, since I don't
> consider it realistic for me to develop on 1.3.1. How do you detect them?
Isn't this what integration builds and tests are for? If someone checks in code that
> Unlike longs, integer assignments are atomic. If we keep the
> statistics in a volatile int, we make sure different threads see the
> most current value, without the need to lock.
Just a minor point, double and long assigments are atomic if volatile.
Kev
Kevin Conner
This is a pers
We already have nested throwables (org.jboss.util.Nested*) that function in JDK 1.3 & 1.4, just use them.
--jason
On Friday, February 28, 2003, at 09:18 PM, Bill Burke wrote:
We're not going to have .jpp or other ant switches just so that people can use nested exceptions
-Original Message
On 2003.02.28 10:23 Jeff Haynie wrote:
> The problem really is with me - I fess up. Bill's mad because I broke
> the build twice this week by inadvertantly checking in code (throwing an
> exception that is the new overloaded version in 1.4) that only compiles
> on 1.4. Unfortunately, my whole wor
Stefan Reich wrote:
Here is what we could do. The servlet statistics are #number of
operations, mix/Max/TotalTime in miliseconds.
Neither of the operations is unlikely to ever exceed the range of an
integer. Unlike longs, integer assignments are atomic. If we keep the
statistics in a volatil
The problem really is with me - I fess up. Bill's mad because I broke
the build twice this week by inadvertantly checking in code (throwing an
exception that is the new overloaded version in 1.4) that only compiles
on 1.4. Unfortunately, my whole work and home environment *DO* require
1.4 and onl
I'd prefer to have a reliable way to report these problems, since I don't
consider it realistic for me to develop on 1.3.1. How do you detect them?
For the particular problem of nested exceptions, I think we should always
use the jboss NestedThrowable stuff Jason wrote since it provides a much
mo
Bill,
JRE 1.4. I don't care how you compile. I just want to make sure that running JBoss
under 1.4 (which is what I'm doing now) is supported.
- Matt
-Original Message-
From: [EMAIL PROTECTED] on behalf of Bill Burke
Sent: Fri 2/28/2003 9:18 AM
no, jboss doesn't require 1.4.
And yes we must support 1.3 because of people that are using JBoss in
production with JDK 1.3
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> Holger Baxmann
> Sent: Friday, February 28, 2003 9:48 AM
> To: [EMAIL PROTECT
The real question is: Does JBoss _require_ 1.4?
I hope the answer will be 'no'.
bax
Am Freitag, 28.02.03, um 15:36 Uhr (Europe/Budapest) schrieb Jeff
Haynie:
What's the reason to support JDK1.3 -- just asking, not against it.
We've been using 1.4.1 for a good while now and it seems to be much
Hi Peter,
The MBeanRegistry is easy,
there is already a ManagedMBeanRegistry implementation in 3.0.x, it
should be simple to expose the classloader through an operation.
The harder part is changing InvokerAdaptorServiceMBean
to be a DynamicMBean, since 3.0.x uses operation "" instead of
"invoke",
What's the reason to support JDK1.3 -- just asking, not against it.
We've been using 1.4.1 for a good while now and it seems to be much
better in performance and stability.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
danch
Sent: Friday, February 28,
There's a big difference between supporting 1.4 and _not_ supporting 1.3
Matt Munz wrote:
Bill,
I thought JBoss was going to support 1.4. Is this not the case?
- Matt
-Original Message-
From: Bill Burke [mailto:[EMAIL PROTECTED]
Sent: Fri 2/28/2003 8:42 AM
To: Jboss-Dev
Title: [JBoss-dev] stop using JDK 1.4 for development
We're
not going to have .jpp or other ant switches just so that people can use nested
exceptions
-Original Message-From: Matt Munz
[mailto:[EMAIL PROTECTED]On Behalf Of Matt
MunzSent: Friday, February 28, 2003 8:54 AMTo:
Bill,
I thought JBoss was going to support 1.4. Is this not the case?
- Matt
-Original Message-
From: Bill Burke [mailto:[EMAIL PROTECTED]
Sent: Fri 2/28/2003 8:42 AM
To: Jboss-Dev
Cc:
Subject: [JBoss-dev] stop using JDK 1.4 for
There have been a lot of build breakages lately because people are using JDK
1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3.
My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3.
Please stop the sloppiness.
Bill
-
Hi, wow,
last night I tought in desperation that I would have to write a detyped
invoker to solve the stuff: and now you have already done it!
Unfortunately it seems like pain to port it to the 3.0.x line, mostly
because of the lack of access to the MBeanRegistry (wich makes it
imposible to get at
Bugs item #676243, was opened at 2003-01-28 18:23
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=676243&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Everitt (andieveritt)
Assigned to: Nob
Bugs item #669112, was opened at 2003-01-16 15:49
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669112&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: Rejected
Priority: 7
Submitted By: Andrew Everitt (andieveritt)
Assigned to:
46 matches
Mail list logo
