|
I have looked at our installation and only have minor use of dynamic tasklists, so I intend to just convert manually. I am now more worried about any other macros that use the same technique. Are there any known issues with other macros?
So far we haven't heard of any other macros affected by this issue. It could well be that the problem is related to the custom TaskList object which will get serialized. I'll have to investigate this to verify that this the case.
Serialized tasklist objects in 1.4 and1.5 format
While this JDK problem awaits developer resources, the workaround is to manually transfer dynamictasklist content as described at
Cheers, The above workaround we guess is not feasible to our setup since we have a large amounts of pages which have dynamic task list been used .
We are not able to use the older version of the JDK (1.4) as its' killing the confluence instance due to conflict with other plug-in/macro dependencies. we are looking another workaround where in we can migrate the older XML to newer versions. This is a roadblock to our production upgrade. We use Confluence Enterprise 2.1.5a (unlimited user edition).This issue is preventing our upgrade to (version 2.2.9).
It is impossible to manually find out and migrate hundreds of tasklists on different pages. Please increase the priority. I also get this error after a JDK upgrade for completely new task lists, such as {dynamictasklist:neverusedthisnamebefore}
Any update on this issue? We're in the same boat as everyone else...
Any update or workaround for this? I'm having the same problem.
An additional note on this. The context is much broader than the upgrade scenario. Our Confluence install was completely new and we experienced this issue.
Ted / Peter
I thought I had the same problem with a broader context, as I was running a brand new install of Confluence 2.3.3. However, it turned out I was using JDK (1.)6, which is distinctly unsupported by the Atlassian product range (look slike that's the problem with yours Ted). It works fine for us using JDK (1.)5. Hope this helps for now, although Atlassian should really start addressing the JDK 6 compatibility issues, now that it's out and many are moving towards it for developing new plugins. Kind Regards Updating the title of this issue to reflect the fact that this will happen when JDK versions are changed and not just an upgrade to 1.5
I've changed the dynamic task list model to not persist the internal java.util.Collections implementation of a synchronized list. This list is marked as transient and is constructed as necessary on creation and deserialization.
When conversion exceptions are thrown we now attempt to convert the task to the new model via a quick SAX converter. When this process is finished a new task list is returned. When lists are saved, they will be persisted in the new, much simpler task list model which will deserialize cleanly without any conversion necessary. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Critical
ConversionException on dynamic tasklist after JDK version change
http://jira.codehaus.org/browse/XSTR-202
You shouldn't have this problem for brand new dynamic task lists, created after the migration to JDK 1.5.