WebVM

Greetings from Guildford,

We are happy to announce a new WebVM SDK 0.9.3785 feature release.

New features

• WVMAttach has been extended to support API feature lists to support the new device capability and API feature mapping in WebVM
• JIDL has been updated in order to support doxygen XML output and OAMXML (OpenAjax Metadata Specification XML) input.
• JIDL has also been updated in order to generate XHTML output for given OAMXML input.

webvm.h changes

The prototype of WVMAttach has been extended as follows:

typedef struct _WVMFeature {
    const char *apiFeature;
    const char *deviceCap;
} WVMFeature;

WVMStatus WVMAttach(WVM              /* [in]  */  *instance,
            WVMCallbackFuncs /* [in]  */  *wvcFuncs,
            WVMModuleFuncs   /* [out] */ **wvmFuncs,
            const WVMFeature /* [out] */ **features);

features is a pointer to an array of WVMFeature structs describing the (BONDI security model) API features and device capabilities used by the module. A WVMFeature struct contains two pointers each to a 0-terminated string. Where a single API feature uses more than one device capability, it appears in that many WVMFeature structs in the array. A pointer to a particular WVMFeature struct in the array is then passed by the module to checkPermission, as the “feature” field in the WVMPermissionQuery struct

New JIDL features

In order to transform Java source files into OAMXML you need a recent doxygen version which supports generating XML-based doxygen dumps. These can be used as input format for JIDL in order to generate OAMXML interfaces. You don’t need a Java compiler anymore.

Synopsis for creating OAMXML from Java source files

1. Make sure you Doxyfile contains the following options:

   GENERATE_XML = YES

   XML_OUTPUT = xml

   XML_SCHEMA =

   XML_DTD =

   XML_PROGRAMLISTING = YES

2. Run doxygen on your Java sources.

3. Run jidl.jar on all class.xml and interfacexml files generated by doxygen, e.g.:

   java -jar jidl.jar output_directory classorg_1_1omtp_1_1bondi_1_1filesystem_1_1_file.xml classorg_1_1omtp_1_1bondi_1_1filesystem_1_1_file_stream.xml classorg_1_1omtp_1_1bondi_1_1filesystem_1_1_file_system_manager.xml interfaceorg_1_1omtp_1_1bondi_1_1filesystem_1_1_file_system_listener.xml

This will create a OAMXML file for each input file in output_directory.

Synopsis for creating XHTML output and C stubs from OAMXML input files

Just run JIDL on all your OAMXML files (note to list all files which depend on each other in a single JIDL run), eg.:

java -jar jidl.jar output_dir filesystem_File.xml filesystem_FileStream.xml filesystem_FileSystemManager.xml filesystem_FileSystemListener.xml

This will create C stub code and XHTML documentation based on these OAMXML files in output_dir.

You will find an example of such example output in the jidl directory of the SDK.

Known issues

• WVMError’s passed to callbacks are currently reported as error code only.
• Arrays of value types are still unsupported (not sure if we will support them).

You can re-use your WebVM SDK download URL from your mail Inbox or re-register at sdk.webvm.net.