无法找到该页
无法找到该页
您正在搜索的页面可能已经删除、更名或暂时不可用。
请尝试以下操作：
确保浏览器的地址栏中显示的网站地址的拼写和格式正确无误。
如果通过单击链接而到达了该网页，请与网站管理员联系，通知他们该链接的格式不正确。
单击按钮尝试另一个链接。
HTTP 错误 404 - 文件或目录未找到。Internet 信息服务 (IIS)
技术信息（为技术支持人员提供）
转到 并搜索包括&HTTP&和&404&的标题。
打开&IIS 帮助&（可在 IIS 管理器 (inetmgr) 中访问），然后搜索标题为&网站设置&、&常规管理任务&和&关于自定义错误消息&的主题。The current browser does not support JavaScript, please set your browser to allow JavaScript
Owner : otjfxbsx
Current Directory:/yGEtvfEEk
Update time
Notic: Pubulish your file lists on your blogs, forum signatures or other places you want to spread your shared files to more people.
The new uploads may be displayed after xxxx minutes.60---Navigation---Main PageCommunity portalCurrent eventsRecent changesRandom pageHelp
---Toolbox---Page informationPermanent linkPrintable versionSpecial pagesRelated changesWhat links here
The programming language OT/J implements the programming model
for the host language Java.
Building complex systems from isolated objects often yields poor structure which readily decays during system evolution. Objects should team-up in order to co-operate and jointly deliver complex behaviors. Objects play specific roles within a given Team.
Role instances are attached as specializers to existing objects. Object behavior is controlled by the currently active context that determines which roles are active at a given point in time. Contexts are reified into team instances, which may further be used to mediate between roles and maintain state of the collaboration.
On the road to re-use of modules larger than classes two approaches compete: frameworks and components. For many applications white box frameworks are too fragile and black box components too rigid. Object Teams provide a middle road which balances encapsulation and adaptability.
This is the definitive point of reference for OT/J
Current version online:
Frozen release 1.3 as printable document:
-- work in progress
Either of the following
can be read as an introduction to OT/J:
-- (Net.ObjectDays, 2002)
-- (AOSD 2003)
-- (Journal Applied Ontology 2007)
category shows a few examples ranging from introductory to slightly advanced.
show OT/J in action regarding recurring problems and their solutions.
which has all the resources like downloads etc.
Compatibility
OT/J is compiled by a modified version of the Eclipse compiler for Java. This means that the OT/J compiler can also compile any Java program. While OT/J introduces some new keywords most of these words are still treated as normal identifiers until the keyword team has been parsed ( -- "scoped keywords"). This provides the greatest possible compatibility at the syntax level.
Compiler invocation
The compiler can be invoked either from the ObjectTeamsDevelopmentTooling (OTDT) or as a . For compiling OT/J source outside Eclipse please see either of:
-- Maven sites:
Compiler output
The compiler produces regular Java .class files, which are enriched with OT/J specific meta data using Java bytecode attributes. These meta data are interpreted by the OTRE (see below) in order to weave playedBy and callin bindings into base classes. This implies that OT/J programs need to be launched with the OTRE enabled. Other than that any recent JVM (&#) can be used.
As mentioned, running an OT/J application requires the OTRE. Currently two alternative modes are supported how the OTRE can be linked into an OT/J application:
This technology is part of the Java standard since version 1.5. Launching an application in JPLIS mode only requires a few items added to the classpath and an -javaagent:... argument, which means a non-invasive way of launching OT/J programs like plain Java programs.
By integration of OT/J with the
component framework, also Eclipse plug-ins (RCP, OSGi bundles) can leverage OT/J. In this case running OT/J code only requires to have the OT/Equinox feature installed on top of Equinox.
Within the OTDT the OTRE is enabled by a new checkbox adjacent to the JRE configuration (see the ).
In contrast to an earlier architecture in JPLIS mode the OTRE can weave into more classes, i.e., even system classes from Java's rt.jar can potentially be bound as base classes (note, that any classes loaded before the OTRE starts operation can still not be woven).
For running OT/J applications outside Eclipse please see .
While load-time weaving has the advantage of easier deployment - no tweaking of the classpath is required to ensure that the right version of a class is loaded - it may be difficult to integrate in some application containers. As a fallback mechanism, the OT weaver can be used to process all affected classes already at build-time. The resulting woven classes can then be executed on any JVM (&#) without using the load-time weaver.如何卡CF绝版武器装备???