Hi,
We have some jaggery APIs protected with basic auth as follows [3]. But
when tenant users try to access these APIs it gives following error [1] to
client and warn [2] in backend. In normal web apps, we could enable saas
mode using web.xml. Do we have to do something similar here ?
[1] You do
Hi API-M team,
I have a question regarding starting the nodes with
-Dprofile=[profile_name] in a distributed setup. Let's say I have a setup
as explained below.
Setup:-
Publisher/Store
Gateway Manager
Gateway Worker1
Gateway Worker2
Key Manager1
Key Manager2
DB:- DB of your choice
LB:- Single Ng
AFAIK at the moment the publisher and store profiles are identical. This is
because we do not yet have control of webapp deployment through server
profiles. So both webapps would work in either profile or even without any
profile (default mode).
On Sat, Dec 19, 2015 at 5:22 PM, Pubudu Priyashan w
Hi Kathees,
Is there a specific reason to use the legacy-encoding prefix here in your
case? Have you tried without the legacy-encoding prefix?
Can you try the following with legacy prefix,
Regards
Kevin
On Fri, Dec 18, 2015 at 8:56 PM, Malaka Silva wrote:
> Hi Kathees,
>
>
Hi,
I created projects using the available archetypes in staging repository and
built and installed via dropins and osgi console and tested the expected
functionality with the kernel 5.0.0 RC2 pack.
[x] Stable - go ahead and release.
Thank you.
On Fri, Dec 18, 2015 at 5:15 PM, Kishanthan Thanga
Hi,
I have just try to execute the carbon-ml sample[1] .
I am getting into error again and again while trying mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WSO2 Carbon - ML Model Usage Sam
Hi All,
I tested following functionalities
* Workflow
Basic operations with embeded BPS
Same operations with external BPS
* XACML
Policy creation
Policy Publish
Try out request
Policy deployment in file
Policy Cache
Decision Cache
So here is my vote.
[x] -Stable - go ahead and release
thanks,
I've tested, the following features
1. Logging framework
2. Transport Management
3. Jar to bundle conversion
4. Dropins bundle deployment
[x] Stable - go ahead and release
Regards,
Aruna
On Sat, Dec 19, 2015 at 11:50 PM, Manuri Amaya Perera
wrote:
> Hi,
>
> I created projects using the availa
Hi,
I have use wso2 ML 1.0.1 to create the model. Now i need to build a java
client to read the model in my project.
I have try to execute java client sample which is provided by carbon-ml git
repo of wso2.
https://github.com/wso2/carbon-ml/tree/master/samples/model-usage
The project is build su
Thanks for reporting. Let us check.
On Sun, Dec 20, 2015 at 11:09 AM, NIFRAS ISMAIL
wrote:
> Hi,
>
> I have use wso2 ML 1.0.1 to create the model. Now i need to build a java
> client to read the model in my project.
>
> I have try to execute java client sample which is provided by carbon-ml
> gi
Hi,
I tried to test ML predict mediator with ESB. Unable install ML features in
ESB 4.9.0 due to Carbon Kernel version incompatibility (ML 1.1.0 RC3 has
4.4.3 and ESB latest released version 4.9.0 has 4.4.1). Voting down due to
this.
[x] Broken - do not release
Best regards.
On Sat, Dec 19, 201
Hi all,
I have tested product-gw's basic functionality with this release candidate.
No issues found.
[x] Stable - go ahead and release
Regards
Senduran
On Sun, Dec 20, 2015 at 10:01 AM, Aruna Karunarathna wrote:
> I've tested, the following features
>
> 1. Logging framework
> 2. Transport Man
Hi,
I tested the following aspects:
- jar-to-OSGi-bundle converter
- converted OSGi bundles in dropins folder being successfully deployed
No issues discovered.
[x] Stable - go ahead and release.
On Sun, Dec 20, 2015 at 11:27 AM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:
> Hi all,
Hi all,
I have tested the launcher framework (loading launcher configurations from
launcher.properties) with logging. No issues found except[1] which is
already reported and will be fixed in 5.1.0.
[1] https://wso2.org/jira/browse/CARBON-15745
[x] Stable - go ahead and release
Thanks,
Nipuni
O
14 matches
Mail list logo