Also needs to be moved as jcontact-business-core has changed (good convention).

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

fixed tpzo

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Continued a bit:
- renamed classes as this is the naming convention
- fixed super bean class

Signed-off-by: Roland Häder <roland@mxchange.org>

added missing dependency jcontacts-business-core/lib

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick (when needed):
- duplicated BusinessDataSessionBean as (correctly) AdminBusinessDataSessionBean
- implemented generic business data EJB with first method which returns an
  entity for given id number or throws a proper exception if not found

Signed-off-by: Roland Häder <roland@mxchange.org>

Possibly cherry-pick:
- added initial EJB for business contact-data

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

added .gitattributes where missing

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

added documentation for cdi-api.jar

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

it is user->login, not login->user

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Opps ...

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- imported new location (package) of classes/interfaces
- moved EJBs to proper locations

Signed-off-by: Roland Häder <roland@mxchange.org>

added new dependencies juser-login-core/lib

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- renamed updatedUser -> managedUser, which is more accurate
- always set values in managed instances to have the JPA noticed it

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- returned managed instance so the web controller (backing bean in your web
  application) can continue to use it (mostly fire an event)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

removed genfiles.properties

Signed-off-by: Roland Häder <roland@mxchange.org>

fixed JAR reference's paths (opps)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- this message-driven bean has been moved to new project
- also the mailer's initialization and config properties

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- rewrote email delivery as EmailDeliveryWrapper() has now a constructor with all required fields
- also saved one parameter (one lesser = easier code)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- 'login' is to generic, there are maybe other logins around than just for users only

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- these entity hints were maybe wrong because a List<POJI> is being returned and
  not POJI alone.

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- checked for this.session as it is required, too

Signed-off-by: Roland Häder <roland@mxchange.org>

Don't cherry-pick:
- need to provide email queues for these EJBs as they will attempt to call
  sendEmail() which would then throw a NPE:

----------------------------
Caused by: java.lang.NullPointerException
        at org.mxchange.jfinancials.database.BaseFinancialsDatabaseBean.sendEmail(BaseFinancialsDatabaseBean.java:555)
        at org.mxchange.jusercore.model.user.register.FinancialsUserRegistrationSessionBean.registerUser(FinancialsUserRegistrationSessionBean.java:208)
----------------------------

However, I will expand sendEmail() a bit to verify that the field session is
really there and not run in such ugly NPE.

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

added missing abstract EJB 'base' beans

Signed-off-by: Roland Häder <roland@mxchange.org>

Rewrite continued:
- Now all project-specific abstract web beans (controllers) inherit from BaseFacesBean to have these nice showFacesMessage() methods.
- Also all project-specific abstract EJBs inherit now only BaseDataBean (one was missing in an old project)
- So, if you have a WAR project, inherit from BaseFacesBean, if you have an EJB project, inherit from BaseDatabaseBean

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- had moved copyAll() to new utility classes which is a much better place for
  them. Per EJB standards, no "complex" methods in POJOs/entity classes which
  makes sense. :-)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

it is an user-specific EJB name

Signed-off-by: Roland Häder <roland@mxchange.org>

fixed EJB name for email delivery beans

Signed-off-by: Roland Häder <roland@mxchange.org>

added missing entity

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- EJB name is now "userRegistration"

Signed-off-by: Roland Häder <roland@mxchange.org>

updated JNDI names

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- moved EJBs to proper package as they are user-related beans
- handled over randomPassword parameter to sendEmail()
- or null if not possible/wanted

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- really have to call super(), else anything there, like logger bean, will not
  be initialized

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- gender -> personalData changed

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- no gender, there is "personal title" for Mr./Mrs.

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

updated jar(s)

Signed-off-by: Roland Häder <roland@mxchange.org>

added missing dependencies on jaddressbook[-share]

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- added base URL parameter + email delivery

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- implemented business method for deleting user accounts

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- renamed variables as they hold a JPA-managed entity

Please cherry-pick:
- made user instance managed which causes not persisting it all over again
- renamed variable

Please cherry-pick:
- closed internal TODO: update new confirmation key in database + user instance

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- first the user instance must become managed, then persist log entry ...
- better check for Long, and not != null test (very lazy)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- added EJB for user activity log
- opps, missed this file updating ...

Signed-off-by: Roland Häder <roland@mxchange.org>

added juser-activity to persistence unit and both projects (core/lib)

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- added assert
- renamed variables to managed user/contact as this reflects the correct JPA state

Please cherry-pick:
- sadly all getReference() + merge() was based on wrong assumption, now find() returns a managed entity where all setter calls leads to an update
- used getManaged() of repeating code (DRY)

Please cherry-pick:
- unsetting all phone numbers make them disconnected from the contact instance, better is to make them managed (merge)

Please cherry-pick:
- if you don't want to have redundant entries (=objects aka. entities) in database of referenced entities, first you need to merge it as it is detached
- then you have a managed instance which you can set in the referencing entity back
- if you don't do this, the entity manager will "think" it is a new instance and persists + relinks it
- maybe some implementations don't do this, but the JPA standard (generic) seems to want to have this way
- do never implement for only one JPA implementation! Do always follow the generic JPA way

Please cherry-pick:
- explicitly flush after persisting to get id number in entity set

Please cherry-pick:
- copy all data from detached to managed instance before updating it
- this needs to be done before the updated timestamp is being set to make sure it is not overwritten by old value (as copyAll() may do it)

Please cherry-pick:
- implemented business methods for deleting/updating fax/land-line numbers
- better this way: managedBla = em.find(Bla.class, bla.getBlaId()); and then managedBla.setBlaSomeFoo(someFooValue);

Signed-off-by: Roland Häder <roland@mxchange.org>

Please cherry-pick:
- unset mobile number, not land-line

Please cherry-pick:
- detachAllContactPhoneEntries() was a bad idea, beter do it the old way.
- The returned instance was a managed instance that have been updated. First find it with find() then you have a managed instanced. Now simply update the fields you want and you are done.