Generic model for application driven XML data processing

Abstract XML technology has emerged during recent years as a popular choice for representing and exchanging semi-structured data on the Web. It integrates seamlessly with web- based applications. If data is stored and represented as XML documents, then it should be possible to query the contents of these documents in order to extract, synthesize and analyze their contents. This thesis for experimental study of Web architecture for data processing is based on semantic mapping of XML Schema. The thesis involves complex methods and tools for specification, algorithmic transformation and online processing of semi- structured data over the Web in XML format with persistent storage into relational databases. The main focus of the research is preserving the structure of original data for data reconciliation during database updates and also to combine different technologies for XML data processing such as storing (SQL), transformation (XSL Processors), presenting (HTML), querying (XQUERY) and transporting (Web services) using a common framework, which is both theoretically and technologically well grounded. The experimental implementation of the discussed architecture requires a Web server (Apache), Java container (Tomcat) and object-relational DBMS (Oracle 9) equipped with Java engine and corresponding libraries for parsing and transformation of XML data (Xerces and Xalan). Furthermore the central idea behind the research is to use a single theoretical model of the data to be processed by the system (XML algebra) controlled by one standard metalanguage specification (XML Schema) for solving a class of problems (generic architecture). The proposed work combines theoretical novelty and technological advancement in the field of Internet computing. This thesis will introduce a generic approach since both our model (XML algebra) and our problem solver (the architecture of the integrated system) are XML Schema- driven. Starting with the XML Schema of the data, we first develop domain-specific XML algebra suitable for data processing of the specific data and then use it for implementing the main offline components of the system for data processing

Scala Server Faces

Progress in the Java language has been slow over the last few years. Scala is emerging as one of the probable successors for Java with features such as type inference, higher order functions, closure support and sequence comprehensions. This allows object-oriented yet concise code to be written using Scala. While Java based MVC frameworks are still prevalent, Scala based frameworks along with Ruby on Rails, Django and PHP are emerging as competitors. Scala has a web framework called Lift which has made an attempt to borrow the advantages of other frameworks while keeping code concise. Since Sun’s MVC framework, Java Server Faces 2.0 and its future versions seem to be heading in a reasonably progressive direction; I have developed a framework which attempts to overcome its limitations. I call such a framework ―Scala Server Faces‖. This framework provides a way of writing Java EE applications in Scala yet borrow from the concept of ―convention over configuration‖ followed by rival web frameworks. Again, an Eclipse tool is provided to make the programmer\u27s task of writing code on the popular Eclipse platform. Scala Server Faces, the framework and the tool allows the programmer to write enterprise web applications in Scala by providing features such as templating support, CRUD screen generation for database model objects, an Ant script to help deployment and integration with the Glassfish Application Server

A gentle transition from Java programming to Web Services using XML-RPC

Exposing students to leading edge vocational areas of relevance such as Web Services can be difficult. We show a lightweight approach by embedding a key component of Web Services within a Level 3 BSc module in Distributed Computing. We present a ready to use collection of lecture slides and student activities based on XML-RPC. In addition we show that this material addresses the central topics in the context of web services as identified by Draganova (2003)

A model-based approach to language integration

The interactions of several languages within a soft- ware system pose a number of problems. There is several anecdotal and empirical evidence supporting such concerns. This paper presents a solution to achieve proper language integration in the context of language workbenches and with limited effort. A simple example is presented to show how cross- language constraints can be addressed and the quality of the support attainable, which covers error-checking and refactoring. A research agenda is then presented, to support future work in the area of language integration, taking advantage of modern language workbenches features

A Survey Paper on Service Oriented Architecture Approach and Modern Web Services

Service-Oriented Architecture is an architectural design pattern based on distinct pieces of software providing application functionality as services to other applications via a protocol. It is a collection of micro-services which are self-contained and provides unit functionality. The architectural style has the following essential core features which are inter-operability, service abstraction, service discovery, service autonomy, service statelessness re-usability, loose coupling. Service-oriented architectures are not a new thing. The first service-oriented architecture for many people in the past was with the use DCOM (uses RPC – Remote Procedural Calls) and CORBA (uses IIOP protocol) but because of the lack of standards and also with the advent of modern web development (Web 2.0) and the use of mobile phones and their penetration service oriented architecture is being implemented as Web Services (uses mainly HTTP/HTTPS) protocol. Most common implementations of Web Services can be done as SOAP (Simple Object Access Protocol)-based which essentially is a HTTP/HTTPS POST with an XML payload in it. SOAP based web services expose service interface using WSDL (Web Service Description Language) and there is a pre-defined contract via XSD (XML Schema Definition) between the service being exposed and the client side that consumes this service. The other most popular lightweight implementation of web services is using RESTful (Representational State Transfer) architecture where the payload is in JSON (Java Script Object Notation) / XML and uses RESTful style of communication to access resources on the server. So any application written in any language for example C# or C++ or C or Groovy or Java that can make a HTTP call should be able to access the services and since the data is in XML/JSON they can make a sense of data and this way we can re-use services and be inter-operable. The goal of our survey is to delve deeper into SOA principles, key constituents and how Web Services - implementation of SOA has taken this into such a wide spread usage and created a phenomena and various technologies that can be used to develop/consume web services and also about the protocols being used and some common use cases in building re-usable and scalable application architectures using web services

Java ME Clients for XML Web Services

Using Web services in developing applications has many advantages like the existence of standards, multiple software platforms that support them, and many areas of usage. These advantages derive from the XML and Web technologies. This paper describes the stages in the development of a Web service client for Java ME platform and presents examples based on kSOAP and JSR 172.Web services, mobile applications, Java ME, SOAP, XML, m-learning

Semantically Resolving Type Mismatches in Scientific Workflows

Scientists are increasingly utilizing Grids to manage large data sets and execute scientific experiments on distributed resources. Scientific workflows are used as means for modeling and enacting scientific experiments. Windows Workflow Foundation (WF) is a major component of Microsoft’s .NET technology which offers lightweight support for long-running workflows. It provides a comfortable graphical and programmatic environment for the development of extended BPEL-style workflows. WF’s visual features ease the syntactic composition of Web services into scientific workflows but do nothing to assure that information passed between services has consistent semantic types or representations or that deviant flows, errors and compensations are handled meaningfully. In this paper we introduce SAWSDL-compliant annotations for WF and use them with a semantic reasoner to guarantee semantic type correctness in scientific workflows. Examples from bioinformatics are presented