Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of stefan.guggisberg@gmail.com
 designates 64.233.166.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=IVNE3joMlfyxHr0GQPoeQ9baZ4F3dFlVuNYps9OGuH8uIfg94Pry/VIrN+APqz76p5gvACrBzgg2neJyzGy+gV0nilEQ5OefXnPVtXOd2HhJicB7ORI2XBptSi24qHL91SrfLNUoCpLc98wOJ3P7qhu0ZmJAqEId7sVsX7iJBkY=
Message-ID: <90a8d1c00608070101g5bdd9706lb90872fde371ffcf@mail.gmail.com>
Date: Mon, 7 Aug 2006 10:01:19 +0200
From: "Stefan Guggisberg" <stefan.guggisberg@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Re: AbstractSAXEventGenerator query
In-Reply-To: <44D6410C.4040709@sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fcbb46050608061159v7a68d6b5le27d7bc0c955f0b8@mail.gmail.com>
	 <44D6410C.4040709@sri.com>

On 8/6/06, Jack Park <jack.park@sri.com> wrote:
> What might be the objections raised to turning this abstract class into
> a public one (in future distributions) for purposes of allowing others
> to write exporters in jackrabbit applications that have different
> behaviors? That would be done by externally extending this class. (I
> realize that, as a default, one can simply duplicate the code in this
> class externally).

AbstractSAXEventGenerator is a core class. i try to avoid making internal
jackrabbit classes public in order to discourage their use from outside of the
core package. core classes should not be externally referenced as they might
change at any time and without notice.

if AbstractSAXEventGenerator is reasonably generic and without
dependencies on the core we could consider moving it to a 'util'
package. feel free to file an 'enhancement' issue.

>
> As a for instance, I would prefer to be able to just export an arbitrary
> node (perhaps there is a way, but I haven't found it), and I'd prefer to
> have the namespace declarations not go with the first node exported, but
> instead, go with a set of declarations outside nodes.
> And, I wouldn't mind a closing </node> tag (not available in an svn
> build from a month ago, possibly changed lately?)

i seriously doubt that the exported xml is not wellformed. please create a
jira issue if you can proof me wrong.

cheers
stefan

>
> Thanks.
> Jack
>