Public

<init>

additionalProperties

dependencies

maxProperties

minProperties

patternProperties

List

Parsing JSON documents to java classes using gson

This class implements a simple HTTP server. A HttpServer is bound to an IP
address and port number a

com.sun.net.httpserver.HttpServer

A thread is a thread of execution in a program. The Java Virtual Machine allows
an application to ha

java.lang.Thread

Formats or parses dates and times.This class provides factories for obtaining
instances configured f

java.text.DateFormat

Factory and utility methods for Executor, ExecutorService,
ScheduledExecutorService, ThreadFactory, 

java.util.concurrent.Executors

javax.management.Notification

Abstract superclass of object loading (and querying) strategies. This class
implements useful common

org.hibernate.loader.Loader

compareTo

startActivity

notifyDataSetChanged

/**
 * A container class used for generation of JSON schema for common modules.
 */

/**
     * The Web Item module allows you to define new links in application menus.
     */

/**
     * The Web Panel module allows you to define panels, or sections, on an HTML page.
     * A panel is an iFrame that will be inserted into a page.
     */

/**
     * The Web Section plugin module allows you to define new sections in application menus.
     */

/**
     * The Web Hook module allows you be notified of key events that occur in the host product
     */

/**
     * A general page module is used to provide a generic chrome for add-on content in the product.
     */

/**
     * An admin page module is used to provide an administration chrome for add-on content.
     */

/**
     * A configure page module is a page module used to configure the add-on itself.
     * It's link will appear in the add-ons entry in 'Manage Add-ons'.
     */

/**
     * A post-install page module is used to provide information about the add-on after it is installed.
     * It's link will appear in the add-ons entry in 'Manage Add-ons'.
     */

/**
     * The Dialog module allows you to define re-usable dialog components.
     */

/**
     * The Keyboard Shortcut module allows to define shortcuts.
     */

/**
 * A container class used for generation of JSON schema for Confluence modules.
 */

/**
     * Dynamic content macros allow you to add a macro into a Confluence page which is rendered as an iframe.
     */

/**
     * A User Profile Page module is used to add new elements to Confluence user profiles.
     */

/**
     * The Space Tools Tab module allows you to add new tabs to the Space Tools area of Confluence.
     */

/**
     * Static content macros allow you to add a macro into a Confluence page which is stored with the Confluence page
     * itself. The add-on is responsible for generating the rendered XHTML in
     * [Confluence Storage Format](https://confluence.atlassian.com/display/DOC/Confluence+Storage+Format)
     */

/**
     * Blueprints allow your connect add on provide content creation templates.
     */

/**
     * Themes, useful for overriding confluence's UI.
     */

/**
     * Definition of a content property index schema for an add-on. It allows extracting specific parts of the JSON
     * documents stored as a content property values, and write them to a search index. Once stored,
     * they can participate in a content search using CQL.
     */

/**
     * Byline modules allow your Connect add on to add dynamic content to the Confluence "by-line".
     */

/**
     * Custom content allow your Connect add-on to provide customized content types like builtin Page and BlogPost to Confluence.
     */

"A key to identify the control. Keys must only contain alphanumeric characters and dashes, and must be unique"

/**
     * Text which will appear inside the button
     */

/**
 * When writing the docs remember to mention that:
 * - max length of each translation is 1KB
 * - the file size is limited to 32KB
 */

