The evolution of j2EE (1)

分层不是数层数,而是责任切割的艺术 分层是软件架构中实现关注点分离(SoC)的基础范式,其本质在于通过契约明确、变更局部、复用可行和可观测一致四大前提,降低系统认知复杂度。在微服务与云原生演进背景下,传统三层架构(Controller-Service-DAO)日益暴露出责任漂移、技术绑架与演进阻塞等问题,已难以适配事件驱动、多端协同和领域聚合等现代业务需求。真正有效的分层应以能力维度组织,如领域层封装业务规则、应用层编排用例、接口适配层统一接入协议,从而支撑高可维护性、可测试性与技术栈演进。本文结合实战健康度检查、ArchUnit约束与DDD 阅读详情

http://www.ibm.com/developerworks/websphere/techjournal/0805_knutson/0805_knutson.html

Date:   14 May 2008

 

Java EE technologies, present and future

The remainder of this article looks at specific technologies included in the Java EE platform and their expectation for change:

Presentation layer

  • Servlets

    Servlets should be a fairly stable technology at this point, mature and fairly well understood. Other than addressing Web 2.0, there are no significant changes expected. Of course, that's not to say that there won't be any changes:

    • Java EE 5 addressed some of the usability problems in the platform by permitting metadata to be embedded in component source code. The servlet specification did not take full advantage of this and so it is expected to do so. However, this should only add additional forms of metadata rather than changing any behavior.

    • Another major change in Java EE 5 is the integration of the expression language between JavaServer™ Faces and JavaServer Pages, but this integration was designed to be backward compatible and should present no major issues.

    • One possible future change is metadata scopes. Servlets tend to declare metadata at a module level and share it among all Web components. EJBs tend to declare metadata at the component level. This is expected to evolve to enable both component and module scoped forms of metadata. Again, this is not expected to cause any incompatibility as the existing scope behavior should be maintained.

    • Another possible area of change is adding programmatic APIs to dynamically define behavior rather than defining it declaratively. SOA seems to be pushing this style and it is likely that all technologies will adopt both a declarative and programmatic behavior model at some point, if they haven't already. For the most part, this should not cause any incompatibility. The only possible exception would be adding methods to interfaces that must be implemented by applications. Given the current trend in the industry of getting away from explicit interfaces (and using annotated methods instead), this is not expected to be an issue.

  • JavaServer Pages (JSP) and Java Standard Tag Library (JSTL)

    JSPs and JSTL are also fairly stable technologies at this point, with no significant changes expected.

  • JavaServer Faces (JSF)

    JSF is still a relatively new technology. JSF is undergoing a major revision for the next round of specifications with an expected integration between JSF managed beans and Enterprise JavaBeans™. The risk of changes affecting existing applications will be higher here than with other presentation technologies. IBM does have representation on the JSF expert group and will keep a watchful eye out for problems.

    One area of future concern is be how well Ajax support in JSF will follow the specifications for the OpenAjax Alliance. Through its participation, IBM will try to ensure that compatibility is maintained as the standards move forward. Ajax support in JSF will be new (when it appears) and use of that feature will be at a somewhat higher risk than other parts of JSF. More details will be known in early 2009.

  • Portlets

    Although not part of the Java EE platform, IBM WebSphere Application Server V6.1 and later provides the ability to utilize portlets. The portlet specification is currently undergoing a revision, but IBM is the specification lead and has a level of control over its evolution.

    Version 2.0 of the portlet specification is a major revision that adds features omitted in Version 1.0, like coordination of resource serving, and leads the Java Portlet specification toward a path of maturity. Changes likely for later versions will mainly be to align with changes in other Java EE specifications, such as Servlet 3.0 or JSF 2.0, but they are not likely to include major new functionality on the portlet side.

    At the time of this writing, Version 2.0 of the Java Portlet specification appeared to be source and binary compatible to Version 1.0, and switches were to be added for controlling underspecified Version 1.0 behavior that is now specified in Version 2.0. This compatibility assertion will be validated once the specification is finalized and sufficient testing has been performed.

