Service Locator Pattern

本文介绍了一种ServiceLocator模式,用于抽象和简化JNDI查找过程,减少重复查找次数并缓存EJBHome接口和数据源对象,从而提高应用程序性能。
转自:http://blog.csdn.net/fitzwilliam/article/details/1539068

How JNDI lookups are accomplished can vary from vendor to vendor. In addition, repeated JNDI lookups can be expensive.
Each time a user needs a service retrieved from JNDI, they must populate the appropriate environment information, make a connection to the JNDI server and then look up the service. What is needed is a single point for creating and retrieving various services from JNDI. This is where the Service Locator pattern is useful. 
The Service Locator pattern abstracts away all JNDI lookups behind a simple-to-use interface. The Service Locator implementation used in this chapter provides methods for retrieving EJBHome interface and JDBC database connections. In addition, this Service Locator minimizes the number of JNDI lookups required by caching EJBHomes interfaces and the DataSource objects used to create JDBC connections the first time a user requests a specific EJB or JDBC connection.
 
The for the Service Locator pattern is shown below:

/*
 * The Service Locator pattern abstracts away the JNDI
 * Logic necessary for retrieving a JDBC Connection or EJBHome
 * interface
 *
 */
public class ServiceLocator {
    private static ServiceLocator serviceLocatorRef = null;
    private static HashMap ejbHomeCache = null;
    private static HashMap dataSourceCache = null;
   
    /*
     * Enumerating the different services avaialbe from the
     * Service Locator
     */
    public static final int COUNTER = 0;
    public static final int TITLEDAO = 1;
    public static final int EDITORDAO = 2;
    public static final int SUBSCRIPTIONDB = 3;
   
    /* The JNDI Names used to lookup a service */
    private static final String COUNTER_JNDINAME="counter/Counter";
    private static final String TITLEDAO_JNDINAME="title/TitleDAO";
    private static final String EDITORDAO_JNDINAME="editor/EditorDAO";
    private static final String SUBSCRIPTIONDB_JNDINAME="java:/subscriptionDS";
   
    /* References to each of the different EJB Home Interfaces */
   private static final Class COUNTERCLASSREF = CounterHome.class;
   private static final Class TITLECLASSREF = TitleDAOHome.class;
   private static final Class EDITORCLASSREF = EditorDAOHome.class;
  
   static {
       serviceLocatorRef = new ServiceLocator();
   }

  
   /* Private Constructor for the ServiceLocator */
   private ServiceLocator(){
       ejbHomeCache = new HashMap();
       dataSourceCache = new HashMap();
   }

  
   /*
    * The ServiceLocator is implemented as a Singleton.  The getInstance()
    * method will return the static reference to the ServiceLocator stored
    * inside of the ServiceLocator Class.
    */
   public static ServiceLocator getInstance(){
       return serviceLocatorRef;
   }

  
   /*
    * The getServiceName will retrieve the JNDI name for a requested
    * service.  The service is indicated by the ServiceId passed into
    * the method.
    */
   static private String getServiceName(int pServiceId) throws ServiceLocatorException{
      
       String serviceName = null;
      
       switch ( pServiceId ) {
        case COUNTER:
            serviceName = COUNTER_JNDINAME;
            break;
        case TITLEDAO:
            serviceName = TITLEDAO_JNDINAME;
            break;
        case EDITORDAO:
            serviceName = EDITORDAO_JNDINAME;
            break;
        case SUBSCRIPTIONDB:
            serviceName = SUBSCRIPTIONDB_JNDINAME;
            break;
        default:
            throw new ServiceLocatorException("Unable to locate the service requested in" +
                    "ServiceLocator.getServiceName() method.  ");
        }
       return serviceName;
   }
  
   /*
    * Returns the EJBHome Class reference for a requested service.
    * If the method can not make a match, it will throw a
    * ServiceLocatorException.
    */
    static private Class getEJBHomeRef(int pServiceId) throws ServiceLocatorException{
        Class homeRef = null;
       
        switch ( pServiceId ) {
            case COUNTER:
                homeRef = COUNTERCLASSREF;
                break;
            case TITLEDAO:
                homeRef = TITLECLASSREF;
                break;
            case EDITORDAO:
                homeRef = EDITORCLASSREF;
                break;
            default:
                throw new ServiceLocatorException("Unable to locate the service requested in" +
                        "ServiceLocator.getEJBHomeRef() method.  ");
        }
        return homeRef;
    }
   
