XSLT version supported in JDK 6 Transformer

Hi! This is a simple question: Does JDK 6 Transformer Class support XSLT 2.0?
My problem raise when I use the <xsl:character-map> tag. A Example:
template.xslt
<xsl:stylesheet version="2.0">
<xsl:output method="xml" version="1.0" encoding="UTF-8" use-character-maps="vxml"/>
<xsl:character-map name="vxml">
   <xsl:output-character character="«" string='&lt'/>
   <xsl:output-character character="»" string='&gt'/>
   <xsl:output-character character="¨" string='"'/>
</xsl:character-map>
<xsl:template match="/">
   «vxml version=¨2.0¨»
   {xslt operations...}
   «/vxml»
</xsl:template>
{code}
*someXML.xml*
{code}
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="template.xslt"?>
{code}
Well, when I use external software (Altova XMLSpy), the result is exactly that I want... but, when I use a simple java class with Transformer (in java 6), the result contains alternative char and no the correct character that character-map is supposed to change.
Then, in this forum all people only use XSLT with version="1.0"... and appear my question... Transformer Class in JDK 6 really support XSLT version 2.0? I can't find information of this...
Edited by: MIrribarra on 20-03-2009 05:51 PM
Edited by: MIrribarra on 20-03-2009 05:53 PM
Deleted intensionally semi-colon in "&lt" and "&gt" because editor change string code                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Simple answer: No.
Less simple answer: you can plug in any transformer you like. The process for doing that is described in the documentation for javax.transform.TransformerFactory, method newInstance.

