facebook

In-workspace deployment

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse IDE
  2.  > 
  3. WebSphere Development
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #319831 Reply

    zdragkas
    Participant

    In-workspace deployment fails when the <build> folder is not found in project path. We were using linked resources and the <build> folders was relocated to another directory. Is this workspace setup not supported by the in-deployment mode yet?

    Thank you in advance for your time.

    #319852

    Brian Fernandes
    Moderator

    zdragkas,

    By “build” – do you mean the output folder for your source folders? Could you please elaborate on your project set up a bit more? If you could send me the .classpath and the .project file, that would help. Is this a web or EJB project?

    #319863

    zdragkas
    Participant

    I am sorry for not being elaborate.

    Our workspace is composed of several ejb, web projects and an ear project. By <build>, yes I mean the output folder, which in our case is located under a tmp directory. The tmp directory is defined as a path variable and the linked resources are enabled.

    Starting the in-workspace deployment, the exception below is thrown:

    [9/22/11 10:21:44:736 CEST] 00000019 SystemErr R org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NestedJarException: IWAE0008E An error occurred reading <ejb>.jar from C:\Projekte\trunk\fb
    Stack trace of nested exception:
    java.io.FileNotFoundException: C:\Projekte\trunk\<ejb>\build (The system cannot find the file specified.)
    at java.io.FileInputStream.<init>(FileInputStream.java:83)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryLoadStrategyImpl.getInputStream(DirectoryLoadStrategyImpl.java:827)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.NestedArchiveLoadStrategyImpl.getZipInputStream(NestedArchiveLoadStrategyImpl.java:296)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.NestedArchiveLoadStrategyImpl.safeGetZipInputStream(NestedArchiveLoadStrategyImpl.java:336)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.NestedArchiveLoadStrategyImpl.getFiles(NestedArchiveLoadStrategyImpl.java:382)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.collectFiles(LoadStrategyImpl.java:732)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ContainerImpl.getFiles(ContainerImpl.java:473)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.EjbJar30NoDDImportStrategyImpl$Discriminator.hasEjbContents(EjbJar30NoDDImportStrategyImpl.java:97)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.EjbJar30NoDDImportStrategyImpl$Discriminator.canImport(EjbJar30NoDDImportStrategyImpl.java:70)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.RootEJBJarDescriminatorImpl.canImport(RootEJBJarDescriminatorImpl.java:47)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.openArchive(ArchiveTypeDiscriminatorImpl.java:161)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.RootEJBJarDescriminatorImpl.openArchive(RootEJBJarDescriminatorImpl.java:108)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.getImportableArchiveFromChild(ArchiveTypeDiscriminatorImpl.java:137)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.openArchive(ArchiveTypeDiscriminatorImpl.java:165)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.CommonarchiveFactoryImpl.openSpecificArchive(CommonarchiveFactoryImpl.java:1527)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.CommonarchiveFactoryImpl.openArchive(CommonarchiveFactoryImpl.java:1163)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.CommonarchiveFactoryImpl.openNestedArchive(CommonarchiveFactoryImpl.java:1380)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl.openNestedArchive(EARFileImpl.java:1172)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.openNestedArchive(LoadStrategyImpl.java:1185)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.collectFilesFromLooseArchives(LoadStrategyImpl.java:785)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.collectFiles(LoadStrategyImpl.java:731)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ContainerImpl.getFiles(ContainerImpl.java:473)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl.getFiles(EARFileImpl.java:2472)
    at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl.getModuleFiles(EARFileImpl.java:970)
    at com.ibm.ws.management.application.client.AppInstallHelper.checkIfEE5ModulesContainXMIBindings(AppInstallHelper.java:1059)
    at com.ibm.ws.management.application.client.AppInstallHelper.checkForEE5Restrictions(AppInstallHelper.java:324)
    at com.ibm.ws.management.application.task.ValidateEE5RestrictionTask.performTask(ValidateEE5RestrictionTask.java:126)
    at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:285)
    at java.lang.Thread.run(Thread.java:736)

    Naturally, the C:\Projekte\trunk\<ejb>\build does not exist since the correct path would be C:\Projekte\trunk\tmp\<ejb>\build .

    #319870

    Brian Fernandes
    Moderator

    zdragkas,

    Thanks for the update – our team is looking into this now; I’ll update this thread with more details as they become available.

    #319878

    zdragkas
    Participant

    I will be watching the topic for updates. Due to the size of our application, the In-workspace deployment is really important for us and one major criterion for the replacement of RAD by MyEclipse.

    #319918

    Brian Fernandes
    Moderator

    We were able to replicate and fix your problem; the fix will be released in 9.1.1 and 10.0, both of which will be released in a couple of weeks.

    The only work-around for now, with 9.1, is to put your binary folders back into your project.

    If you are interested in testing a pre-release of 10.0, please write in to support@genuitec.com with a link to this thread and I’ll send you a beta version to ensure that this problem is correctly taken care of.

    Thank you for your support and for writing in.

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: In-workspace deployment

You must be logged in to post in the forum log in