Old versions of aqapi.jar and xsu12.jar in 10.2 for Windows

I found out that oc4j in 10.2 for Windows contains old versions (1.2) of aqapi.jar and xsu12.jar in oracle_home\oc4j\rdbms\jlib. It was not a problem but when I tried to implement an AQ servlet that interact with a typed XMLType queue I got the java exception during dequeuing:
java.sql.SQLException: XMLTypeFactory can only work with OPAQUE
at oracle.xdb.XMLTypeFactory.create(XMLTypeFactory.java:75)
at oracle.jdbc.driver.Accessor.getORAData(Accessor.java:1387)
at oracle.jdbc.driver.OracleCallableStatement.getORAData(OracleCallableStatement.java:1487)
at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1681)
at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1294)
at oracle.AQ.xml.AQxmlProcessor.dequeueAdtMessages(AQxmlProcessor.java:2564)
at oracle.AQ.xml.AQxmlProcessor.dequeueOperation(AQxmlProcessor.java:1988)
at oracle.AQ.xml.AQxmlProcessor.performAQoperations(AQxmlProcessor.java:678)
at oracle.AQ.xml.AQxmlProcessor.processMessage(AQxmlProcessor.java:381)
at oracle.AQ.xml.AQxmlServlet.doPost(AQxmlServlet.java:238)
The solution is to replace the old versions of these files with new or somehow to remove references to these jars from classpath.

I've been able to find someone willing to do some testing that I can't do without installing old versions of Reader on my computer.  The surprising (to me) result is that the Submit button causes the problem.  By simply removing the Submit button, Reader 10 is now able to print page 1.  The Submit button was set up to do a "mailto".  I don't know whether other destinations also cause the problem of the page not printing with old versions of Reader.

Similar Messages

  • Activation.jar and mail.jar version ????

    I have deployed a web service in Weblogic v7.0 which accepts DataHandler as one
    of its paramters ( for attachments).
    When I invoke from a soap client (weblogic v8.0) it works fine. For using with
    soap client (weblogic v7.0) its
    gives a serializer exception.
    What version of activation.jar and mail.jar should I use for sending attachment
    from weblogic 7.0 client.
    Regards
    Kumar Raj

    Hi Kumar,
    Could you post the exception traceback and clarify the configuration
    (v7.x client to v7.x server fails, but v8.1 client to v7.x server works
    OK?)
    You may also want to take a look at the docs on creating portable stubs
    [1] associated with creating the client jar.
    Thanks,
    Bruce
    [1]
    http://edocs.bea.com/wls/docs81/webserv/client.html#1076586
    Kumar Raj wrote:
    >
    I have deployed a web service in Weblogic v7.0 which accepts DataHandler as one
    of its paramters ( for attachments).
    When I invoke from a soap client (weblogic v8.0) it works fine. For using with
    soap client (weblogic v7.0) its
    gives a serializer exception.
    What version of activation.jar and mail.jar should I use for sending attachment
    from weblogic 7.0 client.
    Regards
    Kumar Raj

  • Classes12.jar and nls_charset12.jar Version

    I am running a java application that talks to 9.2.0.1 Oracle database. I am using classes12.jar,ocrs12.jar and nls_charset12.jar and neither of the jars have a manifest file with a verson number. The classes in the classes12.jar and ocrs12.jar were compiled on 5/17/2001 and the classes in nls_charset12.jar were compiled on 7/13/2000. I need to know what version these jars are, is there any way for you to tell me based on the compilation dates. I tried looking on Oracle download sites for the 9.2.0.1 jdbc jars and they all had classes that were compiled on different dates.
    thank you very much

    You can find out the version of the JDBC driver you're using by creating a DatabaseMetaData object and querying it. The snippet below should work:
        DatabaseMetaData meta = conn.getMetaData();
        // gets driver info:
        System.out.println("\n=============\nDatabase Product Name is ... " +
                           meta.getDatabaseProductName());
        System.out.println("\nDatabase Product Version is " +
                           meta.getDatabaseProductVersion());
        System.out.println("\n=============\nJDBC Driver Name is ........ " +
                           meta.getDriverName());
        System.out.println("\nJDBC Driver Version is ..... " +
                           meta.getDriverVersion());
        System.out.println("\nJDBC Driver Major Version is " +
                           meta.getDriverMajorVersion());
        System.out.println("\nJDBC Driver Minor Version is " +
                           meta.getDriverMinorVersion());
        System.out.println("\n=============");I know of no way, however, to get this information based on the compilation dates of the files.
    Justin
    Distributed Database Consulting, Inc.
    www.ddbcinc.com/askDDBC

  • Difference between aqapi.jar and aqapi13.jar??

    Hi - Can anybody please tell me what is the difference in using aqapi.jar and aqapi13.jar. Is there any compatibility issue. I'm using Oracle database 10g R2.
    I posted the same messgae in AQ section but there was no response. Now I'm posting it here hope no body minds.
    Thanks,
    Sanju.

    An Application Client is written according to the rules of the Application Client component defined by
    the Java EE specification -- just like the Servlet spec defines how to write servlets and the EJB spec
    defines how to write EJB components. An Application Client can have an associated application-client.xml deployment descriptor. It is also packaged into an application client.jar, just like EJBs are packaged into an ejb-jar, and can be placed within an .ear as well. An Application Client can use Java EE environment annotations and injection. The Application Client container automatically performs authentication on behalf of the client. An Application Client is executed by running it within an Application Client container.
    None of these steps apply to stand-alone java clients, but the tradeoff is that the Application Client is
    portable and the stand-alone client is not. You can see the difference between the two approaches
    in this simple Hello, World EJB 3.0 program :
    https://glassfish.dev.java.net/javaee5/ejb/examples/Sless.html

  • Can't get matching xdb6.jar, xmlparserv2.jar and ojdbc6.jar

    No matter what I try, they are always somewhat different and I'm getting exceptions with JDBC on either setSQLXML or on .getString() once I retrieved the SQLXML object and want to get the content back or I'm downright getting "oracle.xdb.XMLType cannot be cast to java.sql.SQLXML"
    How is it possible that Oracle who owns Java and OracleDB can't make a working Java driver? I just want to be able to work with XML, I didn't know this was asking much. I have OracleXE installed.

    Welcome to the forum!
    Whenever you post you need to provide ALL of the product and version information applicable to the question or issue you are asking about
    >
    No matter what I try, they are always somewhat different and I'm getting exceptions with JDBC on either setSQLXML or on .getString() once I retrieved the SQLXML object and want to get the content back or I'm downright getting "oracle.xdb.XMLType cannot be cast to java.sql.SQLXML"
    >
    Before you submit a question or issue use the 'Preview' tab so you can see it as it will display. Then read your entire submission and ask yourself:
    >
    Could I answer a question like that based ONLY on the information that was provided?
    >
    For this thread the answer would be NO!
    All you have done is complain. That is basically the equivalent of a five year old saying 'Mommy, my tummy hurts'.
    >
    No matter what I try
    >
    What did you try? You haven't posted ANY information about what you are even doing, what jars, tools or code you are doing it with or HOW you are doing it.
    >
    I'm getting exceptions with JDBC on either setSQLXML or on .getString() once I retrieved the SQLXML object
    >
    What exceptions? You haven't posted ANY exceptions or any of the code that caused those exceptions.
    Retrieved WHAT SQLXML object? Retrieved from where? What is the full name and version of the database you are using? For Oracle that would be the 4 digit version as returned by 'SELECT * FROM V$VERSION'. Oracle DB doesn't have any SQLXML objects; it has XMLTYPE columns. Is that what you are trying to access?
    >
    Can't get matching xdb6.jar, xmlparserv2.jar and ojdbc6.jar
    >
    Where did you get them from? How did you get them? How do you know that they don't match? What is the full name and version of the jars that you are using?
    Have you used this functionality before? Do you know how to use it? If you have never used it and have no expertise with it we need to know that so we can tell you how to get up to speed so you can use it successfully.
    Since you haven't provided ANY of the information needed to provide any specific suggestions all we can do is assume that you are using the last, current version of Java and all jars files and have never used the functionality. In that case you need to start at the beginning.
    Review the relevant sections of the JDBC Developer's Guide
    http://docs.oracle.com/cd/E18283_01/java.112/e16548/jdbcvers.htm#BABGHBCC
    >
    SQLXML Type
    One of the most important updates in JDBC 4.0 standard is the support for the XML data type, defined by the SQL 2003 standard. Now JDBC offers a mapping interface to support the SQL/XML database data type, that is, java.sql.SQLXML. This new JDBC interface defines Java native bindings for XML, thus making handling of any database XML data easier and more efficient.
    The oracle.jdbc.getObjectReturnsXMLType Property
    In Oracle Database 10g and earlier versions of Oracle Database 11g, Oracle JDBC drivers supported the Oracle SQL XML type (XMLType) through an Oracle proprietary extension. XML values were represented by instances of the oracle.xdb.XMLType class and the SQL XMLType values were read and set through the JDBC standard getObject, setObject, and updateObject methods.
    The JDBC standard requires the getObject method to return an instance of java.sql.SQLXML type when called on a SQL XML type column. But, the earlier versions of Oracle JDBC drivers return an instance of oracle.xdb.XMLType. This does not conform to the JDBC standard.
    The current release of Oracle JDBC drivers conform to the JDBC standard with the introduction of a new connection property, oracle.jdbc.getObjectReturnsXMLType. If you set this property to false, then the getObject method returns an instance of java.sql.SQLXML type. You can achieve this by using the following command line option while compiling your program with javac:
    -Doracle.jdbc.getObjectReturnsXMLType="false"
    If you depend on the existing Oracle proprietary support for SQL XMLType using oracle.xdb.XMLType, then you can change the value of this property back to true by using the following command line option:
    -Doracle.jdbc.getObjectReturnsXMLType="true"
    The value of the oracle.jdbc.getObjectReturnsXMLType property is a String representing a boolean value of either true or false. If the value of this property is true, then the getObject method returns oracle.xdb.XMLType instances, when called for a SQL XMLType column. This is the deafault value of the oracle.jdbc.getObjectReturnsXMLType property. If the value of this property is false, then the getObject method returns java.sql.SQLXML instances. This is the standard JDBC-compliant mode.
    Note:
    The oracle.jdbc.getObjectReturnsXMLType property affects only the result of the getObject method. All other methods conform to the JDBC 4.0 standard regardless of the value of the property.
    >
    The exception that you are getting
    >
    oracle.xdb.XMLType cannot be cast to java.sql.SQLXML
    >
    is telling that the XMLType is NOT an SQLXML type so you can't use it as one. That doc section above should tell explain that those are two DIFFERENT types. You use one or the other depending on which version of the functionality you want to use. You can use the older 'non-JDBC' standard or the new 'JDBC' standard. But you can't mix the two.
    Review that entire chapter of the doc and see if that helps.
    If not then you need to provide ALL relevant information if you need more help:
    1. Java version
    2. DB name and version
    3. JAR file names and versions
    4. Java code that demonstrates the problem
    5. EXACT copies of any and all exceptions and errors that occur
    6. A description, in English, of what you are trying to do and how you are trying to do it.
    When you post use \ on the line before and on the line after any code to preserve formattting. See the FAQ for other formatting guidelines. Use the 'Preview' tab to see what your post will look like before you submit it.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • LDAP Console: why are ds52.jar and ds522.jar needed?

    I updated Sun DS from 5.2 to 5.2 patchlevel 2, the server on Solaris and the LDAP Console on Windows a while ago.
    If I start the LDAP Console all is well.
    If I open the "Server Group" tree node, it wants to download admserv52.jar and ds52.jar
    which fails.
    There are admserv522.jar and ds522.jar (and others with 522 in their file name in the java/jars directory.
    If I copy admserv52.jar and ds52.jar by hand the LDAP Console is able to open the nodes under Server Group,
    but I guess they use the 5.2 and not the 5.22 Versions.
    As an experiment I removed all 5.2 Versions and renamed the 5.22 Versions to 5.2. Result: The LDAP Console does work and it only needs the 5.22 jars.
    Info on Main Console says Server Console 5.2
    Build 2004.007.1414
    Info an Directory Server Windows says Server 5.2
    Build 2003.143.0020(I use the german localized versions but I guess the problem is not relate to that fact)
    Question: How do I configure my setup to use only the new 5.22 Versions in the Console?
    Where did my update go wrong? Or do I really need the 5.2 and 5.22 Versions in /java/Jars?
    Thanks,
    Frerk Meyer

    By try and error I found out that even when I upgraded my
    Sun ONE Directory Server 5.2 to patch level 2, the configuration
    in the administration directory was not changed to the new
    version. So one couldn't connect with the new console
    version 5.2pl2 but used and needed the old one effectively.
    To use the 5.2 pl 2 console there need to be the following
    files in the client directory:
    <root of sun ldap console>/java/jars/
    ds522.jar (main console application)
    ds522_en.jar (english language resources)
    ds522_de.jar (german language resources, in my case, optional)
    ds522.icon (icon used in the console)
    and for the administration console:
    admserv522.jar
    admserv522_en.jar
    admserv522_de.jar
    admserv522.icon
    The old file with the '52' in their name may stay where they
    are to connect to unpatched 5.2 Servers and 5.2pl2 Servers
    without updated configuration.
    The configuration is under:
    cn=ResourceEditorExtension, ou=4.0, ou=Admin, ou=Global Preferences, ou=zentrale.edekanet.de, o=NetscapeRoot
    Search for the attribute 'nsclassname' in all subentries where there
    is a substring '@ds52.jar' and change it to '@ds522.jar'.
    With newer versions of the Sun Directory Server there are
    even jar files with names like 'ds523.jar'. Proceed like above.
    After the next start of the console you are using the new 5.2pl2
    Versions with all bugfixes and enhancements. To verify you may
    move the '52' files away, start and connect. If the directory server
    is configured the right way it won't try to download the '52' files
    to your local computer.
    Frerk

  • Xdb.jar and xmlparserv2.jar for JBossWeb/2.0.0.GA

    I am using xdb.jar and xmlparserv2.jar files in JBoss 4.0.0 and it is working fine but when i deploy my code on JBossWeb/2.0.0.GA it is giving error.
    "java.lang.NullPointerException
    org.apache.commons.digester.Digester.getXMLReader(Digester.java:899)
    org.apache.commons.digester.Digester.parse(Digester.java:1647)
    org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1006)
    org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
    org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
    javax.servlet.GenericServlet.init(GenericServlet.java:212)
    org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
    org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
    org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
    org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    java.lang.Thread.run(Thread.java:595)"
    Could anyone pleaese suggest what could be the possibe reason for this error. Do we need some differant version of jar files for the JBossWeb/2.0.0.GA.
    Thanks and Regards
    Govind Bajoria

    I had a similar problem using xmlparserv2.jar and commons-digester in the same application. It appears that xmlparserv2 sets itself as the default SaxParser but commons-digester doesn't like this (I read it looks for a Version class for the SaxParser and can't find it).
    I solved this problem by explictly setting the SaxParserFactory by adding this System parameter
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    This works for JDK 6 but I assume if you are using an early JDK version and have xerces jar on the class path then setting the following will also work
    -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl

  • Can't find jcert.jar, jnet.jar, and jsse.jar

    I am trying to implement SSL in Tomcat (1.4.18 I think). I have already installed j2sdk1.4.1_01 which is supposed to contain thise files, but I can't find them.
    Does anybody know why this might be happening?

    If you are using j2sdk1.4.1, only jsse.jar exist the rest of it does not. Check the jre folder in your java_home folder and you will see jsse.jar. Copy the jsse.jar and paste it into java_home/jre/lib/ext. after that you can continue with your SSL configuration. I tried it and works fine even without the jnet.jar and jcert.jar. I had the same problem as you when I was configuring SSL on my resin webserver. the documentation for installing jsse may only be applicable to java version jdk1.3 and below.

  • Difference j2ee.jar and javaee.jar

    Hi, it is not clear for me why exist 2 files j2ee.jar and javaee.jar. I have look manifest file for j2ee.jar and found that only contains path to javaee.jar. But
    If I add as library only j2ee.jar to my project - doesn't found e.g. import javax.mail.Folder.
    Problem will be resolved if I add only javaee.jar. But why we need j2ee.jar?

    j2ee.jar has the interface definitions for Java EE v1.4 specification whereas javaee.jar has the interface definitions for Java EE v1.5 (the name has been simplified to Java EE v5). So when you are developing an application that uses JEE v1.4 then you will need j2ee.jar on your classpath when compiling (do not need to package it in the module when deploying). And when you are developing an application that uses JEE v5 then you will need javaee.jar on your classpath when compiling (do not need to package it in the module when deploying).
    The next two questions that might come to your mind are:
    1. How do you know which JEE version you are using for development?
    The j2ee.jar and javaee.jar files are just API deifinitions (interfaces, and abstract classes) for the corresponding Java EE versions (i.e. 1.4 and 5 respectively). These APIs were designed by SUN and specify a contract between a Java EE container and the applications that will be deployed on the container. The implementation of this contract is provided by the various application server vendors. For example, Glassfish v2ur2 implements BOTH versions, however it requires you to specify, in the deployment descriptions, the JEE version which is to be used for the application that you are deploying.
    So in short the version of JEE you are using is specified in the deployment descriptor for the application.
    2. Why do we need these jars only during compilation and do not need to add it to the war (or jar) when deploying our module to the app server?
    The reason is that it will already be available in the app server that you are deploying you application to. This seems quite obvious as if i provide implementation of an interface, i will need to give you the interface as well as you will actually be using my implementation via the interface and not by directly calling my implementation classes. If you directly call my implementation classes then it will beat the whole purpose of defining a standard interface that everyone can use.
    I hope that clears out a few things.
    Regards,
    Jawad.

  • Jstl.jar and standard.jar

    I have an application in 9.2, it is deployed as an exploded directory. For some reason, I have to explicitly add jstl.jar and standard.jar to the weblogic system classpath. I have the jars in the /WEB-INF/lib directory. Weblogic is able to find the classes that are in my other jars that are also in that directory. I have a Spring servlet, and on startup, the application context is able to load and all of my classes and the Spring classes are correctly found.
    However, when I try to hit one of the pages, I get this error:
    java.lang.NoClassDefFoundError: org/apache/taglibs/standard/tag/rt/core/ForEachTag
    I get the feeling that weblogic is correctly parsing through the standard.jar file and correctly finding the tld inside the META-INF directory in the jar. Otherwise, how would it know that it needs to load the "ForEachTag" class? I checked and I made sure that I don't have any .tld files anywhere on the server. I also double checked to make sure that I have the "1.1" version of both of those jars. I also checked and I made sure that my web.xml is the correct version: Here is the top of my web.xml file.
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.4"
    xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" >
    I also did a test where I explicitly added standard.jar and jstl.jar to the classpath (keeping them in the WEB-INF/lib directory, just adding that path to the CLASSPATH) and everything worked.
    Any help would be greatly appreciated. I really don't want to have to modify the startup script of my production servers to include those jars on the classpath.
    Thanks, Chris

    Yes, I tried that. No luck. But, unless I am misunderstanding something, that setting only works if weblogic finds more than one version of a class throughout the classpath. I thought that that setting would just tell weblogic to use the version that it finds in my WEB-INF/lib directory. If this setting were to apply, wouldn't that imply that weblogic is finding some version of this class and I wanted to indicate which one to use. From the error message that I get, weblogic can't find this class anywhere.

  • Difference between admin.jar and admin_client.jar

    OC4J provide two commad-line utility: admin.jar and admin_client.jar for performing configuration tasks on OC4J. admin_client.jar can work in Oracle Application Server clustered environment as well as on a standalone OC4J server, but admin.jar only works in a standalone OC4J installation. Do they have any other difference?
    If used in a standalone OC4J installation, are they the same?

    The documentation on the OC4J management tools covers this to some degree:
    http://download-west.oracle.com/docs/cd/B32110_01/web.1013/b28950/admin.htm#CEGHHGGB
    In a nutshell
    1. admin.jar is the old command line utility we kept in the release for backwards compatibility. It uses a set of internal/proprietrary APIs to work against OC4J. It works only against OC4J standalone.
    2. admin_client.jar is a new command line utility that is based on JMX and its associated set of specifications to manage and deploy to a J2EE container. It can connect to and manage all variants of OC4J -- standalone, single AS instance, clustered AS instance. It has many more resource configuration options added to it. For simplicity, we maintained the "feel" of admin.jar so the command structure is very similar to what was provided in admin.jar, but the way it works is completely different under the covers.
    While admin.jar still works and is supported, you should use admin_client.jar whenever you want to do command line operations with 10.1.3.x. I was considering putting a note to that effect on stdout whenever admin.jar was used, but we didn't end up doing it.
    Another two nice aspects about admin_client.jar are
    1. The common library it uses to perform its operations is also used by the Oracle Ant tasks -- so in effect there are two faces to it -- admin_client.jar and Ant tasks. There's a near 100% compatibility between the two meaning what you can do with admin_client.jar you can most likely do with a set of Ant tasks from a development environment.
    2. We have isolated the dependencies for admin_client.jar and produced a separate, small distribution called oc4j_admin_client.zip (which is 6MB from memory) that can be unzipped onto any remote server and you have the full admin_client.jar utility -- meaning that to perform administration options against ant of the OC4J variants (standalone, single and clustered AS instance) you only need this one, very small distribution.
    cheers
    -steve-

  • What is the difference between admin.jar and admin_client.jar

    Oc4j provide two jar for admin purpose: admin.jar and admin_client.jar. what are the differnce between them?

    I'm sure I've provided an answer for this before -- try searching this forum and see if its there.
    In short: admin.jar is old and uses a bunch of internal APIs.
    admin_client.jar is a new implementation in 10.1.3.x and it uses JMX/JSR77/JSR88 APIs as its basis. It supports config/deployment operations against ALL the OC4J variants -- standalone, OracleAS single instance or OracleAS groups. We've tried to ensure that admin_client.jar has all the necessary coverage from admin.jar -- the syntax is very similar and all the relevant commands are carried forward.
    If you are making a choice, choose admin_client.jar.
    -steve-

  • Standard.jar and jstl.jar directory

    First off I probably should apologize in advance because my problem might be an eclipse config issue.
    I created a simple servlet and I tried to include a jstl library import javax.servlet.jsp.jstl.sql.Result;. It compiled cleanly but, when I ran the application (through a browser accessing tomcat through eclipse) I was getting this error...
    The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application
    I eventually found out what was wrong but I don't understand why it was wrong and that's my question. Originally I had jstl.jar and standard.jar in the projectHome/lib directory. When I moved those 2 files to the projectHome]/WEB-INF/lib directory, however, things ran correctly. Is this a setting somewhere within my tomcat config on eclipse perhaps? Or can someone point me in the right direction about this issue in general?
    Thanks in advance!

    Tomcat and Eclipse have different ideas of classpath.
    In Eclipse you set the classpath as part of the project properties: Java Build Path.
    Tomcat uses:
    - web-inf/classes directory
    - jar files in web-inf/lib
    - jar files in /shared/lib
    - jar files in /common/lib
    So in order to run on Tomcat, they need to be in the web-inf/lib directory.
    Cheers,
    evnafets

  • How to use both ojdbc14.jar and ojdbc6.jar in same weblogic domain(weblogic12C)

    Hi all,
    I 'm having issue of using both ojdbc14.jar and ojdbc6.jar in same weblogic application and same weblogic domain in weblogic 12C environment.
    how can i do that?
    i'm currently having application developed using jdk 1.6 and ojdbc6.jar, application developed using jdk 1.4 and ojdbc14.jar.both are currently installed at same domain.
    i want to use the both ojdbc14.jar and ojdbc6.jar in same domain.
    what i previously did was renaming /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar to /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar.bak and put ojdbc14.jar in the same path when i wanna use ojdbc14.jar.
    i haven't use both in same environment before, but to go live i wanna match about requirement.pls help.
    i know the way use this by having two domains, but in the same domain i could not find a solution yet.
    Please help

    Hey
    I have the similar requirement.. Did you managed to get an option of doing it? If yes, please provide some insights
    Thanks in Advance

  • Webutil.jar and jacob.jar in same archive ?

    Hi,
    When a user connects for the first time to a webutil configured Forms application, 2 popups show up and ask to accept the X509 certificate (because webutil.jar and jacob.jar are signed).
    Our customer wants to know if it's possible to show only one popup (to reduce enduser hassle).
    How can we do it ?
    Is it possible to package webutil and jacob in the same single archive, sign this archive and so have only one popup ?? Any other ideas ?
    Regards

    It's not impossible to find a solution, but then you are miles away from any support from the oracle hotline.
    Don't do that
    Gerd
    PS: Are your users inhouse. Is it possible, that you deploy the jar's via a Software Management System? That may help in this case

Maybe you are looking for