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
4 replies
Subscribers
5 subscribers
Views
11780 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
Error with using the DocumentBuilderFactory when creating a plugin
nickh413445
Certified Senior Developer
over 8 years ago
I keep running into an issue with the DocumentBuilderFactory when creating a custom smart service plug-in.
The issue has to do with the appian-suiteapi.jar
Without the .jar file, my code is able to run successfully. When I add the appian-suiteapi.jar, I start getting the error below.
Does anyone have experience dealing with this issue? Is there another .jar I should be including to avoid this issue?
Exception in thread "main" javax.xml.parsers.FactoryConfigurationError: Provider for class javax.xml.parsers.DocumentBuilderFactory cannot be created
at javax.xml.parsers.FactoryFinder.findServiceProvider(Unknown Source)
at javax.xml.parsers.FactoryFinder.find(Unknown Source)
at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
..
..
Caused by: java.lang.RuntimeException: Provider for class javax.xml.parsers.DocumentBuilderFactor...
OriginalPostID-241401
Discussion posts and replies are publicly visible
Parents
0
nickh413445
Certified Senior Developer
over 8 years ago
The problem is I'm using a .jar that's using the javax.xml.parsers.DocumentBuilderFactory. I guess one solution is updating the .jar source code and recompiling to a new .jar and use that. It's most definitely a class-loading conflict as the code is the same, but only the inclusion of the appian jar gives the error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
nickh413445
Certified Senior Developer
over 8 years ago
The problem is I'm using a .jar that's using the javax.xml.parsers.DocumentBuilderFactory. I guess one solution is updating the .jar source code and recompiling to a new .jar and use that. It's most definitely a class-loading conflict as the code is the same, but only the inclusion of the appian jar gives the error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data