Autumn 2014

TIES456 Introduction to SOA and Cloud Computing, 5 ECTS

TIES532 - Service oriented architectures and cloud computing for developers, 5 ECTS

Today

• Feedback on this week’s exercise
• Short presentations
• Reflective questions
• Next weeks exercise

General feedback - Received submissions

• Code seems ok
• Not all could be run
• Group 2 - merge problem? + answers to questions missing
• Also use references when answereing to questions. Especially when taking quotes.

General feedback - Repository structure

• Keep a project structure
  • Repository reflects working setting
  • Do not dump source files in root directory.
  • Do not put compressed files in the repo
• Include group number in project name

Projects - create your own libraries

• Do not copy your code from one project to the other
• Make a jar file instead
  • Simple with Eclipse
    • … or other IDE
• Do include the jars to version control if you do not use a dependency manager.
  • Project ‘groupX’ is missing required library: ‘D:/jstl-1.2.jar’

General feedback - Repository clean-up

• Clean up stuff which is not used.
  • Unused imports, methods, classes
• Check out a clean copy of your repository and see whether you get it working

Coding style - Use of static and Singleton

• Singleton is a widely used design pattern, but
  • horrible for testing
    • No way you can mock it out
  • largely overused
    • performance??
    • Often have data races or synchronization problems
• The same applies to public static methods

Let’s see some code

Questions for discussion

• Most REST services do not use WSDL and SOAP. What could be reasons for this?
• SOAP and WSDL use XML, would it be better if they would use something more modern like JSON?
• How did you handle errors and how should it be done? Imagine that your application is running on a production server.

Questions for discussion 1

• Most REST services do not use WSDL and SOAP. What could be reasons for this?

Questions for discussion 2

• SOAP and WSDL use XML, would it be better if they would use something more modern like JSON?

Questions for discussion 3

• How did you handle errors and how should it be done? Imagine that your application is running on a production server.

Tasks for week 39

• This weeks task …

This week

• Before Thursday
  • Read prerequisite material
• On Thursday and Monday
  • Make the assignment in groups
• Before Monday (23:59)
  • Submit assignment using git (tip of master branch)