Re: Fortress/ECM handlers

[Berin Loritsch]

Robert McIntosh wrote:

> 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).



Oh, that does make a difference. Fortress creates and manages
components, and manages their relationships. ECM is a different
beast altogether. What you are doing is not using Fortress for
those purposes, and using ECM instead.

It would be better if you remained true to one or the other. Don't
mix and match as the behavior is not easily determined--and the config
files are a bit different. It would be better if you went all Fortress
in the mid term. However we are in the process of trying to handle
a smooth transition.



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