会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • System and method for enabling dynamic modifed class reloading in an application server environment
    • 在应用程序服务器环境中启用动态修改类重新加载的系统和方法
    • US07882501B1
    • 2011-02-01
    • US09561697
    • 2000-05-01
    • Bjorn CarlsonMilton SoongSantosh Hasani
    • Bjorn CarlsonMilton SoongSantosh Hasani
    • G06F15/16G06F15/177G06F9/44
    • G06F9/44521G06F8/656
    • System and method for enabling dynamic class reloading in an application server environment. A distinction is made between “versionable” and “non-versionable” classes. Versionable classes are classes that should be automatically reloaded when they are modified. The application server(s) may execute a background task that executes periodically to check for modified versionable classes. Users may specify class versionability by specifying a list of explicitly versionable classes, specifying a list of superclasses whose extending classes should be considered to be versionable, and specifying a list of interfaces whose implementing classes should be considered to be versionable. Once the background task discovers a modified versionable class, the background task may cause the class to be reloaded, e.g., by instantiating a new classloader and instructing the new classloader to reload the class. The background task may purge the reloaded class from any caches that the application server maintains.
    • 用于在应用程序服务器环境中启用动态类重新加载的系统和方法。 “版本化”和“不可版本”类之间的区别。 版本化类是修改后应自动重新加载的类。 应用服务器可以执行周期性执行的后台任务来检查修改的可版本化类。 用户可以通过指定明确可版本的类的列表来指定类的可版本性,指定扩展类应该被认为是可版本化的超类的列表,并指定其实现类应被视为可版本化的接口列表。 一旦后台任务发现经过修改的版本类,后台任务可能导致重新加载类,例如通过实例化一个新的类加载器并指示新的类加载器重新加载该类。 后台任务可以从应用程序服务器维护的任何缓存中清除重新加载的类。
    • 2. 发明授权
    • System and method for enabling atomic class loading in an application server environment
    • 在应用程序服务器环境中启用原子类加载的系统和方法
    • US06845503B1
    • 2005-01-18
    • US09562424
    • 2000-05-01
    • Bjorn CarlsonMilton SoongSantosh Hasani
    • Bjorn CarlsonMilton SoongSantosh Hasani
    • G06F9/44G06F9/445H04L29/06H04L29/08
    • G06F8/65G06F9/44505G06F9/44521G06F9/505H04L29/06H04L67/10H04L67/34H04L69/329
    • Disclosed is a system and method for enabling dynamic class reloading in the application server environment. Users may specify class versionability by specifying a list of explicitly versionable classes; and the application server(s) may execute a background task which operates periodically to check modified versionable classes, and cause the classes to be reloaded.Administrators may specify a set of class files to be treated as a “bundle”. When the bundle is deployed, a deployer manager may obtain a lock, e.g. a semaphore, referred to as the “dirtyClassListLock”. Once this lock is obtained, the deployer manager may copy all the class files in the bundle from a deployment environment to their appropriate runtime locations. After the runtime locations have been updated, the deployer manager may release the dirtyClassListLock. According to this method, the background task that checks for and reloads modified classes may also have to obtain the dirtyClassListLock in order to run. Thus, the background task will discover and reload class files in the bundle atomically.
    • 公开了一种用于在应用服务器环境中实现动态类重新加载的系统和方法。 用户可以通过指定明确版本化的类的列表来指定类的可分级性; 并且应用服务器可以执行周期性操作以检查修改的可版本类的后台任务,并且使得重新加载类。管理员可以指定要被视为“捆绑”的一组类文件。 当捆绑包部署时,部署管理器可以获得锁定,例如 一个信号量,被称为“dirtyClassListLock”。 获取此锁后,部署管理器可将捆绑中的所有类文件从部署环境复制到其适当的运行时位置。 运行时位置更新后,部署管理员可能会释放dirtyClassListLock。 根据这种方法,检查和重新加载修改的类的后台任务也可能必须获得dirtyClassListLock才能运行。 因此,后台任务将以原子方式发现并重新加载束中的类文件。
    • 4. 发明授权
    • System and method for caching JavaServer Pages™ responses
    • 用于缓存JavaServer Pages(TM)响应的系统和方法
    • US06697849B1
    • 2004-02-24
    • US09561698
    • 2000-05-01
    • Bjorn Carlson
    • Bjorn Carlson
    • G06F1516
    • H04L67/1008G06F9/54H04L29/06H04L67/10H04L67/1002H04L67/101H04L67/1029H04L67/1034H04L67/2852H04L67/34H04L69/329H04L2029/06054
    • System and method for caching JavaServer Page™ (JSP) component responses. The JSP components may be components that execute on an application server that supports networked applications, such as web applications or other Internet-based applications. One or more client computers, e.g., web servers, may perform requests referencing the JSP components on the application server. The execution of JSP components may be managed by a JSP engine process running on the application server. When a request referencing a JSP is received from a client computer, the JSP engine may first check a JSP response cache to determine whether a valid JSP response satisfying the request is present. If a matching cached response is found, then the response may be retrieved and immediately streamed back to the client. Otherwise, the referenced JSP may be executed. Each JSP file may comprise various SetCacheCriteria( ) method calls. When executed, the SetCacheCriteria( ) call may cause the output of the JSP to be cached once the JSP execution is complete. Arguments to the SetCacheCriteria( ) call may specify a criteria set that should be associated with the cached JSP response. This criteria set may then be used to match against attributes of future JSP requests, as described above. In particular embodiments, any of various types of cache criteria may be supported.
    • 用于缓存JavaServer Page(TM)(JSP)组件响应的系统和方法。 JSP组件可以是在支持网络应用程序(如Web应用程序或其他基于Internet的应用程序)的应用程序服务器上执行的组件。 一个或多个客户端计算机,例如web服务器,可以执行引用应用服务器上的JSP组件的请求。 JSP组件的执行可以由在应用服务器上运行的JSP引擎进程来管理。 当从客户端计算机接收到引用JSP的请求时,JSP引擎可以首先检查JSP响应高速缓存以确定是否存在满足请求的有效JSP响应。 如果找到匹配的缓存响应,则可以检索响应并立即流传回客户端。 否则,可以执行引用的JSP。 每个JSP文件可以包括各种SetCacheCriteria()方法调用。 执行时,一旦JSP执行完成,SetCacheCriteria()调用可能导致JSP的输出被高速缓存。 对SetCacheCriteria()调用的参数可以指定应与缓存的JSP响应相关联的条件集。 然后可以使用该标准集合来匹配未来JSP请求的属性,如上所述。 在特定实施例中,可以支持各种类型的高速缓存标准中的任一种。