Java Specification Request development on a mobile device

Nykyaikaiset Java-teknologiaa sisältävät matkapuhelimet kehittyvät vauhdikkaasti prosessoritehon, muistin määrän sekä uusien käyttöjärjestelmäversioiden tarjoamien ominaisuuksien myötä. Laitteiden näyttöjen koko tulee pysymään pienenä,mutta silti moninaista multimediasisältöä äänen, videon ja kuvan osilta voidaanhuomattavasti parantaa JSR 234:n eli kehittyneen multimedialaajennuksen avulla.Erityisesti edistyneet ääniominaisuudet ovat tervetullut lisä, sillä viime aikojen kehitys matkapuhelimissa on saanut aikaan niiden muuntumisen myös kannettavaksi musiikkisoittimiksi. Diplomityössä JSR 234 -spesifikaation tietty osa kehitettiin ympäristössä, joka koostui Series 60 -ohjelmistoalustankolmannesta versiosta sekä Symbian OS v9.1 käyttöjärjestelmästä. Tuloksena syntynyt Java-rajapinta tarjoaa sovelluskehittäjille yksinkertaisemman lähestymistavan Symbianin efektirajapintaan piilottaen samalla alla olevan käyttöjärjestelmänmonimutkaisuuden. Toteutuksen täytyy olla läpikotaisin testattu, jotta voidaan varmentua sen noudattavan tarkkaan JSR 234 -spesifikaatiota. Työssä on esitelty useita eri testausmenetelmiä tarkoituksena saavuttaa projektissa paras mahdollinen laatu.

Optimizing Mobile Java Location-Based Services in Symbian OS

This thesis evaluates methods for obtaining high performance in applications running on the mobile Java platform. Based on the evaluated methods, an optimization was done to a Java extension API running on top the Symbian operating system. The API provides location-based services for mobile Java applications. As a part of this thesis, the JNI implementation in Symbian OS was also benchmarked. A benchmarking tool was implemented in the analysis phase in order to implement extensive performance test set. Based on the benchmark results, it was noted that the landmarks implementation of the API was performing very slowly with large amounts of data. The existing implementation proved to be very inconvenient for optimization because the early implementers did not take performance and design issues into consideration. A completely new architecture was implemented for the API in order to provide scalable landmark initialization and data extraction by using lazy initialization methods. Additionally, runtime memory consumption was also an important part of the optimization. The improvement proved to be very efficient based on the measurements after the optimization. Most of the common API use cases performed extremely well compared to the old implementation. Performance optimization is an important quality attribute of any piece of software especially in embedded mobile devices. Typically, projects get into trouble with performance because there are no clear performance targets and knowledge how to achieve them. Well-known guidelines and performance models help to achieve good overall performance in Java applications and programming interfaces.

SimpleREST -RESTful DSpace API

Poster at Open Repositories 2014, Helsinki, Finland, June 9-13, 2014

MPJ express: Towards thread safe Java HPC

MPJ Express is a thread-safe Java messaging library that provides a full implementation of the mpiJava 1.2 API specification. This specification defines a MPI-like bindings for the Java language. We have implemented two communication devices as part of our library, the first, called niodev is based on the Java New I/O package and the second, called mxdev is based on the Myrinet eXpress library MPJ Express comes with an experimental runtitne, which allows portable bootstrapping of Java Virtual Machines across a cluster or network of computers. In this paper we describe the implementation of MPJ Express. Also, we present a performance comparison against various other C and Java messaging systems. A beta version of MPJ Express was released in September 2005.

BSmart: desenvolvimento rigoroso de aplicações Java Card com base no método formal B

Java Card technology allows the development and execution of small applications embedded in smart cards. A Java Card application is composed of an external card client and of an application in the card that implements the services available to the client by means of an Application Programming Interface (API). Usually, these applications manipulate and store important information, such as cash and confidential data of their owners. Thus, it is necessary to adopt rigor on developing a smart card application to improve its quality and trustworthiness. The use of formal methods on the development of these applications is a way to reach these quality requirements. The B method is one of the many formal methods for system specification. The development in B starts with the functional specification of the system, continues with the application of some optional refinements to the specification and, from the last level of refinement, it is possible to generate code for some programming language. The B formalism has a good tool support and its application to Java Card is adequate since the specification and development of APIs is one of the major applications of B. The BSmart method proposed here aims to promote the rigorous development of Java Card applications up to the generation of its code, based on the refinement of its formal specification described in the B notation. This development is supported by the BSmart tool, that is composed of some programs that automate each stage of the method; and by a library of B modules and Java Card classes that model primitive types, essential Java Card API classes and reusable data structures

KitSmart: Uma biblioteca de componentes para o desenvolvimento rigoroso de aplicações Java Card com o método B

