XML SQL for Java
Hi,
I am trying to load OracleXMLSQL utility into the Oracle 8.1.5
database from our SUN box, but for some reason, I get the
following error message:
"SQL Error while connecting with oci8 driver to ....could not
open connection"
(I have had the USER_PASSWORD set to the right name. sqlplus
connects fine with USER_PASSWORD)
Any pointers ??
Thanks,
-Sandeep.
null
Oracle Team, it is a month since I posed the question. Do U mind
replying ???
I am using XML SQL Utility on OAS server using Java. The code
compiled fine and displays perfect results using the command
line(on the server), but when I call the program thru browser
using OAS4.0 server, it starts to download a file which has the
following text in it:
Exception caught..!
... /oracle.xml.sql.query.OracleXMLQuery.class
Can U please explain this behavior, and advise on what need to be
done to overcome it ??
-Sandeep.
Sandeep Khanna (guest) wrote:
: Hi,
: Thanks for your reply. I don't understand why I got the error.
: Downloading the utility again, and running it worked without
: problems.
: Now, I can see the results on the UNIX box by using: "java
<class
: name>"
: But, when I call the program thru browser using OAS4.0 server,
it
: starts to download and has the following in the downloaded
file:
: Exception caught..! <path of my
: classfile>/oracle.xml.sql.query.OracleXMLQuery.class
: Any ideas/suggestions ??
: -Sandeep.
: Oracle XML Team wrote:
: : Hi Sandeep,
: : where is the error being raised? During loading? (i.e. when
: : running oraclexmlsqlload.csh?) Or is it when using
: : " java OracleXML " ?
: : The primary cause for this could be that the database is not
: up
: : and running. The second cause could be that the ORACLE_SID
and
: : ORA_SID is not set to the right values.
: : If you are having problems with running the client side
"java
: : OracleXML" then u need to supply the user name and password
: thru
: : the parameter, java OracleXML getXML -user
: "username/password"...
: : Hope this helps,
: : Oracle XML team
: : Sandeep Khanna (guest) wrote:
: : : Hi,
: : : I am trying to load OracleXMLSQL utility into the Oracle
: 8.1.5
: : : database from our SUN box, but for some reason, I get the
: : : following error message:
: : : "SQL Error while connecting with oci8 driver to ....could
not
: : : open connection"
: : : (I have had the USER_PASSWORD set to the right name.
sqlplus
: : : connects fine with USER_PASSWORD)
: : : Any pointers ??
: : : Thanks,
: : : -Sandeep.
: : Oracle Technology Network
: : http://technet.oracle.com
null
Similar Messages
-
XML PARSER for JAVA V9.0.4 version check
Hi,
One of post patch activity for RUP7 in 11i(11.5.10.2) is UPGRADE ORACLE XML Parser for java V9.0.4 version (required). When I checked few things it's confirm that I'm already in java V9.0.4 version?
Is there any script/doc where I can look and check "XML PARSER for JAVA V9.0.4 version in Oracle E-business Suite 11.5.10.2?
thanksHi,
Please see these docs.
Upgrading Oracle XML Parser v9.0.4 with Oracle Applications 11i [ID 271148.1]
How To Setup Oracle XML parser with PL/SQL with Oracle Applications 11i [ID 160474.1]
Oracle XML Gateway Troubleshooting Guide [ID 167474.1]
XML Gateway Setup Testing and Diagnostics [ID 337428.1]
Thanks,
Hussein -
ANN: Oracle XML Parser for Java v2.0.0.1
A new maintenance release of the Oracle Parser for Java is
available for download. It has the following fixes and changes:
Bug fixes for #920536, i.e. Cannot access element attributes via
XSLT; #898423. i.e. ElementDecl's in DTDs; #774774, i.e. DOM
extensions using XSL pattern matching; #863890 i.e. SAX
IOException not thrown.
New APIs in the following new interface:
1. oracle.xml.parser.v2.NSResolver
- resolveNamespacePrefix( find the namespace definition in scope
for a given namespace prefix )
New APIs in the following classes:
1. oracle.xml.parser.v2.XMLNode
- selectNodes( Selects nodes from the tree which match the given
pattern; client can provide an NSResolver implementation to
resolve namespace prefixes in the pattern ).
2. oracle.xml.parser.v2.ElementDecl
- getParseTree( Returns the root Node of Content Model parse
tree, which could then be traversed node by node using
getFirstChild() and getLastChild(). The Node types are: PLUS,
COMMA, ASTERISK, ELEMENT, QMARK ).
This is the first beta patch release for v2.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
nullunzip -l appsborg2.zip | grep 9.0.4
0 04-18-03 20:10 .xdkjava_version_9.0.4.0.0_production
do i still need to do that step?No, you do not have to since "XML Parser for Java v9.0.4" is already installed as part of appsborg2.zip -
ANN: XML Parser for Java v2.0.2.6
The v2.0.2.6 of the XML Parser for Java is now available for download. The following features and bug fixes are included:
Changes:
Conformance to the XSLT/XPATH October REC.
New API in XSLStylesheet class:
removeParam(String param)
resetParams()
Bug fixes:
Bug #1111423: OutOfMemory exception, if multiple calls made to document()
Bug #1101028: Unexpected character error in DTD parsing document using Docbook DTD
Bug #1101021: #default not supported in exclude-result-prefixes
Bug #1099830: Extra characters inserted into output using the XML Parser
Bug #1099663: HTML output does not allow only doctype-public to be specified
Bug #1099536: HTML output does not disable escaping for script, style unless lowercase
Bug #1098738: ArrayOutOfBoundsException xsl:if test="not(@a)'"
Bug #1095047: XSLProcessor NPE'S on named templates with non-empty namespaces
Bug #1094971: XSLStylesheet needs methods for removing parameters
Bug #1092351: Using valueof() shuffles order of elements in my source document
Bug #1086663: xsl:sort data-type attribute can now be a namespace-prefixed name
Bug #1086661: xsl:version attribute now required on literal result element
Bug #1064692: Default xml-serialization should use empty-element syntax
Bug #1064689: Current() function doesn't work correctly
This is the sixth production patch release for v2.
Oracle XML Team http://technet.oracle.com
Oracle Technology Network
nullThe link has been fixed. You will go to the v2 download page
now. Sorry for the inconvience.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Renilton Oliveira (guest) wrote:
: I didn't find the file for version 2.0.0.0 as well.
: Renilton
: Andrei Filimonov (guest) wrote:
: : I tried to download XML Parser for Java v2 it seems that
only
: v
: : 1.0.1.4 is available. Could you please give an exact URL for
: v2
: : download?
: : Andrei Filimonov
: : Oracle XML Team wrote:
: : : The Oracle XML v2 parser is now available for download
here
: as
: : : an early beta release and is written in Java. It features
: an
: : : improved architecture over the Oracle XML v1 parser and
has
: : : shown better performance on small to large XML documents.
: It
: : : will also be able to format the XML document according to
a
: : : stylesheet, having integrated an XSLT processor.
: : : Version 2 of the XML Parser for Java, besides
incorporating
: an
: : : XSLT processor, has been re-architected from version 1.
This
: : has
: : : resulted in a number of changes to the class names
: especially
: : : those that support Namespaces. See v2changes.txt and
: the .diff
: : : difference files in the sample directory.
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
null -
ORACLE XML PARSER FOR JAVA FOR AIX
Hi people!
I'm looking for the Oracle XML Parser for Java 9.0.2.0.0C, my 9iAS is BI Installation 9.0.2.3, where can I get it? In the Downloads Section there is only the version for 10g, and the existing versions for 9i are not for AIX (my OS is AIX 5.2L).
Thanks.Thanks for your help, I navigate through this link and, even it shows a table where appears the release for AIX (9.2.0.6.0), when I get to http://www.oracle.com/technology/tech/xml/xdk/software/prod/utilsoft_java.htm
it shows me only downloads for Sun, Linux and HP-UX, but not for AIX.
Has the version for AIX being deprecated or something like that? -
I've just downloaded your XML Schema for Java software are have been systematically testing it with a relatively simple document. A few bugs:
1. the use="required" attribute of the attribute element doesn't have any effect (doesn't show any error message or throw any exceptions) when the required attribute is omitted.
2. If I declare an element like:
<element name="age">
<simpleType>
<restriction base="positiveInteger">
<maxInclusive value="100"/>
</restriction>
</simpleType>
</element>
Then, if I modify my xml document instance to say:
<age pointless="true">26</age>
This will throw a non-parser exception with a message of null, instead of saying "Attribute 'pointless' not expected", as it does if I redefine the schema declaration as:
<element name="age">
<complexType>
<simpleContent>
<extension base="my:ageType"/>
</simpleContent>
</complexType>
</element>
Will Allan
nullI'm glad someone else has noticed that unique keyref and key don't seem to be working with the Dom Parser. If they don't work WHY ARE THEY (key, keyref, unique) IN THE EXAMPLE'S THAT ARE DOWNLOADED WITH THE SCHEMA PARSER. In report.xsd, a file downloaded with the example, it makes clear usage of unique, key, and key ref. But if you violate the schema definitions in the corresponding file report.xml the parser doesn't complain whatsoever. The only time it barfs is if you change the keyref refer attribute to something other than "pNumKey". It obviously has to work. No bone head would send example files along with their product that didn't work.
So, if anyone at ORACLE or elsewhere has figured out how to use unique, key, or keyref please respond with an explination of how to correctly use them with the parser. Your name will be blessed throughout the ages as a most kind and venerable person. You will be a hallmark, a standard, a shining light for all future generations of what a human being should be! Okay maybe I'm going a little overboard but I'm DESPERATE. With no books or collateral on how this stupid thing works all I can do is hack.
-Thanks -
ANN: XML Parser for Java v2.0.2.5
The v2.0.2.5 of the XML Parser for Java is now available for
download. The following features and bug fixes are included:
Conformance to the XSLT/XPATH October PR.
Support for internationalized error messages has been added. The
locale can be set using setLocale(java.util.Locale) function in
XSLProcessor, SAXParser, and DOMParser.
New APIs in XMLNode class:
value-of(String pattern)
selectNodes(String pattern)
selectSingleNode(String pattern)
selectSingleNode(String pattern, NSResolver ns)
New API in XSLStylesheet class
setParam(String param, String value)
Bug fixes:
Bug #957465: Missing a way to set stylesheet-level param-
variables
Bug #962290: selectNodes() improvements
Bug #1033472: Html output prints empty elements for non-empty
elements
Bug #1040717: Character entity for greater that in html output
style
Bug #1046003: Bug is parsing text nodes larger than 16K
Bug #1051671: 'xsl:namespace-alias' not supported
Bug #1052387: Disable-output-escaping doesn't flush while
printing
Bug #1053273: 'xsl:message' terminate attribute not supported
Bug #1058004: No access to media-type and encoding on xsl:output
Bug #1058008: xsl:version attribute not copied to result
Bug #1061159: Exclude-result-prefixes not supported
Bug #1067965: Bug in Non-validating parser while reading QNames
in DTD
This is the fifth production patch release for v2.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
nullThe link has been fixed. You will go to the v2 download page
now. Sorry for the inconvience.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Renilton Oliveira (guest) wrote:
: I didn't find the file for version 2.0.0.0 as well.
: Renilton
: Andrei Filimonov (guest) wrote:
: : I tried to download XML Parser for Java v2 it seems that
only
: v
: : 1.0.1.4 is available. Could you please give an exact URL for
: v2
: : download?
: : Andrei Filimonov
: : Oracle XML Team wrote:
: : : The Oracle XML v2 parser is now available for download
here
: as
: : : an early beta release and is written in Java. It features
: an
: : : improved architecture over the Oracle XML v1 parser and
has
: : : shown better performance on small to large XML documents.
: It
: : : will also be able to format the XML document according to
a
: : : stylesheet, having integrated an XSLT processor.
: : : Version 2 of the XML Parser for Java, besides
incorporating
: an
: : : XSLT processor, has been re-architected from version 1.
This
: : has
: : : resulted in a number of changes to the class names
: especially
: : : those that support Namespaces. See v2changes.txt and
: the .diff
: : : difference files in the sample directory.
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
null -
Does the latest release of the Oracle XML Parser for Java support JDK 1.2.2?
I have an application which makes use of the XML Parser which runs fine with JDK 1.1.7.
But the application crashes with the use of JDK 1.2.2 .
Any insight into this is appreciated.
nullThe Oracle XSQL Servlet makes extensive use of the Oracle XML Parser for Java V2 as well as its XSLT Engine and runs without issue under 1.1.8 and 1.2.2.
-
I download the XML Parser for Java 3.2.1 Release from the IBM site and I have JDK1.3 installed on my Windows 2000 PC. I've placed the files "xerces.jar" and "xalan.jar" in the location specified by the extensions mechanism (i.e "C:\JDK1.3\jre\lib\ext\").
I downloaded an example where java uses XML but I get an error because it fails to import the following class:
import com.ibm.xml.parser.Parser;
Also in another application the same thing happens with this class:
import com.ibm.xml.parser.TXDocument;
If I remove the xerces and xalan JAR files from the directory mentioned above I get move errors so I presume I have the files in the right location. Do I need to place any other files in that DIR other than the xerces and xalan JAR files?
Any help greatly appreciated!Not sure if you solved your problem.
I think Xerces was handed over to the Apache organisation by IBM and the package names were then changed so that com.ibm would have become org.apache or whatever. At a guess nobody got round to changing the examples. -
XML Parser for Java version 2.0.2.9
I can no longer find the XML parser for Java (version 2.0.2.9) for Sun Solaris and Oracle version 8.1.7.3. This would be the file xmlparserv2.jar for parser version 2.0.2.9
This file support the latest Oracle Applications work flow version and so is necessary but does not seem to be available. All notes on Metalink point to Techweb.
Thanks for your help. -Erik StromholtThis is covered by patch for bug 2199206. Thanks
-
Upgrading Oracle XML Parser for Java v9.0.4 with Oracle Applications 11i
Guys, I applied ATG.PF.H.RUP4. In postinstall steps it is mentioned,Upgrading Oracle XML Parser for Java v9.0.4 with Oracle Applications 11i(doc-271148.1)
which says after applying patch 4038964 do the following--
AUTOCONFIG ENABLED APPLICATIONS ENVIRONMENT
If the Oracle E-Business Suite configuration files are maintained using the AutoConfig infrastructure, proceed with the following:
1. Run the AutoConfig utility.
2. Go to [JAVA_TOP].
3. Run the unzip -l appsborg2.zip | grep 9.0.4 command. If there is a file named as .xdkjava_version_9.0.4.0.0_production, which indicates that XML Parser for Java v9.0.4 is installed correctly as part of appsborg2.zip. Otherwise, run ADAdmin to regenerate the appsborg2.zip file.
4. Restart the application tier server processes such that the new version of Oracle XML Parser for Java will take effect.
but actually the patch is already applied- 4038964. How do i verify if i need to do these steps or not.
The xmlparserv2-904.zip file is already there in wrapper.classpath. of jserv.properties, forms.properties. So i think i dont need to do these steps.unzip -l appsborg2.zip | grep 9.0.4
0 04-18-03 20:10 .xdkjava_version_9.0.4.0.0_production
do i still need to do that step?No, you do not have to since "XML Parser for Java v9.0.4" is already installed as part of appsborg2.zip -
Can't use UTF-16 encoding with XML Parser for Java v2.
This is my XML Document:
<?xml version="1.0" encoding="UTF-16" ?>
<Content>
<Title>Documento de Prueba de gestin de contenidos.</Title>
<Creator>Roberto P rez Lita</Creator>
</Content>
This is the way in which i parse de document:
DOMParser parser=new DOMParser();
parser.setPreserveWhitespace(true);
parser.setErrorStream(System.err);
parser.setValidationMode(false);
parser.showWarnings(true);
parser.parse(
new FileInputStream(new File("PruebaA3Ingles.xml")));
I've got this error:
XML-0231 : (Error) Encoding 'UTF-16' is not currently supported.
I am using the XML Parser for Java v2_0_2_5 and I am a little
confused because the documentation says that the UTF-16 encoding
is supported in this version of the Parser.
Does anybody know how can I parse documents containing spanish
accents?
Thanks in advance.
Roberto P rez.
nullOracle just uploaded a new release of V2 Parser. It should
support UTF-16.
Yet, other utilities still have some problems with UTF-16
encoding. Seems we just
have to wait this one out.
BTW, I'm trying to use Japanese. We, also, have some problems
with JServer.
Roberto P rez (guest) wrote:
: This is my XML Document:
: <?xml version="1.0" encoding="UTF-16" ?>
: <Content>
: <Title>Documento de Prueba de gestin de contenidos.</Title>
: <Creator>Roberto P rez Lita</Creator>
: </Content>
: This is the way in which i parse de document:
: DOMParser parser=new DOMParser();
: parser.setPreserveWhitespace(true);
: parser.setErrorStream(System.err);
: parser.setValidationMode(false);
: parser.showWarnings(true);
: parser.parse(
: new FileInputStream(new File("PruebaA3Ingles.xml")));
: I've got this error:
: XML-0231 : (Error) Encoding 'UTF-16' is not currently supported.
: I am using the XML Parser for Java v2_0_2_5 and I am a little
: confused because the documentation says that the UTF-16
encoding
: is supported in this version of the Parser.
: Does anybody know how can I parse documents containing spanish
: accents?
: Thanks in advance.
: Roberto P rez.
null -
Installing XML Parser for Java v2
I downloaded Oracle XML Parser for Java v2 and looked in the doc directory of the unzipped files but couldn't find any doc about installation. Can anyone point me in the right the direction or tell me how to install and use it to convert XML files stored in the files system to HTML output using XSL stylesheet. Thanks
There is no installation involved beyond including the xmlparserv2.jar in your CLASSPATH. Take a look in the sample directory where we have included sample code and instructions on their use.
Addiaitonal HTML conversion samples are included with the XSQL Servlet download.
Oracle XML Team
null -
XML Parser for Java v2. Applying XSLT to DOM tree
I encountered pretty weird behavior of XML Parser for Java v2.
While applying XSLT to XML document created in memory using DOM
interface I couldn't access element attributes. For example,
given the XML document:
<root>
<Item ID="00001">Value of Item 00001</Item>
<Item ID="00002">Value of Item 00002</Item>
</root>
and XSLT:
<xsl:template match="/">
<HTML>
<HEAD>
<TITLE>XSLT Test</TITLE>
</HEAD>
<BODY>
<xsl:for-each select="/Error">
<H1>Error</H1><xsl:value-of select="."/>
</xsl:for-each>
<TABLE border="0" cellspacing="0" cellpadding="2">
<TBODY>
<xsl:for-each select="/root">
<TR>
<TH style="background-color:khaki">
<xsl:text>Attribute</xsl:text>
</TH>
<TH style="background-color:khaki">
<xsl:text>Value</xsl:text>
</TH>
</TR>
<xsl:for-each select="Item">
<TR>
<TD><xsl:value-of select="@ID"/></TD>
<TD><xsl:value-of select="."/></TD>
</TR>
</xsl:for-each>
</xsl:for-each>
</TBODY>
</TABLE>
</BODY>
</HTML>
</xsl:template>
If I build DOM tree by parsing XML file the resulting HTML
document after applying XSLT will display
Attribute Value
00001 Value of Item 00001
00002 Value of Item 00002
But if I build DOM tree using following code:
XMLDocument xDoc = new XMLDocument();
Element root = xDoc.createElement( "root" );
xDoc.appendChild( root );
Element elem = xDoc.createElement( "Item" );
elem.setAttribute( "ID", "00001" );
root.appendChild( elem ).
appendChild( xDoc.createTextNode( "Value of Item 00001" ) );
elem = xDoc.createElement( "Item" );
elem.setAttribute( "ID", "00002" );
root.appendChild( elem )
.appendChild( xDoc.createTextNode( "Value of Item 00002" ) );
the same XSLT will produce the following HTML output:
Attribute Value
Value of Item 00001
Value of Item 00002
So the value for the ID attribute is not displayed. At the same
time I can access this attribute using DOM interface. For
example, following code
NodeList nList = xDoc.getElementsByTagName( "Item" );
Element e;
for( int i = 0; i < nList.getLength(); i++ )
e = (Element)nList.item( i );
System.out.println( "ID: " + e.getAttribute( "ID" ) );
produces an output
ID: 00001
ID: 00002
Here is the code for applying XSLT to DOM tree:
DOMParser parser = new DOMParser();
parser.parse( new FileInputStream( "test.xsl" ) );
XMLDocument xsldoc = parser.getDocument();
XSLStylesheet xsl = new XSLStylesheet( xsldoc, createURL( "" ) );
XMLDocument out = new XMLDocument();
out.appendChild( new XSLProcessor().processXSL(xsl, xDoc) );
out.print( new FileOutputStream( "test.html" ) );
Andrei Filimonov
nullWe are not getting what you're getting on Solaris. See the
following:
Script started on Tue Jun 22 18:53:56 1999
Processing /view/test/vobs/oracore3/.ndeprodrc.csh
Processing /private/.nderc.csh
[test] > cat bruno.xml
<my_grandpa age="88">
<my_dad age="66">
<me age="44">
<my_son age="22">
</my_son>
</me>
</my_dad>
</my_grandpa>
[test] > cat bruno.xsl
<?xml version="1.0"?>
<!-- Identity transformation -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
<xsl:template match="me">
<xsl:value-of select="my_son/@age"/>
<xsl:value-of select="@age"/>
<xsl:value-of select="../@age"/>
<xsl:value-of select="../../@age"/>
</xsl:template>
</xsl:stylesheet>
[test] > java XSLSample bruno.xsl bruno.xml
<root>
22446688
</root>
[test] > exit
script done on Tue Jun 22 18:54:22 1999
What platform are you on and does your stylesheet and xml doc
match ours?
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Bruno Bontempi (guest) wrote:
: I had a similar problem in accessing element attributes from
an
: XSLT sheet.
: It seems like the processor correctly accesses element
attributes
: in the context node, but does not retrieve values of
attributes
: outside the context node.
: For example, for an XML document like:
: <my_grandpa age="88">
: <my_dad age="66">
: <me age="44">
: <my_son age="22">
: </my_son>
: </me>
: </my_dad>
: </my_grandpa>
: and an XSL stylesheet like:
: <xsl:template match="me">
: <xsl:value-of select="my_son/@age"/>
: <xsl:value-of select="@age"/>
: <xsl:value-of select="../@age"/>
: <xsl:value-of select="../../@age"/>
: </xsl:template>
: I expect an output like:
: 22446688
: but all I get is
: 44
: I am also using Jim Clark's XT, which is returning the
expected
: result.
: Thanks in advance for your help,
: Bruno.
: Andrei Filimonov (guest) wrote:
: : I encountered pretty weird behavior of XML Parser for Java
v2.
: : While applying XSLT to XML document created in memory using
DOM
: : interface I couldn't access element attributes. For example,
: : given the XML document:
: : <root>
: : <Item ID="00001">Value of Item 00001</Item>
: : <Item ID="00002">Value of Item 00002</Item>
: : </root>
: : and XSLT:
: : <xsl:template match="/">
: : <HTML>
: : <HEAD>
: : <TITLE>XSLT Test</TITLE>
: : </HEAD>
: : <BODY>
: : <xsl:for-each select="/Error">
: : <H1>Error</H1><xsl:value-of select="."/>
: : </xsl:for-each>
: : <TABLE border="0" cellspacing="0" cellpadding="2">
: : <TBODY>
: : <xsl:for-each select="/root">
: : <TR>
: : <TH style="background-color:khaki">
: : <xsl:text>Attribute</xsl:text>
: : </TH>
: : <TH style="background-color:khaki">
: : <xsl:text>Value</xsl:text>
: : </TH>
: : </TR>
: : <xsl:for-each select="Item">
: : <TR>
: : <TD><xsl:value-of select="@ID"/></TD>
: : <TD><xsl:value-of select="."/></TD>
: : </TR>
: : </xsl:for-each>
: : </xsl:for-each>
: : </TBODY>
: : </TABLE>
: : </BODY>
: : </HTML>
: : </xsl:template>
: : If I build DOM tree by parsing XML file the resulting HTML
: : document after applying XSLT will display
: : Attribute Value
: : 00001 Value of Item 00001
: : 00002 Value of Item 00002
: : But if I build DOM tree using following code:
: : XMLDocument xDoc = new XMLDocument();
: : Element root = xDoc.createElement( "root" );
: : xDoc.appendChild( root );
: : Element elem = xDoc.createElement( "Item" );
: : elem.setAttribute( "ID", "00001" );
: : root.appendChild( elem ).
: : appendChild( xDoc.createTextNode( "Value of Item
00001" )
: : elem = xDoc.createElement( "Item" );
: : elem.setAttribute( "ID", "00002" );
: : root.appendChild( elem )
: : .appendChild( xDoc.createTextNode( "Value of Item
00002" )
: : the same XSLT will produce the following HTML output:
: : Attribute Value
: : Value of Item 00001
: : Value of Item 00002
: : So the value for the ID attribute is not displayed. At the
same
: : time I can access this attribute using DOM interface. For
: : example, following code
: : NodeList nList = xDoc.getElementsByTagName( "Item" );
: : Element e;
: : for( int i = 0; i < nList.getLength(); i++ )
: : e = (Element)nList.item( i );
: : System.out.println( "ID: " + e.getAttribute( "ID" ) );
: : produces an output
: : ID: 00001
: : ID: 00002
: : Here is the code for applying XSLT to DOM tree:
: : DOMParser parser = new DOMParser();
: : parser.parse( new FileInputStream( "test.xsl" ) );
: : XMLDocument xsldoc = parser.getDocument();
: : XSLStylesheet xsl = new XSLStylesheet( xsldoc, createURL
: : XMLDocument out = new XMLDocument();
: : out.appendChild( new XSLProcessor().processXSL(xsl, xDoc) );
: : out.print( new FileOutputStream( "test.html" ) );
: : Andrei Filimonov
null -
ANN: Oracle XML Parser for Java v1.0.1.1 Maintenance
The first maintenance release of the Oracle XML Parser for
Java is available for download here.
It has the following fixes and changes since 1.0.1:
Bug Fixes:
#843157, parseDTD(InputSource, rootElement) and
parseDTD(URL, rootelement) then parse(InputSource) bugs;
#843143, parse(InputSource) bug;
#793012, no need to print a trace of an exception which is
rethrown.
Changes: None
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
nullThe first maintenance release of the Oracle XML Parser for
Java is available for download here.
It has the following fixes and changes since 1.0.1:
Bug Fixes:
#843157, parseDTD(InputSource, rootElement) and
parseDTD(URL, rootelement) then parse(InputSource) bugs;
#843143, parse(InputSource) bug;
#793012, no need to print a trace of an exception which is
rethrown.
Changes: None
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null
Maybe you are looking for
-
Sims 3 with a GMA 950 Graphic Card?
I really want to use the sims 3 on my macbook. It's a few years old. I looked in System Profiler and saw that i have a GMA 950 graphics card? I'm going to upgrad my memory to 2GB. Will it be possible to play the game? Thanks for the help!
-
IChat AV 3.0.1 (v392) Handling Multiple Connections
I currently run AdiumX to connect to my Yahoo! & AIM instant messenger services to talk with Mac & Windows users. I also run iChat AV to connect to my .Mac instant messenger service for using my iSight since Adium doesn't work with video yet. I would
-
Exit button code not working in FireFox
Hi, I am writing a code on exit button , but it is working in IE but not in FireFox--- code is : import flash.external.ExternalInterface; ExternalInterface.call("window.close",""); Also I tried this: var urlString:String = "javascript:window.close();
-
Set a time/date for forms to automatically close
We are using Forms Central for proposal submissions. There is a deadline for the proposals to be turned in, and up to now, we've had to turn the form off by hand. Is there a way to set up the form so that it automatically closes itself at a certain d
-
Version 2.18. We are runing the Do Setup step on "9.1-Apply patch 7303029". The text in the Wizard for this step states: "Before applying 7303029, if you have applied any other patch previously in preinstall mode and do not intend to merge it with 12