Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
To: cocoon-dev@xml.apache.org
Subject: RE: AW: AW: [C2] sitemap editor
Message-ID: <994677163.3b4991ab3a14c@mail.otego.com>
Date: Mon, 09 Jul 2001 13:12:43 +0200 (CEST)
From: Giacomo Pati <giacomo@apache.org>
References: <9E725728E7D0D311B24D00508B6A0543018D6F2E@PDC>
In-Reply-To: <9E725728E7D0D311B24D00508B6A0543018D6F2E@PDC>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.4

Quoting steven.noels@the-ecorp.com:

> > -----Original Message-----
> > From: Giacomo Pati [mailto:giacomo@apache.org]
> > Sent: Monday, July 09, 2001 12:01 PM
> > To: cocoon-dev@xml.apache.org
> > Subject: Re: AW: AW: [C2] sitemap editor
> > 
> > 
> > This might be a short term solution. But take into account 
> > what Bruno said: "It
> > might edit every XML file" and thus might start a project of itself.
> 
> I followed the discussion on the new charter of xml.apache.org and
> wasn't
> sure whether no-core xml-based tools would be in the scope of
> xml.apache.org. Even Cocoon has been debated as being no-core, I
> believe.

Yes, Cocoon is only allowed to stay in xml.apache.org until a better home base
is found (hopefully its own).

> 
> > The same is true for the xml-java toolkit.
> 
> What is this toolkit?

In short: Generating java classes out of XSchemas which are able to
serialize/deserialize itself onto/from streams. Further extension will be
adopting WSDL to generate interfaces out of them to create domain firewalls and
possibly Cocoon logicsheets as well.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org