Hi Scott,
That sounds great! I've switched to the 6.0.0-SNAPSHOT now, i'm seeing some
JMX error messages but nothing major. Still no luck getting everything to
wire together though, I'll have to poke around the commit log and see what
has changed!
In the meantime though, I decided the path of least resistance would be to
indirectly communicate via ActiveMq :-
<route>
<from uri="direct:blueprintRouteWithoutDrools" />
<inOut uri="activemq:springRouteWithDrools" />
</route>
<route>
<from uri="direct:springRouteWithDrools" />
<to uri="drools:..." />
</route>
This didn't work initially, but I was able to fix it by adding 'implements
Serializable' to the Person class
It would be great to hear how you get on with your drools example updates :)
Cheers
Alan
scranton wrote
> Alan,
>
> I haven't tried drools with camel and blueprint yet, but I do know
> that they've made a bunch of osgi enhancements to drools in
> 6.0-SNAPSHOT. I was thinking of upgrading that camel drools example
> (still with spring) to see if I could eliminate more of the uberjar
> stuff...
>
> You may want to try your tests against latest snapshot to see if at
> least the OSGi parts work better...
>
> Scott
>
> On Fri, Mar 8, 2013 at 7:53 AM, AlanFoster <
> alan@
> > wrote:
>> I had planned to do that, but i've spent the past week trying to do this
>> with
>> no luck unfortunately! :(
>>
>> I firstly noticed that drools doesn't offer a blueprint namespace
>> handler,
>> so I can't use any of the spring xml instantiation blocks that it has
>> within
>> blueprint! :(
>>
>> I've also tried to expose the drools camel component from spring as an
>> osgi
>> service so that it can be used in the blueprint routes, but it then dies
>> on
>> the following code within one of the blueprint routes
>>
>> DroolsEndpoint.java
>> protected void configure(DroolsComponent component,
>> String uri) {
>> String nodeId = getExecuteNodeId( uri );
>> ksessionId = getKsessionId( uri );
>>
>> if ( !StringUtils.isEmpty( nodeId ) ) {
>> // let's look it up
>> node = component.getCamelContext().getRegistry().lookup(
>> nodeId,
>>
>> GridNode.class );
>> if ( node == null ) {
>> throw new RuntimeCamelException( "Could not find GridNode
>> for uri=\"" + uri + "\" in CamelContext. Check configuration." );
>> }
>>
>>
>> Presumably this is because the camel context doesn't know about the
>> GridNode
>> class declared in a completely different bundle...
>>
>> I wonder if there's an easy way to make this work at all?
>>
>> I would greatly appreciate any help you can give :)
>>
>>
>> Claus Ibsen-2 wrote
>>> On Thu, Mar 7, 2013 at 2:04 PM, AlanFoster <
>>
>>> alan@
>>
>>> > wrote:
>>>> Hi Claus,
>>>>
>>>> Thanks for the response;
>>>>
>>>> I spotted this example before, but unfortunately the spring example
>>>> doesn't
>>>> work when trying to convert it to a blueprint bundle
>>>>
>>>> Do you happen to know where a blueprint bundle example can be found? :)
>>>>
>>>
>>> No I have not seen a blueprint example. Maybe you can port that
>>> example to blueprint?
>>>
>>>> Alan
>>>>
>>>>
>>>> Claus Ibsen-2 wrote
>>>>> Hi
>>>>>
>>>>> There is a Camel and Drools example here
>>>>> https://github.com/FuseByExample/camel-drools-example
>>>>>
>>>>>
>>>>> On Thu, Mar 7, 2013 at 1:03 PM, AlanFoster <
>>>>
>>>>> alan@
>>>>
>>>>> > wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Just wondering if there's any examples of drools running under
>>>>>> blueprint?
>>>>>>
>>>>>> I can see that there is a camel-spring example, which works great,
>>>>>> but
>>>>>> not a
>>>>>> camel-blueprint example anywhere
>>>>>>
>>>>>> I'd appreciate if anyone knows anything about this :)
>>>>>>
>>>>>> Thanks,
>>>>>> Alan
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://camel.465427.n5.nabble.com/Camel-blueprint-and-drools-tp5728744.html
>>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> Red Hat, Inc.
>>>>> FuseSource is now part of Red Hat
>>>>> Email:
>>>>
>>>>> cibsen@
>>>>
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus
>>>>> Blog: http://davsclaus.com
>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://camel.465427.n5.nabble.com/Camel-blueprint-and-drools-tp5728744p5728750.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email:
>>
>>> cibsen@
>>
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Camel-blueprint-and-drools-tp5728744p5728824.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-blueprint-and-drools-tp5728744p5728998.html
Sent from the Camel - Users mailing list archive at Nabble.com.
