Hi Adam, It kind of depends on what you've done. In your earlier email you mentioned eliminating reflection usage, ArrayList, Hashmap (though I think you meant HashMap, right?), List, Iterator, Collections, Comparator, and Classloader. Some of these are pretty easy to change, others might take some discussion.
My intention has always been to only make the runtime components J2ME compatible, rather than the binding code or the various tools. From a quick search through the org.jibx.runtime classes it looks like there are a few uses of ArrayList, some of which can be replaced by Vector (or by a custom class) and others which should just be eliminated in a J2ME build. Likewise with HashMap. Iterator can be eliminated completely from the J2ME build, and neither Collections nor Comparator appears to be used at all. But that leaves Classloader and reflection. These are hard to avoid, and would severely limit JiBX capabilities if eliminated (it'd be possible, but you'd have to do something like hard coding the name of the generated binding factory class into your application code, since you couldn't use the BindingDirectory class, and also hard code the kXML parser into the JiBX code). From looking at the J2ME specifications it appears that it's only the CDLC profile which requires eliminating these; the CDC profile allows them (along with ArrayList, HashMap, Collections, etc.). Is CDLC still so widely used that it's necessary to support it, rather than just going with the more lenient CDC restrictions? Unless you've been using the CVS code your changes will probably need to be revised to match the current code. Why don't you send me a diff for your changes along with the actual modified Java files and I'll look them over. If there's a substantial amount of code to be included directly I'll need to get a contributor agreement from you, but I suspect it's more a matter of a lot of small changes and that shouldn't require the agreement. Thanks for your interest in this area and your work in adapting JiBX to work for your needs! - Dennis Dennis M. Sosnoski XML and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Ádám Mautner wrote: > Dennis, > > I am using JiBX for J2ME. I have found a few issues with the current > JiBX implementation for J2ME. Since I have not found any solution to > my problems, I have changed JiBX source to introduce more extensive > J2ME support. > > I would like to give my solutions back to JiBX community, so other > people could enjoy JiBX for J2ME, > > How can I get my source code integrated to the next JiBX release? > Should I send it to you? Create a Jira? Check it in directly? > > Please help me out with this problem. > > Thank you. > > Regards, > > Adam > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > jibx-users mailing list > jibx-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jibx-users > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