Business logic

  • Enterprise JavaBeans (EJB)

    The EJB specifications have added new capabilities over time, but have done so in an upward-compatible way. The EJB 3.0 specification changed the EJB programming model syntax in a fairly dramatic way. However, the older 2.1 and prior programming models are still available, and even the 3.0 programming model contains backward compatibility support, enabling clients and server components to be implemented with different versions of the specifications.

    • Session beans are fairly stable at this point and no substantial behavior changes are expected, although new functions are likely to be added.

    • Message-driven beans are also fairly stable.

    • CMP/BMP persistence is stable, but is likely to be deprecated in favor of Java Persistence APIs (JPA) as a relational persistence technology, or the Java EE Connector Architecture (JCA) for non-relational persistence.

    • One possible change that might affect this in the next round of specifications is the potential to bring session and message-driven beans together, into a single component style with both synchronous and asynchronous interaction styles. Given the last revision of the specification, it is reasonable to expect sane and compatible evolution here as well.

Persistence

  • JDBC

    JDBC is quite stable at this point, offering a good long term investment in performance and compatibility, assuming you do not change your database vendor; a database vendor change might require changes in the SQL statements or in the locking and isolation levels you use.

  • Java Persistence APIs (JPA)

    JPA is the technology slated to replace EJB CMP Object/Relational Mapping support in the Java platform. This is a new technology and so further evolution is expected. However, it is also based on multiple vendor implementation experiences (Hibernate, TopLink, and Kodo) and therefore the risk of change causing incompatibilities is somewhat reduced. JPA provides some isolation from JDBC vendor differences.

Integration

  • Java Message Service (JMS)

    JMS has changed little in a long time and is considered a stable technology.

  • Java EE Connector Architecture

    The Java EE Connector Architecture has been stable for some time, but has some issues that will be addressed in the next round of specifications. The current architecture does not address failover or inbound and outbound consistency; vendors have had to rely on extensions to handle these issues. Changes in the specification to address these and other problems are planned to be compatible, but could eventually affect custom-written resource adapters. Adapters purchased and maintained from other vendors should hide any affects (if any) of those changes.

  • JavaMail and JavaBeans Activation Framework (JAF)

    JavaMail's evolution has been somewhat quiet, possibly because there is a smaller percentage of developers using it than, say, servlets or EJBs. This architecture tends to have more implementation classes that could be affected by evolution, making it more difficult to evolve and maintain source compatibility. However, in general, it appears to be mostly stable at this point and no changes are currently foreseen. JAF is used for MIME type handling and is generally considered as stable as JavaMail.

  • Java API for XML-based RPC (JAX-RPC)

    JAX-RPC is likely to be deprecated in Java EE 6, and therefore any new development needs to consider the option of using:

    • JAX RPC: a technology that is stable, but does not work for all cases and will be going away, or
    • JAX-WS: a new technology that is likely to change, but is a reflection of where the industry is moving.
  • Java API for XML Web Services (JAX-WS)

    JAX-WS is the second generation of a Web services API, taking strategic precedence over JAX-RPC. It was defined as a new technology in order to avoid backward compatibility issues that would have hampered the evolution of the specification. There have already been some issues around the evolution of JAX-WS, due to decisions of the W3C standards committees, that have led to revisions removing the support of some requirements of the specification. The Web services area is likely to evolve even more. Currently, there is a desire to standardize the qualities of service related to a Web service (such as reliable messaging or transactions), in addition to a focus on RESTful Web services (via JAX-RS – JSR 311). All of this is still relatively new and shakeouts are likely to occur as the industry gains more experience in these areas.

    From a maturity perspective, JAX-WS has benefited greatly from the JAX-RPC experience. The lessons learned from JAX-RPC and fed into JAX-WS have produced a reasonably effective and mature specification. The inclusion of both JAX-WS and JAXB in Java SE 6 (the JDK/JRE) will likely stabilize these technologies even further.

  • Java Architecture for XML Binding (JAXB)

    JAXB is also new, but similarly evolved from the previous JAXB 1.0 delivery. Combining that experience with leveraging input from JAX-RPC and JAXB's inclusion into JAX-WS, JAXB is better positioned in its second release (like JAX-WS is over JAX-RPC) to be a stable and compatible technology. While it maintains the same name as its predecessor, its implementation and much of what it is trying to accomplish has been rewritten based on lessons learned from its past deficiencies. It could evolve further as the platform tries to address more consistent mappings between Java objects and other representations, such as protocol marshalling or persistence. Expectations are that backward compatibility will be maintained for those mappings.

  • SOAP with Attachments API for Java (SAAJ)

    SAAJ is a fairly stable rendering form for Web service messages. Apart from its extension of leveraging standardized DOM APIs, it has undergone little change since its initial release.

  • Java API for XML Registries (JAXR)

    JAXR is another technology that was introduced and adopted by the Java EE platform too rapidly. JAXR was based on providing an abstraction over UDDI V2 and ebXML V2, but V3 versions of those standards were produced almost simultaneously, rendering JAXR somewhat obsolete out of the gate. The industry is still evolving in this space somewhat, so any further evolution of JAXR is also likely to be out of date when complete. Once the industry settles down a bit, JAXR will likely either evolve dramatically or be replaced by another technology.

