Yes, Michael, I was the driving force behind that. I wanted to make sure
that we've made an informed decision before dropping support for one JDK
or another. Developers obviously like the new stuff but users are
sometimes stuck with old stuff. It often takes them a bit longer to
migrate although th
Shane Curcuru <[EMAIL PROTECTED]> wrote on 11/11/2008 08:08:50 AM:
> +1 to dropping 1.2 support.
>
> Please - be sure that the main website clearly lists the last release we
> think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and
> is used directly or within other products virtua
Any idea how this poll was done? A form you could submit on a website?
Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
had something to do with it. Was this poll easy to set up?
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTE
Worth nothing that although Java 1.4 may have passed Sun's EOL date there
are other JDK vendors who may have end of service dates that are still in
the future. So it may be that a user who is still stuck on that JDK level
is still getting support and bug fixes that they wouldn't be getting
anymore
Xerces doesn't have maintenance releases in the sense that we'll ever have
a 2.[x].y release after a 2.[x+1].0. The codebase is constantly moving
forward with new development. It just happens that over some periods of
time the only changes were bug fixes and minor improvements and if we have
a rel
I doubt maintenance for the current codebase running on Java 1.3 would
be completely removed. I interpreted the original question as aimed at
new and future development. I don't want to speak for Michael, but
that's the way I read it.
-Nathan
On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <[EMAIL P
Not sure what's going on, but a few other things worth pointing out...
1) s for the same target namespace get mashed into the same
Grammar object.
2) s are attached to the grammars which imported them. The
XSGrammarBucket used by the validator will dig them out.
3) The Schema object holds on to
Hi Ajay,
The NullPointerException could have come from any number of places. It
would help if you posted a stack trace.
Also, though it doesn't appear it was even called your LSResourceResolver
is making assumptions about the format of the systemId which aren't
generally true. It's a URI (e.g.
Hi Anderson,
Xerces doesn't implement XPathFactory. Xalan does.
It would be better to ask questions about Xalan on the
[EMAIL PROTECTED] mailing list instead of the Xerces-J list.
Also, keep in mind that you're using Sun's fork of Xalan. The developers in
Apache have no idea what modifications h
Hi,
I was trying to implement LSResourceResolver to load multiple Schemas in my
SchemaFactory but I am getting nullpointer Exception. Below is the code. Please
tell me what I am missing here ?
Thanks
Ajay B.
import java.io.*;
import java.util.*;
import org.w3c.dom.* ;
import org.w3c.dom.ls.* ;
As far as I can see Apache XPath does not implement idref() - see here
-
http://xml.apache.org/xalan-j/apidocs/org/apache/xpath/functions/Functio
nOneArg.html
That may be because idref() is not in the XPath 1.0 Specification - see
here - http://www.w3.org/TR/xpath#section-Node-Set-Functions
Hi all,
my name is Anderson Guiera and i'm have a problem with idref function.
I use this function in the folow code:
XPath xpath = XPathFactory.newInstance().newXPath();
String expression = "idref('pessoaGA.1')";
NodeList nosEnderecos = (NodeList) xpath.evaluate(expression,
this.xmlDocument, XPa
Okay I have placed some breakpoints in SoftReferenceGrammarPool, for the simple
example of A and B it seems to work very well, thanks :-)
Now with more complicated schemas that include multiple schemas that include
even more schemas, I am not sure whether they are being cached in the pool
co
On Tue, 11 Nov 2008 09:36:26 -0500
"David Ezell" <[EMAIL PROTECTED]> wrote:
Well, one person's 4 is another person's 3.
We're stuck on 1.3 for the foreseeable future.
So -1 to drop 1.3.
I partially agree with this. There's no reason 1.3 needs to be dropped for
the current 2.x.x codebase.
Before Advancing beyond 1.3 I'd suggest to maybe initiate a usage poll
analogous to http://wiki.apache.org/xmlgraphics/UserPollOct2007 to get
an overview which JDK version is still in use and required by Xerces-J
users.
That would give the community a foundation to base a good decision upon.
Well, one person's 4 is another person's 3.
We're stuck on 1.3 for the foreseeable future.
So -1 to drop 1.3.
David Ezell
VeriFone
Chair, XML Schema WG
> -Original Message-
> From: Schmidlin, Franck [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 11, 2008 5:35 AM
> To: [EMAIL PROTE
Hi Adam,
If you want to debug it I would suggest putting breakpoints inside of
SoftReferenceGrammarPool [1]. Technically this grammar pool could dump some
of the grammars from the cache later (and then reload them if needed) but
only if the JVM is starving for memory.
Thanks.
[1]
http://svn.apa
> a new infusion of activity and interest.
you betcha, most of us would be up in arms!
I personally am stuck on 1.4.2 for the foreseeable future.
So +1 to drop 1.2/3 support, but let's not get too drastic please.
__
Franck Schmidlin
Corporate Integration Consultant
Hi,
I could not figure out how to implement LSResourceResolver with SchemaFactory
so that all external entities could be loaded when main schema gets loaded.
Any code sample will be greatly appriciated .
Thanks
--- On Mon, 11/10/08, ajay bhadauria <[EMAIL PROTECTED]> wrote:
> From: ajay bha
A…
Great :-) This seems to work initially.
Is there a way I can interrogate the GrammarPool or schema loader in this
approach so that I can confirm that grammars are being loaded once and then
re-loaded from the Cache?
Thanks Adam.
From: Michael
Hi Adam,
Try using the SchemaFactory.newSchema() method. The one which takes no
arguments. It caches based on schema location. That's the one I meant.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
"Adam Retter" <[EMAIL PR
Michael again thanks for the prompt reply ☺
I have attempted to use SAXParserFactory, set up the Schemas and then use the
XMLReader, unfortunately I get exactly the same problems as with the
XMLGrammarPool approach. I guess internally both of these approaches are
looking for a documents Schema
22 matches
Mail list logo
