3. Using the Atlassian Plugin Platform To
Create Your Own SaaS Plugin Platform
Building Qato’s Plugin SDK Using the
Atlassian Plugin Platform
Matthew Schmidt
CTO - DZone, Inc
2

4. What are DZone and Qato?
• Leading Publisher For
Developer Topics
• Java, DevOps, Agile, Cloud
• Enterprise-class Question
and Answer Platform
• Skinnable, Pluggable, Scalable
• Powered by Java, offered as
SaaS, extensible with Atlassian
Plugin Platform 3

5. “ OSGI is quite possibly the most complicated
framework available for Java today!
”
Me
4

6. Why Atlassian Plugins?
• KISS - Don’t Reinvent the Wheel!
• Great abstraction of SpringDM and Felix
• Java development without the application server restart
• Proven in the enterprise
• Easier collaboration with Atlassian users
• What if you could easily integrate your wiki with your Q&A?
5

7. Atlassian Platform to Qato
• Atlassian: Not meant for multiple copies of plugins
• Qato: Admin installs plugins, Tenant enables
• Qato: Sites must be able to enable different plugins
• Qato: Plugins must not affect the other Tenants
• Theme overrides and new translations are very important
6

8. What Did We Change?
• Catch plugin events from core Atlassian components and tie them to
the proper Tenant
• Support for traditional Spring annotations in plugins
• @Autowired
• @Controller
• @RequestMapping
• @Secured
7
• Preferred FreeMarker for views over Velocity

9. “ The Atlassian Plugin Framework allowed DZone to
quickly and easily add a plugin system to it’s
Enterprise Q&A Platform, Qato.
”
#summit11 #qato #dzone
8