Similar Messages

  • Xslt version 2.0 support..

    All,
    SOA Versions: 11g(11.1.1.4) and 10g (10.1.3.4)
    Can anyone pls confirm whether bpel 10g and 11g support xslt version 2.0?
    Thanks
    sen

    Found the documents for Oracle XML Developer's Kit saying it supports XSLT 2.0, according to the references bellow the support is partial...
    XSLT 2.0 (working draft dated 04 April 2005) Partial
    XDK Standards
    http://docs.oracle.com/cd/E12839_01/appdev.1111/b28394/adx_ref_standards.htm
    Using the XSLT Processor for Java
    http://docs.oracle.com/cd/E12839_01/appdev.1111/b28394/adx_j_xslt.htm
    Cheers,
    Vlad

  • Which XSLT versions are support by Oracle BPEL? v1.1  or v2.0?

    Which XSLT versions are support by Oracle BPEL? v1.1 or v2.0?
    As far as I heard v1.1 is the highest version but some functions of v2.0 are supported as well.
    Is this true?
    If yes: Which XSLT functions of v2.0 are supported?
    Does it matter if I change the
    version="1.1"
    attribute in the topmost
    <xsl:stylesheet......>
    tag?
    Which XSLT processor is built-in/used?
    Peter

    XSL mapper in BPEL supports 1.0 only in-built. And this is true for 11g also. However, we can declare <xsl:stylesheet version = 2.0 ... and use all xpath 2.0 functions. I have used few of them and has been successful so far. Once you declare version as 2.0 the only issue will be that XSL's visual GUI mapper will not work in JDeveloper and you will need to modify the code from the source.

  • How to display the current Date and time in xslt version 1

    i am using xslt version 1 .i want to display the current date and time in the output xml using xslt(Jdeveloper) ..i just added the namespace xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
         xmlns:ns1="urn:oracle:integration:b2b:7D30046DC68A4FA689956D8241FA3B99">
    and used thsi function <xsl:value-of select = "xp20:current-date()"/>
    but it does not works for me ..help needed????
    Edited by: user9519185 on Jan 20, 2009 3:04 AM

    Use a formula: =NOW()
    Format the cell for Date and Time, with both the Date part and the Time part displayed. Format the two parts as you wish, using the choices in the Inspector's menus.
    The cell will update each time the table is recalculated.
    (Description is for Numbers '09 (Mac), Numbers for iOS will be similar, but not necessarly identical in details.)
    Regards,
    Barry

  • 2007 US Daylight Savings change time zone support in JDK 1.3

    Sun has supported the 2007 US Daylight Savings change in recent versions of its JDKs 1.4 and 1.5. It has made partial Daylight Savings changes to JDK 1.3, but it's not a complete implementation like in 1.4 and 1.5, because there is no support for past/future Daylight Savings rules, only a single current set of Daylight Savings rules per time zone.
    Our Java application (running in the America/New_York time zone) seems to be doomed, because the likelihood of upgrading to JDK 1.4/1.5 seems slim (we have to upgrade a third-party product first and success is seeming more and more remote), and Sun claims to be unable to fully implement the Daylight Savings change in JDK 1.3.
    If any Sun Java staff can explain the reasons for being unable to implement the change in 1.3 (or at least some kind of workaround that an individual JVM user could enable), please fill me in. Any pointers on cleanly setting up a custom workaround would be valuable too.
    If there are other Java users in the same situation, please fill me in on your own plans if you can. Is anybody trying to pressure Sun or other vendors for a solution? Is anybody writing their own custom workaround?
    More details....
    What we really need is for the default TimeZone in JDK 1.3 (America/New_York on our machines) to work regardless of whether the date/time being checked is pre-2007 or post-2007. In particular, getOffset and inDaylightTime should work for both 2006 dates and 2007 dates. The JDK should return the correct values for 2006 dates, as well as the correct values for the 2007 US DST extension dates (03/12/2007-04/02/2007 and 10/29/2007-11/05/2007). This would enable parsing and formatting using SimpleDateFormat to work correctly as well. The TimeZone and SimpleDateFormat APIs are used throughout our application.
    JDK 1.3.1_19 has an interesting workaround that depends on the current system time. Prior to Jan 1 2007, it will handle 2006 dates correctly but 2007 dates wrong. After Jan 1 2007, it will handle 2007 dates correctly but 2006 dates wrong. Either way, it is always wrong for some dates.
    JDK 1.4.2_13 and 1.5.0_09 both handle 2006 and 2007 dates correctly.
    If JDK 1.3 will never work for 2006 and 2007 dates, then I am contemplating two workarounds:
    1. Set the default TimeZone to a custom implementation as soon after JVM startup as possible.
    2. Avoid the default TimeZone entirely, changing our application code to rely on explicit custom TimeZones.
    Prior related Java Forum topics:
    * http://forum.java.sun.com/thread.jspa?forumID=31&threadID=645874 (Java Essentials - Java Programming) winds up referencing the JDK 1.4 patch as a solution, and there is some discussion about how future/historic dates affect applications
    * http://forum.java.sun.com/thread.jspa?forumID=481&threadID=735038 (Deploying - Java Upgrade) just talks about 1.4 and 1.5 patches
    * http://forum.java.sun.com/thread.jspa?forumID=481&threadID=717268 (Deploying - Java Upgrade) also just talks about 1.4 and 1.5 patches
    * http://forum.java.sun.com/thread.jspa?forumID=37&threadID=703214 (Specifications - Java Virtual Machine (JVM)) also just talks about 1.4 and 1.5
    Related Sun Java Bug Database bugs:
    * http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6471271 reports the same issue with 1.3.1_19 that I am seeing and the reporter makes the same clarification, that past/future dates don't work at all still. Sun seems to indicate that it will not fix this in 1.3.1, and the 1.3.1_19 "hack" is it for 1.3.1.
    * http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6391777 refers to updates in 1.3.1_18 to address Australia DST changes, and also indicates that past/future dates (or "historic" dates) won't work at all. It gives a little more rationale behind the difficulty of implementing this for 1.3.1.
    * http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4257314 refers to the fixes in 1.4 to support historic DST dates.
    Other articles:
    * Sun Java article http://java.sun.com/developer/technicalArticles/Intl/USDST/ refers to 1.3.1_18 as "resolving" the DST issue - this is misleading because the solution in 1.3.1_18 is not complete like that in 1.4 or 1.5
    * Server Side article http://www.theserverside.com/news/thread.tss?thread_id=42212 refers to fixes in 1.4 and 1.5 for the DST issue, and the discussion about 1.3 doesn't lead anywhere
    Thanks for any info or advice available,
    Jim

    Hi KBarney
    I think u have the correct data file. to make sure see the "zi" dir is backed up in ur java lib folder or not.
    if u have suspicion than run the tzupdater tool again.
    this tool must be run for each jre/java version on your machine separately.
    I tried this on 1.4.2.13 and not on 1.5.0.10. here is the result:
    C:\Program Files\Java\j2re1.4.2_13\bin>java -jar c:\tzupdater\tzupdater2006p\tzu
    pdater.jar -t -v
    java.home: C:\Program Files\Java\j2re1.4.2_13
    java.vendor: Sun Microsystems Inc.
    java.version: 1.4.2_13
    JRE time zone data version: tzdata2006p
    Embedded time zone data version: tzdata2006p
    Validating the time zone data
    Validation complete
    C:\tzupdater\tzupdater2006p>java -jar tzupdater.jar test verbose
    java.home: C:\Program Files\Java\jre1.5.0_10
    java.vendor: Sun Microsystems Inc.
    java.version: 1.5.0_10
    JRE time zone data version: tzdata2006k
    Embedded time zone data version: tzdata2006p
    Validating the time zone data
    /data/tzdata2006p.test:990: test failed: America/Managua
    /data/tzdata2006p.test:1465: test failed: America/Havana
    /data/tzdata2006p.test:1466: test failed: America/Havana
    /data/tzdata2006p.test:1847: test failed: Cuba
    /data/tzdata2006p.test:1848: test failed: Cuba
    /data/tzdata2006p.test:2024: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2026: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2028: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2030: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2032: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2034: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2036: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2038: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2040: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2046: test failed: America/Cuiaba
    /data/tzdata2006p.test:2048: test failed: America/Cuiaba
    /data/tzdata2006p.test:2050: test failed: America/Cuiaba
    /data/tzdata2006p.test:2052: test failed: America/Cuiaba
    /data/tzdata2006p.test:2054: test failed: America/Cuiaba
    /data/tzdata2006p.test:2056: test failed: America/Cuiaba
    /data/tzdata2006p.test:2058: test failed: America/Cuiaba
    /data/tzdata2006p.test:2060: test failed: America/Cuiaba
    /data/tzdata2006p.test:2062: test failed: America/Cuiaba
    /data/tzdata2006p.test:2471: test failed: America/Montevideo
    /data/tzdata2006p.test:2472: test failed: America/Montevideo
    /data/tzdata2006p.test:2475: test failed: America/Montevideo
    /data/tzdata2006p.test:2476: test failed: America/Montevideo
    /data/tzdata2006p.test:2479: test failed: America/Montevideo
    /data/tzdata2006p.test:2480: test failed: America/Montevideo
    /data/tzdata2006p.test:2483: test failed: America/Montevideo
    /data/tzdata2006p.test:2484: test failed: America/Montevideo
    /data/tzdata2006p.test:2487: test failed: America/Montevideo
    /data/tzdata2006p.test:2494: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2496: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2498: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2500: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2502: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2504: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2506: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2508: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2510: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2516: test failed: BET
    /data/tzdata2006p.test:2518: test failed: BET
    /data/tzdata2006p.test:2520: test failed: BET
    /data/tzdata2006p.test:2522: test failed: BET
    /data/tzdata2006p.test:2524: test failed: BET
    /data/tzdata2006p.test:2526: test failed: BET
    /data/tzdata2006p.test:2528: test failed: BET
    /data/tzdata2006p.test:2530: test failed: BET
    /data/tzdata2006p.test:2532: test failed: BET
    /data/tzdata2006p.test:2537: test failed: Brazil/East
    /data/tzdata2006p.test:2539: test failed: Brazil/East
    /data/tzdata2006p.test:2541: test failed: Brazil/East
    /data/tzdata2006p.test:2543: test failed: Brazil/East
    /data/tzdata2006p.test:2545: test failed: Brazil/East
    /data/tzdata2006p.test:2547: test failed: Brazil/East
    /data/tzdata2006p.test:2549: test failed: Brazil/East
    /data/tzdata2006p.test:2551: test failed: Brazil/East
    /data/tzdata2006p.test:2553: test failed: Brazil/East
    /data/tzdata2006p.test:3451: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3452: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3453: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3454: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3455: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3456: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3457: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3458: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3459: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3460: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3461: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3462: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3463: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3464: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3465: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3466: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3467: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3468: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3469: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3470: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3471: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3791: test failed: ART
    /data/tzdata2006p.test:3814: test failed: Africa/Cairo
    /data/tzdata2006p.test:3844: test failed: Asia/Amman
    /data/tzdata2006p.test:3848: test failed: Asia/Amman
    /data/tzdata2006p.test:3852: test failed: Asia/Amman
    /data/tzdata2006p.test:3856: test failed: Asia/Amman
    /data/tzdata2006p.test:3860: test failed: Asia/Amman
    /data/tzdata2006p.test:3887: test failed: Asia/Damascus
    /data/tzdata2006p.test:3908: test failed: Asia/Gaza
    /data/tzdata2006p.test:3911: test failed: Asia/Gaza
    /data/tzdata2006p.test:3915: test failed: Asia/Gaza
    /data/tzdata2006p.test:3919: test failed: Asia/Gaza
    /data/tzdata2006p.test:3923: test failed: Asia/Gaza
    /data/tzdata2006p.test:4035: test failed: Egypt
    /data/tzdata2006p.test:4901: test failed: Australia/Perth
    /data/tzdata2006p.test:4902: test failed: Australia/Perth
    /data/tzdata2006p.test:4905: test failed: Australia/Perth
    /data/tzdata2006p.test:4906: test failed: Australia/Perth
    /data/tzdata2006p.test:4909: test failed: Australia/Perth
    /data/tzdata2006p.test:4910: test failed: Australia/Perth
    /data/tzdata2006p.test:4914: test failed: Australia/West
    /data/tzdata2006p.test:4915: test failed: Australia/West
    /data/tzdata2006p.test:4918: test failed: Australia/West
    /data/tzdata2006p.test:4919: test failed: Australia/West
    /data/tzdata2006p.test:4922: test failed: Australia/West
    /data/tzdata2006p.test:4923: test failed: Australia/West
    Validation tests failed.
    -Ranjan

  • No PKCS#11 support in JDK 6 Update 14 for Windows x64?

    Hi there,
    I successfully installed GlassFish 2.1 on Windows 2008 x64 with JDK 6 Update 13 for x64. Everything was ok until I wanted to access my USB token with a certificate on it trough an EJB.
    I then had to reinstall everything based on 32-bit versions. Now it works again, but I'm not very satisfied with the solution because I wanted to have everything based 64-bit.
    Why JDK 6 Update 14 for Windows x64 does not contain PKCS#11 support? When you have look to the x86 version support is available there.

    If you load successfully your pkcs11 lib into java 32bit mean that the lib is 32bit.
    You cannot load a 32bit native lib into java 64bit ( http://java.sun.com/docs/hotspot/HotSpotFAQ.html#64bit_native_porting ).
    If you find the 64bit lib for your token, you should be able to use java64.

  • Windows server edition/version  supports installation of  ERP 6.0

    Hi ,
    I am trying to install Solution manager 7.0 ,ERP 6.0. on windows OS.
    and Oracle database.
    My OS : Microsoft windows XP  Proffessional version 5.1 service pack 3 (32 bit)
    RAM Size : 2 GB
    Could anyone give me the hardware and software requirements for installations of solution manager 7.0 and ERP 6.0. on windows.
    which windows server edition/version  supports installation of SOL MAN 7.0 and ERP 6.0 ?
    thanks.

    > Does Microsoft windows2008 server edition / windows 7/vista  supports installation of ERP 6.0  .
    Did you have a look at the PAM as suggest at http://service.sap.com/pam?
    Vista/Windows 7 are client operating systems and are not supported for ERP 6.0 or Solution Manager or any other backend.
    Markus

  • What's the postscript version supported by Preview

    Can anyone please help me with postscript version supported by Mac Previewer V 6.0.1

    Postscript version of what - a font?

  • Has anyone got dynamic version support to work with the HTML converter?

    I have tried this for some time and followed all the guidelines, but it still don't work. Could someone post the HTML-code for a working applet that is converted with dynamic version support ?

    Using 1.4.1_03
    java -jar htmlconverter.jar -gui
    selected directory, "Standard" template file, "Use any Java 1.4, or higher"
    <html>
    <body>
    <!--"CONVERTED_APPLET"-->
    <!-- HTML CONVERTER -->
    <OBJECT
        classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
        WIDTH = 200 HEIGHT = 100 
        codebase="http://java.sun.com/products/plugin/autodl/jinstall-1_4-win.cab#Version=1,4,0,0">
        <PARAM NAME = CODE VALUE = Version.class >
        <PARAM NAME="type" VALUE="application/x-java-applet;version=1.4">
        <PARAM NAME="scriptable" VALUE="false">
        <COMMENT>
         <EMBED
                type="application/x-java-applet;version=1.4"
                CODE = Version.class
                WIDTH = 200
                HEIGHT = 100 
             scriptable=false
             pluginspage="http://java.sun.com/products/plugin/index.html#download">
                 <NOEMBED>
              </NOEMBED>
         </EMBED>
        </COMMENT>
    </OBJECT>
    <!--
    <APPLET CODE = Version.class WIDTH = 200 HEIGHT = 100>
    </APPLET>
    -->
    <!--"END_CONVERTED_APPLET"-->
    </body>
    </html>

  • Blackbarry and Iphone versions supported by MSA

    Hi Folks,
    Any idea about the latest versions of Blackbarry and Iphone versions supported by Oracl MSA.
    Your eralier response would be appreciated.
    Thanks,
    Mayank

    Hi
    Please visit below URL to get more information on MSA. You will get required information.
    http://crmondemand.oracle.com/en/products/mobile/8271_EN
    Below is extract from there :
    Blackberry...
    Oracle Mobile Sales Assistant supports the following BlackBerry devices running BlackBerry OS 4.2,
    4.3, 4.5, 4.6, 4.7, and 5.0:
    ■ BlackBerry models 8700, 8700c, 8700g, 8700r, 8703e, 8705g, 8707g, 8800, 8820, and 8830
    ■ BlackBerry Bold model 9000
    ■ BlackBerry Curve models 8300, 8310, 8320, 8330, 8350, 8520, 8530, and 8900
    ■ BlackBerry Pearl models 8100, 8110, 8120, 8130, and 8220
    ■ BlackBerry Storm and Storm2 models 9500, 9530, and 9550
    ■ BlackBerry Tour model 9630
    Oracle Mobile Sales Assistant accesses data from the following sources:
    ■ Native Personal Information Manager (PIM) data; that is, the contact, calendar, and task data on
    your BlackBerry device
    ■ Oracle CRM On Demand, Release 15 or later
    I Phones...
    Oracle Mobile Sales Assistant supports the Apple iPhone, Apple iPhone 3G, and Apple iPhone 3GS
    running iPhone OS 3.0 or later.
    Regards
    VK

  • ActiveX support in JDK 1.4

    Where are sun.beans.ole.Packager and unregbean utility
    in Java 2 SDK, Standard Edition, v 1.4 Beta 3 for Win32?
    Who knows Sun's plans about ActiveX support in JDK 1.4 releases?
    Thank you,
    Alexander

    More info found in bug 4616580. Please vote...
    -Trond

  • WLC: which software-version support SHA2 certificates for Web Authentification and Web Management ?

    Hello,
    I tried to install new SHA2 3th-Party certificates on our WLCs. There are old WiSM1-Boards and 2504 to support our old 1230 Access Points, running 7.0.251.2, which didn't install it, although the config manual for 7.6 and 8.0 say that SHA2 certificates are supported since 7.0.250.0. When I tried to install the SHA2-certificates I get the message "File transfer failed" an the log says:
    *TransferTask: Dec 12 13:22:14.394: #UPDATE-3-CERT_INST_FAIL: updcode.c:1869 Failed to install Webauth certificate. rc = 1
    *TransferTask: Dec 12 13:22:14.394: #SSHPM-3-KEYED_PEM_DECODE_FAILED: sshpmcert.c:4085 Cannot PEM decode private key
    I tried to install the same certificates on our WiSM2-Boards, running 7.4.121.0 and I failed too. The same certificates could be installed on a 2504 running 8.0.100 without any problems.
    In all 3 cases I tried to install unchained certificates for web management and Level 3 chained certificates  for web authentication. I used the following guides to get the certificates (e.g. taken from the config manual 8.0.100):
    http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html
    http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wlan-security/70584-csr-wlc-00.pdf
    Which software versions support SHA2 certificates and which didn't ? Is the a list for it ?
    Regards

    Hello,
    I solved the problem. First I used a Debian Linux system with Openssl 1.0.1. After I searched the internet using one of the log messages above I found sites which mentioned to use Openssl 0.9.x. So I tried a productive and security fixes Debian Linux System running Openssl 0.9.8 and I succeeded. The wlcs accepted the certificate files and used it after a reboot. The Web GUI still shows a SHA1 Fingerprint, but the certificate signature Algorithm is SHA2:
    Signature Algorithm: sha256WithRSAEncryption
    When you check the openssl.org homepage Openssl 0.9.8 is still one of the actual version of openssl and is still available and fixed. But the Openssl Roadmap says:
    "We don't want to have to maintain too many branches. This is likely to include a timescale for the EOL of version 0.9.8"
    I don't know the differences between certificates made with openssl 0.9.8 and 1.0.1. Is there anybody who can explain it to me ?
    Regards

  • For CRM 5.0 what is the ECC version supported

    Hi,
    Can any one help on this
    For CRM 5.0 what is the ECC version supported?

    ECC 5.0 onwards,
    lower versions can also be integrated using some plug-ins
    hope this helps
    additional info:
    SAP ECC 6.0 and subsequent releases will automatically contain all integration interfaces that so far have been contained in the SAP R/3 Plug-In and that ensured the technical integration with other SAP Components.
    Customers who run SAP R/3 4.6C, SAP R/3 Enterprise 47x100 and 47x200, and SAP ECC 5.0 will receive additional integration interfaces in a Support Package for PI 2004.1. The delivery of this Support Package will be synchronized with that of mySAP Business Suite. The 2005 delivery is in November as part of Support Package 10. Information about the delievery from 2006 onwards are take place here
    This rule applies only for customers with a SAP R/3 Plug-In release PI 2004.1. Customers with PI 2003.1 or older must first upgrade to PI 2004.1 or SAP ECC 6.0.
    No new interfaces will be provided for integration between new SAP component releases and SAP R/3 3.1I to 4.6B.
    Message was edited by: RH

  • Which IOS version supported EEM?

    Hi
    May I know which IOS version supported EEM (Embedded Event Manager) ?
    we are using 2960 and 3750. Does c2960-lanbasek9-mz.150-2.SE5/c2960-lanbase-mz.122-35.SE5 support?
    hugo

    EEM supported on 3750:-
    http://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-software-releases-12-2-special-early-deployments/product_bulletin_c25-614546.html
    But as leo said its not on 2960.

  • SAP Netweaver ABAP version supports JAVA?

    Hi all,
    Im using SAP Netweaver ABAP sp12 version. Is this version supports JAVA applications to deploy on it?
    With Regards,
    Sreehari

    Hello Sree,
    If u want your java applications to run in your system then you should have Java AS too. you can install Java AS as an Add-on installation and u can find a lot of materials for this thro sdn as well as help.sap.com
    regards,
    Anand

Maybe you are looking for

  • Ann: Super 2.0: J2EE tool

    Announcement: Super 2.0 - an EJB/J2EE monitoring/admin tool with SuperEnvironment SuperLogging SuperPeekPoke SuperReport SuperScheduler SuperStress ane SuperPatrol, as a schedule job. You can anonymously down load evaluation copy from: http://www.ACE

  • How do I confirm ITS flow logic  exists?

    Hi Guys, We are upgrading from R/3 4.6C to ECC6.0. The old ITS 2 applications one on ITS 6.2 and another ITS 2.0. We are having difficulty in finding out/confirming if there is a ITS flow logic involved in the stand alone ITS. This will tell us what

  • How to use Parameter from file in window env

    hi All, Please tell me the how I can get Parameter from Saved file and can use in other file. EX: I want to use Password file for each instance like ORCL-manager ORCL_1-tiger ORCL_2-***** how to call this file in other file. using pasword for instanc

  • Windows Vista and Graphical Screen painter (SE51)

    Hi, I am using Windows Vista Business Service pack 1.  SAP GUI 7.1 with patch 9. When I try to launch a graphical screnn painter tool such as SE51, I am always greeted by a Character screen painter.  I have tried all options by changing settings in c

  • When I try to backup my catlaog the program locks up at "Calculating Total Media Size" 33%?

    When I try to backup my catlaog the program locks up during the "Calculating Total Media Size" process at 33%?