Re: [Apiman-user] Different API version-Contract Creation
Thanks Eric. APIMAN-1187<https://issues.jboss.org/browse/APIMAN-1187> has been
created
Best
Mohan
-----Original Message-----
From: Eric Wittmann [mailto:eric.wittmann@redhat.com]
Sent: Monday, June 13, 2016 12:11 PM
To: Mohan Joyappa <mjoyappa(a)EBSCO.COM>; apiman-user(a)lists.jboss.org
Subject: Re: [Apiman-user] Different API version-Contract Creation
If I understand correctly, then this is most likely a bug. Could you write up a JIRA
issue for this? Perhaps mark it as a Blocker if possible.
I will try to reproduce it asap.
In the meantime, you could use the alternate approach to finding APIs and creating
contracts. See the "Search for APIs to consume" link on the details page (in
the top box) for a given Client App:
http://imgur.com/Q70IIxJ
-Eric
On 6/10/2016 1:38 PM, Mohan Joyappa wrote:
Hi Eric,
I have following scenario. I have two version of same API. Version 1
of API is the base version and version 2 of API has some additional
changes to it (like some extra policy and what not). When I try to
create a contract for my clientApp, I get to select what version of
API I need to use as shown below
So if I select API version 1.0 and click on OK, contract is always
created with latest version of API no matter what other older version
of API you have.
Is this intentionally designed? If yes, the first step to choose a
particular API version while creating a contract is somewhat
misleading to me.
Best
Mohan Joyappa
_______________________________________________
Apiman-user mailing list
> Apiman-user@lists.jboss.org<mailto:Apiman-user@lists.jboss.orgAttachments:
- attachment.html (text/html — 6.7 KB)