Hello,
as to my knowledge the modern containers do not encourage the usage of
shared data anymore, and this was the only possible problem cause
anyway:
The real root cause of this problem is that SHARED data (static
members on a class) is being shared across supposedly independent
"applications".
On Sun, Feb 7, 2010 at 3:39 PM, James Mansion
wrote:
> Andrew Thorburn wrote:
>>
>> Indeed. It's generally regarded as an anti-pattern.
>>
>> evebill8: See below for a couple of links talking about it if your
>> co-workers grumble about it (and for anyone else who comes along
>> asking these quest
I must second Ted on this.
Talking about WSDL - consider IDL compilers, they usually generate an
Interface (operations) and a basic BOA (later POA, which stands for
basic/portable object adapter). You have the choice between extending
the BOA or implementing the operations interface and "tie" your
Hello Jason,
thank you very much for the detailed answer.
On Mon, Jul 20, 2009 at 12:42 AM, Jason
Weinstein wrote:
>
> Hi Leon,
>
> Often generated files are only a starting point.
An interesting point. Actually the mess that happens if you try to
"regenerate" edited generated file is the main a
On Fri, Jul 17, 2009 at 11:11 AM, Jason
Weinstein wrote:
>
> A common problem with templating systems is that they overwrite changes made
> to the generated files, when things are regenerated.
Hello,
maybe I don't understand your point, but why should someone change
generated files?
Leon
--
atched
> perfectly except the little iterator problem.
>
>
> 2009/6/17 James Carman
>
>> Or, ehcache or oscache or something like that?
>>
>> On Wed, Jun 17, 2009 at 10:17 AM, Leon
>> Rosenberg wrote:
>> > why don't you just use softreference + ex
why don't you just use softreference + expiration timestamp and save
all the trouble?
Leon
On Wed, Jun 17, 2009 at 4:07 PM, Renè Glanzer wrote:
> Hi,
>
> it's me again with an update.
> the LRUMap.mapIterator() still produces the
> ConcurrentModificationException when a call to MapIterator.remove(
to it and bang Exception in my delete method.
>
> When i switch back to HashMap the code runs well - as currently on the
> productive system - except the open memory leak.
>
> René
>
> 2009/6/15 Leon Rosenberg :
>> just out of curiosity have you tried the same code with
ode which wants to delete the elements is
> synchronized.
> So I've no clue where the "ConcurrentModificationException" is comming from
> :-(
>
> Thanks René
>
> 2009/6/15 Leon Rosenberg :
>> Hello,
>>
>> on a side note, generics make reading
Hello,
on a side note, generics make reading of code easier :-)
you haven't posted the whole code, but have you (double)checked that
all other acesses to store are synchronized?
regards
Leon
On Mon, Jun 15, 2009 at 2:31 PM, Renè Glanzer wrote:
> I'm calling the remove() method on the iterator.
Hello,
Apparently your code is compiled with another version as used at runtime.
regards
Leon
2009/6/8 yau :
> Hi,
>
> I have a function return a DataSource, like:
> DataSource setupDataSource(String dbName) {
> BasicDataSource ds = new BasicDataSource();
> ...
> return ds;
> }
>
> But, when
Thanks for the reply, but how does NIO plays into it?
On Mon, May 4, 2009 at 11:59 PM, Gary Gregory
wrote:
> Hi Leon,
>
> Is java.nio appropriate for your application?
>
> Gary
>
>> -Original Message-
>> From: Leon Rosenberg [mailto:rosenberg.l...@googlemai
Hello,
in my search for a solution for my problem I came across commons vfs.
After reading the wiki and some of the docs I'm not sure whether I can
(rather not yet, but maybe in the near future?) achieve my task with
commons vfs, hence I'm searching for enlightment.
We have an internal messaging s
13 matches
Mail list logo
