Which XML parser for WLS6.1

I heard BEA's Scott Dietzen at JDJEdge (
http://www.sys-con.com/jdjedge/tv4.cfm ) say that the XML parser used by
WebLogic's web services stack is native (not java). Question - which parser
is it? BEA's own work? Or xp? or...?
do I care?

I think you may have misinterpreted the meaning of "native" ;-)
WLS 6.1 comes with a Java-based, SAX Parser built by BEA engineers. It is included
in the client.jar file created during the Web service assembly process. It is
JAXP-complaint, and definitely Java.
Regards,
Mike Wooten
"dc" <[email protected]> wrote:
I heard BEA's Scott Dietzen at JDJEdge (
http://www.sys-con.com/jdjedge/tv4.cfm ) say that the XML parser used
by
WebLogic's web services stack is native (not java). Question - which
parser
is it? BEA's own work? Or xp? or...?
do I care?

Similar Messages

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
null

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

Oracle XML Parser for Java

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.
null

The 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.

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.
null

Oracle 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

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
null

We 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"?>

<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
null

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
null

ANN: XML Parser for Java Release 1.0.1.4

A new maintenance release of the Oracle Parser for Java is
available for download. It has the following fixes and changes:
Bug fixes for #893971, i.e XML parser cannot parse documents
from InputStream;
#900146 normalize() is wrong if the literal contains angle
brackets;
#898423, multiplicity info about elements enhancement.
New API in the following Classes:
1. oracle.xml.parser.ElementDecl
-getParseTree( Returns the root Node of Content Model
parse tree, which could then be traversed node by node using
getFirstChild() and getLastChild() ).
This is the fourth production patch release. Oracle XML Parser
1.0.1.4.0
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

The 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

Is this a bug or a typo of XML Parser for PL/SQL or something else?

Hello,
Below is a piece of codes I copied from the sample that comes with the XML parser for PL/SQL. I found that this sample could not be compiled since:
1- the method printElements takes in a parameter 'doc' of type 'xmldom.DOMDocument'
2- then this 'doc' is refered to in API method
xmldom.getElementsByTagName which takes two parameter, one of type DOMElement, the other of type char.
Are these tow types compatible?
where can i get a better documentation for the XML parser for PLSQ, the one come with the zip fileis not up to date since the miss documentation for DOM. thank you.
BM
-- prints elements in a document
procedure printElements(doc xmldom.DOMDocument) is
nl xmldom.DOMNodeList;
len number;
n xmldom.DOMNode;
begin
-- get all elements
nl := xmldom.getElementsByTagName(doc, '*');
len := xmldom.getLength(nl);
-- loop through elements
for i in 0..len-1 loop
n := xmldom.item(nl, i);
dbms_output.put(xmldom.getNodeName(n) | | ' ');
end loop;
dbms_output.put_line('');
end printElements;

public class HelpIcon extends Image
The attached snippets showed it extending "mx:Image.
class HelpIcon extends Image
[Embed(source="/assets/Info.png")]public var thisIcon:Class;
The attached snippets showed a type of class.
Not precisely sure what you are asking. I added the code as you suggested, it still will not honor the click event on the image.
Here is the code modified as you suggested;
public class HelpIcon extends Image
[Embed(source="/assets/Info.png")]
public var thisIcon:Class;
public function HelpIcon()
   super();
   this.source = new thisIcon();
   this.addEventListener(FlexEvent.CREATION_COMPLETE,initHelp)
private function initHelp(event:Event):void
   this.removeEventListener(FlexEvent.CREATION_COMPLETE,initHelp);
   this.addEventListener(MouseEvent.CLICK, helpClicked,true,5);
It still does not honor the click event.
Paul

Using XML Parser for PL/SQL in 8.1.7

The XML Parser for PL/SQL is part of 8.1.7,
which is a good thing.
Now my question: What steps do I need to
perfom after installation of 8.1.7 to make
the parser available for my PL/SQL packages,
which call
xmldom.makeNode()
xmldom.appendChild()
xmlparser.newParser()
and other procedures from these packages ?
The schema SYS does not contain the
required packages XMLDOM, XMLPARSER, ...
after installation of 8.1.7.
Do I have to call loadjava and
sqlplus @load.sql extra as in 8.1.5 and
8.1.6 before ?
Of course I'd like to use the natively
compiled XML parser
libjox8_oraclexml_parser_v2.so.
Doesn't the above loadjava override the
installation of this fast parser ?
How can I be safe, that I am using the fast
parser under the PL/SQL cover ?
Tnx for your help
Richard
null

Richard,
That's weird? The packages were installed when I installed 8.1.7. You can just download the latest version of the XDK and reinstall using loadjava and then running the load.sql file to get the packages in. You should use the -f parameter for loadjava to force the new classes to be loaded over the old ones. For code examples and lots of other good tips on using the XDK, check out my new website for everything Oracle and XML at: www.webspedite.com/oracle.

What Oracle version for XML Parser for java

Is the XML Parser for Java only available for use with
Oracle 8i? Is it possible to use with Oracle 8.05
null

The XML Parser for Java can be used with any of the supported
version JavaVMs. The only difference with 8i is that you can
load it into the database and use JServer which is an internal
VM. For 8.0.5 you simple run it externally and connect through
JDBC.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Eddie SHipman (guest) wrote:
: Is the XML Parser for Java only available for use with
: Oracle 8i? Is it possible to use with Oracle 8.05
null

Can I install XML parser for Java in Windows 98?

Could someone tell me how to install XML parser for Java in my PC Windows98 (I already installed JDK1.3)? Or it can not be installed in Windows98?
Thanks in advance!

There's no reason why it shouldn't work on any platform for which JDK1.3 is available. If you're using the batch files shipped with XDK to run the parser, you might need to change the syntax slightly; in any event the key command is just
java -cp c:\xdk\lib\xmlparserv2.jar oracle.xml.parser.v2.oraxml %xdkparm%Brian

Validating XML parser for J2ME?

Hello,
does anybody know a validating XML parser for J2ME?
Thanks
Volker

I mean the XML parser.
I want to know if there are XML parsers which can validate a XML document against a DTD or Schema
Thanks
Volker

URGENT! SEGV-errors when using Oracle C XML Parser for Solaris

I often (not always) got SEGV-error with core dump when I use Oracle Oracle C XML Parser for Solaris. This Error is always got in the call of the the function xmlinit(...) with all params as NULL but the first required for the error code and the second which i assign a macro that evaluates to "US-ASCII". Does anyone knows about this problem?
I am using a very short, wellformed and validated XML document.
I would be very glad for some help about this!
null

Please provide a sample program along with the version number of the XML parser.

What's the best XML parser for J2ME

Hello,
has anybody a suggestione about a light and (hopefully) performant opern source XML parser library to use in a J2ME application?
I'm going to explore Xparse-J and Kxml: Is there anything better?
Thank you,
Andrea

kXML is the most important and popularly use XML parser for KVM. This is a combination of pull parser and the XMLWriter. It coantains a WAP Binary XML and a special kDOM.
NanoXML is another parser for KVM, which works on push-parsing technology. Now it is not very popular.

Which XML parser for WLS6.1

Similar Messages

Maybe you are looking for