Hi, I think that I made that change as part of the changes to handle serialization of EntityManagers. However, issues with BrokerFactory caching based on full properties, so I switched to just use the configuration's id. So, it's probably fine to just revert that one change.
-Patrick On 11/27/07, Prashant Bhat <[EMAIL PROTECTED]> wrote: > I've finally found the place where properties passed were getting removed. > In r597155 this change is made. see > http://fisheye6.cenqua.com/browse/openjpa/trunk/openjpa-lib/src/main/java/org/apache/openjpa/lib/conf/ConfigurationImpl.java?r1=577164&r2=597155 > That block of code is: > // now warn if there are any remaining properties that there > // is an unhandled prop, and remove the unknown properties > Map.Entry entry; > for (Iterator itr = remaining.entrySet().iterator(); itr.hasNext();) > { > entry = (Map.Entry) itr.next(); > Object key = entry.getKey(); > if (key != null) { > warnInvalidProperty((String) key); > map.remove(key); > } > } > > I've not tried to debug further to identify why those > properties(mentioned in my previous post) are not > recognised as standard properties. > > I've reverted the above change and my application is working again. > > So my question is: are those property names changed or the way I pass > it is wrong or there is problem in recognising these properties as > standard properties? > > Regards, > Prashant > -- Patrick Linskey 202 669 5907
