"java.lang.NoSuchMethodError" when migrating from 1.5 to 2.0

Question

[ Problem ]
E:\Adobe2.0\Flash Access Reference Server Implementation\migration>java -cp bin;
libs\*;libs\1.5\*;libs\2.0\* com.adobe.flashaccess.refimpl.migration.V1_5PolicyC
onverter all
Exception in thread "main" java.lang.NoSuchMethodError: com.adobe.schema._1_0.pd
rl.Permission.getConstraint()Ljava/util/List;
        at com.adobe.flashaccess.sdk.policy.PolicyRightHelper.addToPolicy(Policy
RightHelper.java:272)
        at com.adobe.flashaccess.sdk.policy.PolicyRightHelper.toPDRL(PolicyRight
Helper.java:233)
        at com.adobe.flashaccess.sdk.policy.PolicyRightHelper.toASN1(PolicyRight
Helper.java:97)
        at com.adobe.flashaccess.sdk.policy.Policy.serializePolicy(Policy.java:6
70)
        at com.adobe.flashaccess.sdk.policy.Policy.getBytes(Policy.java:181)
        at com.adobe.flashaccess.refimpl.migration.AbstractPolicyConverter.write
PolicyToFile(AbstractPolicyConverter.java:100)
        at com.adobe.flashaccess.refimpl.migration.V1_5PolicyConverter.convertPo
licies(V1_5PolicyConverter.java:140)
        at com.adobe.flashaccess.refimpl.migration.V1_5PolicyConverter.main(V1_5
PolicyConverter.java:87)
[ Solution ]
The class mentioned in the error message is in rm-pdrl.jar, which should be in your libs/2.0 directory.  There may be a conflict between this jar and something in libs/1.5.  Please try moving libs/2.0 before libs/1.5 in your classpath and see if that resolves the issue.

Answer 1

hi Arie,
thanks for the tip ;-), I was using application id which was already use in my htmldb installation. I changed the id in the f105.sql to something which was not used and it went through fine.
We often run htmldb imports through sqlplus because when running it through web site it too often fails with timeout. When import is done through the web site I believe htmldb does the id modification automatically but in sqlplus that obviously won't happen hence we need to do it manually before running the script. If we don't change it import will fail as the workspace with the id mentioned in the sql script does not exist. Like you said might not be supported ....but it still works fine... :-)
thanks for your help.
Nina