Hi All,
I think we $Subject because now that Send mediator is embedding the
endpoint, we no longer need the WS-AddressingEndpoint. Keeping the empty
Send mediator indicates the WS-Addressing scenario just like in the Mgt
Console.
So I'm proposing $Subject.
WDYT?
Thanks and Regards,
Harshana
--
Hi Sumedha,
It seems that the hosted p2-repo has an incorrect jar. Checked with p2-repo
in builder machine [1] and the hosted one and it seems there is a
difference. (The p2-repo in builder machine has correct md5sum for the
relevant jar)
Guess we would have to re-host the p2-repo. For now,
I'm trying to write a script to download and setup CEP 3.0.0.
Where can I find the direct download link for CEP 3.0.0? CEP 3.0.0 isn't
available here:
http://dist.wso2.org/downloads/
I've tried using CEP 3.0.0 from the maven repo:
Hi Nandika,
Sure I'll check and confirm asap.
Thank you Best regards,
*Amal Gunatilake*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
On Sat, Jan 4, 2014 at 1:48 AM, Nandika Jayawardana nand...@wso2.comwrote:
Hi Isuru,
Updated the ui feature to use new version
Hi Lasantha,
Yes, It worked.
@Ruwan,
There is another issue related to APIM. When installing features it shows
APIM as 1.5.0 and I think it should be 1.6.0. Also the jars installed by
the key manager feature are older versions (checked only with Key Manager).
That is the versions of jars
Congrats Sumedha !
On Sun, Jan 5, 2014 at 9:22 AM, Gokul Balakrishnan go...@wso2.com wrote:
Congrats Sumedha!!
On 3 January 2014 13:58, Amila Maha Arachchi ami...@wso2.com wrote:
Hi All,
It's my pleasure to welcome Sumedha Kodithuwakku as a WSO2 Committer.
SumedhaS has
Hi Sumedha,
There was a issue with the nested categories. I did a fix locally and
re-compiled a feature repo on the builder machine.
Please try with the link @ [1], You will be able to see the latest Jars
listed under the API Manager 1.6.0 category.
[1] -
Hi Ruwan,
It's working with the above link. No issues while installing features.
Thanks
SumedhaS
On Sun, Jan 5, 2014 at 6:10 PM, Ruwan Yatawara ruw...@wso2.com wrote:
Hi Sumedha,
There was a issue with the nested categories. I did a fix locally and
re-compiled a feature repo on the
Hi,
+1
WS-Addresing Endpoint is no longer needed. So we can remove it from tool
palette. Created a public Jira [1] to track this.
[1] - https://wso2.org/jira/browse/TOOLS-2274
Thanks,
Viraj.
On Sun, Jan 5, 2014 at 2:23 PM, Harshana Martin harsh...@wso2.com wrote:
Hi All,
I think we
+1
On Mon, Jan 6, 2014 at 9:50 AM, Viraj Rajaguru vi...@wso2.com wrote:
Hi,
+1
WS-Addresing Endpoint is no longer needed. So we can remove it from tool
palette. Created a public Jira [1] to track this.
[1] - https://wso2.org/jira/browse/TOOLS-2274
Thanks,
Viraj.
On Sun, Jan 5,
And we may be able to fix [1] as well.
[1] - https://wso2.org/jira/browse/TOOLS-2271
On Mon, Jan 6, 2014 at 9:59 AM, Susinda Perera susi...@wso2.com wrote:
+1
On Mon, Jan 6, 2014 at 9:50 AM, Viraj Rajaguru vi...@wso2.com wrote:
Hi,
+1
WS-Addresing Endpoint is no longer needed. So we
Hi guys,
I tried the xhr client to send my B64 encoded + URL encoded saml assertion.
However it alters some of the content during the transfer process.
Below is the code bit that im using,
var endpoint = config.oauthConfiguration.tokenEndpoint;
var headers = {
Hi,
It seems that, post method in jaggery URL encodes the body by default. Is
this the correct behaviour.? curl doesnt do that sort of thing.
workaround was, not to URL encode SAML assertion.
thanks,
--Pradeep
___
Dev mailing list
Dev@wso2.org
13 matches
Mail list logo
