• Java Jdk 1.6.0
• Java Jdk 1.6 Download Windows
• Java Jdk 1.6 64-bit Download
• Java Jdk 1.6 Install

Project site: Screen shots: Download: Download JDK 64 bit 1.6.0.26 http://javadl.sun.com/webapps/download/AutoDL?BundleId=49185. Java Platform 1.6.0.10 0 out of 5 based on 0 ratings. File Size: 15.55 MB. Date Released: Oct 26, 2008. Works on: Windows 95 / Windows 98 / Windows 2000 / Windows XP / Windows Vista / Windows Vista x64 / Windows XP x64 / Windows ME / Windows NT 4.0 / Windows 7 / Windows 7 x64 / Windows 8 / Windows Server 2003 x64 / Windows Server 2003 / Windows.

Contents

Supported Platforms
What's New in Java WSDP 1.6?
Redistributable Components
Nonredistributable Components
Environment Variables
Using Ant That Comes with Java WSDP on Linux
Uninstalling Java WSDP 1.6
Known Issues

The Java^TM Web Services Developer Pack (Java WSDP) is an all-in-one download containing key technologies to simplify building of web services using the Java 2 Platform. For release notes for these technologies see:

• Fast Infoset 1.0
• Registry Server 3.0 EA
• Sun Java Streaming XML Parser 1.0 EA Release Notes
• XML Digital Signature 1.0 Release Notes
• XML and Web Services Security 2.0 EA Release Notes
• WS-I Attachment Sample Application 1.0 EA5 Release Notes
• JAXB 1.0.5 Release Notes
• JAXP 1.3.1 Release Notes
• JAXR 1.0.8 Release Notes
• JAX-RPC 1.1.3 Release Notes
• SAAJ 1.2.2 Release Notes
• JSTL 1.1.1_01 Release Notes

Supported Platforms

Java Jdk 1.6.0

This release of the Java WSDP has been tested in various configurations with J2SE 1.4.2 and J2SE 5.0 on the following platforms:

• Solaris^TM 9 Operating System
• Solaris^TM 10 Operating System
• Windows 2003 Server Professional Edition
• Windows XP Professional Edition
• Windows 2000 Professional Edition
• Red Hat Linux 9.0
• Red Hat Linux AS 3.0

What's New in Java WSDP 1.6?

• Fast Infoset 1.0 FCS acceleration technology built on ASN.1 standards
• Service Registry early access release for SOA web services, built on ebXML 3.0 Registry with full UDDI 3.0 support
• XML Web Services Security 2.0 early access
• Sun Java Streaming XML Parser 1.0 EA release, a high performance implementation of JSR 173
• JAXP 1.3.1 FCS release
• XML Digital Signatures 1.0 FCS release
• Bug fixes, refreshed core components (JAX-RPC, JAXB, JAXR, and more)

Redistributable Components

Redistribution of the entire Java WSDP is subject to this license.

The following Java WSDP components are individually redistributable. Redistribution of a component entails the redistribution of all files comprising the component and any dependent components.

Nonredistributable Components

The following Java WSDP components are not redistributable. These components can be used for designing, developing, and testing purposes only.

Using JAXP 1.3.1 in Java WSDP 1.6 with J2SE SDK 1.4

In J2SE SDK 1.4, JAXP 1.2 is included in the rt.jar file. Unless the 'java.endorsed.dirs' mechanism is used to override the JAXP APIs in the rt.jar file with thejaxp-api.jar file from Java WSDP 1.6, the JAXP 1.2 APIs from J2SE SDK 1.4 will be used. These APIs are incompatible with the JAXP 1.3 implementation classes and, if they are used in this situation, an exception will be thrown.

The 'java.endorsed.dirs' property must be set to include boththe JAXP_HOME/lib directory, which contains the jaxp-api.jar file and the JAXP_HOME/lib/endorsed directory, which contains the implementation JAR files. Although only the JAXP API JAR file is reallyneeded with J2SE SDK 1.4, the same 'java.endorsed.dirs'property setting can be used for both J2SE 5.0, where you do need to override theJAXP 1.3 implementation classes, and J2SE SDK 1.4.2.