/**
 * Page modules allow add-ons to insert new pages into Atlassian products. These can be automatically resized to the width
 * and height of your add-on's content. The location attribute defines where links to the new page appear.
 *
 * Each type of page displays differently:
 * <ul>
 * <li><code>generalPages</code> - have no extra styling and by default a link to the page is displayed in the main navigation menu.
 * Use these pages for displaying general content.</li>
 * <li><code>adminPages</code> - display in the administration area. Appropriate menus and other styling appear around your content.
 * Use these pages for providing extra administration functionality.</li>
 * <li><code>profilePages</code> - (Confluence only) displayed as sections inside user profiles. Use these pages for 
 * displaying extra user profile information.</li>
 * </ul>
 * 
 * You can also define page modules to be shown when a user is administering your add-on via the
 * [Universal Plugin Manager](https://confluence.atlassian.com/x/z4Q5Eg). An add-on can only define a single page of
 * each of these types. They should each be defined in the descriptor as a single JSON object, not as a JSON array like 
 * other modules.
 * <ul>
 * <li><code>configurePage</code> - a "Configure" button will link to this page from the add-on's entry in Manage Add-ons.
 * Use this page to provide configuration of the add-on itself.</li>
 * <li><code>postInstallPage</code> - A "Get Started" button will link to this page from both the add-on's entry in Manage Add-ons
 * and from the dialog that the user is shown when they successfully install the add-on. Use this page to provide introductory
 * information about the add-on to the user.</li>
 * </ul>
 *
 *
 * 
 *
 * The content for a page module is injected into the Atlassian application in the form of a "seamless" iframe.
 * Seamless iframes are regular HTML iframes but with the characteristics described below.
 *
 * As implied here, for most page content modules, you do not need to be concerned with iframe sizing.
 * It's all handled for you. However, an exception exists for inline macros.
 * <ul>
 * <li>Their size is based on the page height and width inside the iframe (i.e., no scrollbars)</li>
 * <li>They are dynamically resized based on the inner content or relative browser window sizing</li>
 * <li>They appear without borders, making them look like a non-iframed fragment of the page</li>
 * <li>For general-pages, you can also opt to size your iframe to take up all of the host product's available vertical space (instead of resizing to its internal content).</li>
 * <li>To do this, add the <code>data-options</code> attribute <code>"sizeToParent:true"</code> in the script tag for <code>all.js</code>. It is also possible to hide footer for such pages.</li>
 * <li>For example, using <a href="https://bitbucket.org/atlassian/atlassian-connect-express">ACE</a>:
 *
 * <pre><code>
 *&lt;script src=&quot;{{hostScriptUrl}}&quot;
 * type=&quot;text/javascript&quot;
 * data-options=&quot;sizeToParent:true;hideFooter:true&quot;&gt;
 *&lt;/script&gt;
 * </code></pre></li>
 * </ul>
 *
 * <h2>Example</h2>
 *
 * @schemaTitle Page
 * @exampleJson {@link com.atlassian.plugin.connect.modules.beans.ConnectJsonExamples#PAGE_EXAMPLE}
 * @since 1.0
 */

"Conditions can be added to display only when all the given conditions are true.\n\n"

"The only supported conditions for pages are:\n"

"<li><code>entity_property_equal_to</code>\n"

/**
     * The url to retrieve the content from.
     * This must be relative to the add-on's baseUrl. 
     */

// Note: weight is not defaulted here. Defaulting is done later by delegating to the product accessor

/**
     * Specifies the URL targeted by the page. The URL is relative to the add-on's base URL.
     *
     * @return the URL of the page
     */

/**
     * Determines the order in which the page's link appears in the menu or list.
     *
     * The "lightest" weight (i.e., lowest number) appears first, rising relative to other items,
     * while the "heaviest" weights sink to the bottom of the menu or list.
     *
     * Built-in web items have weights that are incremented by numbers that leave room for additional
     * items, such as by 10 or 100. Be mindful of the weight you choose for your item, so that it appears
     * in a sensible order given existing items.
     *
     * @return the weight of the page
     */

/**
     *  An optional icon to display with the link text or as the link, specified by URL to its hosted location.
     *  You can specify a particular width and height for the icon. Most link icons in Atlassian applications
     *  are 16 by 16 pixels.
     *
     * @return the icon associated with the link to the page
     */

