Skip to main content



      Home
Home » Modeling » M2T (model-to-text transformation) » "Internal Error" when deploying a JET transform
"Internal Error" when deploying a JET transform [message #52129] Fri, 17 October 2008 04:13 Go to next message
Eclipse UserFriend
I have a simple JET transform that works fine when I run it inside a
"child" Eclipse Application for debugging (for some reason I don't fully
understand it doesn't run in my development instance). Now I want to
deploy the transform. I did:

1. Export deployable plugin (into a folder)
2. Closed the original project to prevent interference.
3. Took the create JAR, put it in "Dropins"
4a. The plugin gets loaded eventually, but trying to run transform gives
me an "Internal Error" caused by an "IllegalArgumentException" (stack
trace below, it's the same in all cases.

Since that didn't work, remove the plugin from "Dropins" and restarted
Eclipse.

4b. Added the folder I export to, to the JET Transforms preferences, and
ran the transform again. Same effect as above.

The stack trace I get for the error is this:
java.lang.IllegalArgumentException
at
org.eclipse.jet.internal.launch.JET2TransformationDelegate.g etSource(JET2TransformationDelegate.java:69)
at
org.eclipse.jet.internal.launch.JET2TransformationDelegate.l aunch(JET2TransformationDelegate.java:54)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:764)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:614)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:880)
at
org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlu gin.java:1083)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Any ideas what I'm doing wrong or what could be causing this error?

Thanks,
Jochen
Re: "Internal Error" when deploying a JET transform [message #52261 is a reply to message #52129] Wed, 22 October 2008 16:14 Go to previous message
Eclipse UserFriend
Jochen:

This particular IllegalArgumentException is thrown if the Transformation
Input path on the transformation config does not map to a real-life file.

Obviously, a better error message is in order. I have submitted bug 251773:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=251773

Paul
Previous Topic:why WS tags not autoimported?
Next Topic:Unable to Parse XML EMF Document
Goto Forum:
  


Current Time: Fri May 02 17:22:48 EDT 2025

Powered by FUDForum. Page generated in 0.03794 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top