Today I've got good news that JaxMe 2 shows its second big step. Thank everyone for making this come true. By the way, I posted a proposal on adding RawXMLWriterImpl to JaxMe 2 for non-Latin users hoping to marshal in a "as-it-is" way like JWSDP 1.2 default behavior and renaming XMLWriter14 to CharsetXMLWriterImpl for more compatibility with other implementation classes and more clarity that doesn't depend on JDK version. The latest JaxMe 2 distribution doesn't reflect the proposal, and I'd like to hear what you think of that.
In my opinion, adding RawXMLWriterImpl has more priority to renaming
XMLWriter14.
Regards,
Ias
=========================================================
Lee, Changshin (Korean name)
Ias (International name)
Company Web Site: http://www.tmax.co.kr
Personal Web Site: http://www.iasandcb.pe.kr
---------------------------------------------------------
Senior Researcher, Emerging Technology Evangelist
JCP member - http://jcp.org/en/participation/members/L
R&D Institute
Tmax Soft, Inc.
JCP member - http://jcp.org/en/participation/members/T
=========================================================
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ias
> Sent: Wednesday, August 27, 2003 4:40 PM
> To: 'Jochen Wiedmann'
> Cc: [EMAIL PROTECTED]
>
> >
> > -----Original Message-----
> > From: WWW [mailto:[EMAIL PROTECTED] On Behalf Of Jochen Wiedmann
> > Sent: Tuesday, August 26, 2003 10:43 PM
> > To: Ias
> > Cc: [EMAIL PROTECTED]
> >
> >
> > Hi, Ias,
> >
> > thanks for the patches. I have added them to the
> repository, with some
> > minor changes:
> >
> > - The property jaxme.xml.writer is not a string, but a
> class. This has
> > a couple of advantages, in particular we need not care for
> > classloader
> > issues and the User can cache the class (for example by using
> > MyWriter.class), which is faster than instantiating it every time.
> >
> > - I made XMLWriter an interface. Of course you have been
> right, that
> > the
> > setWriter() method wasn't sufficient. I have added yet another
> > method
> >
> > publuc void init(JMMarshallerImpl pController) throws
> > JAXBException;
> >
> > To be invoked by the Marshaller, when he created the
> XMLWriter. In
> > the
> > case of the XMLWriter14 this can be used to read the desirec
> > encoding.
> >
> Thanks, now this interface enables users to configure their
> writers with sort of lifecycle concept.
>
> > - Depending on the runtime environment, the XMLWriter14 is now
> > actually
> > used. The test suite, however, is still using the
> XMLWriter. May be
> > we have to change this.
> >
> > Forgot to add the RawXMLWriter, although it is definitely a
> nice idea.
> >
> I attached a new raw writer, RawXMLWriterImpl compliant with
> XMLWriter interface. I hope this writer also can be one of
> the writers that JaxMe 2 provides for non-Latin users.
>
> Ultimately, I'd like to suggest about renaming of
> XMLWriter14. IMO, CharsetXMLWriterImpl could be more
> appropriate in accordance with package
> (net.sf.jaxme.impl) and other XMLWriter implementations such
> as XMLWriterImpl and RawXMLWriterImpl.
>
> Ias
>
> >
> >
> > Jochen
> >
> >
>
RawXMLWriterImpl.java
Description: a/octet-stream
