Thanks for the suggestions, guys. This has been a tricky one to work
through but I think I have the answer - kind of.
A number of people responded with help for which I am grateful (think:
2am and I'm all alone and it has to be fixed by morning, it is so nice
to see a helpful message come throug
app its own copy unless you want it to behave as a shared static
class.
I think the way its structured now, static fields sharing makes sense...
that they behaved distinctly at all... is weird.
- Original Message -
From: "Roger Parkinson" <[EMAIL PROTECTED]>
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger,
Roger Parkinson wrote:
> I have two different applications and they both make use of a common
> jar library. The common library has several static fields.
[snip]
> I am trying to figure out what I changed to make this happen because
> it is c
Roger Parkinson wrote:
I have two different applications and they both make use of a common
jar library. The common library has several static fields.
Up until last week the static fields in one application never saw the
static fields in the other but I changed something and suddenly they do.
Al
I have two different applications and they both make use of a common jar
library. The common library has several static fields.
Up until last week the static fields in one application never saw the
static fields in the other but I changed something and suddenly they do.
All the advice I've found
