Borland Janeva 6.0 Release Notes

• About Borland Janeva
• Getting started
• What's new in this release
• Compatiblity with previous releases
• Known issues
• Platform information
• Version information

About Borland Janeva

Welcome to Borland Janeva. Borland Janeva provides seamless integration between Microsoft® .NET™ applications and any CORBA® or J2EE™ compliant applications.

The Janeva product provides high performance connectivity from the Microsoft .NET runtime to J2EE and CORBA applications. This product allows applications developed in .NET to access heterogeneous CORBA and J2EE applications via the highly scalable, interoperable and secure protocol: IIOP.

The Janeva product has two primary parts: a set of runtime libraries, and a set of code generators. The Janeva runtime provides a managed code implementation of the IIOP communication protocol, and a type conversion library that maps transparently between .NET Framework types and corresponding Java types. Janeva also includes compilers to generate stubs (or proxies) from J2EE Remote interfaces and EJBs (packaged as .class, .jar or .ear files) or CORBA servers defined in IDL. These stubs are compatible with the .NET Remoting framework, and can be used by .NET applications to access J2EE and CORBA servers. The stubs target the .NET Common Type System, meaning that Janeva applications can be written in any .NET compatible language.

These release notes provide valuable information regarding this release of Janeva.

Getting started

This section contains important information concerning the following areas:

• Installation
• Licensing
• Running Janeva components

Installation

For information on how to install Borland Janeva, please refer to the Installation Guide.

Pre-requisites for Borland Janeva

• .NET Framework
• Visual J#
• Java Runtime Environment

.NET Framework

Janeva is a .NET library. You will need the .NET Framework to develop and run applications with Janeva. Janeva runs with either .NET Framework Version 1.0 or Version 1.1.

This release has been tested using Microsoft .NET Framework 1.0 and Microsoft .NET Framework 1.1

Visual J#

Then Janeva Runtime and Compilers require the Visual J# redistributable package to execute. Janeva has been tested with both the Visual J# version 1.0 and Visual J# version 1.1 redistributable packages.

Important: Janeva will NOT run on any Visual J# Beta versions.

This release has been tested using Microsoft Visual J# .NET 1.0 and Microsoft J# .NET 1.1.

Important: Matching the Visual J# and .NET Framework versions

For proper execution of the Janeva tools and runtime, both Visual J# and .NET Framework must be installed at the same version levels. This means that if you have version 1.0 of the .NET Framework you need the 1.0 version of the Visual J#. IMPORTANT: You can have both versions of .NET Framework installed on your machine. However, if you have both versions of the .NET Framework installed, you MUST install both versions of the Visual J# redistributable package. Having a version of .NET Framework but not the corresponding version of Visual J# will result in an error.

Java Runtime Environment

The Java Runtime Environment is required to run the java2cs compiler tool. This tool processes J2EE application archives (EAR files and EJB JAR files) and generates corresponding C# code. Note that the JRE IS NOT REQUIRED at runtime. It is required only for development.

If you are not building applications against J2EE servers or otherwise do not need to run the java2cs compiler, you need not install the JRE.

Configuring the JRE

If you installed the JRE or configured it as part of the install process, there is no configuration required. However, if you did not configure the JRE as part of the install process and wish to enable the use of the java2cs compiler, you need to configure the JRE.

To configure the JRE, you can use one of two methods.

• Setting JAVA_HOME: You can run your tools after setting the JAVA_HOME environment variable.
• Modifying config file: You can modify the configuration to permanently point to a JRE. To do this edit the toolsjdk.config file in the bin directory of the Janeva install and update the javahome option to point to your JRE/JDK directory.

Licensing

Janeva requires a license to function. Janeva has no grace evaluation period. The Janeva developer license is currently free of charge but users must register with Borland to acquire a license.

The following steps describe this process:

1. Visit http://info.borland.com/new/janeva/key.html and register your copy of Janeva. (You will be reminded of this URL at the conclusion of the Borland Janeva installation.)
2. You will promptly receive an email from Borland with the subject "Borland Product Registration." Attached to the email as a .txt file is the activation key required to fully enable your installation of Janeva.
3. IMPORTANT NOTE: You must change the name of the file to borland.txt which is different than the filename on the file you will receive.
4. Save the activation file with the new filename borland.txt to the directory in which you installed Janeva. If you did not change it, the default location is C:\Program Files\Borland\Janeva.

Deployment Licenses

