Java EE | Lightning Fast Developers Are Only As Fast As Their Tools | Simon Maple & Alasdair Nottingham
2011-11-01 | 03:00 PM - 03:50 PM | Developer productivity is paramount. We cannot live in a world where developers are resting, drinking coffee, enjoying themselves or talking to other people. This does not produce code. Unacceptable! The new WebSphere Application Server V8.5 Alpha tools and runtime have been designed around developer productivity. They truly are super lightweight and lightning fast. We will look at how the Liberty Profile has been designed to meet the high expectations of a development environment, while maintaining it's best of breed attributes around robustness, scalability and transactional integrity. Don't just take my word for it, there will be live demos so you can see the server start in seconds for your own eyes! With developer tools this fast, we can afford to spend some time away from coding, so there will be some coffee related prizes during the session!
![[object Object],wasdev.net](https://image.slidesharecdn.com/lightningdevs-111111040700-phpapp02/85/Java-EE-Lightning-Fast-Developers-Are-Only-As-Fast-As-Their-Tools-Simon-Maple-Alasdair-Nottingham-1-320.jpg)
![[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (16)
Mais de JAX London
Mais de JAX London (20)
Último
Último (20)
Java EE | Lightning Fast Developers Are Only As Fast As Their Tools | Simon Maple & Alasdair Nottingham
- 4. Lightweight
- 9. WAS fidelity
- 10. WASdev community
- 13. Debug a problem in an application
- 15. Restart server
- 16. Share code with team
- 17. Change app structure (add/remove a module/bundle)
- 19. Share config change with team
- 20. Reproduce problem from another environment
- 21. Upgrade to new service release
- 27. Moving an application between development machines
- 31. Clearly identify the location of problems in the application, helping developers to identify bugs
- 32. Never show stack traces, unless they come from the application. Users should never be able to tell the server is written in Java
- 33. Clearly differentiate between internal errors and an error in the application
- 36. Be robust – same behavior as reinstalling/restarting the app
- 37. Have minimal loss of context – to reduce retesting
- 38. Be fine-grained – or it won’t perform (esp. remote)
- 44. Server must work well on older laptops, with slower hard drives, constrained memory, and shared with tools, email, and web browser
- 46. Startup time
- 51. But radically refactored to focus on the development experience
- 55. Extends Eclipse JEE Helios (3.6) and Indigo (3.7)
- 57. Within Eclipse (Help MarketPlace)
- 60. New lightweight “WAS Liberty profile” is now available through the WAS V8.5 Open Alpha program.
Notas do Editor
- The Top 4 Developer Priorities are: Incremental Publishing This is the most frequent (and hence most important) developer task. It must be easy (robust, consistent, fast) to make changes in a running application Simple Configuration It must be easy to configure the server for an application, compare changes, share among a team, and promote to production Problem Determination Applications are always broken during development - due to bugs, missing or incomplete code, or bad configuration. The server must make it easy for developers to identify and resolve problems within their application Performance Performance focus for development (single user, low throughput) is very different than production. Incremental publishing, startup, and app install must work well on older laptops with slower hard drives and constrained memory Lets look at each in turn starting with Incremental Publishing.