Thanks for the reply.
The code to parse the XML is separate from that which persists it. This was done with intention to separate the integration logic from the persistence logic. No doubt I'll have to read up on Service Unit/Service Engine but if I want to keep the separation between the layers, can I still "easily" create a service unit for my integration piece which will be handed to my persistence service unit? Thanks in advanced. -los Philip Dodds-2 wrote: > > In fact, if you just have a peice of code for reading the XML and > persisting it you could write a simple JSR181 Service Unit with a POJO > that accepts a Source object and use the JSR181 Service Engine to > deploy it :) > > P > > On 10/3/06, James Strachan wrote: >> On 10/3/06, moraleslos wrote: >> > Hi, >> > I'm new to Servicemix and the concept of ESB/JBI in general. Currently >> I'm >> > evaluating ways to integrate various data sources that we use for our >> > product. Instead of developing specific integration modules for each >> data >> > source, I would like to consolidate all of the data sources being >> imported >> > into some sort of integration layer. Hence I came upon ESB and >> Servicemix. >> > >> > Now, if I continue with the ESB/Servicemix route, I want to make sure >> that >> > I'm doing the right thing. I would like to integrate one data source >> first >> > before moving along with the others. This external datasource is a >> > vendor-specific XML file. Currently we ftp this XML file onto our >> server, >> > read/extract contents with a SAX Parser, and store data into our >> database. >> > This is runned as a daemon process (e.g. polls for XML files every >> day). >> > For a scenario such as this, can Servicemix/ESB handle this process >> more >> > elegantly? I'm looking at the long term since many of our external >> data >> > sources will be similar to the process described above. Thanks in >> advance! >> >> Sounds like a good fit for ServiceMix which already has a whole host >> of components for doing things like this. The only thing you may want >> to do is wrap up your current persistence code as a JBI component so >> that you can save a blob of XML however you like in your database; >> other than that the rest of the things you describe are generic JBI >> services/components. >> >> -- >> >> James >> ------- >> http://radio.weblogs.com/0112098/ >> > > -- View this message in context: http://www.nabble.com/Would-servicemix-work-with-ftp-xml-integration-tf2376311.html#a6621112 Sent from the ServiceMix - User mailing list archive at Nabble.com.
