Second, a lack of an ambiguous content mode in the Oracle Parser for Java is limiting to our business. Are there plans to add an ambiguous content mode to the Oracle Parser for Java?
Many customers initially have this concern. It depends on what kind of XML data you are storing. If you are storing XML datagrams that are really just encoding of relational information (for example, a purchase order), then you will get much better performance and much better query flexibility (in SQL) to store the data contained in the XML documents in relational tables, then reproduce on-demand an XML format when any particular data needs to be extracted. If you are storing documents that are mixed-content, like legal proceedings, chapters of a book, reference manuals, and so on, then storing the documents in chunks and searching them using Oracle Text’s XML search capabilities is the best bet. The book, Building Oracle XML Applications, by Steve Muench, covers both of these storage and searching techniques with lots of examples.
Related Questions
- Second, a lack of an ambiguous content mode in the Oracle Parser for Java is limiting to our business. Are there plans to add an ambiguous content mode to the Oracle Parser for Java?
- How is Oracle ADF related to existing Oracle frameworks like Business Components for Java (BC4J), UIX, and JClient?
- Is the XML Parser for Java only available for use with Oracle 9i?
