Why Appian is not recognizing the org/w3c/dom/Node clas theat is bundled as part

sivananthag over 10 years ago

Why Appian is not recognizing the org/w3c/dom/Node clas theat is bundled as part of core JDK 1.7.51 - rt.jar package?

I am developing a smart service that consumes Axis2 (1.6.2 version) web service. ( the smart service has the client code using static stub). I have packaged the essential jars from Axis 2 ( approx 18 jars ) in my lib folder. When i package this plugin project using Appian-> Export plugin option, it creates a jar file and all the axis2 libraries i put in lib folder are moved to META-INF/ lib.

When i run my code in standalone java mode ( using java -jar ), the code works perfectly.
But when i deploy this smart service and test it, I got an error:

JBAS014134: EJB Invocation failed on component UnattendedRequestHandlerBean for method public abstract com.appiancorp.process.engine.ContinuationResponse com.appiancorp.ra.workpoller.UnattendedRequestListener.onMessage(com.appiancorp.process.engine.UnattendedRequest): javax.ejb.EJBException:...

Discussion posts and replies are publicly visible

Parents

0 sivananthag over 10 years ago

...urceByDelegation(BundleWiringImpl.java:1460) [org.apache.felix.framework-4.0.3.jar:]
          at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72) [org.apache.felix.framework-4.0.3.jar:]
          at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843) [org.apache.felix.framework-4.0.3.jar:]
          at java.lang.ClassLoader.loadClass(ClassLoader.java:358) [rt.jar:1.7.0_51]
My question is why should i include w3c/ DOM packages in my plugin when it is curretnly part of core JDK rt.jar itself?

Then to fix the NoClassDefFound issue, i added xml-api.jar (tried with various versions 1.0.b2, 1.3.044, 1.4.01) to my plugin jar and this time Node class got loaded from my plugin, but i got a different error:
Caused by: javax.ejb.EJBException: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
21:56:37,113 INFO [stdout] (default-threads - 35)           at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterce...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 sivananthag over 10 years ago

...urceByDelegation(BundleWiringImpl.java:1460) [org.apache.felix.framework-4.0.3.jar:]
          at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72) [org.apache.felix.framework-4.0.3.jar:]
          at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843) [org.apache.felix.framework-4.0.3.jar:]
          at java.lang.ClassLoader.loadClass(ClassLoader.java:358) [rt.jar:1.7.0_51]
My question is why should i include w3c/ DOM packages in my plugin when it is curretnly part of core JDK rt.jar itself?

Then to fix the NoClassDefFound issue, i added xml-api.jar (tried with various versions 1.0.b2, 1.3.044, 1.4.01) to my plugin jar and this time Node class got loaded from my plugin, but i got a different error:
Caused by: javax.ejb.EJBException: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
21:56:37,113 INFO [stdout] (default-threads - 35)           at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterce...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data