blocks|key|1402954|text|Sun允许您购买support+packages+for+depreciated+software，例如JRE1.4。对于银行和其他一些组织来说，每年为支持过时的产品支付100,000美元比升级更便宜。我建议只为JRE+1.3提供付费支持。如果任何人需要这方面的支持，他们可以支付高额的支持包。然后，您可以搁置当前的1.3代码库，如果有支持合同的客户需要修复错误，那么您可以为他们修复1.3版本，这可能意味着有选择地应用更新版本中的补丁。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1402955|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sun.com/software/javaseforbusiness/perspectives.jsp^0|8|15|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Sun allows you to buy <a href="http://www.sun.com/software/javaseforbusiness/perspectives.jsp" rel="nofollow noreferrer">support packages for depreciated software</a> such as JRE 1.4. For banks and some other organizations, paying $100,000 per year for support of an outdated product is cheaper than upgrading. I would suggest only offering paid support for JRE 1.3. If anyone needs support for this, they can pay for a hefty support package. You would then shelve your current 1.3 code base, and if a customer with a support contract requires a bug fix, then you could fix the 1.3 version for them, which would likely just mean selectively applying a patch from a more recent version.

blocks|key|1404915|text|即使是JDK+1.4也在2008年10月达到了支持生命周期的尽头。我想你是安全的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1404916|但不要从我这里夺走它。你真正需要问的人是你的客户。也许在你的下载页面上放一份调查并征求反馈会有所帮助。如果三个月内没有人问，那就放弃吧。|1404917|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Even JDK 1.4 reached the end of its support life in Oct 2008. I think you're safe. 

But don't take it from me. The people that you really need to ask are your customers. Maybe putting a survey up on your download page and soliciting feedback will help. If no one asks in three months, drop it.

blocks|key|1402912|text|为什么不让您的程序报告它正在运行的Java版本。这会让你对你的用户群有一个概念。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1402913|我强烈建议放弃对Java+1.3的支持，而不是进行Java+1.4的小升级，为什么不使用Java+1.6呢？自1.3版本以来，已经有了巨大的改进。你真的错过了。|1402914|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Why not have your program report back what version of Java it is being run with. This will give you an idea of your user base. 

I highly recommend dropping support for Java 1.3, and instead of doing a minor upgrade to Java 1.4, why not use Java 1.6? There have been massive improvements since 1.3. You really are missing out.

blocks|key|103779|text|生命周期的结束是软件生命周期的正常部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|103780|您应该问/回答的真正问题是，您是否有迫切的业务需求来向“旧”版本添加功能。如果没有，你可以继续为需要它的客户提供它--但鼓励其他人使用最新的&最好的，这需要1.4+(或1.5/1.6)。|103781|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

End-of-life is normal part of software's life cycle.

The real question you should ask/answer is whether you have a compelling business need to add features to the "old" versions. If not, you can continue to offer it for customers who need it -- but encourage everyone else to take the latest &amp; greatest which requires 1.4 (or 1.5/1.6).

blocks|key|4297347|text|很难给出公司内部使用的数据。确实存在浏览器插件安装的数据，但Sun的数据是保密的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4297348|1.3支持在一段时间前停止了(Solaris+8+vintage支持拖了一段时间)。1.4已经完成了其服务生命周期的结束，但可能会在Java+for+Business下得到支持。如果您尝试从sun.com上的存档下载1.4，则系统会要求您提供一些信息，例如电子邮件地址。1.5的使用寿命已经过半(但它在Mac上仍然很常见)。|4297349|选择使用1.4的特性并不是那么困难。你只需要通过反射加载一个类(或者只是以不同的方式打包它)，然后在新功能上有一个轻量级抽象的1.4和1.3实现。|4297350|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

It's difficult to give figures for what companies use internally. There do exist figures for browser plugin installation, but Sun's figures are confidential.

1.3 support stopped some time ago (Solaris 8 vintage support dragged on for a bit). 1.4 has completed its End of Service Life, but is likely to be supported under Java for Business for yonks. IIRC, if you try to download 1.4 from the archives at sun.com then you are asked for some information such as an e-mail address. 1.5 is more than half way through its service life (but its still quite common on Macs).

It's not that difficult to use 1.4 features optionally. You just need to load one class via reflection (or just package it differently) and then have a 1.4 and 1.3 implementation of a light abstraction over the new features.

blocks|key|1404997|text|如果有人真的请求1.3和1.4的关键补丁，并且所有新版本都在Sun支持的当前最旧版本1.5上发布，为什么不只是1.3和1.4的关键补丁？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1404998|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Why not only do critical patches for 1.3 &amp; 1.4 if anyone actually requests them and do all new releases on 1.5 - the current oldest version supported by Sun?

blocks|key|1080435|text|我用jdk+1.4开发了很长一段时间，当时jdk+6.0还没出来。我们不能升级(客户端，服务器等等)。在某种程度上，我们只是升级了，并没有太多谈论它。客户端升级时不会令人讨厌，“这个升级将修复许多安全漏洞，修复许多错误，提高性能:-)”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1080436|现在，我试着让我的代码与jdk+1.5兼容，对于运行1.4及更低版本的人，我一点也不关心。在某种程度上，他们会明白“尝试”升级对他们来说是最有利的。|1080437|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I was developing with jdk 1.4 for a long time while jdk 6.0 was out. We couldn't upgrade(clients this, servers blablabah). At some point, we just upgraded without talking too much about it. Clients upgraded without being annoying, "this upgrade will fix lots of security holes, many bug fixes, improved performance :-)".

Right now, I try to keep my code compatible with jdk 1.5, I have no concern at all for people running 1.4 and below. At some point, they'll understand that it is in their best interest to "try" upgrading.

We provide a popular open source Java FTP library called <a href="http://www.enterprisedt.com/products/edtftpj/overview.html" rel="nofollow noreferrer">edtFTPj</a>.

We would like to drop support for JRE 1.3 - this would clean up the code base and also allow us to more easily use JRE 1.4 features (without resorting to reflection etc). The JRE 1.3 is over 7 years old now!

Is anyone still using JRE 1.3 out there? Is anyone aware of any surveys that give an idea of what percentage of users are still using 1.3?

Dropping support for JRE 1.3

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们提供了一个流行的开源Java FTP库，名为。我们想放弃对JRE 1.3的支持-这将清理代码库，并允许我们更容易地使用JRE 1.4特性(无需求助于反射等)。JRE 1.3已经有7年多的历史了！还有人在使用JRE 1.3吗？有没有人知道有什么调查表明用户中有多少人仍在使用1.3？

问删除对JRE 1.3的支持
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问删除对JRE 1.3的支持EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问删除对JRE 1.3的支持
EN