On Feb 28, 2007, at 12:38 AM, David Blevins wrote:
First, it seems like a bug in xbean-reflect's File property editor (haven't looked too hard yet). We're supplying the string "C:/ temp" and it's giving back "/private/tmp/openejb3/container/openejb- core/C:/temp". So clearly it's calling new File (string).getAbsoulteFile() and returning that. Something to look into fixing as I don't think it's xbean reflect's place to be resolving relative paths.
I wrote that code, but I think you are correct. If the receiving bean wants an absolute path, it can make the calls itself.
Second is a completely trival issues. Seems the calling of equals on two properties instances isn't kosher. It complains "expected:< {key2=value2, key1=value1}> but was:<{key1=value1 key2=value2}>", so obviously they are equal and something else going wrong.
Are you sure that they the values are both plain old java.lang.Strings? -dain
