On Oct 16, 2013, at 5:00 PM, Darran Lofthouse <darran.lofthouse(a)jboss.com> wrote:
On 16/10/13 16:50, Eduardo Martins wrote:
> There is also WFLY-2115, but I am holding resolution till WFLY-794 is resolved.
> For any url scheme we do not provide custom implementation, which is the case for
rmi://, the code you mention is missing is actually invoked at
Ah I missed that line so we do attempt to resolve it that way.
Probably the bit we are missing then is the common method in the JDK code that all
methods use to obtain the correct context rather than issolating it within one lookup
Yes, that's why I believe it's not correct below ^^
> But that's only true for lookups, which I believe is not
correct, for instance a bind or InitialDirContext.search() will never go through that.
For an InitialDirContext non of the JBoss classes come into it at all, once the JDK
supplied classes are found they are used - however the advanced option for finding a url
context is skipped as the JDK classes assume we will handle that.
It's the same for InitialContext, you use the JDK constructors, and that's the
reason we set the factory builder, otherwise we could not override the jdk naming impl.