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

Developing extensible software in Java

This thesis addresses the subject of developing extensible software in Java. In the introductory part, the analysis of the process of software development is presented as well as the main reasons why the majority in the IT business world decide to develop extensible software. In the following part we have the two types of extensible software and the most used design pattern in that area (plugins). Analysis of the widely used framework for developing extensible software (OSGi) were made and the facts behind the reasons for not using that framework and developing our own are presented. In the central part of the thesis a deep analysis of our newly developed framework with emphasis on the main problem in developing such framework - security has been made. In the final part we present the usage example to prove that the framework is almost invisible to the end user, and that it doesn't add complexity to the application

Developing extensible software in Java

This thesis addresses the subject of developing extensible software in Java. In the introductory part, the analysis of the process of software development is presented as well as the main reasons why the majority in the IT business world decide to develop extensible software. In the following part we have the two types of extensible software and the most used design pattern in that area (plugins). Analysis of the widely used framework for developing extensible software (OSGi) were made and the facts behind the reasons for not using that framework and developing our own are presented. In the central part of the thesis a deep analysis of our newly developed framework with emphasis on the main problem in developing such framework - security has been made. In the final part we present the usage example to prove that the framework is almost invisible to the end user, and that it doesn't add complexity to the application

Control and Data Flow Execution of Java Programs

Since decade understanding of programs has become a compulsory task for the students as well as for others who are involved in the process of developing software and providing solutions to open problems. In that aspect showing the problem in a pictorial presentation in a best manner is a key advantage to better understand it. We provide model and structure for Java programs to understand the control and data flow analysis of execution. Especially it helps to understand the static analysis of Java programs, which is an uttermost important phase for software maintenance. We provided information and model for visualization of Java programs that may help better understanding of programs for a learning and analysis purpose. The idea provided for building visualization tool is extracting data and control analysis from execution of Java programs. We presented case studies to prove that our idea is most important for better understanding of Java programs which may help towards static analysis, software debugging and software maintenance

Towards Improving Interface Modularity in Legacy Java Software through Automated Refactoring

The skeletal implementation pattern is a software design pattern consisting of defining an abstract class that provides a partial interface implementation. However, since Java allows only single class inheritance, if implementers decide to extend a skeletal implementation, they will not be allowed to extend any other class. Also, discovering the skeletal implementation may require a global analysis. Java 8 enhanced interfaces alleviate these problems by allowing interfaces to contain (default) method implementations, which implementers inherit. Java classes are then free to extend a different class, and a separate abstract class is no longer needed; developers considering implementing an interface need only examine the interface itself. We argue that both these benefits improve software modularity, and discuss our ongoing work in developing an automated refactoring tool that would assist developers in taking advantage of the enhanced interface feature for their legacy Java software