Ok, I'll check it out.
You'll have to bear with me until I figure out the way everything works in
servicemix.
bsnyder wrote:
>
> On 3/22/07, Alex_ynr <[EMAIL PROTECTED]> wrote:
>>
>> Ok, that sounds promising.
>>
>> Which is the base poller component to extend?
>
> You should take a look at the
> org.apache.servicemix.file.FilePollerEndpoint in the servicemix-file
> component for an example of this. It extends the
> org.apache.servicemix.common.endpoints.PollingEndpoint for the polling
> capabilities.
>
> You could build a single database poller component and just deploy two
> configurations of it. Then it sounds like you'd need to orchestrate
> the use of these two so that when getOrderItems messages arrive,
> they're held until the getOrders item message arrives and the two are
> transformed via XSLT into a single message.
>
That is exactly what I had in mind. I just wasn't sure if/how it was
possible.
bsnyder wrote:
>
>> Also, rather than a SELECT Count(*) etc. I think it should be more like
>> define the query, define the no of rows per event (do we handle 1 at a
>> time
>> even if there are more? all of them? a specific amount? etc.) and define
>> which field is the primary key and use that to poll the DB
>
>
> OK, so we'd need to look closer at your use case, but I think we could
> create some base functionality in the database polling component to
> make it functional and then build some additional configuration
> features on top of that.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Castor - http://castor.org/
>
>
--
View this message in context:
http://www.nabble.com/Question-about-ServiceMix-topologies-tf3439529s12049.html#a9630452
Sent from the ServiceMix - User mailing list archive at Nabble.com.
