Export (0) Print
Expand All

What's New in Java Language Conversion Assistant 3.0 

Visual Studio 2005

The following features are included with this version of Java Language Conversion Assistant:

  • Support for conversion of EJB applications

  • Support for conversion of CORBA applications

  • Support for conversion of RMI applications

  • Support for conversion of JMS applications

  • Support for conversion of serialized applications

  • Support for conversion of applications that use JNDI

  • Support for conversion of JAAS applications

  • Support for conversion of JCE applications

  • Support for conversion of Java Swing applications

  • Support for conversion of JAXP applications

  • Support for conversion of TRAX applications

  • Support for conversion of applications that use JavaMail

  • A command-line property switch

EJB

Enterprise JavaBeans are converted to the classes in the System.EnterpriseServices namespace for support for all types of enterprise JavaBeans: message-driven beans, session beans, and entity beans.

CORBA

Common Request Broker Architecture (CORBA) classes are converted to the classes in the System.Runtime.Remoting namespace to provide support for distributed computing.

RMI

Remote Method Invocation (RMI) classes are converted to the classes in the System.Runtime.Remoting namespace to provide support for distributed applications and remote objects.

JMS

The classes of the Java Message Service (JMS) are converted to the classes in the System.Messaging namespace, which use Windows message queuing.

Serialized Applications

The classes that implement the java.io.Serializable interface are converted to implement the System.Runtime.Serialization.ISerializable interface.

Applications That Use JNDI

The classes of the Java Naming and Directory Interface (JNDI) are converted to the classes in the System.DirectoryServices namespace to provide naming and directory services. Some methods are converted to System.Runtime.Remoting methods to support remote operations for RMI and CORBA.

JAAS

The classes of the Java Authentication and Authorization Service (JAAS) are converted to the classes in the System.Security namespace to provide all security and authentication services.

JCE

The classes of the Java Cryptography Extension (JCE) are converted to the classes in the System.Security.Cryptography namespace to provide encryption and decryption of messages for greater security.

Java Swing

The classes of the javax.swing package are converted to the classes in the System.Windows.Forms namespace to provide user interface components and controls.

JAXP

The classes of the Java API for XML processing are converted to the classes in the System.Xml namespace. Both SAX and DOM models are supported.

TRAX

The classes of the Transformation API for XML are converted to the classes in the System.Xml.Xsl namespace.

Applications That Use JavaMail

The classes of the JavaMail API are converted to the classes of System.Web.Mail namespace to provide support to construct and send messages using the Simple Mail Transfer Protocol (SMTP).

Property Switch

A command-line switch (/ProcessGetSetOff) is provided so that you can choose whether to leave get/set/is methods as methods or convert them to properties. By default, JLCA converts these methods to properties. If you prefer, you can toggle the command-line switch and leave most of these as methods. For compatibility with other conversions, the following patterns are always converted to properties:

  • ActiveX methods are converted to specific properties in the .NET Framework.

  • CORBA attributes.

  • Accessor, mutator, and state-checking methods required by the .NET Framework.

  • Automatically generated .NET Framework properties.

JSP pages that use the setProperty method with the property set to a wildcard character (*) are not converted correctly because the SupportClass code used to emulate the setting of bean properties expects a property, rather than a get/set method.

Taglib handler class properties are converted to get/set methods, and the code used in the generated ASPX page to set the property values will be broken because custom controls use properties to map to ASPX attributes in the custom HTML tags.

If an accessor method of a visual component is called in a different thread from the one that owns the component, it is converted to the Invoke method, which returns an object type when the ProcessGetSetOff flag is turned on. The return value must be cast to the same type as the return value of the original method.

Unsupported Java-Language Packages

Because of differences between the architecture of CORBA and .NET Framework Remoting, the following CORBA packages and classes are not supported:

  • org.omg.CosNaming

  • org.omg.CosNamingContextExtPackage

  • org.omg.Dynamic

  • org.omg.IOP

  • org.omg.IOP.CodecFactoryPackage

  • org.omg.IOP.CodecPackage

  • org.omg.Messaging

  • org.omg.PortableInterceptor

  • org.omg.PortableInterceptor.ORBInitInfoPackage

Because of differences between the architecture of Swing and Windows Forms, the following Swing packages are not supported:

  • javax.swing.plaf

  • javax.swing.plaf.basic

  • javax.swing.plaf.metal

  • javax.swing.plaf.multi

Because it contains interfaces for implementing third-party drivers, the following package is not supported:

  • javax.sql

See Also

Community Additions

ADD
Show:
© 2015 Microsoft