/**
 * The location in the application interface where the page's link should appear. For the Atlassian application
 * interface, a location is something like the coordinates on a map. It points to a particular drop-down menu or
 * navigation list in the UI.
 *
 * Places in the Atlassian UI are identified by what are known as "well-known locations."
 * For example, the "system.admin/globalsettings" location is in the administrative
 * menu link on the left side of the Administration Console.
 *
 * Product location documentation:
 *
 * <ul>
 * <li><a href="https://developer.atlassian.com/display/JIRADEV/Web+Fragments">JIRA locations</a></li>
 * <li><a href="https://developer.atlassian.com/display/CONFDEV/Web+UI+Modules">Confluence locations</a></li>
 * </ul>
 *
 * If the <code>location</code> property is not specified, a default location is used:
 *
 * JIRA:
 *
 * <ul> 
 * <li><code>generalPage</code>: system.top.navigation.bar</li>
 * <li><code>adminPage</code>: advanced\_menu\_section/advanced_section</li>
 * </ul> 
 *
 * Confluence:
 *
 * <ul>
 * <li><code>generalPage</code>: system.browse</li>
 * <li><code>adminPage</code>: system.admin/marketplace_confluence</li>
 * <li><code>profilePage</code>: system.profile</li>
 * </ul>
 *
 * You may wish to have no link to the page shown anywhere - for example, if you are using the page as the
 * target of a <a href="../../javascript/module-Dialog.html">JavaScript API dialog</a>. 
 * In this case, set the value of <code>location</code> to "none".
 *
 * @return the location of the link to the page
 */

"Conditions can be added to display only when all the given conditions are true.\n"

"The supported conditions for pages are:\n"

" <li><code>addon_property_exists</code></li>\n"

" <li><code>addon_property_equal_to</code></li>\n"

" <li><code>addon_property_equal_to_context</code></li>\n"

" <li><code>addon_property_contains_any</code></li>\n"

" <li><code>addon_property_contains_all</code></li>\n"

" <li><code>addon_property_contains_context</code></li>\n"

" <li><code>addon_property_contains_any_user_group</code></li>\n"

" <li><code>user_is_admin</code></li>\n"

" <li><code>user_is_logged_in</code></li>\n"

" <li><code>user_is_sysadmin</code></li>\n"

" <li><code>addon_is_licensed</code></li>\n"

" <li><code>feature_flag</code></li>\n"

" <li><code>entity_property_exists</code></li>\n"

" <li><code>entity_property_equal_to</code></li>\n"

" <li><code>entity_property_equal_to_context</code></li>\n"

" <li><code>entity_property_contains_any</code></li>\n"

" <li><code>entity_property_contains_all</code></li>\n"

" <li><code>entity_property_contains_context</code></li>\n"

" <li><code>entity_property_contains_any_user_group</code></li>\n"

" <li><code>can_use_application</code></li>\n"

" <li><code>project_type</code></li>\n"

" <li><code>has_global_permission</code></li>\n"

"Confluence conditions\n"

" <li><code>content_property_exists</code></li>\n"

" <li><code>content_property_equal_to</code></li>\n"

" <li><code>content_property_equal_to_context</code></li>\n"

" <li><code>content_property_contains_any</code></li>\n"

" <li><code>content_property_contains_all</code></li>\n"

" <li><code>content_property_contains_context</code></li>\n"

" <li><code>content_property_contains_any_user_group</code></li>\n"

" <li><code>space_property_exists</code></li>\n"

" <li><code>space_property_equal_to</code></li>\n"

" <li><code>space_property_equal_to_context</code></li>\n"

" <li><code>space_property_contains_any</code></li>\n"

" <li><code>space_property_contains_all</code></li>\n"

" <li><code>space_property_contains_context</code></li>\n"

" <li><code>space_property_contains_any_user_group</code></li>\n"

