Johan Lindquist wrote:
Hi again Ron,
Just to make sure - do you call the method on the service implementation
that you are currently handling in the method of your filter? Trivial
thing, but I have myself got caught by this before - void method and no
call to the service :)
Cheers,
Johan
Thanks for your answer :)
First I used dependency injected QueryBuilder (the service interface,
not the filter one...) - when this didn't work, I explicitly used
set-service in the <construct of the service which uses the
QueryBuilder, both did the same -
for the logs I will post what I can get ASAP, but it will take a few days...
Cheers and happy eastern,
Ron
Hi,
I just tried using the library's Pipline factory, but ended up only
having the first filter called. Any hints would be most appreciated...
cheers,
Ron
the xml:
<configuration-point id="QueryBuilderPipeline"
schema-id="hivemind.lib.Pipeline">
</configuration-point>
<service-point id="QueryBuilder" interface="QueryBuilder">
<invoke-factory service-id="hivemind.lib.PipelineFactory">
<create-pipeline filter-interface="QueryBuilderFilter"
configuration-id="QueryBuilderPipeline"/>
</invoke-factory>
</service-point>
<contribution configuration-id="QueryBuilderPipeline">
<filter before="*" name="BaseJoin"
object="instance:impl.QBF0BaseJoin"/>
<filter after="BaseJoin" name="CategoryXLocation"
object="instance:impl.QBF1CategoryXLocation"/>
<filter after="*" name="Order" object="instance:impl.QBFxOrder1"/>
</contribution>
---------------------------------------------------------------------
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]
