Service Editor

Introduction

We have property, wsdl, launch config, code generation, context menu ...etc in different places in the current service creation. I am hoping to have the service editor to mushup all functions related with service creation. That means, users can setup the code generation flags(such as namespace), endpoint address(defined in wsdl and code), policies(defined in wsdl), osgi bundles, assemble and deployment(defined in soas?) all within the one editor.

It is a multiple pages editor, which consists of following pages:

* service overview page (for service.xml file)
* service policy page (for policy.xml file, or wsdl file)
* service osgi page (for MANIFEST.MF file)
* service assemble page (for service.assemble file)
* service deploy.page (for service.deploy file)

Service Editor in detail

Service Overview Page

Screenshots

Policy Page

Screenshots

OSGI Page

The OSGI page is the place to configure OSGI dependencies and exports to support OSGI container. Those bundles are retrieved from user selected OSGI runtime.

File

/META-INF/MANIFEST.MF

We won's show the osgi page if the MANIFEST.MF file doesn't exists.

Screenshots

Assembly Page

This page allow user to select folders and files to be included in the generated deployable package. Users can also add extra libraries to the deployable package.

File

The output of this editor page is a service.assemble file. SOAS will create configurable logical package based on this assemble information. Package constructor extensions should use the configurable logical package if exists

Screenshots

Deploy Page

Screenshots