Basics

1. What is Grasshopper?

   Grasshopper is the freely available Developer Edition of Mainsoft^® for Java EE^™. This Visual Studio^® plug-in enables you to develop, debug, and deploy ASP.NET and server applications for Windows^®, Linux^®, and any Java^™-enabled platform using C# or Visual Basic^®. Read more.

2. What's new in version 2.5?

   Version 2.5 allows you to build C# and Visual Basic Web applications using the Visual Studio 2008 development environment and host them on open Java platforms. Version 2.5 supports new language features for C# 3.0 and Visual Basic 9, such as Local Type Inference, Object and Collection Initializers, Anonymous Types, and Auto-Implemented Properties.

   Like Grasshopper 2.2, Grasshopper 2.5 provides full support for ASP.NET AJAX and integrates seamlessly with Microsoft's ASP.NET 2.0 AJAX Extensions and the AJAX Control Toolkit.

3. What version of the .NET Framework is supported?

   Mainsoft for Java EE 2.2 and 2.5 supports the .NET Framework v2.0. We're working with the Mono community on the .NET Framework 3.x.

4. What's the difference between Grasshopper and Mainsoft for Java EE, Enterprise edition?

   They are now one and the same. Grasshopper is freely available to developers that want to use Visual Studio 2008, with C# or Visual Basic, to develop, debug, and deploy ASP.NET applications for Windows, Linux, and any Java-enabled platform deployed on single-CPU, multi-CPU, or clustered servers. Grasshopper provides an integrated development support for WebSphere Application Server and Tomcat; and the ability to deploy to any standard, fully featured Java EE server such as JBoss^® and WebLogic^®. The license allows redistribution of Grasshopper-based applications. Support for Grasshopper is provided through the forums. For enterprise support, contact sales@mainsoft.com.

5. Will Mainsoft continue supporting Websphere Portal?

   Yes, Mainsoft will continue to support Mainsoft, Portal Edition and Mainsoft SharePoint Integrator for WebSphere Portal customers. Customers can contact support@mainsoft.com.

6. Do I need Java development knowledge to use Mainsoft for Java EE?

   No. Mainsoft for Java EE is an extension of the Visual Studio development environment. You can develop Java EE applications using the same tools and techniques you use to develop .NET applications.

