Menu
▾
▴
xmlenc-devel — Discussion of development of xmlenc
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(30) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
|
| 2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Henri Y. <ba...@ge...> - 2003-01-06 16:35:54
|
On Mon, 6 Jan 2003, Ernst de Haan wrote: > > Okay. Would it be good enough if I would upload a file to the sourceforge > > site with each release: > > > > http://xmlenc.sourceforge.net/xmlenc-${version}.jar > > > > ? If so, then that would solve the issue without having to rename files > > inside my .tar.gz. > > Done in HEAD. Try fetching: > > http://xmlenc.sourceforge.net/xmlenc-0.21-dev.jar Yep, it works. Any chance of 0.20 too? Stable versions are probably better to be published at maven. Hen |
|
From: Henri Y. <ba...@ge...> - 2003-01-06 16:34:28
|
On Mon, 6 Jan 2003, Ernst de Haan wrote: > Hey Henri, > > > proejct.xml I can say: > > > > I use xmlenc, version 0.20. And it will automatically grab it. > > Okay. Would it be good enough if I would upload a file to the sourceforge > site with each release: > > http://xmlenc.sourceforge.net/xmlenc-${version}.jar > > ? If so, then that would solve the issue without having to rename files > inside my .tar.gz. Sounds good. If you could do that, I'll get onto asking them to publish it on ibiblio. I have some minor hopes that Maven will turn into CJAN for us someday and Java can finally stop being so jealous of CPAN. Hen |
|
From: Ernst de H. <zn...@Fr...> - 2003-01-06 16:31:15
|
> Okay. Would it be good enough if I would upload a file to the sourceforge > site with each release: > > http://xmlenc.sourceforge.net/xmlenc-${version}.jar > > ? If so, then that would solve the issue without having to rename files > inside my .tar.gz. Done in HEAD. Try fetching: http://xmlenc.sourceforge.net/xmlenc-0.21-dev.jar > > I'd like to get a version of xmlenc up at ibiblio's maven site, which > > might help advertise it as a side-effect. While they will accept any > > naming scheme, it makes thigns a lot smoother if the naming scheme is > > akin to theirs. Regards, Ernst -- Ernst de Haan Development Team Leader Wanadoo Nederland B.V. The Lord has truly risen! Merry Christmas and a blessed New Year! |
|
From: Henri Y. <ba...@ge...> - 2003-01-06 16:21:32
|
On Mon, 6 Jan 2003, Ernst de Haan wrote: > Hi Henri, > > > One thing, have you considered including the version number in the jar > > name? > > > > ie) xmlenc-0.20.jar ? > > Why? It fits nicely with the Maven naming scheme. So in the XmlWriter proejct.xml I can say: I use xmlenc, version 0.20. And it will automatically grab it. I'd like to get a version of xmlenc up at ibiblio's maven site, which might help advertise it as a side-effect. While they will accept any naming scheme, it makes thigns a lot smoother if the naming scheme is akin to theirs. Hen |
|
From: Henri Y. <ba...@ge...> - 2003-01-04 21:38:24
|
On Mon, 30 Dec 2002, Ernst de Haan wrote: > I've been thinking about the cooperation between our 2 projects, xmlenc and > xmlwriter. I would like to have a separate JAR for xmlenc, so that people > can use that as a real small and thin XML output library, for example in > J2ME applications. Yep. Sourceforge gives a project their own repository [I'd assumed module when I started, thus xmlwriter/xmlwriter]. We could have two separate modules in the repository, one for xmlenc and one for xmlwriter. > On the other hand, a tighter integration between the 2 projects is good. > Perhaps we could use a model similar to lex and yacc. Not used them a lot, but I think I get your drift. > We could name our projects loxol and hixol or so, for Low-level XML Output > Library and High-level XML Output Library. Or loxo and hixo. Or lox and > hix. Or maybe this sounds stupid. I was thinking XmlIO at first, but a C++ project has that. Plus we do no input. So how about XmlOutput? [then we just get to argue over XMLOutput vs XmlOutput. Sun spec says XmlOutput, but even they don't obey that and I suspect we should do XMLOutput]. Inside that we would then have separate module/sub-project names. Hix/Lox. Hilo/Lolo. Hen |
|
From: Henri Y. <ba...@ge...> - 2003-01-04 21:32:17
|
On Mon, 30 Dec 2002, Ernst de Haan wrote: > Hi Henri, > > > I've got a nightly build going, which I can happily do for xmlenc if you > > want too [would be easiest to put a maven project.xml in the home dir, > > but I can work around it and use ant instead, currently xmlenc doesn't > > build for me but I assume it's my fault]. > > What exactly do you mean? I checked the xmlenc source out, but when I 'ant'd, it had issues. I may have just been being sleepy as when I build it now it just complains that JDOM is not available. This is 0.18, and I've moved to 0.20 now. > > http://www.flamefew.net/~hen/xmlwriter-design.jpg > > Looks very good! Communication using UML diagrams is really nice. Only difference is that XmlStreamXmlWriter is now XmlEncXmlWriter, and that SchemaCheckingXmlWriter is still JarvXmlWriter. I've migrated to xmlenc 0.20. > > PrettyPrinting pretty prints on top of one of the other two [though it's > > not working atm]. > > Ah, real nice! Working now. I suspect it has issues, but I think I've tweaked and murdered Pete's code enough that it seems to work on basic tests. > > EmptyElement handles the different strategies for null/"". > > This one then wraps another instance, I presume? And what is the default > behaviour for other XmlWriters? They ignore the issue and pass things on. SimpleXmlWriter [xmlenc competitor as such] will print out "null" if passed null. > > Formatted handles DateFormat and NumberFormat, though I think it should > > be a bit more generic and map Classes to Formats. > > How exactly are these formats used? I can't see a use for them. Doesn't mean > there is none though... :-) At work, our biggest use of xml writing is to send xml to a Flash client. It's a real pain to have to keep remembering to do format.format(date) instead of just setting that format in the writer and then writing out whenever we want to. We also get told that numbers must not print decimal places and have to code that in. The XmlWriter interface writes Objects and not Strings, so using java.text.Format extensions to format those Objects is a nice trick. Currently FormattingXmlWriter has a NumberFormat and a DateFormat. I think it ought to map a Class to a Format. I suspect that this will often not be enough as you'll want to output a percentage, decimal and currency in the same xml, but they all map to Number etc. > > XmlIOFactory doesn't exist, but was what I was envisioning being the > > facade behind which lots of this would hide. Not too sure exactly how > > this would look though. > > Is this just the Factory pattern? Yeah. Basically, how should a user setup their chain of XmlWriters. They could do: Writer sw = new StringWriter(); XmlWriter xw = new XmlEncXmlWriter(sw); xw = new FormattingXmlWriter(xw).setDateFormat(new java.text.SimpleDateF ormat("yyyy-MM-dd")).setNumberFormat(new java.text.DecimalFormat("#")); xw = new EmptyElementXmlWriter(xw).setEmptyMode(EmptyElementXmlWriter.NU LL_EMPTY_MODE); xw = new PrettyPrinterXmlWriter(xw); [I've made all setXxx methods return their object. Probably breaks the Bean-ness, but I'm treating this as a play with the method-chaining viewpoint] or they could do: XmlWriter xw = XmlIO.prettyPrinter( XmlIO.emptyElement( XmlIO.NULL_EMPTY_MODE, XmlIO.formatted( "yyyy-MM-dd", "#", XmlIO.xmlenc( new StringWriter() ) ) ) ); Other XmlWriter changes: I've added getWriter() so that the underlying Writer is obtainable. While hiding this is good encapsulation, it also limits the user to the power of our API. If our API doesn't do it, they've no hope at hacking around. Plus they gave us the Writer in the first place anyway. Hen |
|
From: Henri Y. <ba...@ge...> - 2003-01-04 21:03:31
|
Will do then. Not sure if sourceforge will let me point elsewhere, but I can at least point the maven site over. One thing, have you considered including the version number in the jar name? ie) xmlenc-0.20.jar ? The Jar's manifest is also supposed to contain version info, but I must admit that I just let Maven put this in for me. Hen On Mon, 30 Dec 2002, Ernst de Haan wrote: > On Friday 27 December 2002 09:37, Henri Yandell wrote: > > Any objection to me pointing the xmlwriter project to using the xmlenc > > mailing list? :) Assuming I can suitably explain on the site as to why > > they're being sent to the xmlenc site. > > None at all. > > Ernst > > -- > Ernst de Haan > Development Team Leader > Wanadoo Nederland B.V. > > The Lord has truly risen! > Merry Christmas and a blessed New Year! > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > xmlenc-devel mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlenc-devel > |
|
From: Ernst de H. <zn...@Fr...> - 2003-01-01 06:07:24
|
On Friday 27 December 2002 09:37, Henri Yandell wrote:
> Any objection to me pointing the xmlwriter project to using the xmlenc
> mailing list? :) Assuming I can suitably explain on the site as to why
> they're being sent to the xmlenc site.
None at all.
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
The Lord has truly risen!
Merry Christmas and a blessed New Year!
|
|
From: Ernst de H. <zn...@Fr...> - 2003-01-01 06:07:23
|
Hi Henri, > I've got a nightly build going, which I can happily do for xmlenc if you > want too [would be easiest to put a maven project.xml in the home dir, > but I can work around it and use ant instead, currently xmlenc doesn't > build for me but I assume it's my fault]. What exactly do you mean? > http://www.flamefew.net/~hen/xmlwriter-design.jpg Looks very good! Communication using UML diagrams is really nice. > SimpleXml and XmlStream [sits on xmlenc, needs updating] are the active > workers while the DelegatingXmlWriter's are Decorators [and might get > named thus]. The class XMLStream was renamed to XMLOutputter, after discussion with Pete. > PrettyPrinting pretty prints on top of one of the other two [though it's > not working atm]. Ah, real nice! > EmptyElement handles the different strategies for null/"". This one then wraps another instance, I presume? And what is the default behaviour for other XmlWriters? > Formatted handles DateFormat and NumberFormat, though I think it should > be a bit more generic and map Classes to Formats. How exactly are these formats used? I can't see a use for them. Doesn't mean there is none though... :-) > SchemaChecking [JarvWriter currently] uses JARV api to check the xml > being output to a xml schema/dtd/relax-ng. Wow, sounds good! > XmlIOFactory doesn't exist, but was what I was envisioning being the > facade behind which lots of this would hide. Not too sure exactly how > this would look though. Is this just the Factory pattern? > I'm not sure what's in 0.19 of xmlenc, will need to update my code from > the 0.18 I was using. See the release notes on sourceforge. Mainly rename of XMLStream to XMLOutputter, stag(String) to startTag(String) and etag() to endTag(). Ernst -- Ernst de Haan Development Team Leader Wanadoo Nederland B.V. The Lord has truly risen! Merry Christmas and a blessed New Year! |
|
From: Ernst de H. <zn...@Fr...> - 2003-01-01 06:07:21
|
I've been thinking about the cooperation between our 2 projects, xmlenc and
xmlwriter. I would like to have a separate JAR for xmlenc, so that people
can use that as a real small and thin XML output library, for example in
J2ME applications.
On the other hand, a tighter integration between the 2 projects is good.
Perhaps we could use a model similar to lex and yacc.
We could name our projects loxol and hixol or so, for Low-level XML Output
Library and High-level XML Output Library. Or loxo and hixo. Or lox and
hix. Or maybe this sounds stupid.
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
The Lord has truly risen!
Merry Christmas and a blessed New Year!
|
|
From: Pete C. <pe...@fi...> - 2002-12-29 04:41:22
|
Henri, Hope you had a nice Christmas too. Your work on XmlWriter is all very interesting. My production use of XmlWriter uses an older build. I'll probably stick with that for now, until I either need some new feature or the new scheme crystallizes into a release build. Your JPEG of the new class hierarchy is quite impressive. One of the things I liked about XmlWriter in the beginning was its simplicity (one little source code file that I got my feeble mind around inside of 15-20 minutes). But the more elaborate system you're moving to is still quite easy for me to understand. I may have a few "why" questions as I take a closer look, but it seems like you're doing a good job with the design. Happy New Year to all, Pete Cassetta pe...@fi... ------------------------------------------- Fingertip Software 433 Kitty Hawk Rd., Suite 216 P.O. Box 2487 Universal City, TX 78148 Orders: (800) 209-4063 -or- (210) 659-6832 Support: (210) 659-2532 Fax: (210) 659-8870 http://www.fingertipsoft.com ------------------------------------------- |
|
From: Henri Y. <ba...@ge...> - 2002-12-27 08:37:47
|
Any objection to me pointing the xmlwriter project to using the xmlenc mailing list? :) Assuming I can suitably explain on the site as to why they're being sent to the xmlenc site. Hen |
|
From: Henri Y. <ba...@ge...> - 2002-12-27 08:30:47
|
Sorry for being quiet recently, would you believe it was because I was working on xmlwriter? :) I've got a nightly build going, which I can happily do for xmlenc if you want too [would be easiest to put a maven project.xml in the home dir, but I can work around it and use ant instead, currently xmlenc doesn't build for me but I assume it's my fault]. I've pulled the xmlwriter code apart and put in various new bits. It's odd reading the xmlenc mailing list, moving to startTag and endTag was a direction I was going too :) Had a complaint about 'Entity' being the wrong word to use. A design may be seen at: http://www.flamefew.net/~hen/xmlwriter-design.jpg SimpleXml and XmlStream [sits on xmlenc, needs updating] are the active workers while the DelegatingXmlWriter's are Decorators [and might get named thus]. PrettyPrinting pretty prints on top of one of the other two [though it's not working atm]. EmptyElement handles the different strategies for null/"". Formatted handles DateFormat and NumberFormat, though I think it should be a bit more generic and map Classes to Formats. SchemaChecking [JarvWriter currently] uses JARV api to check the xml being output to a xml schema/dtd/relax-ng. XmlIOFactory doesn't exist, but was what I was envisioning being the facade behind which lots of this would hide. Not too sure exactly how this would look though. I'll do a cvs tag tomorrow and start pushing things in. I'm not sure what's in 0.19 of xmlenc, will need to update my code from the 0.18 I was using. Hen |
|
From: Ernst de H. <zn...@Fr...> - 2002-12-18 14:09:46
|
FYI: xmlenc 0.19 was released today.
Changes:
The main class was renamed to XMLOutputter, stag() to startTag(), and
etag() to endTag(). Bugs in startTag() and entityRef() were fixed.
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
|
|
From: Ernst de H. <zn...@Fr...> - 2002-12-18 14:07:00
|
> Proposal:
> * Rename stag(String) to startTag(String)
> * Rename etag(String) to endTag(String)
This has been implemented in CVS HEAD. It will be introduced in xmlenc 0.19.
> In the past a goal was to keep the naming as close as possible to the XML
> specification. However, at this time I believe it should be close to XML,
> but closer to Java naming conventions.
>
> If we would let method names be as close as possible to the XML Spec,
> then the whitespace(String) method should be renamed to s(String) and
> that is IMO not acceptable.
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
|
|
From: Ernst de H. <zn...@Fr...> - 2002-12-12 12:55:05
|
Proposal:
* Rename stag(String) to startTag(String)
* Rename etag(String) to endTag(String)
In the past a goal was to keep the naming as close as possible to the XML
specification. However, at this time I believe it should be close to XML,
but closer to Java naming conventions.
If we would let method names be as close as possible to the XML Spec, then
the whitespace(String) method should be renamed to s(String) and that is
IMO not acceptable.
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
|
|
From: Ernst de H. <zn...@Fr...> - 2002-12-09 12:41:12
|
> One question for Ernst: why did you name the class XMLStream instead of
> XMLWriter? I think the latter is more appropriate, as you're obviously
> using a Writer internally. For example, you have a getWriter() method
> but no getStream() method.
The fact that the class uses a Writer internally has IMHO no impact on the
name of the class. I could use an OutputStream instead of a Writer without
affecting the name.
I couldn't really find a single name that matches the class's function the
best. Some alternatives:
a. XMLEncoder
b. XMLStream
c. XMLOutputter
d. XMLPrinter
e. XMLWriter
f. XMLGenerator
What if we just stay with XMLStream? Is there an appelling reason to use a
different name? Is is considered inappropriate or confusing? If so, then we
should change it, otherwise I think we should just leave it as it is.
[ I will react to your other queries in separate emails, to keep the threads
subject-specific ]
Regards,
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
|
|
From: Ernst de H. <zn...@Fr...> - 2002-12-09 12:41:11
|
> Your proposal of setEscaping() and isEscaping() seems fine to me, though
> I haven't encountered a need for this capability myself. If it seems
> generally useful though, go ahead.
The problem is that entity references cannot be printed in attribute values
nor in comments.
After reconsideration, here's an improved (IMO) proposal.
* setEscaping(boolean enable)
Enables or disables escaping of ampersands. If entity references should be
printed, then escaping should be disabled. This setting applies to
pcdata(String), whitespace(String) and to the attribute value passed to
attribute(String,String).
See: isEscaping()
* isEscaping()
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
|
|
From: Ernst de H. <zn...@Fr...> - 2002-12-09 12:41:10
|
> I didn't understand why you are planning this:
> > I would like to introduce a new class that is responsible only for the
> > different types of output (raw, PCDATA with char entity replacements,
> > attribute values, etc).
>
> Could you elaborate on this thought some time?
Currently the main class (XMLStream, previously XMLEncoder) inheritance
chain is based on the low-level, encoding-specific, output characteristics.
There are 2 subclasses, one for Unicode encodings and one for ASCII-based
encodings.
If the main class should be extensible in terms of functionality or
behaviour, then a new class should be introduced to encapsulate the
low-level output characteristics. Then the main class will delegate that to
this new class.
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
|
|
From: Pete C. <pe...@fi...> - 2002-11-30 04:44:38
|
Hi guys, I'm mostly just trying out the mailing list. One question for Ernst: why did you name the class XMLStream instead of XMLWriter? I think the latter is more appropriate, as you're obviously using a Writer internally. For example, you have a getWriter() method but no getStream() method. If you're worried about conflicting with the name of our XmlWriter, I don't think we need to worry about that. We should just choose the best name. Anyway, we used different capitalization in XmlWriter. Your proposal of setEscaping() and isEscaping() seems fine to me, though I haven't encountered a need for this capability myself. If it seems generally useful though, go ahead. I didn't understand why you are planning this: > I would like to introduce a new class that is responsible only for the > different types of output (raw, PCDATA with char entity replacements, > attribute values, etc). Could you elaborate on this thought some time? Gratefully, Pete Cassetta pe...@fi... ------------------------------------------- Fingertip Software 433 Kitty Hawk Rd., Suite 216 P.O. Box 2487 Universal City, TX 78148 Orders: (800) 209-4063 -or- (210) 659-6832 Support: (210) 659-2532 Fax: (210) 659-8870 http://www.fingertipsoft.com ------------------------------------------- |
|
From: Ernst de H. <zn...@Fr...> - 2002-11-29 08:10:53
|
This is a test. Please ignore.
Ernst
--
Ernst de Haan
Development Team Leader
Wanadoo Nederland B.V.
"Come to me all who are weary and burdened
and I will give you rest" -- Jesus Christ
|
|
From: Ernst de H. <zn...@Fr...> - 2002-11-29 08:10:52
|
This is a test. |
2 messages has been excluded from this view by a project administrator.
