ICE_CONFIG not honored under Java in 3.3

in Bug Reports
I may be misunderstanding under what conditions ICE_CONFIG is used in Java, but the attached tests shows that what I think is a straight-forward usage does not work, while it does so in Python.
0
Comments
And output from three different machines:
"The parameter-less version of createProperties simply creates an empty property set. It does not check ICE_CONFIG for a configuration file to parse."
Change your test to use Ice.Util.createProperties(args) and you should get the behavior you expect.
It's also possible to comment out the call to createProperties completely and still have the test case fail. It's there for doing the manual loading, but I did test without it.
Is the expected behavior that ICE_CONFIG will only be checked when command-line-like arguments are explicitly passed into either Ice.Util.createProperties or an initialize method, i.e. not when using something like "Ice.Util.initialize()" If so, would you mind explaining the logic behind this for me? The behavior in Python where: does honor ICE_CONFIG seems more natural.
Thanks again,
~Josh.
just another data point for your discussions. I was surprised that the two print methods returned different values:
Reading the manual again, createProperties() is responsible for parsing ICE_CONFIG/Ice.Config, but I continually assume that it's Ice.initialize(), perhaps because of the simplicity of Python's Ice.initialize() doing everything.
Not a complaint, just pointing out where even Ice regular's can go afoul.
~J.