Adorsys Commerce Framework. This is a framwork for a modular building of applications that include:
- A rest backend
- Angularjs micro client
- Terminal management
This stands for a shared library module. This is a jar that can be linked and used by other war modules.
A module.lid can contain: - JPA Mapped super classes - JPA Entities. In order for a JPA to be loaded in a referencing application, it must be explicitly listed in the persistence.xml of the referenced module. - Corresponding Repository Classes: These a delta spike repositories used to manage JPA-Entities. - Corresponding EJB Classes: These are ejbs using repository classes to access to entities.
We use these modules to allow for data sharing among war module: - Sharing login and session state among war modules. - Persistent event mechanism among independent modules. Sort of event queue. A module can expose an event through the definition of an EventJPA-Klass and an EventListener-Klass. - Each Module interested in the Event can register a persistent listener. - Before sending an event, the producing module loads the list of listeners and create one instance of the event for each registered listener. - Worker threads in the consuming module regularly check the event table, load event destinated to them, process theses events and delete them.
general core module with utility classes.
general adbase shared library. Contains all database classes for the adbase server module.
This is an angularjs browser based client module. No server side logic.
Is used to stored files shared among all client modules. Because they all run on the save domain, client browser will never need to reload files when they switch among clients.
This is the login client module. It provides the following functionality: - Login - Display a list of workspaces - Change password - See connection history - Logout
This is the client module used to manage organisations, orgUnits, logins and terminals.
REST modules. Contains all rest interfaces used to service client modules.
Special module used to register terminals. Uses basic authentication help register terminals.
Server module for the management of organisations, orgUnits, logins and terminals.
In order to initialize the module, follow these steps:
$JBOSS_HOME is the base directory of the jboss-eap-6.3.0 --> adcom> cp adcom.configuration/jboss-eap-6.3/standalone/security/adcom.jks $JBOSS_HOME/standalone/security/adcom.jks --> adcom> cp adcom.configuration/jboss-eap-6.3/standalone/configuration/standalone.xml $JBOSS_HOME/standalone/configuration/standalone.xml
Then start jboss-eap
--> adcom> mvn clean install --> adcom> cp adlogin.client/target/adlogin.client.war $JBOSS_HOME/standalone/deployments/ --> adcom> cp adbase.server/target/adbase.server.war $JBOSS_HOME/standalone/deployments/ --> adcom> cp adres.client/target/adres.client.war $JBOSS_HOME/standalone/deployments/ --> adcom> cp adterm.server/target/adterm.server.war $JBOSS_HOME/standalone/deployments/ --> adcom> cp adbase.client/target/adbase.client.war $JBOSS_HOME/standalone/deployments/
This is the data file. --> adcom> cp adcom.configuration/jboss-eap-6.3/adbase/data/adbase.xls $JBOSS_HOME/adbase/data/adbase.xls
You can deploy h2console.war to have access to the database. --> adcom> cp $Downloads/h2console.war $JBOSS_HOME/standalone/deployments/
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent