Skip to end of metadata
Go to start of metadata

Backend development has finally reached a stage where we can start experimenting with different end user applications. With two port call visualizations as a starting point, as seen here. Creating new visualisations is a fairly straightforward process at this point, so new ideas can be tested and evaluated. Metro map visualisation Port call overview metroBilden.png 150414-mikael-01.png        
Most of what has been done so far has been in preparation and exploration to figure out how best to achieve the goals for the technical development within our part of MonaLisa 2. From this sprint on, we have moved into the realm of the real world in all of our different sub-projects.…
As our first sprint this year has been completed we are setting the first artefacts that may actually be part of the project deliverables. Development libraries for a number of core and basic services are being finalised, including ETx_manager, Approach_status and Status_update.…
This week has left us with a fully functional, albeit very basic, chain of service from a status update client, via maritime cloud to our status update service, which then geocasts the resulting approach state changes through the approach status service over maritime cloud to an approach status client, making it possible for everyone within a specific geographical area to take part of updates about an approach as it progresses.…
This week, we have progressed quite well in two areas: Sample data and Maritime Cloud integration. Sample data The response to our requests for sample data has been good. We now have data sets from several new systems, including Safe Sea Net (SSN), Fenix and a bigger data set from VTMS, covering all of august 2014. Next week, we'll be meeting with a shipping agency that have shown interest in participating by, initially, contributing sample data. For more details,…

Project resources

Maritime Cloud - development resources
WildFly - application server
PortCDM Data model 
Port Call Message Format 


Development environment - how to set stuff up to work with our code
Software Management - work flow, release calendar and other management info
Creating services
Maven magic
Connecting to services
Apache License 
Release management 
WildFly magic 

Team resources

JIRA - workflow and issue handling
Stash - code repository management
Bamboo - Continous Integration and release management
Crowd - user profile and password
Nexus - deployment artifact repository
Utility tools - some tools we use on our servers 

External references

Weld - the CDI implementation used on Wildfly ( Reference, version 2.2.0 )
Javadoc Guidelines 



  • No labels