Deployment licenses for Janeva are provided on the deployment CD under the license directory. Since Janeva 2.5 is a download only release, the deployment CDs will contain the Janeva 1.0 software, but the deployment license on the CD is valid for Janeva 2.5. You can download the Janeva 2.5 software from the Borland website

Licensing Matrix

There are three kinds of licenses for Janeva:

• Development: Used to develop Janeva applications
• Client Runtime Deployment: Used to deploy Janeva based thick-client desktop applications
• Server/CPU Deployment: Used to deploy Janeva based server applications

These licenses differ in their support of the following features:

• Running in an ASP.NET hosted environment (ASP)
• Running in a server environment: For licensing purposes, an application is considered to be a server if running on a host with greater than 2(two) CPUs, running in an ASP.NET environment or servicing other clients(Server). Note that a Server application is one that services other clients (irrespective of whether it is through Janeva or not). I.e. If you are running a application which is not running on ASP.NET and running on a machine with 2 or less cpus, but it is servicing other clients, you will still have to get a Server/CPU license.
• Communicating with J2EE/CORBA servers on a host other than that running the Janeva based application (Remote Communication)
• Creating and using Portable Object Adapters(POA). Note that callback objects are still allowed. Only persistent long running servers are restricted

The following table shows the various features and the appropriate license to enable these features

Running

Running the tools

To run the janeva tools, the [install-root]\bin directory must be in your path.

If you did not configure the JDK at installation time, you can configure it as described in the Configuring JRE section. This is required to run the java2cs compiler as it runs on a Java VM. You can also run the idl2csj tool if you have a JRE configured.

Running the examples

To compile and run the client code you will require the following to be in the path:

• The Janeva compiler tools
• The csc.exe (C# compiler), vbc.exe (Visual Basic compiler), and cl.exe (Managed C++ Compiler)

The scripts to compile the server examples are written to work with the Borland Enterprise Server. To compile and run the server side code you will need the following in your path:

• [bes-install-root]\bin
• [jdk-root]\bin

What's new in this release

• Server support: Full OMG Portable Object Adapter based servers are supported.
• .NET Remoting Well Known Server Type: .NET Remoting style servers using the WellKnownServerType model are supported.
• .NET remoting transient and callback objects: .NET Remoting style transient objects and callback objects are supported
• CAO model support for EJBs: This release supports the CAO pattern abstraction over the EJB factory pattern
• Portable Interceptors: Request Interceptors based on the OMG Portable Interceptors specification are supported
• Security: This release supports security.
  • Client authentication with username/password
  • Identity delegation in ASP.NET
  • SSL for clients and servers
• Configuration model: This release supports the standard .NET configuration mechanism for Janeva that uses an application config file.
• This release is certified against the following application servers
  • Borland Enterprise Server 6.0
  • Oracle9i Application Server Java Edition v9.0.3

What's new in 2.5

• Visual Studio 2003 support
• This release is certified against the following application servers
  • Borland Enterprise Server 5.2.1
  • BEA WebLogic 7.0 and 8.1
  • IBM WebSphere 5.0
• This release has integrated API documentation with Visual Studio.
• HTML API Document documentation is now available in the docs/Janeva-API-Docs directory.

Compatibility with previous releases

This release is not source compatible with Janeva 1.0 or 2.5. If you were using Janeva 1.0 or 2.5, you will need to regenerate your stubs using the Janeva compiler.

The following items highlight source incompatibilities with respect to Janeva 2.5

• Janeva 6.0 now supports full configuration using .NET configuration files. This is now the preferred way of configuring Janeva.
• Janeva 6.0 no longer enables the Borland Enterprise Server proprietary Smart Agent (OSAgent) service by default. The functionality is still available but is not enabled by default. This includes generating code for the BES proprietary Bind() methods.
  • To enable the Bind() methods, use the -bind option when running the compilers.
  • To enable OsAgent functionality at runtime, use

    <janeva>
      <agent enabled="true" port="xxx"/>
    </janeva>
    

    in the configuration file. Note that the port is optional as before and defaults to 14000. You may also use -janeva.agent true command line argument.

The following items highlight source incompatibilities with respect to Janeva 1.0

• Janeva uses strong named assemblies and all applications must be rebuilt to use the new assemblies. Otherwise, your application will still refer to the previous version of Janeva.
• The IiopChannel has now been moved to a different namespace. You must now refer to it as Janeva.Remoting.IiopChannel as opposed to Corba.Remoting.IiopChannel
• The Write/Read methods on ValueData class has been moved to the corresponding ValueFactory class and have been renamed to DefaultWriteValueData and DefaultWriteValueData respectively. Also, the RecordDefaultWrite and CheckDefaultWrite methods have been removed. There is no need to call these methods anymore.
• IDL Attributes now map to .NET properties as opposed to a Get/Set method pair. Note that for java interfaces, methods with the JavaBean convention for properties map to IDL attributes and hence to properties in .NET
• In order to make Janeva CLSCompliant the following method and class names have been changed. Note that this typically will not affect existing applications unless you are using advanced features of Janeva.

  Class/Interface	Original Name	New Name
  Stub classes	_<interface>Stub	<interface>MarshalingStub
  ObjectStub class	_ObjectStub	ObjectMarshalingStub
  Helper Method	_Read	Read_
  Helper Method	_Write	Write_
  Helper Method	_GetTypeCode	GetTypeCode_
  Helper Method	_GetRepId	GetRepId_
  Stub Method	_GetDelegate	GetDelegate_
  Stub Method	_SetDelegate	SetDelegate_
  Stub Method	_GetRepIds	GetRepIds_
  Stub Method	_UncheckedNarrow	UncheckedNarrow_
  ObjectOperations Method	_IsA	IsA_
  ObjectOperations Method	_GetInterface	GetInterface_
  ObjectOperations Method	_NonExistent	NonExistent_
  ObjectOperations Method	_IsEquivalent	IsEquivalent_
  ObjectOperations Method	_Hash	Hash_
  ObjectOperations Method	_Request	Request_
  ObjectOperations Method	_GetPolicy	GetPolicy_
  ObjectOperations Method	_SetPolicyOverrides	SetPolicyOverrides_
  ObjectOperations Method	_GetClientPolicy	GetClientPolicy_
  ObjectOperations Method	_GetPolicyOverrides	GetPolicyOverrides_
  ObjectOperations Method	_ValidateConnection	ValidateConnection_

Known issues with this release

Installation

• The default security configuration of Windows 2003 trusts only a small number of sites including microsoft.com. To view all the live information on the Borland Web Site, you need to modify your Internet Explorer Trusted Sites security zone appropriately.

Examples

• examples\Corba\Callback\Server\app.config:
  The commented section contains typo in property name. The janeva section should read:

  <janeva>
    <vbroker vbroker.orb.enableBiDir="server"/>
  </janeva>
      

  instead of:

  <janeva>
    <vbroker vbroker.orb.enableDiDir="server"/>
  </janeva>
      

• examples\Advanced\Gatekeeper\Firewall\InboundServer\InboundFirewallServer.html:
  Running the example section incorrectly says "Run the client as shown". It should say "Run the server as shown".
• examples\Advanced\QoSPolicies\ExclusiveConnection\Build.bat:
  There is an error in the last line. It should read:

  copy app.config bin\Release\ExclusiveConnectionClient.exe.config
      

  instead of:

  copy app.config bin\Release\ExclusiveConnnectionClient.exe.config
      

Product Usage

• The 'Build Action' advanced property for a J2EE or IDL (.idl,.jar,.ear) file in Visual Studio must be set to 'None' and will otherwise result in unpredictable behavior

Application Server Specific issues

IBM WebSphere

• There is no support for finder methods returning Enumerations and Collections.

Oracle 9i Application Server

• There is no support for finder methods returning Enumerations and Collections.
• When the user code throws a java.lang.RuntimeException, java.rmi.RemoteException or a java.lang.Error, the client will receive a CORBA.UNKNOWN and not the original exception.

BEA WebLogic

• [WLS CR#CR123506] java.sql.DataTruncation and java.sql.SQLWarning exceptions thrown by the server will result in a CORBA.UNKNOWN on the client.

          CORBA.UNKNOWN: Unexpected User Exception: IDL:java/sql/DataTruncation.idlEx:1.0
          CORBA.UNKNOWN: Unexpected User Exception: IDL:java/sql/SQLWarning.idlEx:1.0
       

  This is due to the incorrect repository ID returned by the server, for these exceptions

Platform information

Important: For information on minimum hardware requirements, certified operating systems, JDKs, and compilers, please refer to the Product Platforms Page.

J2SE

The Janeva runtime does not require the Java runtime environment to work. However, the java2cs and idl2csj tools do require the JRE to be installed and configured. The idl2csj is identical to the idl2cs tool, except that it runs on a java VM. If you need to only run idl2cs you DO NOT require the JRE.

Version information

To find the version of your installed copy of Janeva, right-click on a DLL from the explorer and select properties. Change to the "Version" tab and select "Product Version".