Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
6 replies
Subscribers
5 subscribers
Views
2700 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
I've written an Appian smart service plugin for an integration that has a de
gauravg568
over 8 years ago
I've written an Appian smart service plugin for an integration that has a dependency on jersey-client-1.18.jar, and jersey-core-1.18.jar. However, Appian's installation also has atlassian-rest-module-2.6.7.jar, which has classes with same name and package as in the jersey-client* and jersey-core* jars. The class loader seems to load the atlassian-rest-module classes, which is causing the following Class Cast Exception: Cannot cast com.sun.jersey.core.impl.provider.header.LocaleProvider to com.sun.jersey.core.impl.provider.header.LocaleProvider . Is there any way to resolve this class loading conflict so I may get my plugin smart service to use the jersey* jar classes? Appreciate your help.
OriginalPostID-196932
OriginalPostID-196932
Discussion posts and replies are publicly visible
Parents
0
gauravg568
over 8 years ago
Thanks Eliot. We are trying to integrate with DocuSign using an Appian smart service plugin. The error is thrown when making a DocuSign method call such as when creating an envelope. The jersey jar is in turn a dependency for the docusign jar, which is why we need classes from the Jersey jar to load. However, classes with same name and package as Jersey jar are loaded from the Atlassian-rest jar in Appian thus causing the class conflict. We can't do away with the Jersey jar since DocuSign requires it, and it is unlikely we can do away with atlassian-rest jar since it comes prepackaged with Appian.
For those who have integrated with DocuSign before, did you run into a similar issue? How did you achieve the integration?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
gauravg568
over 8 years ago
Thanks Eliot. We are trying to integrate with DocuSign using an Appian smart service plugin. The error is thrown when making a DocuSign method call such as when creating an envelope. The jersey jar is in turn a dependency for the docusign jar, which is why we need classes from the Jersey jar to load. However, classes with same name and package as Jersey jar are loaded from the Atlassian-rest jar in Appian thus causing the class conflict. We can't do away with the Jersey jar since DocuSign requires it, and it is unlikely we can do away with atlassian-rest jar since it comes prepackaged with Appian.
For those who have integrated with DocuSign before, did you run into a similar issue? How did you achieve the integration?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data