How to make two ejbs that can call each other

Question

0.00/5 (No votes)

See more:

, +

Using WildFly 29, I followed the quickstart guide for the EJB-Multi-Server at the wildfly quickstart github

Let' s supposes I have two EJB projects A and B
I am already able to call B from A via a JNDI lookup
But when I setup B to be able to call A, I got a maven cyclic dependency error
Because as in the quickstart, we need the dependency of the ejb-client in the pom.xml

What I have tried:

I have already made some research about how to avoid the cyclic dependency but I did not find anything related to EJB and my context
I have also searched for cyclic ejbs, but in my case they are separated projects

Posted 9-Oct-23 23:49pm

Maloda 2022

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2023-10-10T00:27:00

If you have two projects called A and B, and A references B while B also references A which do you build first?

If you build A, then B you end up with A being out of date because B has changed. But when you build A, B becomes out of date so that needs rebuilding as well!
If you build B, then A you end up with B being out of date because A has changed. But when you build B, A becomes out of date so that needs rebuilding as well!

That's a cyclic dependency: you cannot build a project because the act of building it affects the projects it is dependent on.
You can't make them call each other: you have to move the dependent code into separate project(s) that do not relay on A or B, and refer to those in both A and B.