Hi Keethika,
Please use the http endpoint to resolve this issue.
call
* endpoint*
* http method=post
uri-template=https://api.stripe.com/v1/charges/{uri.var.chargeId}/refunds
https://api.stripe.com/v1/charges/%7Buri.var.chargeId%7D/refunds/http*
*/endpoint*
Hi Marcin,
Seems like the latest changes are not merged in the given git repo . Can
you please try to build from [3].
[3] https://github.com/wso2-dev/product-is
On Wed, Dec 10, 2014 at 3:04 PM, Marcin Krystek mkrys...@man.poznan.pl
wrote:
Hi Hasintha,
Thank you for the quick response.
I
Thank you Vanji, I tried as you suggested. Now I am able to get the correct
response.
On Thu, Dec 11, 2014 at 1:32 PM, Vanjikumaran Sivajothy va...@wso2.com
wrote:
Hi Keethika,
Please use the http endpoint to resolve this issue.
call
* endpoint*
* http
Hi Prabath,
Do we needs to include following jars for the coverage in Storage Server? I
think DSS has tests on these components. We haven't wrote specific tests to
check these components functionality.
org.wso2.carbon.ndatasource.common_
org.wso2.carbon.ndatasource.core_
Hi,
was able to resolve the issue. Thanks Nirmal, Nuwan and Asanka for the
support.
On Thu, Dec 11, 2014 at 10:35 AM, Udara Liyanage ud...@wso2.com wrote:
Hi Nirmal,
Error disappeared when added to tenant-axis2.xml. However UI giving some
errors
HTTP method GET is not supported by this
The ndatasource component is actually part of the Kernel, specific products
should not add them IMO for checking code coverage.
Cheers,
Anjana.
On Thu, Dec 11, 2014 at 3:10 PM, Harsha Kumara hars...@wso2.com wrote:
Hi Prabath,
Do we needs to include following jars for the coverage in Storage
Hi,
Should n't this be added to the file by kernel?
On Thu, Dec 11, 2014 at 3:12 PM, Udara Liyanage ud...@wso2.com wrote:
Hi,
was able to resolve the issue. Thanks Nirmal, Nuwan and Asanka for the
support.
On Thu, Dec 11, 2014 at 10:35 AM, Udara Liyanage ud...@wso2.com wrote:
Hi
Hi Harsha,
On Thu, Dec 11, 2014 at 3:10 PM, Harsha Kumara hars...@wso2.com wrote:
Hi Prabath,
Do we needs to include following jars for the coverage in Storage Server?
I think DSS has tests on these components. We haven't wrote specific tests
to check these components functionality.
Hi Udara,
Can you try with the configuration file available on [1].
[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0006/distribution/kernel/carbon-home/repository/conf/axis2/tenant-axis2.xml
*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
I'm doing ZOHO-Invoice ESB Connector.When i send request to end points
with the optional parameter *description* to the back end,It returns the
error code *505 Http Version Not Supported. *
If the description parameter sent without any spaces I am able to get the
correct response. The only
No,Only through the ESB.
On Wed, Dec 10, 2014 at 10:38 PM, Malaka Silva mal...@wso2.com wrote:
Are you getting the same error, if you directly invoke the api via a rest
client?
On Wed, Dec 10, 2014 at 7:08 PM, Sriashalya Srivathsan asha...@wso2.com
wrote:
I'm doing ZOHO-Invoice ESB
AFAIK, we don't support registering multiple ACS urls.. But IdP honour to
the ACS in the authentication request, if the request is signed.
On Thu, Dec 11, 2014 at 12:51 PM, Dinusha Senanayaka dinu...@wso2.com
wrote:
Hi,
Requirement is, in App Manager, synapse gateway act as the assertion
Are you getting the same error, if you directly invoke the api via a rest
client?
On Wed, Dec 10, 2014 at 7:08 PM, Sriashalya Srivathsan asha...@wso2.com
wrote:
I'm doing ZOHO-Invoice ESB Connector.When i send request to end points
with the optional parameter *description* to the back end,It
Do we have any test cases that we deploy web apps during integration test.
Can you shed some light please.
On Thu, Dec 11, 2014 at 1:20 PM, Irham Iqbal iq...@wso2.com wrote:
Hi Vijitha,
Did you try this manually ?
I mean deploy your web application to a tomcat manually.
Thanks,
Iqbal
Hi,
I have tested your use case[1] with 4.9.0 M3 pack with url encoding and it
worked. This is not working in 4.8.1 due to a bug [2] in ESB on handling
201 response with payload.
You can find the M3 pack in [2]
Best Regards,
Vanji
[1]
api xmlns=http://ws.apache.org/ns/synapse; name=strip
Yes we have,
This[1] test case is for deploy a web application in AS.
Using this code[2] you can see how we start,stop and restart carbon servers.
[1]
Hi
Please refer the documentation[1] for how to deploy a web application on
the tomcat server which can be started with test framework. You can follow
sample test case from[2]
[1]
https://docs.wso2.com/display/TA430/Using+Embedded+Tomcat+Server+as+a+JAX-RS+Backend+for+REST+Testing
[2]
Hi,
I need to add the base64 encoding attachment to parent sObject in
Salesforce. I used the following payload. Could you please suggest a way?
We use the Salesforce partner WSDL.
payloadFactory
format
soapenv:Envelope xmlns:soapenv=
Hi,
Thanks, I'll try this and get back to you.
On Thu, Dec 11, 2014 at 6:17 PM, Nuwan Wimalasekara nuw...@wso2.com wrote:
Hi
Please refer the documentation[1] for how to deploy a web application on
the tomcat server which can be started with test framework. You can follow
sample test case
Hi CarbonTeam,
Looks like the method is removed from the new carbon-deployment module [1].
What is the alternative for this ?
[1]
Hi Jeewantha
It is not removed, *isCAppArtifact* is a newly added property to
service-mgt component. It will be available once it is merged to
carbon-deployment repo [1]
If you are referring to this ESB integration [2] please comment out until
that pull request is merged
[1]
Hi Marcin,
Also I believe the reason for the compilation failure is axis2 and axiom
snapshots have been removed from the repositories. You can change the axis2
and axiom versions in the product pom file as follows instead of SNAPSHOT
versions and try the build too.
I am implementing the slideshare Connector using slideshare API.
I have to set this to the SHA1 hash of the concatenation of the shared
secret and the timestamp (ts). i.e. SHA1 (sharedsecret + timestamp).
package org.wso2.carbon.connector;
import java.math.BigInteger;
import
On you code it seem you are using the MD5 to hash. However expected hashing
mechanism is SH-1 according to doc.
Hence, please try with MessageDigest md =
MessageDigest.getInstance(SHA-1);
MessageDigest md = MessageDigest.getInstance(MD5);
On Thu, Dec 11, 2014 at 9:21 PM, Vanii Thiyagarajah
thanks. i changed that MessageDigest md =
MessageDigest.getInstance(SHA-1). it's working now.
On Thu, Dec 11, 2014 at 9:25 PM, Vanjikumaran Sivajothy va...@wso2.com
wrote:
On you code it seem you are using the MD5 to hash. However expected
hashing mechanism is SH-1 according to doc.
Hence,
Hi Manoj,
Issue is not visible with the config file you have provided. Thanks.
On Thu, Dec 11, 2014 at 3:25 PM, Manoj Kumara ma...@wso2.com wrote:
Hi Udara,
Can you try with the configuration file available on [1].
[1]
Hi Udara,
The issue might be the configuration files coming from kernel patches not
being applied in the product.
Regards
Manoj
*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188
On Thu, Dec 11, 2014 at 9:51 PM, Udara Liyanage
Hi Pubudu,
Seems like the PR is to release-4.3.0 branch. Could you resent to master
branch pls ?.
thanks,
On Thu, Dec 11, 2014 at 7:15 PM, Pubudu Dissanayake pubu...@wso2.com
wrote:
Hi Jeewantha
It is not removed, *isCAppArtifact* is a newly added property to
service-mgt component. It will
Hi All,
In JWT token generator [1] use low level JWT building and signing process
which makes bit difficult to validate signature in client side. But in [2]
we use nimbus [3] to generate and sign OpenID connect ID token. Shall we
change JWT generator in [1] to use nimbus library ?
Nimbus provides
Hi Gayan
FYI
I was able to validate the APIM JWT signature with java.security.* classes.
Thanks
On Thu, Dec 11, 2014 at 11:48 PM, Gayan Gunawardana ga...@wso2.com wrote:
Hi All,
In JWT token generator [1] use low level JWT building and signing process
which makes bit difficult to validate
Hi all,
I am implementing the new feature for the Identity server existing
component SAML SSO configuration that is we can add the service provider
and identity provider through uploading metadata configuration file(.xml)
rather than interacting with existing method of adding service
Hi Gayan,
+1.
Using nimbuz is a good approach. It provides better flexibility than
hardcoding the kwt token format.
Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 11, 2014 11:49 PM, Gayan Gunawardana ga...@wso2.com wrote:
Hi All,
In JWT token generator [1] use low
Hi
+1 to use nimbus.
We have created a orbit bundle for nimbus. Please use that if you are using
nimbus.
@Gayan : I think we might need to change those identity components also to
use the orbit bundle.
Thanks Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile :
Hi,
As I remember nimbuz jar is embedded while building the identity component.
+1 using orbit bundle rather than embedding nimbuz jar.
Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 12, 2014 12:20 AM, Danushka Fernando danush...@wso2.com wrote:
Hi
+1 to use nimbus.
Hi Kathees,
Every object is salesforce is treated as a sobject. (Including Attachment)
Fields are listed in [1]. You need to create and send a payload similar to
[2]
Since there is already connector with create method, Just debug and check
the request send to api.
[1]
Hi All,
Thanks all for feedback. We can plan identity components for next Identity
Server release with orbit bundle rather than embedding nimbuz jar.
Thanks,
Gayan
On Fri, Dec 12, 2014 at 12:23 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
As I remember nimbuz jar is embedded while building
Hi,
This problem was discussed here [1].
[1] [Dev] chunk 05 packs 05/12/2013
On Thu, Dec 11, 2014 at 10:41 PM, Manoj Kumara ma...@wso2.com wrote:
Hi Udara,
The issue might be the configuration files coming from kernel patches not
being applied in the product.
Yes this issue occurred
We are good since we are only hosting those connectors with 4.9.0
On Thu, Dec 11, 2014 at 5:50 PM, Vanjikumaran Sivajothy va...@wso2.com
wrote:
Hi,
I have tested your use case[1] with 4.9.0 M3 pack with url encoding and it
worked. This is not working in 4.8.1 due to a bug [2] in ESB on
+1
On Friday, December 12, 2014, Malaka Silva mal...@wso2.com wrote:
We are good since we are only hosting those connectors with 4.9.0
On Thu, Dec 11, 2014 at 5:50 PM, Vanjikumaran Sivajothy va...@wso2.com
javascript:_e(%7B%7D,'cvml','va...@wso2.com'); wrote:
Hi,
I have tested your use
Did you manage to resolve this?
On Thu, Dec 11, 2014 at 6:24 PM, Vijitha Ekanayake vijit...@wso2.com
wrote:
Hi,
Thanks, I'll try this and get back to you.
On Thu, Dec 11, 2014 at 6:17 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi
Please refer the documentation[1] for how to deploy a
Hi,
Is there a way to set a connector to a TomcatServerManager instance which
is provided by automation? since i need to enable ssl.
On Thu, Dec 11, 2014 at 6:24 PM, Vijitha Ekanayake vijit...@wso2.com
wrote:
Hi,
Thanks, I'll try this and get back to you.
On Thu, Dec 11, 2014 at 6:17
Guys, we need this today before 4.9 M4 is released.
On Fri, Dec 12, 2014 at 9:50 AM, Vijitha Ekanayake vijit...@wso2.com
wrote:
Hi,
Is there a way to set a connector to a TomcatServerManager instance which
is provided by automation? since i need to enable ssl.
On Thu, Dec 11, 2014 at
We have to rewrite all the QoS related tests as we changed our QoS enabling
approach with the 4.3 kernel.
On Tue, Dec 9, 2014 at 1:13 PM, Jeewantha Dharmaparakrama
jeewan...@wso2.com wrote:
On Tue, Dec 9, 2014 at 12:46 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi ESB Team,
Hi all,
If it's for the latest IS release, shall we use the latest nimbus
version(3.4 instead of 2.26.1) for this?
Thanks.
/Gayashan
On Fri, Dec 12, 2014 at 12:43 AM, Gayan Gunawardana ga...@wso2.com wrote:
Hi All,
Thanks all for feedback. We can plan identity components for next Identity
Hi All/Kishanthan,
I tried to debug this in OSGI level and some of the components saying No
unresolved constraints and some pop out Missing optionally imported
packages.
When I try diag 19, I can see the following.
osgi diag 19
reference:file:../plugins/bsf-all_3.0.0.wso2v2.jar [19]
Direct
Thanks Malaka, I will try with this scenario.
Thanks,
Kathees
On Fri, Dec 12, 2014 at 12:26 AM, Malaka Silva mal...@wso2.com wrote:
Hi Kathees,
Every object is salesforce is treated as a sobject. (Including Attachment)
Fields are listed in [1]. You need to create and send a payload
Hi all,
I am developing ESB connector for Teamwork API.I am getting
java.net.MalformedURLException when I invoke the update Milestone
operation.I am using ESB-4.9.0 M3 pack.
Wire log for the request:
[2014-12-12 10:40:24,935] DEBUG - wire POST
/services/tw_updateMilestone HTTP/1.1[\r][\n]
Hi,
On Fri, Dec 12, 2014 at 9:50 AM, Vijitha Ekanayake vijit...@wso2.com
wrote:
Hi,
Is there a way to set a connector to a TomcatServerManager instance which
is provided by automation? since i need to enable ssl.
I'm afraid there is no way to set connector to TomcatServerManager. Since
Hi Kesavan,
[1] only fixed this for status 301. But in your case it's 200 ok.
So the issue still remains. Pls add a jira for ESB
[1] https://wso2.org/jira/browse/ESBJAVA-3132
On Fri, Dec 12, 2014 at 10:42 AM, Kesavan Yogarajah kesav...@wso2.com
wrote:
Hi all,
I am developing ESB connector
Let's do another RC with only this change:
https://github.com/wso2/carbon4-kernel/pull/120
This is a critical non-intrusive change which adds support for Hazelcast
custom serializers which is essential in the case of replicating heavy
objects. WSO2 MB will be the first customer of this feature,
On Thu, Dec 11, 2014 at 7:15 PM, Pubudu Dissanayake pubu...@wso2.com
wrote:
Hi Jeewantha
It is not removed, *isCAppArtifact* is a newly added property to
service-mgt component. It will be available once it is merged to
carbon-deployment repo [1]
If you are referring to this ESB integration
Hi Sriashalya,
Can you try section 'Handling messages with no content type' in [1].
Also in this case you can try building using builder mediator [2]
[1]
https://docs.wso2.com/display/ESB481/Working+with+Message+Builders+and+Formatters
[2] https://docs.wso2.com/display/ESB481/Builder+Mediator
Hi Guys,
I have a another question regarding UES.
When we remove the
%
var user = require('/modules/user.js').current();
if (!user) {
response.sendRedirect('/vv/login');
}
%
snippet from a dashboard index.jag page, the gadgets will not show on the
1st page load. After a page refresh the
I figured out the error. It was a configuration problem with the
configurations in registry.xml
Thanks,
On Fri, Dec 12, 2014 at 10:07 AM, Madusanka Premaratne madusan...@wso2.com
wrote:
Hi All/Kishanthan,
I tried to debug this in OSGI level and some of the components saying No
unresolved
54 matches
Mail list logo
