Abstract:
An application framework for composing applications involving a plurality of webservices. The application framework comprises: 1) a layout editor adapted to create a graphical user interface of an application comprising a plurality of pages, each page comprising at least one element for interaction with a user to generate or modify a set of data; 2) a control layer editor, adapted to create for each page of the graphical user interface a corresponding code fragment receiving and processing the set of data relating to the respective page; and 3) a generator generating an orchestration sequence from the plurality of code fragments, wherein the processing of the orchestration sequence by an engine involves the invoking of the plurality of webservices.

Description:
PRIORITY CLAIM  
       [0001]     This application claims benefit of priority of European application no. EP 06003964.1 titled “Application Framework”, filed Feb. 27, 2006, and whose inventors are Kay Winkler, Christine Zimmermann, Udo Hafermann, Bjorn Mueller and Jurgen Harbarth.  
       INCORPORATED BY REFERENCE  
       [0002]     European application no. EP 06003964.1 titled “Application Framework”, filed Feb. 27, 2006, and whose inventors are Kay Winkler, Christine Zimmermann, Udo Hafermann, Bjorn Mueller and Jurgen Harbarth, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.  
       TECHNICAL FIELD  
       [0003]     The present invention relates to an application framework for composing applications involving a plurality of webservices.  
       THE PRIOR ART  
       [0004]     Webservices are nowadays standardized interfaces for exchanging data over the internet An application of a client may request data from a server over the internet using a webservice provided by a server. More technically advanced applications typically combine various webservices to obtain or process the desired data, for example to provide and to modify information concerning a business operation. An application developer must provide both a user interface and the application logic, so that a user can interact with the application and that the application performs the desired processing of the data based on the various webservices involved.  
         [0005]     However, the application logic and also the user interface of such a composite application often need to be quickly changed, for example if changing business operations are to be reflected by the application. Low-level programming of the changed application logic and/or a changed user interface in a typical programming language such as JAVA is time consuming and difficult. Therefore, there are approaches in the prior art, how applications using webservices can be more efficiently created or modified.  
         [0006]     One approach is the Business Process Execution Language (BPEL) as it is for example described in the publication on p. 34 of the 6. edition 2006 of the magazine “Computerwoche”. BPEL allows to flexibly provide or change application logic which processes data involving a plurality of webservices.  
         [0007]     However, applicant has found that the task of quickly creating or adapting an application involving webservices requires more than quickly adapting the application logic alone. The user interface, i.e. the possibilities of data input or output also needs to be quickly modified. In the prior art it is generally known, how to quickly generate or change graphical used interfaces, for examples by graphically selecting and positioning user control elements such as check boxes or lists etc. In application frameworks according to the prior art, the data generated by the user interface at first needs to be processed by some intermediate code in order to bring it into a format, which is suitable to interact with BPEL. Changing the user interface and/or the application logic therefore still needs low-level programming in order to assure that an application logic modified using BPEL and the user interface can still work together.  
         [0008]     It is therefore the technical problem to provide an application framework, which allows to flexibly generate and/or to modify applications involving webservices with a reduced amount of low-level programming, to reduce development time and the involved risk of programming errors.  
       SUMMARY OF THE INVENTION  
       [0009]     This problem is solved by an application framework for composing applications involving a plurality of webservices. The application framework comprises 
        a layout editor adapted to create a graphical user interface of an application comprising a plurality of pages, each page comprising at least one element for interaction with a user to generate or modify a set of data,     a control layer editor, adapted to create for each page of the graphical user interface a corresponding code fragment receiving and processing the set of data relating to the respective page and     a generator generating an orchestration sequence from the plurality of code fragments, wherein the processing of the orchestration sequence by an engine involves the invoking of the plurality of webservices.        
 
         [0013]     The close relationship between the graphical user interface created in the layout editor and the processing logic created by the control editor of the invention allows the generation or modification of an application without programming in low-level languages such as Java, C#, etc. for processing the data received by the user interface. In particular, the feature of providing for each page of the graphical user interface a corresponding code fragment significantly facilitates the tasks of a developer, when adapting the user interface and/or the application logic of an existing application to changing requirements.  
         [0014]     The generator is responsible for generating a single orchestration sequence out of the various code fragments. The sequence can then at runtime be processed by an engine, which for example directly interprets the sequence or transforms it into an executable format such as a JAVA class.  
         [0015]     In a preferred embodiment, the application framework is further adapted to create each code fragment such that it receives the set of data via a webservice interface, wherein the definition for this interface comprises preferably an XML schema definition (XSD) of the set of data and at least one function called by the respective page, in particular a web service definition (WSDL). Particularly preferred is an embodiment, wherein the application framework is further adapted to automatically derive the XSD and at least one WSDL for each page created in the layout editor. As a result, the interface definition is effectively driven by the page, which is defined independently from the application logic and defines only its interface of data and functions it requires to talk to the application logic.  
         [0016]     In one embodiment of the invention, the control layer editor is adapted to create the code fragments as fragments implemented in Business Process Execution Language (BPEL) and wherein the orchestration sequence is a BPEL sequence, which can be processed by a BPEL engine. BPEL is standardized, platform independent and specifically designed to orchestrate Web services. Another advantage is that is can process XML documents as variables. Furthermore, it is compared to the above mentioned low-level, pointer based programming languages easy to use and can at least for simple scenarios be visualized as a flow chart diagram. However, whereas BPEL is presently preferred for implementing the code fragments of the invention, other languages could be used as well such as a .NET implementation, a NATURAL implementation etc.  
         [0017]     According to a further aspect of the present invention, each code fragment comprises preferably a plurality of method fragments, wherein each method fragment corresponds to a function call generated on the respective page of the graphical user interface. This is a further preferred feature, which additionally facilitates to develop structured code fragments for the application logic corresponding to each page of the user interface.  
         [0018]     Finally, the processing of the orchestration sequence of an application composed by the application framework comprises preferably holding the state of an object and processing the state based on the operations defined in one or more code fragments. The processing of the state comprises preferably transforming the object into a format suitable for a webservice, executing the webservice and transforming the response of the webservice back into an initial format of the object. In one embodiment of the invention the object comprises XML data conforming to an XSD and the transforming is performed using XSLT encapsulated as a webservice. The encapsulation as a webservice is particularly preferred, if BPEL fragments are used as code fragments, since BPEL itself does presently not provide a concept of nesting one sequence inside another.  
         [0019]     Further improvements of the described application framework are the subject matter of further dependent claims.  
         [0020]     In addition, the present invention concerns a method using the above explained application framework, an application composed by the above described application framework and a data carrier comprising the above described application framework. 
     
    
     SHORT DESCRIPTION OF THE DRAWINGS  
       [0021]     In the following detailed description presently preferred embodiments of the invention are further described with reference to the following figures:  
         [0022]      FIG. 1 : A schematic representation of the various pages of a graphical user interface;  
         [0023]      FIG. 2 : A schematic representation of a single page comprising a plurality of control elements for interaction with a user;  
         [0024]      FIG. 3 : A schematic representation of the general relation between a graphical user interface, the application logic and the involved webservices;  
         [0025]      FIG. 4 : A schematic representation of the set of data and functions automatically derived from a layout definition of a page in a preferred embodiment of the invention;  
         [0026]      FIG. 5 : An example of an actual page of the graphical user interface of the invention;  
         [0027]      FIG. 6 : A schematic representation of the preferred 1:1 relation between pages of the graphical user interface and the BPEL code fragments;  
         [0028]      FIG. 7 : A schematic representation of the generator generating a BPEL program from a plurality of BPEL fragments.  
         [0029]      FIG. 8 : A schematic representation of the internal and external structure of a BPEL fragment in a preferred embodiment of the invention; and  
         [0030]      FIG. 9 : A schematic representation of the internal and external structure of a BPEL fragment in another preferred embodiment of the invention; 
     
    
     DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS  
       [0031]     In the following, the mapping of a user interface to webservice processing, as it is performed by an embodiment of the application framework of the present invention, will be explained in a first section. The preferred implementation of the webservice processing itself using BPEL fragments is discussed in a further section below.  
         [0032]     A graphical user interface of an application composed with an embodiment of the application framework of the invention is separated into pages  10 , as they are exemplary shown in  FIG. 1 . Each page  10  is representing a certain amount of data and functions that are presented to the user at runtime. Between pages  10  there is a page navigation which typically includes: 
    Following a sequence of pages (cf. the arrows in  FIG. 1 )     Opening pages as modal/modeless popup     Nesting of pages (cf. page  5  nested in page  4  of  FIG. 1 )    
 
         [0036]     The page  10  is typically representing some dedicated, self containing application task that needs to be operated by the user. The definition of this application task is up to the page&#39;s designer/developer. The page  10  is internally structured into controls  11 . Controls  11  are representing preferably reusable components that represent a certain piece of data (e.g. input field) and/or a certain behavior (e.g. button).  
         [0037]     The coupling of a page&#39;s processing to its corresponding application logic operates generally as follows (cf.  FIG. 3 ): 
        The page  10  is representing a certain amount of data and functions. The page&#39;s task is to visualize this data using controls  11  and to communicate changes to this data (e.g. user input into field) or function calls (e.g. a user presses a button) to the application logic  20  of the application.     The layout of the page  10  is defined by a layout definition in the layout editor. The layout definition holds the information which control  11  is used inside the page  10 .     Inside the layout definition each control  11  is specified with its optical attributes (e.g. colour, position) and with its binding attributes. The binding attributes define which part of the page&#39;s data is required/accessed by the corresponding control  11  and/or which function is called by the corresponding control.        
 
         [0041]      FIG. 3  schematically reflects the standard processing of inputs of a user of an application involving webservices  30 . A page  10  requests at runtime its data from the application logic  20  and presents this data to the user. The user manipulates the data, for example by doing inputs (not shown). At certain synchronization-relevant points of time (e.g. pressing a button) the updated page&#39;s data is sent back to the application logic  20  together with the information of which function to process. The application logic  20  receives the manipulated page data, processes it (e.g. does some calculation involving one or more webservices  30 ) and sends the updated data back to the page  10 . The page  10  receives this updated data, updates its controls  11  so that the data that is visualized is adjusted.  
         [0042]     In application frameworks of the prior art, the communication between the pages  10  of the graphical user interface and the application logic  20  is typically provided by a separate intermediate layer (not shown in  FIG. 3 ) arranged between the user interface and the application logic. Using low-level programming, the input of a user at the user interface is read out by the intermediate layer and forwarded to the application logic. Whenever at least one end of this communication changes, i.e. any of the controls  11  of the pages  10  of the user interface and/or the application logic  20 , the low-level programming of the intermediate layer needs to be repeated. This is time consuming and may cause errors in the overall data processing.  
         [0043]     In order to overcome these disadvantages, the described embodiment of the present invention technically and semantically decouples the page processing from the application logic  20 . Accordingly, an embodiment of the present invention provides a program interface definition between a page  10  and the application logic  20  (cf.  FIG. 4 ). This interface definition contains: 
        The schema definition of the data of the page  10  that is exchanged every time the page synchronizes its data with the corresponding application logic (not shown in  FIG. 4 ).     The list of functions that is called by the page  10 —associated with a data synchronization.        
 
         [0046]     In a preferred embodiment, webservice interfaces are used as a concrete implementation. As a consequence for each page, the following definitions are automatically derived from the page&#39;s layout (cf.  FIG. 4 ): 
        The XML schema  41  of the page&#39;s data. This XML schema presents a “net data structure” of the respective page  10 .     The webservice definition  42  of the webservice that is expected to be made available by the application logic  20 .        
 
         [0049]     It is important to point out that the program interface definition is driven by the page  10 . In the described embodiment of the invention a page is defined substantially independently from the application logic  20  and defines only its interface of data and functions that are requires to communicate with the application logic  20 .  
       EXAMPLE  
       [0050]     The following page is defined as the page shown in  FIG. 5  to view some article data. The page layout (using “Application Designer”) is defined as:  
                                   &lt;?xml version=“1.0” encoding=“UTF-8”?&gt;       &lt;xcipage xciname=“test”&gt;        &lt;xcisetup&gt;         &lt;xciparameter paramname=“test” paramtype=“xs:string”&gt;         &lt;/xciparameter&gt;        &lt;/xcisetup&gt;        &lt;titlebar name=“Article Browser”&gt;        &lt;/titlebar&gt;        &lt;header withdistance=“false”&gt;         &lt;button name=“Save” method=“onSave”&gt;         &lt;/button&gt;        &lt;/header&gt;        &lt;pagebody&gt;         &lt;rowarea name=“Article Selection”&gt;          &lt;itr&gt;           &lt;label name=“Article Id” width=“120”&gt;           &lt;/label&gt;           &lt;field valueprop=“articleid” width=“200”&gt;           &lt;/field&gt;           &lt;hdist width=“10”&gt;           &lt;/hdist&gt;           &lt;button name=“Read” method=“onRead”&gt;           &lt;/button&gt;          &lt;/itr&gt;         &lt;/rowarea&gt;         &lt;rowarea name=“Article Details”&gt;          &lt;itr takefullwidth=“true”&gt;           &lt;label name=“Description” width=“120”&gt;           &lt;/label&gt;           &lt;field valueprop=“description” width=“100%”           displayonly=“true”&gt;           &lt;/field&gt;          &lt;/itr&gt;          &lt;itr&gt;           &lt;label name=“Type” width=“120”&gt;           &lt;/label&gt;           &lt;field valueprop=“type” width=“200” displayonly=“true”&gt;           &lt;/field&gt;          &lt;/itr&gt;         &lt;/rowarea&gt;         &lt;rowarea name=“List of Suppliers”&gt;          &lt;itr takefullwidth=“true”&gt;           &lt;textgridsss2 griddataprop=“suppliers” rowcount=“10”       width=“100%” selectprop=“selected” hscroll=“true”       directselectmethod=“onSelect” directselectevent=“ondblclick”&gt;            &lt;column name=“Id” property=“supplierid” width=“100”&gt;            &lt;/column&gt;            &lt;column name=“Name” property=“name” width=“50%”&gt;            &lt;/column&gt;            &lt;column name=“Description” property=“description”            width=“50%”&gt;            &lt;/column&gt;           &lt;/textgridsss2&gt;          &lt;/itr&gt;         &lt;/rowarea&gt;        &lt;/pagebody&gt;        &lt;statusbar withdistance=“false”&gt;        &lt;/statusbar&gt;       &lt;/xcipage&gt;                  
 
         [0051]     Inside the page layout certain controls define their binding to some data:  
       Example 1  
       [0052]    
       
         
               
               
             
           
               
                   
                   
               
               
                   
                   
               
             
             
               
                   
                 &lt;field valueprop=“description” width=“100%” displayonly=“true”&gt; 
               
               
                   
                 &lt;/field&gt; 
               
               
                   
                   
               
             
          
         
       
     
         [0053]     The field expects a data element “description” to be available.  
       Example 2  
       [0054]    
       
         
               
             
           
               
                   
               
               
                   
               
             
             
               
                  &lt;textgridsss2 griddataprop=“suppliers” rowcount=“10” width=“100%” 
               
               
                 selectprop=“selected” hscroll=“true” directselectmethod=“onSelect” 
               
               
                 directselectevent=“ondblclick”&gt; 
               
               
                   &lt;column name=“Id” property=“supplierid” width=“100”&gt; 
               
               
                   &lt;/column&gt; 
               
               
                   &lt;column name=“Name” property=“name” width=“50%”&gt; 
               
               
                   &lt;/column&gt; 
               
               
                   &lt;column name=“Description” property=“description” width=“50%”&gt; 
               
               
                   &lt;/column&gt; 
               
               
                  &lt;/textgridsss2&gt; 
               
               
                   
               
             
          
         
       
     
         [0055]     The grid expects a list of suppliers to be available. For each supplier the “supplierid”, “name” and “description” is expected to be available. Out of the page the following XML schema definition is created:  
                                   &lt;?xml version=“1.0”?&gt;       &lt;xs:schema xmlns:xs=“http://www.w3.org/2001/XMLSchema”       xmlns:pg=“http://www.softwareag.com/xci/test/test”       targetNamespace=“http://www.softwareag.com/xci/test/test”       elementFormDefault=“qualified”&gt;        &lt;xs:simpleType name=“methodType”&gt;         &lt;xs:restriction base=“xs:string”&gt;          &lt;xs:enumeration value=“xcilnit”&gt;          &lt;/xs:enumeration&gt;          &lt;xs:enumeration value=“onSave”&gt;          &lt;/xs:enumeration&gt;          &lt;xs:enumeration value=“onRead”&gt;          &lt;/xs:enumeration&gt;          &lt;xs:enumeration value=“onSelect”&gt;          &lt;/xs:enumeration&gt;         &lt;/xs:restriction&gt;        &lt;/xs:simpleType&gt;        &lt;xs:complexType name=“dataType”&gt;         &lt;xs:sequence&gt;          &lt;xs:element name=“xciParameters” minOccurs=“0”&gt;           &lt;xs:complexType&gt;            &lt;xs:sequence&gt;             &lt;xs:element name=“test” type=“xs:string” minOccurs=“0”&gt;             &lt;/xs:element&gt;            &lt;/xs:sequence&gt;           &lt;/xs:complexType&gt;          &lt;/xs:element&gt;          &lt;xs:element name=“suppliers” minOccurs=“0”          maxOccurs=“unbounded”&gt;           &lt;xs:complexType&gt;            &lt;xs:sequence&gt;             &lt;xs:element name=“selected” type=“xs:string”             minOccurs=“0”&gt;             &lt;/xs:element&gt;             &lt;xs:element name=“supplierid” type=“xs:string”             minOccurs=“0”&gt;             &lt;/xs:element&gt;             &lt;xs:element name=“name” type=“xs:string”             minOccurs=“0”&gt;             &lt;/xs:element&gt;             &lt;xs:element name=“description” type=“xs:string”             minOccurs=“0”&gt;             &lt;/xs:element&gt;            &lt;/xs:sequence&gt;           &lt;/xs:complexType&gt;          &lt;/xs:element&gt;          &lt;xs:element name=“articleid” type=“xs:string” minOccurs=“0”&gt;          &lt;/xs:element&gt;          &lt;xs:element name=“description” type=“xs:string” minOccurs=“0”&gt;          &lt;/xs:element&gt;          &lt;xs:element name=“type” type=“xs:string” minOccurs=“0”&gt;          &lt;/xs:element&gt;         &lt;/xs:sequence&gt;        &lt;/xs:complexType&gt;       &lt;/xs:schema&gt;                  
 
         [0056]     Part of the schema definition is the data that is required by the controls  11  and the list of functions that is called from the controls. The web service definition is:  
                                   &lt;?xml version=“1.0” encoding=“UTF-8”?&gt;       &lt;definitions name=“test”        targetNamespace=“http://www.softwareag.com/xci/test/test”        xmlns=“http://schemas.xmlsoap.org/wsdl/”        xmlns:http=“http://schemas.xmlsoap.org/wsdl/http/”        xmlns:mime=“http://schemas.xmlsoap.org/wsdl/mime/”        xmlns:soap=“http://schemas.xmlsoap.org/wsdl/soap/”        xmlns:soapenc=“http://schemas.xmlsoap.org/soap/encoding/”        xmlns:tns=“http://www.softwareag.com/xci/test/test”        xmlns:xs=“http://www.w3.org/2001/XMLSchema”&gt;        &lt;types&gt;         &lt;xs:schema elementFormDefault=“qualified”          targetNamespace=“http://www.softwareag.com/xci/test/test”          xmlns:pg=“http://www.softwareag.com/xci/test/test”          xmlns:ht=“http://www.softwareag.com/xciHeaderTrailer”          xmlns:xs=“http://www.w3.org/2001/XMLSchema”&gt;          &lt;xs:import           namespace=“http://www.softwareag.com/xci/xciHeaderTrailer”           schemaLocation=“xciHeaderTrailer.xsd” /&gt;          &lt;xs:simpleType name=“methodType”&gt;           &lt;xs:restriction base=“xs:string”&gt;            &lt;xs:enumeration value=“xcilnit”&gt;&lt;/xs:enumeration&gt;            &lt;xs:enumeration value=“onSave”&gt;&lt;/xs:enumeration&gt;            &lt;xs:enumeration value=“onRead”&gt;&lt;/xs:enumeration&gt;            &lt;xs:enumeration value=“onSelect”&gt;&lt;/xs:enumeration&gt;           &lt;/xs:restriction&gt;          &lt;/xs:simpleType&gt;          &lt;xs:complexType name=“dataType”&gt;           &lt;xs:sequence&gt;            &lt;xs:element name=“xciParameters” minOccurs=“0”&gt;             &lt;xs:complexType&gt;              &lt;xs:sequence&gt;               &lt;xs:element name=“test” type=“xs:string”                minOccurs=“0”&gt;               &lt;/xs:element&gt;              &lt;/xs:sequence&gt;            &lt;/xs:complexType&gt;           &lt;/xs:element&gt;           &lt;xs:element name=“suppliers” minOccurs=“0”            maxOccurs=“unbounded”&gt;            &lt;xs:complexType&gt;             &lt;xs:sequence&gt;              &lt;xs:element name=“selected”               type=“xs:string” minOccurs=“0”&gt;              &lt;/xs:element&gt;              &lt;xs:element name=“supplierid”               type=“xs:string” minOccurs=“0”&gt;              &lt;/xs:element&gt;              &lt;xs:element name=“name” type=“xs:string”               minOccurs=“0”&gt;              &lt;/xs:element&gt;              &lt;xs:element name=“description”               type=“xs:string” minOccurs=“0”&gt;              &lt;/xs:element&gt;             &lt;/xs:sequence&gt;            &lt;/xs:complexType&gt;           &lt;/xs:element&gt;           &lt;xs:element name=“xMLDataMode” type=“xs:string”            minOccurs=“0”&gt;           &lt;/xs:element&gt;           &lt;xs:element name=“articleid” type=“xs:string”            minOccurs=“0”&gt;           &lt;/xs:element&gt;           &lt;xs:element name=“description” type=“xs:string”            minOccurs=“0”&gt;           &lt;/xs:element&gt;           &lt;xs:element name=“type” type=“xs:string”            minOccurs=“0”&gt;           &lt;/xs:element&gt;          &lt;/xs:sequence&gt;         &lt;/xs:complexType&gt;         &lt;xs:element name=“xdo”&gt;          &lt;xs:complexType&gt;           &lt;xs:sequence&gt;            &lt;xs:element ref=“ht:header” /&gt;            &lt;xs:element name=“data” type=“pg:dataType” /&gt;            &lt;xs:element ref=“ht:trailer” /&gt;           &lt;/xs:sequence&gt;          &lt;/xs:complexType&gt;         &lt;/xs:element&gt;        &lt;/xs:schema&gt;       &lt;/types&gt;       &lt;message name=“xdo”&gt;        &lt;part element=“tns:xdo” name=“xdo” /&gt;       &lt;/message&gt;        &lt;portType name=“test”&gt;         &lt;operation name=“doProcess”&gt;          &lt;input message=“tns:xdo” /&gt;          &lt;output message=“tns:xdo” /&gt;         &lt;/operation&gt;        &lt;/portType&gt;       &lt;/definitions&gt;                  
 
         [0057]     This exemplary webservice contains one operation “doprocess” which is expected to be implemented by the application logic  20 . The in/out parameter of this operation is the XML document representing the page&#39;s data and the function that is invoked by the page processing.  
         [0058]     In the following, the implementation of the application logic  20  using BPEL in a preferred embodiment of the invention is described in more detail.  
         [0059]     As can be seen above, the application user interface created by the layout editor is separated into pages  10 , wherein each page  10  covers a certain amount of data and functions that are represented to the user. Further, there is a navigation between different pages  10  (e.g. to put them into a certain sequence), as mentioned above. Each page  10  is related to a webservice that is associated with the page&#39;s data and functions and which needs to be provided by the application logic  20 .  
         [0060]     The presently preferred embodiment of the invention uses BPEL as a general purpose programming language for implementing the application logic  20 . Using BPEL can be drastically simplified by applying the following principles in accordance with a preferred embodiment of the invention (cf.  FIG. 6 ): 
        Each page  10  is represented by a so called BPEL fragment  50 , wherein the fragment is taking care of processing the data and the functions of the respective page  10 .     BPEL Fragments  50  are preferably isolated from one another so that its corresponding data is not visible to other BPEL fragments.     It is possible to share an explicitly defined application context which is defined as a cross-segment.        
 
         [0064]     A generator  100  (cf.  FIG. 7 ) of the application framework in accordance with an embodiment of the invention is responsible for generating a single comprehensive BPEL sequence  80  out of the plurality of BPEL fragments  50 . Each BPEL fragment  50  contains the BPEL code for the fragment and the webservice definition that is implemented by the fragment. The finally generated BPEL sequence  80  serves as a program, which can at runtime be deployed to any BPEL engine  110  that conforms to the BPEL specifications.  
         [0065]     Inside one BPEL fragment  50  (representing the application logic for one page  10 ) the following structure is preferably applied (cf.  FIG. 8 ): 
        The XML representation  41  of the page&#39;s data content is made available by a predefined BPEL variable, which is called “xciState” in one embodiment.     It is possible to define one or more additional fragment-specific variables  45  that are not directly related to the page&#39;s data and which influence the application logic provided by the BPEL fragment  50 .     Each reaction on a user interface call is reflected by the definition of a method fragment  51 —containing the BPEL code that is responsible for processing this specific call. Any kind of BPEL code can be applied within such a method fragment.     Inside the BPEL code of the method calls  51 , the page&#39;s data can be accessed and manipulated.        
 
         [0070]     A request that is sent from a page is automatically processed in the following way: 
        (1) The request is received by the overall BPEL sequence  80 .     (2) The right BPEL fragment  50  is selected for processing.     (3) The variable “xciState” is filled with the page&#39;s data that comes with the request.     (4) The right method fragment  51  is selected for processing.     (5) The method is executed, which may involve one or more webservices  30 . The page&#39;s data may be updated.     (6) The updated page&#39;s data is sent back within the response.        
 
         [0077]     Only step (5) is visible to the BPEL developer—all other steps are generated automatically by the generator.  
         [0078]     In addition, a set of default method fragments is available for each BPEL fragment  50  (cf.  FIG. 9 ): 
        xcilnit  52 : This method fragment is called when the BPEL fragment  50  is used for the first time at runtime. Any kind of fragment specific initialization can be executed.     xciSetup  53 : This method fragment is called when the page  10  is called as result of page navigation. As part of the navigation the corresponding BPEL fragment received information what data to load for the corresponding page  10 .     xciPreMethod  54 /xciPostMethod  55 : These methods are called before/after calling any other method fragment  50 .        
 
         [0082]     As mentioned in the introductory part, BPEL is designed to orchestrate web services, such as the webservices  30  shown in  FIG. 3 . As a result, if a certain user interface consists of several pages  10 , the resulting BPEL sequence  80  obtained from the various BPEL fragments  50  will be quite long. The present invention therefore provides in one embodiment an application framework which makes BPEL effectively usable. One aspect thereof is to make BPEL “Stateful/Object aware”:  
         [0083]     A state reflects a status of a set of data such as the net data object of the XML data  41  shown in  FIGS. 4, 8  and  9 . Such a state is kept for a certain duration. For example, the net data of a screen is kept for the duration the screen is processed (or maybe longer).  
         [0084]     Diverse operations are available to update this state. For example, data is input into a screen or a certain operation is triggered to run in BPEL manipulating the net data object possibly including one of the webservices  30  (cf.  FIG. 3 ). The state is the central part that is referred to by all operations. Therefore, the diverse functions that are triggered by the user interface call may concern different parts of the overall BPEL sequence  80 . However, they always lead to the following processing steps: 
    (a) receiving of a net data object,     (b) operating on the net data object,     (c) responding the net data object    
 
         [0088]     For example, a call to any of the webservices  30  inside the BPEL sequence  80  for a certain screen is done in the following sequence: 
    (a) take data from net data object and transform this data into a structure that is adequate to the webservice  30 ,     (b) call the webservice  30 ,     (c) transform the response of the webservice  30  back into the net data object.    
 
         [0092]     The transformation is done using XSLT. Because XSLT is not supported as native BPEL statement it has to be encapsulated by a corresponding web service. A tool can generate all these parts to form a valid BPEL sequence  80 .  
       EXAMPLE  
       [0093]     The following BPEL fragments represent the processing of two pages:  
                                   First page “address”, holding the methods “xciInit” and “onCheck”:       &lt;?xml version=“1.0” encoding=“UTF-8”?&gt;       &lt;xci:bpelo xmlns:xci=“http://www.softwareag.com/xci/”        xmlns=“http://schemas.xmlsoap.org/ws/2003/03/business-process/”        xmlns:ht=“http://www.softwareag.com/xci/xciHeaderTrailer”        xmlns:xo=“http://www.softwareag.com/xci/wt/address” name=“address”        targetNamespace=“http://www.softwareag.com/xci/wt/address”&gt;        &lt;xci:variables /&gt;        &lt;xci:methods&gt;         &lt;xci:method name=“xcilnit”&gt;          &lt;sequence name=“Sequence”&gt;           &lt;empty name=“Empty” /&gt;          &lt;/sequence&gt;         &lt;/xci:method&gt;         &lt;xci:method name=“onCheck”&gt;          &lt;sequence name=“Sequence”&gt;           &lt;empty name=“Empty” /&gt;          &lt;/sequence&gt;         &lt;/xci:method&gt;        &lt;/xci:methods&gt;       &lt;/xci:bpelo&gt;       Second page “second”, holding method “xciInit”:       &lt;?xml version=“1.0” encoding=“UTF-8”?&gt;       &lt;xci:bpelo xmlns:xci=“http://www.softwareag.com/xci/”        xmlns=“http://schemas.xmlsoap.org/ws/2003/03/business-process/”        xmlns:ht=“http://www.softwareag.com/xci/xciHeaderTrailer”        xmlns:xo=“http://www.softwareag.com/xci/wt/second” name=“second”        targetNamespace=“http://www.softwareag.com/xci/wt/second”&gt;        &lt;xci:variables /&gt;        &lt;xci:methods&gt;         &lt;xci:method name=“xcilnit”&gt;          &lt;sequence name=“Sequence”&gt;           &lt;empty name=“Empty” /&gt;          &lt;/sequence&gt;         &lt;/xci:method&gt;        &lt;/xci:methods&gt;       &lt;/xci:bpelo&gt;                  
 
         [0094]     The BPEL code that is generated out of the pages is: