Hi everybody, Currently I am trying to do an integration of kandula2 with one of our products.
What I am interested in is do you tend to keep Kandula2 in synch with the latest axis2 snapshots. I mean axis2 guys are doing lots of changes, but kandula2 still uses some old axis2 versions which can be seen from project.properties' "Versions of dependencies" section. The other jars cited in this maven file are also not the latest ones. I will try these days to synch the kandula2 with more resent axis2, but I will appreciate any comments. May be you have some experience with this process. I have already had some experience to do that. For example in the more recent version of axis-kernel.jar org.apache.axis2.context.ServiceContexthas been changed and one of the constructors used into kandula2 has different modifier, it was "public" now it has none (so it is none(package) access modifier). Another thing happened is that I should refactor the kandula2 src because for example it was expecting org.oasis_open.docs.ws_tx.wscoor._2006._06.CoordinationContext_type3, but org.oasis_open.docs.ws_tx.wscoor._2006._06.CoordinationContext_type0 was generated after invoking maven. Another example is Identifier_type1 is generated as Identifier_type0. There are some AxisFault and exception handling changes, too. Do you think to migrate to java 1.5? As we can see from project.properties' "Compile" section 1.3 version is used. Any comments? Another question is do you've thought about moving to maven2. Do you think it will be a hard task? What are the reasons not to do that yet? Just lack of time or something more? Thank you in advance!
