Skip to content

Latest commit

 

History

History
86 lines (72 loc) · 3.44 KB

UPGRADE-1.1.0.md

File metadata and controls

86 lines (72 loc) · 3.44 KB
Raw

Upgrade from 1.0.x to 1.1.0

Provisioning

The provisioning functionality changed in a massive way. Up from 1.1.0-beta1, as result of closing issue 760, provisioning is part of application deployment and not of thecontainer start-up process. This results in the possiblity to use classes, that are part of your application, because the applications autoloader are now loaded prior provisioning.

In case, that your application is distributed with a provision.xml, either in the WEB-INF or META-INF folder, you have to change the provision.xml distributed with your application from

<?xml version="1.0" encoding="UTF-8"?>
<provision xmlns="http://www.appserver.io/appserver">
    <datasource name="appserver.io-example-application"/>
    <installation>
        <steps>
            <step type="AppserverIo\Appserver\Core\Provisioning\CreateDatabaseStep">
                <params>
                    <param name="pathToEntities" type="string">common/classes/AppserverIo/Apps/Example/Entities</param>
                </params>
            </step>
        </steps>
    </installation>
</provision>

to

<?xml version="1.0" encoding="UTF-8"?>
<provision xmlns="http://www.appserver.io/appserver">
    <datasource name="appserver.io-example-application"/>
    <installation>
        <steps>
            <step type="AppserverIo\Appserver\Provisioning\Steps\CreateDatabaseStep">
                <params>
                    <param name="pathToEntities" type="string">common/classes/AppserverIo/Apps/Example/Entities</param>
                </params>
            </step>
        </steps>
    </installation>
</provision>

Only change is the type declaration for the provisioning steps, that changed from AppserverIo\Appserver\Core\Provisioning to AppserverIo\Appserver\Provisioning\Steps\CreateDatabaseStep.

Scanner Initialization

The scanner initialization now needs a factory class to instanciate the apropriate scanner instance.

Instead to specify the scanner type only

  <scanner name="logrotate" 
           type="AppserverIo\Appserver\Core\Scanner\LogrotateScanner">
    <params>
      <param name="interval" type="integer">1</param>
      <param name="extensionsToWatch" type="string">log</param>
      <param name="maxFiles" type="integer">10</param>
      <param name="maxSize" type="integer">1048576</param>
    </params>
    <directories>
      <directory>var/log</directory>
    </directories>
  </scanner>
</scanners>

now the factory attribute is necessary to create a new scanner instance

<scanner name="logrotate" 
         type="AppserverIo\Appserver\Core\Scanner\LogrotateScanner"
         factory="AppserverIo\Appserver\Core\Scanner\DirectoryScannerFactory">
    <params>
      <param name="interval" type="integer">1</param>
      <param name="extensionsToWatch" type="string">log</param>
      <param name="maxFiles" type="integer">10</param>
      <param name="maxSize" type="integer">1048576</param>
    </params>
    <directories>
      <directory>var/log</directory>
    </directories>
  </scanner>
</scanners>

Actually two default factories are provided. The DirectoryScannerFactory expects a <directories/> node, whereas the StandardScannerFactory does not. If you use the DirectoryScannerFactory, behind the scenes a separate scanner instance for each directory will be created. As each scanner is a thread, keep in mind, that this could lead to a massive CPU usage.