CA2474109C - Framework for development and customization of web services deployment descriptors - Google Patents
Framework for development and customization of web services deployment descriptors Download PDFInfo
- Publication number
- CA2474109C CA2474109C CA2474109A CA2474109A CA2474109C CA 2474109 C CA2474109 C CA 2474109C CA 2474109 A CA2474109 A CA 2474109A CA 2474109 A CA2474109 A CA 2474109A CA 2474109 C CA2474109 C CA 2474109C
- Authority
- CA
- Canada
- Prior art keywords
- user interface
- data fragment
- xml
- data
- adapter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000011161 development Methods 0.000 title abstract description 20
- 239000012634 fragment Substances 0.000 claims abstract description 101
- 230000008859 change Effects 0.000 claims description 17
- 238000000034 method Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims 8
- 230000007246 mechanism Effects 0.000 abstract description 13
- 238000013507 mapping Methods 0.000 abstract description 8
- 238000012545 processing Methods 0.000 description 28
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 4
- 230000027455 binding Effects 0.000 description 3
- 238000009739 binding Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 230000000644 propagated effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000035755 proliferation Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
An extensible software framework for the development and customization of XML based Web service deployment descriptors is provided. The framework provides for the mapping and synchronization of XML data fragments in the XML files to user interface components, resulting in a visually appealing interface that can be used for the rapid development and customization of the Web service configuration. This mechanism allows concurrent read and write accesses to the XML based Web service deployment descriptors, eliminating common concurrency problems, such as data loss. The mechanism is highly extensible, providing for the mapping between the user interface and the XML data fragments to be customized. Additional extensibility comes from the ability of the framework to readily accommodate the situation where the complete configuration of the Web service is described in multiple XML files. The resulting editor presents one unified display of all of the information across multiple files.
Description
FRAMEWORK FOR DEVELOPMENT AND CUSTOMIZATION OF WEB
SERVICES DEPhOYMENT DESCRIPTORS
BACKGROUND OF THE INVENTION
1. Technical Field:
The present invention relates to an improved data processing system and, in particular, to customization of Web services.
SERVICES DEPhOYMENT DESCRIPTORS
BACKGROUND OF THE INVENTION
1. Technical Field:
The present invention relates to an improved data processing system and, in particular, to customization of Web services.
2. Description of Related Art:
HyperText Markup Language is a document format used on the World Wide Web. Web pages are text documents built with HTML tags embedded in the text. HTML defines the page layout, fonts, and graphic elements as well as hypertext links to other documents on the Web. HTML is derived from the Standard Generalized Markup Language (SGML).
A subset of SGML is known as eXtensible Markup Language (XML). XML is used for defining data elements on a Web page and business-to-business documents. XML
uses a similar tag structure as HTML; however, whereas HTML defines how elements are displayed, XML defines what those elements contain. HTML uses predefined tags, but XML allows tags to be defined by the developer of the page. Thus, virtually any data items can be identified, allowing Web pages to function like database records.
XML tags are defined in an XML Schema, which defines content type as well as name. XML tags can also be described in a Document Type Definition (DTD) format, since XML is a subset of the SGML language. Unlike HTML, which uses a rather loose coding style and which is tolerant of coding errors, XML pages must be "well formed," which means they must comply with rigid rules.
HTML and XML documents are primarily text documents.
Therefore, HTML and XML documents can be created and edited using a simple text editor. However, the complexity of the documents and the structure to which they must conform makes this a difficult task.
Therefore, an HTML- or XML-specific editor may be used.
These editors may be implemented in a variety of ways.
For example, a stand-alone application may be provided.
Web-based solutions are preferred because the author need not install heavy software on the client and, theoretically, the editor may be supported by any computer with a Web browser application.
Rapid proliferation of Web services technology requires tools that simplify the development and deployment of Web services. Developing and configuring a Web service may require the developer to edit and/or customize several XML-based deployment descriptors. This can be cumbersome, time consuming, and, hence, costly.
Even currently available XML editors, which provide the ability to view and edit XML files using a graphical user interface (GUI), have the drawback of exposing the complexity of XML to the user, thus distancing them from the otherwise straightforward task of configuring Web services and, instead, requiring them to create and modify Web services in an XML-centric fashion.
Another way of making XML more readable is through commercially available tools based on eXstensible Stylesheet Language (XSL) technology. XSL provides a mechanism for customizing the display of the Web service configuration so that it is easier to read and interpret.
However XSL fails to provide a mechanism for the user to develop or modify the configuration through this display.
On the other hand, some developers may be comfortable with XML descriptors. The developer must then choose between using a GUI-based editor that isolates the user from the complexities of XML and using a text-only editor that may be cumbersome and time consuming. These tools must be used separately; there is insufficient integration between GUI-based tools and text-based editors. Particularly, when they are used concurrently, they may produce undesirable effects, such as data loss.
SL'J1~ARY OF THE INVENTION
The present invention provides an extensible software framework for the development and customization of XML based Web service deployment descriptors. The framework provides for the mapping and synchronization of XML data fragments in the XML files to user interface components, resulting in a visually appealing interface that can be used for the rapid development and customization of the Web service configuration. This mechanism allows concurrent read/write access to the XML
based Web service deployment descriptors, eliminating common concurrency problems, such as data loss. The mechanism is highly extensible, providing for the mapping between the user interface and the XML data fragments to be customized. Additional extensibility comes from the ability of the framework to readily accommodate the situation where the complete configuration of the Web service is described in multiple XML files. The resulting editor presents one unified display of all of the information across multiple files.
BRIEF DESCRIPTION OF THE DRAWINGS
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
Figure 1 depicts a pictorial representation of a network of data processing systems in which the present invention may be implemented;
Figure 2 is a block diagram of a data processing system that may be implemented as a server in accordance with a preferred embodiment of the present invention;
Figure 3 is a block diagram of a data processing system in which the present invention may be implemented;
Figures 4A and 4B depict a framework for developing and customizing Web services deployment descriptors in accordance with an exemplary embodiment of the present invention;
Figure 5 is a block diagram depicting initialization and operation of an editor for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention;
Figure 6 is a timing diagram illustrating the operation of the framework for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention;
Figures 7A-7D illustrate example XML deployment descriptors and corresponding user interface components for a web services descriptor document in accordance with a preferred embodiment of the present invention;
Figures 8A and 8B illustrate example XML deployment descriptors and corresponding user interface components for Web service security extensions deployment descriptors in accordance with a preferred embodiment of the present invention;
Figures 9A-9D illustrate example XML deployment descriptors and corresponding user interface components for Web service bindings deployment descriptors in accordance with a preferred embodiment of the present invention;
Figure 10 is a flowchart illustrating the operation of initializing an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention; and Figure 11 is a flowchart illustrating the operation of an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EI~ODIMENT
The present invention provides a method, apparatus, and compute r program product for development and customization of XML based Web services deployment descriptors. The data processing device may be a stand-alone computing device or may be a distributed data processing system in which multiple computing devices are utilized to perform various aspects of the present invention. Therefore, the following Figures 1-3 are provided as exemplary diagrams of data processing environments in which the present invention may be implemented. It should be appreciated that Figures 1-3 are only exemplary and are not intended to assert or imply any limitation with regard to the environments in which the present invention may be implemented. Many modifications to the depicted environments may be made without departing from the spirit and scope of the present invention.
With reference now to the figures, Figure 1 depicts a pictorial representation of a network of data processing systems in which the present invention may be implemented.
Network data processing system 100 is a network of computers in which the present invention may be implemented. Network data processing system 100 contains a network 102, which is the medium used to provide communications links between various devices and computers connected together within network data processing system 100. Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.
In the depicted example, server 104 is connected to network 102 along with storage unit 106. In addition, clients 108, 110, and 112 are connected to network 102.
These clients 108, I10, and 112 may be, for example, personal computers or network computers. In the depicted example, server 104 provides data, such as boot files, operating system images, and applications to clients 108-112. Clients 108, 110, and 112 are clients to server 104.
HyperText Markup Language is a document format used on the World Wide Web. Web pages are text documents built with HTML tags embedded in the text. HTML defines the page layout, fonts, and graphic elements as well as hypertext links to other documents on the Web. HTML is derived from the Standard Generalized Markup Language (SGML).
A subset of SGML is known as eXtensible Markup Language (XML). XML is used for defining data elements on a Web page and business-to-business documents. XML
uses a similar tag structure as HTML; however, whereas HTML defines how elements are displayed, XML defines what those elements contain. HTML uses predefined tags, but XML allows tags to be defined by the developer of the page. Thus, virtually any data items can be identified, allowing Web pages to function like database records.
XML tags are defined in an XML Schema, which defines content type as well as name. XML tags can also be described in a Document Type Definition (DTD) format, since XML is a subset of the SGML language. Unlike HTML, which uses a rather loose coding style and which is tolerant of coding errors, XML pages must be "well formed," which means they must comply with rigid rules.
HTML and XML documents are primarily text documents.
Therefore, HTML and XML documents can be created and edited using a simple text editor. However, the complexity of the documents and the structure to which they must conform makes this a difficult task.
Therefore, an HTML- or XML-specific editor may be used.
These editors may be implemented in a variety of ways.
For example, a stand-alone application may be provided.
Web-based solutions are preferred because the author need not install heavy software on the client and, theoretically, the editor may be supported by any computer with a Web browser application.
Rapid proliferation of Web services technology requires tools that simplify the development and deployment of Web services. Developing and configuring a Web service may require the developer to edit and/or customize several XML-based deployment descriptors. This can be cumbersome, time consuming, and, hence, costly.
Even currently available XML editors, which provide the ability to view and edit XML files using a graphical user interface (GUI), have the drawback of exposing the complexity of XML to the user, thus distancing them from the otherwise straightforward task of configuring Web services and, instead, requiring them to create and modify Web services in an XML-centric fashion.
Another way of making XML more readable is through commercially available tools based on eXstensible Stylesheet Language (XSL) technology. XSL provides a mechanism for customizing the display of the Web service configuration so that it is easier to read and interpret.
However XSL fails to provide a mechanism for the user to develop or modify the configuration through this display.
On the other hand, some developers may be comfortable with XML descriptors. The developer must then choose between using a GUI-based editor that isolates the user from the complexities of XML and using a text-only editor that may be cumbersome and time consuming. These tools must be used separately; there is insufficient integration between GUI-based tools and text-based editors. Particularly, when they are used concurrently, they may produce undesirable effects, such as data loss.
SL'J1~ARY OF THE INVENTION
The present invention provides an extensible software framework for the development and customization of XML based Web service deployment descriptors. The framework provides for the mapping and synchronization of XML data fragments in the XML files to user interface components, resulting in a visually appealing interface that can be used for the rapid development and customization of the Web service configuration. This mechanism allows concurrent read/write access to the XML
based Web service deployment descriptors, eliminating common concurrency problems, such as data loss. The mechanism is highly extensible, providing for the mapping between the user interface and the XML data fragments to be customized. Additional extensibility comes from the ability of the framework to readily accommodate the situation where the complete configuration of the Web service is described in multiple XML files. The resulting editor presents one unified display of all of the information across multiple files.
BRIEF DESCRIPTION OF THE DRAWINGS
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
Figure 1 depicts a pictorial representation of a network of data processing systems in which the present invention may be implemented;
Figure 2 is a block diagram of a data processing system that may be implemented as a server in accordance with a preferred embodiment of the present invention;
Figure 3 is a block diagram of a data processing system in which the present invention may be implemented;
Figures 4A and 4B depict a framework for developing and customizing Web services deployment descriptors in accordance with an exemplary embodiment of the present invention;
Figure 5 is a block diagram depicting initialization and operation of an editor for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention;
Figure 6 is a timing diagram illustrating the operation of the framework for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention;
Figures 7A-7D illustrate example XML deployment descriptors and corresponding user interface components for a web services descriptor document in accordance with a preferred embodiment of the present invention;
Figures 8A and 8B illustrate example XML deployment descriptors and corresponding user interface components for Web service security extensions deployment descriptors in accordance with a preferred embodiment of the present invention;
Figures 9A-9D illustrate example XML deployment descriptors and corresponding user interface components for Web service bindings deployment descriptors in accordance with a preferred embodiment of the present invention;
Figure 10 is a flowchart illustrating the operation of initializing an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention; and Figure 11 is a flowchart illustrating the operation of an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EI~ODIMENT
The present invention provides a method, apparatus, and compute r program product for development and customization of XML based Web services deployment descriptors. The data processing device may be a stand-alone computing device or may be a distributed data processing system in which multiple computing devices are utilized to perform various aspects of the present invention. Therefore, the following Figures 1-3 are provided as exemplary diagrams of data processing environments in which the present invention may be implemented. It should be appreciated that Figures 1-3 are only exemplary and are not intended to assert or imply any limitation with regard to the environments in which the present invention may be implemented. Many modifications to the depicted environments may be made without departing from the spirit and scope of the present invention.
With reference now to the figures, Figure 1 depicts a pictorial representation of a network of data processing systems in which the present invention may be implemented.
Network data processing system 100 is a network of computers in which the present invention may be implemented. Network data processing system 100 contains a network 102, which is the medium used to provide communications links between various devices and computers connected together within network data processing system 100. Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.
In the depicted example, server 104 is connected to network 102 along with storage unit 106. In addition, clients 108, 110, and 112 are connected to network 102.
These clients 108, I10, and 112 may be, for example, personal computers or network computers. In the depicted example, server 104 provides data, such as boot files, operating system images, and applications to clients 108-112. Clients 108, 110, and 112 are clients to server 104.
Network data processing system 100 may include additional servers, clients, and other devices not shown.
In accordance with a preferred embodiment of the present invention, server 104 provides an editor to clients 108, 110, 112. More particularly, server 102 may provide access to XML based Web services descriptor files in storage 106, for example. Thus, a user may access the XML based descriptor files directly using a simple and well-known text editor.
In accordance with one preferred embodiment, a dynamic framework is provided for developing a graphical user interface (GUI) for reading and editing Web services deployment descriptors. This framework involves the development of user interface (UI) components for XML data fragments in the deployment descriptors and adapters responsible for synchronizing between these UI components and XML data fragments. This framework may be provided through an editor mechanism on server 104 in the depicted example. The UI components may be accessed, for example, using a browser client application on one of clients 108, 110, 112. Alternatively, the deployment descriptor documents may be accessed directly using a text editor, for instance, on one of clients 108, 110, 112.
Although Web services deployment descriptors are XML
based documents that are supposed to be human readable, this feature degrades with the complexity of the XML
documents. Furthermore, editing XML based documents directly may be error prone. The custom UI components developed by the editor mechanism of the present invention provide a user-friendly environment for reading and editing these documents. The use of custom UI components also increases the accuracy and integrity of the data.
In accordance with a preferred embodiment of the present invention, server 104 provides an editor to clients 108, 110, 112. More particularly, server 102 may provide access to XML based Web services descriptor files in storage 106, for example. Thus, a user may access the XML based descriptor files directly using a simple and well-known text editor.
In accordance with one preferred embodiment, a dynamic framework is provided for developing a graphical user interface (GUI) for reading and editing Web services deployment descriptors. This framework involves the development of user interface (UI) components for XML data fragments in the deployment descriptors and adapters responsible for synchronizing between these UI components and XML data fragments. This framework may be provided through an editor mechanism on server 104 in the depicted example. The UI components may be accessed, for example, using a browser client application on one of clients 108, 110, 112. Alternatively, the deployment descriptor documents may be accessed directly using a text editor, for instance, on one of clients 108, 110, 112.
Although Web services deployment descriptors are XML
based documents that are supposed to be human readable, this feature degrades with the complexity of the XML
documents. Furthermore, editing XML based documents directly may be error prone. The custom UI components developed by the editor mechanism of the present invention provide a user-friendly environment for reading and editing these documents. The use of custom UI components also increases the accuracy and integrity of the data.
A two-way synchronization is also achieved using the adapters. Updates in an UI component will result in a corresponding change in the deployment descriptors.
Similarly, changes that are made directly to the deployment descriptor documents may be reflected in the UI
components. Thus, the editor mechanism of the present invention allows both reading and editing of XML
documents, as opposed to eXtensible Stylesheet Language (XSL) technology, which transforms XML documents into HTML
documents for reading purposes but provides no editing support. The editor mechanism of the present invention also allows disjoint deployment descriptors to be presented together as one logical unit. The editor mechanism of the present invention also allows continual synchronization between UI components and XML documents, eliminating common concurrency problems, such as data loss.
In the depicted example, network data processing system 100 is the Internet with network 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational and other computer systems that route data and messages. Of course, network data processing system 100 also may be implemented as a number of different types of networks, such as for example, an intranet, a local area network (LAN) , or a wide area network (WAN) . Figure 1 is intended as an example, and not as an architectural limitation for the present invention.
Similarly, changes that are made directly to the deployment descriptor documents may be reflected in the UI
components. Thus, the editor mechanism of the present invention allows both reading and editing of XML
documents, as opposed to eXtensible Stylesheet Language (XSL) technology, which transforms XML documents into HTML
documents for reading purposes but provides no editing support. The editor mechanism of the present invention also allows disjoint deployment descriptors to be presented together as one logical unit. The editor mechanism of the present invention also allows continual synchronization between UI components and XML documents, eliminating common concurrency problems, such as data loss.
In the depicted example, network data processing system 100 is the Internet with network 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational and other computer systems that route data and messages. Of course, network data processing system 100 also may be implemented as a number of different types of networks, such as for example, an intranet, a local area network (LAN) , or a wide area network (WAN) . Figure 1 is intended as an example, and not as an architectural limitation for the present invention.
Referring to Figure 2, a block diagram of a data processing system that may be implemented as a server, such as server 104 in Figure l, is depicted in accordance with a preferred embodiment of the present invention.
Data processing system 200 may be a symmetric multiprocessor (SMP) system including a plurality of processors 202 and 204 connected to system bus 206.
Alternatively, a single processor system may be employed.
Also connected to system bus 206 is memory controller/cache 208, which provides an interface to local memory 209. I/0 bus bridge 210 is connected to system bus 206 and provides an interface to I/0 bus 212. Memory controller/cache 208 and I/0 bus bridge 210 may be integrated as depicted.
Peripheral component interconnect (PCI) bus bridge 214 connected to I/0 bus 212 provides an interface to PCI
local bus 216. A number of modems may be connected to PCI
local bus 216. Typical PCI bus implementations will support four PCI expansion slots or add-in connectors.
Communications links to clients 108-112 in Figure 1 may be provided through modem 218 and network adapter 220 connected to PCI local bus 216 through add-in connectors.
Additional PCI bus bridges 222 and 224 provide interfaces for additional PCI local buses 226 and 228, from which additional modems or network adapters may be supported. In this manner, data processing system 200 allows connections to multiple network computers. A
memory-mapped graphics adapter 230 and hard disk 232 may also be connected to I/O bus 212 as depicted, either directly or indirectly.
Those of ordinary skill in the art will appreciate that the hardware depicted in Figure 2 may vary. For example, other peripheral devices, such as optical disk drives and the like, also may be used in addition to or in place of the hardware depicted. The depicted example is not meant to imply architectural limitations with respect to the present invention.
The data processing system depicted in Figure 2 may be, for example, an IBM eServerTM pSeries~ system, a product of Tnternational Business Machines Corporation in Armonk, New York, running the Advanced Interactive Executive (AIXTM) operating system or LINUX operating system.
With reference now to Figure 3, a block diagram of a data processing system is shown in which the present invention may be implemented. Data processing system 300 is an example of a computer, such as client 108 in Figure l, in which code or instructions implementing the processes of the present invention may be located. In the depicted example, data processing system 300 employs a hub architecture including a north bridge and memory controller hub (MCH) 308 and a south bridge and input/output (I/0) controller hub (ICH) 310. Processor 302, main memory 304, and graphics processor 318 are connected to MCH 308. Graphics processor 318 may be connected to the MCH through an accelerated graphics port (AGP), for example.
In the depicted example, local area network (LAN) adapter 312, audio adapter 316, keyboard and mouse adapter 320, modem 322, read only memory (ROM) 324, hard disk drive (HDD) 326, CD-ROM driver 330, universal serial bus (USB) ports and other communications ports 332, and PCI/PCIe devices 334 may be connected to ICH 310.
PCI/PCIe devices may include, for example, Ethernet adapters, add-in cards, PC cards for notebook computers, etc. PCI uses a cardbus controller, while PCIe does not.
ROM 324 may be, for example, a flash binary input/output system (BIOS). Hard disk drive 326 and CD-ROM drive 330 may use, for example, an integrated drive electronics (IDE) or serial advanced technology attachment (SATA) interface. A super I/0 (SIO) device 336 may be connected to ICH 310.
An operating system runs on processor 302 and is used to coordinate and provide control of various components within data processing system 300 in Figure 3. The operating system may be a commercially available operating system such as Windows XPTM, which is available from Microsoft Corporation. An object oriented programming system, such as the JavaTM programming system, may run in conjunction with the operating system and provides calls to the operating system from JavaTM programs or applications executing on data processing system 300.
~~JAVA" is a trademark of Sun Microsystems, Inc.
Instructions for the operating system, the object-oriented programming system, and applications or programs are located on storage devices, such as hard disk drive 326, and may be loaded into main memory 304 for execution by processor 302. The processes of the present invention are performed by processor 302 using computer implemented instructions, which may be located in a memory such as, for example, main memory 304, memory 324, or in one or more peripheral devices 326 and 330.
Those of ordinary skill in the art will appreciate that the hardware in Figure 3 may vary depending on the implementation. Other internal hardware or peripheral devices, such as flash memory, equivalent non-volatile memory, or optical disk drives and the like, may be used in addition to or in place of the hardware depicted in Figure 3. Also, the processes of the present invention may be applied to a multiprocessor data processing system.
For example, data processing system 300 may be a personal digital assistant (PDA), which is configured with flash memory to provide non-volatile memory for storing operating system files and/or user-generated data. The depicted example in Figure 3 and above-described examples are not meant to imply architectural limitations. For example, data processing system 300 also may be a tablet computer, laptop computer, or telephone device in addition to taking the form of a PDA.
Figures 4A and 48 depict a framework for developing and customizing Web services deployment descriptors in accordance with an exemplary embodiment of the present invention. More particularly, with reference to Figure 4A, GUI component 410 is generated based on XML data fragment 430. A GUI component may include one or more GUI controls for displaying data and capturing user input. In the depicted example, GUI component 410 includes text field control 412, list control 414, and other controls (not shown).
XML data fragment 430 may be a portion of an XML
file, a portion of another XML data fragment, or a collection of XML data fragments, for example. There may be one adapter and one GUI component for each identified data fragment. Adapter 420 keeps track of the mapping and synchronization between the GUI component 410 and XML
data fragment 430. When a user makes a modification in GUI component 410, adapter 420 is informed of this modification and updates XML data fragment 430 accordingly. Similarly, if any changes occur in XML data fragment 430 from another source, adapter 420 is informed of the changes and updates GUI component 410 accordingly.
Another source may originate from the same or a different computer. As an example, a user may develop XML based Web services deployment descriptors using the GUI
components and, in another window, edit the XML
descriptors using a simple text editor. Alternately, one user may develop or customize the Web Services deployment descriptors on one computer while another user directly accesses the XML files) on another computer.
In addition to displaying the Web services configuration in a way that hides the underlying XML, this framework also displays the data in a way that hides file boundaries from the user. Multiple files may be registered, by name, with one editor and, as long as the mapping between the GUI components and the XML data fragments contained in the files is complete, the contents of the registered files are made available in the editor.
Figure 4B illustrates an adapter for synchronizing Web services deployment descriptors with GUI components in accordance with a preferred embodiment of the present invention. Adapter 470 includes listeners to GUI
components 472, listeners to the data fragment 474, GUI
component routines/handlers 476, and data fragment routines/handlers 478. Adapter 470 contains a reference to GUI component 460 and data fragment 480.
When listeners 472 are notified that changes are made through GUI component 460, data fragments routines/handlers 478 are invoked. Data fragments routines/handlers propagate these changes to data fragment 480. Similarly, when listeners 474 are notified that changes are made to data fragment 480, GUI
components routines/handlers 476 are invoked. GUI
components routines/handlers 476 propagate these changes to GUI component 460.
Figure 5 is a block diagram depicting initialization and operation of an editor for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention. Editor 510, in client 560 opens XML descriptors 502. Editor 510 parses XML descriptors 502 to identify or divides the XML descriptors into data fragments. As described above, an XML data fragment is a portion of an XML deployment descriptor file or files. A
data fragment may be a portion of another data fragment or, conversely, a data fragment may be a collection of other data fragments. Many techniques may be used for parsing the XML descriptors; however, the manner in which XML deployment descriptors are divided into data fragments is not the focus of the present invention.
There is an adapter type for every GUI component and editor 510 creates an adapter instance for each instance of GUI components 512. Each instance of adapters 514 registers an association between one of GUI components 512 and a data fragment in XML descriptors 502.
In operation, GUI components 512 are provided to client 560. GUI components 512 may be presented to a user at client 560. GUI components 512 may be, for example, JavaTM Standard Widget Toolkit (SWT) classes that include controls, such as text fields, drop-down boxes, lists, radio buttons, tables, buttons, and the like.
These controls may be used to develop and customize the Web services without being exposed to the potentially complicated XML deployment descriptors. Thus, users need not know the language and syntax of the XML descriptors, just the details of the Web services they wish to deploy or configure. The user may then use editor 510, in which the GUI components are rendered, to navigate GUI
components 512 and send changes to adapters 514. In turn, adapters 514 listen for these changes and effectuate appropriate changes to XML descriptors 502.
Adapters 514 also listen for changes to data fragments within XML descriptors 502. A user at client 550 may directly access XML descriptors 502 using, for example text editor 552. Responsive to changes being made directly to XML descriptors 502, adapters 514 propagate these changes to GUI components 512.
Figure 6 is a timing diagram illustrating the operation of the framework for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention. The framework operates as follows:
1. A user initiates reading or editing of the Web services deployment descriptors by opening an editor. The editor serves as the GUI for the deployment descriptors.
2. The editor parses the deployment descriptors and identifies the XML data fragments.
3. As part of the editor's initialization, the editor creates all the UI components for each of the identified XML data fragments.
4. The editor creates the adapters.
5. The editor registers the UI components with the adapters.
6. The editor registers the corresponding data fragments with the adapters. The registration process adds listeners to both UI components and XML data fragments.
7. The user initiates an update to the deployment descriptors via the GUI.
8. The update triggers the listeners to notify the adapter.
9. When the adapter receives this notification, it invokes the routines/handlers that are responsible for updating the corresponding XML data fragments.
The XML data fragments may reside in disjoint documents.
Data processing system 200 may be a symmetric multiprocessor (SMP) system including a plurality of processors 202 and 204 connected to system bus 206.
Alternatively, a single processor system may be employed.
Also connected to system bus 206 is memory controller/cache 208, which provides an interface to local memory 209. I/0 bus bridge 210 is connected to system bus 206 and provides an interface to I/0 bus 212. Memory controller/cache 208 and I/0 bus bridge 210 may be integrated as depicted.
Peripheral component interconnect (PCI) bus bridge 214 connected to I/0 bus 212 provides an interface to PCI
local bus 216. A number of modems may be connected to PCI
local bus 216. Typical PCI bus implementations will support four PCI expansion slots or add-in connectors.
Communications links to clients 108-112 in Figure 1 may be provided through modem 218 and network adapter 220 connected to PCI local bus 216 through add-in connectors.
Additional PCI bus bridges 222 and 224 provide interfaces for additional PCI local buses 226 and 228, from which additional modems or network adapters may be supported. In this manner, data processing system 200 allows connections to multiple network computers. A
memory-mapped graphics adapter 230 and hard disk 232 may also be connected to I/O bus 212 as depicted, either directly or indirectly.
Those of ordinary skill in the art will appreciate that the hardware depicted in Figure 2 may vary. For example, other peripheral devices, such as optical disk drives and the like, also may be used in addition to or in place of the hardware depicted. The depicted example is not meant to imply architectural limitations with respect to the present invention.
The data processing system depicted in Figure 2 may be, for example, an IBM eServerTM pSeries~ system, a product of Tnternational Business Machines Corporation in Armonk, New York, running the Advanced Interactive Executive (AIXTM) operating system or LINUX operating system.
With reference now to Figure 3, a block diagram of a data processing system is shown in which the present invention may be implemented. Data processing system 300 is an example of a computer, such as client 108 in Figure l, in which code or instructions implementing the processes of the present invention may be located. In the depicted example, data processing system 300 employs a hub architecture including a north bridge and memory controller hub (MCH) 308 and a south bridge and input/output (I/0) controller hub (ICH) 310. Processor 302, main memory 304, and graphics processor 318 are connected to MCH 308. Graphics processor 318 may be connected to the MCH through an accelerated graphics port (AGP), for example.
In the depicted example, local area network (LAN) adapter 312, audio adapter 316, keyboard and mouse adapter 320, modem 322, read only memory (ROM) 324, hard disk drive (HDD) 326, CD-ROM driver 330, universal serial bus (USB) ports and other communications ports 332, and PCI/PCIe devices 334 may be connected to ICH 310.
PCI/PCIe devices may include, for example, Ethernet adapters, add-in cards, PC cards for notebook computers, etc. PCI uses a cardbus controller, while PCIe does not.
ROM 324 may be, for example, a flash binary input/output system (BIOS). Hard disk drive 326 and CD-ROM drive 330 may use, for example, an integrated drive electronics (IDE) or serial advanced technology attachment (SATA) interface. A super I/0 (SIO) device 336 may be connected to ICH 310.
An operating system runs on processor 302 and is used to coordinate and provide control of various components within data processing system 300 in Figure 3. The operating system may be a commercially available operating system such as Windows XPTM, which is available from Microsoft Corporation. An object oriented programming system, such as the JavaTM programming system, may run in conjunction with the operating system and provides calls to the operating system from JavaTM programs or applications executing on data processing system 300.
~~JAVA" is a trademark of Sun Microsystems, Inc.
Instructions for the operating system, the object-oriented programming system, and applications or programs are located on storage devices, such as hard disk drive 326, and may be loaded into main memory 304 for execution by processor 302. The processes of the present invention are performed by processor 302 using computer implemented instructions, which may be located in a memory such as, for example, main memory 304, memory 324, or in one or more peripheral devices 326 and 330.
Those of ordinary skill in the art will appreciate that the hardware in Figure 3 may vary depending on the implementation. Other internal hardware or peripheral devices, such as flash memory, equivalent non-volatile memory, or optical disk drives and the like, may be used in addition to or in place of the hardware depicted in Figure 3. Also, the processes of the present invention may be applied to a multiprocessor data processing system.
For example, data processing system 300 may be a personal digital assistant (PDA), which is configured with flash memory to provide non-volatile memory for storing operating system files and/or user-generated data. The depicted example in Figure 3 and above-described examples are not meant to imply architectural limitations. For example, data processing system 300 also may be a tablet computer, laptop computer, or telephone device in addition to taking the form of a PDA.
Figures 4A and 48 depict a framework for developing and customizing Web services deployment descriptors in accordance with an exemplary embodiment of the present invention. More particularly, with reference to Figure 4A, GUI component 410 is generated based on XML data fragment 430. A GUI component may include one or more GUI controls for displaying data and capturing user input. In the depicted example, GUI component 410 includes text field control 412, list control 414, and other controls (not shown).
XML data fragment 430 may be a portion of an XML
file, a portion of another XML data fragment, or a collection of XML data fragments, for example. There may be one adapter and one GUI component for each identified data fragment. Adapter 420 keeps track of the mapping and synchronization between the GUI component 410 and XML
data fragment 430. When a user makes a modification in GUI component 410, adapter 420 is informed of this modification and updates XML data fragment 430 accordingly. Similarly, if any changes occur in XML data fragment 430 from another source, adapter 420 is informed of the changes and updates GUI component 410 accordingly.
Another source may originate from the same or a different computer. As an example, a user may develop XML based Web services deployment descriptors using the GUI
components and, in another window, edit the XML
descriptors using a simple text editor. Alternately, one user may develop or customize the Web Services deployment descriptors on one computer while another user directly accesses the XML files) on another computer.
In addition to displaying the Web services configuration in a way that hides the underlying XML, this framework also displays the data in a way that hides file boundaries from the user. Multiple files may be registered, by name, with one editor and, as long as the mapping between the GUI components and the XML data fragments contained in the files is complete, the contents of the registered files are made available in the editor.
Figure 4B illustrates an adapter for synchronizing Web services deployment descriptors with GUI components in accordance with a preferred embodiment of the present invention. Adapter 470 includes listeners to GUI
components 472, listeners to the data fragment 474, GUI
component routines/handlers 476, and data fragment routines/handlers 478. Adapter 470 contains a reference to GUI component 460 and data fragment 480.
When listeners 472 are notified that changes are made through GUI component 460, data fragments routines/handlers 478 are invoked. Data fragments routines/handlers propagate these changes to data fragment 480. Similarly, when listeners 474 are notified that changes are made to data fragment 480, GUI
components routines/handlers 476 are invoked. GUI
components routines/handlers 476 propagate these changes to GUI component 460.
Figure 5 is a block diagram depicting initialization and operation of an editor for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention. Editor 510, in client 560 opens XML descriptors 502. Editor 510 parses XML descriptors 502 to identify or divides the XML descriptors into data fragments. As described above, an XML data fragment is a portion of an XML deployment descriptor file or files. A
data fragment may be a portion of another data fragment or, conversely, a data fragment may be a collection of other data fragments. Many techniques may be used for parsing the XML descriptors; however, the manner in which XML deployment descriptors are divided into data fragments is not the focus of the present invention.
There is an adapter type for every GUI component and editor 510 creates an adapter instance for each instance of GUI components 512. Each instance of adapters 514 registers an association between one of GUI components 512 and a data fragment in XML descriptors 502.
In operation, GUI components 512 are provided to client 560. GUI components 512 may be presented to a user at client 560. GUI components 512 may be, for example, JavaTM Standard Widget Toolkit (SWT) classes that include controls, such as text fields, drop-down boxes, lists, radio buttons, tables, buttons, and the like.
These controls may be used to develop and customize the Web services without being exposed to the potentially complicated XML deployment descriptors. Thus, users need not know the language and syntax of the XML descriptors, just the details of the Web services they wish to deploy or configure. The user may then use editor 510, in which the GUI components are rendered, to navigate GUI
components 512 and send changes to adapters 514. In turn, adapters 514 listen for these changes and effectuate appropriate changes to XML descriptors 502.
Adapters 514 also listen for changes to data fragments within XML descriptors 502. A user at client 550 may directly access XML descriptors 502 using, for example text editor 552. Responsive to changes being made directly to XML descriptors 502, adapters 514 propagate these changes to GUI components 512.
Figure 6 is a timing diagram illustrating the operation of the framework for development and customization of XML based Web services deployment descriptors in accordance with a preferred embodiment of the present invention. The framework operates as follows:
1. A user initiates reading or editing of the Web services deployment descriptors by opening an editor. The editor serves as the GUI for the deployment descriptors.
2. The editor parses the deployment descriptors and identifies the XML data fragments.
3. As part of the editor's initialization, the editor creates all the UI components for each of the identified XML data fragments.
4. The editor creates the adapters.
5. The editor registers the UI components with the adapters.
6. The editor registers the corresponding data fragments with the adapters. The registration process adds listeners to both UI components and XML data fragments.
7. The user initiates an update to the deployment descriptors via the GUI.
8. The update triggers the listeners to notify the adapter.
9. When the adapter receives this notification, it invokes the routines/handlers that are responsible for updating the corresponding XML data fragments.
The XML data fragments may reside in disjoint documents.
10. Similarly, any updates in the deployment descriptors trigger the listeners of the affected XML data fragments.
11. The updates trigger the listeners to notify the adapter.
12. The adapter invokes the routines/handlers that are responsible for updating the corresponding UI
components. The user then sees the most up-to-date data in the deployment descriptors and a two-way synchronization is achieved.
components. The user then sees the most up-to-date data in the deployment descriptors and a two-way synchronization is achieved.
13. Registration for XML data fragments with adapters is not restricted to being performed only in the initialization process. At any point in time, registration for XML data fragments may occur. An example of this scenario is when a user selects an item from a list to be added, which may result in new XML information.
14. The GUI component then registers the XML
information with the adapter.
information with the adapter.
15. The adapter, in turn, updates the GUI component.
As seen above, the framework achieves a two-way synchronization between GUI components and the corresponding XML deployment descriptors. The framework is dynamic, allowing changes to GUI components and data fragments to be propagated throughout the framework.
Thus, a user may develop or customize Web services without being directly exposed to the XML deployment descriptors, while still interacting with an up-to-date user interface, which is especially useful when concurrent read and write accesses to the XML descriptors are allowed.
Figures 7A-7D illustrate example XML deployment descriptors and corresponding user interface components for a web services descriptor document in accordance with a preferred embodiment of the present invention. XML
descriptor file 700 is parsed to identify XML data fragments. The GUI components shown in Figures 7B-7D
correspond to the data fragments identified in XML
descriptor file 700.
More particularly, as shown in Figure 7B, GUI window 710 includes controls for the Web services. For example, text fields 712, 714 correspond to the description and display-name tags in XML descriptor file 700. Figures 7C
and 7D show GUI components that correspond to other XML
information in XML descriptor file 700.
Figures 8A and 8B illustrate example XML deployment descriptors and corresponding user interface components for Web service security extensions deployment descriptors in accordance with a preferred embodiment of the present invention. XML descriptor file 800 is parsed to identify XML data fragments. The GUI components shown in Figure 8B
correspond to the data fragments identified in XML
descriptor file 800. More particularly, as shown in Figure 88, GUI window 810 includes controls for the Web service security extensions. For example, UI components 812 correspond to the port component binding data fragment in XML descriptor file 800.
Figures 9A-9D illustrate example XML deployment descriptors and corresponding user interface components for Web service bindings deployment descriptors in accordance with a preferred embodiment of the present invention. XML descriptor file shown in Figures 9A and 9B
is parsed to identify XML data fragments. The GUI
components shown in Figures 9C and 9D correspond to the data fragments identified in the XML descriptor file.
More particularly, as shown in Figure 9C, GUI window 900 includes button control 902 for adding descriptor information and button control 904 for removing descriptor information. As shown in Figure 9D, GUI window 910 includes button control 912 for editing descriptor information. Selection of buttons 902 and 912 may result in further GUI components being created or presented for the development or customization of XML deployment descriptors. It follows that interaction with these GUI
components may result in further data fragments being created. Selection of 904 may result in GUI and corresponding data fragments being removed.
Figure 10 is a flowchart illustrating the operation of initializing an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention. Operation begins and the editor parses the XML
descriptors to form a list of data fragments (block 1002).
The editor then identifies data fragments and corresponding GUI components (block 1004).
For each data fragment in the list (block 1006), the editor instantiates the appropriate GUI component (block 1008), instantiates an adapter (block 1010), and registers the GUI component and corresponding data fragment to the adapter (block 1012). If the current data fragment is not the last data fragment in the list in block 1014, the loop returns to block 1006 to initialize the editor framework for the next data fragment. However, if the current data fragment is the last data fragment in block 1014, operation ends.
F3.gure 11 is a flowchart illustrating the operation of an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention.
Operation begins when an editor is activated by a requesting client, such as a JavaTM SWT editor. The editor renders the GUI components to the requesting client (block 1102). A determination is made as to whether an exit condition exists (block 1104). An exit condition may exist, for example, when the requesting client closes the editor or when the server providing access to the editor application shuts down. If an exit condition exists, operation ends.
If an exit condition does not exist in block 1104, a determination is made as to whether there is a change to a GUI component (block 1106). If an adapter is notified of a change to a GUI component, the editor reflects the changes to the appropriate data fragment (block 1108).
Thereafter, operation returns to block 1106 to determine whether an exit condition exists.
If an adapter does not receive notification of a change to GUI component in block 1106, a determination is made as to whether there is a change to a data fragment (block 1110). If an adapter is notified of a change to a data fragment, the editor reflects the changes to the appropriate GUI component (block 1112). Thereafter, operation returns to block 1104 to determine whether an exit condition exists. If an adapter is not notified of a change to a data fragment in block 1110, operation returns to block 1104 to determine whether an exit condition exists.
Thus, the present invention provides an extensible software framework for the development and customization of XML based Web service deployment descriptors. The framework provides for the mapping and synchronization of XML data fragments in the XML files to user interface components, resulting in a visually appealing interface that can be used for the rapid development and customization of the Web service configuration. This mechanism allows concurrent read/write access to the XML
based Web service deployment descriptors, eliminating common concurrency problems, such as data loss. The mechanism is highly extensible, providing for the mapping and synchronization between the user interface and the XML data fragments to be customized. Additional extensibility comes from the ability of the framework to readily accommodate the situation where the complete configuration of the Web service is described in multiple XML files. The resulting editor presents one unified display of all of the information across multiple files.
In addition, the framework achieves a two-way synchronization between GUI components and the corresponding XML deployment descriptors. The framework is dynamic, allowing changes to GUI components and data fragments to be propagated throughout the framework.
Thus, a user may develop or customize Web services without being directly exposed to the XML deployment descriptors, while still interacting with an up-to-date user interface, which is especially useful when concurrent read and write accesses to the XML deployment descriptors are allowed.
It is important to note that while the present invention has been described in the context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the form of a computer readable medium of instructions and a variety of forms and that the present invention applies equally regardless of the particular type of signal bearing media actually used to carry out the distribution. Examples of computer readable media include recordable-type media, such as a floppy disk, a hard disk drive, a RAM, CD-ROMs, and DVD-ROMs. Computer software may also be embodied in a propagated signal or transmission-type media, such as digital and analog communications links, wired or wireless communications links using transmission forms, such as, for example, radio frequency and light wave transmissions. The computer readable media may take the form of coded formats that are decoded for actual use in a particular data processing system.
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
As seen above, the framework achieves a two-way synchronization between GUI components and the corresponding XML deployment descriptors. The framework is dynamic, allowing changes to GUI components and data fragments to be propagated throughout the framework.
Thus, a user may develop or customize Web services without being directly exposed to the XML deployment descriptors, while still interacting with an up-to-date user interface, which is especially useful when concurrent read and write accesses to the XML descriptors are allowed.
Figures 7A-7D illustrate example XML deployment descriptors and corresponding user interface components for a web services descriptor document in accordance with a preferred embodiment of the present invention. XML
descriptor file 700 is parsed to identify XML data fragments. The GUI components shown in Figures 7B-7D
correspond to the data fragments identified in XML
descriptor file 700.
More particularly, as shown in Figure 7B, GUI window 710 includes controls for the Web services. For example, text fields 712, 714 correspond to the description and display-name tags in XML descriptor file 700. Figures 7C
and 7D show GUI components that correspond to other XML
information in XML descriptor file 700.
Figures 8A and 8B illustrate example XML deployment descriptors and corresponding user interface components for Web service security extensions deployment descriptors in accordance with a preferred embodiment of the present invention. XML descriptor file 800 is parsed to identify XML data fragments. The GUI components shown in Figure 8B
correspond to the data fragments identified in XML
descriptor file 800. More particularly, as shown in Figure 88, GUI window 810 includes controls for the Web service security extensions. For example, UI components 812 correspond to the port component binding data fragment in XML descriptor file 800.
Figures 9A-9D illustrate example XML deployment descriptors and corresponding user interface components for Web service bindings deployment descriptors in accordance with a preferred embodiment of the present invention. XML descriptor file shown in Figures 9A and 9B
is parsed to identify XML data fragments. The GUI
components shown in Figures 9C and 9D correspond to the data fragments identified in the XML descriptor file.
More particularly, as shown in Figure 9C, GUI window 900 includes button control 902 for adding descriptor information and button control 904 for removing descriptor information. As shown in Figure 9D, GUI window 910 includes button control 912 for editing descriptor information. Selection of buttons 902 and 912 may result in further GUI components being created or presented for the development or customization of XML deployment descriptors. It follows that interaction with these GUI
components may result in further data fragments being created. Selection of 904 may result in GUI and corresponding data fragments being removed.
Figure 10 is a flowchart illustrating the operation of initializing an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention. Operation begins and the editor parses the XML
descriptors to form a list of data fragments (block 1002).
The editor then identifies data fragments and corresponding GUI components (block 1004).
For each data fragment in the list (block 1006), the editor instantiates the appropriate GUI component (block 1008), instantiates an adapter (block 1010), and registers the GUI component and corresponding data fragment to the adapter (block 1012). If the current data fragment is not the last data fragment in the list in block 1014, the loop returns to block 1006 to initialize the editor framework for the next data fragment. However, if the current data fragment is the last data fragment in block 1014, operation ends.
F3.gure 11 is a flowchart illustrating the operation of an editor framework for development and customization of Web services deployment descriptors in accordance with an exemplary embodiment of the present invention.
Operation begins when an editor is activated by a requesting client, such as a JavaTM SWT editor. The editor renders the GUI components to the requesting client (block 1102). A determination is made as to whether an exit condition exists (block 1104). An exit condition may exist, for example, when the requesting client closes the editor or when the server providing access to the editor application shuts down. If an exit condition exists, operation ends.
If an exit condition does not exist in block 1104, a determination is made as to whether there is a change to a GUI component (block 1106). If an adapter is notified of a change to a GUI component, the editor reflects the changes to the appropriate data fragment (block 1108).
Thereafter, operation returns to block 1106 to determine whether an exit condition exists.
If an adapter does not receive notification of a change to GUI component in block 1106, a determination is made as to whether there is a change to a data fragment (block 1110). If an adapter is notified of a change to a data fragment, the editor reflects the changes to the appropriate GUI component (block 1112). Thereafter, operation returns to block 1104 to determine whether an exit condition exists. If an adapter is not notified of a change to a data fragment in block 1110, operation returns to block 1104 to determine whether an exit condition exists.
Thus, the present invention provides an extensible software framework for the development and customization of XML based Web service deployment descriptors. The framework provides for the mapping and synchronization of XML data fragments in the XML files to user interface components, resulting in a visually appealing interface that can be used for the rapid development and customization of the Web service configuration. This mechanism allows concurrent read/write access to the XML
based Web service deployment descriptors, eliminating common concurrency problems, such as data loss. The mechanism is highly extensible, providing for the mapping and synchronization between the user interface and the XML data fragments to be customized. Additional extensibility comes from the ability of the framework to readily accommodate the situation where the complete configuration of the Web service is described in multiple XML files. The resulting editor presents one unified display of all of the information across multiple files.
In addition, the framework achieves a two-way synchronization between GUI components and the corresponding XML deployment descriptors. The framework is dynamic, allowing changes to GUI components and data fragments to be propagated throughout the framework.
Thus, a user may develop or customize Web services without being directly exposed to the XML deployment descriptors, while still interacting with an up-to-date user interface, which is especially useful when concurrent read and write accesses to the XML deployment descriptors are allowed.
It is important to note that while the present invention has been described in the context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the form of a computer readable medium of instructions and a variety of forms and that the present invention applies equally regardless of the particular type of signal bearing media actually used to carry out the distribution. Examples of computer readable media include recordable-type media, such as a floppy disk, a hard disk drive, a RAM, CD-ROMs, and DVD-ROMs. Computer software may also be embodied in a propagated signal or transmission-type media, such as digital and analog communications links, wired or wireless communications links using transmission forms, such as, for example, radio frequency and light wave transmissions. The computer readable media may take the form of coded formats that are decoded for actual use in a particular data processing system.
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (19)
The embodiments of the invention in which an exclusive property of privilege is claimed are defined as follows:
1. A method for managing Web services deployment descriptors, the method comprising:
parsing a deployment descriptor document to identify at least one data fragment;
providing a user interface component;
providing an adapter, wherein the adapter is associated with the user interface component and the date fragment;
updating the data fragment in response to the adapter being notified of a change to the associated user interface component; and updating the associated user interface component in response to the adapter being notified of a change to the associated data fragment.
parsing a deployment descriptor document to identify at least one data fragment;
providing a user interface component;
providing an adapter, wherein the adapter is associated with the user interface component and the date fragment;
updating the data fragment in response to the adapter being notified of a change to the associated user interface component; and updating the associated user interface component in response to the adapter being notified of a change to the associated data fragment.
2. The method of claim 1, wherein the data fragment is one of a portion of a deployment descriptor document, a portion of another data fragment, and a collection of other data fragments.
3. The method of claim 1, wherein the user interface component presents one unified display of all information across multiple deployment descriptor files.
4. The method of claim 1, wherein the deployment descriptor document comprises at least one extensible markup language file.
5. The method of claim 1, wherein parsing a deployment descriptor document to identify at least one data fragment comprises parsing a plurality of deployment documents to identify a plurality of data fragments, and wherein providing a user interface component comprises providing a plurality of user interface components, and wherein providing an adapter comprises providing a plurality of adapters, and wherein each of the plurality of adapters is associated with appropriate ones of the plurality of user interface components and a corresponding one of the plurality of data fragments.
6. The method of claim 5, further comprising:
updating the associated one data fragment in response to the corresponding adapter being notified of a change to the associated user interface component.
updating the associated one data fragment in response to the corresponding adapter being notified of a change to the associated user interface component.
7. The method of claim 5, further comprising:
updating the associated user interface component in response to the corresponding adapter being notified of a change to the associated data fragment.
updating the associated user interface component in response to the corresponding adapter being notified of a change to the associated data fragment.
8. A computer program product for managing Web services deployment descriptors, the computer program product comprising:
a computer readable medium having computer readable program code embodied therein, the computer readable program code comprising:
computer readable program code configured to parse a deployment descriptor documents to identify at least one data fragment;
computer readable program code configured to provide a user interface component;
computer readable program code configured to provide an adapter, wherein the adapter is associated with the user interface component and the data fragment;
computer readable program code configured to update the data fragment in response to the adapter being notified of a change to the associated user interface component; and computer readable program code configured to update the associated user interface component in response to the adapter being notified of a change to the associated data fragment.
a computer readable medium having computer readable program code embodied therein, the computer readable program code comprising:
computer readable program code configured to parse a deployment descriptor documents to identify at least one data fragment;
computer readable program code configured to provide a user interface component;
computer readable program code configured to provide an adapter, wherein the adapter is associated with the user interface component and the data fragment;
computer readable program code configured to update the data fragment in response to the adapter being notified of a change to the associated user interface component; and computer readable program code configured to update the associated user interface component in response to the adapter being notified of a change to the associated data fragment.
9. The computer program product of claim 8, wherein the data fragment is one of a portion of a deployment descriptor document, a portion of another data fragment, and a collection of other data fragments.
10. The computer program product of claim 8, wherein the user interface component presents one unified display of all information across multiple deployment descriptor files.
11. The computer program product of claim 8, wherein the deployment descriptor document comprises at least one extensible markup language file.
12. The computer program product of claim 8, wherein the computer readable program code configured to parse a deployment descriptor documents to identify at least one data fragment comprises computer readable program code configured to parse a plurality of deployment documents to identify a plurality of data fragments, and wherein the computer readable program code configured to provide a user interface component comprises computer readable program code configured to provide a plurality of user interface components, and wherein the computer readable program code configured to provide an adapter comprises computer readable program code configured to provide a plurality of adapters, and wherein each of the plurality of adapters is associated with appropriate ones of the plurality of user interface components and a corresponding one of the plurality of data fragments.
13. The computer program product of claim 12, further comprising computer readable program code configured to update the associated one data fragment in response to the corresponding adapter being notified of a change to the associated user interface component.
14. The computer program product of claim 12, further comprising computer readable program code configured to update the associated user interface component in response to the corresponding adapter being notified of a change to the associated data fragment.
15. An apparatus for managing Web services deployment descriptors, the apparatus comprising:
a parser, wherein the parser divides at least one deployment descriptor document into a plurality of data fragments;
a plurality of user interface components; and a plurality of adapters, wherein each of the plurality of adapters is associated wit a respective one of the plurality of user interface components and a corresponding one of the plurality of data fragments, wherein each of the plurality of adapters comprises:
a user interface component listener;
a data fragment listener;
a user interface handler that effectuates changes to a user interface component responsive to the data fragment listener receiving notification of a change to an associated data fragment; and a data fragment handler that effectuates changes to a data fragment responsive to the user interface listener receiving notification of a change to an associated user interface component.
a parser, wherein the parser divides at least one deployment descriptor document into a plurality of data fragments;
a plurality of user interface components; and a plurality of adapters, wherein each of the plurality of adapters is associated wit a respective one of the plurality of user interface components and a corresponding one of the plurality of data fragments, wherein each of the plurality of adapters comprises:
a user interface component listener;
a data fragment listener;
a user interface handler that effectuates changes to a user interface component responsive to the data fragment listener receiving notification of a change to an associated data fragment; and a data fragment handler that effectuates changes to a data fragment responsive to the user interface listener receiving notification of a change to an associated user interface component.
16. The apparatus of claim 15, wherein each of the plurality data fragments is one of a portion of a deployment descriptor document, a portion of another data fragment, and a collection of other data fragments.
17. The apparatus of claim 15, wherein the plurality of user interface components present one unified display of all information across multiple deployment descriptor files.
18. The apparatus of claim 15, wherein the at least one deployment descriptor document comprises at least one extensible markup language file.
19. The apparatus of claim 15, wherein the parser divides a plurality of deployment descriptor documents into a plurality of data fragments.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2474109A CA2474109C (en) | 2004-07-14 | 2004-07-14 | Framework for development and customization of web services deployment descriptors |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2474109A CA2474109C (en) | 2004-07-14 | 2004-07-14 | Framework for development and customization of web services deployment descriptors |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2474109A1 CA2474109A1 (en) | 2006-01-14 |
| CA2474109C true CA2474109C (en) | 2010-03-30 |
Family
ID=35610398
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2474109A Expired - Fee Related CA2474109C (en) | 2004-07-14 | 2004-07-14 | Framework for development and customization of web services deployment descriptors |
Country Status (1)
| Country | Link |
|---|---|
| CA (1) | CA2474109C (en) |
-
2004
- 2004-07-14 CA CA2474109A patent/CA2474109C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CA2474109A1 (en) | 2006-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8572494B2 (en) | Framework for development and customization of web services deployment descriptors | |
| KR101099272B1 (en) | Web page rendering mechanism using external programmatic themes | |
| US6901585B2 (en) | Active ALT tag in HTML documents to increase the accessibility to users with visual, audio impairment | |
| US8978019B2 (en) | Instrumentation of software applications for configuration thereof | |
| Armstrong et al. | The J2EE 1.4 tutorial | |
| US6569207B1 (en) | Converting schemas to component models | |
| US8201153B2 (en) | Configurable Java Server pages processing | |
| US20030110442A1 (en) | Developing documents | |
| US20050102612A1 (en) | Web-enabled XML editor | |
| US20050022116A1 (en) | System and method for manipulating a document object model | |
| US20020099738A1 (en) | Automated web access for back-end enterprise systems | |
| WO2002027511A1 (en) | System and method for transforming custom content generation tags associated with web pages | |
| JP2002196967A (en) | Method for redirecting source of data object displayed on html document | |
| EP1333374A1 (en) | Dynamic generation of language localized and self-verified Java classes using XML descriptions and static initializers | |
| US20080005182A1 (en) | Changing documents to include changes made to schemas | |
| Gordon et al. | Seahawk: moving beyond HTML in Web-based bioinformatics analysis | |
| US7657869B2 (en) | Integration of external tools into an existing design environment | |
| US20040205587A1 (en) | System and method for enumerating arbitrary hyperlinked structures in which links may be dynamically calculable | |
| US20040221228A1 (en) | Method and apparatus for domain specialization in a document type definition | |
| US7480855B2 (en) | Apparatus and method of highlighting parts of web documents based on intended readers | |
| CA2474109C (en) | Framework for development and customization of web services deployment descriptors | |
| Gill | Building Web Applications with C# and. NET: A Complete Reference | |
| Cazzulino et al. | Beginning Visual Web Programming in VB. NET: From Novice to Professional | |
| Beerman | Collaborative web content management—wiki and beyond | |
| Hague et al. | End‐user programming of reconfigurable systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed | ||
| MKLA | Lapsed |
Effective date: 20120716 |