Roland Häder [Wed, 1 Nov 2017 20:58:38 +0000 (21:58 +0100)]
Continued:
- had to rename Headquarters again, to Headquarter to make room for a tools
class, it is common to name them <Entity>s and Headquarterss is not correct
Roland Häder [Wed, 1 Nov 2017 20:21:18 +0000 (21:21 +0100)]
Continued:
- removed suffix Data, just Headquarters is okay here, not for basic data
entity, of course
- renamed exception, only company headquarters will exist
- added checked exception which is being thrown when headquarters with same
address already exists
Roland Häder [Mon, 16 Oct 2017 18:28:23 +0000 (20:28 +0200)]
Continued:
- no other employees than company/business employees will be there ...
- renamed Employee interface to a much nicer Employable name
- renamed CompanyDepartment -> BusinessDepartment as there will be other kinds
of departments (e.g. fire/police)
- renamed more company -> business, but not all
Roland Häder [Sat, 14 Oct 2017 12:59:58 +0000 (14:59 +0200)]
Continued:
- need to change CascadeType to ALL as this should be persisted and all others
- also changed back from ALL to REFRESH as the foreign entities do already exist
Roland Häder [Sat, 7 Oct 2017 22:17:52 +0000 (00:17 +0200)]
Continued (renaming-season has started):
- renamed OpeningTimes -> OpeningTime as it is a single entity anyway
- also renamed package opening_times -> opening_time
- add event for when an opening time has been added
Roland Häder [Sat, 7 Oct 2017 19:55:01 +0000 (21:55 +0200)]
Continued:
- added event when department has been added
- added exception for not-found opening times
- added utils class for departments
- fixed some tzpos here and there
- used REFRESH instead of ALL as else maybe the other entityos being duplicated
- added first 2 named queries for opening times
- renamed CompanyDepartment -> Department
Roland Häder [Sun, 24 Sep 2017 19:13:57 +0000 (21:13 +0200)]
Continued:
- user "owner" is no longer required for employee as it may not be available at
all times
- one opening-times line is maybe not enough as they may varry from day to day
Roland Häder [Sun, 24 Sep 2017 12:33:39 +0000 (14:33 +0200)]
Continued:
- branch offices may have an "owning employee" which is a personal who may own
one or more branch offices with e.g. franchise supermarkets
- they may also have separate opening times depending on local laws
Roland Häder [Wed, 20 Sep 2017 18:37:12 +0000 (20:37 +0200)]
Continued:
- need to have serial number unique accross project's JARs
- added named query SearchBranchOfficeById which searches for branch office
entity by it's primary key
Roland Häder [Sun, 10 Sep 2017 19:19:05 +0000 (21:19 +0200)]
Continued:
- renamed exceptions BusinessDataBlaException was to generic, it should be
BasicCompanyDataBlaException
- renamed BranchOfficeUtils -> BranchOffices as this is more common
- fixed imports
Roland Häder [Fri, 8 Sep 2017 23:22:59 +0000 (01:22 +0200)]
Continued:
- added utilities class for branch offices
- added event class/interface for branch offices being added
- added exception when a branch office has already been added
- renamed branchPhoneNumber -> branchLandLineNumber as everywhere is land-line
used
- sorted members
- added contructor CompanyBranchOffice() with all required fields and validated
parameters before setting them
- also need to add default constructor as the JPA requires it
- renamed companyDataId -> basicDataId
Roland Häder [Sun, 3 Sep 2017 22:54:42 +0000 (00:54 +0200)]
Continued:
- renamed branchCompanyContact -> branchCompany
- added new entity field/property "branchContactEmployee", an employee may act
as a contact person in this branch office
- added first named query for branch office entity: "AllBranchOffices"
- renamed package "branch" -> "branchoffice"
- added event for when an administrator has added basic company data
Roland Häder [Sat, 19 Aug 2017 18:33:19 +0000 (20:33 +0200)]
Continued:
- moved business (basic) data related exceptions to own package
- added exception when a company employee was not found
- some auto-formatting
Roland Häder [Thu, 27 Jul 2017 20:04:23 +0000 (22:04 +0200)]
Continued:
- renamed field where an employee is a contact person within the company
- added named query to search for entities based on primary key (id)
Roland Häder [Sun, 23 Jul 2017 16:53:05 +0000 (18:53 +0200)]
Continued a bit:
- also headquarters are maybe optional (unknown to the user)
- added initial named query which loads all basic business data
- legal status may be empty for self-employed persons (single-person companies)
Roland Häder [Sun, 23 Jul 2017 11:49:34 +0000 (13:49 +0200)]
Having basic data and "business contact" which is really no contact in general
terms was a bad style anyway. Now these two entities are merged into
"BusinessBasicData" and kept in main package of this project.
Roland Häder [Sun, 23 Jul 2017 11:38:27 +0000 (13:38 +0200)]
owner is already given in "super-entity" BusinessContact, which may need
renaming because it is not a contact, but an abstract business entity where all
data of that (entire) business is attached to, like employees, branch offices
and so on.
Roland Häder [Sat, 3 Sep 2016 08:41:48 +0000 (10:41 +0200)]
Continued a bit:
- added "own" enumeration for day-of-week (the default is currently not supported by JPA)
- see: http://stackoverflow.com/questions/2243730/jpa-hibernate-embedded-and-enum
projects / jcontacts-business-core.git / log