Hi all,
I have tried the same scenario which is "Creating a Smooks configuration
artifact" by referring the documentation [1] and I get exactly the same
error [2] as mentioned.
Any input on this is highly appreciated.
[1].
Hi Nuwan,
AFAIU if the requirement is to store the images, another approach would be
to store them directly in file system something similar we did for file
transfer feature. You can have some file sync mechanism or FTP server to
support clustering.
Thanks,
Waruna
On Tue, Jan 16, 2018 at 1:10
[Adding NipuniC]
Sewmini Jayaweera
*Software Engineer - Support Team*
Mobile: +94 (0) 773 381 250
sewm...@wso2.com
On Wed, Dec 14, 2016 at 6:56 PM, Schürpf, Thomas wrote:
> We are using the WSO2 ESB Tooling 5.0 and installed it as described at
>
Hi IAM Team,
The UserStoreConfigAdminService has been documented in [1]. I have also
added a tip under the addUserStore operation that links off to the relevant
docs for a full list of properties including optional properties for each
user store type.
However, the sample request given under the
On Tue, Jan 16, 2018 at 1:10 PM, Ruwan Yatawara wrote:
> As to my knowledge, image analysis is not supported, and won't be
> supported in the near future.
>
> @Mohan, @Ramindu, please correct me if I am wrong.
>
In that case, it is better to go with the BinaryStream approach.
Hi Chathurika,
I hope you were trying to add access control with restricted by roles and
not the visibility. Can you please try the below parameters and see?
"accessControl": "RESTRICTED",
"accessControlRoles": [
"rolename"
],
Thanks,
Kavitha
On Tue, Jan 16, 2018 at 2:59 PM, Sanjeewa Malalgoda
Previously there were a few issues with using JsonStreamBuilder and
JsonStreamFormatter
in APIM, hence by default APIM used JsonBuilder and JsonFormatter (up to
the release 2.1.0). I think we can move to JsonStreamBuilder and
JsonStreamFormatter
in the 2.2.0 release.
On Tue, Jan 9, 2018 at 8:59
Can we address this and fix it for 2.2.0?
Thanks,
sanjeewa.
On Fri, Jan 12, 2018 at 4:23 PM, Kavitha Subramaniyam
wrote:
> Thanks Rajith to pointing out!
>
> @Harsha, please find the github issue created on [1]
> [1] https://github.com/wso2/product-apim/issues/2388
>
>
Hi Kavitha
Thank you. It worked. I have reported a doc issue as this information
should be included to documentation
[1] https://github.com/wso2/product-apim/issues/2431
Best Regards
Erandi
On Tue, Jan 16, 2018 at 3:05 PM, Kavitha Subramaniyam
wrote:
> Hi Chathurika,
>
> I
Hi Nadeeshaan
Very grateful for your help
The error I reported was obtained from the log file. It is the only one found.
TID: [-1234] [] [2017-12-21 17:15:38,305] ERROR
{org.apache.synapse.transport.passthru.util.RelayUtils} - Error while building
Passthrough stream
Hi,
Tried to explain little more.I have to append a random number to "too many ids"
present in my request.
Actual request consists of thousands of lines and there are many ids in it.
some ids are within array , some are direct elements.sample input : { "id" :
"1", { "id":"2" }}
I
In this document[1] we have added sample request to create API. There we
have visibility and visible roles attributes.
"visibility": "PUBLIC", "visibleRoles": [], "visibleTenants": [],
[1]
https://docs.wso2.com/display/AM210/apidocs/publisher/#!/operations#APICollection#apisPost
Thanks,
Hi
I am trying to creating an api using the rest interfaces to have access
control for selected roles. In Publisher UI i can set "Restricted to Roles"
as Access Control mechanism. Referred [1] to find the relevant parameter to
set the above through the REST APIs but couldn't find the reference.
Hi all,
[+]Anusha
Anusha has implemented a video processing solution. But it is not
integrated to the SP. Anusha, can you please explain how you stored and
processed the data in your solution? Maybe IoT team can get an idea.
Best Regards,
Ramindu.
On Tue, Jan 16, 2018 at 4:03 AM, Nuwan
Hi All,
Thanks for the feedback.
Based on what everyone has said, I thought it was best to go ahead with
using the *BinaryStream*.
Will update this thread further along the way! :)
On Tue, Jan 16, 2018 at 2:07 PM, Madawa Soysa wrote:
>
>
> On Tue, Jan 16, 2018 at 1:10 PM,
Hi, Enrich mediator inside for-each not working properly :
Please consider what I have tried so far and Please Guide.
I have to add(suffix) a random number, to the values present in below tags in
input request xml. 1) _JsonReader_PS_id2) _JsonReader_PS_ref
Input xml, Current Output xml,
Hi Manuri/Heshitha,
Thanks for the input as you mentioned when html content is directly added
to the popup dialog body without encoding it as text it works fine.
Thanks,
On Wed, Jan 17, 2018 at 10:27 AM, Heshitha Hettihewa
wrote:
> Hi Malaka,
>
> It seems the message(Popup
[UPDATED]
Hi all,
I have updated the repo with by removing the SSOAgentAppListener class and
having SSO properties defined in an XML block inside web.config and wiring
it. Thus, there isn't any .settings file in the web application's
directory.
All the SSO related settings will have to be defined
[1]https://docs.wso2.com/display/ADMIN44x/Enabling+Java+Security+Manager
On Tue, Jan 16, 2018 at 2:53 PM, Sanjeewa Malalgoda
wrote:
> I haven't checked these steps recently with latest API Manager packs. I
> think we will need to do some changes to policy and see the impact
Hi Nuwan.
Even though I did video processing, In the end, the processing was done by
per image. In my case, I resized the images into a 480p or 720p(most of the
time videos was 1080p) and after the processing was done, saved them into
the main storage in binary format. So you also can check the
Hi Heshitha,
Thanks for the prompt response. I'll try out the mentioned resolutions and
let know if any other problem occurs.
Thanks,
Nipuni
On Tue, Jan 16, 2018 at 11:12 PM, Heshitha Hettihewa
wrote:
> Hi Thomas/Nipuni,
>
> Thanks for pointing out. It seems Smooks
Hi all,
We are currently working on improving the conditional authentication
support using JavaScript feature [1] to be able to handle authentication
conditions based on HTTP context.
Following is the approach taken to achieve this requirement.
In order to store the HTTP request and response I
Thanks for the response Vijitha.
Thanks
Godwin
On Wed, Jan 10, 2018 at 5:44 PM, Vijitha Ekanayake
wrote:
> Hi Godwin,
>
> I could get the failed message list by providing Lucene query[1] in the
> search box. It seems we need to search for the fault count internally to
>
Hi Team,
Verifying details: Do we need to change the explanation given in docs?If
yes, what should the messaging be?
Thanks & Regards
Shavindri Dissanayake
Senior Technical Writer
WSO2 Inc.
lean.enterprise.middleware
On Mon, Jan 15, 2018 at 11:00 AM, Shakila Sasikaran
wrote:
Hi Marcos,
This is what I see, you get the content type as text/xml and when you try
to build this particular payload it is invalid xml content. If you take a
look at the wirelogs, you will be able to find that the content type is set
to text/xml before the below payload.
Hi,
Apologies I am raising the same issue again but this time with improved subject
and content.Please consider what I have tried so far and Please Guide.
I have to add(suffix) a random number, to the values present in below tags in
input request xml. 1) _JsonReader_PS_id2) _JsonReader_PS_ref
Select Error Codes section does not work properly when configuring advance
properties of end points.
When Select Error Codes section is selected while trying to configure
suspend or timeout error codes in Address Endpoints it just pop up a html
code rather than showing the actual error codes as
Apart from the above, "triggerPostRevokeListeners" method invocation is
happening inside the loop sending the whole "AccessTokenDO" always [1].
So if the "AccessTokenDO" set has "n" number of objects,
"triggerPostRevokeListeners" method invocation is happening "n" times and
in each time, an array
Hi Chiranga,
On Wed, Jan 17, 2018 at 1:22 AM, Chiranga Alwis wrote:
> Hi all,
>
> when analyzing the existing PCF BOSH implementations [1] [2], I
> encountered a package defined named 'common'. The rationale behind the
> existence of this package is not clear to me.
>
The
I haven't checked these steps recently with latest API Manager packs. I
think we will need to do some changes to policy and see the impact of that.
If this[1] doc do not work lets create document improvement request and see
do we have any gap in official document. The blog post was bit old but
Hi Thomas/Nipuni,
Thanks for pointing out. It seems Smooks libraries are not correctly packed
with the developer studio distribution. I've added smooks libs to the
org.wso2.developerstudio.eclipse.esb.libraries project build path with
this[1] PR. This change will be released with the next
Hi all,
when analyzing the existing PCF BOSH implementations [1] [2], I encountered
a package defined named 'common'. The rationale behind the existence of
this package is not clear to me.
As you may know, BOSH packages provide the required information to prepare
the binaries and
32 matches
Mail list logo