/**
 * The location in the application interface where the page's link should appear. For the Atlassian application
 * interface, a location is something like the coordinates on a map. It points to a particular drop-down menu or
 * navigation list in the UI.
 *
 * Places in the Atlassian UI are identified by what are known as "well-known locations."
 * For example, the "system.admin/globalsettings" location is in the administrative
 * menu link on the left side of the Administration Console.
 *
 * Product location documentation:
 *
 * <ul>
 * <li><a href="https://developer.atlassian.com/jiracloud/jira-platform-modules-39987040.html#JIRAplatformmodules-locations">Basic JIRA locations</a></li>
 * <li><a href="https://developer.atlassian.com/jiracloud/jira-software-ui-modules-39987281.html">JIRA Software locations</a></li>
 * <li><a href="https://developer.atlassian.com/jiracloud/jira-service-desk-ui-modules-39988267.html">JIRA Service Desk locations</a></li>
 * <li><a href="https://developer.atlassian.com/display/CONFDEV/Web+UI+Modules">Confluence locations</a></li>
 * </ul>
 *
 * If the <code>location</code> property is not specified, a default location is used:
 *
 * JIRA:
 *
 * <ul> 
 * <li><code>generalPage</code>: system.top.navigation.bar</li>
 * <li><code>adminPage</code>: advanced\_menu\_section/advanced_section</li>
 * </ul> 
 *
 * Confluence:
 *
 * <ul>
 * <li><code>generalPage</code>: system.browse</li>
 * <li><code>adminPage</code>: system.admin/marketplace_confluence</li>
 * <li><code>profilePage</code>: system.profile</li>
 * </ul>
 *
 * You may wish to have no link to the page shown anywhere - for example, if you are using the page as the
 * target of a <a href="../../javascript/module-Dialog.html">JavaScript API dialog</a>. 
 * In this case, set the value of <code>location</code> to "none".
 *
 * @return the location of the link to the page
 */

"A key to identify the macro. Keys must only contain alphanumeric characters and dashes, and must "

"be globally unique. Prefixing it with the name of your add-on is the best way to ensure this."

/**
 * The link to the add-on resource that provides the macro content.
 * This URL has to be relative to the add-on base URL.
 *
 * Additional context parameters can be passed as variables in the URL:
 * <pre><code>
 * {
 * "url": "/macro-renderer?body={macro.body}&space_id={space.id}&page_id={page.id}"
 * }
 * </code></pre>
 *
 * Since macro bodies can be of arbitrary size and may contain sensitive data, care must be taken
 * as to how its passed to your connect add-on. You have three options to gain access to the body:
 *
 * - If you can predict the size of your body and it is consistently less than 128 characters, you
 * can include it in the GET request using the `{macro.body}` parameter.
 * - If you know your macro contains a body that will often exceed the 128 character threshold
 * (or is known to contain sensitive data), then you can include the `{macro.id}` parameter and
 * use the Confluence REST api to call back to collect the body.
 * - If you want, you can include, `{macro.body}`, `{macro.id}`, and `{macro.truncated}`. This way
 * your plugin can call back to confluence only if `{macro.truncated}` is '`true`'. This will allow
 * you to skip the callback if it's not needed. This would be useful for macros that don't
 * contain sensitive data of an unpredictable size.
 *
 *
 *__Note:__ If you include the `{macro.body}` in your URL you are potentially leaking sensitive data
 * to any intermediate host on the internet. This may result in the body being cached or indexed
 * by a third party. If you are concerned about the security of your macro, you should always use
 * the `{macro.id}` and use the Confluence REST API to collect the body.
 *
 * Here's an example:
 *
 * Declare the variables that are later required to fetch the macro content in the URL:
 * <pre><code>
 * {
 * "url": "/render-macro?pageId={page.id}&pageVersion={page.version}&macroId={macro.id}"
 * }
 * </code></pre>
 *
 * Then use the Confluence REST API to collect the body, for example directly from the iframe:
 * <pre><code>
 * AP.require("request", function(request) {
 * var pageId = getUrlParameter("pageId");
 * var pageVersion = getUrlParameter("pageVersion");
 * var macroId = getUrlParameter("macroId");
 * request({
 * url: "/rest/api/content/" + pageId +
 * "/history/" + pageVersion +
 * "/macro/id/" + macroId,
 * success: function(response) {
 * var macro = JSON.parse(response);
 * process(macro.body);
 * }
 * });
 * });
 * </code></pre>
 *
 * __Preview Mode:__ If you use the `{macro.id}` in your URL, the REST api will not return the macro body during
 * a preview request, because the page has not been saved yet. You can use the `{output.type}` parameter to detect
 * whether the macro is rendered in preview mode and adapt the response accordingly.
 *
 * __Note:__ `macro.body` will not be truncated when `renderingMethod` field was set to `POST` in static content macro.
 * Refer to the [`Static Content Macros`](./static-content-macro.html) for information on
 * how to set this field.
 *
 * Currently supported variables for macros are:
 *
 * - `macro.hash`: The hash of the macro body (deprecated, use the macro.id)
 * - `macro.id`: The id of the macro
 * - `macro.body`: The macro body, truncated to 128 characters
 * - `macro.truncated`: True if the macro body was truncated, false of not
 * - `page.id`: The page ID, e.g. `1376295`
 * - `page.title`: The page title, e.g. `My Page`
 * - `page.type`: The page type, e.g. `page`
 * - `page.version`: The page version, e.g. `6`
 * - `space.id`: The space ID, e.g. `65537`
 * - `space.key`: The space key, e.g. `AC`
 * - `user.id`: The user ID, e.g. `admin`
 * - `user.key`: The user key, e.g. `ff80808143087d180143087d3a910004`
 * - `output.type`: The output type, e.g. `display` or `preview`
 *
 *Context parameters for macros are also required in the URL. Please see the
 * [Macro Input Parameter](../fragment/macro-input-parameter.html) documentation for details.
 */

