 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | SV: [jdom-interest] Announcing JDOM b10-rc1 | SV: [jdom-interest] Announcing JDOM b10-rc1 2004-02-15 - By Jason Hunter
Back
Per Norrman wrote:
> I think this is my point: Stick with the initial vision, follow through
> with the
> consequences. You are never going to achieve the perfect API**. Skip
> Parent/Child!
Unless you can show how Parent/Child is seriously damaging, I'm inclined
to leave it because I'm serious about finishing 1.0 on time -- no more
distractions in the quest for the perfect API -- and to rip it out would
take a day's worth of effort and another debugging cycle.
> Two other issues, perhaps on a smaller scale:
>
> *) Did you consider the change I proposed to XMLOutputter?
> http://www.servlets.com/archive/servlet/ReadMsg?msgId=447565&listName=jd
> om-interest
Yeah, we're trying not to expose too many protected methods that we'll
have to keep around in the future. printNamespace() is an internal
method that shouldn't be counted on remaining over the long haul. Since
you can do your subclassing and just copy/paste the method code (god
bless open source) I think that's a better solution. Less elegant
today, more elegant long term.
> *) Why can't I *get* the current Format from XMLOutputter?
Fixed.
-jh-
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@(protected)
.com
Earn $52 per hosting referral at Lunarpages.
|
|
|