    /*
     * The getEJBHome method will return an EJBHome interface for a
     * requested service.  If it can not find the requested EJB, it will
     * throw a ServiceLocatorException.
     *
     * The getEJBHome interface caches a requested EJBHome so that the first
     * time an EJB is requested, a home interface will be retrieved but then
     * be placed into a cache.
     */
    public EJBHome getEJBHome(int pServiceId) throws ServiceLocatorException{
        //Tring to find the JNDI Name for the requested service
        String serviceName = getServiceName(pServiceId);
        EJBHome ejbHome = null;
       
        try {
            //checking to see if I can find the EJBHome interface in cache
            if ( ejbHomeCache.containsKey(serviceName) ) {
                ejbHome = ( EJBHome ) ejbHomeCache.get(serviceName);
                return ejbHome;
            } else {
                //If I could not find the EJBHome interface in the cache, look it
                //up and the cache it.
                Context ctx = new InitialContext();
                Object jndiRef = ctx.lookup(serviceName);
               
                Object portableObj = PortableRemoteObject.narrow(jndiRef, getEJBHomeRef(pServiceId));
               
                ejbHome = ( EJBHome ) portableObj;
               
                ejbHomeCache.put(serviceName, ejbHome);
                return ejbHome;
            }
        } catch ( NamingException e ) {
            throw new ServiceLocatorException("Naming exception error in ServiceLocator.getEJBHome()", e);
        } catch (Exception e) {
            throw new ServiceLocatorException("General exception in ServcieLocator.getEJBHome", e);
        }
    }
   