Other technologies

  • Java EE Management

    Java EE Management has been fairly stable and its stability is expected to continue.

  • Java EE Deployment

    This technology should be avoided, as it is insufficient for the task and is likely to go away or be replaced by a substantial revision in the future.

  • Java Authentication and Authorization Service (JAAS)

    JAAS provides the core of security services for the Java EE platform. It is generally stable, but there are known differences in behavior across vendors regarding JAAS subject propagation. This will attempt to be clarified in a future Java EE platform specification so that industry consistency may be achieved.

  • Java Authorization Contract for Containers (JACC)

    The changes in Java EE 5, enabling metadata declarations via annotations, have required changes to JACC to enable the handling of annotated security declarations. JACC 1.0 providers are not likely to be able to provide appropriate security behavior with security annotations in use, although existing applications that do not use annotated security declarations should continue to run fine.

Future technologies

Of course, the future is uncertain, but you can expect some technologies to continue influencing the Java EE platform. The technologies listed below should be approached with caution from a compatibility standpoint, since it is likely that they will evolve dramatically.

  • JAX-RS - RESTful services

    The industry has recognized that it is not always efficient to have a formal Web service for loosely coupled services. However, this is new for the industry and not a lot of experience has been built up yet around this hot topic. As best practice patterns emerge, it can easily be imagined that the specification could change dramatically.

  • WebBeans

    The Java EE 6 content proposal includes the addition of a new technology called WebBeans. Originally proposed as a way to integrate JSF managed beans and EJBs, it has since evolved into a distinct component model meant to encompass many other component models. There is very little experience in this space (although WebBeans was intended to be modeled on JBoss Seam, it has gone well beyond that experience). The closest example might be to look at the years of deliberation that went into producing the first SCA specification, which also serves as a component model that encompasses many other component models. Unless the scope of WebBeans is reduced dramatically in the near future, its specification is likely to evolve dramatically.

  • Timer and Workmanager

    These specifications drive enterprise qualities of service into asynchronous (that is, threaded) programming styles. They are based on joint work done by IBM and BEA (CommonJ) and have somewhat reduced risk based on multiple vendors having delivered these technologies, but these specifications have rebased the API on the Java Concurrency Utilities for threaded work management. It remains to be seen whether the industry will accept this or require additional changes, but the risk of their use is likely to be smaller than WebBeans. Using existing Asyncronous Beans APIs within WebSphere Application Server will provide the best long term stability and compatibility -- at least until these specifications stabilize.

