JNDI-Exploitation-Kit(A modified version of the great JNDI-Injection-Exploit created by @welk1n. This tool can be used to start an HTTP Server, RMI Server and
seen from United States
seen from United States

seen from Malaysia

seen from Malaysia
seen from United States

seen from Malaysia

seen from Uzbekistan

seen from Malaysia
seen from Türkiye
seen from China
seen from China
seen from Germany

seen from United Kingdom

seen from United States
seen from Philippines
seen from Netherlands
seen from China

seen from Austria

seen from United States

seen from United Kingdom
JNDI-Exploitation-Kit(A modified version of the great JNDI-Injection-Exploit created by @welk1n. This tool can be used to start an HTTP Server, RMI Server and

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Configurar mensajerÃa spring JMS por JNDI
Configurar mensajerÃa spring JMS por JNDI
En este ejemplo, quiero mostraros como realizar una configuración por JNDI para conectar nuestra aplicación con una cola de mensajerÃa (MQ, Rabbit…etc) y consumir mensajes de ella mediante un listener que estará escuchando de forma continua.
Lo primero que debemos de hacer es configurar en nuestro servidor de colas (el que tengamos, en mi caso tengo MQ-Series) las colas que vayamos a necesitar.…
View On WordPress
// JNDI: a Service Locator
The Java Naming and Directory Interface (JNDI) is a good example of Service Locator Pattern. It is often used by application servers to register resources at start time and later by deployed applications to look them up. Web applications typically use JNDI to look up data sources in this manner.
I often want to have myself a standalone JNDI context.
JNDI Datasource Tomcat
JNDI Datasource Tomcat
This tutorial will show you how to configure JNDI data source to tomcat server and get connection through your program using configured JNDI name. (more…)
View Post

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Java Naming and Directory Interface (JNDI)
To find JNDI names of your EJB with Jboss,
browse to http://<IP>:8080/jmx-console/
Under Jboss section, click on "service=JNDIView"
Click invoke under "java.lang.String list()"
Under "Global JNDI Namespace" you should have your namespace tree.
To talk to a local interface of the following Bean:
MyProject    +-MyBean       +-local       +-remote
        So this EJB is injected like this:
@EJB(mappedName="MyProject/MyBean/local") MyBeanLocal mbl;
Using context lookup:
initCtx = new InitialContext(); mbl = (MyBeanLocal)initCtx.lookup("MyProject/MyBean/local");
On Tomcat 6.x, Hibernate 3.x, MySQL, and JNDI
After lots of googling and documentation reading, I got a setup of mine to work properly with Tomcat 6.x, Hibernate 3.x, MySQL, and JNDI datasources. For what its worth, most of the resources on the web regarding setting this up with the versions I specified are worthless. To save myself the future hassle, and the lot of you who might be having a hard time setting this up, here are the configuration files and directives required.
yourapp/web/META-INF/context.xml:
<Context> <Resource name="jdbc/my_app" global="jdbc/my_app" auth="Container" type="javax.sql.DataSource" username="user" password="XXXX" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/my_db_name?autoReconnect=true" maxActive="8" maxIdle="4"/> </Context>
yourapp/web/WEB-INF/web.xml:
... <resource-ref> <description>DB Connection</description> <res-ref-name>jdbc/my_app</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref> ...
hibernate.cfg.xml:
... <hibernate-configuration> <session-factory> <!-- Database connection settings --> <property name="connection.datasource">java:comp/env/jdbc/my_app</property> <property name="dialect">org.hibernate.dialect.MySQLDialect</property> <property name="current_session_context_class">thread</property> <mappings here> </session-factory> </hibernate-configuration> ...
You can get your session factory as usual:
sessionFactory = new Configuration().configure().buildSessionFactory();
or whichever way you prefer.