    /*
     * The getDBConn() method will create a JDBC connection for the
     * requested database.  It too uses a caching algorithm to minimize
     * the number of JNDI hits that it must perform.
     */
    public Connection getDBConn(int pServiceId) throws ServiceLocatorException{
        //Getting the JNDI Service Name
        String serviceName = getServiceName(pServiceId);
        Connection conn = null;
       
        try {
            //Checking to see if the requested DataSource is in the Cache
            if ( dataSourceCache.containsKey(serviceName) ) {
                DataSource ds = ( DataSource ) dataSourceCache.get(serviceName);
                conn = ds.getConnection();
                return conn;
            } else {
                //The DataSource was not in the cache.  Retrieve it from JNDI
                //and put it in the cache.
                Context ctx = new InitialContext();
                DataSource newDataSource = ( DataSource ) ctx.lookup(serviceName);
                dataSourceCache.put(serviceName, newDataSource);
                conn = newDataSource.getConnection();
                return conn;
            }
        } catch ( SQLException e ) {
            throw new ServiceLocatorException("A SOL error has occured in ServiceLocator.getDBConn()", e);
        } catch ( NamingException e ) {
            throw new ServiceLocatorException("A JNDI Naming exception has occured in ServiceLocator.getDBConn()", e);
        } catch (Exception e) {
            throw new ServiceLocatorException("An exception has occured in ServiceLocator.getDBConn()", e);
        }
    }

 

Implementing the ServiceLocator as a Singleton pattern is extremely efficient because the class is heavily used and does not need to maintain instance information.
The use of non-final static methods in the ServiceLocator is actually in violation of the EJB specification (see section 21.4.2). However, we can get away with this because we are not dependant on our cache being consistent across Java Virtual Machine, which is the reason that the restriction exists. You must also verify that your factory classes can be used by multiple threads concurrently without synchronization; this issue is not addressed in this specification. These two issues make our solution perform better but also make it slightly less portable. We could trade some performance back for portability by doing the caching in the bean instance instead.
 
From: 
J2EE Design Patterns Applied, Wrox
by Craig A.Berry, John Carnell, Matjaz B.Juric, Meeraj Moidoo Kunnumpurath, Nadia Nashi, Sasha Romano

内容概要:本文提出了一种基于非合作博弈理论的居民负荷分层调度模型,并结合双层鲸鱼优化算法(Two-level Whale Optimization Algorithm)进行高效求解,模型与算法均通过Matlab代码实现。研究针对电力系统中居民侧用电负荷的复杂调度问题,引入非合作博弈机制刻画各用户之间的利益竞争关系,实现负荷的分层优化分配;同时设计双层优化架构,上层优化资源配置,下层模拟用户自主决策行为,提升了模型的实用性与合理性。通过智能优化算法求解多层级、非凸非线性的博弈模型,有效提高了调度方案的收敛性与全局寻优能力,适用于现代智能电网中的需求侧管理与能源优化场景。; 适合人群:具备电力系统基础理论知识和Matlab编程能力,从事智能电网、能源优化调度、需求侧管理、博弈论应用等方向的科研人员、高校研究生及工程技术人员。; 使用场景及目标:①应用于居民区电力负荷的分层优化调度系统设计与仿真分析;②为非合作博弈在多主体能源系统建模中的应用提供方法论支持;③利用双层鲸鱼算法解决具有嵌套结构的复杂双层优化问题,提升求解效率与调度方案的可行性。; 阅读建议:建议读者结合提供的Matlab代码深入理解模型构建逻辑与算法实现流程,重点关注博弈模型的效用函数设计、纳什均衡求解思路以及双层优化结构的迭代机制,宜配合实际用电数据开展复现实验以验证模型有效性与鲁棒性。
内容概要:本文围绕基于自适应神经模糊推理系统(ANFIS)智能控制器的可再生能源微电网功率管理系统展开研究,结合Simulink仿真实现,深入探讨了微电网中功率的智能调控与经济机组组合调度问题。通过引入ANFIS控制器,有效应对风能、光伏等可再生能源出力的波动性与不确定性,提升系统运行的稳定性与电能质量。研究内容涵盖微电网多源协调控制策略、功率平衡管理、优化调度模型构建及仿真验证,实现了对分布式电源、储能系统和负荷的协同优化,兼顾经济性与可靠性目标,并通过仿真平台验证了所提方法的有效性与优越性。; 适合人群:具备电力系统、自动化或新能源相关专业背景,熟悉Matlab/Simulink仿真环境,从事微电网能量管理、智能控制、能源优化等领域研究的研究生、科研人员及工程技术人员。; 使用场景及目标:①用于高比例可再生能源接入场景下的微电网能量管理系统研发与教学实践;②为实现微电网功率稳定控制与经济高效运行提供先进的智能控制解决方案;③支撑高水平学术论文复现、科研课题攻关及实际工程项目的仿真验证与方案优化。; 阅读建议:建议结合提供的Simulink模型与相关代码进行动手实践,重点关注ANFIS控制器的设计流程、规则库构建与参数调优方法,并通过与传统PID或MPC控制策略的对比实验,深入理解其在动态响应与鲁棒性方面的优势。同时可进一步拓展文中提出的优化调度逻辑,应用于多目标、多约束的复杂实际应用场景中。
内容概要:本文档聚焦于“直流电机双闭环控制Matlab仿真”,系统阐述了基于Matlab/Simulink平台实现直流电机双闭环控制系统(主要包括速度环与电流环)的设计与仿真全过程。通过构建直流电机的数学模型,结合PI控制器进行调控,实现对电机转速和电枢电流的高精度动态控制,验证控制策略的稳定性与响应性能。文档详细介绍了仿真模型的搭建流程、关键参数的整定方法、系统动态波形的分析手段以及仿真结果的有效性验证,体现了经典自动控制理论在实际电机系统中的工程应用,是电机控制与电力电子技术相结合的典型研究案例。; 适合人群:具备自动控制原理、电机与拖动基础、电力电子技术和Matlab/Simulink仿真能力的电气工程、自动化、机电一体化等专业的本科生、研究生及从事电机驱动系统研发的工程技术人员。; 使用场景及目标:①作为高校课程设计或实验教学材料,帮助学生深入理解双闭环调速系统的工作机理与工程实现;②服务于科研项目,为新型电机控制算法(如滑模、模糊PID等)的开发与性能对比提供基础仿真验证平台;③作为工业界产品前期设计的仿真工具,用于评估不同控制策略在动态响应、抗干扰能力和稳态精度方面的可行性。; 阅读建议:建议读者在学习过程中紧密结合自动控制理论知识,亲手在Simulink环境中搭建完整的双闭环仿真模型,通过反复调整PI控制器的比例与积分参数,观察并分析转速、电流的阶跃响应曲线,从而深刻理解反馈控制的本质、系统稳定性条件以及参数整定对动态性能的影响,进而掌握电机控制系统的设计精髓。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值