1 / 30

An Open Development Platform

An Open Development Platform. Mike Milinkovich mike@eclipse.org Executive Director Eclipse Foundation. Agenda. Brief overview of Eclipse Why open source matters for Web Services and SOA Web Services and Rich Clients How to get involved. Hidden Agenda.

kevina
Download Presentation

An Open Development Platform

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. An Open Development Platform Mike Milinkovich mike@eclipse.org Executive Director Eclipse Foundation

  2. Agenda • Brief overview of Eclipse • Why open source matters for Web Services and SOA • Web Services and Rich Clients • How to get involved

  3. Hidden Agenda Open source implementations of standards-based runtimes, tools and testing frameworks are vital to the pervasive success of Web Services.

  4. What is Eclipse? • Eclipse is an open source community focused on developing a universal platformof frameworks and exemplary tools that make it easy and cost-effective to build and deploy software in today’s connected and unconnected world. • Eclipse is a consortium of major software vendors, solution providers, corporations, educational and research institutions and individuals working together to create an eco-system that enhances, promotes and cultivates the Eclipse open platform with complementary products, services and capabilities.

  5. The Members of Eclipse • 9 Strategic Members • 62 Add-in Providers • 14 Associate Members (Publishers, Research Institutes, Standards Org., etc.) • Large community of open source developers

  6. Eclipse Eco-System – Community of Add-in Providers • 600+ available Eclipse add-ins • 400+ Eclipse based projects on SourceForge www.eclipse-plugins.info www.eclipseplugincentral.com www.surceforge.net

  7. Enterprise IT Borland Together Edition for Eclipse HP OCMP OClet Development Env. IBM WSAD SAP NetWeaver Studio Linux Novell/SuSE Linux SDK Red Hat Developer Studio Intel Compiler for Linux BPM Oracle Collaxa BPEL Designer IBM WBI Embedded PalmOS Dev Suite Monta Vista DevRocket Wind River Workbench QNX Momentics TimeSys TimeStorm IDE Tensilica Xtensa Xplorer IDE Mentor Graphics Nucleus Edge Examples of Eclipse Based Commercial Tools

  8. Why open source matters for Web Services and SOA

  9. Web Services are About Interoperability Company B Company A

  10. ? Vendor A Vendor C Vendor A Vendor C Vendor C Vendor B Vendor B ? Interoperability with Multiple Vendors • Different implementation of standards • ‘Value add’ proprietary extensions • Implementation of a web service does not conform to standard • Result: Lots of interoperability testing

  11. Where problems may arise • Implementation of Web Service Runtime (SOAP Engine) • Each vendor implements standards differently • Different interpretation of standards • ‘Value add’ proprietary features • Optimization to certain environments (security, transactional, reliability, XML compression) • Implementation of specific web service • Is the web service using well formed WSDL? • Does the web service support the WS-I Basic Profile? • E.g. exclude SOAP encoding

  12. Learn from the Past: Success of the Internet • Early 1990’s Internet starts to take off • TCP/IP and HTML become accepted standards • Most major software vendors develop HTML web servers • Apache evolves from NCSA and becomes dominant web server • It was good and free! • Commercial friendly license • Software vendors adopt Apache or ensure interoperability • IBM, Oracle, etc adopted Apache • The result: an Internet which is pervasively available and free Open source provides the platform

  13. Key to Success for Interoperability • Open Standards • OASIS, W3C, WS-I • Pervasive open source reference implementations • Forces vendors to adhere to standards to ensure interoperability • Royalty free software promotes quick adoption • Open source implementation must be commercial quality • Freely available tools to create, test and deploy web services • Ensures web services conform to standards, ex WS-I Basic Profile

  14. Open Development Platform • Eclipse, Mono, Netbeans • Consistent implementation and validation environment Open Source Platform • OASIS, W3C, WS-I • XML, SOAP, WSDL • Consistent Meta-data Open Standards Open Source Runtimes • ObjectWeb, Apache • Consistent execution environment

  15. Characteristics of a Development Platform • Based on a managed runtime • Operating system neutral and portable • Semantically rich component model • Application frameworks which are extensible • Support update and management capabilities • Rich, extensible toolset appealing to both ISVs and application developers • Broad industry support and an active ecosystem

  16. And in a Perfect World…. • The development platform provides tools that cover the entire software development life-cycle. • Model, Design, Develop, Test, Deploy, Monitor, Manage • Provides choice at each point in the tool chain • Single vendor tools suite vs. integrating best of breed • Is customizable for specific tasks, languages, runtimes • Ex. How do you support the wide range of J2EE servers • Supports all of your favourite operating systems • Has critical mass • Broad ecosystem of users, vendors, research, open source developers, education, etc

  17. Java Dev Tools C/C++ Dev Tools Test and Performance Web Tools Web Services Web applications J2EE Business Intelligence & Reporting Frameworks Modeling Frameworks Graphical Frameworks Tools Platform Project Model Rich Client Platform Runtime(OSGi) Generic Workbench Update Eclipse Open Development Platform Ecosystem

  18. Delivering the Vision • A sampling of Eclipse development solutions for: • Web Services • J2EE • Test and Performance • Rich Client Platform

  19. Eclipse Web Tools • Focus on making it easy to create applications based on the common web, Java and web services standards • HTML, XML, XSL, CSS • SOAP, WSDL, WS-I Profile • J2EE: Servlet, JSP, EJB • Make it easy to deploy and validate for the common open source runtime environments and extensible for targeting commercial ones • JOnAS, JBoss, Apache Geronimo Eclipse Web Tools W3C JCP WS-I JOnAS JBoss Apache

  20. Eclipse Web Services Eclipse Web Tools • Creation wizard based on W3C spec for WSDL and SOAP • Validation tools for WS-I profile (Eclipse WSVT Project) • Deployment support based on JSR 109 for JOnAS and Apache W3C WSDL WS-I Profile JCP WSDL File JOnAS Apache Axis

  21. Web Service Tools in Eclipse Web Tools Project • Web Standard Tools • WSDL/XSD Editor • Web Service Explorer • Discover, Test, Publish • Web Service Wizard • WS-I Test Tools • WS-I Basic Profile 1.0/1.1, Simple SOAP Binding Profile 1.0, Attachments Profile 1.0 • J2EE Standard Tools • J2EE Explorer • JAX-RPC • JSR 109 • Axis 1.0

  22. Eclipse J2EE Tools Eclipse Web Tools • Creation wizard for servlets, EJB, JSP • Deployment support to multiple J2EE runtimes • Annotation based programming using XDOCLET W3C WSDL WS-I Profile JCP Servlets EJB JSP JOnAS JBoss

  23. Eclipse Test and Performance Tools • HTTP Load testing • Support for JVMPI to generate trace • Support for JMX to monitor a Java runtime • CBE (Common Base Event) format support for correlating log files • Monitor Linux operation system • Support for U2TP (UML Test Profile) to define test cases and report on execution Eclipse Test Tools Open Standard JOnAS Apache Linux

  24. Rich Clients and Web Services • Rich clients will supplant portals as the primary interface to Web Services & Service-oriented functionality in the enterprise by the end of 2007 • Projected market size of $932M by 2010 for standalone rich client technology • Over 80% of business application products sold between 2005 and 2008 will be Service Oriented Business Applications (SOBA) (Gartner) Workplace Competitive Analysis: Lotus Competitive Project Office, November 3, 2004

  25. Custom development of rich client applications • Fat Client Applications • Rich User Experience • Difficult to manage and update • Difficult to support multi-platforms • Rich Client Applications • Rich user experience • Works disconnected • Native platform support • Ease to update • Consumer of Web services Sophisticated User Experience • Browser Applications • Easy to Deploy • Need to be connected • Limited user interface Simple Ease of deployment and management Difficult Easy

  26. Eclipse Rich Client Platform • Generic workbench • Extensible infrastructure • Editors, hierarchical lists, template for views and layouts • Runs on variety of platforms • Integrated help system • Pluggable component model • Based on OSGI standard • Update manager • Discovery of new plug-ins • Product packaging allows for custom branding of deployed applications • Native support for Windows, Linux GTK and Motif, Mac OS X, AIX, HP/UX, and Solaris

  27. Custom Development of Rich Client Applications • ISVs are moving towards building rich client applications for their power users • Require support for Linux and Windows • Require component model • Require ability to update • Enterprises looking towards building rich client applications on Linux • Need a coexistence strategy with Windows

  28. Eclipse Open Community • Become an Eclipse user and tell your friends • Test and report bugs • Write tutorials, articles • Fix bugs • Become a committer • Develop plug-ins based on WTP or others • Help wanted, e.g.: • Axis 1.1/1.2 support • WSDL 2.0 test suite (W3C) and validator • New WS-I profiles • Attend EclipseCon 2005

  29. Open Communities: Engine of Innovation • Level playing field encourages participation from all • Shared intellectual property reduces cost and risk when adopting new technologies for both vendors and customers • Openness that makes it difficult for a single vendor to control • Result is a powerful platform for open innovation Open Standards Open Source Runtimes Open Source Development Platform

  30. Questions Thank you!

More Related