Yeah, the whole bootstrap mechanism was rewritten. There was no way we could keep it backwards compatible.
I tried to keep a few things around though, that are not detectable during user app compilation. E.g. org.apache.cayenne.conf.WebApplicationContextFilter (declared in web.xml), etc. But the upgrade definitely requires inspecting compile errors and providing 3.1 replacements for those.
Andrus
On Nov 22, 2010, at 12:01 PM, Aristedes Maniatis wrote:
> On 22/11/10 8:52 PM, Tore Halset wrote:
>> Hello.
>>
>> I am trying out the new M1 candidate. Upgrading from 3.0.1 this got me to a compile error since org.apache.cayenne.conf.Configuration does not exist any more.
>>
>> Is okay to remove this in 3.1 when it was not deprecated in 3.0.1?
>>
>> What should I use instead of Configuration.getSharedConfiguration().getDomain() to get to the DataDomain?
>>
>> - Tore.
>
> There are some notes about this in the UPGRADE.txt file. The whole org.apache.cayenne.conf package is gone.
>
> Ari
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
This archive was generated by hypermail 2.0.0 : Mon Nov 22 2010 - 11:04:52 UTC