On Thu, 2 Dec 2004 13:08:34 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote:
> Well, Paul, your own last response was about the framework and about
> Java. I sure am getting quizzical about these interjections.
>
Martin is right ... this thread has gone outside the bounds of
off-topicness for Strut
Well, Paul, your own last response was about the framework and about
Java. I sure am getting quizzical about these interjections.
I cannot raise these questions simply in relation to WeakReference,
etc. They are an ongoing issue about one look at the Struts framework
which I have called HaD. If
There are almost 800 people subscribed to this list. The first use of
the word "Struts" in this thread (now over a dozen messages) was in my
message, asking you to move the thread. I don't believe that's what
all those people expect to be reading about here.
If you want to develop your HaD ideas,
I agree with Martin which is why I originally prefixed the subject with
[OT] on my first response.
In the end, fleshed out, your stuff may be of interest. But in the mean
time, there are probably more appropriate places for you to learn about
these parts of Java on your journey to realizing yo
Good points, Paul,
I definitely agree that this is only for a few key classes, Paul.
There is no reason to think at this stage that it would be other than
for framework classes. I have to think through whether that would in
itself be worthwhile. Thanks for your input.
Jack
On Thu, 02 Dec 200
Thanks for your input, Martin, however .
I am doing this in an attempt to flush out HaD, Martin. HaD is a
potential Struts 2.0 implementation, which seems to be an eminently
appropriate topic for a Struts developer list.
Jack
On Thu, 2 Dec 2004 12:40:30 -0800, M
Please move this thread to a Java language mailing list. This
discussion is not related to Struts. Thanks.
--
Martin Cooper
On Thu, 2 Dec 2004 12:30:03 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote:
> Craig,
>
> I am thinking of doing a wrapper, e.g. PointComposite, which will then
> not have to
I don't think weak referencing is going to help you. As Craig
mentioned, an Object is immutably tied to its Class... which is
immutably tied to its ClassLoader.
If Foo has a reference to Bar and you want to replace Bar's
implementation (BarImpl) at runtime without effecting Foo then you are
g
Craig,
I am thinking of doing a wrapper, e.g. PointComposite, which will then
not have to be updated, because it will only adapt the signatures of
the interface Point (not implement Point) but that the actual object
doing the work will be a PointImpl which will soley be a weak
reference and availa
Thanks, Craig,
I am going to have to look into this more, then. Interesting stuff in
any event.
Jack
On Thu, 2 Dec 2004 12:07:28 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On Thu, 2 Dec 2004 11:56:31 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote:
>
> > Essentially, I am trying to kee
Another way of putting my question, maybe, is: why do these == return
different values:
package com.crackwillow.deploy;
import java.lang.ref.Reference;
import java.lang.ref.WeakReference;
public class MyReference {
public static void main(String [] params) {
CheckPlease cp = new CheckPleas
On Thu, 2 Dec 2004 11:56:31 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote:
> Essentially, I am trying to keep a WeakReference to
> Point classes so that when I update the Point.class I can change the
> classes for all the PointImpl objects out there.
My understanding of Java (extensive in many are
Paul and Craig
I am getting what I expect with the following code (see below), thanks
to Craig, but not with the code which you can find at
http://131.191.32.112:8080/classes.zip and I am not sure what the
difference is. Essentially, I am trying to keep a WeakReference to
Point classes so that wh
On Thu, 2 Dec 2004 00:05:12 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> Don't forget that Strings are immutable in Java :-).
>
> You might have better luck experimenting with a JavaBean that has
> getters/setters for the properties you want to be able to mess with.
>
> Craig
>
>
Thank
Ok, I haven't run this, but let me try to interpret what I see inline...
Dakota Jack wrote:
Thanks for the response, Paul. Here's what I am up to. I can get an
object from the weak reference created from a strong reference. What
I want to do, and am not sure if I can (I am starting to think I
ca
Don't forget that Strings are immutable in Java :-).
You might have better luck experimenting with a JavaBean that has
getters/setters for the properties you want to be able to mess with.
Craig
On Wed, 1 Dec 2004 23:44:38 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote:
> Thanks for the response,
Thanks for the response, Paul. Here's what I am up to. I can get an
object from the weak reference created from a strong reference. What
I want to do, and am not sure if I can (I am starting to think I
cannot), is to grab the object with the weak reference and make
changes which will happen also
A WeakReference is just a way of holding a reference to an object that
will not keep it from being garbage collected (a very useful thing).
There are also ways that you can track when it has been garbage
collected. Once it has been garbage collected, it's gone though. All
you have is any data
18 matches
Mail list logo
