This depends on exactly what you mean, but the best answer is probably "a bit of both". I'll try to give the complete picture of things as best as I can.
UserSettingsServiceis a thin wrapper around its UserPropertyManager, a JIRA-specific API.
UserPropertyManager. It's pretty worthless, except that it presents the properties as a Preferences object from the atlassian-core library. That was a noble but ultimately doomed effort to unify a common cross-product platform and predates SAL. It's mostly useless today, but there are still a few things that need it, like the cron expression editor on the filter subscription page.
UserPropertyManagerdelegates to the JiraPropertySetFactory using the entity name
ApplicationUserand the entity ID of the
app_userrow that corresponds to the user. This is also a JIRA-specific API.
JiraPropertySetFactorycreates instances of an OpenSymphony PropertySet, a typed key-value store in an Open Source library that you can find on BitBucket. The OpenSymphony libraries are best known as the original authors of Webwork (still in JIRA, but most other products have moved on to using Struts). Although
PropertySetis open source, I'm not aware of anybody else that uses it outside of Atlassian.
PropertySetis split across two main ones that JIRA uses (there are several others in existence which JIRA does not use, including those based on Hibernate, non-cluster-safe caching strategies, EJB, and more):
PropertySetlibrary. As you can see in its implementation, it interacts directly with the GenericDelegator from Atlassian's OFBiz Entity Engine Fork. This is a very old fork of a small portion of the Apache OFBiz project. Although OFBiz itself has many products that use it, JIRA is very likely the only consumer of our highly customized fork of its entity engine. (The other Atlassian products use Hibernate for this.)
PropertySetimplementation we use is one that I wrote, and it uses QueryDSL under the hood. That implementation is closed source, but if you have access to JIRA's sources, you can find its implementation split across
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs