well, it seems to be ignoring that. The log shows:

DEBUG 10451 [system.r] (): looking up shorthand business-object-service, returning com.browsersoft.eq.bc.BusinessObjectService
DEBUG 10451 [system.c] (): Adding component (com.browsersoft.eq.bc.BusinessObjectService = com.browsersoft.eq.bc.BusinessObjectServiceImpl)
DEBUG 10451 [system.c] (): Attempting to get Handler for role [com.browsersoft.eq.bc.BusinessObjectService]
DEBUG 10451 [system.c] (): Handler type = org.apache.avalon.excalibur.component.DefaultComponentHandler

I even tried setting the handler to "org.apache.avalon.excalibur.component.ThreadSafeComponentHandler" (instead of the Fortress one), as that is what shows up for the Excalibur conn. pool. component that I'm also using. I also tried the handler as a sub-tag instead of an attribute, but it ignored that.

again, I'm using ExcaliburComponentManagerCreator and not Fortress directly (if that makes a difference).

- Robert

Berin Loritsch wrote:

Robert McIntosh wrote:



In a word, no :-)
What I need is the ThreadSafeHandler for my service, which is the class c.b.e.b.BusinessObjectServiceImpl. So what if I did:

<role name="com.browsersoft.eq.bc.BusinessObjectService">
<component shorthand="buisiness-object-service"
class="com.browsersoft.eq.bc.BusinessObjectServiceImpl"

handler="org.apache.avalon.fortress.impl.handler.ThreadSafeComponentHandler"/>
</role>

???
I _think_ the 'handler' attribute is what I was looking for(?)

Yep.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to