Package com.vaadin.flow.server.startup

Class DefaultApplicationConfigurationFactory

java.lang.Object
com.vaadin.flow.server.startup.AbstractConfigurationFactory
com.vaadin.flow.server.startup.DefaultApplicationConfigurationFactory
All Implemented Interfaces:
ApplicationConfigurationFactory, Serializable
Direct Known Subclasses:
SpringApplicationConfigurationFactory
public class DefaultApplicationConfigurationFactory extends AbstractConfigurationFactory implements ApplicationConfigurationFactory
Default implementation of ApplicationConfigurationFactory.
Since:
Author:
Vaadin Ltd
See Also:

  • Constructor Details

    • DefaultApplicationConfigurationFactory

      public DefaultApplicationConfigurationFactory()

  • Method Details

    • create

      public ApplicationConfiguration create(VaadinContext context)
      Description copied from interface: ApplicationConfigurationFactory
      Creates a new instance of ApplicationConfiguration for the given context.
      Specified by:
      create in interface ApplicationConfigurationFactory
      Parameters:
      context - the context to create a configuration for
      Returns:
      the configuration created based on the context

    • doCreate

      protected DefaultApplicationConfigurationFactory.ApplicationConfigurationImpl doCreate(VaadinContext context, Map<String,String> properties)
      Creates application configuration instance based on provided data.
      Parameters:
      context - the Vaadin context, not null
      properties - the context parameters, not null
      Returns:
      a new application configuration instance

    • getTokenFileFromClassloader

      protected String getTokenFileFromClassloader(VaadinContext context) throws IOException
      Gets token file from the classpath using the provided context.

      The contextClass may be a class which is defined in the Web Application module/bundle and in this case it may be used to get Web Application resources. Also a VaadinContext context instance may be used to get a context of the Web Application (since the contextClass may be a class not from Web Application module). In WAR case it doesn't matter which class is used to get the resources (Web Application classes or e.g. "flow-server" classes) since they are loaded by the same ClassLoader. But in OSGi "flow-server" module classes can't be used to get Web Application resources since they are in different bundles.

      Parameters:
      context - a VaadinContext which may provide information how to get token file for the web application
      Returns:
      the token file content
      Throws:
      IOException - if I/O fails during access to the token file