![\"Build](\"https://travis-ci.org/grails-plugins/grails-angular-scaffolding.svg?branch=master\")
A plugin for generating client side assets based on domain classes
\nLatest: https://grails-plugins.github.io/grails-angular-scaffolding/latest\nSnapshot: https://grails-plugins.github.io/grails-angular-scaffolding/snapshot
\n" }, { + "deprecated": "This repository was archived by the owner on Feb 28, 2025. It is now read-only.", "bintrayPackage": { "name": "angularjs-scaffolding", "repo": "plugins", @@ -379,16 +382,16 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/grails-async/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "5.0.2", "updated": "2024-01-09T11:43:22.000Z", "systemIds": [ - "org.grails.plugins:async" + "org.apache.grails:grails-async" ], - "vcsUrl": "https://github.com/grails/grails-async" + "vcsUrl": "https://github.com/apache/grails-core" }, "documentationUrl": "https://async.grails.org/latest/guide/index.html", - "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/plugins/async/maven-metadata.xml", + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-async/maven-metadata.xml", "readme": "" }, { @@ -467,6 +470,7 @@ }, { "comment": "This entry in the registry is for the umbrella project for all the AWS plugins from agorapulse. Perhaps this entry is not necessary as each separate plugin also has its own entry?", + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk", "repo": "plugins", @@ -500,6 +504,7 @@ "readme": "![\"Build](\"https://travis-ci.org/agorapulse/grails-aws-sdk.svg\")
![\"Download\"](\"https://api.bintray.com/packages/agorapulse/plugins/aws-sdk-dynamodb/images/download.svg?version=2.2.12\")
The AWS SDK Plugins for Grails3 are a suite of plugins that adds support for the Amazon Web Services infrastructure services.
\nThe aim is to to get you started quickly by providing friendly lightweight utility Grails service wrappers, around the official AWS SDK for Java (which is great but very \ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdjava-esque\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd).\nSee this article for more info.
\nThe following services are currently supported:
\nPlease check each README for usage info.
\nHow to Unit Test AWS Services with LocalStack and Testcontainers
\nTo report any bug, please use the project Issues section on GitHub.
\nNOTE: For Grails 4 you should consider migrating to Micronaut AWS SDK as Miconaut is now the first class citizen in Grails. Use -micronaut-1.2 releases for Grails 4.0.x.
| Grails | Plugin |\n| ------------- |---------------|\n| 3.3.x, 4.x | 2.2.x |\n| 3.2.x | 2.1.x |\n| 2.x | 1.x |
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-cognito", "repo": "plugins", @@ -525,6 +530,7 @@ "readme": "This repo has been migrated to the main AWS SDK Grails Plugin repo.
\nHere his the latest version of it
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-dynamodb", "repo": "plugins", @@ -550,6 +556,7 @@ "readme": "This repo has been migrated to the main AWS SDK Grails Plugin repo.
\nHere his the latest version of it
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-kinesis", "repo": "plugins", @@ -575,6 +582,7 @@ "readme": "This repo has been migrated to the main AWS SDK Grails Plugin repo.
\nHere his the latest version of it
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-s3", "repo": "plugins", @@ -600,6 +608,7 @@ "readme": "This repo has been migrated to the main AWS SDK Grails Plugin repo.
\nHere his the latest version of it
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-ses", "repo": "plugins", @@ -625,6 +634,7 @@ "readme": "This repo has been migrated to the main AWS SDK Grails Plugin repo.
\nHere his the latest version of it
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-sns", "repo": "plugins", @@ -650,6 +660,7 @@ "readme": "This repo has been migrated to the main AWS SDK Grails Plugin repo.
\nHere his the latest version of it
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-sqs", "repo": "plugins", @@ -675,6 +686,7 @@ "readme": "This repo has been migrated to the main AWS SDK Grails Plugin repo.
\nHere his the latest version of it
\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "aws-sdk-sts", "repo": "plugins", @@ -874,6 +886,7 @@ "readme": "![\"Build](\"https://travis-ci.org/grails-plugins/grails-cache-ehcache.svg\")
Makes Ehcache the cache implementation for the Grails Cache Plugin
\nSee https://plugins.grails.org/plugin/grails/cache-ehcache and Documentation
\nSee https://grails.org/plugin/cache-ehcache and Documentation
\nThe current master branch is for 3.x versions of the plugin compatible with Grails 3. There is a 1.x branch for on-going maintenance of 1.x versions of the plugin compatible with Grails 2. Please submit any pull requests to the appropriate branch. Changes to the 1.x branch will be merged into the master branch if appropriate.
\n" }, { + "deprecated": "This repository was archived by the owner on Jul 12, 2024. It is now read-only.", "bintrayPackage": { "name": "cache-guava", "repo": "plugins", @@ -971,6 +984,7 @@ "readme": "This plugin establishes a `phoneNumber` constraint property for validateable objects, that being domain objects, and objects implementing `grails.validation.Validateable`. It relies on Google's [libphonenumber](https://github.com/google/libphonenumber) Java implementation" }, { + "deprecated": "This repository was archived by the owner on Dec 5, 2024. It is now read-only.", "bintrayPackage": { "name": "cassandra", "repo": "plugins", @@ -1135,17 +1149,17 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/sheehan/grails-console/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "2.1.1", "updated": "2018-01-23T03:19:17.309Z", "systemIds": [ - "org.grails.plugins:grails-console" + "org.grails:grails-console" ], - "vcsUrl": "https://github.com/sheehan/grails-console" + "vcsUrl": "https://github.com/apache/grails-core" }, "documentationUrl": null, - "mavenMetadataUrl": null, - "readme": "A web-based Groovy console for interactive runtime application management and debugging
\n![\"Screenshot\"](\"https://raw.github.com/sheehan/grails-console/images/screenshot.png\")
The 1.X version is for Grails 2.
\nThe 2.0.X version is for Grails 3.0 - 3.2.
\nThe 2.1.X version is for Grails 3.3+.
\nAdd a dependency in BuildConfig.groovy:
\ngrails.project.dependency.resolution = {\n // ...\n plugins {\n runtime ':console:1.5.12'\n // ...\n }\n}\nNote: If using Grails 3.0.4, you need to update the asset-pipeline dependency in build.gradle to 3.0.6 or greater. 3.0.5 is used by default and has a bug that prevents the console page from rendering.
\nNote: If using Grails 3.0.12, you will need to add this to your configuration: grails.resources.pattern = '/**'. There is a bug related to resource paths.
Add a dependency in build.gradle
\nruntime 'org.grails.plugins:grails-console:2.1.1'\nUse a browser to navigate to the /console page of your running app, e.g. http://localhost:8080/{app-name}/console
\nType any Groovy commands in the console text area, then click on the execute button. The console plugin relies on Groovy Shell. Lookup Groovy Shell documentation for more information.\nThe Groovy Shell uses the Grails classloader, so you can access any class or artifact (e.g. domain classes, services, etc.) just like in your application code.
\nClick on the Save button to save the current script.
Use the Storage pane to navigate existing files. Click on a file to load it into the editor.
\nThere are currently two storage options available:
\nLocal Storage uses HTML5 Web Storage. The files are serialized and stored in the browser as a map under the key gconsole.files.
Remote Storage uses the filesystem of the server on which the application is running.
\nCalls made to the implicit console variable will be executed on the browser's console.\nThe arguments are serialized as JSON and the calls are queued to run after the script completes.
Example:\n![\"Screenshot\"](\"https://raw.github.com/sheehan/grails-console/images/screenshot2.png\")
The following implicit variables are available:
\nctx - the Spring ApplicationContextgrailsApplication - the GrailsApplication instanceconfig - the Grails configurationrequest - the current HTTP requestsession - the current HTTP sessionout - the output PrintStreamSee Script Examples for example usage.
\n| Key | Command |\n|---|---|\n| Ctrl-Enter / \ufffd\ufffd\ufffd\ufffd\ufffd\ufffd-Enter | Execute |\n| Ctrl-S / \ufffd\ufffd\ufffd\ufffd\ufffd\ufffd-S | Save |\n| Esc | Clear output |
\nThe following configuration options are available:
\n| Property | Description |\n|---|---|\n| grails.plugin.console.enabled | Whether to enable the plugin. Default is true for the development environment, false otherwise. |\n| grails.plugin.console.baseUrl | Base URL for the console controller. Can be a String or a List of Strings if having multiple URLs is desired. Default uses createLink(). |\n| grails.plugin.console.fileStore.remote.enabled | Whether to include the remote file store functionality. Default is true. |\n| grails.plugin.console.fileStore.remote.defaultPath | Default path when browsing remote files. Default is /. |\n| grails.plugin.console.layout | Used to override the plugin's GSP layout. |\n| grails.plugin.console.newFileText | Text to display as a template for new files. Can be used to add frequently used imports, environment specific warnings, etc... Defaults to empty. |\n| grails.plugin.console.tabSize | The width of a tab character. Defaults to 4. |\n| grails.plugin.console.indentWithTabs | Whether indents should use tabs rather than spaces. Default is false. |\n| grails.plugin.console.indentUnit | How many spaces a block should be indented. Default is 4. |\n| grails.plugin.console.csrfProtection.enabled | Whether to enable CSRF protection. Default is true. |
By default (as of v1.5.0) the console plugin is only enabled in the development environment. You can enable or disable it for any environment with\nthe grails.plugin.console.enabled config option in Config.groovy / application.groovy (Grails 3). If the plugin is enabled in non-development environments, be sure to guard access using a security plugin like Spring Security Core or Shiro. For Grails 2.x, the paths /console/** and /plugins/console*/** should be secured. For Grails 3.x, the paths /console/** and /static/console/** should be secured.
Spring Security Core example:
\ngrails.plugin.springsecurity.controllerAnnotations.staticRules = [\n [pattern:"/console/**", access:['ROLE_ADMIN']],\n [pattern:"/plugins/console*/**", access:['ROLE_ADMIN']], // Grails 2.x\n [pattern:"/static/console/**", access:['ROLE_ADMIN']], // Grails 3.x\n]\nAnother example restricting access to localhost IPs:
\ngrails.plugin.springsecurity.controllerAnnotations.staticRules = [\n [pattern:"/console/**", access:["hasRole('ROLE_ADMIN') && (hasIpAddress('127.0.0.1') || hasIpAddress('::1'))"]],\n [pattern:"/plugins/console*/**", access:["hasRole('ROLE_ADMIN') && (hasIpAddress('127.0.0.1') || hasIpAddress('::1'))"]], // Grails 2.x\n [pattern:"/static/console/**", access:["hasRole('ROLE_ADMIN') && (hasIpAddress('127.0.0.1') || hasIpAddress('::1'))"]], // Grails 3.x\n]\nPlease see CONTRIBUTING.md
\n" + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/grails-console/maven-metadata.xml", + "readme": "A web-based Groovy console for interactive runtime application management and debugging
" }, { "bintrayPackage": { @@ -1184,16 +1198,17 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/grails-plugin-converters/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "5.0.0", "updated": "2024-02-26T10:59:18.000Z", "systemIds": [ - "org.grails.plugins:converters" + "org.grails.plugins:converters", + "org.apache.grails:grails-converters" ], - "vcsUrl": "https://github.com/grails-plugins/grails-plugin-converters" + "vcsUrl": "https://github.com/apache/grails-core" }, "documentationUrl": null, - "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/plugins/converters/maven-metadata.xml", + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-converters/maven-metadata.xml", "readme": "This is the Converters plugin that has been part of Grails core up until version 3.3 and now is a standalone plugin.
\nUsers of Grails 3.3.x and above should use this plugin.
\nSimply add the dependency to your build.gradle file:
compile "org.grails.plugins:converters"\nSee the README on GitHub
" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "facebook-sdk", "repo": "plugins", @@ -1965,17 +1982,17 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/gpc/fields/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "5.0.3", "updated": "2024-04-08T19:47:32.000Z", "systemIds": [ - "io.github.gpc:fields" + "org.apache.grails:grails-fields" ], - "vcsUrl": "https://github.com/gpc/fields" + "vcsUrl": "https://github.com/apache/grails-core" }, - "documentationUrl": "https://gpc.github.io/fields/", - "mavenMetadataUrl": "https://repo1.maven.org/maven2/io/github/gpc/fields/maven-metadata.xml", - "readme": "Find the latest documentation here: https://gpc.github.io/fields" + "documentationUrl": "https://docs.grails.org/latest/guide/theWebLayer.html#fields", + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-fields/maven-metadata.xml", + "readme": "Find the latest documentation here: https://docs.grails.org/latest/guide/theWebLayer.html#fields" }, { "displayName": "file-viewer", @@ -2093,19 +2110,20 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/geb/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "4.1.1", "updated": "2024-12-22T00:53:39.000Z", "systemIds": [ - "org.grails.plugins:geb" + "org.apache.grails:grails-geb" ], - "vcsUrl": "https://github.com/grails/geb" + "vcsUrl": "https://github.com/apache/grails-core" }, "documentationUrl": null, - "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/plugins/geb/maven-metadata.xml", + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-geb/maven-metadata.xml", "readme": null }, { + "deprecated": "This repository was archived by the owner on Mar 10, 2025. It is now read-only.", "bintrayPackage": { "name": "gorm-graphql", "repo": "plugins", @@ -2381,6 +2399,7 @@ "readme": "This is a fork of the original Grails Hibernate Filter Plugin\ncreated from fork appcela/grails-hibernate-plugin\nto make it work with the Grails 3 and Hibernate 4.
\nThis repo contains two projects:
\nClone the repository and execute in main directory command:
\n./gradlew hibernate-filter-plugin:jar\nYou can publish it to your maven local repository using:
\n./gradlew hibernate-filter-plugin:publishToMavenLocal\nTo run example application use command:
\n./gradlew hibernate-filter-example:bootRun\nAdd dependency in build.gradle:
\ncompile "org.grails.plugins:grails-hibernate-filter:0.2.0"\nConfigure dataSource in application.yml
\nconfigClass: org.grails.plugin.hibernate.filter.HibernateFilterDomainConfiguration\nPlease refer to the official Grails Hibernate Filter Plugin for usage.
\n![\"Build](\"https://travis-ci.org/fingo/grails-hibernate-filter.svg?branch=master\")
This project contains the sources for GSP, the server-side view rendering technology used in Grails.
\nLatest - http://gsp.grails.org
\nLatest - http://gsp.grails.org/latest/api
\nSnapshot Guide - http://gsp.grails.org/snapshot
\nSnapshot API - http://gsp.grails.org/snapshot
\n![\"Java](\"https://github.com/grails/grails-data-mapping/workflows/Java%20CI/badge.svg?branch=master\"){kind=icon}
\n![\"Release\"](\"https://github.com/grails/grails-data-mapping/workflows/Release/badge.svg?branch=master\"){kind=icon}
\n![\"Maven](\"https://github.com/grails/grails-data-mapping/workflows/Maven%20Central%20Sync/badge.svg?branch=master\"){kind=icon}
[Grails][Grails] is a framework used to build web applications with the [Groovy][Groovy] programming language. This project provides the plumbings for the GORM API both for Hibernate and for new implementations of GORM ontop of NoSQL datastores.\n[Grails]: http://grails.org/\n[Groovy]: http://groovy-lang.org/
\nFor further information see the dedicated websites:
\n\nGrails and Groovy are licensed under the terms of the [Apache License, Version 2.0][Apache License, Version 2.0].\n[Apache License, Version 2.0]: http://www.apache.org/licenses/LICENSE-2.0.html
\n" }, { + "deprecated": "This repository was archived by the owner on Dec 5, 2024. It is now read-only.", "bintrayPackage": { "name": "hibernate4", "repo": "plugins", @@ -3224,16 +3244,16 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/grails-data-mapping/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "8.1.1", "updated": "2024-11-19T01:27:50.000Z", "systemIds": [ - "org.grails.plugins:hibernate5" + "org.apache.grails:grails-data-hibernate5" ], - "vcsUrl": "https://github.com/grails/grails-data-mapping" + "vcsUrl": "https://github.com/apache/grails-core/issues" }, - "documentationUrl": "https://grails.github.io/grails-data-mapping/", - "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/plugins/hibernate5/maven-metadata.xml", + "documentationUrl": null, + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-data-hibernate5/maven-metadata.xml", "readme": "\n\n
[Grails][Grails] is a framework used to build web applications with the [Groovy][Groovy] programming language. This project provides the plumbings for the GORM API both for Hibernate and for new implementations of GORM ontop of NoSQL datastores.\n[Grails]: http://grails.org/\n[Groovy]: http://groovy-lang.org/
\nFor further information see the dedicated websites:
\n\nGrails and Groovy are licensed under the terms of the [Apache License, Version 2.0][Apache License, Version 2.0].\n[Apache License, Version 2.0]: http://www.apache.org/licenses/LICENSE-2.0.html
\n" }, { @@ -3286,6 +3306,7 @@ "readme": "![\"Build](\"https://travis-ci.org/agorapulse/grails-html-cleaner.png\")
\n![\"Download\"](\"https://api.bintray.com/packages/agorapulse/plugins/html-cleaner/images/download.svg\")
The Html Cleaner Plugin is a whitelist based html sanitizer, based on Jsoup.\nThis is a port to Grails3 of the Grails1 plugin, originally written by Sudhir Nimavat.
\nIt provides:
\nNote: Html cleaner is not just a sanitizer, it cleans ill-formed user supplied html and produces a well formed xml.
\nDeclare the plugin dependency in the build.gradle file, as shown here:
\nrepositories {\n ...\n maven { url "http://dl.bintray.com/agorapulse/plugins" }\n}\ndependencies {\n ...\n compile "org.grails.plugins:html-cleaner:1.1"\n}\nFollowing whitelists are available by default and does not need any configuration:
\nYou can define default white list in your grails-app/conf/application.yml:
\ngrails:\n plugin:\n htmlcleaner:\n defaultWhiteList: basic\nSee below to define custom whitelists.
\nLet's say you have a form with a text area, but you don't want to allow any html. You can clean the user supplied text with whitelist none and it will stripe out all the html.
\nimport grails.plugin.htmlcleaner.HtmlCleaner\n\nclass FooController {\n\n HtmlCleaner htmlCleaner\n\n def save = {\n String cleaned = htmlCleaner.cleanHtml(params.textArea, 'none') \n }\n}\nOr in a service:
\nimport grails.plugin.htmlcleaner.HtmlCleaner\n\nclass FooService {\n\n HtmlCleaner htmlCleaner\n\n def foo(unsafe) {\n String cleaned = htmlCleaner.cleanHtml(unsafe, 'none')\n }\n}\nYou can also allow basic html as per basic whitelist.
\ndef cleaned = htmlCleaner.cleanHtml(unsafe, 'basic')\nThe plugin also provides a taglib.
\n<hc:cleanHtml html="${domainInstance.description}" whitelist="basic"/>\nPlugin provides a DSL to define custom whitelists in configuration.\nDefine a custom whitelist sample that will allow just b, i, p and span tags.
\napplication.groovy
\ngrails {\n plugin {\n htmlcleaner {\n whitelists = {\n whitelist("sample") {\n startwith "none"\n allow "b", "p", "i", "span"\n }\n }\n }\n }\n}\nThe above configuration would define a whitelist with name sample that builds on top of whitelist none and allows additional tags b, i, p and span.
\nA whitelist can start with any of the default whitelists or A whitelist can start with any custom whitelists that are defined earlier in configuration as well, but it must start with another whitelist.
\nDefine a whitelist sample2 that starts with whitelist sample we defined above and allows tag a with just one attribute href and puts rel="nofollow"
\ngrails {\n plugin {\n htmlcleaner {\n whitelists = {\n whitelist("sample2") {\n startwith "sample"\n allow("a") {\n attributes "href"\n enforce attribute:"rel", value:"nofollow"\n }\n }\n }\n }\n }\n}\nDefine a whitelist basic-with-tables that starts with whitelist basic and allows tables.
\ngrails {\n plugin {\n htmlcleaner {\n whitelists = {\n whitelist("basic-with-tables") {\n startwith "basic"\n allow "table", "tr", "td"\n }\n }\n }\n }\n}\nRestricting attributes
\ngrails {\n plugin {\n htmlcleaner {\n whitelists = {\n whitelist("sample") {\n allow("div") {\n attributes "id", "class"\n }\n }\n }\n }\n }\n}\nEnforcing attributes - An enforced attribute will always be added to the element. If the element already has the attribute set, it will be overridden.
\ngrails {\n plugin {\n htmlcleaner {\n whitelists = {\n whitelist("sample") {\n allow("div") {\n enforce attribute:"class", value:"block"\n }\n }\n }\n }\n }\n}\nDefining multiple whitelists
\ngrails {\n plugin {\n htmlcleaner {\n whitelists = {\n whitelist("sample") {\n startwith "none"\n allow "b", "p", "span"\n }\n whitelist("sample-with-anchor") {\n startwith "sample"\n allow("a") {\n attributes "href"\n enforce attribute:"rel", value:"nofollow"\n }\n }\n \n whitelist("basic-with-tables") {\n startwith "basic"\n allow "table", "tr", "td"\n }\n \n }\n }\n }\n}\nTo report any bug, please use the project Issues section on GitHub.
\n" }, { + "deprecated": "This repository was archived by the owner on Jun 18, 2024. It is now read-only.", "bintrayPackage": { "name": "http-builder-helper", "repo": "plugins", @@ -3310,6 +3331,7 @@ "readme": "This plugin used to be called the REST plugin in Grails 1.x & 2.x, but for Grails 3.x it has been renamed to httpbuilder-helper. The plugin enables the usage of HTTPBuilder in a Grails application.
The REST plugin enables the usage of HTTPBuilder on a Grails application.
\nThe plugins will inject the following dynamic methods:
\nwithHttp(Map params, Closure stmts) - executes stmts using a HTTPBuilderwithAsyncHttp(Map params, Closure stmts) - executes stmts using an AsyncHTTPBuilderwithRest(Map params, Closure stmts) - executes stmts using a RESTClientTaken from HttpBuilder's Simplified GET Request
\nwithHttp(uri: "http://www.google.com") {\n def html = get(path : '/search', query : [q:'Groovy'])\n assert html.HEAD.size() == 1\n assert html.BODY.size() == 1\n}\nNotice that you can call HTTPBuilder's methods inside stmts, the current HTTPBuilder is set as the closure's delegate. The same holds true for the other dynamic methods.\nAsyncHTTPBuilder
import static groovyx.net.http.ContentType.HTML\nwithAsyncHttp(poolSize : 4, uri : "http://hc.apache.org", contentType : HTML) {\n def result = get(path:'/') { resp, html ->\n println ' got async response!'\n return html\n }\n assert result instanceof java.util.concurrent.Future\n\n while (! result.done) {\n println 'waiting...'\n Thread.sleep(2000)\n }\n\n /* The Future instance contains whatever is returned from the response\n closure above; in this case the parsed HTML data: */\n def html = result.get()\n assert html instanceof groovy.util.slurpersupport.GPathResult\n}\nAll dynamic methods will create a new http client when invoked unless you define an id: attribute. When this attribute is supplied the client will be stored as a property on the instance's metaClass. You will be able to access it via regular property access or using the id: again.
\nclass FooController {\n def loginAction = {\n withRest(id: "twitter", uri: "http://twitter.com/statuses/") {\n auth.basic model.username, model.password\n }\n }\n def queryAction = {\n withRest(id: "twitter") {\n def response = get(path: "followers.json")\n // \ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\n }\n /* alternatively\n def response twitter.get(path: "followers.json")\n */\n }\n}\nDynamic methods will be added to controllers and services by default. You can change this setting by adding a configuration flag application.yml or application.groovy:
grails.rest.injectInto = ["Controller", "Service", "Routes"]\nYou can apply proxy settings by calling setProxy(String host, int port, String scheme) on the client/builders at any time. You can also take advantage of the proxy: shortcut
withHttp(uri: "http://google.com", proxy: [host: "myproxy.acme.com", port: 8080, scheme: "http"])\nThis shortcut has the following defaults
\nport: = 80\nscheme: = http\nMeaning most of the times you'd only need to define a value for host:
If you are connecting to a server through HTTPS you might need to add a Key and or a Trust Store to the underlying SSL Socket Factory. Some examples are\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd
\nThe service you are connecting to requires some sort of SSL Cert authentication,\nYou want to make sure that the server you are connecting to provides a specific certificate.\nYou do not mind that the certificate that the server provides doesn't match the Domain Name that the server has.\nNote, this last option will normally apply to development and test environments.
\nThe client will try to add a Key and a Trust Store if the URL of the host starts with https. By default it will attempt to locate a Key Store through the File System's path $HOME/.keystore e.g /home/berngp/.keystore and a Trust Store through the JVM Classpath ./truststore.jks, you can override this by specifying a rest.https.keystore.path and/or rest.https.truststore.path configuration entries in the application.yml or application.groovy file.
Also by default it will try to open the stores using the following passwords '', 'changeit', 'changeme' but you can set a specific password through the rest.https.keystore.pass and rest.https.truststore.pass configuration entries. If for some reason it is unable to setup the underlying SSL Socket Factory it will fail silently unless the rest.https.sslSocketFactory.enforce configuration entry is set to true.
You can set three different Hostname Verification strategies through the rest.https.cert.hostnameVerifier configuration entry.
ALLOW_ALL: The URL requested doesn't need to match the URL in the Certificate.\nSTRICT: The URL requested needs to match the URL in the Certificate.\nBROWSER_COMPATIBLE: The URL requested must be in the same domain as the one in the Certificate. It accepts wildcards.\nExample of a specific setup
/** SSL truststore configuration key */\nrest.https.truststore.path = 'resources/certs/truststore.jks'\n/** SSL keystore configuration key */\nrest.https.keystore.path='resources/certs/keystore.jks'\n/** SSL keystore password configuration key */\nrest.https.keystore.pass='changeme'\n/** Certificate Hostname Verifier configuration key */\nrest.https.cert.hostnameVerifier = 'BROWSER_COMPATIBLE'\n/** Enforce SSL Socket Factory */\nrest.https.sslSocketFactory.enforce = true\nGenerating a Java Key Store is outside the scope of this guide but you can find some useful information through the following links.
\nOfficial JDK Guide - http://download.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html
\nImporting a Private Key into a KeyStore (JDK 1.6 and above) - http://cunning.sharp.fm/2008/06/importing_private_keys_into_a.html
\nKeyMan - An non JDK Key Tool by IBM - http://www.alphaworks.ibm.com/tech/keyman
\n![\"Build](\"https://travis-ci.org/budjb/grails-jaxrs.svg?branch=grails-3.x\")
See the documentation at http://budjb.github.io/grails-jaxrs/3.x/latest/.
\n" }, { + "deprecated": "This repository was archived by the owner on Jul 3, 2023. It is now read-only.", "bintrayPackage": { "name": "jaxrs-integration-test", "repo": "grails-plugins", @@ -3509,6 +3533,7 @@ "readme": "
See the documentation at http://budjb.github.io/grails-jaxrs/3.x/latest/.
\n" }, { + "deprecated": "This repository was archived by the owner on Jul 3, 2023. It is now read-only.", "bintrayPackage": { "name": "jaxrs-jersey1", "repo": "grails-plugins", @@ -3533,6 +3558,7 @@ "readme": "
See the documentation at http://budjb.github.io/grails-jaxrs/3.x/latest/.
\n" }, { + "deprecated": "This repository was archived by the owner on Jul 3, 2023. It is now read-only.", "bintrayPackage": { "name": "jaxrs-restlet", "repo": "grails-plugins", @@ -3557,6 +3583,7 @@ "readme": "
See the documentation at http://budjb.github.io/grails-jaxrs/3.x/latest/.
\n" }, { + "deprecated": "This repository was archived by the owner on Jul 3, 2023. It is now read-only.", "bintrayPackage": { "name": "jaxrs-swagger-ui", "repo": "grails-plugins", @@ -3634,6 +3661,7 @@ "readme": null }, { + "deprecated": "This repository was archived by the owner on Jul 9, 2025. It is now read-only.", "bintrayPackage": { "name": "jesque-admin", "repo": "plugins", @@ -3808,6 +3836,7 @@ "readme": "A plugin to read raw kml file in - load google maps and overlay kml boundaries over map geo locations, international postcode lookup & resolve address from postcode feature
\ncompile "org.grails.plugins:kml:0.4"\n\n\nDemo project (grails 3.3.8)
\n
\n\nYouTube videos:
\n
Boxset - play all 3 as a playlist
\nPart 1 Walk through urls and simple usage of plugin - very basic
\nPart 2 Walk through of how to build on new grails project from scratch
\nPart 3 Talk through code process / steps
\n\n\nJava docs for classes
\n
kmlplugin{\n //TO USE MAP API FEATURE NEEDS TO BE ENABLED\n GOOGLE_API_KEY='YOUR GOOGLE API KEY'\n //This is total amount of local areas to collect for editing KML \n MAX_AREAS=30\n\n //How far to look for local areas in miles\n MAX_DISTANCE=30\n\n //This defines to enable map\n ENABLE_MAP_LOOKUP=true\n\n //By default treated as false\n DISABLE_LAT_LNG_LOOKUP=false\n\n // If you don't have API feature enabled on key disable this you get a developer map instead\n MAP_HAS_API_ENABLED=false\n\n \n //2 char country code of where your _default.kml belongs to so we can look up area names\n KML_COUNTRY='UK'\n\n // Internal folder to manage KML files - create and ensure web user has access\n KML_LOC="/opt/kmlplugin/_map/KML/"\n KML_HISTORY="/opt/kmlplugin/_map/KML_HISTORY/"\n\n //Drop this file in KML_LOC root folder - refer to notes below\n KML_DEFAULT="_default.kml"\n\n //This will re-run - recreate entries from _default.kml\n //if you are running in dev on h2 db - it is worth enabling this to add areas to db upon boot\n KML_RESET_FROM_DEFAULT=false\n}\nThis provides a page that given country / postcode will attempt to:
\n\n\n1.1: Lookup postcode and return as much of address as possible
\n
\n\n1.2. If
\nENABLE_MAP_LOOKUPis set to true andGOOGLE_API_KEYhas valid API access\nWill load map, put postcode on map\n& if KML boundaries loaded and matches will load in the area overlay on the map.
\n\n1.3 To disable features you can add any or all these to url line:
\n
Other examples:
\nhttp://localhost:8080/lookup/index?showState=false&showArea=true&showLatLong=true&streetRequired=false&countrysearch=United%20Kingdom&countryCode=UK&postcode=SE1%201AP
\nhttp://localhost:8080/lookup/index?countrysearch=United%20Kingdom&countryCode=UK&postcode=SE1%201AP
\nhttp://localhost:8080/lookup/index?countrysearch=United%20Kingdom&countryCode=UK&postcode=SE1%201AP&longitude=-0.09326659999999999&latitude=51.5017828
\nhttp://localhost:8080/lookup/index?countrysearch=United%20Kingdom&countryCode=UK&postcode=SE1%201AP&longitude=-0.09326659999999999&latitude=51.5017828&communitySearch=Southwark
\nAll passed variables to map and instance are not required but to show what above url params can be either posted or done as per above with instance being addition to params above\nfor tag lib if you already have data this is what it is expecting to be sent to it
\n<map:lookup \n showState="${false}" \n showArea="${false}" \n showLatLong="${false}" \n streetRequired="${false}"\n instance="${[\n countrysearch:'',\n countryCode:'',\n postcode:'',\n building:'',\n street:'',\n city:'',\n state:'',\n communitySearch:'',\n latitude:'',\n longitude:'',\n ]}"\n />\n<!-- similar example with some data already set all of below\n is enough to trigger maps / overlay - could be saved data -->\n<map:lookup\n showState="${false}"\n showArea="${false}"\n showLatLong="${false}"\n streetRequired="${false}"\n instance="${[\n countrysearch:'United Kingdom',\n countryCode:'UK',\n postcode:'SE1 1AP',\n building:'',\n street:'',\n city:'',\n state:'',\n communitySearch:'Southwark',\n latitude:'51.5017828',\n longitude:'-0.09326659999999999',\n ]}"\n/>\nThis provides an interface to edit and modify existing kml boundaries on the fly.\nIt provides raw kml extracted file, has feature to upload, hasn't been tested.
\nYou will need to take a copy of _address.gsp when verifyCode is called the data object returned contains full dump of\neverything useful .
console.log(JSON.stringify(data)) will show all but 2 full data sets: data.latLongDetails and data.fullPostCodeDetails
/opt/kmlplugin/_map/KML/ ->Place a file for the given country. This will be KML file you get hold of that contains typically all the official boroughs/councils of a given country in the case of UK we found:
\nwas here\nSite appears to no longer work. You can get hold of file from here
\nThis file was then stored in this folder as
\n_default.kml
\n/opt/kmlplugin/_map/KML/_default.kml
\n KmlHelper.parseKml()\nWhen the site starts up for the very first time, it will attempt to read through this file and inside the same folder it will expand out all the found boroughs.
\n$ ls -rtml /opt/kmlplugin/_map/KML/|more\ntotal 9876\n-rw-rw-r-- 1 mx1 mx1 7394653 Nov 29 17:08 _default.kml\n-rw-rw-r-- 1 mx1 mx1 19199 Dec 1 19:36 BEDFORDSHIRE.kml\n-rw-rw-r-- 1 mx1 mx1 31337 Dec 1 19:36 BUCKINGHAMSHIRE.kml\n-rw-rw-r-- 1 mx1 mx1 24338 Dec 1 19:36 CAMBRIDGESHIRE.kml\n-rw-rw-r-- 1 mx1 mx1 584 Dec 1 19:36 CHESHIRE.kml\n-rw-rw-r-- 1 mx1 mx1 584 Dec 1 19:36 CORNWALL.kml\n-rw-rw-r-- 1 mx1 mx1 582 Dec 1 19:36 CUMBRIA.kml\nAt this point it has loaded up each borough and also split each borough/community into its own specific file.
\nThis process happens only once and can be redone by clearing out and dropping in as above a _default.kml file.
\nThis triggers an internal process to do what has been demonstrated.
\nOnce it has been generated. The site will from there on refer to all created files to load up each community.
\nThis means you can now edit each of the generated files for a given community and re-save it \ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd a saved version and application restart will then ensure the site is using whatever latest content each community has.
\nUpon start up you will need to visit the map regions and it will show what has been produced.
\nAdd below to grails-app/conf/logback.groovy
logger('org.grails.plugins.kml', ERROR, ['STDOUT'], false)\n logger('org.grails.plugins.kml', DEBUG, ['STDOUT'], false)\n logger('org.grails.plugins.kml', WARN, ['STDOUT'], false)\n logger('org.grails.plugins.kml', INFO, ['STDOUT'], false)\n##Credits
\n/map KML Editor taken from Kjell ScharningKML Map editor or /map segement is thanks to above link which gave the source to build the rest as such.\nHis worked got wired into what the rest of the code does, as per what his page expected.
/lookup my own work over different projects / requirements.![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit1.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit2.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit3.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit4.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit5.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit6.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit7.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit8.png\")
\n![\"sample](\"https://vahidhedayati.github.io/grails-kml-map-plugin/screenshots/map-region-editor-edit9.png\")
The Grails mail plugin provides a convenient DSL for sending email. It supports plain text, html, attachments, inline resources and i18n among other features.\n![\"Build](\"https://travis-ci.org/grails3-plugins/mail.svg?branch=master\")
Mail can be sent using the @mailService@ via the @sendMail@ method. Here is an example\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd
\nmailService.sendMail {\n to "fred@gmail.com","ginger@gmail.com"\n from "john@gmail.com"\n cc "marge@gmail.com", "ed@gmail.com"\n bcc "joe@gmail.com"\n subject "Hello John"\n text 'this is some text'\n}\nPlease see the User Guide for more information.
\nThe plugin is released under the Apache License 2.0 and is produced under the Grails Plugin Collective.
\nIssues can be raised via GitHub Issues.
\nPull requests are the preferred method for submitting contributions. Please open an issue via that issue tracker link above and create an issue describing what your contribution addresses.
\nIf you are contributing documentation, raising an issue is not necessary.
\n" + "readme": "The Grails mail plugin provides a convenient DSL for sending email. It supports plain text, html, attachments, inline resources and i18n among other features.\n
Mail can be sent using the @mailService@ via the @sendMail@ method. Here is an example\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd
\nmailService.sendMail {\n to "fred@gmail.com","ginger@gmail.com"\n from "john@gmail.com"\n cc "marge@gmail.com", "ed@gmail.com"\n bcc "joe@gmail.com"\n subject "Hello John"\n text 'this is some text'\n}\nPlease see the User Guide for more information.
\nThe plugin is released under the Apache License 2.0 and is produced under the Grails Plugin Collective.
\nIssues can be raised via GitHub Issues.
\nPull requests are the preferred method for submitting contributions. Please open an issue via that issue tracker link above and create an issue describing what your contribution addresses.
\nIf you are contributing documentation, raising an issue is not necessary.
\n" }, { "bintrayPackage": { @@ -4017,16 +4046,16 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/gorm-mongodb/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "8.2.0", "updated": "2024-03-15T19:26:14.000Z", "systemIds": [ - "org.grails.plugins:mongodb" + "org.apache.grails:grails-data-mongodb" ], - "vcsUrl": "https://github.com/grails/gorm-mongodb" + "vcsUrl": "https://github.com/apache/grails-core" }, "documentationUrl": null, - "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/plugins/mongodb/maven-metadata.xml", + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-data-mongodb/maven-metadata.xml", "readme": "![\"Java](\"https://github.com/grails/gorm-mongodb/workflows/Java%20CI/badge.svg?branch=master\"){kind=icon}
\n![\"Release\"](\"https://github.com/grails/gorm-mongodb/workflows/Release/badge.svg?branch=master\"){kind=icon}
This project implements GORM for the MongoDB Document Database.
\nNOTE: This source code here is for version 6.x and above. For prevoius versions' source see the relevant branch on the Grails Data Mapping project.
\nFor more information see the following links:
\nFor the current development version see the following links:
\n\n" }, { @@ -4080,6 +4109,7 @@ "readme": "# TOC
\nThis plugin is sponsored by IP Geolocation. It adds multitenant support for grails 3 applications based on hibernate filters. Tenants are resolved using spring security.
\nOnly branch grails3.0.xhibernate4 is working. Rest of branches are for GORM5 which has broken the way hibernate filters are applied. So they won't work. Also, this plugin works only for Grails 3.0 and 3.1. For later versions of grails, use GORM's built in multi-tenancy support.\nThe work on this plugin has been stopped in favor of Grails internal support for Multi-tenant architecture.
\nAdd following dependency in build.gradle
\ncompile 'org.grails.plugins:multitenant:0.1'\nAdd configClass attribute in application.yml under dataSource section like this:
\n configClass: org.grails.plugin.multitenant.HibernateMultitenantConfiguration \nThis plugin uses single database single schema differentiator based technique to identify tenants.
\nCurrently it resolves tenant using spring security. So you have to edit spring security user domain class to implement TenantIdentifier trait like this:
\nclass User implements Serializable, TenantIdentifier\nIt add userTenantId property to User domain class and injects two closures dynamically to this domain
\nThis closure executes a particular code inside its scope with a tenantId supplied as parameters even if the logged in user does not belong to that tenant. You can only execute idempotent code inside this block. If your code is query, or some other read only operation, it will execute that with supplied tenantId. If your code is going to change something in database, it will use tenantId of logged in user. Be careful . .
\nUser.withTenantId(12){\n\n// Your code goes here\n\n}\n\nAs the name states, you can bypass tenantId filter temporarily to do operations not specific to any tenant.
\nUser.withoutTenantId(){\n\n// You code goes here\n\nThe code in this scope should be read only as is the case with withTenantId method above.
\nYou have to implement Multitenant trait in all domain classes you want to be multitenant.
\nclass Book implement Multitenant\nThis will add a property tenantId to domain class and three methods as below:
\nLong tenantId\n\n def beforeInsert() {\n if(tenantId == null){\n tenantId = tenantResolverService.resolveTenant()\n }\n }\n\n def beforeValidate() {\n if(tenantId == null){\n tenantId = tenantResolverService.resolveTenant()\n }\n }\n\n def beforeUpdate() {\n if(tenantId == null){\n tenantId = tenantResolverService.resolveTenant()\n }\n }\n \nSo if you want to use these methods in any of multitenant domain class, you have to reproduce above code along with your own implementation as yours will overwrite these methods.
\nThis plugin provide TenantResolverService to your application which can be injected anywhere just like normal grails services. It provides only one method resolveTenant which provides tenantId of current user. Multitenant plugin makes extensive use of this service at various places inside the code. Multitenant filter intercepts controller actions only. If you want to do some multitenant stuff inside a service then you should call that service from controller or use withTenantId as below:
\ndef tenantResolverService\nUser.withTenantId(tenantResolverService.resolveTenant()){\n // your code here\n}\nIP Geolocation's IP intelligence APIs help developer's find out Geolocation, Tim Zone, Local Currency and much more from just an IP address. For more information checkout document page
\n" }, { + "deprecated": "This repository was archived by the owner on Mar 10, 2025. It is now read-only.", "bintrayPackage": { "name": "neo4j", "repo": "plugins", @@ -4106,6 +4136,7 @@ "readme": "This project implements GORM for the Neo4j 3.x Graph Database using the Bolt Java Driver.
\nFor more information see the following links:
\n![\"Build](\"https://travis-ci.org/grails/gorm-neo4j.svg?branch=master\")
For the current development version see the following links:
\n\n" }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "newrelic", "repo": "plugins", @@ -4808,6 +4839,7 @@ "readme": "![\"Build](\"https://travis-ci.org/grails-plugins/grails-rabbitmq.svg?branch=master\")
Grails RabbitMQ Plugin
\n\n" }, { + "deprecated": "This repository was archived by the owner on Jul 3, 2023. It is now read-only.", "bintrayPackage": { "name": "rabbitmq-native", "repo": "grails-plugins", @@ -4909,6 +4941,7 @@ "readme": "![\"Build](\"https://travis-ci.org/grails-plugins/grails-redis.svg\")
The 2.X version of the plugin is compatible only with grails 3.
\nFor integration between Redis and Grails GORM layer, see the Redis GORM plugin.
\nThat plugin was originally called "redis" (the name of this plugin), but it has since been refactored to "redis-gorm" and now relies on this plugin for connectivity.
\nThe best definition of Redis that I've heard is that it is a "collection of data structures exposed over the network".
\nRedis is an insanely fast key/value store, in some ways similar to memcached, but the values it stores aren't just dumb blobs of data. Redis values are data structures like strings, lists, hash maps, sets, and sorted sets. Redis also can act as a lightweight pub/sub or message queueing system.
\nRedis is used in production today by a number of very popular websites including Craigslist, StackOverflow, GitHub, The Guardian, and Digg.
\nIt's commonly lumped in with other NoSQL technologies and is commonly used as a caching layer. It has some similarities to Memcached or Tokyo Tyrant. Because Redis provides network-available data structures, it's very flexible and it's able to solve all kinds of problems. The creator of Redis, Salvatore Sanfilippo, has a nice post on his blog showing how to take advantage of Redis by just adding it to your stack. With the Grails Redis plugin, adding Redis to your grails app is very easy.
\nI've created an introduction to Redis using groovy that shows you how to install redis and use some basic groovy commands. There is also a presentation that I gave at gr8conf 2011.
\nThe official Redis documentation is fantastic and includes a comprensive list of Redis commands, each command web page also has an embedded REPL that lets you test out the command against a live Redis server.
\nJedis is the Java Redis connection library that the Grails Redis plugin uses. It's actively maintained, very fast, and doesn't try to do anything too clever. One of the nice things about it is that it doesn't try to munge around with the Redis command names, but follows them as closely as possible. This means that for almost all commands, the Redis command documentation can also be used to understand how to use the Jedis connection objects. You don't need to worry about translating the Redis documentation into Jedis commands.
\ngrails install-plugin redis\nOut of the box, the plugin expects that Redis is running on localhost:6379. You can modify this (as well as any other pool config options) by adding a stanza like this to your grails-app/conf/Config.groovy file:
grails {\n redis {\n poolConfig {\n // jedis pool specific tweaks here, see jedis docs & src\n // ex: testWhileIdle = true\n }\n timeout = 2000 //default in milliseconds\n password = "somepassword" //defaults to no password\n useSSL = false //or true to use SSL\n\n // requires either host & port combo, or a sentinels and masterName combo\n\n // use a single redis server (use only if nore using sentinel cluster)\n port = 6379\n host = "localhost"\n database = 5 // set default database to 5\n\n // use redis-sentinel cluster as opposed to a single redis server (use only if not use host/port)\n sentinels = [ "host1:6379", "host2:6379", "host3:6379" ] // list of sentinel instance host/ports\n masterName = "mymaster" // the name of a master the sentinel cluster is configured to monitor\n }\n\n}\nThe poolConfig section will let you tweak any of the setter values made available by the JedisPoolConfig. It implements the Apache Commons GenericObjectPool.
\nNOTE: Please see Redis Sentinel - Documentation for more info on using redis-sentinel for high availability
\ndef redisService\nThe redisService bean wraps the pool connection. It has a number of caching/memoization helper functions, template methods, and basic Redis commands, it will be your primary interface to Redis.
The service overrides propertyMissing and methodMissing to delegate any missing requests to a Redis connection object. This means that any method that you'd normally call on a Redis connection object can be called directly on redisService.
// overrides propertyMissing and methodMissing to delegate to redis\ndef redisService\n\nredisService.foo = "bar"\nassert "bar" == redisService.foo\n\nredisService.sadd("months", "february")\nassert true == redisService.sismember("months", "february")\nIt also provides a template method called withRedis that takes a closure as a parameter. It passes a Jedis connection object to Redis into the closure. The template method automatically gets an object out of the pool and ensures that it gets returned to the pool after the closure finishes (even if there's an error).
redisService.withRedis { Jedis redis ->\n redis.set("foo", "bar")\n}\nThe advantage to calling withRedis rather than just calling methods directly on redisService is that multiple commands will only use a single connection instance, rather than one per command.
Redis also allows you to pipeline commands. Pipelining allows you to quickly send commands to Redis without waiting for a response. When the pipeline is executed, it returns a Result object, which works like a Future to give you the results of the pipeline. See the Jedis documentation on pipelining for more details. It works pretty much like the withRedis template does:
redisService.withPipeline { Pipeline pipeline ->\n pipeline.set("foo", "bar")\n}\nRedis has the notion of transactions, but it's not exactly the same as a database transaction. Redis transactions guarantee that all of the commands in the transaction will be executed as an atomic unit. Because Redis is single threaded, you're guaranteed to execute atomically and have a known state throughout the transaction. Redis does not support rolling back modifications that happen during a transaction.
\nThe withTransaction template method automatically opens and closes the transaction for you. If the closure doesn't throw and exception, it will tell Redis to execute the transaction
redisService.withTransaction { Transaction transaction ->\n transaction.set("foo", "bar")\n}\nMemoization is a write-through caching technique. The plugin gives a number of methods that take a key name, and a closure as parameters. These methods first check Redis to see if the key exists. If it does, it returns the value of the key and does not execute the closure. If it does not exist in Redis, it executes the closure and saves the result in Redis under the key. Subsequent calls will then be served the cached value from Redis rather than recalculating.
\nThis technique is very useful for caching values that are frequently requested but expensive to calculate.
\nAs of version 1.2 you may also use the new memoize annotations. See the Memoization Annotation section for usage and examples.
\nThere are methods for the basic Redis data types:
\nredisService.memoize("user:$userId:helloMessage") {\n // expensive to calculate method that returns a String\n "Hello ${security.currentLoggedInUser().firstName}"\n}\nBy default, the key/value will be cached forever in Redis, you can ensure that the key is refreshed either by deleting the key from Redis, making the key include a date or timestamp, or by using the optional expire parameter, the value is the number of seconds before Redis should expire the key:
def ONE_HOUR = 3600\nredisService.memoize("user:$userId:helloMessage", [expire: ONE_HOUR]) {\n """\n Hello ${security.currentLoggedInUser().firstName.\n The temperature this hour is ${currentTemperature()}\n """\n}\nYou can memoize a single domain object with redis. It will cache the ID of the domain object returned from the closure and on subsequent cache hits will return a proxy domain object using grails DomainObject.load(cachedId).
String key = "user:42:favorite:author"\nAuthor author = redisService.memoizeDomainObject(Author, key) {\n Author author = ... // expensive method to calculate user 42's favorite author...\n return author\n}\nNow that you have the proxy object for the Author, you can do queries with it without actually having to hydrate the object (and anything it eagerly loads):
\ndef recommendedBooks = Book.findByAuthor(author)\nThe object has the id field populated, but the remaining fields are lazily loaded only if their values are requested, so you can still do:
\nprintln author.name\nTo actually print out the name of the author.
\nYou can also memoize a list of domain object identifiers. It doesn't cache the entire domain object, just the database IDs of the domain objects in a returned list.
\nThis allows you to still grab the freshest objects from the database, but not repeatedly create an expensive list. This could be a big database query that joins a bunch of tables. Or some other process that does additional filtering based on selections the user has made in the UI. Something ephemeral for that session or user, that you don't want to persist, but need to be able to react to.
\ndef key = "user:$id:friends-books-user-does-not-own"\n\nredisService.memoizeDomainList(Book, key, ONE_HOUR) { redis ->\n // expensive process to calculate all friend\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffds books and filter out books\n // that the user already owns, this stores the list of determined Book IDs\n // in Redis, but hydrates the Book objects from the DB\n}\nThere are other memoization methods that the plugin provides, check out the RedisService.groovy and the plugin tests for the exhaustive list.
\n// Redis Hash memoize methods\n\nredisService.memoizeHash("saved-hash") { return [foo: "bar"] }\n\nredisService.memoizeHashField("saved-hash", "foo") { return "bar" }\n\n// Redis List memoize method\nredisService.memoizeList("saved-list") { return ["foo", "bar", "baz"] }\n\n// Redis Set memoize method\nredisService.memoizeSet("saved-set") { return ["foo", "bar", "baz"] as Set }\n\n// Redis Sorted Set memoize method\nredisService.memoizeScore("saved-sorted-set", "set-item") { return score }\nThe plugin also provides a few utility methods such as:
\nredisService.flushDB() // dangerous!!!! should probably only be used for test cleanup\n\n// deletes all keys in the database matching a pattern, this is fairly expensive\n// as it uses the <code>keys</code> operation. If you're doing this a lot and\n// have many keys in redis, you should be aggregating your own set of keys that\n// you'll later want to delete\nredisService.deleteKeysWithPattern("key:pattern:*")\nYou can have direct access to the pool of Redis connection objects by injecting redisPool into your code. Normally, you won't want to directly work with the pool, and instead interact with the redisService bean, but you have the option to manually work with the pool if desired.
def redisPool\nThe redis:memoize TagLib lets you leverage memoization within your GSP files. Wrap it around any expensive to generate text and it will cache it and quickly serve it from Redis.
<redis:memoize key="mykey" expire="3600">\n <!--\n insert expensive to generate GSP content here\n\n taglib body will be executed once, subsequent calls\n will pull from redis till the key expires\n -->\n <div id='header'>\n ... expensive header stuff here that can be cached ...\n </div>\n</redis:memoize>\nIf you are using multiple redis servers in your environment which are NOT clustered and would like to perform discrete operations on them seperately from a single application, you can accomplish that by by adding some configuration to your application.
\nThe configuration block for redis accepts the following connections block parameters.
\nConfig.groovy
\ngrails {\n redis {\n poolConfig {\n // pool specific tweaks here\n // for parms see https://github.com/xetorthio/jedis/blob/master/src/main/java/redis/clients/jedis/JedisPoolConfig.java\n // numTestsPerEvictionRun = 4\n }\n\n // requires either host & port combo, or a sentinels and masterName combo\n\n // use a single redis server (use only if nore using sentinel cluster)\n port = 6379\n host = "localhost"\n\n // use redis-sentinel cluster as opposed to a single redis server (use only if not use host/port)\n sentinels = [ "host1:6379", "host2:6379", "host3:6379" ] // list of sentinel instance host/ports\n masterName = "mymaster" // the name of a master the sentinel cluster is configured to monitor\n\n connections {\n cache {\n poolConfig {\n // pool specific tweaks here\n // for parms see https://github.com/xetorthio/jedis/blob/master/src/main/java/redis/clients/jedis/JedisPoolConfig.java\n // numTestsPerEvictionRun = 4\n }\n\n // requires either host & port combo, or a sentinels and masterName combo\n\n // use a single redis server (use only if nore using sentinel cluster)\n port = 6380\n host = "localhost"\n\n // use redis-sentinel cluster as opposed to a single redis server (use only if not use host/port)\n sentinels = [ "host1:6380", "host2:6380", "host3:6380" ] // list of sentinel instance host/ports\n masterName = "cache" // the name of a master the sentinel cluster is configured to monitor\n }\n search {\n poolConfig {\n // pool specific tweaks here\n // for parms see https://github.com/xetorthio/jedis/blob/master/src/main/java/redis/clients/jedis/JedisPoolConfig.java\n // numTestsPerEvictionRun = 4\n }\n\n // requires either host & port combo, or a sentinels and masterName combo\n\n // use a single redis server (use only if nore using sentinel cluster)\n port = 6381\n host = "localhost"\n\n // use redis-sentinel cluster as opposed to a single redis server (use only if not use host/port)\n sentinels = [ "host1:6381", "host2:6381", "host3:6381" ] // list of sentinel instance host/ports\n masterName = "search" // the name of a master the sentinel cluster is configured to monitor\n }\n }\n }\n}\nThe standard config block for the default connection has not changed. The new configuration is under the connections block. You will need to name your connections ('cache' and 'search' in the above block). The names must be unique.
A new service bean will be wired in addition to the default redisService bean with the capitalized connection name appended to it. For example the above two connections would create a redisServiceCache and redisServiceSearch bean you can reference from your application code. If desired, you can also access the connection-specific redisPool beans that are created using the same naming convention, in this example they would be redisPoolCache and redisPoolSearch.
In addition to the newly wired beans, you may also choose to continue using the standard redisService bean and simply refer to the connections by name when invoking targets on the service via redisService.withConnection('cache').withRedis{...} or redisService.withConnection('search').memoize(key){...}.
Note: It is up to you if you prefer using the main redisService bean and the withConnection method or if you want to inject the additional service beans. The end result is the same and the withConnection is simply a pass through to the newly created beans.
class FooService {\n\n def redisService\n // custom created beans for each connection, you can use these or just use the `withConnection` method\n // both methods are demonstrated below for example purposes, but you'd like choose one method or the other\n def redisServiceCache\n def redisServiceSearch\n\n def doWork(){\n redisService.withRedis { Jedis redis ->\n redis.set("foo", "bar")\n }\n\n redisService.withConnection('cache').withTransaction { Jedis redis ->\n redis.set("foo", "bar")\n }\n\n redisServiceSearch.withPipeline { Jedis redis ->\n redis.set("foo", "bar")\n }\n\n redisServiceCache.memoize("somecachekey") {Jedis redis ->\n return cacheData\n }\n\n redisService.withConnection('search').memoizeDomainList(Book, "domainkey"){\n return Book.findAllByTitleInList(["book1", "book3"])\n }\n\n redisService.memoizeDomainIdList(Book, "domainkey"){\n return Book.findAllByTitleInList(["book1", "book3"])\n }\n\n redisServiceCache.memoizeDomainObject(Book, "domainkey"){\n return Book.get(book1.id)\n }\n\n redisServiceSearch.memoizeHash("domainkey"){\n return [foo: "bar"]\n }\n }\n}\nIn addition to using the concrete and finite redisService.memoize* methods, as of version 1.2 you may now also annotate a method with an appropriate @Memoize* annotation. This will perform an AST transformation at compile time and wrap the entire body of the method with the corresponding memoization method. The parameters such as key and expire are passed into the annotation and used in the redisService memoize method calls.
\nThe following are available as annotations:
\n| Annotation | Description |
| @Memoize | Used to memoize methods that return a \"string\" - redisService.memoize |
| @MemoizeObject | Used to memoize methods that return an object - redisService.memoize |
| @MemoizeDomainObject | Used to memoize methods that return a domain object - redisService.memoizeDomain |
| @MemoizeDomainList | Used to memoize methods that return a domain object list - redisService.memoizeDomainList |
| @MemoizeHash | Used to memoize methods that return a hash - redisService.memoizeHash |
| @MemoizeHashField | Used to memoize methods that return a hash field - redisService.memoizeHashField |
| @MemoizeList | Used to memoize methods that return a list - redisService.memoizeList |
| @MemoizeSet | Used to memoize methods that return a set - redisService.memoizeSet |
| @MemoizeScore | Used to memoize methods that returns a score from a hash - redisService.memoizeScore |
There are integration usage tests written in spock for services at RedisMemoizeServiceSpec.groovy and for domains at RedisMemoizeDomainSpec.groovy
\nSince the value of the key must be passed in but will also be transformed by AST, we can not use the $ style gstring values in the keys. Instead you will use the # sign to represent a gstring value such as @Memoize(key = "#{book.title}:#{book.id}").
During the AST tranformation these will be replaced with the $ character and will evaluate correctly during runtime as redisService.memoize("${book.title}:${book.id}"){...}.
Anything that is not in the format key='#text' or key="${text}" will be treated as a string literal. Meaning that key="text" would be the same as using the literal string "text" as the memoize key redisService.memoize("text"){...} instead of the variable $text.
Any variable that you use in the key property of the annotation will need to be in scope for this to work correctly. You will only get a RUNTIME error if you use a variable reference that is out of scope.
\nThis also applies to the expire field.
You are not required to import the import grails.plugin.redis.RedisService namespace or declare the service def redisService on any objects you wish to use this annotation with as the AST transform will detect whether this field is on your object and add it for you. You may certainly have either the import or def statements if you would like, but they are not required if you use the @Memoize* annotations.
The user should be aware that any annotated method will be completely wrapped in the redis service call so any calculations that are contained within will also be wrapped and not executed of the key is in scope and not expired.
\nIf the compile succeeds but runtime fails or throws an exception, make sure the following are valid:\n* Your key OR value is configured correctly.\n* The key uses a #{} for all variables you want referenced.
\nIf the compile does NOT succeed make sure check the stack trace as some validation is done on the AST transform for each annotation type:\n* Required annotation properties are provided.\n* When using expire it is a valid Integer type variable.\n* When using value it is a valid closure.\n* When using key it is a valid String.
The @Memoize annotation is to be used when dealing with objects that are stored in Redis as strings. This annotation takes the following parameters:
\nvalue - A closure in the following format. (key OR value required)\nkey - A unique key for the data cache. (key OR value required)\nexpire - Expire time in seconds. Will default to never so only pass a value like 3600 if you want value to expire.\nYou can either specify a closure OR a key and expire. When using the closure style key @Memoize({"#{text}"}) you may not pass a key or expire to the annotation as the closure will be evaluated directly and used as the key value. This is due to a limitation on how Java deals with closure annotation parameters.
Here is an example of usage:
\n@Memoize({"#{text}"})\ndef getAnnotatedTextUsingClosure(String text, Date date) {\n println 'cache miss getAnnotatedTextUsingClosure'\n return "$text $date"\n}\n\n@Memoize(key = '#{text}')\ndef getAnnotatedTextUsingKey(String text, Date date) {\n println 'cache miss getAnnotatedTextUsingKey'\n return "$text $date"\n}\n\n//expire this extremely fast\n@Memoize(key = '#{text}', expire = '1')\ndef getAnnotatedTextUsingKeyAndExpire(String text, Date date) {\n println 'cache miss getAnnotatedTextUsingKeyAndExpire'\n return "$text $date"\n}\n\n//configurable expire time to live\n@Memoize(key = '#{text}', expire = '#{grailsApplication.config.cache.ttl}')\ndef getAnnotatedTextUsingKeyAndExpire(String text, Date date) {\n println 'cache miss getAnnotatedTextUsingKeyAndExpire'\n return "$text $date"\n}\n\n@Memoize(key = "#{book.title}:#{book.id}")\ndef getAnnotatedBook(Book book) {\n println 'cache miss getAnnotatedBook'\n return book.toString()\n}\nThe @MemoizeObject annotation is to be used when dealing with simple (non-domain) objects that are to have their contents stored in Redis in JSON form. The simple object being returned by the return statement will be converted to JSON, stored in Redis, then converted from JSON back to the object. It is important to ensure that the object class you're using is able to be converted to and from JSON for this annotation to work. This annotation takes the following parameters:
\nkey - A unique key for the data cache. (required)\nexpire - Expire time in seconds. Will default to never so only pass a value like 3600 if you want value to expire.\nclazz - The class of the object to be memoizing. (required)\nHere is an example of usage:
\n@MemoizeObject(key = "#{title}", expire = "#{grailsApplication.config.cache.ttl}", clazz = Book.class)\ndef createObject(String title, Date date) {\n println 'cache miss createObject'\n new Book(title: title, createDate: date)\n}\nThis method is also available from the RedisService:
redisService.memoizeObject(Book.class, title, grailsApplication.config.cache.ttl) {\n println 'cache miss createObject'\n new Book(title: title, createDate: date)\n}\nThe @MemoizeDomainObject annotation is to be used when dealing with domain objects that are to have their id's stored in Redis. See the documentation on Domain Object Memoization above for more details. This annotation takes the following parameters:
\nkey - A unique key for the data cache. (required)\nexpire - Expire time in seconds. Will default to never so only pass a value like 3600 if you want value to expire.\nclazz - The class of the object to be memoizing. (required)\nHere is an example of usage:
\n@MemoizeDomainObject(key = "#{title}", clazz = Book.class)\ndef createDomainObject(String title, Date date) {\n println 'cache miss createDomainObject'\n Book.build(title: title, createDate: date)\n}\nThe @MemoizeDomainList annotation is to be used when dealing with lists of domain objects that are to have their id's stored in Redis. See the documentation on Domain List Memoization above for more details. This annotation takes the following parameters:
\nkey - A unique key for the data cache. (required)\nexpire - Expire time in seconds. Will default to never so only pass a value like 3600 if you want value to expire.\nclazz - The class of the object to be memizing. (required)\nHere is an example of usage:
\n@MemoizeDomainList(key = "getDomainListWithKeyClass:#{title}", clazz = Book.class)\ndef getDomainListWithKeyClass(String title, Date date) {\n println 'cache miss getDomainListWithKeyClass'\n Book.findAllByTitle(title)\n}\nThe @MemoizeList annotation is to be used when dealing with list type objects. This annotation takes the following parameters:
\nvalue - A closure in the following format. (key OR value required)\nkey - A unique key for the data cache. (key OR value required)\nexpire - Expire time in seconds. Will default to never so only pass a value like 3600 if you want value to expire.\nYou can either specify a closure OR a key and expire. When using the closure style key @Memoize({"#{text}"}) you may not pass a key or expire to the annotation as the closure will be evaluated directly and used as the key value. This is due to a limitation on how Java deals with closure annotation parameters.
Here is an example of usage:
\n@MemoizeList(key = "#{list[0]}")\ndef getAnnotatedList(List list) {\n println 'cache miss getAnnotatedList'\n return list\n}\nThe @MemoizeScore annotation is to be used when dealing with scores in hashes. This annotation takes the following parameters:
\nkey - A unique key for the data cache. (required)\nexpire - Expire time in seconds. Will default to never so only pass a value like 3600 if you want value to expire.\nmember - The hash property to store. (required)\nHere is an example of usage:
\n@MemoizeScore(key = "#{map.key}", member="foo")\ndef getAnnotatedScore(Map map) {\n println 'cache miss getAnnotatedScore'\n return map.foo\n}\nThe @MemoizeHash annotation is to be used when dealing with maps/hash type objects. This annotation takes the following parameters:
\nvalue - A closure in the following format. (key OR value required)\nkey - A unique key for the data cache. (key OR value required)\nexpire - Expire time in seconds. Will default to never so only pass a value like 3600 (one hour) if you want value to expire.\nYou can either specify a closure OR a key and expire. When using the closure style key @Memoize({"#{text}"}) you may not pass a key or expire to the annotation as the closure will be evaluated directly and used as the key value. This is due to a limitation on how Java deals with closure annotation parameters.
Here is an example of usage:
\n@MemoizeHash(key = "#{map.foo}")\ndef getAnnotatedHash(Map map) {\n println 'cache miss getAnnotatedHash'\n return map\n}\nMost things remain the same except configuration in the application.yml file will be done not in dsl closure but YAML style.
---\ngrails:\n redis:\n poolConfig:\n maxIdle: 10\n doesnotexist: true\nThe package namespace has changed to grails.plugins.redis. Note the addition of the s in plugin[s].
@Memoize annotations currently do NOT work with domain objects and classes. We are working to fix this.
\nPreviously the @Memoize annotations would inject the redisService into your classes, due to changes in how beans are wired in grails 3.0.0+ it is recommended that you\ndefine the service in your classes like the following:
\nclass MyService {\n \n RedisService redisService\n \n @Memoize()\n def doFoo(){\n ...\n }\n \n}\norg.grails.plugins:redis. Moved bintray location. Breaking Change@Memoize annotations don't work on domain classes, most everything else works.database parameter in the config to pick a redis databasememoizeDomainObject and checking logging level before calling logging method@MemoizeObject annotation which allows for JSON representation to be stored in redis, moved log level of "optional" redis connections down to info, better handling/transformation of config valuesredisService.memoizeObject method (#34) with optional [cacheNull: false] flag (#35)RedisService is spring injected so that it's easier to mock out for tests by clients. Upgraded to Jedis 2.6.0.The Grails Retina Tag plugin adds retina tag image support to the asset pipeline <asset:image/> taglib.\nRetinaTag resolves this by extending <asset:image/> to create a hidpi_src attribute with the retina image path if it exists.
Add retina tag to your build config
\nplugins {\n\tcompile ':retina-tag:1.1.0'\n}\ndependencies {\n\tcompile 'com.bertramlabs.plugins:retina-tag:3.0.0'\n}\nAdd retina_tag.js to your application.js file after including jQuery:
//=require retina_tag\nAdd double pixel resolution images in your assets directory with the @2x modifier
\nlogo.png\nlogo@2x.png\nBe sure to also specify the base dimensions in your image_tag calls:
<asset:image src='logo.png' height=50/>\nAwesome right?
\nRetina tag listens to the global event on document called retina_tag:refresh. Firing this event will force retina_tag to rescan the dom for images and update their image src if necessary. Useful if loading content dynamically. Note: retina_tag automatically supports turbolinks.
In some cases it becomes necessary to override the data-hidpi-src attribute and skip asset pipeline. A good example of this might be to load a users profile picture which is stored elsewhere.
\n\t<asset:image src="${user.photo.url('medium')}" data-hidpi-src="${user.photo.url('medium_2x')" height="75%" width="75"/>\ngit checkout -b my-new-feature)git commit -am 'Added some feature')git push origin my-new-feature)##License\nThis project is licensed under the APACHE License.
\n" }, { + "deprecated": "This repository was archived by the owner on Dec 5, 2024. It is now read-only.", "bintrayPackage": { "name": "rx-gorm-rest-client", "repo": "plugins", @@ -5151,17 +5185,17 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/gorm-mongodb/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "6.1.7", "updated": "2020-07-06T19:52:37.703Z", "systemIds": [ "org.grails.plugins:rx-mongodb" ], - "vcsUrl": "https://github.com/grails/gorm-mongodb" + "vcsUrl": "https://github.com/apache/grails-core" }, "documentationUrl": "https://gorm.grails.org/latest/rx/manual/", "mavenMetadataUrl": null, - "readme": "\n
This project implements GORM for the MongoDB Document Database.
\nNOTE: This source code here is for version 6.x and above. For prevoius versions' source see the relevant branch on the Grails Data Mapping project.
\nFor more information see the following links:
\nFor the current development version see the following links:
\n\n" + "readme": "This project implements GORM for the MongoDB Document Database.
\nFor the current development version see the following links:
\n\n" }, { "bintrayPackage": { @@ -5276,16 +5310,16 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/scaffolding/issues", + "issueTrackerUrl": "https://github.com/apache/grails-core/issues", "latestVersion": "5.1.3", "updated": "2024-11-20T12:41:42.000Z", "systemIds": [ - "org.grails.plugins:scaffolding" + "org.apache.grails:grails-scaffolding" ], - "vcsUrl": "https://github.com/grails/scaffolding" + "vcsUrl": "https://github.com/apache/grails-core" }, "documentationUrl": null, - "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/plugins/scaffolding/maven-metadata.xml", + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-scaffolding/maven-metadata.xml", "readme": null }, { @@ -5390,6 +5424,7 @@ "readme": null }, { + "deprecated": "This repository was archived by the owner on Jan 18, 2023. It is now read-only.", "bintrayPackage": { "name": "segment", "repo": "plugins", @@ -5549,17 +5584,17 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails-plugins/grails-spring-security-acl/issues", + "issueTrackerUrl": "https://github.com/apache/grails-spring-security/issues", "latestVersion": "4.0.0.M2", "updated": "2019-04-18T15:29:17.202Z", "systemIds": [ - "org.grails.plugins:spring-security-acl" + "org.apache.grails:grails-spring-security-acl" ], - "vcsUrl": "https://github.com/grails-plugins/grails-spring-security-acl" + "vcsUrl": "https://github.com/apache/grails-spring-security" }, "documentationUrl": "https://grails-plugins.github.io/grails-spring-security-acl/", "mavenMetadataUrl": null, - "readme": "[![\"Build](\"https://travis-ci.org/grails-plugins/grails-spring-security-acl.svg?branch=master\")
See documentation for further information.
\nTo run the tests exeucte:
\n./gradlew -Dgeb.env=chromeHeadless check
See documentation for further information.
\nTo run the tests exeucte:
\n./gradlew -Dgeb.env=chromeHeadless check
![\"Build](\"https://travis-ci.org/grails-plugins/grails-spring-security-ldap.svg\")
See documentation for further information.
\nIntroduction to Lightweight Directory Services
\nBranches:
\nmaster Grails 4 compatible versions.3.x Grails 3 compatible versions.See documentation for further information.
\nIntroduction to Lightweight Directory Services
\nBranches:
\nmaster Grails 4 compatible versions.3.x Grails 3 compatible versions.![\"Build](\"https://travis-ci.org/alvarosanchez/grails-spring-security-rest.png?branch=develop\")
\n![\"Latest](\"https://api.bintray.com/packages/grails/plugins/spring-security-rest/images/download.svg\")
\n![\"Known](\"https://snyk.io/test/github/alvarosanchez/grails-spring-security-rest/develop/badge.svg\"){kind=icon}
Grails plugin to implement a stateless, token-based, RESTful authentication\nusing Spring Security. Sponsored and supported by Object Computing Inc.
\nDocumentation:
\nAre you using this plugin and want to be listed here? Include your company yourself.
\n#spring-security-rest channel in Slack.grails and spring-security-rest tags.NOTE: if you have questions or issues, enable debug logging,\nand include the output in your request.
\nThis software is licensed under the terms of the Apache License, Version 2.0
\n" }, { "bintrayPackage": { - "name": "spring-security-rest-gorm", + "name": "grails-spring-security-rest-datamapping", "repo": "plugins", "owner": "grails", "desc": "Spring Security REST plugin for Grails - GORM module", @@ -6042,16 +6077,16 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails-plugins/grails-spring-security-rest/issues", + "issueTrackerUrl": "https://github.com/apache/grails-spring-security/issues", "latestVersion": "3.0.1", "updated": "2020-04-06T05:51:13.612Z", "systemIds": [ - "org.grails.plugins:spring-security-rest-gorm" + "org.apache.grails:grails-spring-security-rest-datamapping" ], - "vcsUrl": "https://github.com/grails-plugins/grails-spring-security-rest" + "vcsUrl": "https://github.com/apache/grails-spring-security" }, "documentationUrl": "https://grails-plugins.github.io/grails-spring-security-rest/latest/docs/", - "mavenMetadataUrl": null, + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-spring-security-rest-datamapping/maven-metadata.xml", "readme": "\n\n
Grails plugin to implement a stateless, token-based, RESTful authentication\nusing Spring Security. Sponsored and supported by Object Computing Inc.
\nDocumentation:
\nAre you using this plugin and want to be listed here? Include your company yourself.
\n#spring-security-rest channel in Slack.grails and spring-security-rest tags.NOTE: if you have questions or issues, enable debug logging,\nand include the output in your request.
\nThis software is licensed under the terms of the Apache License, Version 2.0
\n" }, { @@ -6109,7 +6144,7 @@ }, { "bintrayPackage": { - "name": "spring-security-rest-redis", + "name": "grails-spring-security-rest-redis", "repo": "plugins", "owner": "grails", "desc": "Spring Security REST plugin for Grails - Redis module", @@ -6122,16 +6157,16 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails-plugins/grails-spring-security-rest/issues", + "issueTrackerUrl": "https://github.com/apache/grails-spring-security/issues", "latestVersion": "3.0.1", "updated": "2020-04-06T05:51:18.295Z", "systemIds": [ - "org.grails.plugins:spring-security-rest-redis" + "org.apache.grails:grails-spring-security-rest-redis" ], - "vcsUrl": "https://github.com/alvarosanchez/grails-spring-security-rest" + "vcsUrl": "https://github.com/apache/grails-spring-security" }, "documentationUrl": "https://grails-plugins.github.io/grails-spring-security-rest/latest/docs/", - "mavenMetadataUrl": null, + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-spring-security-rest-redis/maven-metadata.xml", "readme": "\n\n
Grails plugin to implement a stateless, token-based, RESTful authentication\nusing Spring Security. Sponsored and supported by Object Computing Inc.
\nDocumentation:
\nAre you using this plugin and want to be listed here? Include your company yourself.
\n#spring-security-rest channel in Slack.grails and spring-security-rest tags.NOTE: if you have questions or issues, enable debug logging,\nand include the output in your request.
\nThis software is licensed under the terms of the Apache License, Version 2.0
\n" }, { @@ -6215,7 +6250,7 @@ }, { "bintrayPackage": { - "name": "spring-security-ui", + "name": "grails-spring-security-ui", "repo": "plugins", "owner": "grails", "desc": "Grails Spring Security UI", @@ -6226,16 +6261,16 @@ "licenses": [ "Apache-2.0" ], - "issueTrackerUrl": "https://github.com/grails/grails-spring-security-ui/issues", + "issueTrackerUrl": "https://github.com/apache/grails-spring-security/issues", "latestVersion": "4.0.0-RC1", "updated": "2022-09-07T00:00:00.000Z", "systemIds": [ - "org.grails.plugins:spring-security-ui" + "org.apache.grails:grails-spring-security-ui" ], - "vcsUrl": "https://github.com/grails-plugins/grails-spring-security-ui" + "vcsUrl": "https://github.com/apache/grails-spring-security" }, "documentationUrl": "https://grails.github.io/grails-spring-security-ui/", - "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/grails/plugins/spring-security-ui/maven-metadata.xml", + "mavenMetadataUrl": "https://repo1.maven.org/maven2/org/apache/grails/grails-spring-security-ui/maven-metadata.xml", "readme": "Grails websocket chat Plugin provides a multi-chat room add-on to an existing grails based site/application.
\nVideo: Client/Server Messaging part 1.\nEarlier version focus on backend control of socket messages. So the backend of your application. Override a service for this. Explained in links further below.
\nVideo: Client/Server Messaging part 2\n(Messages via websockets to frontend). In short update frontend via websocket callbacks.
\nVideo: 1.22 Multiple login with same Chat user and TicTacToe
\nVideo 1.23-SNAPSHOT1 Live chat Logs BOT Artificial Intelligence and more
\nVideo 1.24 Chat BOT now working in chat rooms, returning responses and banning/kicking users
\nVideo 1.25 LiveChat (1 room multiple users with 1 admin interacting with all)
\nVideo 3.0.6 1.27 LiveChat monitoring and changing live chat style/colours
\n3.0.6/1.27 \t- Major tidyup removed most ajax processing besides popup pages. \n\t\t\t Added css/internationlisation customisation\n\t\t\t \n3.0.5/1.26\t- Tidy up with new look and new feature to monitor Live Chat requests\n3.0.4/1.25 - Live Chat Many users to 1 admin (Video 10).\n\n3.0.3/1.24 - ChatBot and badWords added to the main chat room\n\n3.0.3/1.23 - Live Chat feature added as part of the plugin(watch video 7)\n\n3.0.3/1.21 - Websocket TicTacToe game added (Watch video 6)\n\n3.0.3/1.20 - Multiple login with same user but must be different rooms - removal of dbSupport check\n\n1.18 - Mediastreaming enabled but has not worked for me \n \n1.17 - Websocket -> WebRTC File sharing peer2peer available - \n \n1.12 - Chat room bookings for multiple participants\n \n1.0+ - Supports WebRTC currently only on Chrome Canary.\n\n0.19+ - Supports webcam tested on chrome/firefox.\n\nAdmin can: kick/Ban (for specified time period)\nUsers can create profiles define details and upload photos.\nChat rooms can be created in Config.groovy +/ DB once logged in using UI.\n\nYou can websocket :\n\tsend files / use webRTC technology to have video chat or share screen\n\tplay Tictactoe / noughts + crosses\n\tLive chat - set up a client easily and monitor live chats\n\tConfigure chat bookings / invite external attendees (emails)\n