Create custom library #4488
-
Hi guys, im trying since yesterday to get this simple Mirth tutorial working: I've created the simple POJO file and converted it via eclipse and was also able to import it into another project: When im trying to use this Class now in Mirth i get the following error: Can someone please tell me what is wrong with my jar file? There shouldn't be many pitfalls in this simple tutorial ? I've made sure that the library is imported: And also enabled in the channel: This is my created JAR file: This is what is inside the JAR File: I know that something is wrong with the process i've done since i was able to sucessfully import a JAR file from Talend. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
I do not see anything obviously wrong with this. You may want to try setting up a real directory resource instead of using custom-lib and see if that makes a different. Custom-lib usage is generally considered deprecated. |
Beta Was this translation helpful? Give feedback.
-
Tried with the JAR you supplied and got the same error. Tried reproducing creating my own class and JAR, got the same error again. I saw your comment and realized I had compiled with OpenJDK 15. When building with Oracle Java 8, it works. I should note that I was running Connect with Oracle Java 8 when testing. Per @tonygermano's question, I tested again building with OpenJDK 15, but setting the source and build target to Java 8. Tested with two JARs built with OpenJDK, one targeting 15 and one targeting 8 and confirmed that the former generates the error while the latter doesn't. |
Beta Was this translation helpful? Give feedback.
Tried with the JAR you supplied and got the same error. Tried reproducing creating my own class and JAR, got the same error again. I saw your comment and realized I had compiled with OpenJDK 15. When building with Oracle Java 8, it works. I should note that I was running Connect with Oracle Java 8 when testing.
Per @tonygermano's question, I tested again building with OpenJDK 15, but setting the source and build target to Java 8. Tested with two JARs built with OpenJDK, one targeting 15 and one targeting 8 and confirmed that the former generates the error while the latter doesn't.