7. Why should I use a Visual Studio-based development tool to develop Java EE applications?

   While there is a growing set of commercial and open source tools for Java EE development, these tools are designed for Java–savvy developers. If you have invested a lot of time into becoming an expert in Visual Studio development, the .NET languages (C# or VB) and the .NET Framework (ASP.NET, ADO.NET, etc.), we believe Mainsoft for Java EE can be your most productive Java EE development tool.

8. Does Mainsoft for Java EE hinder my ability to develop Windows applications?

   No. You can continue using Visual Studio to create Windows applications as you always have. Mainsoft simply adds Visual C# for Java EE and Visual Basic for Java EE project types. You can continue working with the regular Visual C# and Visual Basic projects types.

9. How does Mainsoft test Mainsoft for Java EE?

   Mainsoft's QA team uses standard, commercial, and proprietary test suites and nearly 5 million lines of code from real world integrative applications to ensure that the .NET Framework used in Mainsoft for Java EE is enterprise-ready. We use the Microsoft Shared Source CLI test suites, OASIS, NIST, and WS-I test suites, as well as commercial test suites including the PlumHall C# test suite.

   We also use large enterprise class servers in our QA labs for system stress and throughput testing.

   Finally, we've designed Mainsoft for Java EE to be self-hosted. The .NET Framework is written in C#, and validates both the Mainsoft for Java EE cross compiler and the .NET core library.

10. Is Mainsoft for Java EE a standards-based solution?

    Yes. Mainsoft is part of the Visual Studio Industry Partner (VSIP) program, which ensures our cross-platform technologies meet the highest requirements for an add-on. Mainsoft for Java EE's cross compiler is based on ECMA CLI and ECMA C# specifications and generates Java bytecode compliant with the Java Virtual Machine specifications. Mainsoft for Java EE has been certified Java Powered for the Enterprise by Sun Microsystems, and has been validated Ready for WebSphere Software, Ready for IBM Systems with Linux, and Server Proven to run on all IBM server platforms.

Licensing

1. What are the licensing terms for Grasshopper?

   Grasshopper is freely available, with no support and no warranty. Here is the license agreement and an activation key. Applications can be deployed on single-CPU, multi-CPU, or clustered servers. Applications developed with Grasshopper can also be distributed commercially.

2. How do I obtain an activation key for Grasshopper?

   Register on the Mainsoft Developer Zone. Then click here.

Architecture

1. How does Mainsoft for Java EE work?

   Mainsoft for Java EE is built on three major components:

   1. The core technology is the cross compiler that converts the Microsoft Intermediate Language (MSIL) code to Java bytecode. This infrastructure generates native Java applications from C# or VB source code.

   2. A Visual Studio plug-in that seamlessly integrates Mainsoft for Java EE extends the IDE functionalities cross-platform.

   3. The Mono .NET Framework is rehosted on top of the Java EE infrastructures, allowing you to port .NET applications to Java EE.

2. Does the Mainsoft for Java EE cross compiler handle language constructs that are specific to .NET?

   Yes, the Mainsoft for Java EE cross compiler handles delegates, generics, multi-dimensional arrays, nullable types, unsigned types, structs, enums, boxing, etc. It also maps the basic .NET types to the Java Virtual Machine built-in types (e.g. System.Object maps to java.lang.Object) in order to take full advantage of the Java VM capacities.

   You cannot compile unsafe code. See detailed limitations in the Mainsoft online help.

3. How does Mainsoft for Java EE integrate into the Visual Studio IDE?

   Mainsoft for Java EE provides two new project types, Visual C# for Java EE and Visual Basic for Java EE, which are very similar to Visual Studio C# and VB project types. The Mainsoft project types extend multiple functionalities, such as:

   • Build process: The Microsoft compiler creates the MSIL DLL and then invokes the Mainsoft for Java EE compiler. Once the build is complete, Mainsoft for Java EE deploys the final Web Java binary as a WAR (Web Archive) file, onto the Java EE application server.

   • Reference system: Java references are also available.

   • Debugger: Attach, monitor, and control the execution of Java EE applications from Visual Studio debugger windows.

   • Online help: The Mainsoft for Java EE online help is integrated into the Visual Studio book collection and the Mainsoft Reference Guide is integrated into Visual Studio indexes and Visual Studio dynamic help. Mainsoft also provides SUN JDK HTML help as part of the Visual Studio online help.

4. Do I need a Windows server to run Mainsoft applications?

   No. Mainsoft applications are pure Java applications that can be run on any server that runs a Java Virtual Machine. Mainsoft applications have been deployed on various hardware architectures including System z, Power, SPARC, and Intel running various operating systems including Linux, zOS, Windows, and AIX.

5. How is the Mainsoft .NET Framework architected on top of the Java EE infrastructure?

   The Mainsoft for Java EE .NET Framework is built on the Mono .NET class library re-hosted to the Java EE infrastructure. Mainsoft designed the runtime according to the following architectural tenets:

   • The deployed applications are compliant to the Java EE specifications, have full access to application server services, and are manageable through the regular Java EE application server management tools and by Java EE administrators.

   • The .NET Framework APIs are compliant to Microsoft implementation, to support porting of .NET applications to the Java EE platform.

   To meet these two tenets, Mainsoft architected the .NET Framework components on top of the Java EE infrastructures:

   • The ASP.NET engine is implemented on top of the servlet container, exactly like the JSP (Java Server Page) engine or the Java Server Faces (JSF) Web applications engines.

   • The ASP.NET Membership, Role, and Profile providers are relying on Apache Derby, a pure Java-embedded database to provide the persistent storage for the ASP.NET runtime.

   • In the Portal Edition:

     • The ASP.NET Authentication module is using WebSphere Portal User Management to access the portal logged-in user information.

     • The ASP.NET Membership and Role providers use WebSphere Portal User Management to access user and role information.

     • The ASP.NET Profile provider is built on top of JSR 168 user attributes and JSR 168 portlet preferences to store and retrieve user properties.

   • The ADO.NET runtime is implemented on top of the JDBC (Java DataBase Connectivity) APIs and support any database that is JDBC-enabled. Java EE administrators can create Java EE data sources that can be seamlessly used by ADO.NET based applications.

   • The thread APIs, reflection APIs, globalization APIs and all the core functionality is implemented on top of the J2SE (Java 2 Standard Edition) APIs.

6. Is Mainsoft for Java EE an emulation?

   No. Mainsoft for Java EE converts Microsoft Common Intermediate Language (MSIL) bytecode directly to Java bytecode. The final executed code is native Java code.

Open Source

1. What exactly is Mono?

   The Mono Project is the leading open source implementation of the Microsoft .NET Framework and runtime environment (CLR). Sponsored by Novell, the Mono open source project has an active and enthusiastic contributing community. Its .NET implementation is based on the ECMA standards for C# and the Common Language Infrastructure. For details on the project, read the Mono FAQ.

2. What is the relationship between Mainsoft and the Mono project?

   Mainsoft has actively contributed to the Mono since 2003, contributing to the ongoing development and testing of Mono class libraries, primarily ASP.NET, ASP.NET AJAX, ADO.NET, XML, System, and Visual Basic. The Mainsoft .NET Framework is based on the Mono .NET Framework, re-hosted on the Java EE infrastructures, using the Mainsoft cross compiler and a proprietary, Java implementation of the .NET core library – mscorlib.jar.

3. What are the major differences between Mainsoft for Java EE and Mono?

   There are three primary differences between Mainsoft for Java EE and Mono:

   1. Mainsoft's runtime strategy is based on Java EE and proven enterprise quality and platform availability. Mono implements its own .NET execution engine, the Common Language Infrastructure (CLI), on several Linux and UNIX-based platforms.

   2. Mainsoft for Java EE focuses exclusively on Web and server applications, while Mono also supports desktop applications, with Gtk# and Windows.Forms.

   3. Mainsoft for Java EE is fully integrated into the Visual Studio IDE whereas Mono uses its own IDE.

4. Is Mainsoft for Java EE an open source project?

   No. Mainsoft for Java EE is a proprietary product, with commercial and freely available editions with an open source runtime. Mainsoft is an active contributor to the Mono open source project. You can download the Mono-based class libraries and contribute to the Mono project using Mainsoft for Java EE.

5. Which of the Mainsoft for Java EE .NET Framework assemblies are open source?

   All of Mainsoft's .NET Framework assemblies are open source, with the exception of mscorlib, which is Mainsoft's proprietary implementation of the .NET core library on top of Java EE.

6. Can I enhance the Mainsoft for Java EE runtime libraries myself?

   Yes, you can download the Grasshopper Framework sources, browse them, edit them, and recompile them using Mainsoft for Java EE. You can contribute your enhancements to us, through the Grasshopper Forums, and we will synchronize them with Mono, or you can post them to the Mono community directly. Currently most of the Grasshopper Framework assemblies are directly developed within the Mono SVN codebase, and you can download the Mono sources to get the latest sources. For more details, see the Open Source Zone.

7. Can I contribute to Mono using Mainsoft for Java EE?

   Yes. Mainsoft is sponsoring Visual Studio developers' contributions to the Mono project. For the first time, you can use Visual Studio to contribute to the Mono project. Download Grasshopper Framework sources directly from the Mono tree and submit your classes, fixes and enhancements. Get involved with the Mono developer community using the mono-devel-list. Your contribution will be integrated directly in the next Grasshopper release. For more details, see Download the Source Code.

System Requirements

1. What are the system requirements for developing an application with Mainsoft for Java EE?

   Development machines must be Windows machines running Windows XP, Windows 2003 Server, or Windows Vista. You also need to install Visual Studio 2005, Service Pack 1. Check the Mainsoft for Java EE Release Notes for further details.

   If you're using Mainsoft for Java EE to develop for IBM WebSphere Application Server or IBM WebSphere Portal, we recommend you have at least 1GB of physical memory. Check the Mainsoft for Java EE Release Notes for further details.

2. Can I use Mainsoft for Java EE with Visual Studio Express Edition?

   Unfortunately not, since the Visual Studio Express Edition has a limited support for extensibility that does not match the tight integration needs of Mainsoft for Java EE. You need to install Visual Studio Standard or Professional Edition to use Mainsoft for Java EE.

3. What are the runtime system requirements to deploy my Mainsoft for Java EE-based application?

   Mainsoft applications are pure Java applications and as such they do not impose runtime requirements beyond those of Tomcat or the application server you decided to use. For system requirements of Linux deployments, refer to the article, Configuring your Linux box to deploy your Grasshopper application.

4. Will my deployed application run on any operating system and any hardware?

   Deployed applications will run on any operating system and hardware supported by your target Java EE application server.

5. Which Java EE application servers are supported by Grasshopper?

   Today, Mainsoft's integration with the Visual Studio IDE level is supported for IBM WebSphere Application Server 6.0, 6.1 and Tomcat 5.5 (as a Web-container). Grasshopper also supports deployment to any standard, fully featured Java EE server such as JBoss^® and WebLogic^®.

6. Can I deploy my application on a non-supported application server?

   Yes, you can adapt the Java EE application you've developed to any standards-compliant Java EE application server such as JBoss or WebLogic. You will have to modify the generated server specific deployment descriptors and potentially change your code if you make direct calls to server-specific APIs or server specific extensions.

   With Mainsoft for Java EE, Portal Edition, the .NET Framework provided by Mainsoft is based on the JSR 168 specifications. Therefore, if you use the .NET classes exclusively, you can deploy your application on any JSR 168 compliant portal.

   If you are using the Mainsoft Membership and Role providers or Mainsoft controls that are specific to WebSphere Portal, you will be able to deploy on WebSphere Portal only. For more details, check the Mainsoft for Java EE Release Notes.

7. Which databases can I use when developing with Mainsoft for Java EE?

   Mainsoft for Java EE uses JDBC as its underlying technology for connecting to databases. While all databases with a valid JDBC driver can be used with Mainsoft for Java EE, we have certified:

   • Microsoft SQL Server 2005 (all editions) with SQL server 2005 JDBC driver

   • Microsoft SQL Server 2000 SP4 with SQL server 2000 JDBC driver

   • PostgreSQL 8.0 with JDBC 3 driver for JDK versions 1.4 and 1.5

   • Oracle 9.2 and Oracle 10g with JDBC driver 10g

   • IBM DB2 8.2 with JDBC driver 8.2

8. Can I use a non-supported database?

   Yes. Any database that has a compliant JDBC driver should work successfully with Mainsoft for Java EE. Given the differences in behavior between databases, certain code modifications may be necessary.

Porting

1. Can I port DLLs to Java EE even if I don't have the source code?

   No. Although the cross compiler can cross-compile a .NET DLL to a Java EE JAR successfully, you will likely need to perform a few source code changes to complete your port successfully.

2. Can I port any .NET application with Mainsoft for Java EE?

   You can port any type of .NET Web or server applications such as ASP.NET applications, ASP.NET Web services, remoting servers, tcp/ip servers, class libraries, and console applications. You cannot port desktop applications using Windows.Forms.

3. Can I use Mainsoft for Java EE to port ASP.NET Web applications?

   Yes. Mainsoft supports the required .NET Framework components, including System.Web and System.Web.Extensions to port ASP.NET Web applications and ASP.NET AJAX applications to the Java EE platform.

4. Can I use Mainsoft for Java EE to port ASP.NET XML Web services?

   Yes. Mainsoft supports the required .NET Framework components, attributes, and access points, including System.Web, System.WebServices, and System.XML, and it supports the WebServices and WebMethod attributes and .asmx entry points to enable you to port ASP.NET XML Web services to Java EE.

5. Can I port an application using .NET third party libraries?

   Yes, provided you have the the third party's .NET source code. Without the source code, you will need to find a Java EE-equivalent third party that provides similar functionality and then adapt your code to invoke the third-party Java component using the Mainsoft for Java EE Add Java Reference feature.

6. How can I estimate the work effort required to port my .NET applications to Java EE using Mainsoft for Java EE?

   The complexity of the port will depend on which Windows, .NET technologies, and third party applications your application uses, and whether Mainsoft supports these technologies on Java. If not, you may have to find Java alternatives and modify your code to use the Java components. Mainsoft's cross-compiler will emit compilation errors and warnings when you're using unsupported .NET classes. Mainsoft also provides a porting analysis tool, which scans your application binaries and reports the unsupported classes your application uses.

   There are also a few behavioral differences related to basic differences between Java EE and .NET or between Windows and UNIX/Linux that you may also need to address. For instance, URLs are case sensitive in Java EE and files are case sensitive in UNIX/Linux.

   For commercial applications, Mainsoft Consulting provides porting services on a fixed-cost and fixed-time basis. You can contact our professional services team for a free binary analysis.

7. How much of the .NET Framework is supported by Mainsoft for Java EE?

   Mainsoft for Java EE supports.NET technologies used by enterprise server and Web applications. Mainsoft .NET Framework includes the following assemblies: mscorlib, System, System.Web, System.Web .Extensions, System.Web.Services, System.XML, System.Data, System.Drawing, System.DirectoryServices, System.Runtime.Remoting, System.Runtime.Serialization.Formatters.Soap, Microsoft.VisualBasic, System.Configuration, and System.Data.OracleClient.

   Mainsoft's cross compiler issues build warnings and errors if your application uses unsupported or partially implemented classes. They are also listed in the Mainsoft for Java EE Class Library Reference. Read our Runtime Framework overview for further information.

   Additional assemblies will be delivered in future releases. Watch for future releases of Beta components on the Developer Zone. You can also enhance the Mainsoft for Java EE .NET Framework and implement additional classes yourself. Download the sources packaged as Mainsoft for Java EE projects and build them in the Visual Studio development environment. You can develop, compile, and debug your edition of the application. You can also contribute your enhancements back to us using the Mainsoft for Java EE forums or via the Mono community.

Development

1. Which types of applications can I create with Visual Studio and Mainsoft for Java EE?

   Mainsoft provides Java EE project templates for Web applications, Web AJAX applications, portal applications, Web services, Web control libraries, console applications, and class libraries. You can use any Java class library in your project and consume Web services.

2. Can I integrate my ASP.NET Web application or ASP.NET Web service into my Java EE security configuration?

   Yes. Mainsoft-based ASP.NET Web applications and Web services are Java EE servlets. Mainsoft ASP.NET project templates include the web.xml servlet deployment descriptor file that you can update to configure your Java EE security settings.

3. Is it possible to reuse existing Java code with Mainsoft for Java EE?

   Yes, developers can import any Java class library into a Mainsoft for Java EE project and use it as a native C# or Visual Basic class. See Adding Java references in the online help.

4. Do .NET applications developed with Mainsoft for Java EE support internationalization?

   Yes. Mainsoft for Java EE supports the System.Globalization namespace, satellite assemblies, and ASP.NET local and global resources.

   When using the Portal Edition to develop ASP.NET portal applications, you can configure your Java EE portal using the visual Portlet Designer and automatically set the .NET Culture according the portal users' preferred languages. For more information, refer to Localizing portal applications in the online help.

5. Can I develop a Java EE class library, in C# or VB, and use them in Java projects?

   Yes. You can use Mainsoft for Java EE to create class libraries that can be used from Java development tools as regular Java class libraries. Read Developing Java libraries in the online help for details.

6. Can I debug an application running on a remote machine?

   Yes. The Visual Studio plug-in connects to your remote Java EE application using Java Platform Debugger Architecture (JPDA). You dont need the application server to reside on the local machine to debug the application. You can debug, from the Visual Studio development environment, a Java EE application server running on your Java EE server.

7. Does Mainsoft for Java EE provide tools for troubleshooting?

   Yes. For problems during development, Mainsoft for Java EE enables logging for the various Visual Studio integration components: the compiler, the debugger, and the IDE integration.

   During runtime, use the Mainsoft for Java EE tracing engine to troubleshoot problems. See Troubleshooting in the online help.

Portal Applications

1. Are Mainsoft-based portal applications compliant to the JSR 168 specifications?

   Yes. Mainsoft for Java EE produces 100% Java-compliant bytecode, which is packaged into a WAR package that is compliant to the JSR 168 specifications. It contains the JSR 168 portlet deployment descriptor that is generated by the Mainsoft Portlet Designer.

2. Can I run Mainsoft portal applications on any JSR 168-compliant portal server?

   Yes, provided that you use Mainsoft .NET Framework classes only, and you do not use the portal server APIs directly or Mainsoft's providers that are specific to WebSphere Portal. Refer to the Supported application servers for details.

3. Which portal servers are supported by Mainsoft for Java EE, Portal Edition.

   Today, Mainsoft supports IBM WebSphere Portal Versions 6.1, 6 and 5.1. You can also deploy to any JSR 168-compliant Java EE server, provided you rely on Mainsoft .NET Framework classes exclusively.

4. Can I create ASP.NET portlets that will leverage WebSphere's single sign-on and security infrastructures?

   Yes. Mainsoft-based ASP.NET portlets run natively inside the IBM WebSphere Portal JSR 168 portlet container and use WebSphere Portal's authentication. The ASP.NET Principal identity is set with WebSphere Portal user identity, and the ASP.NET Membership and Roles APIs are based on WebSphere Portal User Management Architecture (PUMA).

5. Can I create ASP.NET portlets that will be part of a WebSphere Portal composite application, cooperating with Java based portlets?

   Yes. Since Mainsoft-based ASP.NET portlets run natively on WebSphere Portal, they can be part of a WebSphere Portal Composite Application. Together with Java portlets, Mainsoft-based .NET portlets can leverage the Portal Property Broker and cooperate with other portlets written in Java or .NET. Read Developing cooperative portlets with Mainsoft, Portal Edition for more details.

6. Will my portlet integrate with my portal branding?

   Yes. Mainsoft provides an ASP.NET theme named WebSphere Portal that contains a skin file with CSS definitions that apply to the ASP.NET controls.

7. Can my ASP.NET portlets leverage the various WebSphere Portal portlet services?

   Yes. Since Mainsoft-based ASP.NET portlets run locally on the WebSphere Portal JSR 168 portlet container, they have access to all WebSphere Portal portlet services such as the Credential Vault service for identity mapping, the PUMA service for user management, the Model SPI for accessing the portal navigation structure, and more...

8. Do I need to know the JSR 168 specifications to create ASP.NET portlets?

   No, using Mainsoft's Portal Edition -- and its Portal Authentication Module, Portal Membership, Role and Profile Providers, Visual Studio-based Portlet Designer, and ASP.NET WebSphere Portal theme -- you can use your expertise in ASP.NET development to create fully integrated portal applications.

Web Services

1. Are Web services developed with Mainsoft for Java EE interoperable with Web services developed with native Java tools? With Web services running on .NET?

   Yes. We have tested interoperability with Web services developed with major Java IDEs and with Web services running on the Microsoft .NET Framework.

2. Are Web services developed with Mainsoft for Java EE exposed to the Web like ASP.NET Web services?

   Yes. It will appear by default with an .asmx URL.

3. Can I create a Web service from my .NET class?

   Yes. Mainsoft for Java EE supports attribute programming and implements the WebService and WebMethod attributes that you can use to create a Web service from your .NET class.

4. Does Mainsoft for Java EE adhere to the Web Service Interoperability rules defined by WS-I?

   Yes. We run the WS-I basic profiles 1.0 test set to validate compliancy to WS-I rules. You need to follow the .NET programming rules as defined in MSDN Applying Basic Profile Rules articles. Mainsoft supports the .NET 2.0 WS-I conformance claim.

5. Does Mainsoft support .NET 2.0 SOAP 1.2 protocol functionalities?

   Yes, Mainsoft supports the SOAP 1.2 protocol specification and the new 2.0 Web Services classes related to SOAP 1.2.

6. Can I use DataSets in a Web services interface?

   Yes, however your Web services will interoperate only with Web services running on the Microsoft .NET Framework and with Mainsoft-based Web services. This is because DataSets do not comply to the WS-I basic profile rules.

7. Does Mainsoft for Java EE support Microsoft-specific extensions to Web services like WSE 2.0 or Disco?

   No. You need to use Java alternatives or standard APIs such as UDDI instead.

8. How do I consume a Web service in my Mainsoft for Java EE project?

   You can add a Web service reference in Mainsoft for Java EE exactly as you would in typical Visual Studio projects, using Add Web Reference. Mainsoft for Java EE creates a proxy class that hides the complexity of the Java coding, so the references look like any other Microsoft project.

9. Does Mainsoft create a test page for my Web service?

   Yes. The test page will use the standard HTTP SOAP operation and not the HTTP GET and POST.

10. Does Mainsoft support Windows Communication Framework?

    Not yet. Mainsoft will introduce support for .NET Framework 3.0 key components, such as the Windows Communication Framework (WCF), with the release of Mainsoft for Java EE. We're working on the development of WCF with the Mono community.

Deployment

1. Do I need a Windows .NET server to run applications developed with Mainsoft for Java EE?

   No, you do not need any Microsoft .NET components to deploy or run your application. Mainsoft for Java EE creates fully compliant Java EE applications that run on any Java EE-enabled server, including Linux, UNIX, and Windows.

2. Does my Java EE system administrator need to use Mainsoft to deploy my applications?

   No. System administrators can install and manage applications created with Mainsoft for Java EE as standard Java EE applications. Once a Mainsoft for Java EE application is deployed on a Java EE application server, it can be administered through the Java EE application server administration console and third party tools such as Tivoli.

3. Does my Java EE system administrator need to install additional software on the production Java EE application server?

   No. Systems administrators can install and manage applications created with Mainsoft for Java EE as fully packaged, standard Java EE applications from the Java EE application server admin console.

4. Can I deploy a Mainsoft application on a clustered environment?

   Yes. Applications developed with Grasshopper can be deployed in a clustered environment.

5. I am running several Mainsoft-based applications on my application server. Do I need to deploy each of them with all Mainsoft runtime JARs (Java Archive files)?

   No. You can deploy the Mainsoft for Java EE Framework in the application server's shared classpath.

6. What kinds of JAR files are provided by Mainsoft for Java EE to deploy an application on a Java-enabled server?

   The Mainsoft for Java EE runtime libraries consist of JAR files that are compliant with the Java specification. These files can either be added to the classpath of the Java EE application server, or they can be included in the WAR file of the application being deployed.

7. Can I use a Java Data Source in my Mainsoft for Java EE-based application?

   Yes. This is the recommended way to interact with a database. It greatly improves the performance of database communications, and it provides the most flexibility during deployment.

8. Does Mainsoft for Java EE generate the Java EE application deployment descriptors?

   Yes. Mainsoft for Java EE generates the web.xml, portlet.xml (in portal applications), and the application server specific deployment descriptors that your Java EE administrator needs to deploy and maintain your application using Java EE administration tools.

9. How do I deploy a console application?

   Mainsoft for Java EE generates a script that you can use to run your console application outside your development environment.

Performance

1. Is the Java code produced by Mainsoft for Java EE optimized?

   Yes. Mainsoft for Java EE produces 100% Java-compliant code, which relies on the built-in Java Virtual Machine types. The application will perform similarly to code compiled from Java sources. The Mainsoft cross compiler has been optimized to reduce runtime type checking. It performs a static analysis to create the optimized code.

2. How can I tune my .NET code to reach optimal performance on Java EE?

   When porting from .NET to Java EE, you will need to tune your application to get the most from your Java EE infrastructure, which is architecturally different from the .NET infrastructure that your original application relied upon. For details, refer to Optimizing your .NET code in the online help.

3. Do you have any performance studies of ported applications?

   Yes. We've thoroughly tested a customer's composite application platform, written end-to-end in .NET on Java EE under Linux. At IBM's Chicago Innovation Labs, the ported application performed just as well as the original .NET application, in three user scenarios. Read the full Performance Study for details.