You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Pierpaolo Fumagalli <pi...@apache.org> on 2000/02/07 16:50:04 UTC
Cocoon 2.0?
Hi all...
It has been a very long week-end, at least for me, but at the ends the
results were (IMVHO) quite good.
I spent the last three days working on the Cocoon 2.0 idea, and I came
up with a bunch of classes that can be defined "a first very rough
implementation" of Cocoon 2.0.
Now, blame me. The architecture sucks, the object names sucks,
everything sucks, but at least the sitemap is working (or at least it
seems to be working).
To avoid any collision, I created a new branch on the CVS called
"xml-cocoon2-alpha0".
Right now it works (barely!). It creates all factories necessary for
obtaining instances of Producers, Filters and Serializers. The Sitemap
is instantiated, and works. Requests through the servlet interface are
(more or less!) handled by the sitemap, and, for a three days work (but
almost 20 hours/day) is more than enough.
I'll be actively working on this new branch all next week, thanks to
Exoffice wich lets me do that also on office hours, until I don't reach
a "decent" version of the code.
Still need to be done, before the code can be placed in "open
development" (or shredded, depending on how you evaluate it!) are all
the link translation stuff, and Sitemap exception handling (for
redirections and so on).
Also, as soon as Xerces makes it available, I'm planning to integrate
full SAX2 in it, but I can't do it without some way of testing.
Flames are accepted both on the M/L or privately :)
Take care...
Pier
--
--------------------------------------------------------------------
- P I E R -
stable structure erected over water to allow the docking of seacraft
<ma...@betaversion.org> <http://www.betaversion.org/~pier/>
--------------------------------------------------------------------
- ApacheCON Y2K: Come to the official Apache developers conference -
-------------------- <http://www.apachecon.com> --------------------
Re: Cocoon 2.0?
Posted by Brett McLaughlin <br...@earthlink.net>.
Pierpaolo Fumagalli wrote:
>
> Brett McLaughlin wrote:
> >
> > Why don't you quickly write a wrapper that uses the SAX 2.0
> > ParserAdapater? That makes a SAX 1.0 (or 2.0 alpha, for that matter)
> > parser give you all the callbacks (including namespace support) that SAX
> > 2.0 does. Wouldn't that be a work around?
>
> Nahhh... Too much work... There are more important things to do than
> that at this point... I don't care about the transport, as long as it's
> event driven (and seeing from the number of
> Producers/Filters/Serializers I have..)
>
> > I know Andy Clark is working now on getting SAX 2.0 in, but until then....
>
> Yep... I just hope he comes out w/ something soon...
Shouldn't be long. I know David Brownell (on XML-dev) managed to get
his parsers converted last week (roughly 1 week after SAX 2.0 went
beta). The only concern I have is that in talking with Andy, he said he
was going to have teh same class (org.apache.xerces.parsers.SAXParser)
implement both the SAX 1.0 Parser interface and the SAX 2.0 XMLReader
interface. This, IMHO, is bad and going to be very troublesome, and
will probably add time to get things going. SAX 2.0 is (admittedly) not
backwards compatible, so I'm not sure why the effort to keep one
class...
>
> > I have been using the ParserAdapater class and it works very well.
>
> The thing is that I could care less of the Parser... It's all the
> transport mechanism between components that is event driven... :)
right, it just makes it easy to see what kind of response you get in
those callbacks. Let me know if you need any specific information about
what you would get on a callback. I can always run something through my
setup at home (which wraps Xerces into a SAX 2.0 parser) and let you
know exactly what you will be getting as input.
-Brett
>
> Pier
>
> --
> --------------------------------------------------------------------
> - P I E R -
> stable structure erected over water to allow the docking of seacraft
> <ma...@betaversion.org> <http://www.betaversion.org/~pier/>
> --------------------------------------------------------------------
> - ApacheCON Y2K: Come to the official Apache developers conference -
> -------------------- <http://www.apachecon.com> --------------------
Re: Cocoon 2.0?
Posted by Pierpaolo Fumagalli <pi...@apache.org>.
Brett McLaughlin wrote:
>
> Why don't you quickly write a wrapper that uses the SAX 2.0
> ParserAdapater? That makes a SAX 1.0 (or 2.0 alpha, for that matter)
> parser give you all the callbacks (including namespace support) that SAX
> 2.0 does. Wouldn't that be a work around?
Nahhh... Too much work... There are more important things to do than
that at this point... I don't care about the transport, as long as it's
event driven (and seeing from the number of
Producers/Filters/Serializers I have..)
> I know Andy Clark is working now on getting SAX 2.0 in, but until then....
Yep... I just hope he comes out w/ something soon...
> I have been using the ParserAdapater class and it works very well.
The thing is that I could care less of the Parser... It's all the
transport mechanism between components that is event driven... :)
Pier
--
--------------------------------------------------------------------
- P I E R -
stable structure erected over water to allow the docking of seacraft
<ma...@betaversion.org> <http://www.betaversion.org/~pier/>
--------------------------------------------------------------------
- ApacheCON Y2K: Come to the official Apache developers conference -
-------------------- <http://www.apachecon.com> --------------------
Re: Cocoon 2.0?
Posted by Brett McLaughlin <br...@earthlink.net>.
Pierpaolo Fumagalli wrote:
>
> Hi all...
> It has been a very long week-end, at least for me, but at the ends the
> results were (IMVHO) quite good.
>
<snip />
>
> Also, as soon as Xerces makes it available, I'm planning to integrate
> full SAX2 in it, but I can't do it without some way of testing.
Why don't you quickly write a wrapper that uses the SAX 2.0
ParserAdapater? That makes a SAX 1.0 (or 2.0 alpha, for that matter)
parser give you all the callbacks (including namespace support) that SAX
2.0 does. Wouldn't that be a work around? I know Andy Clark is working
now on getting SAX 2.0 in, but until then.... I have been using the
ParserAdapater class and it works very well.
-Brett
>
> Flames are accepted both on the M/L or privately :)
>
> Take care...
>
> Pier
>
> --
> --------------------------------------------------------------------
> - P I E R -
> stable structure erected over water to allow the docking of seacraft
> <ma...@betaversion.org> <http://www.betaversion.org/~pier/>
> --------------------------------------------------------------------
> - ApacheCON Y2K: Come to the official Apache developers conference -
> -------------------- <http://www.apachecon.com> --------------------