Hello, maturing OpenERP to use asynch message bus is interesting indeed, especially for multi-company and/or larger companies which will be used to J2EE ESB's. I didn't look into details about what you and Cloves did, but I let you know that Tiny did a parallel effort with the Twisted Python asyn messaging system. Here is the work of Stephane Wirtel: https://code.launchpad.net/~stephane-openerp/openobject-server/twisted In any case, I hope you can join efforts rather than double work on those issues.
I think this is also a place where a total or partial (eg in redundancy with a CPython instance) usage of OpenERP on Jython would shine as the Java platform has plenty of valuable and mature ESB systems generally built upon the JMS protocol. Finally, may be something that could be used as a rule engine to trigger an anych message emission could be the "SARTRE" rule module by Smile in extra addons now (currently use to trigger alerts and standard server actions). Then message emission would be a regular server action triggered by that rule engine upon given conditions. Not sure, but something to investigate may be. Would also be nice to have the reverse: a rule engine that know how to analyse the message queue en trigger a given server action if the message matches a given condition, may be similar to what the Smile SARTRE module does. Again not sure. All right, good luck with this one... Raphaël Valyi http://www.akretion.com <https://code.launchpad.net/~stephane-openerp/openobject-server/twisted> 2010/2/22 Dukai Gábor <[email protected]> > Hello! > There are tools already present that could be used to integrate OpenERPs > (And > other systems, too. It's based on xml.) and it would work on slow, > unreliable > connections. > > IMHO to develop something like this would take two workdays: > -Confirming a PO creates an SO at the supplier's side. > -It matches products with bar code and partners with VAT number for > example. > Or it uses a unique identifier for products and in the first run maps those > identifiers to bar codes, and if didn't succeed, uses product.supplierinfo. > -Confirming the SO at the supplier's side validates the PO at the > customer's > side. > -Any number of connections can be used and they are relatively easy to set > up > for an administrator. > -It stores the messages if you or the other parties aren't online and > automatically sends them as soon as possible. > > This is all based on Cloves Almeida's mbi module that is the tool to turn > any > object into xml/read from xml and send/receive it using stomp (we use it > with > an ActiveMQ broker). > I've created a module mbi_openerp that adds easy setup routing, easy setup > CRUD operations synchronization between OpenERPs. > > My original intent was to provide even more: send workflow events and send > the > call of methods, too. That way I would have synchronized basic OpenERP > instances with only the stock module installed (used at warehouses) with > the > company's main db. Although this approach didn't prove to be reliable, > stripping out the workflow and method sending code would result in a small > base > module suitable for B2B integration that I mentioned above. > > > Regards, > Gábor Dukai > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-expert-framework > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-expert-framework > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
