Example of communication between two EAR's that resides on the same JVM / Application Server.
Java
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.settings
ear-intercommunication.api
ear-intercommunication.client
ear-intercommunication.service
.gitignore
.project
README.md
pom.xml

README.md

Communication Between EARs In One JVM / Application Server

Example of communication between two EAR's that resides on the same JVM / Application Server.

Usage of local business interfaces of the EJB's in such communication can be very misleading. It's prohibited by the EJB specification but many application server vendors are supporting it anyway.

If you won't use them wisely you can fall into class loaders problems or non-portable behavior.

After deployment of the two EAR's (service and client) invoke the client -> service communication by accessing to the following URL:

http://HOST:PORT/client/rest/invoke