[Paypal connector] The dependent component Geo does not exist anymore

[Paypal connector] The dependent component Geo does not exist anymore

  
Forge Component
(0)
Published on 2016-01-14 by Gonçalo Borrêga
0 votes
Published on 2016-01-14 by Gonçalo Borrêga

Hi!

The dependent component "Geo" does not exist anymore in the Forge.

Geo - https://www.outsystems.com/forge/439/ (HTTP 404 - not found)

Is this a temporary error (the component Geo will become available) or this component Geo was effectively removed and this component "Paypal connector" needs to be updated?

The non existence of the component Geo also impacts other components like "UPS connector".

--Tiago Bernardo

Hi Tiago,

I'm trying to investigate what happened because I tried myself and I was able to access the component. Can you please double check?

Either way, find the Geo.oap attached.

Vera

Hi Vera,

1) The link to the Forge component Geo still does not work (Geo - https://www.outsystems.com/forge/439/ (HTTP 404 - not found));

2) The application that you have supplied (Geo-4.1.0.oap) is not coherent: It has 1 extension (Geo.xif) has 2 espaces (Geo.oml, GeoServices.oml), but the 2 espaces have duplicate functionality (for example: the bootstrap of data, and all the logic in server actions), and GeoServices has dependencies of entities on an espace "GeoModel" which does no exist but that I believe is the "Geo" espace which probably was renamed...

--Tiago Bernardo


Vera Tiago wrote:

Hi Tiago,

I'm trying to investigate what happened because I tried myself and I was able to access the component. Can you please double check?

Either way, find the Geo.oap attached.

Vera



For others reading this thread:

By just removing the espace "GeoServices.oml" from the previously supplied "Geo-4.1.0.oap" file by Vera Tiago (just use for example the application 7-Zip to edit the file since the .oap is just a zip file), although there will occur some minor errors when publishing the application,

the application Geo will be correctly published.
--Tiago Bernardo

-edited: PS: For simplification I just attached the new .oap file without the espace GeoServices.oml.

Tiago Bernardo wrote:

Hi Vera,

1) The link to the Forge component Geo still does not work (Geo - https://www.outsystems.com/forge/439/ (HTTP 404 - not found));

2) The application that you have supplied (Geo-4.1.0.oap) is not coherent: It has 1 extension (Geo.xif) has 2 espaces (Geo.oml, GeoServices.oml), but the 2 espaces have duplicate functionality (for example: the bootstrap of data, and all the logic in server actions), and GeoServices has dependencies of entities on an espace "GeoModel" which does no exist but that I believe is the "Geo" espace which probably was renamed...

--Tiago Bernardo


Vera Tiago wrote:

Hi Tiago,

I'm trying to investigate what happened because I tried myself and I was able to access the component. Can you please double check?

Either way, find the Geo.oap attached.

Vera





Solution

Just to inform that the Geo component was restored by the OutSystems team in the same location: https://www.outsystems.com/forge/439/

--Tiago Bernardo

Solution