Hi Shameera, (Apologies for the late response.)
Shameera Rathnayaka <[email protected]> wrote on 04/25/2013 11:25:40 AM: > From: Shameera Rathnayaka <[email protected]> > To: [email protected], > Date: 04/25/2013 11:30 AM > Subject: Re: Interesting in doing GSOC 2013 with Xerces > > Hi Micheal, > > On Tue, Apr 23, 2013 at 1:15 AM, Michael Glavassevich <[email protected] > > wrote: > Hi Shameera, > > I'm a bit confused by what you meant in the first diagram. If StAXWriter > is the implementation of XMLStreamWriter wouldn't that contain the > "XMLStAXHandler"? It looks like you have it reversed. > > do you mean, something like this? It doesn't look like the image reached the mailing list or at least I didn't receive it. > Do we have any advantage of using xalan SerializerBase? As I see > SerializerBase inherited from set of SAX interfaces along with other > interfaces most of them will not be used under XMLStreamWriter > implementation(StAXWriter). Is it beacause to be inline with the > rest of xerces architecture ? SerializerBase provides quite a bit of infrastructure for XML serialization. It's well tested and stable so there could be value in reusing it, the advantages being that you're starting with something robust as a base, rather than re-writing the parts you would use from scratch. > Yes, if your project proposal is accepted for GSoC I would volunteer to > mentor it. > > Nice, > > Thanks, > Shameera > > > > > Thanks, > > Shameera. > > > > > On Sat, Apr 13, 2013 at 1:12 AM, Shameera Rathnayaka > <[email protected] > > > wrote: > > Hi Michael, > > > > On Fri, Apr 12, 2013 at 11:59 PM, Michael Glavassevich > <[email protected] > > > wrote: > > > > > No, you wouldn't use those DOM methods. LSSerializerImpl is an extension > > of Xalan's base serializer. I was suggesting that you could build a StAX > > serializer on top of Xalan's base serialization support (see the main > > org.apache.xml.serializer package). I believe those methods look more > like > > SAX, allowing you to stream the result. You should not need to build an > > in-memory model of the document. > > > > I looked at org.apache.xml.serializer package of Xalan's. > > Writing a StAX Writer by implementing both XMLStreamWriter and > > org.apache.xml.serializer.Serializer will do the works, > > as org.apache.xml.serializer.SerializerBase is more bias to DOM. WDYT? > > > > Thanks, > > Shameera. > > > > > > > Thanks, > > > Shameera. > > > > > > > > > An > > > XMLEventWriter could be layered on top of the XMLStreamWriter. > > > > > > If you'd like to get a feel for what a good proposal looks like > (content > > > and structural wise) there's a number of successful GSoC proposals > from > > > previous years up on the Xerces Wiki [1] which are great examples. > > > > > > Thanks. > > > > > > [1] http://wiki.apache.org/xerces/FrontPage > > > > > > Michael Glavassevich > > > XML Technologies and WAS Development > > > IBM Toronto Lab > > > E-mail: [email protected] > > > E-mail: [email protected] > > > > > > Shameera Rathnayaka <[email protected]> wrote on 06/04/2013 > > 02:12:02 > > > AM: > > > > > > > Hi devs/Michael Glavassevich, > > > > > > > > I have successfully done 2012 GSOC with Apache Axis2. In that I > > > > wrote a StAX XMLStreamWriter/Reader implementation to provide XML > > > > info-set using JSON input and output streams[1]. AXIOM use that to > > > > get the XML infoset. > > > > > > > > Xerces has proposed similar requirement which is to implement StAX > > > > XMLStreamWriter[2]. I have talked abut this under particular jira > > > > issue. Thought it would be good talk more about how to create an > > > > excellent proposal for that in dev list other than ruin the jira > issue > > > :). > > > > > > > > As i have mentioned we can provide XMLOutputFactory api which > > > > provide StAX XMLStreamWriter via createXMLStreamWriter(OutputStream > > > > stream), createXMLStreamWriter(OutputStream stream, String encoding) > > > > and createXMLStreamWriter(Writer stream). > > > > > > > > Above implementatinos , Documentation and unit test to cover those > > > > functionalities would perfectly match with GSOC scope. WDYT? > > > > > > > > Regars, > > > > Shameera > > > > > > > > [1] https://issues.apache.org/jira/browse/AXIS2-5270 > > > > [2] https://issues.apache.org/jira/browse/XERCESJ-1558 > > > > > > > > -- > > > > Best Regards, > > > > Shameera Rathnayaka. > > > > > > > > Blog : http://shameerarathnayaka.blogspot.com/ > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > Thanks. > > > > Michael Glavassevich > > XML Technologies and WAS Development > > IBM Toronto Lab > > E-mail: [email protected] > > E-mail: [email protected] > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > -- > > Best Regards, > > Shameera Rathnayaka. > > > > Blog : http://shameerarathnayaka.blogspot.com/ > > > > > > > -- > > Best Regards, > > Shameera Rathnayaka. > > > > Blog : http://shameerarathnayaka.blogspot.com/ > > Thanks. > > Michael Glavassevich > XML Technologies and WAS Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- > Best Regards, > Shameera Rathnayaka. > > email: shameera AT apache.org , shameerainfo AT gmail.com > Blog : http://shameerarathnayaka.blogspot.com/ Thanks. Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
