Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Turbine Wiki" for 
change notification.

The "Turbine4/Turbine4.0M1/Migrate233" page has been changed by ThomasVandahl:
https://wiki.apache.org/turbine/Turbine4/Turbine4.0M1/Migrate233?action=diff&rev1=26&rev2=27

Comment:
Clarify scheduler file location

              basePackage="your.base.package.">
      ...
  }}}
-  
+ 
  === SecurityService ===
  
  The !TorqueSecurityService has been replaced with the 
[[http://turbine.apache.org/fulcrum/fulcrum-security/index.html|Fulcrum 
Security Components]]. The following example shows the default configuration of 
the ''!SecurityService'' before and after the migration. For details of the 
configuration options available see the 
[[http://turbine.apache.org/fulcrum/fulcrum-security/index.html|Fulcrum 
Security Site]]. Additional information may be found here: 
[[Turbine4/Turbine4.0M1/Diff|4.0M1 -> 4.0M2: Updating Fulcrum Service as 
Default]].
  
-  
+ 
  
  
  `TurbineResources.properties`:
@@ -559, +559 @@

          default-class="org.apache.torque.avalon.TorqueComponent"
          early-init="true" />
  
-     <!-- These components belong to the Fulcrum-Security services -->        
+     <!-- These components belong to the Fulcrum-Security services -->
      <role
          name="org.apache.fulcrum.security.SecurityService"
          shorthand="securityService"
@@ -609, +609 @@

  `componentConfiguration.xml`:
  
  {{{#!xml
-     <!-- These components belong to the Fulcrum-Security services -->        
+     <!-- These components belong to the Fulcrum-Security services -->
      <securityService/>
      <authenticator/>
      <modelManager/>
@@ -636, +636 @@

  
  === SchedulerService ===
  
- The !TurbineSchedulerService has been replaced with different 
implementations. The old !TurbineSchedulerService has been renamed to 
!TorqueSchedulerService (because this is what it always was) and is now 
deprecated. 
+ The !TurbineSchedulerService has been replaced with different 
implementations. The old !TurbineSchedulerService has been renamed to 
!TorqueSchedulerService (because this is what it always was) and is now 
deprecated.
  The recommended implementation now is the !QuartzSchedulerService which is 
based on the [[http://turbine.apache.org/fulcrum/fulcrum-quartz/|Fulcrum 
Quartz]] component. The following example shows the default configuration of 
the ''!SchedulerService'' before and after the migration. For details of the 
configuration and persistence options available see the 
[[http://turbine.apache.org/fulcrum/fulcrum-quartz/|Fulcrum Quartz Site]].
  
  `TurbineResources.properties`:
@@ -676, +676 @@

  `roleConfiguration.xml`:
  
  {{{#!xml
-     <!-- Service required for the QuartzSchedulerService -->        
+     <!-- Service required for the QuartzSchedulerService -->
      <role
          name="org.apache.fulcrum.quartz.QuartzScheduler"
          shorthand="quartz"
@@ -694, +694 @@

          configuration/properties := a set of properties to configure Quartz
          configuration/properties/parameter := a  single configuration
          configuration/properties/parameter@name := the name of the property
-         configuration/properties/parameter@value := the value of the property 
                   
+         configuration/properties/parameter@value := the value of the property
      -->
  
      <quartz>
@@ -709, +709 @@

                  <parameter name="org.quartz.jobStore.misfireThreshold" 
value="60000"/>
                  <parameter name="org.quartz.jobStore.class" 
value="org.quartz.simpl.RAMJobStore"/>
                  <parameter name="org.quartz.plugin.jobInitializer.class" 
value="org.quartz.plugins.xml.XMLSchedulingDataProcessorPlugin"/>
-                 <parameter name="org.quartz.plugin.jobInitializer.fileNames" 
value="/WEB-INF/conf/quartz.xml"/>
+                 <parameter name="org.quartz.plugin.jobInitializer.fileNames" 
value="quartz.xml"/>
                  <parameter 
name="org.quartz.plugin.jobInitializer.failOnFileNotFound" value="true"/>
                  <parameter 
name="org.quartz.plugin.jobInitializer.scanInterval" value="120"/>
                  <parameter 
name="org.quartz.plugin.jobInitializer.wrapInUserTransaction" value="false"/>
@@ -718, +718 @@

      </quartz>
  }}}
  
- The actual configuration of the jobs is delegated to the file `quartz.xml` or 
any other persistence mechanism supported by 
[[http://www.quartz-scheduler.org/|Quartz Scheduler]]. An example configuration 
is shown below. 
+ The actual configuration of the jobs is delegated to the file `quartz.xml` or 
any other persistence mechanism supported by 
[[http://www.quartz-scheduler.org/|Quartz Scheduler]]. An example configuration 
is shown below. By default, the file name `quartz.xml` must be fully qualified.
+ If the file is not found in the file system, it is being loaded from the 
class path.
+ 
  For backward compatibility with legacy scheduled jobs, the following 
conventions must be met:
   * the simple module name of the scheduled job must be placed into the 
`<name></name>` tag
   * the job group must be `TURBINE`
@@ -855, +857 @@

   * `org.apache.turbine.util.security.DataBackendException` with 
`org.apache.fulcrum.security.util.DataBackendException`
   * `org.apache.turbine.util.security.UnknownEntityException` with 
`org.apache.fulcrum.security.util.UnknownEntityException`
   * `org.apache.turbine.util.security.PasswordMismatchException` with 
`org.apache.fulcrum.security.util.PasswordMismatchException`
-  * `org.apache.turbine.om.security.*` with 
`org.apache.fulcrum.security.entity.*` 
+  * `org.apache.turbine.om.security.*` with 
`org.apache.fulcrum.security.entity.*`
   * ...
  
  === Actually Modify Code ===

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to