This page (revision-19) was last changed on 06-Sep-2012 15:54 by Dieter Käppel

This page was created on 12-Feb-2011 02:54 by Dieter Käppel

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
19 06-Sep-2012 15:54 7 KB Dieter Käppel to previous
18 06-Sep-2012 15:54 7 KB Dieter Käppel to previous | to last
17 26-Jun-2012 13:57 7 KB Dieter Käppel to previous | to last
16 09-May-2012 23:19 7 KB Dieter Käppel to previous | to last
15 09-May-2012 23:18 7 KB Dieter Käppel to previous | to last
14 11-Apr-2012 11:45 7 KB Dieter Käppel to previous | to last
13 11-Apr-2012 11:32 7 KB Dieter Käppel to previous | to last
12 11-Apr-2012 10:55 7 KB Dieter Käppel to previous | to last
11 22-Feb-2011 12:05 7 KB Dieter Käppel to previous | to last
10 14-Feb-2011 10:34 7 KB Dieter Käppel to previous | to last
9 14-Feb-2011 10:32 6 KB Dieter Käppel to previous | to last
8 14-Feb-2011 10:28 6 KB Dieter Käppel to previous | to last
7 14-Feb-2011 10:24 6 KB Dieter Käppel to previous | to last
6 14-Feb-2011 10:24 6 KB Dieter Käppel to previous | to last
5 13-Feb-2011 17:09 6 KB Dieter Käppel to previous | to last
4 13-Feb-2011 15:51 6 KB Dieter Käppel to previous | to last
3 12-Feb-2011 03:14 6 KB Dieter Käppel to previous | to last
2 12-Feb-2011 02:55 6 KB Dieter Käppel to previous | to last
1 12-Feb-2011 02:54 4 KB Dieter Käppel to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
Intersult Live is a product for live deployment of files.
Intersult Live is a very simple product for live mapping of workspace file into deployment. All is managed by slim live.xml configurations. Using maven build process, just copy the examples into your resource path without any changes.
At line 17 changed one line
!How it works
!Installation
At line 23 added one line
# Start your application server and live deployment will work
At line 78 changed one line
WAR:
WAR on Tomcat or JBoss:
At line 91 added 15 lines
WAR on Glassfish (only difference is JNDI-location):
{{{
<?xml version="1.0" encoding="UTF-8"?>
<live xmlns="http://intersult.com/live/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://intersult.com/live/1.0 http://repository.intersult.com/repository/com/intersult/live/1.0-SNAPSHOT/live.xsd">
<mapping source="${project.build.directory}/classes" target="/WEB-INF/classes"/>
<mapping source="${basedir}/src/main/webapp" target="/" loader="jndi:/server/${project.name}">
<exclude path="/META-INF*"/>
</mapping>
</live>
}}}
!Working with Development Environments
If you continue using Eclipse server plugin, you should mind to disable ''resource publishing''. Disabling this feature will prevent Eclipse to restart the application server.
At line 108 added 10 lines
!How it works
The key to live mapping is the live.xml defintion files. These files contains a few specifications, how Intersult Live will map workspace files to the deployment. The XML-File contains the following elements:
* __live:__ Every live.xml contains a <live> element as root definition
* __mapping:__ Each deployment-to-workspace-mapping is described by a <mapping> element
** source: The source attribute describes an absolute path in the system which is mapped into the deployment
** target: The target attribute describes a relative path to map the source into a deployment WAR, EAR or JAR
** loader: An optional attribute to specify a loader URL prefix. If no loader is specified, the URL prefix found while class loading is used. Usually, this is a file or JAR URL.
* __include/exclude:__ These elements are nested in <mapping> elements to specify inclusion or exclusion of files. Wildcards like ? and * can be used.