Use CDATA instead of PCDATA elements,
but check the other consequences ...
Your elements will be used as-is,
without -any- changes.
While PCDATA stands for
-parsed- character data.
Check out the differences...
BTW: xerces-dev is deprecated;
use xerces-j-dev for the java version
use xerces-c-dev fo
Hello,
First I would suggest U to set Ur class path according to either JAXP or
xerses. though both contain the same files. set it to include the jaxp.jar file
in the jaxp directory. Then U have to use the APIs in the file jaxp.jar. But in
case U only need the desired content to be printed, then
ÿþ< ! D O C T Y P E H T M L P U B L I C " - / / W 3 C / / D T D H T M L 4 . 0 T r a n s i t i o n a l / / E N " >
< H T M L > < H E A D >
< M E T A c o n t e n t = " t e x t / h t m l ; c h a r s e t = u n i c o d e " h t t p - e q u i v = C o n t e n t - T y p e >
< M
Hi.
Can you please tell me what method are you trying to invoke in that class
(ImplementationMessages) ? Also, let me know which is that program in the
book ?
Regards,
Sujay.
> --
> From: [EMAIL PROTECTED]:[EMAIL PROTECTED]
> Reply To: [EMAIL PROTECTED]
> Sent: Frida
i am not an expert of xml but i own the xml notepad of microsoft wich works
fairly well.
In the edit menu you choose save and it's done
here we go
christophe
Jeroen Wolf a écrit :
> Hi all,
>
> I have a question about how to save an XML document to disk.
> I am using Visual C++ 6.0 as the compile
Don Brutzman wrote:
>
> our new strategy:
> develop a schema to replace DTD, then use XSLT to autogenerate
> - IDL for spec
> - corresponding Java interfaces & methods for all elements & attributes
> - stub Java classes implementing those interfaces, suitable for a sample
> implementation
> - do
Arnaud Le Hors wrote:
> [...]
> > I'd try to
> > convince them to stop using IDL to specify DOM and use
> > UML instead.
>
> You're welcome to try on www-dom. I don't remember anybody ever trying
> (and I've been on the DOM WG from its beginning).
good ideas to consider, thanks
> > (The lack of
> -Original Message-
> From: Arnaud Le Hors [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 18, 2000 2:25 PM
> To: general@xml.apache.org
> Cc: [EMAIL PROTECTED]; xerces-j-dev@xml.apache.org
> Subject: Re: Question about document type nodes and JAXP
>
Eric Hodges wrote:
>
> I'm not convinced that a language neutral spec is that important. What does
> it give us? I'd rather use an API tailored to the language I'm in, I think.
But that was one of the requirements the DOM WG had to work with. People
want to implement and use the DOM in many dif
Sean Kelly wrote:
>
> Ah, so the DOM is specified in IDL, as in OMG's IDL?
Yes.
> I didn't know that.
I'm always amazed to find out how so few people ever read the specs.
Which doesn't stop some from forming opinions and be vocal about it...
(that's not intended to you in particular btw!)
I sug
> -Original Message-
> From: Sean Kelly [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 18, 2000 1:53 PM
> To: general@xml.apache.org
> Cc: [EMAIL PROTECTED]; xerces-j-dev@xml.apache.org
> Subject: Re: Question about document type nodes and JAXP
>
>
&g
> They are but not at the IDL level. It has to be done at the language
> binding level. BTW we've been told it's a known pb with IDL!...
Ah, so the DOM is specified in IDL, as in OMG's IDL? I
didn't know that.
> > > I wish JAXP addressed this problem but it doesn't either. :-(
> >
> > Thanks a
Eric Hodges wrote:
>
> You can't specify a factory in IDL?
You can, but it would be yet another interface which wouldn't solve the
bootstrapping issue. As I said in my previous message we've been told
it's a know pb with IDL!...
> I don't know much about IDL, so I'm
> curious why you can't. See
Sean Kelly wrote:
>
> Blech. Are static methods allowed in the DOM specification (and are
> they language independent)?
They are but not at the IDL level. It has to be done at the language
binding level. BTW we've been told it's a known pb with IDL!...
> I'd love to see a singleton or static
>
> -Original Message-
> From: Arnaud Le Hors [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 18, 2000 12:25 PM
> To: general@xml.apache.org
> Cc: [EMAIL PROTECTED]; xerces-j-dev@xml.apache.org
> Subject: Re: Question about document type nodes and JAXP
>
>
>
> Because there doesn't seem to be any way to specify a bootstrap
> mechanism which is platform and language independent the DOM spec
> doesn't define any. :-(
> I've made a proposal to fix this at least for Java in DOM Level 3. In
> the meantime, you have to use some "proprietary" call.
Blech. A
@xml.apache.org
> Subject: Re: Question about document type nodes and JAXP
>
>
> > OK, how do I get the first instance of DOMImplementation so I can create
> the
> > DocumentType before I create the Document? I can only find a
> way to get a
> > DOMImplementa
Because there doesn't seem to be any way to specify a bootstrap
mechanism which is platform and language independent the DOM spec
doesn't define any. :-(
I've made a proposal to fix this at least for Java in DOM Level 3. In
the meantime, you have to use some "proprietary" call.
Sean Kelly wrote:
>
> OK, how do I get the first instance of DOMImplementation so I can create
the
> DocumentType before I create the Document? I can only find a way to get a
> DOMImplementation if I already have a Document.
Document toss = new org.apache.xerces.dom.DocumentImpl();
DOMImplementation impl = toss.getI
t: Monday, October 16, 2000 8:51 PM
> To: [EMAIL PROTECTED]
> Cc: general@xml.apache.org; xerces-j-dev@xml.apache.org
> Subject: Re: Question about document type nodes and JAXP
>
>
> In DOM Level 2, you first need to create the doctype node with
> DOMImplementation.createDocu
- Original Message -
From: "Arnaud Le Hors" <[EMAIL PROTECTED]>
To:
Cc: ; <[EMAIL PROTECTED]>
Sent: Tuesday, October 17, 2000 11:14 AM
Subject: Re: Question about document type nodes and JAXP
> Eric Hodges wrote:
> >
> > > In DOM Level 2, you fi
Eric Hodges wrote:
>
> > In DOM Level 2, you first need to create the doctype node with
> > DOMImplementation.createDocumentType() and then create the document node
> > with DOMImplementation.createDocument() to which you pass the doctype.
> > You can't change the doctype afterwards.
>
> Wow, tha
- Original Message -
From: "Arnaud Le Hors" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: ;
Sent: Monday, October 16, 2000 8:51 PM
Subject: Re: Question about document type nodes and JAXP
> In DOM Level 2, you first need to cre
In DOM Level 2, you first need to create the doctype node with
DOMImplementation.createDocumentType() and then create the document node
with DOMImplementation.createDocument() to which you pass the doctype.
You can't change the doctype afterwards.
--
Arnaud Le Hors - IBM Cupertino, XML Technology
Eric Hodges wrote:
>
> I'm still trying to add a DocumentType from to a Document.
I just worked around this using JAXP by creating a dummy document
of the right type and then reading it in.
This restriction is probably a limitation because:
http://www.w3.org/TR/2000/PR-DOM-Level-2-Core-292
I'm still trying to add a DocumentType from to a Document. I'm using
DocumentImpl.createDocumentType(name, publicId, systemId) to create the new
DocumentType. When I call Document.importNode(docType, true) I get a run
time error (NullPointerException) because DocumentImpl asks the DocumentType
fo
0 4:04 PM
> To: general@xml.apache.org
> Cc: xerces-j-dev@xml.apache.org; [EMAIL PROTECTED]
> Subject: RE: Question about document type nodes and JAXP
>
>
> Unfortunately that's a xerces specific method. Like I said, we're using
> Xerces through JAXP, so we want
56 PM
> To: general@xml.apache.org; [EMAIL PROTECTED]
> Cc: xerces-j-dev@xml.apache.org; [EMAIL PROTECTED]
> Subject: Re: Question about document type nodes and JAXP
>
>
> HI Eric!
> I think the Api "cloneNode" which is in
> org.apache.xerces.dom.DocumentImpl sho
HI Eric!
I think the Api "cloneNode" which is in
org.apache.xerces.dom.DocumentImpl should help you out. Please check the
documentation to make sure of it. I used long time back and i remember i didn't
had any problems.
Thanks
Venkat Ramana
Eric Hodges wrote:
> I need to duplicate XML doc
The xml4c 3.1.0 binaries are build on solaris 2.6 with CC 4.2.
That package does not have CC5.0 support. Best thing would be to take
the source from cvs repository (in xml.apache.org) and recompile it.
What's the error you get on parse(xmlFile)? You also need to check if
you have the file resides i
Download the latest 1.0.3 version and you should see the package.
Boris Garbuzov wrote:
> Where this package is? I am finding just following:
>
Where this package is? I am finding just following:
org.apache.xerces.dom
org.apache.xerces.dom.traversal
org.apache.xerces.domx.events
org.apache.xerces.domx.traversal
org.apache.xerces.framework
org.apache.xerces.parsers
org.w3c.dom
org.xml.sax
org.xml.sax.helpers
---
Take a look at org.apache.xml.serialize package.
Boris Garbuzov wrote:
> What people use to print DOM document in Xerces for Java? It is left
> outside the core? Why not put to the core any default writer class
> like DOMWriter from the samples? Can I use DOMWriter for commercial
> needs, a littl
Joakim wrote:
>
> Will xerces provide method for appending other Node implementation
> beside NodeImpl?
>
> Now when i try to appendChild of another Node implementation the
> following error is raised "WRONG_DOCUMENT_ERR".
> Why not make a conversion to xerces Node type instead of casting that
>
Try the following:
newNode = docOne.importNode( docTwo.getFirstChild() )
___
Linda Derezinski
Interface & Control Systems
-Original Message-
From: Joakim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 22, 2000 2:
The exception that you are getting is because you are trying to append a
node that belongs to another document.
To import a node from one document to another (whether it is a node, and
element, or whatever) you must first use the DOM Document method
'importNode'
DOM_Document doc1( getMyMagicalDoc
I'm not sure I completely understand what you want. If you just want to
include bits of markup declarations in another DTD, you just can just
external entities. But that has nothing to do with namespaces. Namespaces
in general don't have anything to do with DTDs, and DTDs don't understand
anythi
The serializer gets the attributes from the document (DOM) or events
(SAX), do by definition these attributes exist. They may have any value,
and an empty string is a value.
Since the attribute was obtained from the DOM, you want it to appear in
the document and be brought back to the DOM when the
Pierpaolo Fumagalli wrote:
> Don't lie :) You forgot to update it yesterday :)
> CVS logs tell me that you uploaded the deprecated version 4 hours ago,
> so, the one I downloaded yesterday WAS NOT deprecated :) :)
At the time I made the statement, I though that it
was updated. But then I checked a
Andy Clark wrote:
>
> Pierpaolo Fumagalli wrote:
> > I've seen in the original SAX2 file I got that DocumentHandler has
> > been deprecated, while the one coming with Xerces, in CVS, right now
> > is not?
>
> Actually, the DocumentHandler in Xerces is also deprecated.
> The SAX2beta people deprec
Pierpaolo Fumagalli wrote:
> I've seen in the original SAX2 file I got that DocumentHandler has
> been deprecated, while the one coming with Xerces, in CVS, right now
> is not?
Actually, the DocumentHandler in Xerces is also deprecated.
The SAX2beta people deprecated a lot of the original SAX
stu
Pierpaolo Fumagalli wrote:
>
> Another thing.. Why the setLexicalHandler() in SAXParser is protected?
Sorry... Next time I'll look @ the API documentation (setProperty!)
Pier
--
- P I
Pierpaolo Fumagalli wrote:
>
> I've seen in the original SAX2 file I got that DocumentHandler has
> been deprecated, while the one coming with Xerces, in CVS, right now
> is not?
> Is this a willing thing or just a forgotten thing?
Another thing.. Why the setLexicalHandler() in SAXParser is prote
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
> om> cc: (bcc: Scott Boag/CAM/Lotus)
> Subject: Re: question about
> Parser Liaison and Documents
> 01/31
D]To: [EMAIL PROTECTED]
om> cc: (bcc: Scott Boag/CAM/Lotus)
Subject: Re: question about Pa
Can someone please comment on this. I posted this last Thursday,
and no one has made any comments.
Thanks,
Paul
Paul Levin wrote:
I realize that the Document implementation class
used, and the ParserLiaison class used, are tightly coupled.
I notice, in the latest Xalan distribution, that
: "Ben Bertola" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 17, 2000 2:24 PM
Subject: Re: Question...
> I've been on this list for a couple of weeks now just kind of trying to
get a feel
> for everything and would also be interested in helpin
- Original Message -
From: "Nicholas Oddson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 17, 2000 11:17 AM
Subject: Question...
> Apologies for posting this to the group, but I'm fairly new to this and
> couldn't find any information on the website or in the FAQs/IN
I've been on this list for a couple of weeks now just kind of trying to get a
feel
for everything and would also be interested in helping out where possible. I
have
to admit that I'm not too advanced in XML right now, but am using it quite a
bit in
some projects I have right now. One thing tha
There are a bunch of people working on Xerces-J and C right now. Most
of them are focusing on:
solidifying the core (e.g. namespaces)
completing DOM Level 2 (e.g ranges)
XML Schema (e.g. updating to the latest draft spec)
bugs (plenty of these to go around)
"Oberpriller, Wade D." wrote:
>
> Hello,
>
> I was just wondering if there is support for taking a DOM_Document object
> and converting it to the equivalent XML string? The Perl DOM module simply
> allows one to create a DOM_Document and call something as simple as
> doc->toString(). This metho
Oops. Sorry our packaging scripts are still not quite there yet.
We have just refreshed the win32 binary archive. Hopefully, we got
the packaging right this time.
rahul
This is a legal thing. Once W3C publishes their own files (the ones in
org.w3c.dom have the W3C copyright), then we can copy them over the
ones that we have now. I hope that won't be long, now that DOM L2 has
gone CR.
Ted
- Original Message -
From: Christopher Taylor <[EMAIL PROTECTED]>
53 matches
Mail list logo
