Is this behavior the same across all JRE's?

Question

Hey folks!
Given the following piece of code:
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.dns.DnsContextFactory");
DirContext ictx = new InitialDirContext(env);
String dnsServers = (String) ictx.getEnvironment().get("java.naming.provider.url");
System.out.println(dnsServers);
The magically returns back to me the DNS servers when I didn't even set my provider URL. I did a little Google search and came across this from Sun's website:
"The host and port indicate the DNS server to use. If only a host is given, the port defaults to 53; if only a port is given, the host defaults to "localhost". If neither is given, the provider will attempt to determine and use the server(s) configured for the underlying platform, and if successful, will set the java.naming.provider.url property to a space-separated list of URLs constructed using the server(s). (For example, on Solaris or Linux, the provider will read the /etc/resolv.conf file.) If DNS has not been configured on the underlying platform, the host and port default to "localhost" and 53."
I am running this code on windows XP. What is the mechanism by which it is determining the DNS? Am I guaranteed that whenever I don't set the URL for the DNS it will always try and locate one? And lastly, will the above code work on all JRE's (IBM's, BEA's) ? I know I am setting the initial context to com.sun.jndi.dns.DnsContextFactory, what would it be for BEA and IBM?

Answer 1

AS I understand your question, after you migrate to V6 you want all the controls in your 5.1 application to have the new 3D look and be consistent....
There is no tool that automatically goes through all your code and converts one control to another. However, depending on how you developed your code, the process might not be too bad. The key issue is the extent to which you utilized typedefs.
If you change the look of all you typedefs, the strict ones will change right away to the new look. For the regular typedefs, you'll need to have all the VIs in you application in memory at once.
Now, open the non-strict typedef and change it to the new 3D controls, and save it as a strict typedef. At this point all the instances will update. Finally reopen the typ
edef and change it back to a non-strict and save it again.
Having said all this, the process I outlined above will can take a bunch of memory (and time) depending upon how big your application is... but it will work.
As far as the nontypedef controls in your application--you're on your own...
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps