jndi

Spring Framework提供了一个使用 JavaMailSender 接口发送电子邮件的简单抽象，Spring Boot为它提供了自动配置以及启动器模块。 有关如何使用JavaMailSender的详细说明，请参阅参考文档。 如果 spring.mail.host 和相关库（由 spring-boot-starter-mail 定义）可用，则创建默认 JavaMailSender （如果不存在）。可以通过 spring.mail 命名空间中的配置项进一步自定义发件人。有关详细信息，请参阅 MailProperties 。 特别是，某些默认超时值是无限的，您可能希望更改它以避免线程被无响应的邮件服务器阻塞，如以下示例所示： spring.mail.properties.mail.smtp.connectiontimeout=5000 spring.mail.properties.mail.smtp.timeout=3000 spring.mail.properties.mail.smtp.writetimeout=5000 也可以使用JNDI中的现有 Session 配置 JavaMailSender ： spring.mail.jndi-name=mail/Session 设置 jndi-name 时，它优先于所有其他与会话相关的设置。 觉得有帮助的可以支持一下博主 来源：

I've added the following in my web.xml: <ejb-ref> <ejb-ref-name>ejb/userManagerBean</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <home>gha.ywk.name.entry.ejb.usermanager.UserManagerHome</home> <remote>what should go here??</remote> </ejb-ref> The following java code is giving me NamingException: public UserManager getUserManager () throws HUDException { String ROLE_JNDI_NAME = "ejb/userManagerBean"; try { Properties props = System.getProperties(); Context ctx = new InitialContext(props); UserManagerHome userHome = (UserManagerHome) ctx.lookup(ROLE_JNDI_NAME); UserManager userManager =

I have DataSource which is configured on Tomcat 6 in context.xml as MyDataSource. And I'm fetching it the following way: DataSource dataSource; try { dataSource = (DataSource) new InitialContext().lookup("java:comp/env/MyDataSource"); } catch (NamingException e) { throw new DaoConfigurationException( "DataSource '" + url + "' is missing in JNDI.", e); } Everything works fine. Now I'm exporting this code to Jboss AP 6. and I configured my dataSource and its connection pool as local-tx dataSource under the same name. When I'm executing the code above, I'm getting NamingException exception. after

What is the best approach to get EntityManagerFactory in web app(jsp/servlets)? Is this a good way When should EntityManagerFactory instance be created/opened? , or is it better to get it from JNDI, or something else? They're heavyweight and they're supposed to be in the application scope. So, you need to open them on application startup and close them on application shutdown. How to do that depends on your target container. Does it support EJB 3.x (Glassfish, JBoss AS, etc)? If so, then you don't need to worry about opening/closing them (neither about transactions) at all if you just do the

I just spent too much time of my day trying to figure out some errors when hooking up some JNDI factory bean. The problem turned out to be that instead of this... <bean id="someId" class="org.springframework.jndi.JndiObjectFactoryBean"> <property name="jndiName" value="java:comp/env/jdbc/loc"/> </bean> I had actually written this... <bean id="someId" class="org.springframework.jndi.JndiObjectFactoryBean"> <property name="jndiName" value="jdbc/loc"/> </bean> I infer that the java:comp/env/ perhaps references some environment variable and makes it so that, ultimately, my context file is looked

What is JNDI ? What is its basic use? When is it used? duffymo What is JNDI ? It stands for Java Naming and Directory Interface . What is its basic use? JNDI allows distributed applications to look up services in an abstract, resource-independent way. When it is used? The most common use case is to set up a database connection pool on a Java EE application server. Any application that's deployed on that server can gain access to the connections they need using the JNDI name java:comp/env/FooBarPool without having to know the details about the connection. This has several advantages: If you