/**
     * A description of the macro's functionality.
     */

/**
     * A link to the icon resource (80x80 pixels) that will be shown in the macro selection dialog.
     * The URL can be absolute or relative to the add-on base URL.
     */

/**
     * A link to the documentation for the macro.
     */

/**
     * The categories the macro should appear in. A macro with no category will show up in the default 'All' category.
     *
     * Currently, the following categories are supported by Confluence:
     *
     * * `admin`: Administration
     * * `communication`: Communication
     * * `confluence-content`: Confluence Content
     * * `development`: Development
     * * `external-content`: External Content
     * * `formatting`: Formatting
     * * `media`: Media
     * * `navigation`: Navigation
     * * `reporting`: Reporting
     * * `visuals`: Visuals & Images
     */

/**
     * How this macro should be placed along side other page content.
     */

/**
     * The type of body content, if any, for this macro.
     */

/**
     * Define aliases for the macro. The macro browser will open for the defined aliases as if it were this macro.
     */

/**
     * Whether the macro should be "featured", meaning having an additional link in the "Insert More Content" menu in the editor toolbar.
     */

/**
     * If set to true, the macro will not appear in the macro browser.
     */

/**
     * The list of parameter input fields that will be displayed.
     */

/**
     *  URL patterns associated with this macro. If a URL matching a defined pattern is pasted into the editor, this macro
     *  will be created and will replace the URL string.
     */

/**
     * The configuration of a custom macro editor. This is useful if the parameter input field types are
     * not sufficient to configure the macro.
     */

/**
     * The configuration of a property panel. Specify a hidden iframe to be loaded in the macro's property panel.
     */

/**
     * The image rendered in the editor as the macro placeholder. It can only be used with bodyless macros and will behave
     * just like a regular macro placeholder. Any parameter changes in the macro browser will cause the image
     * to be reloaded - so that changes can be seen.
     */

How to use com.atlassian.json.schema.annotation.ObjectSchemaAttributesconstructor

Best Java code snippets using com.atlassian.json.schema.annotation.ObjectSchemaAttributes.<init> (Showing top 9 results out of 315)

How to use
com.atlassian.json.schema.annotation.ObjectSchemaAttributes
constructor