Over the last years, I have hardly seen anyone using the xbean-spring stuff anymore. I think most of custom namespaces have been implemented using JAXB instead. I think one of the problem is that the xml tends to be ugly, so starting from the xml and using JAXB usually makes more sense. I guess if you plan to use it in ActiveMQ, the generated schema has to be compatible with the previous ones, right ? Is that the case with your changes ?
Guillaume Le jeu. 2 août 2018 à 16:17, <[email protected]> a écrit : > Ladies and gentlemen, > I started messing around XBean as its codebase is in moderate form. I’ve > run into multiple issues while trying to get it running under Karaf 4.1 > together with ActiveMQ and decided to push it forward. I spent last couple > of days cleaning up duplicated code and refactoring maven plugin so it does > not depend on any specific generator. There is still lots of things to do > as there are several Spring tests which are failing. Due to stronger schema > validation around 15 spring tests currently fails. This is because > generated schema works only for basic elements and fails with embedded > collections. I already started to reform that part and I should be able to > update XsdGenerator. > > I would like to submit PR once I solve all the issues and test it with > ActiveMQ would you accept my work? Due to amount of breaking changes I > started 5.0.x branch (which might be good to start support Spring 4 or 5). > There is one big commit so far in my GitHub fork: > https://github.com/splatch/geronimo-xbean/tree/xbean-5.0.x, which I can > chunk into smaller (yet non compilable) commits in order to make history a > bit clearer. > > Kind regards, > Łukasz > — > Apache Karaf Commiter & PMC member > [email protected] > Twitter: ldywicki > Blog: http://dywicki.pl > Code-House - http://code-house.org > > -- ------------------------ Guillaume Nodet
