JNDI Tricks
At work we have to keep the clients in mind.
We do middleware. So at any given time we will have two versions of our software running.
When we release a new version, we deprecate and remove from service the oldest.
So here is what we have resorted to:
We deploy the JNDI name with a version prepended to the front.
The clients (looking for the newest version with our changes) then look up that new JNDI, etc...
Anyone else run into this issue and do they have any great suggestions rather than resorting to these funny JNDI tricks?
-7
We do middleware. So at any given time we will have two versions of our software running.
When we release a new version, we deprecate and remove from service the oldest.
So here is what we have resorted to:
We deploy the JNDI name with a version prepended to the front.
The clients (looking for the newest version with our changes) then look up that new JNDI, etc...
Anyone else run into this issue and do they have any great suggestions rather than resorting to these funny JNDI tricks?
-7
