Awsome, so its fixed? That was driving me nuts. Anything need to change in
jndi.properties?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830662#3830662
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830662
--
I believe it is fixed. However, maybe it goes a bit away from the original intent, by
us simply calling new InitialContext().bind()? I'm a bit confused!!! Why is this
different from using the standard context that comes with JBoss? Hmm...
Anyway, all unit tests work.
View the original post :
h
jndi.properties is the same
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830707#3830707
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830707
---
This SF.Net email
"kabkhan" wrote : maybe it goes a bit away from the original intent, by us simply
calling new InitialContext().bind()? I'm a bit confused!!!
Been reading up on naming and think it is kosher. I reckon the idea behind the
FakeInitialContext is to use the contained HashMap of bindings, and not to h
Calling the standard jboss InitialContext would have to connect to JBoss's naming
service which we'd have to set up and bind stuff etc. Might work just as well if we
take server/default/conf/jndi.properties and do it locally and register it in the
depends-service.xml but for some reason I could
Hi,
I'm having a slight problem with the jndi stuff for the testing. I am trying to use
the jboss naming service rather than the fake contet stuff.
I have set up the jndi.properties file to be:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.
Great questions. I think this is probably about where I got when I gave up and did
FakeIntialContext :-)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830876#3830876
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830
I've been very naughty and have done a cross post regarding the jndi properties in
order to reach a wider audience.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830929#3830929
Adrian has some comments regarding how we set up our MBeans, Andy what do you think?
View the original pos
I have commited the changes to the head branch, so that the mail services tests now
use the normal jboss naming service.
Using Adrian's suggestion
Thread.currentThread().getContextClassLoader().getResources("jndi.properties");
uncovered that java.naming.provider.url is present in twiddle.jar.
PS I could only get the NamingService to work "in-jvm", setting the ports to > 0
caused whole bunch of other problems.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831398#3831398
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mod
No longer any need to play around with twiddle.jar. Getting the naming service to work
both "in-jvm" and with sockets was simply a case of setting the bind addresses in
depens-service.xml.
Cheers,
Kab
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833524#38
11 matches
Mail list logo
