(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
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 servlet containers that are part of an EE
technolo
Hello,
I want to bring this question again.
Why do we change NamingEntry type from REFERENCE to ENTRY? I think that each
lookup must return a new instance. But in this case, it returns the same bound
object instance.
Let's says that we have a Servlet
MyServlet{
private @Resource(na
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 Reference, current
implemen
