Open ESB supports Java EE platforms for GlassFish, JBoss, and the Sun Java Application Server Enterprise Edition. Check the release notes with each download to get the latest list of supported Java EE servers and operating platforms.

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.

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.

The specification, RI, and TCK insure that the Java Persistence API works with Java SE as well as with Java EE. Passing the TCK for the Java SE portion allows vendors to be compliant with the Java Persistence API without having a Java EE certification.

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:

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. 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.

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.

Yes. Open ESB is regularly tested to ensure conformance to the JBI specification. Milestone builds that have been validated will be identified on the Downloads page. Any other work in progress on the project site or in the CVS tree not identified as having passed the JBI validation tests will be considered out of conformance with the specification. Any derived work will also be considered not to be in conformance with the JBI specification. Yes.

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.

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

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.

Java Enterprise Edition (EE) is a standard for developing powerful sever-side applications using Java. It is meant for enterprise-level development. Note that JSP and other web related technologies are considered to be part of Java EE. See the tutorial for more information.

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.

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 a class library to be used in a Java IDE in the online help for details.

No. ChatLive121 incorporates technology that allows Web site visitors from various browser platforms to chat with an operator. However, the operator's browser must be JAVA compliant. Operators must use Netscape 4.x or Explorer 4.x - 5.x. Yes. ChatLive121 operates within a secure socket layer (SSL), which addresses the security concerns associated with online transactions.

If you answered yes to any of these questions, you need to evaluate whether GLUT is the right choice for your application. I need to set up different tasks for left and right mouse button motion. However, I can only set one glutMotionFunc() callback, which doesn't pass the button as a parameter. You can easily set up different tasks depending on the state of the SHIFT, ALT, and CTRL keys by checking their state with glutGetModifiers().

Since both of these are documents and not source code, there is no source to open! Thus, while we are open sourcing Sun's implementations of both, we cannot "open source" the Java programming language, nor the platform APIs and specifications, which are governed by the JCP.

We introduced the Java Persistence API to the Java platform for two reasons. First, this new API simplifies the development of Java EE and Java SE applications using data persistence. Second, we wanted to get the entire Java community behind a single, standard persistence API.

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

Everything you need to get started is in googleapi.jar. Advanced users may prefer to use their own Java SOAP implementations and use the WSDL file to generate client code.

The Java Platform is richer than its predecessors in functionality, performance, and security options. As a developer, you want the users of your software to have the most feature-complete Java platform possible so that the full range of APIs and libraries are available for your applications. If your customers are using the Java Platform, you can write more powerful, robust, and full-featured applications and applets. And with the Java Platform the performance of your code will be better too.

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. No. You can continue using Visual Studio to create Windows applications as you always have.

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. No. System administrators can install and manage applications created with Mainsoft for Java EE as standard Java EE applications.

The Java 2 Platform, Enterprise Edition (J2EE) is a set of coordinated specifications and practices that together enable solutions for developing, deploying, and managing multi-tier server-centric applications. Building on the Java 2 Platform, Standard Edition (J2SE), the J2EE platform adds the capabilities necessary to provide a complete, stable, secure, and fast Java platform to the enterprise level.

Because the Java Foundation Classes are designed to be truly cross-platform, they run equally well on all Java Compatible Platforms.

Mainsoft's QA team uses standard, commercial, and proprietary test suites as well as real world integrative applications comprised of 4.7 million lines of code 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. Finally, we've designed Mainsoft for Java EE to be self-hosted. The .

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.

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. A Visual Studio plug-in that seamlessly integrates Mainsoft for Java EE extends the IDE functionalities cross-platform. The Mono .NET Framework is rehosted on top of the Java EE infrastructures, allowing you to port .NET applications to Java EE.

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. Mainsoft for Java EE focuses exclusively on Web and server applications, while Mono also supports desktop applications, with Gtk# and Windows.Forms.

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.