Using JAXP 1.3.1 in Java WSDP 1.6 with J2SE 5.0

If you are using Java WSDP 1.6 with J2SE 5.0, you should be using the JAXP 1.3.1 JAR files from JWSDP 1.6, not the JAXP 1.3 JAR files from J2SE 5.0. Since the JAXP classes have been renamed to 'com.sun...' in both JDK 5 and Java WSDP 1.6, we need to override the built-in classes. The APIs are the same (both are version 1.3) but version 1.3.1 implementation classes that ship with Java WSDP 1.6 include some bug fixes that are not included in the version 1.3 implementation classes that ship with J2SE 5.0.

Using Ant That Comes with Java WSDP on Linux

On Linux systems, even if you set your ANT_HOME and PATH environment variables to point to the version of Ant that is installed with the Java WSDP 1.6, when you run the Java WSDP's Ant scripts, your system will look in the /etc/ant.conf configuration file and execute the version of Ant that is configured there. In this case, the default entry is /usr/share/ant. If you want to use the version of ANT that is shipped with Java WSDP, comment out the line that configures Ant in the /etc/ant.conf configuration file and your ANT_HOME and PATH environment variable settings will be used.

Service Registry is Unavailable on Sun Java System Web Server 6.1

The Service Registry software is not supported on Sun Java System Web Server 6.1. If you want to try out the Service Registry software, please use one of the other containers (Sun Java System Application Server 8.1 or Tomcat for Java WSDP).

Fast Infoset Is Turned Off By Default

Fast Infoset is turned off (content negotiation is set to none) by default in Java WSDP 1.6. See the Fast Infoset User's Manual for information about turning on content negotiation.

Environment Variables

The JAVA_HOME environment variable is set to point to the version of the J2SE SDK you specify during installation. If you change your J2SE SDK installation, you will need to edit your <JWSDP_HOME>jwsdp-sharedbinsetenv.bat batch file or <JWSDP_HOME>/jwsdp-shared/bin/setenv.sh and reset the JAVA_HOME environment variable.

All other custom system properties can be set in the file <JWSDP_HOME>/conf/jwsdp.properties as follows:

You can override any of the properties in your file <JWSDP_HOME>/conf/jwsdp.properties by using the -D... argument to any of the start scripts. For example,

Unix: catalina.sh -Dhttp.proxyHost=webcache -Dhttp.proxyPort=8080

Microsoft Windows: catalina -Dhttp.proxyHost=webcache -Dhttp.proxyPort=8080

Console Installation on J2SE 5.0.

If you are running a console installation with J2SE 5.0, the installation will exit if the DISPLAY variable hasn't been set. Make sure that you set the DISPLAY variable before you start the console installation.

Uninstalling Java WSDP 1.6

At some point, you may need to uninstall Java WSDP 1.6:

• On Microsoft Windows, select Start --> Programs --> Java(TM) Web Services Developer Pack 1.6 --> Uninstall.
• On Solaris and Linux, run the <JWSDP_HOME>/uninstall.sh script.

If you ran one of the integration scripts after you installed the Java WSDP, you must rerun the script using the revert.<container>.changes target before you uninstall the Java WSDP.

Known Issues

wscompile in Application Server Is Not Equivalent with wscompile in Java WSDP 1.6

After installing Java WSDP 1.6 into the SunJava System Application Server 8.1, the wscompile script in <sjsas.root>/bin doesn't support the -securityoption, whereas, the wscompile script under <jwsdp.home>/jaxrpc/bindoes support the -securityoption.

Signature Function in XWSS Does Not Work with Application Server and J2SE SDK 1.4.X on Windows

In the domain.xml file, in the <java-config ...>element, the <jvm-options>element sets the java.endorsed.dirs property as follows:

