Thanks for the reply.
The IVTCF-ds.xml includes the explicit config
use-java-contextfalse/use-java-config
Also, the JMX-Console JNDIView 'list' operation confirms that IVTCF is bound
in the JNDI Global Namespace.
It remains puzzling that when I parameterize the InitialContext with
Thanks for your reply gaohoward.
I modified the code as you indicated:
| Properties props = new Properties();
|
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,org.jnp.interfaces.NamingContextFactory);
|
FYI, I have a reasonably manageable workaround (though not ideal).
When I code the exact same .lookup() logic from a JBoss-deployed servlet
(instead of from an external app), everything works perfectly. This is
obviously because the internal InitialContext construction needs no Context.XXX
I have successfully deployed and executed IBM's WSMQ JCA Resource Installation
and Verification Test application (wmq.jmsra.ivt.ear) on my JBoss 5.1 AS
instance.
The IVT app establishes on my JBoss instance a
Resource--ConnectionFactory--TxConnectionFactory named 'IVTCF' that is
visible
I am trying to write a super-simple .java standalone app that looks up a JBoss
JNDI-hosted ConnectionFactory (configured as JCA Resource). The
ConnectionFactory (named 'IVTCF' and visible in my JBoss AS 5 Admin Console
under Resource--ConnectionFactory) is also configured (via a Resource
I am trying to write a super-simple .java standalone app that looks up a JBoss
JNDI-hosted ConnectionFactory (configured as JCA Resource). The
ConnectionFactory (named 'IVTCF' and visible in my JBoss AS 5 Admin Console
under Resource--ConnectionFactory) is also configured (via a Resource
Given an IBM WSMQ 6.x hosted 'Queue' instance (MANAGER, QUEUE NAME, CHANNEL all
explicitly identified with values), what is the easiest way to bind this
specific 'Queue' to a NAME in a JBoss 5.x hosted JNDI tree?
I've already copied the WSMQ provided wmq.jmsra.rar to my
Never mind. Found a best answer to this question here:
http://www.ibm.com/developerworks/websphere/library/techarticles/0710_ritchie/0710_ritchie.html?ca=drs
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4255165#4255165
Reply to the post :
Given JSR-299 is in final DRAFT, is it fair to say that, once all of {MC,
Spring, Guice, et. al. DI IoC providers} are JSR-299 compliant, the community
may soon have a single provider independent API for wiring application Bean
sets?
Will this be true of MC? I.e. will I be able to realize
Thanks for these responses. Very informative.
Regarding MC's enthusiasm for implementing JSR-330 ... have the strong concerns
expressed by significant JCP executive members
(http://jcp.org/en/jsr/results?id=4944) been addressed satisfactorily?
Especially re: RedHat's explicit abstain vote
10 matches
Mail list logo
