Powered by Qumana
The client/server app can have coded entries that are seperate from the FINAL environment JNDI entries. This helps in differentiating coding from application assembly.
So inside the code you may have ctx.lookup("java:env/jms/blah1") but using the concept of "Resource References" and "Resource Environment References" you can map it up to "java:env/jms/blah2". The blah2 should be valid in the actual production environment. This avoids the need to change code or deployment descriptors.
Take a situaiton without them: the coder puts in blah1, but the server has blah2 which is being used by other programs already! now either has to change!- thatz where this comes in.
The funny part is that ResourceReference supports DB, Qconnections etc but does not support Queues. The support for JMS Queues (and their reference mapping) is covered under Resource Environment References.
The resource reference covers AS administered only and hence queue is dropped out.
No comments:
Post a Comment