SpringBoot+Vue+MySQL 高校学科竞赛平台 完整可运行版(源码+文档) 本项目基于SpringBoot+Vue+MySQL构建高校学科竞赛管理平台,覆盖学生、教师、领队教师、管理员四大角色,实现竞赛发布、报名、刷题、评分、公示等全流程闭环管理。系统架构清晰,技术主流,配套完整源码、数据库脚本、万字论文、开题报告、答辩PPT及部署文档,支持一键运行,适用于毕业设计、课程设计及院系二次开发,真正实现“开箱即用”。 阅读详情

相关推荐

Amesim与Simulink联合仿真:S-Function接口配置与实战避坑指南

本文详细介绍了Amesim与Simulink联合仿真中S-Function接口的配置方法与实战避坑指南。从环境搭建、编译器配置到S-Function接口实战,逐步解析关键步骤与常见问题解决方案,帮助工程师高效实现多领域系统仿真,特别适合汽车、航空航天等复杂系统建模场景。

weixin_29173777的博客 345

xperience the Evolution of Java EE 2nd Edition

xperience the Evolution of Java EE 2nd Edition.pdf

nmx253的专栏 157

STM32单片机:驱动ADS1115四个通道全开程序

本文介绍了德州仪器(TI)的ADS1115高精度16位模数转换器(ADC)及其应用实现。该芯片具有16位分辨率、可编程增益放大器(PGA)和低功耗特性,支持±0.256V至±6.144V量程。文章提供了完整的C语言驱动代码,包括初始化、配置寄存器读写、单次/连续转换模式设置、电压值读取等功能实现。代码通过I2C接口与ADS1115通信,支持多通道选择和不同PGA设置,可实现高精度模拟信号采集。该方案适用于需要精密测量的嵌入式系统,如传感器数据采集等应用场景。

weixin_42122070的博客 691

GENERIC FRAMEWORK MODEL OF JAVA PLATFORM

Link from http://blog.youkuaiyun.com/hongkong2007/archive/2007/08/23/1755894.aspx 1. PATTERNS AMONG THE THREE FRAMEWORKS This portion discusses the patterns used in the JAVA EE and Spring. JAVA EE 5, the ...

weixin_34040079的博客 414

光学仿真案例(1) 铌酸锂非线性波导仿真模拟 FDTD仿真

在过去几年里,许多集成光子学应用往往需要多个相干可调谐光源,而且从外部激光器引入额外的光输入增加了芯片封装的复杂性,如果使用基于III-V族、氮化硅(SiN)或铌酸锂(LNO)的集成光源又大大增加了制造复杂性和成本。然而,通过非线性谐波相互作用产生的光源不需要额外的制造工艺来产生增益、反馈和外部电路,即可支持许多应用。在下面的案例中,演示了一种基于Luo[1]的铌酸锂波导频率转换集成系统。该案例主要仿真了利用温度调制实现高效相位匹配的铌酸锂纳米光子波导的二次谐波产生。

q895235273的博客 4147

【学习系列】SAP RAP 16:RAP应用部署集成至Fiori Launchpad 【On-Premise】

本文详细介绍了如何将开发完成的RAP应用部署到S4HANA 2023 On-Premise环境并集成到Fiori Launchpad的完整流程。主要内容包括:1)通过ADT工具创建Fiori项目并配置外部IDE(VSCode);2)使用npm命令部署应用到系统;3)通过事务代码创建语义对象、磁贴目录和目标映射;4)配置PFCG角色分配;5)补充了部署失败解决方案、翻译问题处理、自定义主题设置以及登录页面LOGO修改等内容。文章提供了step-by-step的操作指南,帮助开发者将预览模式的应用正式部署到生产

DeveloperMrMeng的博客 637

netbeans 出现Enter password for default keyring to unlock 问题的解决方案

这几天又遇到了一个新问题,在netbeans安装好之后,

sunbirdhan的专栏 1215

iOS应用突然无法从App Store获取到内购(IAP)产品列表的解决

