>> <doomsday...@gmail.com> wrote in message
>>
[quoted text clipped - 20 lines]
> backend is already coded in J++. Are there any other options to
> correcting this issue?
Every option I can think of is going to be painful. I named two of them
above. Another might be to start moving towards SOAs and do all new
development in a supported language (whether Java, or C# or Ruby or
something else). Yet another would be to look for an AOP implementation
built upon J++ (they exist for Java, but I don't know if they exist for J++)
and then add hook points to intercept any calls to your Timezone object, and
do whatever fiddling needs to be done.
I imagine the least painful would be to do the hacks mentioned above.
- Oliver
On 20 Feb., 18:28, "doomsday...@gmail.com" <doomsday...@gmail.com>
wrote:
> I dont have the option to switch to Sun's java because our whole
> backend is already coded in J++. Are there any other options to
> correcting this issue?
Moving away from J++ is your only reasonable option. Your problems
with J++ will get worse and worse over time. The earlier you start to
accept reality the cheaper will be the migration. Microsoft threw a
temper tantrum in January 2001 and put J++ on life support at that
time. The support from that time on until the final termination of the
product in January 2004 was just lip service. The MSJVM got a support
extension until January 2008, but that is only the VM, and don't
expect MS doing anything else than lip service.
You are effectively running your backend on a software platform which
is rotting away for six years. Formally you are already three years
behind with necessary, unavoidable actions. You don't have to trust us
here, see what Microsoft has to say about this.
http://www.microsoft.com/windowsxp/evaluation/news/jre.mspx
> we cannot recommend that customers continue to use the Microsoft VM in
> production environments after January 2, 2004,
> Microsoft recommends that developers cease development work that
> depends on the MSJVM and consider migration options for existing code that
> depends on the MSJVM
and so on. Get your act together and migrate.