Ralf Joachim wrote: > Hi Werner and Joachim > > I share Joachim's opinion that we should not create an own module for > pull parsing but instead integrate into into the XML module even if this > introduces the new dependency to StaX-API.
Sorry, guys, but this is like saying let's install mySQL right now, even if we do not need it (as we might be heading towards a OO database anyhow). Why increase the number of JARs artificially for somebody wishing to use Castor as is ? > We are introducing a new (and OPTIONAL) module that enables > pull parsing using STaX on top of it. Why force folks to have > to 'import' the StaX-API dependency when all they want is to > use SAX-absed (un)marshalling. Let me try to apply your argument to something elese to give it anotehr spin. This is like saying 'Let's move spring orm back into spring-jdbc, as they are both using JDBC as underlying technology; or let's move spring-oxm back into spring-ws, as web services is about XML, correct ? In both cases, the authors of those modules have made decisions to split functionality into separate 8and thus smaller) modules, paying carefully attention to limiting the dependencies as defined in the POMs to the core minimum. I can only invite you to read the maven users list, or the codehasu mojo dev lists 8archives) where such discussions are 'held' again and again. > > Having said that I would also appreciate the XML_DIFF module to disapear > and be integrated into one of the other modules. Feel free to have a go at this. In other words, it is not that I did not try. have a look at what XMLDiff needs, and you'll come to a conclusion yourself. > In other words, I do not prefer to create new modules for a few classes > that only refer to small general purpose API's like StaX. If a bunch of > classes introduce a dependency to big or specific libs I would take a > new module into account. Ralf, are you trying to say that as long as the size of the JAR of the API is small, you don't care ? > Regards > Ralf > > > Werner Guttmann schrieb: >> Joachim Grüneis wrote: >> >>> Hello, >>> >>> as for another question of this topic... >>> >>> wouldn't it be good to have the StAX-SAX translation inside the xml module? >>> >> I don't think this is teh right way forward. Castor XML uses SAX only >> for (un-)marshalling, and has its dependencies optimized for this purpose. >> >> We are introducing a new (and OPTIONAL) module that enables pull parsing >> using STaX on top of it. Why force folks to have to 'import' the >> StaX-API dependency when all they want is to use SAX-absed (un)marshalling. >> >> >>> and the rest a new module... >>> I'm just a bit reluctant to still increase the numbers of modules >>> Castor consists of >>> >> Why. It has so many benefits .... which I ma happy to enumerate agin, >> if required. >> >> >>> and besides the translation it would be only very few classes the >>> fragment mapper introduces... >>> the next patch will show this in more detail >>> >>> Joachim >>> >>> 2008/11/13 Joachim Grüneis <[EMAIL PROTECTED]>: >>> >>>> Hello, >>>> >>>> I'm currently converting the ANTLR stuff to JavaCC - to be exact I >>>> first searched for a ready JavaCC solution, which I didn't find, and >>>> now I rewrite the ANTLR grammer to JavaCC to reduce the dependencies >>>> and technologies we use... >>>> >>>> Joachim >>>> >>>> 2008/11/13 Werner Guttmann <[EMAIL PROTECTED]>: >>>> >>>>> Joachim, >>>>> >>>>> any progress on your side ? An opinion ? An updated Maven POM ? Anything >>>>> ? I am sure you have read the mentor agreement you have signed with >>>>> Google, right ? >>>>> >>>>> Werner >>>>> >>>>> Joachim Grüneis wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> after adapting the existing pull purser patch I'm not 100% sure if we >>>>>> should have it in the main source tree of Castor... >>>>>> it requires StAX API's, StAX implementation and two ANTLR libraries >>>>>> maybe - even that it is a very small piece of code - we should have it >>>>>> in an own project? >>>>>> >>>>>> what is your opinion? >>>>>> >>>>>> Joachim >>>>>> >>>>>> 2008/10/23 Werner Guttmann <[EMAIL PROTECTED]>: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> any chances of committing yourself to a firm deadline? I would like to >>>>>>> ship 1.3 final any time soon, and I do not want to be waiting for weeks. >>>>>>> >>>>>>> Werner >>>>>>> >>>>>>> Joachim Grüneis wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I plan to add it to the code base within the next days... >>>>>>>> >>>>>>>> Joachim >>>>>>>> >>>>>>>> 2008/10/22 Werner Guttmann <[EMAIL PROTECTED]>: >>>>>>>> >>>>>>>>> Hi Joachim, >>>>>>>>> >>>>>>>>> what are your plans of committing the pull-parsing add-on that has >>>>>>>>> been >>>>>>>>> developed as part of GSoC 2008 ? >>>>>>>>> >>>>>>>>> Werner >>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> To unsubscribe from this list, please visit: >>>>>>>>> >>>>>>>>> http://xircles.codehaus.org/manage_email >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe from this list, please visit: >>>>>>>> >>>>>>>> http://xircles.codehaus.org/manage_email >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe from this list, please visit: >>>>>>> >>>>>>> http://xircles.codehaus.org/manage_email >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe from this list, please visit: >>>>>> >>>>>> http://xircles.codehaus.org/manage_email >>>>>> >>>>>> >>>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>>> >>>>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