问题现象 Apple开发中,在应用中嵌入内购(IAP)功能的小伙伴们可能会发现,吃着火锅唱着歌,突然App就无法获取到产品列表了,而且产品请求操作并不会返回任何错误。 此时检查发现,并没有对App的内购逻辑做任何改动。 那么,这是什么原因导致的呢? Let’s find out!???? 问题分析 1. 排除其它原因 首先,你先得排除不是你IAP内购逻辑变更或其他原因导致的。 在SKProductsRequestDelegat代理实现的productsRequest方法里下断点: func produc

享受开发,颠倒银河 6144

paper weekly_Java Weekly 11/15:Java Money,REST API演进,CDI 2.0等…

这篇文章最初发表于thoughts-on-java.org ,其中Thorben扬森博客关于Java和Java EE。 Java世界正在快速发展,要跟踪它可能是一个挑战。 幸运的是,每周都会创建大量的有用资源,用于解释新功能或从不同角度查看现有内容。 我正在使用Java Weekly系列来收集上周发现的最有趣的链接,并将它们呈现给大家。 我希望您觉得它有用,并且可以让您更轻松地保持最新...

187

AMS TMF8820/21/28 SPAD 掩码和模式选择

为了实现最快的测距周期,将报告周期设置在测距周期以下的毫秒,以确保不会有等待时间。除了8X8固定了pixel的位置意外,其他模式客户可以设计自己的spad掩码,并将spad单独分配给通道。对于这些spad掩码,有一些约束。左下角提示红色代表光学中心,绿色方框表示单个spad,每个MP里可能有2X3个spad,也有2X5个spad,也有3X6+3个spad,这部分适配光学,最大的程度的利用spad区域。以下是几种预定义的spad掩码,非常灵活的配置,来适配各种3X3,4X4,8X8的模式选择。

dream it possible 701

第二十一:Python接口自动化-处理Json数据

【代码】第二十一:Python接口自动化-处理Json数据。

欢迎来到本博客! 111

Tomcat的简介、版本选择与安装、配置与运行(启动、关闭、重启、配置成开机自启动服务)

Apache Tomcat是一个对于 【Jakarta Servlet、Jakarta 服务器页面、Jakarta 表达式语言?、Jakarta WebSocket、Jakarta 注解和Jakarta 身份验证规范】的开源实现。Jakarta EE平台(Jakarta EE platform)是Java EE平台(Java EE platform)的演变。Tomcat 10及更高版本实现了作为Jakarta EE一部分开发的规范。Tomcat 9及更早版本实现了为Java EE一部分发展的规范。

u010804417的博客 1万+

PCL RANSAC拟合分割多条直线【2026最新版】

使用RANSAC算法拟合分割多条直线,输出每一条直线的拟合参数到控制台,并保存直线点云到本地文件夹。博客长期更新,本文最新更新时间为:2026年5月24日。

点云侠的博客 7975

《创造传染病》游戏策略与流行病学原理深度解析

流行病学是研究疾病在人群中分布规律及影响因素的重要学科,其核心原理包括传播动力学和防控策略。通过基本再生数(R0)等关键指标,可以量化传染病的传播能力,当R0>1时疫情将持续扩散。在技术实现层面,Python编程结合SIR模型能够有效模拟疫情传播过程,为公共卫生决策提供数据支持。这种技术方法在游戏《创造传染病》中得到了生动体现,玩家需要平衡病毒传染性、严重性和抗药性等属性,通过数据分析制定传播策略。该游戏精准模拟了现实中的疫情传播规律,从印度尼西亚等起始国家的选择到多阶段进化策略的实施,都体现了流行病学原理

weixin_34245082的博客 436

精雕软件(JDpaint) 5.5 绿色版

精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版

汉书HE8,好用的汇编代码编写工具

汉书HE8,好用的汇编代码编写工具早期编写汇编代码所用功能强大

InnoDB 内存结构总览:Change Buffer、AHI 与 Log Buffer