-Djava.endorsed.dirs=${com.sun.aas.installRoot}/lib/jwsdp-tools-lib:${com.sun.aas.installRoot}/lib/endorsedsfssdfs

On Windows, the ':'separator is incorrect. It should be ';'. Because of this,the JAXP 1.3.1 JAR files from the <sjsas.home>/lib/endorseddirectory are not loaded and, instead, the JAXP 1.2.6 JAR files from J2SE SDK 1.4are used. This affects the signature function in XWSS. The problemonly applies to the Windows platform when you use the Sun Java SystemApplication Server as the container and use J2SE SDK 1.4.x.

You can easily work around the problemby stopping the server, and manually editing the domain.xml file.

WSI-Sample Application index.html File Omits derbytools.jar in Classpath

In Section 3.2.3, Step 3, which describes how to createa database, doesn't include the derbytools.jarfile in the classpath, which is required.

Service Registry Has User Registration Turned Off

You do not have to be a registereduser to use the publishing functions with the Service Registry Web UITool. You have permission to perform all operations as the defaultRegistry Operator. You may ignore the documentation about registering and creating user accounts.

Service Registry Has Versioning Turned Off

By default, the Web UI has versioning turned off. You can turn it on by checking the box in the Web UI.This feature was turned off because there are a number of versioningbugs:

• Versioned RegistryPackage Loses Its Contents (Bug ID 6248218)
  Problem Summary: In the JAXR provider, if youchange a Registry Package so as to create a new version of theobject, all the package contents disappear from thenew version.
• Classification Is Added to Both Old and NewVersions of Object (Bug ID 6248293)
  Problem Summary: In general, addingan attribute to an object creates a new version of the object thatcontains the previous attributes of the object plus the changes,but leaves the previous version of the object unchanged. Adding a Classification does not work this way. If you add a classification to version 1.1 of the object, then save the object, the classification now exists in both version 1.1 and version 1.2. (This happens in either the Web Console or the JAXRprovider.)
• Adding Classification, ExternalIdentifier, orSlot Has Side Effect of Deleting External Link (Bug ID 6248418)
  Problem Summary: In the JAXR provider, if you add a Slot, a Classification,or an ExternalIdentifier to an object that has an ExternalLink,the ExternalLink disappears from the new version of the object.

Service Registry Web UI Logs Benign Message to AppServer Log

When you load the Service Registry inthe Application Sever and use the Web UI, the Application Server's server.log file shows anumber of messages about the connection to the database not beingmade and about serialization/deserialization problems that you canignore.

Servive Registry Database (Derby) Running in Embedded Mode

The Derby database used by the ServiceRegistry, which is installed in code>${user.home}, is run in embedded mode. You cannot connect to the database throughany other client when the service registry is running with Derby in embeddedmode.

JAX-RPC Samples Notes

• The Attachments sample has incorrect jwsdphome property. In the build.propertiesfiles you should change the jwsdphomesetting to ${buildhome}/../../../.
• Thesamples.html document includes a %antdeploy-war task that is not required as long as the pre-packaged WAR file is not changed. This step isrequired regardless, since the WAR file is not autodeployed on the container.

JAX-RPC Documentation Errata

The JAX-RPC Release Notes installedwith Java WSDP 1.6 have the wrong release number. It should be 1.1.3. Thetools documentation has not been updated to describe the new-security option.

FastInfoset Does Not ImprovePerformance in Some Cases

FastInfoset makes little or no impactwhen:

• There is no binding, using the wscompileoption -f:nodatabinding
• Complex schema that results in the use of SOAPElement for non-supported schema features, such as xsd:choice

FastInfoset and EJB Web Services Endpoints Using Authentication in Application Server 8.1 2005Q2 UR2

There is a problem with authenticationwhen FastInfoset is enabled and EJBs areused as WebService endpoints. This isbecause 'EJBWebServiceDispatcher' is rejecting all themessages that are not of type 'text/xml'. As a result,applications using 'EJB Webservices endpoints' may fail when FastInfoset is used.

