-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Digital signature - class cast exception #82
Comments
This is happening for our company as well. |
Do you have an update on this issue? Need screenshots or logs? |
This is happening for our customer as well. Please can someone take a look?
|
Please @Tiliavir, can you take a look at this issue? |
Hi @vcknapp @ziton-git @bobbejokohler Please have a look here: #70 (comment) Best regards |
Hi @Tiliavir, I just uninstalled and re-installed the plugin and the issue is persisting. Please can you help? |
Hi @vcknapp did you also invalidate the plugin cache and restart confluence afterwards? |
Hi @vcknapp - we've just briefly discussed the issue reported (again) here; we'd kindly like to ask you to
|
feedback from todays mob-pair programming - @arburk @Tiliavir @svene @kullmanp :[...] So the solution we frequently use is to add a event listener, that listens for the PluginEnabledEvent and clears our caches. [...] Ideas worth a try
|
- BandanaManager.init() is called initially - removes workaround with clone - serialization of Signature to JSON using GSON
Besides other posts regarding this issue in the "Atlassian Developer Community" this one summarizes it quite well:
and further
Following that, I've added a PR that should address this issue in a self healing way. Meaning: The issue might occur again after an environment gets this patch (and requires a manual plugin cache reset / reboot once again), but should be fixed for all following updates. |
PR to review #88 |
Deeper investigations on that issue have shown a strange behaviour with Bandana Manager when upgrading the plugin. As soon as the plugin is updated, former created key-value pairs in Bandana Manager are still present by their key but corresponding values are null. This can be reproduced by following steps:
It is not yet clear why and how the value is getting lost, in particular as no write or update method on Bandana Manager can be noticed during the steps mentioned above. A quick research has also shown, that this behavior is monitored by others developers, too (e.g. https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Bandana-Keys-persist-plugin-update-but-values-don-t/qaq-p/459762) |
Maybe filing a bug directly @atlassian (developer board) - maybe more people and project (as above mentioned) are affected by this. |
#82: ClassCastException after Plugin update on DC
Fixed in 7.0.7 |
Hi Support
Something has happened with Digital Signature... It has stopped working across the entire platform/Confluence we have.
Behaviour is like this:
On any page add the DS-macro -> fill in what is needed and hit save -> macro will look okay, but:
The error given is the same irrespective of 1 or 2:
**Error rendering macro 'signature'
class com.baloise.confluence.digitalsignature.Signature cannot be cast to class com.baloise.confluence.digitalsignature.Signature (com.baloise.confluence.digitalsignature.Signature is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @32dc35ce; com.baloise.confluence.digitalsignature.Signature is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @5a5001e0)**
Action taken:
Not much I can do, I guess... I have tried disabling and re-enabling the plugin: no change.
I am really to look for details in the logs and share with you - please let me know of what to look for.
Brgds Felter
The text was updated successfully, but these errors were encountered: