Petals Studio

Unable to export an EIP croquis when no network is available

Details

  • Type: Bug Bug
  • Status: New New
  • Priority: Blocker Blocker
  • Resolution: Unresolved
  • Affects Version/s: 1.3.4
  • Fix Version/s: None
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide

    Try to export an EIP croquis as Maven projects on a computer without network connection available. An error occurs: The network is unreachable.

    We should be able to export a croquis without network available.

    Note: A web-service is included in the EIP croquis, and it seems that the WSDL of this web-service is retrieved from the external endpoint when exporting. So if no network is available, an error occurs when retrieving the WSDL.

    Show
    Try to export an EIP croquis as Maven projects on a computer without network connection available. An error occurs: The network is unreachable. We should be able to export a croquis without network available. Note: A web-service is included in the EIP croquis, and it seems that the WSDL of this web-service is retrieved from the external endpoint when exporting. So if no network is available, an error occurs when retrieving the WSDL.
  • Environment:
    -
  1. SaveOrderService.wsdl
    (2 kB)
    Christophe DENEUX
    Tue, 19 Aug 2014 - 10:33:21 +0200
  2. TP4.peip
    (3 kB)
    Christophe DENEUX
    Tue, 19 Aug 2014 - 10:31:27 +0200
  3. WriteOrderService.wsdl
    (2 kB)
    Christophe DENEUX
    Tue, 19 Aug 2014 - 10:33:21 +0200

Activity

Christophe DENEUX made changes - Tue, 19 Aug 2014 - 10:14:43 +0200
Field Original Value New Value
Priority Blocker [ 1 ]
Description Try to export an EIP croquis as Maven projects on a computer without network connection available. An error occurs: The network is unreachable.

We should be able to export a croquis without network available.
Try to export an EIP croquis as Maven projects on a computer without network connection available. An error occurs: The network is unreachable.

We should be able to export a croquis without network available.

A web-service is included in the EIP croquis, and it seems that the WSDL of this web-service is retrieved from the external endpoint when exporting. So if no network is available, an error occurs when retrieving the WSDL.
Christophe DENEUX made changes - Tue, 19 Aug 2014 - 10:14:58 +0200
Description Try to export an EIP croquis as Maven projects on a computer without network connection available. An error occurs: The network is unreachable.

We should be able to export a croquis without network available.

A web-service is included in the EIP croquis, and it seems that the WSDL of this web-service is retrieved from the external endpoint when exporting. So if no network is available, an error occurs when retrieving the WSDL.
Try to export an EIP croquis as Maven projects on a computer without network connection available. An error occurs: The network is unreachable.

We should be able to export a croquis without network available.

Note: A web-service is included in the EIP croquis, and it seems that the WSDL of this web-service is retrieved from the external endpoint when exporting. So if no network is available, an error occurs when retrieving the WSDL.
Hide
Vincent Zurczak added a comment - Tue, 19 Aug 2014 - 10:18:49 +0200

Can you post the croquis file?
If the referenced WSDL is a remote URL, then it is normal you get an error. Generating the SU requires to import the WSDL.

Although the jbi.xml could reference a remote WSDL, this is considered as a bad practice by the studio.
So, no connection, no import.

Show
Vincent Zurczak added a comment - Tue, 19 Aug 2014 - 10:18:49 +0200 Can you post the croquis file? If the referenced WSDL is a remote URL, then it is normal you get an error. Generating the SU requires to import the WSDL. Although the jbi.xml could reference a remote WSDL, this is considered as a bad practice by the studio. So, no connection, no import.
Hide
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 10:31:28 +0200

The croquis for which the export fails

Show
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 10:31:28 +0200 The croquis for which the export fails
Christophe DENEUX made changes - Tue, 19 Aug 2014 - 10:31:28 +0200
Attachment TP4.peip [ 10770 ]
Hide
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 10:33:21 +0200

The WSDLs used by the Wire-Tap and the Routing-Slip

Show
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 10:33:21 +0200 The WSDLs used by the Wire-Tap and the Routing-Slip
Christophe DENEUX made changes - Tue, 19 Aug 2014 - 10:33:21 +0200
Attachment SaveOrderService.wsdl [ 10771 ]
Attachment WriteOrderService.wsdl [ 10772 ]
Hide
Vincent Zurczak added a comment - Tue, 19 Aug 2014 - 10:43:34 +0200

No remote WSDL file in the croquis.
Can you post the error log?

Show
Vincent Zurczak added a comment - Tue, 19 Aug 2014 - 10:43:34 +0200 No remote WSDL file in the croquis. Can you post the error log?
Hide
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 12:02:05 +0200

I have no error log.

I think it's due to the XSD import in the WSDL 'SaveOrderService.wsdl'

Show
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 12:02:05 +0200 I have no error log. I think it's due to the XSD import in the WSDL 'SaveOrderService.wsdl'
Hide
Vincent Zurczak added a comment - Tue, 19 Aug 2014 - 12:07:13 +0200

This is weird that there is no error log.
But you are right about the XML schema import. What happens if you type in this URL in your browser?

If it fails, and if bug there is, it is about the fact that there is no entry in the error logs.

Show
Vincent Zurczak added a comment - Tue, 19 Aug 2014 - 12:07:13 +0200 This is weird that there is no error log. But you are right about the XML schema import. What happens if you type in this URL in your browser? If it fails, and if bug there is, it is about the fact that there is no entry in the error logs.
Hide
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 19:49:56 +0200

The problem was coming from the WSDLs associated to the Wire-Tap and Routing-Slip that included an XSD import. Removing the imports solves the problem.

Can you add a clearer error message as "Unable to parse the WSDL xxxx.wsdl" ?

Show
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 19:49:56 +0200 The problem was coming from the WSDLs associated to the Wire-Tap and Routing-Slip that included an XSD import. Removing the imports solves the problem. Can you add a clearer error message as "Unable to parse the WSDL xxxx.wsdl" ?

People

Dates

  • Created:
    Tue, 19 Aug 2014 - 09:27:00 +0200
    Updated:
    Tue, 19 Aug 2014 - 19:49:56 +0200