[jdom-interest] org.jdom.Namespace not implementing Serializable?

Thu Jul 20 22:10:51 PDT 2000

> 1.  Should Namespace be Serializable?  

Yes, and making it so is in our public TODO.txt under CVS.

> 2.  Anybody got any idea why RMI tries to serialize Namespace in the first
> place when I'm only trying to pass around an instance of a Document  (which
> contains no references to Namespace)?

Jools answered this well.

-jh-

Received: from exch01.netivation.com (IP097.netivation.com [208.44.18.97])
	by dorothy.denveronline.net (8.9.3/8.9.3) with ESMTP id RAA25565
	for <jdom-interest at jdom.org>; Thu, 20 Jul 2000 17:06:03 -0600 (MDT)
Received: by EXCH01 with Internet Mail Service (5.5.2650.21)
	id <PHZHC8YL>; Thu, 20 Jul 2000 16:05:51 -0700
Message-ID: <F5887AB32E0AD411BADE00B0D0207AB96C40F9 at EXCH01>
From: "Eddy, Joel" <joel.eddy at medinex.com>
To: jdom-interest at jdom.org
Date: Thu, 20 Jul 2000 16:05:50 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFF29F.0C2A64D0"
Subject: [jdom-interest] ok...
Sender: jdom-interest-admin at jdom.org
Errors-To: jdom-interest-admin at jdom.org
X-BeenThere: jdom-interest at jdom.org
X-Mailman-Version: 2.0beta2
Precedence: bulk
List-Id: JDOM Mailing List for General Issues and Updates <jdom-interest.jdom.org>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFF29F.0C2A64D0
Content-Type: text/plain;
	charset="iso-8859-1"

i have been using some of the fundamental classes associated with jdom and
xalan... so far so good.. much success and quickly.. i am very happy

i was wondering is there a way to build an xsl template using dom, sax, jdom
or some other package.. the key is keep from having to use the filesystem..
and just stick to an RDBMS, memory, and EJB's for generating XML and
displaying it... 

any ideas? :)

------_=_NextPart_001_01BFF29F.0C2A64D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2652.35">
<TITLE>ok...</TITLE>
</HEAD>
<BODY>

i have been using some of the fundamental classes =
associated with jdom and xalan... so far so good.. much success and =
quickly.. i am very happy

i was wondering is there a way to build an xsl =
template using dom, sax, jdom or some other package.. the key is keep =
from having to use the filesystem.. and just stick to an RDBMS, memory, =
and EJB's for generating XML and displaying it...

<P><FONT SIZE=3D2>any ideas? :)</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFF29F.0C2A64D0--