differences in 3.2 and 3.3 sdk?

[esource]

there seem to be differences between the 3.2 and 3.3 sdk.  For example, in alfresco-core-3.2r2.jar in package org.alfresco.config, there exists a Config.class as well as a number of other classes that don't exist in org.alfresco.config in alfresco-core-3.3g.jar nor in alfresco-core-3.3.jar.  In attempting to upgrade from 3.2 to 3.3, I find significant differences in the sdks.  What is the best way to approach this problem?

[mrogers]

In general this is caused by classes moving to spring source.   Your compiler will give you a list of classes which are "missing" and you need to change the "includes" in the failing classes to reference the new package.    You can probably do a global search and replace once you get going.

You will probably find the classes which are missing from org.alfresco in org.springframework

For example your Config class is org.springframework.extensions.config.Config

[esource]

I see.  Thank you for the information.   How about org.alfresco.web.scripts?  Do you know where these classes have been moved?  For example org.alfresco.web.scripts.DeclarativeWebScript or org.alfresco.web.scripts.Status or org.alfresco.web.scripts.WebScriptRequest?

[esource]

Looks like org.springframework.extensions.webscripts

[esource]

No, I can't find DeclarativeWebScript.  Would you know what replaces it in 3.3?

[mrogers]

org.springframework.extensions.webscripts.DeclarativeWebScript

[esource]

Yes, thank you! 

I have another error that puzzles me:

method does not override a method from its superclass
    [javac]    @Override
    [javac]          ^

The method in question is :

public class SampleEvaluator implements ActionEvaluator {

   @Override
   public boolean evaluate(Node node) {
       …
…
‍‍‍‍‍‍‍‍

org.alfresco.web.action.ActionEvaluator.evaluate(Node node) has the same signature:

  public abstract boolean evaluate(org.alfresco.web.bean.repository.Node arg0);
‍‍‍

The class signature hasn't changed from 3.2 to 3.3.  I didn't have any errors in 3.2.  Why am I now getting an error in 3.3?

[mrogers]

These @Override errors tend to come from compiling with different versions of Java.    I think the decision was made with 3.3 to make use Java 1.6 features.

[esource]

Yes, that fixed it.  Changing from 1.5 to 1.6 resolved the issue.