I think we can use [1] to convert messaging component data model to python at the build time and the agent can refer that directly. WDYT?
[1] https://github.com/natural/java2python On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <chami...@wso2.com> wrote: > Hi Raj, > > On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Please double check the java agent code too. It works somehow. Don't know >> the reason :) > > > The Java agent makes use of the org.apache.stratos.messaging component, so > any changes done from a publisher's point of view is reflected on a > receiver's end. In the Python agent, the serialization and the > deserialization of the events published and received from the message > broker is written anew in Python. > > The problem rises here, when the changes made in the messaging component > needs to be reflected in the Python agent too. I think for the time being > whenever a change is done, it is better to assign the relevant JIRA issue > to the person responsible of the changes in Python cartridge agent, which > is me for now :). > > In the long run, a set of unit tests can manage the changing code better. > > > Regards, > Chamila de Alwis > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > >
