https://issues.apache.org/bugzilla/show_bug.cgi?id=49994
--- Comment #3 from Mark Thomas 2010-11-04 14:03:17 EDT ---
Note this behaviour will be configurable from 7.0.5 onwards and will default to
the previous behaviour of returning the same object for each lookup.
--
Configure bugmail: https:/
https://issues.apache.org/bugzilla/show_bug.cgi?id=49994
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://issues.apache.org/bugzilla/show_bug.cgi?id=49994
--- Comment #1 from Gurkan Erdogdu 2010-09-24
08:00:08 EDT ---
Comments from David Jencks:
For reference, the EE 6 platform spec explains that usually a new instance
should be returned on each lookup in section 5.2.4 page 67 "Sharing of
E
https://issues.apache.org/bugzilla/show_bug.cgi?id=49994
Summary: NamingContext Possible Bug
Product: Tomcat 7
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
(removing
caching statements) this does not break anything.
I will open an issue.
Regards;
--Gurkan
- Original Message
From: Konstantin Kolinko
To: Tomcat Developers List
Sent: Fri, September 24, 2010 2:36:46 AM
Subject: Re: NamingContext Possible Bug
2010/9/21 Gurkan Erdogdu
2010/9/21 Gurkan Erdogdu :
> Hello folks,
>
> In NamingContext implementation, if "lookup()" is a Reference, current
> implementation caches the result of the NamingManager # getObjectInstance via
> following statements and changes the type of the entry. In the following
> lookups, same object is r
On 22/09/2010 23:48, David Jencks wrote:
> For reference, the EE 6 platform spec explains that usually a new instance
> should be returned on each lookup in section 5.2.4 page 67 "Sharing of
> Environment Entries". The servlet 3.0 spec section 15.2.2 page 174 indicates
> that this applies to se
ce/ResourceRef" binding. Therefore each lookup
> to
> "MyResource" must return a "ResourceRef". Becuase it is a reference, context
> must call NamingManager.getObjectInstance again to create a new instance.
>
> If this is a bug, I will open an issue.
>
;ResourceRef". Becuase it is a reference, context
must call NamingManager.getObjectInstance again to create a new instance.
If this is a bug, I will open an issue.
Thanks;
--Gurkan
- Original Message
From: Gurkan Erdogdu
To: dev@tomcat.apache.org
Sent: Tue, September 21, 2010
Sorry but skip the question!
Thanks;
--Gurkan
- Original Message
From: Gurkan Erdogdu
To: dev@tomcat.apache.org
Sent: Tue, September 21, 2010 6:30:43 PM
Subject: NamingContext Possible Bug
Hello folks,
In NamingContext implementation, if "lookup()" is a Referenc
Hello folks,
In NamingContext implementation, if "lookup()" is a Reference, current
implementation caches the result of the NamingManager # getObjectInstance via
following statements and changes the type of the entry. In the following
lookups, same object is returned. I would like to write Obje
11 matches
Mail list logo