The development of smart card applications requires a high level of reliability. Formal methods provide means for this reliability to be achieved. The BSmart method and tool contribute to the development of smart card applications with the support of the B method, generating Java Card code from B specifications. For the development with BSmart to be effectively rigorous without overloading the user it is important to have a library of reusable components built in B. The goal of KitSmart is to provide this support. A first research about the composition of this library was a graduation work from Universidade Federal do Rio Grande do Norte, made by Thiago Dutra in 2006. This first version of the kit resulted in a specification of Java Card primitive types byte, short and boolean in B and the creation of reusable components for application development. This work provides an improvement of KitSmart with the addition of API Java Card specification made in B and a guide for the creation of new components. The API Java Card in B, besides being available to be used for development of applications, is also useful as a documentation of each API class. The reusable components correspond to modules to manipulate specific structures, such as date and time. These structures are not available for B or Java Card. These components for Java Card are generated from specifications formally verified in B. The guide contains quick reference on how to specify some structures and how some situations were adapted from object-orientation to the B Method. This work was evaluated through a case study made through the BSmart tool, that makes use of the KitSmart library. In this case study, it is possible to see the contribution of the components in a B specification. This kit should be useful for B method users and Java Card application developers

JavaFMI una librería Java para el estándar Functional Mockup Interface

[ES] El estándar Functional Mockup Interface (FMI), es un estándar abierto e independiente de cualquier aplicación o herramienta que permite compartir modelos de sistemas dinámicos entre aplicaciones. Provee una interfaz escrita en lenguaje C que ha de ser implementada por las distintas herramientas exportadoras y pone en común un conjunto de funciones para manipular los modelos.
JavaFMI es una herramienta que permite utilizar simulaciones que cumplen con el estándar FMI en aplicaciones Java de una manera muy simple, limpia y eficiente. Es un proyecto open source con licencia LGPL V2.1H y su código fuente se encuentra disponible para ser clonado en la pagina del proyecto. El proyecto se encuentra alojado en www.bitbucket.org/siani/javafmi y cuenta con una página de bienvenida donde se explica como se usa la librería, una página para reportar incidencias o solicitar que se implementen nuevas historias y una página donde se listan todas las versiones que hay disponibles para descargar. JavaFMI se distribuye como un fichero zip que contiene el .jar con el código compilado de la librería una carpeta lib con las dos dependencias que tiene con librerías externas y una copia de la licencia. Comparada con JFMI, con menos lineas de código, una API limpia, expresiva y auto documentada, y un rendimiento que es un 66 % mejor, JavaFMI es objetivamente la mejor herramienta Java que existe para manipular FMUs de la versión 1.0 y 2.0 del estándar FMI.

Adjusting WSMO API Reference Implementation to Support More Reliable Entity Persistence

* The research has been partially supported by INFRAWEBS - IST FP62003/IST/2.3.2.3 Research Project No. 511723 and “Technologies of the Information Society for Knowledge Processing and Management” - IIT-BAS Research Project No. 010061.

Sensitization Prevalence, Antibody Cross-Reactivity and Immunogenic Peptide Profile of Api g 2, the Non-Specific Lipid Transfer Protein 1 of Celery

Background: Celery (Apium graveolens) represents a relevant allergen source that can elicit severe reactions in the adult population. To investigate the sensitization prevalence and cross-reactivity of Api g 2 from celery stalks in a Mediterranean population and in a mouse model. Methodology: 786 non-randomized subjects from Italy were screened for IgE reactivity to rApi g 2, rArt v 3 (mugwort pollen LTP) and nPru p 3 (peach LTP) using an allergen microarray. Clinical data of 32 selected patients with reactivity to LTP under investigation were evaluated. Specific IgE titers and cross-inhibitions were performed in ELISA and allergen microarray. Balb/c mice were immunized with purified LTPs; IgG titers were determined in ELISA and mediator release was examined using RBL-2H3 cells. Simulated endolysosomal digestion was performed using microsomes obtained from human DCs. Results: IgE testing showed a sensitization prevalence of 25.6% to Api g 2, 18.6% to Art v 3, and 28.6% to Pru p 3 and frequent co-sensitization and correlating IgE-reactivity was observed. 10/32 patients suffering from LTP-related allergy reported symptoms upon consumption of celery stalks which mainly presented as OAS. Considerable IgE cross-reactivity was observed between Api g 2, Art v 3, and Pru p 3 with varying inhibition degrees of individual patients' sera. Simulating LTP mono-sensitization in a mouse model showed development of more congruent antibody specificities between Api g 2 and Art v 3. Notably, biologically relevant murine IgE cross-reactivity was restricted to the latter and diverse from Pru p 3 epitopes. Endolysosomal processing of LTP showed generation of similar clusters, which presumably represent T-cell peptides. Conclusions: Api g 2 represents a relevant celery stalk allergen in the LTP-sensitized population. The molecule displays common B cell epitopes and endolysosomal peptides that encompass T cell epitopes with pollen and plant-food derived LTP.

White stem borer damage and grain yield in irrigated rice in West Java, Indonesia

Factors influencing the relationship between whiteheads caused by the white stem borer Scirpophaga innotata (Walker) and grain yield were investigated. We determined the effect of different numbers of whiteheads on grain yield using different cultivars, nitrogen application, and at different field locations in Cilamaya, West Java. At the same number of panicles and whiteheads per plant, yield reduction is greater in cisadane than in IR64. With increasing nitrogen application, the range in panicle height increased. Except for Ketan, more whiteheads were recorded in shorter panicles. Two locations planted to the same cultivar showed different relationships between whiteheads and grain yield. The relationship between whiteheads and grain yield depends on the distribution of whiteheads in the field. Unless these factors have been taken into consideration, it may be difficult to make a damage prediction of white stem borer in the field. (C) 1997 Published by Elsevier Science Ltd.