Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Extending Eclipse Modeling Framework for DOM

IP.com Disclosure Number: IPCOM000167045D
Original Publication Date: 2008-Jan-30
Included in the Prior Art Database: 2008-Jan-30
Document File: 5 page(s) / 58K

Publishing Venue

IBM

Abstract

Disclosed is a mechanism for extending EMF/SDO to support DOM so that DOM related industry standard technologies can be applied to EMF/SDO based data, including XPath and XSLT. Therefore, WebSphere Business Integration doesn't need to maintain its own XPath interpreter which can only accept a very small portion of XPath specification. Furthermore, the proprietary Business Object Mapping can be potentially replaced with industry standard XSLT or some extension.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 60% of the total text.

Page 1 of 5

Extending Eclipse Modeling Framework for DOM

This disclosure extends org.eclipse.emf.ecore.EStructuralFeature.Setting (Fig. 1) from Eclipse Modeling Framework to NodeFeatureSetting.

Figure 1

1

[This page contains 1 picture or other non-text object]

Page 2 of 5

This invention correlates (Fig. 2) data structure between DOM and EMF/SDO:

Figure 2

2

[This page contains 1 picture or other non-text object]

Page 3 of 5

Now XSLT including XPath, can be applied to EMF/SDO based data:

Transformer boMap =

TransformerFactory.newInstance().newTransformer( new
StreamSource( "Clarify2SAP.map"));
boMap.transform( new DOMSource( clarifyBO1), new DOMResult(
sapBO1));
boMap.transform( new DOMSource( clarifyBO2), new DOMResult(
sapBO2));

A type itself is an instance of another type, too; therefore, it has syntax child nodes as above. On the other hand, the type defines properties, semantically, the properties are also child nodes to the type. Furthermore, annotations are child nodes to the type, too. This disclosure uses name space to distinguish the three sets of child nodes. e.g.

<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="TNS" xmlns:tns="TNS" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xmlns:meta="TypeMeta">

       <complexType name="ClarifyBO"
xsi:type="meta:BusinessObject" version="2">

                <annotation
xmlns:comment="AnnotationNamespace">

                        <appinfo
source="AnnotationNamespace">...

                        <documentation
source="AnnotationNamespace">...

ClarifyBO has a syntax child node qualified as meta:version, a semantic child node qualified as tns:id, and annotation child nodes qualified as comment:appinfo and comment:documentation.

Similarly, with enumerations and namespace:

<schema xmlns="http://www.w3.org/2001/XML...