RE: Xerces problem

2007-03-22 Thread Ana Ateca
PROTECTED] [mailto:[EMAIL PROTECTED] Enviado el: jueves, 22 de marzo de 2007 18:37 Para: j-users@xerces.apache.org Asunto: Re: Xerces problem >We would like to maintain the HTML text in the XML file. Don't think of it as text, then; think of it (and build it as) XML document structure. N

Re: Xerces problem

2007-03-22 Thread keshlam
>We would like to maintain the HTML text in the XML file. Don't think of it as text, then; think of it (and build it as) XML document structure. Note that you will have to use XHTML rather than HTML (or some approximation of XHTML), or your file will almost certainly be ill-formed and hence not u

Xerces problem

2007-03-22 Thread Ana Ateca
To whom it might concern, We have developed a Java programme using the xercesImpl.jar in order to developed an XML file from data stored in Oracle Database. In the database, we have normal and HTML text (including HTML tags), both informations should be included in the XML file. When we inc

Re: Xerces Problem - Compound Schemas - Name Resolution Error

2007-02-01 Thread Michael Glavassevich
The DOM shouldn't have been modified. The schema loader has a bug where it mutates the DOM in order to rename the original component which is being redefined. This was actually fine before JAXP 1.3 came along. Back then the DOM was always built by the schema loader so it didn't matter whether w

Re: Xerces Problem - Compound Schemas - Name Resolution Error

2007-02-01 Thread Dick Deneer
When I parse your XSD into a DOM, validate it, and serialize it back to XML I get the following modified XML: http://www.w3.org/1999/xhtml"; xmlns:xforms="http://www.w3.org/2002/xforms"; xmlns:xhtml="http://www.w3.org/1999/xhtml"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xm

Re: Xerces Problem - Compound Schemas - Name Resolution Error

2007-02-01 Thread George Cristian Bina
Hello Cefn, You are trying to redefine a complex type with the name head from the XHTML schema but there is no such complex type in that schema, there is only an element with the name head. If you look at the head element definition you see that it contains references to the head.misc group an

Xerces Problem - Compound Schemas - Name Resolution Error

2007-02-01 Thread xerces . apache . org
I'm getting a very weird error when using Xerces to parse an XSD document (Xerces as embedded in Oxygen 8.1). "E src-resolve: Cannot resolve the name 'xhtml:head_fn3dktizrknc9pi' to a(n) 'type definition' component." The full document is shown below as it's very simple. If anyone can make

Re: inside/outside eclipse vs java 1.4/1.5 vs xerces problem

2005-11-10 Thread Stanimir Stamenkov
/[EMAIL PROTECTED]/: For Eclipse, I did have the system library above the Xerces library. I tried moving that below the xerces jars (xercesimpl.jar and xml-apis.jar) but this made no difference in Eclipse (i.e. the test file still compiled without error). I can't help you much more as to ask

Re: inside/outside eclipse vs java 1.4/1.5 vs xerces problem

2005-11-09 Thread msorens
005 17:51:15 +0200 To: j-users@xerces.apache.org Subject: Re: inside/outside eclipse vs java 1.4/1.5 vs xerces problem /michael sorens/: (1) Why am I seeing a difference between command-line and Eclipse compilation? Check your Eclipse project configuration - you've most probably got the Xerces library s

Re: inside/outside eclipse vs java 1.4/1.5 vs xerces problem

2005-11-06 Thread Stanimir Stamenkov
/michael sorens/: (1) Why am I seeing a difference between command-line and Eclipse compilation? Check your Eclipse project configuration - you've most probably got the Xerces library set before the System library, which is really loaded at JVM boot, i.e. before Xerces, during run-time (incl

inside/outside eclipse vs java 1.4/1.5 vs xerces problem

2005-11-06 Thread michael sorens
I have a Xerces issue that surfaced when I upgraded from Java 1.4.2 to 1.5. Plus I get different behavior depending on whether I am inside or outside Eclipse. Here's my simple test file: import org.apache.xerces.dom.DocumentImpl; public class DocTest extends DocumentImpl {