Ok. In general this is an implicit dependency that should require an @EJB to resolve. You
won't be able to run the profile service (or any other vendor deployment tool) and
analyze the deployment for unsatisfied component usage/dependencies. The only reason to
not require an @EJB or ejb-ref in this case is because wars generally should be started
after everything else.
Of course the first support case will be about an ejb depending on a webservice.
View the original post :
Reply to the post :