cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <tcu...@dff.st>
Subject RE: XObject
Date Thu, 30 Nov 2000 22:13:58 GMT
> > > On Thu, Nov 30, 2000 at 11:12:55AM +0000, Jeremy Quinn wrote:
> > > > At 13:45 -0500 29/11/00, Donald Ball wrote:
> > > > So either we officially add the org.apache.cocoon.framework 
> heirarchy to
> > > > Cocoon 2, or we define a new common location for both C1 and C2 and
> > > > depreciate org.apache.cocoon.framework.XObject.
> > >
> > > I'd rather not add a new directory just for XObject. Would it
> > > not make sense for it to be in either the 'xml' or 'util'
> > > packages? Since C1 doesn't have the 'xml' package, I guess
> > > there is sane, given the functionality the XObject provides.
> > > Thoughts?
> >
> > I'm for deprecating C1 XObject, then creating a new XObject
> > org.apache.cocoon.xml.XObject with the new SAX2 methods and putting it
> > in C1 and C2.  Might upset some C1 users however...
> 
> the whole _point_ of the XObject class was to provide a bridge between C1
> and C2, right? doesn't it make sense to keep it in the same location
> between projects, even if it doesn't make sense in the C2 directory
> structure.
> 
> not that i care, i never wrote an XObject class, but still.

That's exactly the point... 
I didn't use the XObject interface with cocoon1 myself and I don't
think a lot of people do so - but what about asking in the cocoon-user
list who is concerned about this changes?

What about the different Handlers? How can this be solved?
--
Torsten

Mime
View raw message