On Wed, Dec 31, 2008 at 1:25 PM, Rahul Akolkar wrote:
> On Wed, Dec 31, 2008 at 8:55 AM, Jukka Zitting
> wrote:
>> Hi,
>>
>> Until we come up with consensus on where (Commons, Xerces or Cocoon)
>> we should place this proposed library, I'd like to start putting some
>> bits together in the Commo
Hi,
On Wed, Dec 31, 2008 at 2:55 PM, Jukka Zitting wrote:
> Until we come up with consensus on where (Commons, Xerces or Cocoon)
> we should place this proposed library, I'd like to start putting some
> bits together in the Commons Sandbox.
I've now set up a project skeleton at
https://svn.apach
Michael Glavassevich wrote:
> Ralph Goers wrote:
> > someone wrote:
> > >
> > > As part of the gradual shutdown of the XML project, the Xerces PMC has
> > > agreed some time ago to take over the responsibility for XML Commons.
> > > The xml-commons group which you mentioned is basically for committ
Jeremias Maerki wrote:
> Frankly, I don't believe Cocoon is the right place. It's too high-level.
> IMO, this should either be Commons or XML Commons.
>
While I don't think that Cocoon is too high level for this, I actually don't
care that much where the code is hosted. As long as I'm able to comm
Frankly, I don't believe Cocoon is the right place. It's too high-level.
IMO, this should either be Commons or XML Commons.
On 02.01.2009 09:11:52 Carsten Ziegeler wrote:
> Jukka Zitting wrote:
> > Hi,
> >
> > On Mon, Dec 29, 2008 at 9:56 AM, Carsten Ziegeler
> > wrote:
> >> In the Cocoon proje
Jukka Zitting wrote:
> Hi,
>
> On Mon, Dec 29, 2008 at 9:56 AM, Carsten Ziegeler
> wrote:
>> In the Cocoon project we're about to refactor/move some of our common
>> xml stuff into an own sub project at Cocoon. This will be a small
>> reusable library. So maybe we could add the common stuff from
On Wed, Dec 31, 2008 at 8:55 AM, Jukka Zitting wrote:
> Hi,
>
> Until we come up with consensus on where (Commons, Xerces or Cocoon)
> we should place this proposed library, I'd like to start putting some
> bits together in the Commons Sandbox.
>
> The Commons web page defines the Sandbox as "a pl
Hi,
Until we come up with consensus on where (Commons, Xerces or Cocoon)
we should place this proposed library, I'd like to start putting some
bits together in the Commons Sandbox.
The Commons web page defines the Sandbox as "a place to try out new
ideas and prepare for inclusion into the Commons
Hi,
On Mon, Dec 29, 2008 at 9:56 AM, Carsten Ziegeler wrote:
> In the Cocoon project we're about to refactor/move some of our common
> xml stuff into an own sub project at Cocoon. This will be a small
> reusable library. So maybe we could add the common stuff from Tika there
> as well. We have a
Ralph Goers wrote on 12/29/2008 02:36:30 PM:
> On Dec 29, 2008, at 9:51 AM, Jeremias Maerki wrote:
>
> > As part of the gradual shutdown of the XML project, the Xerces PMC has
> > agreed some time ago to take over the responsibility for XML Commons.
> > The xml-commons group which you mentioned
On Dec 29, 2008, at 9:51 AM, Jeremias Maerki wrote:
As part of the gradual shutdown of the XML project, the Xerces PMC has
agreed some time ago to take over the responsibility for XML Commons.
The xml-commons group which you mentioned is basically for committers
who only have access to XML comm
As part of the gradual shutdown of the XML project, the Xerces PMC has
agreed some time ago to take over the responsibility for XML Commons.
The xml-commons group which you mentioned is basically for committers
who only have access to XML commons (mainly Norman Walsh when he still
worked on the res
On Dec 29, 2008, at 6:20 AM, Jeremias Maerki wrote:
See:
http://markmail.org/message/i4mzckmqzy2gdwsc
Xerces (responsible for XML Commons) seems open to revive XML
Commons a
bit. I think it would make sense to do Commons SAX or Commons XML in
XML
Commons, not here. I'm planning to invest
See:
http://markmail.org/message/i4mzckmqzy2gdwsc
Xerces (responsible for XML Commons) seems open to revive XML Commons a
bit. I think it would make sense to do Commons SAX or Commons XML in XML
Commons, not here. I'm planning to invest some time in this after New
Year.
On 29.12.2008 12:07:14 Pau
Erm... what about xml-commons ?
http://xml.apache.org/commons/
is this considered dropped?
At least another project that's in the realm of xml-commons is xml-
resolver, or?
Would that migrate in as well? It could but...
paul
Le 29-déc.-08 à 11:06, Jochen Wiedmann a écrit :
On Mon, Dec 29
It may be worth quoting that:
- it's livable to be registered to commons-dev without filter (you
need a swift delete key)
- the filter practice is deep anchored until the netiquette for both
commons-dev and commons-user so that mails without the project prefix
are very quickly warned about a
On Mon, Dec 29, 2008 at 4:56 AM, Henri Yandell wrote:
> I don't see why it's not a good fit for Commons. We've a few xml
> related components in the dormant section. I think a component with
> things for both SAX and DOM would be fine, and letting it grow
> organically would also work well.
Ok,
Jukka Zitting wrote:
> I believe this code would be useful also outside Tika, and I was
> thinking that it might perhaps make sense to create a Commons project
> for this. I also know of some SAX processing classes in Cocoon and
> Jackrabbit that could well be of interest to a wider audience.
>
> D
I don't see why it's not a good fit for Commons. We've a few xml
related components in the dormant section. I think a component with
things for both SAX and DOM would be fine, and letting it grow
organically would also work well.
Hen
On Wed, Dec 17, 2008 at 5:09 AM, Jukka Zitting wrote:
> Hi,
>
Hi,
On Thu, Dec 18, 2008 at 9:25 AM, Jeremias Maerki
wrote:
> Oversight/Responsibility over XML Commons has been transferred to the
> Xerces PMC in November 2006. The XML project itself is subject to be
> killed as soon as the last issues (AxKit & XIndice) have been dealt with.
> Xerces is curre
Oversight/Responsibility over XML Commons has been transferred to the
Xerces PMC in November 2006. The XML project itself is subject to be
killed as soon as the last issues (AxKit & XIndice) have been dealt with.
Xerces is currently just using XML Commons to maintain the XML APIs. Not
much else is
"I looked at XML Commons in xml.apache.org, but it seems pretty dormant."
Perhaps this would be an opportunity to re-vitalize it? I really dislike the
implication that Commons should accept a new project simply because a more
appropriate parent project wasn't paying attention.
--
Martin Cooper
FOP basically does all its XML parsing based on SAX. I don't see too
much overlap right now (without looking more closely). But maybe someone
can see something worth copying/moving in such a Commons SAX. A
colleague of mine had to implement something like a TeeContentHandler a
few weeks ago. So I g
Hi,
In the Apache Tika project [1] we use SAX quite a lot, and have
written a set of quite useful general utility classes for SAX
handling.
For example, in org.apache.tika.sax [2] we have the following:
* ContentHandlerDecorator - Convenient base class for writing
ContentHandler decorators
* Emb
24 matches
Mail list logo
