Skip to main content
Jump to: navigation, search

Difference between revisions of "STP/XEF XML Framework"

< STP
(New page: {| border="0" cellspacing="15" valign="top" style="width:100%;" |-valign="top" |style="width:50%;"| <h1>Proposal</h1> The main idea of this proposal is to expose XEF editor in more gene...)
 
Line 19: Line 19:
  
 
<h1>Draft Interface Proposal</h1>
 
<h1>Draft Interface Proposal</h1>
 +
Draft proposal of two interfaces is represented bellow. The IXEFFramework is public interface of framework. IXEFCallback should be implemented by framework consumer to receive notifications.
 +
 +
[[Image:XEF_Framework_ClassDiagram.JPG]]
 +
 
|}
 
|}

Revision as of 16:58, 30 December 2008

Proposal

The main idea of this proposal is to expose XEF editor in more generic way: as XML framework. GUI representation of XML schema is very common task, required by the number of applications and Eclipse projects. So intention is to make XEF usable not only in context of policy editor, but also for many another scenarios like:

  • representation of WSDL for WS invocation
  • generation of test WS requests
  • editing XML-based configuration, descriptors
  • etc

This proposal also will be very helpful to redesign Policy Editor regarding UI Walkthrough [Policy Editor UI Walkthrough].

Using of XEF Framework

XEF Framework provides well defined public interface. Components and applications will use XEF Framework in different contexts and scenarios via this interface. Policy Editor can use XEF Framework directly or via XEF Editor.

XEF Framework.JPG


Draft Interface Proposal

Draft proposal of two interfaces is represented bellow. The IXEFFramework is public interface of framework. IXEFCallback should be implemented by framework consumer to receive notifications.

XEF Framework ClassDiagram.JPG

Copyright © Eclipse Foundation, Inc. All Rights Reserved.