Petals Studio

SA import does not import all files into the workspace

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.0, 1.1.0
  • Fix Version/s: 1.1.1
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:

    I use the SA import feature to add existing SA archives (the ones provided with the Petals View tutorial).
    They are not corectly imported. For example, the JBI descriptor is missing.

  • Environment:
    Ubuntu 10.04, 32 bits, Intel

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Fri, 23 Jul 2010 - 11:12:12 +0200

Have you tested this issue with the version 1.1.0?
In 1.0, here was a bug during the parsing of the SA's jbi.xml (the component name could not be retrieved).

Show
Vincent Zurczak added a comment - Fri, 23 Jul 2010 - 11:12:12 +0200 Have you tested this issue with the version 1.1.0? In 1.0, here was a bug during the parsing of the SA's jbi.xml (the component name could not be retrieved).
Hide
Permalink
Christophe DENEUX added a comment - Fri, 23 Jul 2010 - 11:32:07 +0200

No. Where can I get the version 1.1.0 ?
Only the version 1.0 is available on http://download.petalslink.com/petals-studio/

Show
Christophe DENEUX added a comment - Fri, 23 Jul 2010 - 11:32:07 +0200 No. Where can I get the version 1.1.0 ? Only the version 1.0 is available on http://download.petalslink.com/petals-studio/
Hide
Permalink
Christophe DENEUX added a comment - Fri, 23 Jul 2010 - 15:30:15 +0200

With the version 1.1, the problem has changed.
Importing a SA creates the following project in the Package Eplorer view:

  • the project associated to the SA, without the jbi.xml
  • the project associated to the SU, without the jbi.xml
    And, only the project associated to the SA in the Petals Project view.
    More over, the following error appears twice: Could not move the jbi.xml file.
    java.io.IOException: Could not move the jbi.xml file.
    at com.ebmwebsourcing.petals.services.wizards.ServiceAssemblyImportWizard.doFinish(ServiceAssemblyImportWizard.java:250)
    at com.ebmwebsourcing.petals.services.wizards.ServiceAssemblyImportWizard$1.execute(ServiceAssemblyImportWizard.java:95)
    at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
    at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Show
Christophe DENEUX added a comment - Fri, 23 Jul 2010 - 15:30:15 +0200 With the version 1.1, the problem has changed. Importing a SA creates the following project in the Package Eplorer view:
  • the project associated to the SA, without the jbi.xml
  • the project associated to the SU, without the jbi.xml And, only the project associated to the SA in the Petals Project view. More over, the following error appears twice: Could not move the jbi.xml file. java.io.IOException: Could not move the jbi.xml file. at com.ebmwebsourcing.petals.services.wizards.ServiceAssemblyImportWizard.doFinish(ServiceAssemblyImportWizard.java:250) at com.ebmwebsourcing.petals.services.wizards.ServiceAssemblyImportWizard$1.execute(ServiceAssemblyImportWizard.java:95) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Hide
Permalink
Vincent Zurczak added a comment - Fri, 23 Jul 2010 - 18:25:51 +0200

This is an issue with File#renameTo, which depends on the OS.

Show
Vincent Zurczak added a comment - Fri, 23 Jul 2010 - 18:25:51 +0200 This is an issue with File#renameTo, which depends on the OS.
Hide
Permalink
Vincent Zurczak added a comment - Fri, 23 Jul 2010 - 18:28:09 +0200

Commit #1726

I replaced the use of File#renameTo by a robust move method.
If File#renameTo fails, the file is copied before being deleted.

Since I cannot reproduce this bug, I will let this bug open until you test it and confirm this is solved.

Show
Vincent Zurczak added a comment - Fri, 23 Jul 2010 - 18:28:09 +0200 Commit #1726 I replaced the use of File#renameTo by a robust move method. If File#renameTo fails, the file is copied before being deleted. Since I cannot reproduce this bug, I will let this bug open until you test it and confirm this is solved.
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Jul 2010 - 16:52:33 +0200

Can you set the attribute 'Fix version/s'

Show
Christophe DENEUX added a comment - Thu, 29 Jul 2010 - 16:52:33 +0200 Can you set the attribute 'Fix version/s'
Hide
Permalink
Vincent Zurczak added a comment - Mon, 2 Aug 2010 - 12:55:57 +0200

The "fix version" attribute must be set when a bug is closed.

Show
Vincent Zurczak added a comment - Mon, 2 Aug 2010 - 12:55:57 +0200 The "fix version" attribute must be set when a bug is closed.

People

Dates

  • Created:
    Fri, 23 Jul 2010 - 09:47:14 +0200
    Updated:
    Tue, 24 Aug 2010 - 15:09:40 +0200
    Resolved:
    Fri, 23 Jul 2010 - 18:28:09 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.