gian wrote:
... have to use java [sic] 1.4
Lew wrote:
Just out of curiosity, why are you stuck on an obsolete version? What is
the
client's reasoning?
gian wrote:
websphere AS
In this particular case IBM maintains the JVM, mitigating the risk.
Many organizations who have lingered on Java 1.4 by dint of their application
servers are now upgrading the ASs to ones based on Java 5+. It is likely
your client has considered an upgrade to WAS and has a timeline in their plan
for when they'll move up. My guess is that the Java Enterprise world is a
little past the middle of the bell curve on that transition.
If their expected transition is near, and you might be pleasantly surprised,
sometimes you can plead a target release for a new feature or report or
whatever to wait until the new platform.
I've seen now on three large-scale projects huge opportunity as an employee
to position myself as a transition expert for Java 5 upgrades. Run a few
exercises at your desk - generify a core class and follow through all the
dependent consequences, for example. Whew!
Luckily you don't actually do that for initial transition. Don't even
@SuppressWarnings("unchecked") the legacy code. Let it warn you - it's good
for the project. Later you turn the new hires loose on a private branch and
tell 'em to generify store.general.foo.core.logic.* types and all consequent
dependencies. A team of three for a large project, two for a smaller one.
Once you yourself know the scope of the solution (how much overall team work
to transition - probably very little), you casually hit up the team lead with
the knowledge. Don't demand any action, just make sure they understand you
have an answer and are aware of the planned transition dates. Clue in the
team lead that it will be easy but don't you yourself tell that to anyone in
management.
Stay a little late after work each day and implement the transition for the
whole project on a private version-control branch. Debug the automation
thoroughly.
Privately email only the team lead that you have a completely debugged
transition branch ready to use as a starting point. Follow up with direct
verbal conversation. Follow their lead in how to use the prototype. A smart
team lead will make good advantages with it.
When a customer says, "We have to use product X", they often as in your case
present an opportunity to cash in on the transition to product Y from X. If
the transition is inevitable, as with the upgrade to Java 5 and later, and
your opportunism is good, then you can create a near certainty of advantage
for yourself. If the transition is already scheduled though not yet fully
planned by your customer/employer then your certain advantage is likewise
scheduled.
While a customer may superficially express a dogmatic restriction ("Thou
shalt use the version 1.4 of Java!"), they actually reveal an exploitable
opportunity ("We shall need help in six months to upgrade!").