Hi Everyone,
*Context*
- The Service RXT will be hosted in the ES for the next GREG release
(5.0.0)
- This involves replicating the create,update and lifecycle behaviour
present in the registry
- The behaviour of the Service lifecycle allows users to define a new
version at
Hi Gokul,
Basically above util method filltered out all adminservices ,
hiddenServices and dynamicServices. If you define any of these parameters
to true using services.xml then that services is become filteredOutService.
Thanks,
Shameera.
On Mon, Aug 11, 2014 at 3:32 PM, Gokul Balakrishnan
Hi
I have created a redmine entry[1] and finished the initial phase of the
implementation to support $subject.
[1] https://redmine.wso2.com/issues/3149
Thanks,
Nuwanw
On Tue, Aug 12, 2014 at 11:18 AM, Dharshana Warusavitharana
dharsha...@wso2.com wrote:
+1 , Implemetation is on the way will
Hi Malaka,
My initial payload is as follows:
payloadFactory media-type=xml
format
jsonObject xmlns=
nameJanaka/name
descriptionDesc/description
statusopen/status
Hi,
Seems this issue[1] happens due to URL redirections during SSO login.
Initially we use URL[2] to browse store homepage. When we click log-in,
store redirects to a similar URL like this[3]. If we provide correct login
credentials it redirects back to the store[2]. Up to now everything works
as
Hi Kasun,
i have created Ticket WSAS-1771 for this in JIRA (
https://wso2.org/jira/browse/WSAS-1771) and provided a patch file for the
two changed classes. Additionally i have provided a stacktrace, which you
get without patching the CarbonTomcatSessionManager#checkAccess method.
Looks like
Hi,
There is a requirement to deploy dataservice configuration (.dbs) file with
its corresponding services.xml using Capp. According to the current
implementation, DefaultAppDeployer[1] calls .dsb files deployer. As the
artifacts in the Capp are extracted and copied to a temporary location
before
Hi All
As per the pack released on 05/08/2014 following is the status
1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue
status - inprogress. This is the main scenario of the migration. Thus the
fix for this is crucial to proceed with the proper user scenario based
testing
Hi there,
I have a Oracle database view containing details of around 8000 employees.
I need to populate employee search suggestions from that view. I'm planning
to use DSS/ DSS+ESB to create a data service for that. Rather querying the
view for each and every service call, i'm thinking of caching
Problem was solved after building with a clean m2 repo.
Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
On Wed, Aug 13, 2014 at 10:14 AM, Sandamal Weerasinghe sanda...@wso2.com
wrote:
Hi,
I'm getting a FileNotFoundException in the above test case. Has this been
encountered
Hi Nipuni,
On Wed, Aug 13, 2014 at 10:52 AM, Nipuni Perera nip...@wso2.com wrote:
Hi,
I am working on issue[1]. According to the existing implementation the
constant LDAPConstants.USER_CONTEXT_NAME has been used in several places
to build OrganizationalSubContextAttribute. If the
Please find the $subject in [1].
[1]. http://builder1.us1.wso2.org/~appm/14-08-2014/wso2eam-1.0.0.zip
Regards,
Dinusha.
--
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
Hi,
I was trying to implement WS-Discovery scenario referring to the article
[1] .
I am been using ESB 4.8.1 and G-Reg 4.6.0.
Initially I added the G-Reg as discovery proxy in ESB and it showed it as
on-line.
Thereafter when I tried to view the discovered proxies, it keeps me
throwing
Hi,
Still the issue exists. Please fix it ASAP, since we need to get the pack
out for testing.
Thanks,
Sinthuja
On Wed, Aug 13, 2014 at 10:48 AM, Shameera Rathnayaka shame...@wso2.com
wrote:
Hi Kasun,
Please fix this, This is downstream build error with hazelcast upgrade.
Cheers,
Hi all,
Considering the discussions, I have implemented unified response message as
follows.
*Error Response*
{
'error': error message
}
*Success Response*
{
'data' : [ ]
}
In both cases * HTTP status code *is sent in header.
In success response what ever the response
On Wednesday, August 13, 2014, Thomas Wieger developer.wie...@gmail.com
wrote:
Hi Kasun,
i have created Ticket WSAS-1771 for this in JIRA (
https://wso2.org/jira/browse/WSAS-1771) and provided a patch file for the
two changed classes. Additionally i have provided a stacktrace, which you
get
Hi Dilan / Harshan,
Below is the commit for branch feature/cloud where the agent download URL
has been changed to mdm from emm. Why is this?
modules/apps/emm/modules/device.js
* } else if (userAgent.indexOf(iPhone) 0) {*
*-
Hi,
I have taken this from EMM 1.1.0 master branch in wso2. It's same in the
master branch also.
https://github.com/wso2/product-emm/blob/master/modules/apps/emm/modules/device.js
Thanks,
Best Regards,
Lakshitha Harshan
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog :
Hi Harshan,
There were some fixes that where done for the develop branch. From the top
of my head, fixes like Unit Test issues and all where committed to the dev
branch. Also since it was taken from the master branch, we will be having
some problem merging it to the dev branch.
Regards,
Nira
Hi Niranjan,
This was taken from the master branch because this pack needs to be a
released pack. If there is no issue for using dev branch for this, we can
merge our changes to a pack taken from dev branch update cloud feature
branch with that.
Thanks,
Best Regards,
Lakshitha Harshan
Hi,
In order to resolve $Subject raised by G-reg mentioned in [01], I made
changes to following places in the ES source.
modules/apps/publisher/config/publisher.json
modules/apps/publisher/extensions/assets/gadget/apis/assets.jag
modules/apps/social/configs/social.json
21 matches
Mail list logo
