[Apiman-user] PluginNotFoundException when adding a new plugin

Helio Frota 00hf11 at gmail.com
Mon May 23 10:19:30 EDT 2016


Working fine thanks a lot !

https://github.com/bucharest-gold/apiman-admin-client/issues/10


On Mon, May 23, 2016 at 10:58 AM, Eric Wittmann <eric.wittmann at redhat.com>
wrote:

> If you're just testing the node.js admin client, try this:
>
>          let plug = {
>              type: 'war',
>              version: '1.2.5.Final',
>              groupId: 'io.apiman.plugins',
>              artifactId: 'apiman-plugins-log-policy'
>          };
>
> The rest of the properties are not required.
>
> That should result in a successful response.
>
> -Eric
>
> On 5/23/2016 9:52 AM, Helio Frota wrote:
>
>> Hi,
>>
>>  --- No, no plugin created. ---
>>
>> Now it makes a lot of sense.
>>
>> Thanks again for the clarification !
>>
>> Wow - this also means development of nodejs-apiman-admin-client we got
>>
>>> Zero << issues from/with Apiman.
>>>>
>>> Congratulations and thanks to all the Apiman team for this ^ too.
>>
>>
>>
>>
>> On Mon, May 23, 2016 at 10:40 AM, Eric Wittmann
>> <eric.wittmann at redhat.com <mailto:eric.wittmann at redhat.com>> wrote:
>>
>>     Have you created a plugin already?  You must use maven to build and
>>     deploy your plugin so that apiman can find it.  The endpoint you
>>     mention is for installing a plugin, so you must provide the correct
>>     information.
>>
>>     Typically the value of "type" would be "war" and the value of
>>     "classifier" can simply be omitted.  The following properties are
>>     all directly related to their identically named maven properties:
>>
>>             groupId, artifactId, version, type, classifier
>>
>>     What apiman will attempt to do when you invoke this endpoint, is
>>     download the appropriate plugin file from maven (either by finding
>>     it locally in your maven .m2 directory or by downloading it from a
>>     configured remote maven repository).  The above information is
>>     needed to identify the proper maven artifact and download it.
>>
>>     -Eric
>>
>>
>>     On 5/20/2016 11:51 AM, Helio Frota wrote:
>>
>>         Hi ,
>>
>>         I'm trying to use the endpoint :
>>
>>         http://localhost:8080/apiman/plugins/ [ POST ]
>>
>>         ' Use this endpoint to add a plugin to apiman. '
>>
>>         Using this object representation:
>>
>>         let plug = {
>>             name: 'the-new-plugin',
>>             description: 'the description',
>>             type: 'plugs',
>>             version: '1.0.0.Final',
>>             groupId: 'org.myplugins',
>>             artifactId: 'superplugin',
>>             classifier: '1',
>>             upgrade: false
>>         };
>>
>>         And I'm getting this error :
>>
>>          type: 'PluginNotFoundException',
>>           errorCode: 12002,
>>           message: 'org.myplugins:superplugin:1.0.0.Final-1:plugs',
>>           moreInfoUrl: null,
>>           stacktrace:
>>
>> 'io.apiman.manager.api.rest.contract.exceptions.PluginNotFoundException:
>>           ...
>>
>>         Maybe I'm populating the object with wrong values ? [ e.g
>>         classifier ? ]
>>
>>         Thanks
>>
>>
>>
>>
>>         _______________________________________________
>>         Apiman-user mailing list
>>         Apiman-user at lists.jboss.org <mailto:Apiman-user at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>>
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160523/1f204e18/attachment-0001.html 


More information about the Apiman-user mailing list