Notes for XWS-Security 2.0 EA

• When running XWS-Security samples under the followingonfiguration:
  • Windows Platform
  • Java WSDP 1.6 installed onTomcat container
  • J2SE SDK 1.4.x

  The classpath separator online number 3 of <jwsdp.home>xws-securitysamplesbuildconfigtomcat-config.xml needs to be changed from ':' to ';' .

  Unix: <property name='java.endorsed.dirs'
value='${tomcat.home}/jaxp/lib/endorsed:${tomcat.home}/jaxp/lib/'/>

  Windows:

  <property name='java.endorsed.dirs'
value='${tomcat.home}/jaxp/lib/endorsed;${tomcat.home}/jaxp/lib/'/>

• Due to a Bug in this release, the order of <xwss:Target>/<xwss:EncryptionTarget> elements within an<xwss:RequireEncryption> element should match the order of corresponding<xenc:DataReference>'s in the <xenc:ReferenceList>of the incoming Message if the Type of the <xenc:EncryptedData>for any of the <xenc:DataReference>'s is 'http://www.w3.org/2001/04/xmlenc#Element'.
• Although the default DataEncryptionMethod, according to the XWS-Security configuration schema, is 'http://www.w3.org/2001/04/xmlenc#aes128-cbc', for backward compatibility reasons, the XWS-Securityimplementation still uses'http://www.w3.org/2001/04/xmlenc#tripledes-cbc' as the default DataEncryptionMethod.

Please send feedback on the Java Web Services Developer Pack to users@jwsdp.dev.java.net.

If you do not already havethe JDK software installed or if JAVA_HOME is not set, the Java CAPS installation will notbe successful. The following tasks provide the information you needto install JDK software and set JAVA_HOME on UNIXor Windows systems.

The following list provides the Java CAPS JDK requirements byplatform.

Java Jdk 1.6 Download Windows

JDK5: At least release 1.5.0_14

Java Jdk 1.6 64-bit Download

JDK6: At least release 1.6.0_03

JDK5: The latest 1.5 release supported by IBM AIX

JDK5: At least release 1.5.0_14

JDK6: At least release 1.6.0_03

JDK5: The latest 1.5 release supported by Apple

JDK5: At least release 1.5.0_14

JDK6: At least release 1.6.0_03

It is not recommended to user JDK 1.6.0_13 or 1.6.0_14with Java CAPS due to issues with several of the wizards used to developapplications. Inaddition, the installation fails on Windows when using JDK 1.6.0_13or 1.6.0_14. The Java CAPS Installerdoes not support JDK release 1.6.0_04 in the 64–bit versionon Solaris SPARC or AMD 64–bit environments. The installer alsodoes not support JDK 1.6.0 or later on AIX 5.3.

To Install the JDK Softwareand Set JAVA_HOME on a UNIX System

1. Install the JDK software.

   1. Go to http://java.sun.com/javase/downloads/index.jsp.

   2. Select the appropriate JDK software version and clickDownload.

      The JDK software is installed on your computer,for example, /usr/jdk/jdk1.6.0_02. You can changethis location.

2. Set JAVA_HOME.

   • Korn and bash shells:

   • Bourne shell:

   • C shell:

3. Change the permissions to enable you to run the Java CAPSInstaller.

Java Jdk 1.6 Install

To Install the JDK Softwareand Set JAVA_HOME on a Windows System

1. Install the JDK software.

   1. Go to http://java.sun.com/javase/downloads/index.jsp.

   2. Select the appropriate JDK software and click Download.

      The JDK software is installed on your computer, for example,at C:Program FilesJavajdk1.6.0_02. You can movethe JDK software to another location if desired.

2. To set JAVA_HOME:

   1. Right click My Computer and select Properties.

   2. On the Advanced tab, select Environment Variables, andthen edit JAVA_HOME to point to where the JDK softwareis located, for example, C:Program FilesJavajdk1.6.0_02.