Building Qato’s Plugin SDK Using the Atlassian Plugin Platform

Matthew SchmidtCTO - DZone, Inc

Using the Atlassian Plugin Platform To Create Your Own SaaS Plugin Platform

2

• 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

What are DZone and Qato?

3

OSGI is quite possibly the most complicated

framework available for Java today!

Me

”“

4

• 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?

Why Atlassian Plugins?

5

• 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

Atlassian Platform to Qato

6

• 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

• Preferred FreeMarker for views over Velocity

What Did We Change?

7

#summit11 #qato #dzone

The Atlassian Plugin Framework allowed DZone to

quickly and easily add a plugin system to it’s

Enterprise Q&A Platform, Qato.

“”

8