The Ephox EditLive! for Java ASP .NET Server Control has been designed to allow easy integration of the WYSIWYG HTML editing capabilities of EditLive! for Java into ASP.NET Web Forms. The EditLive! for Java ASP.NET Server Control has been designed to allow for seamless interaction between the ASP.NET architecture and the EditLive! for Java applet. Once the required files have been included in an ASP.NET Web project EditLive! for Java can be easily included in any of your ASP.NET Web Forms.
When using the EditLive! for Java ASP.NET Server Control there are several steps that must be followed. The server control file, EditLiveJavaControl.dll, must be installed in the relevant project. In addition to this the EditLive! for Java source files and libraries must be deployed on the same Web server as the relevant project. Finally, to provide IntelliSense (popup context menu) support for the EditLive! for Java Server Control in the HTML view of the Web Forms editor an XML schema file must be placed in a specific directory.
The EditLive! for Java Server Control may be added to the Microsoft Visual Studio .NET Toolbox to allow developers to create an instance of the EditLive! for Java Server Control on a page via the drag-and-drop mechanism. To use the EditLive! for Java Server Control in this manner the following steps must be followed:
When using the EditLive! for Java Server Control via the Microsoft Visual Studio .NET Toolbox, the relevant reference will automatically be added to the project when the first instance of the EditLive! for Java Server Control is created.
If the EditLive! for Java Server Control cannot be made available, or you do not wish to make it available, through the use of the Microsoft Visual Studio .NET Toolbox then a reference to it can be added directly to the project. To use the EditLive! for Java Server Control in this manner the following steps must be followed:
The EditLive! for Java Server Control is now available to reference from the project. Instances of the control can now be created using the tag associated with it.
This is no longer required. ASP.NET 2.0 and later can infer this information from the metadata in the EditLiveJavaControl.dll file.
In addition to including the EditLiveJavaControl.dll file in your ASP.NET project, either through the ASP.NET Toolbox or a project reference, the EditLive! for Java source files and libraries must be present on the same Web server as the relevant project. It is recommended that, in order to ensure that these files are present on the same Web server as the relevant project, that they be added to the project itself. These files can be found within the redistributables/editlivejava directory and its subdirectories.
As the Microsoft Visual Studio .NET IDE does not allow directories and their contents to be recursively added to a project the following method describes a way to easily add the EditLive! for Java source files and libraries to your .NET Web Project:
As EditLive! is an HTML editor, it will need to be able to edit HTML and send HTML text back to the server. This means that the .net request validation functionality will need to be disabled through setting the property validateRequest="false" in the page (through the Page directive: <%@ Page validateRequest="false" ...%>).
The server side code behind view exposes the EditLive! content through properties on the control. It is possible to access content at any stage in the life cycle through these attributes. Updates to content will only be visible in the control when they are made before rendering the applet. This means that content updated in the Page_Load event will be correctly reflected, but changes made in the event handlers for form events will not be reflected in the client control. In order to update content on a form event, the JavaScript APIs for EditLive! will need to be used.
In order to use multiple instances of EditLive! the "AppletName" of each control will need to be initialised in the Page_Load event. Each applet name should be set to a unique value, which can then be used to access content in the postbacks. A useful value for the applet name is the name of the control.