29
29
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
30
30
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
31
31
<![endif]-->
32
-
32
+
33
33
< script src ="http://www.apiman.io/latest/resources/jquery-1.11.1/js/jquery.min.js "> </ script >
34
34
< script src ="http://www.apiman.io/latest/resources/bootstrap-3.3.0/js/bootstrap.min.js "> </ script >
35
35
< script id ="dsq-count-scr " src ="//apiman.disqus.com/count.js " async > </ script >
78
78
< li class ="menu-item ">
79
79
< a href ="https://issues.jboss.org/browse/APIMAN "> Report a Bug</ a >
80
80
</ li >
81
- < li class ="menu-item ">
82
- < a href ="http://www.apiman.io/latest/chat.html "> Chat on IRC</ a >
83
- </ li >
84
81
< li class ="menu-item ">
85
82
< a href ="https://twitter.com/apiman_io " rel ="nofollow " target ="_blank "> Twitter Feed</ a >
86
83
</ li >
87
- < li class ="menu-item ">
88
- < a href ="https://lists.jboss.org/mailman/listinfo/apiman-user " rel ="nofollow " target ="_blank "> Mailing List</ a >
89
- </ li >
90
84
< li class ="divider "> </ li >
91
85
< li class ="menu-item ">
92
86
< a href ="http://www.apiman.io/latest/contributors.html "> Contributors List</ a >
@@ -596,8 +590,8 @@ <h1><a href="/blog/apiman/3scale/2016/08/19/3scale-apiman-part2.html">3scale and
596
590
< span style ="color: #243446; margin-left: 15px; font-size: 13px "> < i class ="fa fa-user "> </ i > Eric Wittmann</ span >
597
591
< span style ="color: #243446; margin-left: 15px; font-size: 13px "> < i class ="fa fa-tags "> </ i > apiman and 3scale</ span >
598
592
< div class ="excerpt " style ="font-size: 14px; margin-top: 8px; line-height: 20px ">
599
- < p > It’s been almost two months since Red Hat announced it was acquiring 3scale Technologies and turning
600
- the 3scale API Management solution into a Red Hat supported product. In that time, we’ve been trying
593
+ < p > It’s been almost two months since Red Hat announced it was acquiring 3scale Technologies and turning
594
+ the 3scale API Management solution into a Red Hat supported product. In that time, we’ve been trying
601
595
to figure out some stuff for the apiman community. Here some of the things we wanted to suss out:</ p >
602
596
603
597
< ul >
@@ -606,7 +600,7 @@ <h1><a href="/blog/apiman/3scale/2016/08/19/3scale-apiman-part2.html">3scale and
606
600
< li > How can existing apiman users transition to a Red Hat supported API Management solution.</ li >
607
601
</ ul >
608
602
609
- < p > It doesn’t sound like much, but it actually really is. We’ve made some preliminary decisions, and
603
+ < p > It doesn’t sound like much, but it actually really is. We’ve made some preliminary decisions, and
610
604
because we want to be as transparent and upfront as possible, read on to find out what they are!</ p >
611
605
612
606
@@ -647,7 +641,7 @@ <h1><a href="/blog/apiman/release/2016/04/24/release-1.2.4.html">Version 1.2.4.F
647
641
< span style ="color: #243446; margin-left: 15px; font-size: 13px "> < i class ="fa fa-user "> </ i > Eric Wittmann</ span >
648
642
< span style ="color: #243446; margin-left: 15px; font-size: 13px "> < i class ="fa fa-tags "> </ i > apiman and release</ span >
649
643
< div class ="excerpt " style ="font-size: 14px; margin-top: 8px; line-height: 20px ">
650
- < p > Greetings, earthlings! On Friday of last week we released the < em > absolute best</ em > version
644
+ < p > Greetings, earthlings! On Friday of last week we released the < em > absolute best</ em > version
651
645
of apiman ever! This release has a fair number of bugs fixed, as well as a few new
652
646
things. Read on for the details!</ p >
653
647
@@ -725,7 +719,7 @@ <h1><a href="/blog/apiman/release/2016/03/24/release-1.2.3.html">Version 1.2.3.F
725
719
< div class ="excerpt " style ="font-size: 14px; margin-top: 8px; line-height: 20px ">
726
720
< p > Greetings, earthlings! Yesterday we released the < em > best</ em > version of apiman yet,
727
721
and I’m not just saying that because the version number (1.2.3.Final) is awesome.
728
- This release has a bunch of bug fixes in it, as well as a few targeted new
722
+ This release has a bunch of bug fixes in it, as well as a few targeted new
729
723
features. Read on for more details!</ p >
730
724
731
725
@@ -768,7 +762,7 @@ <h1><a href="/blog/apiman/1.2.x/gateway/jdbc/registry/2016/03/09/jdbc-registry.h
768
762
< div class ="excerpt " style ="font-size: 14px; margin-top: 8px; line-height: 20px ">
769
763
< p > One of the strongest features of apiman, in general, is its excellent
770
764
extensibility. Not only is it easy to add new policies, for example,
771
- but many of its core components are also pluggable. This includes,
765
+ but many of its core components are also pluggable. This includes,
772
766
for example, the registry used by the API Gateway to store configuration
773
767
information published to it by the manager. This blog post will detail
774
768
a new JDBC based implementation of that registry, explaining how you can
@@ -790,7 +784,7 @@ <h1><a href="/blog/apiman/1.2.x/gateway/2016/02/24/reregistering.html">Re-Regist
790
784
< span style ="color: #243446; margin-left: 15px; font-size: 13px "> < i class ="fa fa-user "> </ i > Eric Wittmann</ span >
791
785
< span style ="color: #243446; margin-left: 15px; font-size: 13px "> < i class ="fa fa-tags "> </ i > apiman, 1.2.x, and gateway</ span >
792
786
< div class ="excerpt " style ="font-size: 14px; margin-top: 8px; line-height: 20px ">
793
- < p > In a recent blog post I explained why APIs used to be completely frozen
787
+ < p > In a recent blog post I explained why APIs used to be completely frozen
794
788
once they were published, and how we have loosened that restriction for
795
789
Public APIs. Similarly, we did not allow Client Apps to be changed and
796
790
then re-registered. This was never a good decision, since the Client App
@@ -815,11 +809,11 @@ <h1><a href="/blog/apiman/1.2.x/gateway/2016/02/24/republishing.html">Re-Publish
815
809
< p > An early design decision we made in apiman was to not allow APIs to be
816
810
re-published to the Gateway. The reasoning was that Client Apps may have
817
811
established Contracts with the API, and thus have agreed to specific terms
818
- and conditions (whether implicit or explicit). Therefore, we shouldn’t
812
+ and conditions (whether implicit or explicit). Therefore, we shouldn’t
819
813
allow the API provider to modify those terms and re-publish the API, as it
820
814
may violate the agreement.</ p >
821
815
822
- < p > However, we later added the concept of a Public API, which allows any
816
+ < p > However, we later added the concept of a Public API, which allows any
823
817
client to invoke it without first creating a Contract. It is clear that
824
818
API providers should be able to re-publish a Public API (presumably after
825
819
changing the API’s configuration).</ p >
0 commit comments