July 2011
Intermediate to advanced
111 pages
2h 51m
English
Content preview from Practical JIRA PluginsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 6. Storing Data with Your Plugin
Overview
One of the most common questions when adding new functionality to JIRA is “where do I store my plugin’s data?”. The brute-force way is to add new tables or new columns to the database by modifying the file entitydefs/entitymodel.xml, but then all your future upgrades will need to make the same changes.
Two better approaches to storing your data are covered in this
chapter. The first one is to use the same PropertySet interface that JIRA uses for much of
its own configuration data. The second approach is to use the newer Active
Objects plugin, which can handle both more complex data and more of it.
This Atlassian plugin is shipped as part of JIRA 5.0 and later, but can also be
installed separately in JIRA 4.3 and 4.4.
Storing Data with PropertySet
The first approach is to store plugin data where JIRA stores this
kind of configuration data, which is in the propertyentry table. This also has the advantage
of allowing us to use the same classes, such as PropertyUtils, that JIRA uses for accessing the
data. However it is strictly key/value pairs with no idea of relational concepts.
The way that JIRA uses the propertyentry database table is based on the
PropertySet interface from
OpenSymphony. This interface allows you to store unique
“key=value” pairs with various get and set
methods for different types of data.
The propertyentry table is
defined in the entitymodel.xml file,
as shown in Example 6-1. Note that the entity name
OSPropertyEntry ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.