Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Giribabu Paruchuri (Giri Paruchuri) Lead System Architect
Coforge
AU
Giri Paruchuri Member since 2014 5 posts
Posted: Jul 30, 2015
Last activity: Aug 3, 2015
Posted: 30 Jul 2015 23:29 EDT
Last activity: 3 Aug 2015 2:04 EDT
Closed

Web.xml syntax required to use resource references in JMS Listener

Hi ,

As part of my project needs we need to work with JMS Listener.Initially we used Direct JNDI Lookup but there some limitation when adding custom properties in JNDI Server.  
I want to configure JNDI server properties using Resource Reference option.
As my project supports war deployment we need web.xml syntax  for configuring JNDI server details.

Your quick response will be highly appreciated.

Thanks in advance.

To see attachments, please log in.
Data Integration

Related content:

Question Solved

Impact of modifying "WebStandard" Servlet in web.xml

Question

< distributable/ > tag from web.xml

Question

How to utilize web.xml and custom servlet to create dual URL

Question

Can anyone help me with the changes of the web.xml for enabling api?

Question Solved

Custom Servlet mapping in web.xml not working in Pega 23.1

Question Solved

Session Timeout configured in web.xml in Pega 7.3 Personal edition not working

Question

configure JMS listeners for activemq in JBOSS. How to Configure a JMS service to get JMS resources through resource references

Question

Is there a way to customise in the Web.xml that this particular URL should use SSO AuthService and the other URL should use SSO1 AuthService

Question

Connect JMS in Tomcat 6.0.37 via Resource Reference

Discussion

Error when using global resource setting syntax in MQ Listeners and MQ Servers

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice