Deploy new forms and PIPAs

Deploy new components

We've deprecated WDS-Client in favor of a more general, unified deployment service. With the deployment service, you can deploy either via WS or directly through the file system.

The deployment service accepts "assemblies". An assembly is a packaging of one or more component, each being a sub-directory of the assembly.

e.g.

MyAssembly\
   MyComponent1.type1\
   MyComponent2.type2\
   ...

The sub-directory extension represents the component type (e.g. "xform", "pipa", ...).

Assemblies deployed directly on the file system under var\deploy, or are zipped (without the top-level directory) and deployed through the deployment WebService.

To deploy XForms, you would create an assembly that looks like:

MyAssembly\
  MyForms.xform\
    ... any .xform files here ...
  MyPIPA.pipa\
    ... place .pipa descriptors here...

There's an example of this in SVN at http://www.intalio.org/tempo/trunk/forms/AbsenceRequest/src/main/

.
|-- AbsenceRequest
|   |-- AbsenceRequest.pipa
|   |   `-- AbsenceRequest
|   |       `-- AbsenceRequest.pipa
|   `-- AbsenceRequest.xform
|       `-- AbsenceRequest
|           |-- AbsenceApproval.xform
|           |-- AbsenceApproval.xform.xsd
|           |-- AbsenceRequest.xform
|           |-- AbsenceRequest.xform.xsd
|           |-- Notification.xform
|           `-- Notification.xform.xsd

The file are packaged during the build to obtain:

boisvert@boog:~/svn/tempo/trunk/forms/AbsenceRequest$ unzip -l target/tempo-forms-AbsenceRequest-5.2.1.4-SNAPSHOT.zip 
Archive:  target/tempo-forms-AbsenceRequest-5.2.1.4-SNAPSHOT.zip
  Length     Date   Time    Name
 --------    ----   ----    ----
        0  10-03-08 08:15   AbsenceRequest.pipa/
        0  10-03-08 08:15   AbsenceRequest.pipa/AbsenceRequest/
      490  10-03-08 08:15   AbsenceRequest.pipa/AbsenceRequest/AbsenceRequest.pipa
        0  10-03-08 08:15   AbsenceRequest.xform/
        0  10-03-08 08:15   AbsenceRequest.xform/AbsenceRequest/
     8806  10-03-08 08:15   AbsenceRequest.xform/AbsenceRequest/AbsenceApproval.xform
     3123  10-03-08 08:15   AbsenceRequest.xform/AbsenceRequest/AbsenceApproval.xform.xsd
    11325  10-03-08 08:15   AbsenceRequest.xform/AbsenceRequest/AbsenceRequest.xform
     3061  10-03-08 08:15   AbsenceRequest.xform/AbsenceRequest/AbsenceRequest.xform.xsd
     4233  10-03-08 08:15   AbsenceRequest.xform/AbsenceRequest/Notification.xform
     1753  10-03-08 08:15   AbsenceRequest.xform/AbsenceRequest/Notification.xform.xsd
 --------                   -------

If the component is properly deployed, it will appear with a .deployed extension, like this:

|-- AbsenceRequest.deployed

The deploy service in tempo is working on a really similar model as the one used in Apache Ode. In fact, we are planning into merging both of them in the near future.