You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by di...@multitask.com.au on 2002/06/19 01:48:40 UTC
More documentation tools
And now for another tool producing documentation @ Apache...
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
----- Forwarded by dIon Gillard/Multitask Consulting/AU on 06/20/02 05:24
AM -----
Andy Clark
<andyc@apache. To: general@xml.apache.org
org> cc: xerces-j-user@xml.apache.org, xerces-j-dev@xml.apache.org
Subject: [Announce] CyberNeko Tools for XNI 2002.06.18 Available
06/18/02 10:15
PM
Please respond
to general
When I made the announcement a few days ago about the
first version of the CyberNeko Tools for XNI, I was
busy working on another tool. At the time, it wasn't
quite ready for release so I pushed out the first
collection of tools without it. But now it's ready! :)
I am pleased to announce the 2002.06.18 release of
NekoXNI! This release adds a new tool to the lineup:
the CyberNeko Style Processor, version 0.1.
NekoStyle is an XML batch processing framework that
is similar to the StyleBook tool we've been using for
several years to generate documentation of XML projects
here at Apache.
Why have I chosen to create yet another XML batch
processing framework? Because I wasn't happy with the
other ones. Because I like doing things *my* way.
Because I could. Because we just don't have enough of
them. ;) Because of a million reasons... Take your pick.
But before you decide whether it was worthwhile to
write in the first place, check out the web page[1],
download the code[2], and try it out for yourself.
You may find that you like it! Or not. Either way,
it works extremely well for what I need to do. :)
NekoStyle offers the following features:
* simple, flexible, and extensible framework for
automating XML processing
* JAXP/TrAX compliant
* parses HTML documents (using NekoHTML) as well
as XML documents
* dynamic pipelines
* an Ant task for executing within build scripts
* small size (the Jar is only 25K!)
and perhaps the most important is:
* DOCUMENTATION! :)
One of the primary reasons I delayed the initial
release was so that I could write more documentation
about how it works. I hate writing docs as much as
the next person but I knew it was important for
people to understand the framework.
In fact, the HTML documentation included with NekoStyle
is actually generated *by* the NekoStyle processor at
build time. So this is a good way to learn how the
system works in practice.
<aside>
Most of the content is written in DocBook and then
transformed to the HTML output. However, there are
some files that are written using custom DTDs so that
they can keep the semantic meaning behind the data.
These files (e.g. the change log) are first converted
to DocBook and then to HTML.
(This is one of my first attempts at using DocBook so
you'll have to excuse me if I used it incorrectly in
certain places. That grammar is HUGE! ;)
</aside>
The real reason that I wrote NekoStyle was that I
needed specific features for other things that I'm
working on. So that's what I designed it for. There
are a few limitations and things I want to improve
but I think it's a nice little system for performing
XML processing. And I already have plans for features
to add in subsequent versions.
The most important feature I want to add is a
template processor that people can use to write the
output HTML. This would allow them to change the
design of the output without needing to edit XSLT
stylesheets. *And*, using NekoHTML, these templates
can be written in standard, "dirty" HTML much like
the templating functionality in other systems (e.g.
PostNuke, etc). This would alleviate a lot of the
trouble in maintaining documentation and adapting
the old docs to fit new requirements.
Anyway, if you need a small library to automate
batch XML processing, then NekoStyle may be what you
need. So check it out and let me know what you think.
You can also download all of the NekoXNI tools in a
single package[3] if you don't already have NekoHTML
or NekoDTD.
Enjoy!
[1] http://www.apache.org/~andyc/neko/doc/style/
[2] http://www.apache.org/~andyc/neko/nekostyle-0.1.zip
http://www.apache.org/~andyc/neko/nekostyle-0.1.tar.gz
[3] http://www.apache.org/~andyc/neko/nekoxni-2002.06.18.zip
http://www.apache.org/~andyc/neko/nekoxni-2002.06.18.tar.gz
--
Andy Clark * andyc@apache.org
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Servlet 2.4 & JSP 2.0
Posted by Steven Noels <st...@outerthought.org>.
Danny Angus wrote:
> Hi,
>
> Just out of curiosity, how come Apache didn't vote in
>
> the jsp 2.0 Community Review Draft
> http://jcp.org/jsr/results/152-7-1.jsp
> and the Java Servlet 2.4 Community Review Draft
> http://jcp.org/jsr/results/154-7-1.jsp
It's only an assumption, but wouldn't this be because Sun hasn't yet met
the terms of its LOI so publicly declared during JavaOne?
http://jakarta.apache.org/site/jspa-agreement.html
You have to read the comments coming with the votes in this perspective:
On 14-Jun-2002, IBM voted YES with the following comment:
IBM's vote is based on the technical merits of this JSR and is not a
vote on the licensing terms. IBM supports licensing models that create
an open and level playing field by allowing third parties to create
independent implementations of Java Specifications and that do not allow
individuals or companies to exercise unneccessary control for
proprietary advantage. We support open source as a licensing model for
contributions in the JCP, and would hope others will support this direction.
Basically, IBM has been almost the only company actually caring about
this situation and has been posting similar comments for the past
months. (No, I don't work for IBM ;-)
What surprises me is that Caldera has never been supporting this
situation. Oh well, I never understood why they are part of the JCP
anyhow ;-)
Open Source & Sun??? Naaah....
</Steven>
ps: these are assumptions of course, I guess it's up to Jason to inform
us on the real story.
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
stevenn@outerthought.org stevenn@apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Servlet 2.4 & JSP 2.0
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 6/19/02 6:07 AM, "Danny Angus" <da...@apache.org> wrote:
> Hi,
>
> Just out of curiosity, how come Apache didn't vote in
>
> the jsp 2.0 Community Review Draft
> http://jcp.org/jsr/results/152-7-1.jsp
> and the Java Servlet 2.4 Community Review Draft
> http://jcp.org/jsr/results/154-7-1.jsp
I think that we are still trying to figure out what to vote. ;-)
Personally, I think the servlet api has turned into a big mess because web
application specific features and EJB stuff don't belong in this API (they
should go into a web app api). Of course my opinion on that is ignored
because the big players like BEA and IBM get whatever they want.
Bah. I'm tired of fighting these battles....
-jon
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Servlet 2.4 & JSP 2.0
Posted by Danny Angus <da...@apache.org>.
Hi,
Just out of curiosity, how come Apache didn't vote in
the jsp 2.0 Community Review Draft
http://jcp.org/jsr/results/152-7-1.jsp
and the Java Servlet 2.4 Community Review Draft
http://jcp.org/jsr/results/154-7-1.jsp
d.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>