> From: Peter Donald [mailto:[EMAIL PROTECTED]]
>
> I really don't like the toString "solution" as it just wont
> work in a bunch of places.
>
> I would recomend that you use the proxying class (I
> think it is named
> ProxyHelper) which has a method to get the underlying object
> from the
I really don't like the toString "solution" as it just wont work in a bunch of
places. I would recomend that you use the proxying class (I think it is named
ProxyHelper) which has a method to get the underlying object from the proxy
and then use the underlying object where appropriate.
--
Chee
Should be dead dead dead now.
/LS
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Leo Sutic wrote:
One question - are you using the lifecycle extensions in any way?
(If you don't know what that is, the answer is "no".)
From: Leo Sutic [mailto:[EMAIL PROTECTED]]
Everone is given a default lifecycle extension manager with no
extensions.
---
Leo Sutic wrote:
Berin,
this sounds like an issue with proxies. The StaticBucketMap should
be able to handle proxies, as long as the key being put == the
key being get.
I'm not that keen on the solution applied - it assumes that a
component's
toString() method returns the same value all the time
> From: J Aaron Farr [mailto:[EMAIL PROTECTED]]
>
> proxies to not equal() each other?
They don't. A Proxy isn't even equal() to itself many times.
Consider the case where an object O is wrapped by a proxy P.
P.equals (P) leads to O.equals (P), which in most cases is false
due to class mism
On Mon, 2003-02-17 at 11:12, Leo Sutic wrote:
> Appears to be a bug in StaticBucketMap.
>
> Remove tests like this:
>
> if( n.key == null || ( n.key != null && n.key.equals( key ) ) )
>
> but get tests like this:
>
> if( n.key == key || ( n.key != null && n.key.equals( key ) ) )
>
On Mon, 2003-02-17 at 10:50, Leo Sutic wrote:
> One question - are you using the lifecycle extensions in any way?
>
> (If you don't know what that is, the answer is "no".)
>
No. Normal Lifecycles. No extensions.
> > From: Leo Sutic [mailto:[EMAIL PROTECTED]]
>
>
> -
Appears to be a bug in StaticBucketMap.
Remove tests like this:
if( n.key == null || ( n.key != null && n.key.equals( key ) ) )
but get tests like this:
if( n.key == key || ( n.key != null && n.key.equals( key ) ) )
and of course the equals() comparison dies on proxies
One question - are you using the lifecycle extensions in any way?
(If you don't know what that is, the answer is "no".)
> From: Leo Sutic [mailto:[EMAIL PROTECTED]]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional co
> From: J Aaron Farr [mailto:[EMAIL PROTECTED]]
>
> One thing you might want to know is that I did try changing
> it from a StaticBucketMap to a normal Hashtable and still had
> the same issue. So apparently, the key that's being put is
> NOT the key that is being "get" even though the toSt
On Mon, 2003-02-17 at 04:31, Leo Sutic wrote:
> Berin,
>
> this sounds like an issue with proxies. The StaticBucketMap should
> be able to handle proxies, as long as the key being put == the
> key being get.
>
> I'm not that keen on the solution applied - it assumes that a
> component's
> toStrin
Berin,
this sounds like an issue with proxies. The StaticBucketMap should
be able to handle proxies, as long as the key being put == the
key being get.
I'm not that keen on the solution applied - it assumes that a
component's
toString() method returns the same value all the time. This may be true
Berin Loritsch wrote:
J Aaron Farr wrote:
--- J Aaron Farr <[EMAIL PROTECTED]> wrote:
Apparently the attatchment didn't work right. Here's the patch file (I
hope).
:)
jaaron
My email client is acting buggy.
One last try, this time cut and paste:
Thanks a heap. I applied the fix to
J Aaron Farr wrote:
--- J Aaron Farr <[EMAIL PROTECTED]> wrote:
Apparently the attatchment didn't work right. Here's the patch file (I
hope).
:)
jaaron
My email client is acting buggy.
One last try, this time cut and paste:
FortressServiceManager
[snip]---
--- J Aaron Farr <[EMAIL PROTECTED]> wrote:
> Apparently the attatchment didn't work right. Here's the patch file (I
> hope).
> :)
>
> jaaron
>
My email client is acting buggy.
One last try, this time cut and paste:
FortressServiceManager
[snip]---
Apparently the attatchment didn't work right. Here's the patch file (I hope).
:)
jaaron
--- J Aaron Farr <[EMAIL PROTECTED]> wrote:
> Hi.
>
> I'm having lots of troubles disposing my components with Fortress.
> Basically,
> I've got some disposable components with a FactoryComponentHandler. H
Hi.
I'm having lots of troubles disposing my components with Fortress. Basically,
I've got some disposable components with a FactoryComponentHandler. However,
when I use the ServiceManager to release them, nothing happens.
The problem comes from this line in the FortressServiceManager.release()
18 matches
Mail list logo
