RPC (non-xml based) for java

We are looking at replacing and existing Proprietary (Distinct) RPC interface with a Sun RPC (non-xml based) version. I've seen mentioned somewhere about the sun.sunrpc.* package but can't find anything else about it.
Something like rpcgen for java.
Your help will be much appreciated.

I think you mean RMI - Remote Method Invocation. No XML.

Similar Messages

Sun RPC - Java libraries (non XML based)

We are looking at replacing and existing Proprietary (Distinct) RPC interface with a Sun RPC (non-xml based) version. I've seen mentioned somewhere about the sun.sunrpc.* package but can't find anything else about it.
Something like rpcgen for java.
Your help will be much appreciated.

I think you mean RMI - Remote Method Invocation. No XML.

RPC and XML based ?

Hi
We are in mid of confusion :-) between confusion between JAX RPC and XML based
web services. Now as i understand there are 2 ways of doing web service
1) JAX RPC
2) JAXM
My questiuon when do we use each of them and which would be deciding factor ?
Also say i make a service using java and servicegen. Deploy on weblogic 7.0. I
have my WSDL in place. Now can any client ( C or .NET) access my webservice as
far as they are able to grab my WSDL ?
DO we have tools like WSDL2JAVA for other languages. WSDL2C or WSDL2NET etc.
I am be too offf but am confused and need something to go ahead with weblogic
and java based sewrvice.
Thanks

To keep it simple, JAX-RPC provides an API for building web services and web service
clients that use RPC and XML. While JAXM is an API for XML-based messaging, where
using a messaging provider you can send/receive SOAP messages.
JAXM is used when you are doing a messaging (a la JMS or JavaMail) with SOAP messages.
I would suggest to refer to the following links for good starter course on web
services :
http://java.sun.com/webservices/docs/1.1/tutorial/doc/
http://dev2dev.bea.com/technologies/webservices/tutorials.jsp
In BEA WebLogic we provide "wsdl2service", which is an Ant task that takes as
input an existing WSDL file, and generates the following WebLogic Web service
components:
- the web-services.xml deployment descriptor file
- a Java source file that partially implements the Web service.
Now we probably we could have utilities provided by other vendors to generate
service components in a certain implementation from a WSDL.
Regards
Shridhar
"pranav" <[email protected]> wrote:
>
Hi
We are in mid of confusion :-) between confusion between JAX RPC and
XML based
web services. Now as i understand there are 2 ways of doing web service
1) JAX RPC
2) JAXM
My questiuon when do we use each of them and which would be deciding
factor ?
Also say i make a service using java and servicegen. Deploy on weblogic
7.0. I
have my WSDL in place. Now can any client ( C or .NET) access my webservice
as
far as they are able to grab my WSDL ?
DO we have tools like WSDL2JAVA for other languages. WSDL2C or WSDL2NET
etc.
I am be too offf but am confused and need something to go ahead with
weblogic
and java based sewrvice.
Thanks

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

XML Schema for Java Bugs

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
null

I'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
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

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: 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 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?

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.

XML parser for Java setup

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 Stromholt

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

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

RPC (non-xml based) for java

Similar Messages

Maybe you are looking for