- OrderCRUDController refactored
- Save or update for OrderSyncInfo instead of creating new instance for each sync
- Name change for TimImpExpInfo to SynchronizationInfo
- JiraSyncInfo is removed instead SynchronizationInfo is used
- All files which are affected by name changes are modified
- Translations added where applicable
- clean up unused variables etc
- JIRA is moved to connectors and all files modified that has to do with this change.
- JiraConfiguration file is removed
- ImportedLabel attribute is deleted from Order and order.hbm.xml
- Imstead of importedLabel is now used the key from OrderSyncInfo
- and some more changes where applicable
Better error handling:
* check if connector connection values are valid
* New ConnectorException
* New .zul file to show import/export failed/success information
* All files modified affected by these changes
* CRUD for scheduler
* The UI job_scheduling.zul for CRUD is splits to _editJobScheduling.zul and _listJobScheduling.zul
* Lots of changes in scheduler to make it generic
- jobs can be scheduled, rescheduled and deleted
- check if job has a connector and is enabled
- check if job is allowed to be scheduled
- do manual is moved to JobConfigurationController
* attributes connectorName and scheduled added to JobSchedulerConfiguration modified
* triggerGroup and triggerName deleted from JobScheduleerConfiguration
* In JobConfigurationDAO findByConnectorName added
* New JobClassNameEnum added to be used as data type for JobClassName in JobSchedulerConfiguration
* Import/Export Jobs read the beans that do the real work from ApplicationContext
* Some minor changes in ConfigurationController
AppProperties entity has been removed as it stores the same information
(majorId) repeated in each database record and it doesn't match with the real
model that we need.
A new entity Connector with a majorId identifier has been created, this entity
contains a list of properties (pairs key-value).
Moreover it has been created the predefined Tim connector with its own
properties (predefined too).
For new connectors, apart from the specific classes implementing them it would
be only needed to modify PredefinedConnectors and PredefinedConnectorProperties.
The database will be updated automatically on LibrePlan startup thanks to the
ConnectorBootstrap.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
- Import rosters for all departments configured in DB implemented
- Unneeded checks for resource calendar removed
- Some hardcoded strings moved to constants
- Exception with 0h effort allowed
- confirmSave is used to update exceptions
- RESOURCE_HOLIDAY or BANK_HOLIDAY used correctly
- calculating exception hours solved
* Renamed .zul file and page to "Job Scheduling".
* Include ROLE_JOB_SCHEDULING in default profile SYSTEMS_ADMINISTRATOR.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
Like in the case of JIRA, the Tim synchronization UI in the project edition will
only appear if Tim connector is activated.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
Lots of changes:
* Created a new model to follow the standard structure of controllers in
LibrePlan.
* Marked several strings to be internationalized.
* Improved .zul page, removing unneeded stuff and simplifying code.
* Checked that cron expression is right, otherwise inform the user.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
Maybe it's not needed to get all workers, so the call to findAll has been changed by findByCode.
Moreover, it was using code in ExportTimesheetsToTim and NIF in
ImportRosterFromTim which was not coherent, so it has been changed to use code
in both places.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
It makes code simpler than using Calendar API, and it's the common way to manage
dates into LibrePlan.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
DTO classes are renamed to class-name with suffix DTO according to Libreplan naming convention
Modified all classes which are affected by the renamed classes
Comments and author information added where applicable
Test cases modified
An implementation of the interface IImportRosterFromTim
It import rosters from Tim convert them to workers calendar exception. If
worker's calendar exception already exists it updates effort duration, otherwise
creates new worker's calendar exception.
This client creates SOAP message, makes connection to the SOAP server, sends
the request and processes the response. It uses jaxb lirary to marshal and
unmarshal the request and response.
An implementation of the interface ISchedulerManager
Dynamically creates jobs and cron triggers. It associated the triggers with the jobs and add
them to the scheduler. It also supports the rescheduling of jobs.
