Iacturus wrote:
That's the mechanism currently used to flag whether a component is to
be treated as a singleton. Why wouldn't it be possible?
The problem is, that i need to have exclusive access on object
(component) level.
Using the Threadsafe interface will cause the need of java
synchronization:
synchronized (myComponent) {
myComponent.doSomething1();
myComponent.doSomething2();
}
This is in any case a bottleneck, but i intended to delegate this to
the component manager.
My component is not thread safe and it is not possible to make it
thread safe.
Ok, I'm a little confused now. I thought you asked how to make
something a singleton--which is what I shared. Now you are saying that
is not really what you need.
Without having any more details, I'm not sure how I can help you out
further. If you can help me understand a bit better what it is you
need, I can help you find a solution. Is it possible to use the actual
code itself or is that an NDA or corporate secret? If not, can you get
as similar as you possibly can without violating your employer's trust?
I suspect that you may need another component to do aggregate work, or
something of that nature. I'm not sure. When everything is called
"component" its hard to understand what you are really trying to accomplish.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
