Hi Vijitha,
On Tue, Jul 16, 2013 at 8:08 AM, Vijitha Kumara wrote:
> Had a chat with Lakmali about this.
>
> As of now this requires a manual publishing of the REST API, but since
> this is a feature of the registry itself it would be good to ship it
> published OOTB?
>
+1. AFAIK there will be
Had a chat with Lakmali about this.
As of now this requires a manual publishing of the REST API, but since this
is a feature of the registry itself it would be good to ship it published
OOTB?
As we are not letting the REST API to be accessed without going through
APIM component, the EnableAPIMana
Hi Vijitha,
On Sun, Jul 14, 2013 at 11:13 AM, Vijitha Kumara wrote:
> Hi All,
>
> What's the status of this now? Do we have a working use case to be
> reviewed? We might need to finalize & test within next few days.
>
We have committed changes to trunk and have completed basic testing. You
can
Hi All,
What's the status of this now? Do we have a working use case to be
reviewed? We might need to finalize & test within next few days.
Regards,
Vijitha.
On Thu, Jun 20, 2013 at 11:20 AM, Dinusha Senanayaka wrote:
> Hi Ragu,
>
> On Thu, Jun 20, 2013 at 10:52 AM, Sriragu Arudsothy wrote:
Hi Dinusha,
Good progress. I will use the in-built APIM to test the
Registry REST API.
1) Version support can be added. I will do that.
2) Since we wanted to create the users with user name and tenant id to
separate registry space belongs to the user based on the tenant and
username
Hi Ragu,
On Thu, Jun 20, 2013 at 10:52 AM, Sriragu Arudsothy wrote:
> Hi Lakmali and Dinusha,
>
>
>As you have been completed the tomcat valve, shall I use the tomcat
> valve ( kind of interceptor) to test the Registry REST API with the
> externally running API Manager instance ?
>
We ar
Hi Lakmali and Dinusha,
As you have been completed the tomcat valve, shall I use the tomcat
valve ( kind of interceptor) to test the Registry REST API with the
externally running API Manager instance ?
Thanks,
Ragu
On Tue, Jun 18, 2013 at 1:20 PM, Dinusha Senanayaka wrote:
>
>
> On
On Tue, Jun 18, 2013 at 12:59 PM, Sriragu Arudsothy wrote:
> Hai Dinusha,
>
> At the later part of your answer, you mentioned the how
> to send the request. Do we have a use case where "without API manager".
> AFAIR, It has been clearly said during the final discussion , request
Hai Dinusha,
At the later part of your answer, you mentioned the how
to send the request. Do we have a use case where "without API manager".
AFAIR, It has been clearly said during the final discussion , request will
be given inbuilt or external APIM. But you mention about without
Hi Ragu,
We have wrote a Tomcat Valve which will be act as interceptor for all
incoming requests. There was a need of using
Axis2ConfigurationContextObserver to get the throttling related properties,
which cannot be done through the CXF hander in GREG REST API. This tomcat
valve can be used not on
Hai Dinusha and Lakmali,
Please update this mail thread that
what have you done so far regarding the "Lightweight API manager
component".
1) Please let me know the strategy that you are using when integrate the
external API manager instance.
2) when an API ma
Hai Sanjeewa..!
We are having a strategic discussion that how to
include the API publisher/ store jag apps to other products. Therefore, I
will update this thread after the discussion...! As far as I understand,
there will be single interceptor which decides the processing
Hai Lakmali..!
Yes, the above link does not work...! I moved the
user token generation menu under the "Resources" menu in order to appear
for Greg. Therefore the existing doc won't work. Also these changes have
not yet been committed. I will give you , the locally built lat
On Mon, Jun 10, 2013 at 4:08 PM, Dinusha Senanayaka wrote:
> Hi All,
>
> This is what we are going to add from the APIM side.
>
> 1) We will be exposing current api manager handlers related
> functionalities as some common packages. So this bundle can be included
> into any of products to get API
14 matches
Mail list logo
