Glen Mazza wrote:
--- Peter B. West [EMAIL PROTECTED] wrote:
...
That is, I would turn allow the namespace-prefixes
feature to remain in
its default 'false' state, but make sure the parser
is namespace aware.
I don't know that there is any reason for us to
collect prefixes,
This is
At 12:56 PM +1000 3/4/04, Peter B. West wrote:
Fops,
In HEAD, ///apps/FOFileHAndler.java contains the following:
protected static XMLReader createParser() throws FOPException {
try {
SAXParserFactory factory = SAXParserFactory.newInstance();
Christian Geisert wrote:
J.Pietschmann wrote:
[..]
Should we wait for the Apache XML reorganization to
complete or should we rush ahead and create out own
Wiki already?
+1 for the new wiki
It has a nicer look, supports XML export and we can have 'commit
messages' to fop-cvs
Others opinions?
On Mar 4, 2004, at 9:01 AM, Christian Geisert wrote:
Christian Geisert wrote:
J.Pietschmann wrote:
[..]
Should we wait for the Apache XML reorganization to
complete or should we rush ahead and create out own
Wiki already?
+1 for the new wiki
It has a nicer look, supports XML export and we can have
On Mar 4, 2004, at 9:20 AM, Clay Leeds wrote:
[2]
http://wiki.apache.org/general
BTW, I might add, that we're not the first... It seems[1] that
Xindice[2] also has a MoinMoinWiki...
[1]
http://wiki.apache.org/xindice
[2]
http://xml.apache.org/xindice
-Original Message-
From: Clay Leeds [mailto:[EMAIL PROTECTED]
snip /
Sounds good to me... Looks 'snappier'! (sorry! ;-) and the added
capabilities[1] look promising. There're a couple of other Wiki's I'm
I also had a look, and apparently, the bottom-part (below 5. Contact...) of
the
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Thanks, Manuel. We have about 430 people on FOP-DEV,
snip /
--- Manuel Mall [EMAIL PROTECTED] wrote:
The e-mail to fop-dev below which I received last
night contained the Beagle
virus and according to the SMTP
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
snip /
PleaseI'm not implying intent here, or email owner
capabilities.
Of course not. Sorry, was just a bit annoyed with the logic in the OP.
Cheers,
Andreas
--- Elliotte Rusty Harold [EMAIL PROTECTED]
wrote:
What I ask on reading this code is why you're using
SAXParserFactory
at all? SAXParserFactory is a Sun class they
invented to fill a hole
in SAX 1.0. It's unnecessary in SAX 2.0. SAX2 apps
should use
XMLReaderFactory instead, which has
Peter B. West wrote:
What's the intention for fop.xconf?
It's been there for ages with the intent to provide for
configurable, easily changed defaults. Unfortunately
1. There's not much more than PDF filters (in the maintenance
branch), and if all filters are deleted, the code uses a
flate
At 2:36 PM -0800 3/4/04, Glen Mazza wrote:
--- Elliotte Rusty Harold [EMAIL PROTECTED]
wrote:
What I ask on reading this code is why you're using
SAXParserFactory
at all? SAXParserFactory is a Sun class they
invented to fill a hole
in SAX 1.0. It's unnecessary in SAX 2.0. SAX2 apps
should
Andreas L. Delmelle wrote:
a) The Apache list server has no virus scanner?
The Apache list server has a virus scanner. It just happend
that there were apparently at least three and more than 7
new variants of Bagle, MyDoom and NetSky released yesterday
within a few hours.
Also, the worms seem to
Christian Geisert wrote:
Christian Geisert wrote:
J.Pietschmann wrote:
[..]
Should we wait for the Apache XML reorganization to
complete or should we rush ahead and create out own
Wiki already?
+1 for the new wiki
It has a nicer look, supports XML export and we can have 'commit
messages' to
Elliotte Rusty Harold wrote:
At 12:56 PM +1000 3/4/04, Peter B. West wrote:
...
SAXParserFactory factory = SAXParserFactory.newInstance();
factory.setNamespaceAware(true);
return factory.newSAXParser().getXMLReader();
...
What I ask on reading this code is why
At 10:43 AM +1000 3/5/04, Peter B. West wrote:
I think this might be because the HEAD developers were moving to a
JAXP implementation, and SAXParserFactory is still in the 1.4
javax.xml.parsers package, which, AIUI, is what one is supposed to
use for JAXP-compatible applications. I don't know
On Mar 4, 2004, at 6:53 PM, Elliotte Rusty Harold wrote:
At 10:43 AM +1000 3/5/04, Peter B. West wrote:
I think this might be because the HEAD developers were moving to a
JAXP implementation, and SAXParserFactory is still in the 1.4
javax.xml.parsers package, which, AIUI, is what one is
On Mar 4, 2004, at 6:53 PM, Elliotte Rusty Harold wrote:
At 10:43 AM +1000 3/5/04, Peter B. West wrote:
I think this might be because the HEAD developers were moving to a
JAXP implementation, and SAXParserFactory is still in the 1.4
javax.xml.parsers package, which, AIUI, is what one is
17 matches
Mail list logo
