Gaurav Seth's WebLog

It's never too late to get started.

Browse by Tags

Tagged Content List
  • Blog Post: .NET Vs J2EE: How do we compare

    A customer recently wrote the following to us- My organization is currently considering either .NET or Java (J2EE) as our enterprise application development platform. I am sold on .NET as I believe that:- · There are cheaper resources (per hour rate) and large vendor/contractor providers...
  • Blog Post: JLCA 3.0 – A Perspective: Cheat Sheet unleashed

    As I promised, I have posted the JLCA 3.0 cheat sheet for the users on my Blogs. The aim of this exercise has been for the JLCA users to understand the conversion process using the Java Language Conversion Assistant 3.0 and the issues they might face during the conversion process. Here is the TOC of...
  • Blog Post: JLCA 3.0 - Usability Features

    JLCA 3.0 includes a new set of features to improve the tool’s usability. Special source code analysis has enabled this version to produce better converted code and could produce customized converted code. These new features are the following: Visual Studio .NET Designer Compliant Usually, as...
  • Blog Post: JLCA 3.0 - Threads

    In Java, there are two ways to create a new thread of execution. One is to declare a class inheriting java.lang.Thread and overriding the method run(). The other way is to create a class implementing java.lang.Runnable and passing it to a new instance of java.lang.Thread. Java Threads are mainly converted...
  • Blog Post: JLCA 3.0 - Java Event Model (AWT and Swing)

    Java Event Model mechanism is primarily featured by listeners and adapters used to deal with the different types of events fired by AWT, Swing of the user himself. Most of Swing components use new event types and listeners. Java Event Model is mainly converted through towards .NET Framework event delegation...
  • Blog Post: JLCA 3.0 - Java Accessibility (JAAPI)

    Java Accessibility allows extending programs by interfacing application components with assistive technologies -such as speech recognition and audio output- for users having special needs and/or permissions. Accessibility could be featured as a two-sided conversation between an assistive technology and...
  • Blog Post: JLCA 3.0 - Serialization

    Serialization corresponds with the core and native technology that Java provides to save/recover the state of objects. It is used by other Java technologies inherent in J2SE 1.3. Java provides two kinds of Serialization: Basic Serialization (Java managed) and Custom Serialization (User managed). In Java...
  • Blog Post: JLCA 3.0 - Java Messaging Service (JMS)

    Messaging is a system of asynchronous request conducted as event-driven communication layer that allows applications to exchange information in the form of messages. The Messages are transmitted using a Message Oriented Middleware (MOM), an intermediary between the clients exchanging information. JMS...
  • Blog Post: JLCA 3.0 - CORBA - Dealing with Other Languages

    Since JLCA only converts Java applications and Java CORBA support is targeted through .NET Remoting, server and/or client applications written in other languages are not be converted entirely. Usually, a converted application could require extensive user-intervention to adapt the .NET Remoting application...
  • Blog Post: JLCA 3.0 - Common Object Request Broker Architecture (CORBA)

    CORBA is a core part of the Object Management Architecture (OMA), a complete infrastructure for distributed computing. It was developed to merge remote procedure calls and object orientation to achieve support for distributed objects. The standard can be implemented with hardware, OS and programming...
  • Blog Post: JLCA 3.0 - Enterprise Java Beans

    Enterprise Java Beans define a server side distributed component model architecture that intends to provide solutions for business applications in a transactional, secure, scalable and platform independent way. It provides features like automatic data persistence, remote messaging, security, resource...
  • Blog Post: JLCA3.0 - Java Beans

    Java Beans are components that can be controlled dynamically and assembled to applications via visual components. However, they not only have visual uses but they could be used to implement non-visual components as well. They are mainly converted to .NET Framework through System.ComponentModel API and...
  • Blog Post: JLCA 3.0 – Java API’s and Java Technologies

    JLCA 3.0 incorporates support to convert J2SE APIs. The APIs are converted to equivalent .NET Framework APIs or Compatibility Classes (Support Classes). Some APIs are either not converted or are converted with a different behavior. Table 5 enumerates the Java APIs that JLCA 3.0 supports and their mappings...
  • Blog Post: JLCA 3.0 - Introduction

    Java Language Conversion Assistant (JLCA henceforth) is a tool that provides support for the conversion of software written in VJ++ and Java to Microsoft’s Visual C# .NET and .NET Framework. JLCA 3.0 is the latest version of the tool. It supports conversion of a majority of Java’s APIs and Java technologies...
  • Blog Post: JLCA 3.0 Cheat Sheet – A perspective

    A lot many times I feel that exhaustive documentation is not available on the Java Language Conversion Tool (JLCA). We have recently been working on the same and in the next few blogs, I would aim to present parts of a cheat sheet for JLCA in the way of my blogs. Here is a list of all topics that I would...
  • Blog Post: Migrating Web/JSP apps using Java Language Conversion Assistant 3.0

    I just want to discuss one of the issues that we have in the Java Language Conversion Assistant (JLCA) 3.0 for which we have had a few customer queries. This relates to migrating Web apps and JSP apps using JLCA 3.0. JLCA converts the Web/JSP apps to the ASP.NET. However, the limitation here is...
  • Blog Post: Customizing Menu Options in Visual Studio

    This is one of the cool features that is offered in Visual Studio 2005 . I came across this recently, when one of our customers was unable to find the location of the Java Language Conversion Assistant in the normal File -> Open -> Convert... menu of Visual Studio. When I dug deeper into the same...
  • Blog Post: ADOMD.NET and JLCA

    Another JLCA customer query… I have a java applet that connects to a servlet which makes calls to an ADOMD.dll via a Java Native Interface. For Microsoft clients I need to change the back end. I was planning to create a Web service in C# to receive requests from the applet and retrieve data from Analysis...
  • Blog Post: Intallation of JLCA 3.0 Beta on Visual Studio .NET 2003

    While installing the JLCA 3.0 beta release for Visual Studio .NET 2003, we have heard back from some customers that there are errors such as the following being thrown “The VJU.EXE Process ended unexpectedly” “Microsoft.JConvert.Extensions.dll not registered. Please reinstall the JLCA” “Conversion...
  • Blog Post: Moving from JDBC to ADO.NET

    One of our customers who wanted to move from JDBC to ADO.NET wrote to us that he was unable to find any article, white pages or case studies about migration database applications from java to .NET i.e. JDBC to ADO.net. He wanted help in finding the relevant information. A> Data access technologies...
  • Blog Post: Availability of JLCA with Visual Studio Express SKUs

    The Java Language Conversion Assistant tool is not available as a download with the express editions of Visual Studio 2005. You would need to install Visual Studio .NET 2003 or Visual Studio 2005 to use Java Language Conversion Assistant. For Visual Studio 2005, the JLCA tool is available with the following...
  • Blog Post: JLCA 3.0 is now SQM Enabled

    With the launch of Visual Studio 2005 and JLCA 3.0, we are a step closer to the customers. In today’s blog I am going to discuss about the Software Quality Metrics (SQM) feature that is now enabled in JLCA as a part of this release. Here are a few excerpts from James Lau’s Blog about SQM … SQM...
  • Blog Post: What’s new for JLCA in Whidbey?

    In a few days from now, come November 7th, the world of software development and developers would take a big leap ahead. Visual Studio a.k.a. Whidbey would be shipped. The product teams and the entire organization are very excited to have come so close to this milestone. And the excitement is increasing...
  • Blog Post: JLCA - The Source Converter Tool (Contd...)

    Continuing from my previous post JLCA - The Source Converter Tool here are some more of my findings Java Messaging Service - Converted JMS applications can not use JMS-compliant MOMs - MSMQ does not handle acknowledgment as JMS-compliant MOMs in the sense it does not re-send messages when a MOM does...
  • Blog Post: JLCA - The Source Converter Tool

    Ah! I wish that the Java Language Conversion Assistant should have been a tool so powerful that one just needs to provide the project files/solution to it, do some settings and BINGO... you have a solution available, up and running, which is completely migrated to C#, makes use of the complete technology...
Page 1 of 2 (36 items) 12