本文系统梳理InnoDB内存结构中的ChangeBuffer、Adaptive Hash Index(AHI)与LogBuffer。ChangeBuffer缓存二级索引页不在内存时的变更,减少随机IO,仅在页加载时合并;聚簇索引修改立即执行,因数据本身不可延后。AHI基于高频等值查询自动构建哈希索引,加速定位,仅支持等值操作。LogBuffer为redo log内存缓冲,配合磁盘日志实现崩溃恢复。三者均服务于性能优化,其中ChangeBuffer与AHI共享BufferPool空间,而LogBuffer独立

bksczm的博客 310

假人有限元模型

假人模型,车辆碰撞假人有限元模型,适合做乘员安全的研究者利用

信创环境下PageOffice文档控件适配与实践

信创适配做到文档控件这一层,拼的已经不是"有没有国产版本",而是同一个功能在两类终端上是否真的等价。等价的标准很具体:同一次点击能得到同样的结果,同一份公文能得到同样的版式,同一个项目不需要维护两套代码。这背后是三件并不轻松的工作:服务端用一套接口同时支撑两类终端,客户端把两种系统与四种芯片的安装包分发清楚,文档内核层由产品侧跟着 WPS 的版本走。浏览器这一层的压力,则被收进了产品自己的窗口里——升级节奏由产品掌握,不再交给运气。

zi_wu_xian的专栏 336

jre9下载 jdk9

(Java SE Runtime Environment 9.0) 9.0u175 官方最新版 【x86|x64】

第三篇 第 6 课

前置:第三篇第 1 课(stdx 引入),第二篇第 1 课(std.regex)。环境:仓颉 SDK 1.2.0。本文所有代码与输出均逐行实测。

weixin_41618057的博客 557

【从零理解 Spring AI · 12】MCP 的两种角色:做客户端还是做服务端

上一篇讲了 MCP 的概念:标准协议、三大角色、M+N 替代 M×N。

nice_lcj520的博客 615

pcl2启动器下载(Minecraft PCL2 启动器 最新版 安装与使用说明)

摘要:PCL2(Plain Craft Launcher 2)是一款面向 Minecraft 的第三方启动器,支持正式版与快照版本管理、模组与整合包安装、Java 运行时自动匹配,绿色免安装、双击即可运行。适合在 Windows 上玩单机整合包、需要多版本共存或离线启动的用户使用

2611_96675819的博客 226

spring boot 4集成SQLLite,及其SQLLite的建库

spring boot 4集成SQLLite,及其SQLLite的建库

weixin_41463944的博客 237

Java 集合容器高频面试题全解:HashMap 树化阈值、1.7 死循环与 ConcurrentHashMap 演进(2026 招聘 JD 真题复盘)

HashMap 树化阈值 8 的泊松分布依据、退化阈值 6 的防抖设计、JDK 1.7 头插成环死循环的排查与修复、1.8 尾插后为何仍线程不安全、ConcurrentHashMap 放弃分段锁的原因与 ForwardingNode 协作扩容、computeIfAbsent 死锁陷阱、大集合找重复的场景题选型,附三层追问链自测。题目来源为 38 期公开招聘 JD 样本与字节、拼多多、建行、美团、快手公开面经。

蒙眼过河 427

spdlog 同步日志库使用详解

spdlog是一个轻量级 C++ 日志库,支持同步日志、异步日志、多线程日志、日志文件轮转和自定义日志格式。对于嵌入式 Linux 应用开发,我建议先使用。它可以帮我们完成:日志级别过滤。时间戳和线程 ID 输出。日志格式化。终端和文件输出。多线程安全写入。日志文件按大小或时间轮转。我们不需要自己实现互斥锁、文件写入、日志格式化和轮转等底层功能。

zengjiajun2006的博客 1124

JavaSE通关手册:数据类型与变量

代码无需额外处理,编译时编译器自动完成转换。

xys_678的博客 236
上一篇: The evolution of java
下一篇: Web service message view tool: TCPMon
FireCoder
博客等级 码龄17年 65粉丝 100原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值