Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

com.jensfendler:ninja-sitemap

Package Overview
Dependencies
Maintainers
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

com.jensfendler:ninja-sitemap

Sitemap Generator Module for the Ninja Web Framework

  • 0.0.4
  • Source
  • Maven
  • Socket score

Version published
Maintainers
1
Source

Ninja Sitemap

A Sitemap generator module for the Ninja Framework, based on the Jirka Pinkas' Java Sitemap Generator.

Features:

The Ninja Sitemap module can automatically create single sitemap entries for non-dynamic routes (i.e. routes for unique URIs, without any path parameters). For "dynamic" routes (i.e. routes for URIs with {...}-style variable parts, you can register a custom SitemapMultiPageProvider instance for every such route, which can create any number of entries for your sitemap.xml (e.g. based on your database contents). Of course, you can also register a SitemapMultiPageProvider for non-dynamic routes, if you want them to result in a different sitemap entry, or result in more than one entry for your sitemap.

For every entry in your sitemap, you can specify the priority, the changeFrequency, and the actual path, if you want to. All of these are optional. However, for "dynamic" routes you will have to provide a SitemapMultiPageProvider, as the module has no chance to figure out what kind of content in your URIs should result in a sitemap entry.

Basic Usage:

  • ninja-sitemap has been published on Maven Central. Add the following dependency to your Ninja application's pom.xml:

    <dependency>
        <groupId>com.jensfendler</groupId>
        <artifactId>ninja-sitemap</artifactId>
        <version>0.0.3</version>
    </dependency>

  • Install an instance of the NinjaSitemapModule in your Ninja application's conf.Modules class:

	install(new NinjaSitemapModule());

If you plan to use Guice injection in your SitemapMultiPageProvider classes (see useInjector setting below), you need to bind the respective classes here as well. E.g.


   bind( ProductSitemapMultiPageProvider.class );
  • Inject NinjaSitemapRoutes into your conf.Router class, and make a call to its init(Router) method:
	@Inject
	NinjaSitemapRoutes sitemapRoutes;

    public void init(Router router) {

        sitemapRoutes.init(router);
        
        // ... your application's routes go here
    }

  • Configure the URL prefix for all entries in your sitemap through your application.conf:

ninja.sitemap.prefix=https://www.myserver.com:8443/basePath/

  • Annotate all controller methods with @Sitemap annotations, if you want them to be included in your resulting sitemap.xml.

Example:


@Singleton
public class MyContoller {

	// create a single sitemap entry with default priority and change frequency
    @Sitemap
    public Result aboutUs(Context context) {
        // ...
    }
    
    // create a single sitemap entry with maximum priority and an hourly change frequency
    @Sitemap(priority=1.0, changeFrequency=Sitemap.HOURLY)
    public Result homepage(Context context) {
        // ...
    }


    // Create multiple entries in the sitemap for a controller method with `@PathParam` arguments
    // A SimpleMultiPageProvider instance will be created straight from the given class (without Guice injection) 
    @Sitemap(multiPageProvider="modules.SimpleMultiPageProvider")
    public Result productDetails(Context context, @PathParam("productId") long productId) {
        // ...
    }
    
    // Create multiple entries in the sitemap for a controller method with `@PathParam` arguments
    // A ProductSitemapMultiPageProvider instance will be created using the Guice injector, to allow e.g.
    // injection of DAOs or other Ninja modules. 
    @Sitemap(multiPageProvider="modules.ProductSitemapMultiPageProvider", useInjector=true)
    public Result productDetails(Context context, @PathParam("productId") long productId) {
        // ...
    }
}

  • You should now be able to view your sitemap by pointing your browser to /sitemap.xml (under your application's context path).

For further details, please have a look at the JavaDoc documentation, especially of the Sitemap.java annotation code.

Ninja Configuration Properties

Ninja Sitemap can be configured further with some properties in your application.conf file as follows:

  • ninja.sitemap.prefix (String): The prefix URL to use for all entries in the sitemap. This property should always be configured to ensure correct URLs in your sitemap. (See above).

  • ninja.sitemap.route (String): the route (URI) to use for pointing to the generated sitemap.xml file. Default: /sitemap.xml

  • ninja.sitemap.expires (String): The expiry time of the cached sitemap after an update. This must be a string compatible with the time format of the NinjaCache interface (e.g. "12h"). Default: "6h".

  • ninja.sitemap.ping.google (boolean): If true, the Google search engine will be notified every time your sitemap has been updated. Default: false.

  • ninja.sitemap.ping.bing (boolean): If true, the Bing search engine will be notified every time your sitemap has been updated. Default: false.

  • ninja.sitemap.multiPageWarnings (boolean): If true, warning messages will be logged when the sitemap generator encounters a non-dynamic method which has been configured to use a SitemapMultiPageProvider (i.e. might result in more than one entry in the sitemap). If you know what you are doing, and these warnings annoy you, set this property to false to switch them off. Default: true.

  • ninja.sitemap.routeDetailsProvider (String): The name of a class implementing the SitemapRouteDetails interface. Your own implementation of this class can then control details such as the last-modified date, changeFrequency, and priority for each entry in your sitemap dynamically at run-time (rather than set to fixed values using the annotation parameters). Default: com.jensfendler.ninjasitemap.SimpleSitemapRouteDetails.

License

Copyright (C) 2016 Fendler Consulting cc. This work is licensed under the Apache License, Version 2.0. See LICENSE for details.

FAQs

Package last updated on 23 May 2016

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc