This is an issue of the Mashup portal

Currently, If you want to create an offering containing one or more application mashup components (widget, operators or mashups) you need to comply with the following rules:

• The store currently doesn't allow to associate metadata with resources and Wirecloud needs the component id to know if the component is already installed or not. So you need to uploaded the resource using the following file name pattern: <vendor>_<name>_<version>.wgt
• Use one of the following content-types: application/x-widget+mashable-application-component, application/x-operator+mashable-application-component or application/x-mashup+mashable-application-component

Currently, the best way for comply with these rules is by uploading resources from Wirecloud (using the publish button). Anyway, we know this has to be fixed, by adding new features to the Store so we don't depend on the name of the file and by improving documentation.

Hi,

In your email you pointed to three rules you must follow in order to upload a resource successfully, so we will try to explain the issue rule by rule, and 6 screenshots (named from 1 to 6) has been uploaded to try to explain better.

• You cannot use an URL for creating the resource

We found we can use it: we created a resource using a URL, then we attached the resource to a new offering. After that we publish temporarily the offering inside the store, we logged in with another account and finally we downloaded the resource. No problem with that. You can see it step by step in the attached pictures 1 to 6.

If the platform is not intended to allow this behavior, just as an recommendation, we will suggest to hide the URL option in the resource upload form.

• The store currently doesn't allow to associate metadata with resources and Wirecloud needs the component id to know if the component is already installed or not. So you need to uploaded the resource using the following file name pattern: <vendor><name><version>.wgt

Maybe this is the reason that produced the error we reported at the beginning of this discussion. We think that, until the moment you add your new functionality, a control should be implemented in order to avoid uploading widgets that doesn't match with the refered pattern. That would be easy to do, as well as you already have the vendor's name (account) and you, as a user, must insert name and version in the resource upload form.

• Use one of the following content-types: application/x-widget+mashable-
  application-component, application/x-operator+mashable-application-component or application/x-mashup+mashable-application-component

In fact that field in the form produced us a bit of confusion while we uploaded our widgets. It would be great, even better than the documentation improvement, if you decide to change that field for a selection one that contains the allowed content-types.

Best regards,

Hi Pablo,

sorry for the misunderstanding, I created the comment through the jira user interface and then I edited it, so probably you have only read the original comment. Indeed, you CAN use an URL for creating a resource, so the first point doesn't apply .

The other two points require changes in the form for uploading resources in the Store, so I'm going to reassign this ticket to Fran.

Best regards,
Álvaro

Hi Pablo,

Currently, a resource can be any digital asset, not only widgets or mashups, this is the reason why there is not explicit support for widgets or mashups in the resource creation form. However, we realised that this could be difficult and confusing, for this reason we have included in our roadmap the development of a plugin-based approach in order to allow the definition of explicit types of resources. In this way, It would be possible to deal with Wirecloud restrictions without the need of forcing the provider to set specific names or learn the content types.

Best regards,
Francisco

This problem has been solved by the creation of a plugin for WStore for the creation of Wirecloud resources, using this plugin it is possible to upload a widget to WStore using an URL with any format and a file with any name, since the information of the widget, mashup or operator is extracted from the WGT file. Moreover, the media type is automatically filled.