Re: [Architecture] [Cloud] Filtering applications based on subscription

2013-10-11 Thread Ashansa Perera
Hi Chris, If I am not mistaken, what Amila means is to show only the services related to iPaaS if the user logs in through iPaaS login and show only aPaaS related services if he logs in through aPaaS login. So this would require a separate log in to access the services in the other cloud. ( user

[Architecture] Support per API (ESB) logging configuration

2013-10-11 Thread Sagara Gunathunga
Proxy services already support for per service logging configuration, which means though the log4j.properties file it is possible to control logging behavior per proxy services such as create separate log file per proxy, define log category per proxy etc. But for the moment ESB APIs don't support

Re: [Architecture] [Cloud] Filtering applications based on subscription

2013-10-11 Thread Chris Haddad
The stated use case is simply broken user needs to log out and log in to the other cloud to access its services If I subscribe to all cloud services, I should be able to access all cloud services without multiple logins. My credentials should work across all clouds, and I should have a

Re: [Architecture] Support per API (ESB) logging configuration

2013-10-11 Thread Isuru Udana
Hi Sagara, This is a very useful feature to have. Please check-in the code to synapse so that we can have it for ESB 4.8.0. Thanks, IsuruU On Fri, Oct 11, 2013 at 8:12 PM, Sagara Gunathunga sag...@wso2.com wrote: Proxy services already support for per service logging configuration, which

Re: [Architecture] Support per API (ESB) logging configuration

2013-10-11 Thread Kasun Indrasiri
On Fri, Oct 11, 2013 at 8:12 PM, Sagara Gunathunga sag...@wso2.com wrote: Proxy services already support for per service logging configuration, which means though the log4j.properties file it is possible to control logging behavior per proxy services such as create separate log file per

Re: [Architecture] Support per API (ESB) logging configuration

2013-10-11 Thread Jackie Wheeler
If this is going into 4.8.0, please be sure to create a RedMine story for it (if you haven't already) and follow the usual protocol. No more features slipped into releases like stealthy ninjas, please. :) Sent from my iPhone On Oct 11, 2013, at 9:23 AM, Isuru Udana isu...@wso2.com wrote:

Re: [Architecture] Support per API (ESB) logging configuration

2013-10-11 Thread Sanjiva Weerawarana
Great feature but don't slip it into 4.8.0 which is due to release in days! NOT a good idea to add features last second like this. On Fri, Oct 11, 2013 at 10:50 PM, Sumedha Rubasinghe sume...@wso2.comwrote: On Friday, October 11, 2013, Isuru Udana wrote: Hi Sagara, This is a very

[Architecture] WSO2 Enterprise Store 1.0.0 Beta-1 Released !

2013-10-11 Thread Nuwan Bandara
*WSO2 Enterprise Store 1.0.0 Beta-1 Released !* This is the Beta-1 release of WSO2 Enterprise Store, which will create a marketplace for your enterprise assets. You can download the Beta-1 at [1]. This release specifically contains following tasks, improvements and bug fixes towards 1.0.0 GA.

Re: [Architecture] New Mediator for Transformation

2013-10-11 Thread Sanjiva Weerawarana
I'm sorry but I don't understand this at all. This means I have to write Java classes to represent each of my data items and then there's some magic to convert the Java class to JSON/XML? Java - JSON/XML is not possible without loss either. Can you please explain a bit more of what this is?

Re: [Architecture] [Cloud] Filtering applications based on subscription

2013-10-11 Thread Sanjiva Weerawarana
No I don't agree Chris. We are offering 3 URLs for the 3 cloud services ... app, integration and API clouds. API is a different product so lets ignore that. (There's absolutely no unified interface to see that.) If a person is writing an app in the app cloud then they should not see the