[
https://issues.jboss.org/browse/JBWEB-263?page=com.atlassian.jira.plugin....
]
Bartosz Baranowski edited comment on JBWEB-263 at 3/27/13 10:04 AM:
--------------------------------------------------------------------
It seems to work. One side note, I took time to test one thing. Not sure if this is a
"seam" thing. When sun classes are pocked, they create BeanELResolver
instance(B1). However when SEAM kicks in, for every app(B1+n)(or context, not quite sure)
it creates another instance. Even though SEAM does that, this particular instance is not
used, the B1 is used for all invocations.
was (Author: baranowb):
It seems to work. One side note, I took time to test one thing. Not sure if this is a
"seam" thing. When sun classes are pocked, they create BeanELResolver
instance(B1). However when SEAM kicks in, for every app(B1+n)(or context, not quite sure)
it creates another instance. Even though SEAM does that, this particular is not used, the
B1 is used for all invocations.
Remove WeakHash map from BeanELResolver and depend on proper callback
to remove bean properties
-----------------------------------------------------------------------------------------------
Key: JBWEB-263
URL:
https://issues.jboss.org/browse/JBWEB-263
Project: JBoss Web
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Bartosz Baranowski
Assignee: Remy Maucherat
Attachments: JBWEB-263.patch, JBWEB-263.patch
As in subject. Even though its a weakhashmap( and current source has the
ConcurrentCache.
Affected version: 2.1.12.GA -
http://svn.jboss.org/repos/jbossweb/branches/2.1.x/
Fix version: next( EAP depends on 2.1.13.GA-patch01 or JBOSSWEB_2_1_12_GA_patch03 )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira