Caused by: java.io.FileNotFoundException: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ArchiveStore\306\at\integrata\livecycle\component\BootstrapImpl.class (The system cannot find the path specified)
...
Caused by: java.io.FileNotFoundException: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ArchiveStore\306\at\integrata\livecycle\component\BootstrapImpl.class (The system cannot find the path specified)
...
The problem is, that the workbench is not running on the same computer as the ES server. When I extract the jar-file manually into the considered directory on the server everything works fine.
Is this a bug or even not possible to import components from a remote workbench?
I ran into the same problem. I created the JAR file in Eclipse Java IDE, then used the 'Install Components' in Workbench. I get the same error you got. Sorry I don't have an answer for you, but I'll keep an eye on this forum and maybe an 'expert' will provide us an answer.
Thanks but I don't think that the tree is wrong because there are just two directories (mainpackage [com.company.component], icons) and the componant.xml in the root directory.
And as I said, if I'll extrat it manually into the required directory the import works fine.
I think that Debaecker is right. In the error log it actually lists your temp folder. You might wanna double check the structure again. Have you tried opening the JAR with a compression utility like WinRar, or 7-Zip?
I think the cause with me is that I added libraries my component needs manually into the jar-file of my component and sometimes I added the component.xml file manually into the component-jar. I use 7Zip for this but every I did that I could not get the component to install correctly, unless I unpacked it manually in the temp-dir.
I believe this is happens because when I manually place files in the jar file with a tool like 7Zip they are automatically being compressed and the jar-file of a component must not be compressed.
So therefore I imported everything correctly in my Eclipse-project and now when I Export my component to a jar-file, everything is included and I don't have to place files manually into the jar-file of my component.
When I install a component created like that I don't have any problems.