We tried it this way:
But still get:
EJBCLIENT000025: No EJB receiver available for handling
This does work, we just used the wrong HOST (somehow we had the whole remote://host:4447 and not just host).
Emil Nilimaa wrote:
However! Our system is running for different hosts, each host needs to modify this file. Having it inside a jar make this installation harder for them, and even so, they cannot sign the jar file after modifying it with our certificate (which all other files used in jws are signed with).
Is there any other way to get around this?
So how exactly were you invoking on EJBs, in the older version? Since you mention that the caller can invoke on any number of hosts which aren't known beforehand, you perhaps had some mechanism for such a dynamic behaviour. What was it?
Hmm, i probably expressed our setup wrong. Anyways, i got it working now using the setup from:
It didnt work at first only because we screwed up and set the wrong HOST to the properties.
Working fine now it seems!