Oxygen XML Author plugin 13.2.0

Author Developer Guide | 257Author ComponentThe Author Component was designed as a separate product to provide the functionality of the standard Author mode.The component can be embedded either in a third-party standalone Java application or customized as a Java Web Appletto provide WYSIWYG-like XML editing directly in your web browser of choice.The Author Component Startup Project for Java/Swing integrations is available online on the oXygen XML website:http://www.oxygenxml.com/demo/AuthorDemoApplet/author-component-sample.zipLicensingJust like the oXygen standard deployment, the Author component requires license information in order to run. Licensinginformation must follow the same models imposed for the standard oXygen application, namely the floating, named-userbased or group licenses.You can configure the component to:• Inject floating license server details in the Java code. You can license an Author component using standard oXygenXML Editor/Author floating license keys or special Author Component license keys. This is the recommendedmethod. Here are details to configure a floating license servlet or server:http://www.oxygenxml.com/license_server.html.• Inject the licensing information key directly in the component's Java code. This method MUST be used only whenyou have a site license or a special evaluation license (for development purposes) obtained by contacting our technicalsupport email address (support@oxygenxml.com).Warning: When the license key is injected set in the Author Component, only site and evaluation licensekeys can be used to license the component. Attempts to use other types of license will fail to initialize thecomponent.• Display the license registration dialog to the end user. This is the default behavior and transfers the licensingresponsibility to the end-user. The standard licensing procedure applies. You can license an Author component usingstandard oXygen XML Editor/Author license keys or special Author Component license keys. The license key willbe saved to the local user's disk and on subsequent runs the user will not be asked anymore.The most common use-case is when you as a developer customize the component and then want to deliver it to endusers (either embedded in a Java application or a Java Web applet). Your licensing options are:• named-user based model, where users provide their own oXygen license keys and register the component (paste itin the license registration dialog);