jndi

I'm using WildFly 8.1.0 Final release. My application is a JavaEE web app deployed in a WAR (there is no EJB module .ear). I want to programmatically invoke local EJB with his name using JNDI. The EJB are just annotated with @Stateless (there is no Local or Remote interfaces) I try below function: private <E extends DomainObject> CrudService<E> lookUp(Class<E> cl) { try { final Hashtable jndiProperties = new Hashtable(); jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); final Context context = new InitialContext(jndiProperties); // The app name is the application

I have a maven project in IntelliJ where I am trying to deploy a war file to a jetty container. The purpose of this is for a quick integration test of some of the functionality in said war file. Since out of the box Jetty does not come with CDI or JNDI, I am trying to add support for these but running into some issues. For example, I get the following error on startup: 15:30:50 [34mINFO [0;39m o.a.s.c.CdiObjectFactory - [lookup]: Checking for BeanManager under JNDI key java:comp/BeanManager 15:30:50 [39mDEBUG[0;39m o.a.s.c.CdiObjectFactory - [lookup]: BeanManager lookup failed for JNDI key

I have a .properties file in my application which contains dataSource properties. I set up a JNDI reference to this dataSource using the following code : // first I create MyDataSource from the properties found in the .properties file //then : Context initContext = new InitialContext(); initContext.createSubcontext("jdbc"); initContext.createSubcontext("jdbc/oracle"); initContext.rebind(jdbc/oracle/myDataSource, MyDataSource); If I use a lookup in this application, the dataSource is found : Context initContext = new InitialContext(); BasicDataSource dataSource = (BasicDataSource) initContext

Context context = new InitialContext(); dataSource = (DataSource) context.lookup("java:comp/env/jdbc/multiDS"); connection = dataSource.getConnection(); Please help me to mock the above code. Hi Tom Anderson I tried the below code @BeforeClass public static void setUpClass() throws Exception { // rcarver - setup the jndi context and the datasource try { // Create initial context System.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.apache.naming.java.javaURLContextFactory"); System.setProperty(Context.URL_PKG_PREFIXES, "org.apache.naming"); Context ic = new InitialContext(); ic

Is there any situation still ( given that Java EE6 has java:global/, app/, module/ naming standards) that necessitates declaring EJBs or Resources like the example below? @EJB (name = "ejb/PlaceBid", beanInterface = PlaceBid.class) public class ActionBazaarBidControllerServlet extends HttpServlet { } Looking up PlaceBid in the helper class used by ActionBazaarBidControllerServlet PlaceBid placeBid = (PlaceBid)context.lookup("java:comp/env/ejb/PlaceBid"); The java:comp/env/ namespace is sometimes a little understood feature. This namespace corresponds to what is called the Enterprise Naming

连接池的优缺点 优点 使用连接池的最主要的优点是性能。创建一个新的数据库连接所耗费的时间主要取决于网络的速 度以及应用程序和数据库服务器的 ( 网络 ) 距离，而且这个过程通常是一个很耗时的过程。而采用 数据库连接池后，数据库连接请求可以直接通过连接池满足而不需要为该请求重新连接、认证到 数据库服务器，这样就节省了时间。 缺点 数据库连接池中可能存在着多个没有被使用的连接一直连接着数据库 ( 这意味着资源的浪费 ) 。 DBCP 一、导包 Apache官网下载DBCP包，导入两个包路径如下： commons-dbcp-1.4-bin\commons-dbcp-1.4\commons-dbcp-1.4.jar：连接池的实现 commons-pool-1.5.6-bin\commons-pool-1.5.6\commons-pool-1.5.6.jar：连接池实现的依赖库 CSDN上jar包的下载地址：http://download.csdn.net/detail/u012802702/9491642 二、代码示例： 方式一：使用BasicDataSource 通过方法设置连接参数。 [java] view plain copy //获取BasicDataSource并配置，开始.... BasicDataSource source = new BasicDataSource();

I'm using Websphere Portal 7.0 and creating a portlet with RAD 8.0. My portlet is trying to make a db2 connection to a remote server. I wrote a java program locally to do a basic JDBC connection to the server and get records from a table. The code works fine; however, when I add the code to my portlet as well as the db2jcc4.jar, the connection doesn't work. I'm using the basic: Connection connection = DriverManager.getConnection("jdbc:db2://server:port/db:user=user;password=pw;"); I figure that using the Websphere datasource is the right way to go. I know the JNDI name for the datasource, but