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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user