Re: [Dev] Custom authentication error message in APIM
Can you attach your modified auth_failure_handler.xml?
On Tue, Sep 26, 2017 at 10:17 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
wrote:
> See this document [1]. You will have to customize auth_failure_handler.xml
> sequence.
>
> [1] https://docs.wso2.com/display/AM210/Error+Handling#ErrorHandling-
> Customerrormessages
>
> On Tue, Sep 26, 2017 at 8:14 AM, vivekkumar <vivek.kum...@fisglobal.com>
> wrote:
>
>> I would like to send custom error message for any authentication related
>> issue.
>>
>> Currently APIM is sending default error message that is following
>>
>> {
>> "fault": {
>> "code": 900901,
>> "message": "Invalid Credentials",
>> "description": "Access failure for API: //v1, version: v1
>> status: (900901) - Invalid Credentials. Make sure you have given the
>> correct
>> access token"
>> }
>> }
>>
>> I tried to modify the sequence '_auth_failure_handler_.xml', but that
>> didn't
>> make any difference.
>>
>> Any suggestion would be helpful.
>>
>> Vivek
>>
>>
>>
>>
>> --
>> Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development
>> -f3.html
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Custom authentication error message in APIM
See this document [1]. You will have to customize auth_failure_handler.xml
sequence.
[1]
https://docs.wso2.com/display/AM210/Error+Handling#ErrorHandling-Customerrormessages
On Tue, Sep 26, 2017 at 8:14 AM, vivekkumar <vivek.kum...@fisglobal.com>
wrote:
> I would like to send custom error message for any authentication related
> issue.
>
> Currently APIM is sending default error message that is following
>
> {
> "fault": {
> "code": 900901,
> "message": "Invalid Credentials",
> "description": "Access failure for API: //v1, version: v1
> status: (900901) - Invalid Credentials. Make sure you have given the
> correct
> access token"
> }
> }
>
> I tried to modify the sequence '_auth_failure_handler_.xml', but that
> didn't
> make any difference.
>
> Any suggestion would be helpful.
>
> Vivek
>
>
>
>
> --
> Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-
> Development-f3.html
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API ManagerToken API
This the key manager host name you configure under APIKeyValidator section
in api-manager.xml of Gateway.
On Thu, Jul 20, 2017 at 8:58 PM Júnior <fjunio...@gmail.com> wrote:
> Hi Rajkumar,
>
> In the code you sent, it tries to take the property from the
> SystemProperty: -DkeyManagerHostname=myhost.
>
> But it always take localhost.
>
> Where do I need to set this value?
>
> Thanks,
>
> 2017-07-20 18:19 GMT-03:00 Rajkumar Rajaratnam <rajkum...@wso2.com>:
>
>> You don't need to set this manually.
>>
>> Gateway will read key manager configuration from api-manager.xml and
>> automatically set these values.
>>
>> See -
>> https://github.com/wso2/carbon-apimgt/blob/5.0.x/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/handlers/common/SynapsePropertiesHandler.java
>>
>> On Thu, Jul 20, 2017 at 5:13 PM, Júnior <fjunio...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Where do I set the value for those variables:
>>>
>>> >> expression="get-property('keyManager.port')"/>
>>> >> expression="get-property('keyManager.hostname')"/>
>>>
>>>
>>>
>>>
>>> Used in the Token API in API Manager.
>>>
>>> I didn't find in the docs where to set those values.
>>>
>>> Any tips are very welcome.
>>>
>>> Thanks,
>>> --
>>> Francisco Ribeiro
>>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Senior Software Engineer, WSO2
>>
>
>
>
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API ManagerToken API
You don't need to set this manually.
Gateway will read key manager configuration from api-manager.xml and
automatically set these values.
See -
https://github.com/wso2/carbon-apimgt/blob/5.0.x/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/handlers/common/SynapsePropertiesHandler.java
On Thu, Jul 20, 2017 at 5:13 PM, Júnior <fjunio...@gmail.com> wrote:
> Hi,
>
> Where do I set the value for those variables:
>
> expression="get-property('keyManager.port')"/>
>expression="get-property('keyManager.hostname')"/>
>
>
>
>
> Used in the Token API in API Manager.
>
> I didn't find in the docs where to set those values.
>
> Any tips are very welcome.
>
> Thanks,
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do I execute a piece of code when a connector is deployed/initialized?
Thanks Rajjaz. Firstly, I don't want to use a script mediator, because it has performance issues with high concurrency. Secondly, I want to execute a piece of code when the connector is deployed and enabled. I've implemented ManagedLifecycle and have put my code inside init() and everything works fine for my usecase. Any issue with this approach? Thanks, Raj. On Sun, Jul 9, 2017 at 2:26 AM, Rajjaz Mohammed <raj...@wso2.com> wrote: > Hi Raj, > > You can do this by read the system variables and store it in the > registry[1][2]. If the resource is updated then it will not read again and > again for every request. Normally we follow this approach to store the > access token and refresh token variables from the first call. > > [1] https://github.com/wso2-extensions/esb-connector- > googlespreadsheet/blob/master/src/main/resources/config/ > getAccessTokenFromRefreshToken.xml#L54 > [2] https://github.com/wso2-extensions/esb-connector- > googlespreadsheet/blob/master/src/main/resources/config/init.xml#L69 > > On Sun, Jul 9, 2017 at 9:12 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Would implementing ManagedLifecycle be the option for this? >> >> On Sat, Jul 8, 2017 at 11:20 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I need to execute a piece of code to read some system variables and >>> initialize my connector. I need to do this only once and IMO it's better to >>> do this during connector deployment time. I don't want to execute this code >>> again and again for every requests. >>> >>> How do I do this? >>> >>> Thanks. >>> >> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Senior Software Engineer, WSO2 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thank you > Best Regards > > *Rajjaz HM* > Software Engineer > Platform Extension Team > WSO2 Inc. <http://wso2.com/> > lean | enterprise | middleware > Mobile | +94752833834 <+94%2075%20283%203834>|+94777226874 > <+94%2077%20722%206874> > Email | raj...@wso2.com > LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger > <http://rajjazhm.blogspot.com/> | WSO2 Profile > <http://wso2.com/about/team/mohammer-rajjaz/> > [image: https://wso2.com/signature] <https://wso2.com/signature> > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do I execute a piece of code when a connector is deployed/initialized?
Would implementing ManagedLifecycle be the option for this? On Sat, Jul 8, 2017 at 11:20 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Hi, > > I need to execute a piece of code to read some system variables and > initialize my connector. I need to do this only once and IMO it's better to > do this during connector deployment time. I don't want to execute this code > again and again for every requests. > > How do I do this? > > Thanks. > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How do I execute a piece of code when a connector is deployed/initialized?
Hi, I need to execute a piece of code to read some system variables and initialize my connector. I need to do this only once and IMO it's better to do this during connector deployment time. I don't want to execute this code again and again for every requests. How do I do this? Thanks. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to build a connector?
Yeah, but it doesn't give an impression that it won't work with maven > 3.0.5. So better to reword it. On Sat, Jul 8, 2017 at 12:10 AM, Rajjaz Mohammed <raj...@wso2.com> wrote: > Hi Rajkumar, > > In the doc[1] we mentioned that it's tested with Maven 3.0.5. > > [1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+ > Connector#WritingaConnector-CreatetheMavenprojecttemplate > > On Sat, Jul 8, 2017 at 9:20 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Thanks Hasitha. >> >> I was using maven 3.3.9. Downgraded it to 3.0.5 and it builds now. >> >> So we need to mention in the doc [1] that this won't build with maven >> version > 3.0.5 >> >> [1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector >> >> Thanks, >> Raj. >> >> >> On Fri, Jul 7, 2017 at 11:37 PM, Hasitha Jayasundara < >> hasithajayasunda...@gmail.com> wrote: >> >>> Hi Rajkumar, >>> >>> Works fine with >>> >>> Apache Maven 3.0.5 >>> Java version: 1.8.0_131, vendor: Oracle Corporation >>> >>> Thanks >>> >>> On Sat, Jul 8, 2017 at 8:52 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> >>> wrote: >>> >>>> I'm trying to build this connector https://github.com/w >>>> so2-extensions/esb-connector-gmail >>>> >>>> It's failing - see below. Do we need to do anything special to build >>>> this other than doing mvn clean install? >>>> >>>> >>>> [INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail >>>> 3.0.6-SNAPSHOT >>>> [INFO] >>>> >>>> [WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no >>>> dependency information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.http.servlet:jar:1.0.200.v20090520-1800 is missing, no >>>> dependency information available >>>> [WARNING] The POM for org.eclipse.osgi:org.eclipse.o >>>> sgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency >>>> information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no >>>> dependency information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency >>>> information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency >>>> information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.jsp.jasper:jar:1.0.200.v20090520-1800 is missing, no >>>> dependency information available >>>> [WARNING] The POM for org.eclipse.equinox:javax.serv >>>> let.jsp:jar:2.0.0.v200806031607 is missing, no dependency information >>>> available >>>> [WARNING] The POM for org.eclipse.equinox:org.apache >>>> .jasper:jar:5.5.17.v200806031609 is missing, no dependency information >>>> available >>>> [WARNING] The POM for org.eclipse.equinox:org.apache >>>> .commons.el:jar:1.0.0.v200806031608 is missing, no dependency >>>> information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency >>>> information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.concurrent:jar:1.0.0.v20090520-1800 is missing, no >>>> dependency information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no >>>> dependency information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is >>>> missing, no dependency information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.p2.artifact.repository:jar:1.0.100.v20090520-1905 is >>>> missing, no dependency information available >>>> [WARNING] The POM for org.eclipse.equinox:org.eclips >>>> e.equinox.p2.core:jar:1.0.100.v20090520-1905 is missing, no dependency >>>> informat
Re: [Dev] How to build a connector?
Thanks Hasitha. I was using maven 3.3.9. Downgraded it to 3.0.5 and it builds now. So we need to mention in the doc [1] that this won't build with maven version > 3.0.5 [1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector Thanks, Raj. On Fri, Jul 7, 2017 at 11:37 PM, Hasitha Jayasundara < hasithajayasunda...@gmail.com> wrote: > Hi Rajkumar, > > Works fine with > > Apache Maven 3.0.5 > Java version: 1.8.0_131, vendor: Oracle Corporation > > Thanks > > On Sat, Jul 8, 2017 at 8:52 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> I'm trying to build this connector https://github.com/w >> so2-extensions/esb-connector-gmail >> >> It's failing - see below. Do we need to do anything special to build this >> other than doing mvn clean install? >> >> >> [INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail >> 3.0.6-SNAPSHOT >> [INFO] >> >> [WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.http.servlet:jar:1.0.200.v20090520-1800 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.osgi:org.eclipse.o >> sgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.jsp.jasper:jar:1.0.200.v20090520-1800 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:javax.serv >> let.jsp:jar:2.0.0.v200806031607 is missing, no dependency information >> available >> [WARNING] The POM for org.eclipse.equinox:org.apache >> .jasper:jar:5.5.17.v200806031609 is missing, no dependency information >> available >> [WARNING] The POM for org.eclipse.equinox:org.apache >> .commons.el:jar:1.0.0.v200806031608 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.concurrent:jar:1.0.0.v20090520-1800 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is missing, >> no dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.artifact.repository:jar:1.0.100.v20090520-1905 is missing, >> no dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.core:jar:1.0.100.v20090520-1905 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.director:jar:1.0.100.v20090520-1905 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.director.app:jar:1.0.100.v20090521-1912 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.directorywatcher:jar:1.0.100.v20090520-1905 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.engine:jar:1.0.100.v20090520-1905 is missing, no dependency >> information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.exemplarysetup:jar:1.0.100.v20090520-1905 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.extensionlocation:jar:1.0.100.v20090520-1905 is missing, no >> dependency information available >> [WARNING] The POM for org.eclipse.equinox:org.eclips >> e.equinox.p2.jarprocessor:jar:1.0.100.v200
[Dev] How to build a connector?
I'm trying to build this connector https://github.com/wso2-extensions/esb-connector-gmail It's failing - see below. Do we need to do anything special to build this other than doing mvn clean install? [INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail 3.0.6-SNAPSHOT [INFO] [WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.http.servlet:jar:1.0.200.v20090520-1800 is missing, no dependency information available [WARNING] The POM for org.eclipse.osgi:org.eclipse.osgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.jsp.jasper:jar:1.0.200.v20090520-1800 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:javax.servlet.jsp:jar:2.0.0.v200806031607 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.apache.jasper:jar:5.5.17.v200806031609 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.apache.commons.el:jar:1.0.0.v200806031608 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.concurrent:jar:1.0.0.v20090520-1800 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.artifact.repository:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.core:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.director:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.director.app:jar:1.0.100.v20090521-1912 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.directorywatcher:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.engine:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.exemplarysetup:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.extensionlocation:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.jarprocessor:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.metadata.generator:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.metadata:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.metadata.repository:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.reconciler.dropins:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.publisher:jar:1.0.0.v20090521-1912 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.repository.tools:jar:1.0.0.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.repository:jar:1.0.0.v20090520-1905 is missing, no dependency information available [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.touchpoint.natives:jar:1.0.100.v20090520-1905 is missing, no dependency information available [WARNING] The POM for
Re: [Dev] Fixing the cache mediator
Also the existing cache mediator doesn't honor the cache ID as per my testing sometimes back (not sure it's fixed though). It means caching works globally, not at cache mediator instance level. If we can't correlate a finder with a collector (using cache mediator ID), then we are going to hit memory issues. Here is the reason. Let's say we have two APIs - location and exchange. 1. /location API response size is 10 MB and we have 100 different responses 2. /exchange API response size is 1MB and we have 1000 different responses If we want to enable response caching for these two APIs, if we can correlate a finder with a collector (i.e if we support caching at cache mediator instance level), then I can allocate 100*10 + 1000*1 = 2000 MB memory to the JVM in addition to our recommended memory settings, so that it will never go OOM. If we can't correlate a finder with a collector (i.e, if we support global caching), then I have to allocate 1100 * 10 = 11000 MB memory. See I have to use additional 9000 MB if we don't honor cache ID. It's not practical and efficient because memory is expensive - so it doesn't scale. Can we fix this issue and honor cache ID please in the next EI release? On Wed, Jul 5, 2017 at 9:18 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Is this going to be a rewrite or improvement to existing cache mediator? > If this is a rewrite, will it be included in next EI release? > > Also can we also implement cache eviction as part of this effort? > > Ideally, we should be able to configure how many maximum responses we can > cache (not sure whether it's there already, it was not working sometimes > back) and what's the maximum message size (it's already there) we can cache > to avoid OOM. Then we need to have cache eviction in place to evict some > cached items when cache is full, in-order to give space for most recent > responses. > > Thanks. > > On Wed, Jul 5, 2017 at 6:02 AM, Riyafa Abdul Hameed <riy...@wso2.com> > wrote: > >> Hi, >> Please find the requirements doc below: >> https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9a >> qAFEubmFgNkQhoDvqz8/edit?usp=sharing >> Any suggestions would be highly appreciated. >> Thank you. >> Riyafa >> >> On Tue, Jul 4, 2017 at 5:37 PM, Riyafa Abdul Hameed <riy...@wso2.com> >> wrote: >> >>> Hi all, >>> >>> Thank you for the suggestions. Yes the mediator should also work with >>> the call mediator. >>> >>> Further on a discussion with the APIM team I have identified the >>> following issues which points to requiring a rewrite of the cache mediator: >>> >>>1. >>> >>>Current cache mediator[1] caches responses for all the HTTP Request >>>Methods which include GET, POST, PUT and DELETE. Ideally a cache mediator >>>should cache only the response for GET method and caching for POST method >>>should be configurable (because POST is the only method used in SOAP >>>implementations). The caching for PUT and DELETE methods should be >>>completely omitted. The reason for caching responses only for GET is >>>because in the REST world other methods (POST, PUT and DELETE) are used >>> for >>>creating, modifying or deleting existing records and hence the response >>>would only mention the success or failure of the request. Caching these >>>responses is meaningless and error prone. >>>2. >>> >>>Current cache mediator caches all the responses whether they are >>>success or failure responses. Ideally the mediator should cache only >>>success (200 OK) responses and not the failures >>>3. >>> >>>Current mediator hashes the payload (both DOMHASHGenerator and >>>REQUESTHASHGenerator) which is a huge overhead for messages with larger >>>bodies. The mediator should hash only the recipient (To) address of the >>>request and the HTTP headers which can be easily handled when only >>>responses for GET methods are hashed. Payload should be hashed only if >>> PUT >>>method is configured. >>>4. >>> >>>Current mediator does not allow configurations for omitting certain >>>headers when hashing. For example there’s no point in hashing the >>> timestamp >>>header--it will almost always be different from message to message. >>>5. >>> >>>The current mediator does not honor the http headers[2]. For example >>>the max-age header specifies the maximum time in seconds that the fetched >>>response is
Re: [Dev] Fixing the cache mediator
ator.
>>>> 3). Feasibility to introduce native JSON caching support to cache
>>>> mediator.
>>>> 4). Feasibility to introduce service level caching which isn't support
>>>> at the moment.
>>>>
>>> IMO, service level caching is not a requirement as long as we can
>>> achieve all the requirements through the Cache Mediator.
>>>
>>> Thanks.
>>>
>>>>
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On Tue, Jul 4, 2017 at 12:06 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>>>> wrote:
>>>>
>>>>> Dear all,
>>>>>
>>>>> By going through the issues faced by the customers in the past I
>>>>> discovered the following issues:
>>>>>
>>>>>1. Continue the execution on cache hit. Reported as an issue in
>>>>>github[1]
>>>>>2. Issue in processing JSON array (payload) with a single element
>>>>>when response caching is enabled where expected response is:
>>>>>
>>>>> [
>>>>>{
>>>>> "msg":"Hello",
>>>>> "services":[
>>>>> "elec",
>>>>> "patrol"
>>>>> ],
>>>>> "test":"World."
>>>>>},
>>>>>{
>>>>> "msg":"Hi",
>>>>> "services":[
>>>>> "water"
>>>>> ],
>>>>> "test":"Sri Lanka."
>>>>>}
>>>>> ]
>>>>>
>>>>> but received response is:
>>>>>
>>>>> [
>>>>> { "msg": "Hello", "services": [ "elec", "patrol" ], "test": "World." }
>>>>>
>>>>> ,
>>>>> { "msg": "Hi", "services": "water", "test": "Sri Lanka." }
>>>>>
>>>>> ]
>>>>>
>>>>> This issue has been fixed in the carbon mediation[2].
>>>>>
>>>>>3. When a xml body with processing instructions is stored
>>>>> in cache and sent back as json it fails with an exception. Issue was
>>>>> reported in 2015 and already has a fix in current EI.
>>>>>
>>>>> Since the last two issues have been already fixed, I would like to
>>>>> know what other issues if any needs to be addressed and if a complete
>>>>> rewrite of the cache mediator would be required.
>>>>>
>>>>> [1] https://github.com/wso2/product-ei/issues/695
>>>>>
>>>>> [2]https://github.com/riyafa/carbon-mediation/commit/7aaf597
>>>>> 988a333e1cad36dc0b5057e24fb779a5c
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Riyafa
>>>>>
>>>>> --
>>>>> Riyafa Abdul Hameed
>>>>> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>>>>>
>>>>> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
>>>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>>>> <http://facebook.com/riyafa.ahf> <http://lk.linkedin.com/in/riyafa>
>>>>> <http://twitter.com/Riyafa1>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Vijitha Ekanayake
>>>> Software Engineer*, *WSO2, Inc.; http://wso2.com/
>>>> Mobile : +94 777 24 73 39 | +94 718 74 44 08
>>>> lean.enterprise.middleware
>>>>
>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Senior Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887 <+94%2077%20379%201887>
>>> blog: http://mytecheye.blogspot.com/
>>>
>>
>>
>>
>> --
>> Riyafa Abdul Hameed
>> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>>
>> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>> <http://facebook.com/riyafa.ahf> <http://lk.linkedin.com/in/riyafa>
>> <http://twitter.com/Riyafa1>
>>
>
>
>
> --
> Riyafa Abdul Hameed
> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>
> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
> <http://facebook.com/riyafa.ahf> <http://lk.linkedin.com/in/riyafa>
> <http://twitter.com/Riyafa1>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager Basic Auth
There is no out of the box way to secure your APIs with basic authentication in WSO2 API Manager. But you can write a new authentication handler for your requirement. However please note you need to evaluate the security mechanism and how it is applied via a handler first. For example, when the current handler receives an OAuth2 access token, it knows the user, application, subscription information. That's how it knows how to throttle and publish stats accordingly. You need to be able to find these information from your new handler you introduce for the throttling and stats to work accurately. Thanks. On Wed, Jul 5, 2017 at 4:02 PM, Júnior <fjunio...@gmail.com> wrote: > Hello, > > I am trying to configure an API on WSO2AM 2.1.0, and the only > authentication mechanism it supports is via OAuth. Is there any way to use > Basic Auth for API Authentication? > > Thanks, > -- > Francisco Ribeiro > *SCEA|SCJP|SCWCD|IBM Certified SOA Associate* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn: https://lk.linkedin.com/in/rajuu Mobile: +1 408 791 7640 Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [EI 6.1.1] DM vs PF, which is fast?
Do we have a comparison? -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn: https://lk.linkedin.com/in/rajuu Mobile: +1 408 791 7640 Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automated deployment API Manager
Hi,
Recommended way to move APIs between environments is using API
import/export tool. See
https://docs.wso2.com/display/AM1100/Migrating+the+APIs+to+a+Different+Environment
In terms of environment specific things like URLs, you can externalize them
from the API definition and resolve it using a class mediator. See
http://nuwanzone.blogspot.com/2015/03/api-gateways-with-dedicated-back-ends.html
Even better, for latest API-M releases (1.10 onwards) that are based on
synapse 3, we can use get-property('system', 'host') and therefore won't
need any class mediators as I mentioned above to resolve environment
variables.
Passing environment variables in the server startup;
sh bin/wso2server.sh -Dhost=prod.wf.com -Dport=6443
Reading them in API synapse definition.
Thanks,
Raj.
On Wed, May 17, 2017 at 1:59 PM, Júnior <fjunio...@gmail.com> wrote:
> Hello,
>
> Is it possible to have automated deployment for API definitions on API
> Manager?
>
> We need to have the same API Definition in different environments, what
> will change per environemt would be the URLs of the services.
>
> Is there any way to automate this "deployment" in the different
> environments, or is it needed to create one by one per environment?
>
> Thanks in advance
>
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
LinkedIn: https://lk.linkedin.com/in/rajuu
Mobile: +1 408 791 7640
Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Preventing API Developers from updating an API once its Published
sts. > > What if we introduce another life cycle state and transfer the API to that > state until API publisher re-publishes the API. In this way, there is no > effect to the existing API. > > Thank you! > > On Thu, Mar 30, 2017 at 11:41 PM, Rukshan Premathunga <ruks...@wso2.com> > wrote: > > Hi Nuwan, > > If we demote API back to create, state how we are going to handle > subscription already have? Are we going to disable them till the API get > publish again? > > Also can we introduce or use the existing state to allow the API to be > update without un-publishing it. once it is done we can publish it again > with the changes. Because in if we demote to create state, we cannot have > subscription information right? > > Thanks and Regards > > On Thu, Mar 30, 2017 at 11:15 PM, Nuwan Dias <nuw...@wso2.com> wrote: > > Hi, > > On API Manager, API Developers (!= publishers) aren't able to publish an > API to the Store or Gateway. But on API Manager version 2.1.0 and before, > if an API Developer makes an update to an API that is already published, > the changes made by the developer are immediately reflected on the Store > and Gateway. This kind of beats the purpose of preventing API Developers > from publishing APIs to the Store and Gateway directly. > > For API Manager 3.0.0, I suggest that we prevent the API being updated by > API Developers after the API has gone beyond the "CREATED" state. API > Publishers should still be allowed to make updates to the fields they are > eligible for (non technical information). If someone badly needs to update > technical information of a published API, they should first bring the API > to the "CREATED" state, which will make the API disappear temporarily and > bring it back to "PUBLISHED" once the changes are saved. > > Thanks, > NuwanD. > > -- > Nuwan Dias > > Software Architect - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 <+94%2077%20777%205729> > > > > > -- > Rukshan Chathuranga. > Software Engineer. > WSO2, Inc. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > > > > -- > Nuwan Dias > > Software Architect - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 <+94%2077%20777%205729> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > -- > Malintha Amarasinghe > Software Engineer > *WSO2, Inc. - lean | enterprise | middleware* > http://wso2.com/ > > Mobile : +94 712383306 <+94%2071%20238%203306> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > -- > Nuwan Dias > > Software Architect - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn: https://lk.linkedin.com/in/rajuu Mobile: +1 408 791 7640 Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I add a registry resource using registry REST API?
On Mon, Mar 13, 2017 at 12:26 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Hi Shazni, > > I just want to add/update a synapse sequence to the registry through a > HTTP call. Please let me know if there is a way to do this in API-M 1.10. > > Thanks, > Raj. > > On Mon, Mar 13, 2017 at 12:19 AM, Shazni Nazeer <sha...@wso2.com> wrote: > >> If you want to retrieve first class assets like the ones to which you >> have rxt definition, you can use the following recently introduced REST >> API. This is a separate feature which may not be packed with the API-M >> versions. You should be able to install it manually however. >> >> [1] https://docs.wso2.com/display/Governance540/Governance+REST+API >> >> On Mon, Mar 13, 2017 at 9:39 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> It seems registry REST API is not there in API-M 1.10. >>> >>> Using the following command I can get a registry resource in API-M 1.10 >>> >>> curl -X GET -k -H "Authorization:Basic YWRtaW46YWRtaW4=" " >>> https://127.0.0.1:9443/registry/resource/_system/governance >>> /apimgt/applicationdata/provider/admin/CalculatorAPI/1.0/in/ >>> cal_log_in_message" >>> >>> Similarly, how can I add/update a resource? >>> >>> Thanks. >>> >>> On Sun, Mar 12, 2017 at 11:29 PM, Rajkumar Rajaratnam < >>> rajkum...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> I'm referring [1] and trying to add a registry resource using registry >>>> REST API in API Manager 1.10 using the following command. >>>> >>>> curl -X PUT -k -H "Authorization:Basic YWRtaW46YWRtaW4=" -H >>>> "Content-Type: application/xml" -H "Media-Type: application/xml" -d >>>> @cal_log_in_message.xml "https://127.0.0.1:9443/resour >>>> ce/1.0.0/artifact/_system/governance/apimgt/applicationdata/ >>>> provider/admin/CalculatorAPI/1.0/in/cal_log_in_message" >>>> >>>> It's not working. Here is the response. >>>> >>>> raj@raj-Latitude-E6540:~/workspace$ curl -i -X PUT -k -H >>>> "Authorization:Basic YWRtaW46YWRtaW4=" -H "Content-Type: application/xml" >>>> -H "Media-Type: application/xml" -d @cal_log_in_message.xml " >>>> https://127.0.0.1:9443/resource/1.0.0/artifact/_system/gove >>>> rnance/apimgt/applicationdata/provider/admin/CalculatorAPI/1 >>>> .0/in/cal_log_in_message" >>>> HTTP/1.1 302 Found >>>> Set-Cookie: JSESSIONID=1A4DC76C0BB20201DF5C416D5B7105FE; Path=/; >>>> Secure; HttpOnly >>>> Set-Cookie: requestedURI=../../resource/1. >>>> 0.0/artifact/_system/governance/apimgt/applicationdata/provi >>>> der/admin/CalculatorAPI/1.0/in/cal_log_in_message; Path=/ >>>> Location: https://127.0.0.1:9443/carbon/admin/login.jsp >>>> Content-Type: text/html;charset=UTF-8 >>>> Content-Length: 0 >>>> Date: Mon, 13 Mar 2017 03:22:18 GMT >>>> Server: WSO2 Carbon Server >>>> >>>> Can you please advise how to do it in API-M 1.10? >>>> >>>> [1] https://docs.wso2.com/display/Governance510/Resources+with+REST+API >>>> >>>> Thanks, >>>> Raj. >>>> >>>> -- >>>> Rajkumar Rajaratnam >>>> Committer & PMC Member, Apache Stratos >>>> Senior Software Engineer, WSO2 >>>> >>>> LinkedIn: https://lk.linkedin.com/in/rajuu >>>> Mobile: +1 408 791 7640 <(408)%20791-7640> >>>> Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech >>>> >>> >>> >>> >>> -- >>> Rajkumar Rajaratnam >>> Committer & PMC Member, Apache Stratos >>> Senior Software Engineer, WSO2 >>> >>> LinkedIn: https://lk.linkedin.com/in/rajuu >>> Mobile: +1 408 791 7640 <(408)%20791-7640> >>> Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech >>> >> >> >> >> -- >> Shazni Nazeer >> Associate Technical Lead | WSO2 >> >> Mob : +94 37331 >> LinkedIn : http://lk.linkedin.com/in/shazninazeer >> Blog : http://shazninazeer.blogspot.com >> >> <http://wso2.com/signature> >> > > > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Senior Software Engineer, WSO2 > > LinkedIn: https://lk.linkedin.com/in/rajuu > Mobile: +1 408 791 7640 <(408)%20791-7640> > Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn: https://lk.linkedin.com/in/rajuu Mobile: +1 408 791 7640 Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I add a registry resource using registry REST API?
Hi Shazni, I just want to add/update a synapse sequence to the registry through a HTTP call. Please let me know if there is a way to do this in API-M 1.10. Thanks, Raj. On Mon, Mar 13, 2017 at 12:19 AM, Shazni Nazeer <sha...@wso2.com> wrote: > If you want to retrieve first class assets like the ones to which you have > rxt definition, you can use the following recently introduced REST API. > This is a separate feature which may not be packed with the API-M versions. > You should be able to install it manually however. > > [1] https://docs.wso2.com/display/Governance540/Governance+REST+API > > On Mon, Mar 13, 2017 at 9:39 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> It seems registry REST API is not there in API-M 1.10. >> >> Using the following command I can get a registry resource in API-M 1.10 >> >> curl -X GET -k -H "Authorization:Basic YWRtaW46YWRtaW4=" " >> https://127.0.0.1:9443/registry/resource/_system/governance >> /apimgt/applicationdata/provider/admin/CalculatorAPI/ >> 1.0/in/cal_log_in_message" >> >> Similarly, how can I add/update a resource? >> >> Thanks. >> >> On Sun, Mar 12, 2017 at 11:29 PM, Rajkumar Rajaratnam <rajkum...@wso2.com >> > wrote: >> >>> Hi, >>> >>> I'm referring [1] and trying to add a registry resource using registry >>> REST API in API Manager 1.10 using the following command. >>> >>> curl -X PUT -k -H "Authorization:Basic YWRtaW46YWRtaW4=" -H >>> "Content-Type: application/xml" -H "Media-Type: application/xml" -d >>> @cal_log_in_message.xml "https://127.0.0.1:9443/resour >>> ce/1.0.0/artifact/_system/governance/apimgt/applicationdata/ >>> provider/admin/CalculatorAPI/1.0/in/cal_log_in_message" >>> >>> It's not working. Here is the response. >>> >>> raj@raj-Latitude-E6540:~/workspace$ curl -i -X PUT -k -H >>> "Authorization:Basic YWRtaW46YWRtaW4=" -H "Content-Type: application/xml" >>> -H "Media-Type: application/xml" -d @cal_log_in_message.xml " >>> https://127.0.0.1:9443/resource/1.0.0/artifact/_system/gove >>> rnance/apimgt/applicationdata/provider/admin/CalculatorAPI/ >>> 1.0/in/cal_log_in_message" >>> HTTP/1.1 302 Found >>> Set-Cookie: JSESSIONID=1A4DC76C0BB20201DF5C416D5B7105FE; Path=/; >>> Secure; HttpOnly >>> Set-Cookie: requestedURI=../../resource/1.0.0/artifact/_system/governanc >>> e/apimgt/applicationdata/provider/admin/CalculatorAPI/1.0/in/cal_log_in_message; >>> Path=/ >>> Location: https://127.0.0.1:9443/carbon/admin/login.jsp >>> Content-Type: text/html;charset=UTF-8 >>> Content-Length: 0 >>> Date: Mon, 13 Mar 2017 03:22:18 GMT >>> Server: WSO2 Carbon Server >>> >>> Can you please advise how to do it in API-M 1.10? >>> >>> [1] https://docs.wso2.com/display/Governance510/Resources+with+REST+API >>> >>> Thanks, >>> Raj. >>> >>> -- >>> Rajkumar Rajaratnam >>> Committer & PMC Member, Apache Stratos >>> Senior Software Engineer, WSO2 >>> >>> LinkedIn: https://lk.linkedin.com/in/rajuu >>> Mobile: +1 408 791 7640 <(408)%20791-7640> >>> Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech >>> >> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Senior Software Engineer, WSO2 >> >> LinkedIn: https://lk.linkedin.com/in/rajuu >> Mobile: +1 408 791 7640 <(408)%20791-7640> >> Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech >> > > > > -- > Shazni Nazeer > Associate Technical Lead | WSO2 > > Mob : +94 37331 > LinkedIn : http://lk.linkedin.com/in/shazninazeer > Blog : http://shazninazeer.blogspot.com > > <http://wso2.com/signature> > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn: https://lk.linkedin.com/in/rajuu Mobile: +1 408 791 7640 Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I add a registry resource using registry REST API?
It seems registry REST API is not there in API-M 1.10. Using the following command I can get a registry resource in API-M 1.10 curl -X GET -k -H "Authorization:Basic YWRtaW46YWRtaW4=" " https://127.0.0.1:9443/registry/resource/_system/governance/apimgt/applicationdata/provider/admin/CalculatorAPI/1.0/in/cal_log_in_message " Similarly, how can I add/update a resource? Thanks. On Sun, Mar 12, 2017 at 11:29 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Hi, > > I'm referring [1] and trying to add a registry resource using registry > REST API in API Manager 1.10 using the following command. > > curl -X PUT -k -H "Authorization:Basic YWRtaW46YWRtaW4=" -H "Content-Type: > application/xml" -H "Media-Type: application/xml" -d > @cal_log_in_message.xml "https://127.0.0.1:9443/resource/1.0.0/artifact/_ > system/governance/apimgt/applicationdata/provider/ > admin/CalculatorAPI/1.0/in/cal_log_in_message" > > It's not working. Here is the response. > > raj@raj-Latitude-E6540:~/workspace$ curl -i -X PUT -k -H > "Authorization:Basic YWRtaW46YWRtaW4=" -H "Content-Type: application/xml" > -H "Media-Type: application/xml" -d @cal_log_in_message.xml " > https://127.0.0.1:9443/resource/1.0.0/artifact/_system/governance/apimgt/ > applicationdata/provider/admin/CalculatorAPI/1.0/in/cal_log_in_message" > HTTP/1.1 302 Found > Set-Cookie: JSESSIONID=1A4DC76C0BB20201DF5C416D5B7105FE; Path=/; Secure; > HttpOnly > Set-Cookie: requestedURI=../../resource/1.0.0/artifact/_system/ > governance/apimgt/applicationdata/provider/admin/CalculatorAPI/1.0/in/cal_log_in_message; > Path=/ > Location: https://127.0.0.1:9443/carbon/admin/login.jsp > Content-Type: text/html;charset=UTF-8 > Content-Length: 0 > Date: Mon, 13 Mar 2017 03:22:18 GMT > Server: WSO2 Carbon Server > > Can you please advise how to do it in API-M 1.10? > > [1] https://docs.wso2.com/display/Governance510/Resources+with+REST+API > > Thanks, > Raj. > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Senior Software Engineer, WSO2 > > LinkedIn: https://lk.linkedin.com/in/rajuu > Mobile: +1 408 791 7640 <(408)%20791-7640> > Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn: https://lk.linkedin.com/in/rajuu Mobile: +1 408 791 7640 Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How can I add a registry resource using registry REST API?
Hi, I'm referring [1] and trying to add a registry resource using registry REST API in API Manager 1.10 using the following command. curl -X PUT -k -H "Authorization:Basic YWRtaW46YWRtaW4=" -H "Content-Type: application/xml" -H "Media-Type: application/xml" -d @cal_log_in_message.xml " https://127.0.0.1:9443/resource/1.0.0/artifact/_system/governance/apimgt/applicationdata/provider/admin/CalculatorAPI/1.0/in/cal_log_in_message " It's not working. Here is the response. raj@raj-Latitude-E6540:~/workspace$ curl -i -X PUT -k -H "Authorization:Basic YWRtaW46YWRtaW4=" -H "Content-Type: application/xml" -H "Media-Type: application/xml" -d @cal_log_in_message.xml " https://127.0.0.1:9443/resource/1.0.0/artifact/_system/governance/apimgt/applicationdata/provider/admin/CalculatorAPI/1.0/in/cal_log_in_message " HTTP/1.1 302 Found Set-Cookie: JSESSIONID=1A4DC76C0BB20201DF5C416D5B7105FE; Path=/; Secure; HttpOnly Set-Cookie: requestedURI=../../resource/1.0.0/artifact/_system/governance/apimgt/applicationdata/provider/admin/CalculatorAPI/1.0/in/cal_log_in_message; Path=/ Location: https://127.0.0.1:9443/carbon/admin/login.jsp Content-Type: text/html;charset=UTF-8 Content-Length: 0 Date: Mon, 13 Mar 2017 03:22:18 GMT Server: WSO2 Carbon Server Can you please advise how to do it in API-M 1.10? [1] https://docs.wso2.com/display/Governance510/Resources+with+REST+API Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn: https://lk.linkedin.com/in/rajuu Mobile: +1 408 791 7640 Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0
Hi Pubudu, Thanks for the response. My question is bit different. We have a requirement that we want to make sure the official patches released by WSO2 should be applied to the nodes. That means, we should be able to specify the the checksum of the official patches in hiera or whatever and verify the checksum of the patches before applying it to the nodes. I think with the current puppet modules, it's not possible to do, as we copy all patches found inside /files folder to the nodes. But if we want to have this feature, then we need to define a resource per patch, I think that's not scalable or maintainable. Thanks, Raj. On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Raj, > > Yes, we do. Basically, when copying files or templates puppet checks the > checksum by default. We haven't done anything specifically to verify > checksum in files in our puppet modules. > > Thank you! > > On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi Pubudu, >> >> Do we support verifying checksum when applying patches, in latest puppet >> modules? >> >> Thanks, >> Raj. >> >> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka <pubu...@wso2.com> >> wrote: >> >>> Hi Devs, >>> >>> We are currently doing final testing for releasing puppet-base [1] and >>> puppet-common [2] repositories. Once these repos are released, puppet-apim, >>> puppet-iot and puppet-is can be released for latest product versions. >>> Please let us know if you have any concerns. >>> >>> [1] - https://github.com/wso2/puppet-base >>> [2] - https://github.com/wso2/puppet-common >>> >>> Thank you! >>> -- >>> *Pubudu Gunatilaka* >>> Committer and PMC Member - Apache Stratos >>> Software Engineer >>> WSO2, Inc.: http://wso2.com >>> mobile : +94774078049 <%2B94772207163> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Senior Software Engineer, WSO2 >> >> LinkedIn : https://lk.linkedin.com/in/rajuu >> Mobile : +94777568639 <+94%2077%20756%208639> >> > > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn : https://lk.linkedin.com/in/rajuu Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0
Hi Pubudu, Do we support verifying checksum when applying patches, in latest puppet modules? Thanks, Raj. On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Devs, > > We are currently doing final testing for releasing puppet-base [1] and > puppet-common [2] repositories. Once these repos are released, puppet-apim, > puppet-iot and puppet-is can be released for latest product versions. > Please let us know if you have any concerns. > > [1] - https://github.com/wso2/puppet-base > [2] - https://github.com/wso2/puppet-common > > Thank you! > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn : https://lk.linkedin.com/in/rajuu Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC2
Hi Abimaran, I'm sorry I couldn't understand the context of what you are saying. I was reporting that IDP initiated SSO is not working (login to IDP first and let IDP to redirect user to SP). Thanks. On Thu, Jan 12, 2017 at 1:59 AM Abimaran Kugathasan <abima...@wso2.com> wrote: > Hi Rajkumar, > > On Wed, Jan 11, 2017 at 11:08 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > > IDP initiated SSO for Store is also not working. Should be the same case > with Publisher. Reason for this issue is as below. > > For SP initiated SSO, we read SSO properties from site.json and set them > to SSO relaying party object in sso/filter [1]. > > For IDP initiated SSO, the same thing should be done in jaggery_acs.jag. > Why?, because the very first request to API Store will land on > jaggery_acs.jag and since SSO properties are not there in SSO relaying > party object, you will get NPE like below. > > > > > Why should someone allowed to hit SP, if IDP initiated SSO configured? I > do understand the annonymous access API Manager should allowed for API > Srore, but, when someone requested to login, don't we redirect to IDP login? > > > > > [2017-01-11 12:34:07,151] ERROR - Util Error when getting key store of > tenant carbon.super > java.lang.NullPointerException > at java.io.File.(File.java:277) > at > org.wso2.carbon.hostobjects.sso.internal.util.Util.validateSignature(Util.java:281) > at > org.wso2.carbon.hostobjects.sso.SAMLSSORelyingPartyObject.jsFunction_validateSignature(SAMLSSORelyingPartyObject.java:168) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126) > at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386) > at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32) > at > org.jaggeryjs.rhino.store.jagg.c0._c_anonymous_1(/store/jagg/jaggery_acs.jag:70) > at org.jaggeryjs.rhino.store.jagg.c0.call(/store/jagg/jaggery_acs.jag) > at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23) > at > org.jaggeryjs.rhino.store.jagg.c0._c_script_0(/store/jagg/jaggery_acs.jag:5) > at org.jaggeryjs.rhino.store.jagg.c0.call(/store/jagg/jaggery_acs.jag) > at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394) > at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091) > at org.jaggeryjs.rhino.store.jagg.c0.call(/store/jagg/jaggery_acs.jag) > at org.jaggeryjs.rhino.store.jagg.c0.exec(/store/jagg/jaggery_acs.jag) > at > org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567) > at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273) > at > org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(WebAppManager.java:588) > at > org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:508) > at org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:650) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:747) > at > org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:485) > at > org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:377) > at > org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:337) > at org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.wso2.carbon.ui.filters.cache.ContentTypeBasedCachePreventionFilter.doFilter(ContentTypeBasedCachePreventionFilter.java:53) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:120) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja
Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC2
nload, test the product and vote. The vote will be open >>>>>>> for 72 hours or as needed. >>>>>>> >>>>>>> Source and distribution >>>>>>> >>>>>>> Run-time : https://github.com/wso2/prod >>>>>>> uct-apim/releases/download/v2.1.0-rc2/wso2am-2.1.0-RC2.zip >>>>>>> Analytics : https://github.com/wso2/anal >>>>>>> ytics-apim/releases/download/v2.1.0-rc2/wso2am-analytics-2.1 >>>>>>> .0-RC2.zip >>>>>>> Tooling : https://github.com/wso2/devs >>>>>>> tudio-tooling-apim/releases/tag/v2.1.0-rc2 >>>>>>> >>>>>>> >>>>>>> This release fixes the following issues: >>>>>>> Runtime : https://wso2.org/jira/issues/?filter=13623 >>>>>>> Analytics : https://wso2.org/jira/issues/?filter=13624 >>>>>>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1 >>>>>>> >>>>>>> >>>>>>> Please vote as follows. >>>>>>> [+] Stable - go ahead and release >>>>>>> [-] Broken - do not release (explain why) >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> - WSO2 API Manager Team - >>>>>>> >>>>>>> -- >>>>>>> Malintha Amarasinghe >>>>>>> Software Engineer >>>>>>> *WSO2, Inc. - lean | enterprise | middleware* >>>>>>> http://wso2.com/ >>>>>>> >>>>>>> Mobile : +94 712383306 <+94%2071%20238%203306> >>>>>>> >>>>>>> ___ >>>>>>> Architecture mailing list >>>>>>> architect...@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Chamila Adhikarinayake >>>>>> Software Engineer >>>>>> WSO2, Inc. >>>>>> Mobile - +94712346437 <+94%2071%20234%206437> >>>>>> Email - chami...@wso2.com >>>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>>> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> architect...@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Tharindu Dharmarathna*Software Engineer >>>>> WSO2 Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> mobile: *+94779109091 <+94%2077%20910%209091>* >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> architect...@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Arshardh Ifthikar* >>>> Trainee Software Engineer >>>> WSO2, Inc. >>>> Mobile: +94719806525 <+94%2071%20980%206525> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> *Praminda Jayawardana* >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918> >>> >>> ___ >>> Architecture mailing list >>> architect...@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Thanks >> Abimaran Kugathasan >> Senior Software Engineer - API Technologies >> >> Email : abima...@wso2.com >> Mobile : +94 773922820 <+94%2077%20392%202820> >> >> <http://stackoverflow.com/users/515034> >> <http://lk.linkedin.com/in/abimaran> >> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >> <https://twitter.com/abimaran> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Malintha Amarasinghe > Software Engineer > *WSO2, Inc. - lean | enterprise | middleware* > http://wso2.com/ > > Mobile : +94 712383306 <+94%2071%20238%203306> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 LinkedIn : https://lk.linkedin.com/in/rajuu Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB 5] Access Response JSON Payload in a Class Mediator
On Thu, Oct 27, 2016 at 9:42 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
wrote:
> Hi Isuru,
>
> I think you have to build the message first and call
> jsonPayloadToString(). Try this.
>
> try {
>RelayUtils.buildMessage(a2mc);
> } catch (IOException | XMLStreamException e) {
>log.error("Error occurred while building the message", e);
> }
>
> JsonUtil.jsonPayloadToString(a2mc);
>
This code worked for me in AM 1.10.
>
>
> Also make sure you are using org.apache.synapse.commons.json.
> JsonStreamFormatter/org.apache.synapse.commons.json.JsonStreamBuilder for
> application/json.
>
> Thanks,
> Raj.
>
> On Thu, Oct 27, 2016 at 9:28 AM, Rajith Vitharana <raji...@wso2.com>
> wrote:
>
>> Hi Isuru,
>>
>> Below [1] worked for me to retrieve jsonbody. And then to set it back,
>> what you did worked for me. IE [2]
>>
>> [1] - StringBuilder json = JsonUtil.toJsonString(synCtx.g
>> etEnvelope().getBody());
>> [2] - JsonUtil.getNewJsonPayload(
>> ((Axis2MessageContext) synCtx).getAxis2MessageContext
>> (),
>> transformedJson, true, true);
>>
>> Thanks,
>>
>> On 27 October 2016 at 17:55, Isuru Haththotuwa <isu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> How to do $subject? Need to modify the response payload from BE and send
>>> it to the client.
>>>
>>> Tried [1], but did not work.
>>>
>>> [1].
>>>String jsonPayloadToString = JsonUtil
>>> .jsonPayloadToString(((Axis2MessageContext)
>>> messageContext)
>>> .getAxis2MessageContext());
>>> try {
>>> JsonUtil.getNewJsonPayload(((Axis2MessageContext)
>>> messageContext).getAxis2MessageContext(),
>>> jsonPayloadToString, true, true);
>>> } catch (AxisFault axisFault) {
>>> log.error("Error building aggregated JSON payload",
>>> axisFault);
>>> return false;
>>> }
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>>
>>> _______
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajith Vitharana
>>
>> Senior Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94715883223
>> Blog : http://lankavitharana.blogspot.com/
>> <http://wso2.com/signature>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
> Mobile : +94777568639
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB 5] Access Response JSON Payload in a Class Mediator
Hi Isuru,
I think you have to build the message first and call jsonPayloadToString().
Try this.
try {
RelayUtils.buildMessage(a2mc);
} catch (IOException | XMLStreamException e) {
log.error("Error occurred while building the message", e);
}
JsonUtil.jsonPayloadToString(a2mc);
Also make sure you are using
org.apache.synapse.commons.json.JsonStreamFormatter/org.apache.synapse.commons.json.JsonStreamBuilder
for application/json.
Thanks,
Raj.
On Thu, Oct 27, 2016 at 9:28 AM, Rajith Vitharana <raji...@wso2.com> wrote:
> Hi Isuru,
>
> Below [1] worked for me to retrieve jsonbody. And then to set it back,
> what you did worked for me. IE [2]
>
> [1] - StringBuilder json = JsonUtil.toJsonString(synCtx.
> getEnvelope().getBody());
> [2] - JsonUtil.getNewJsonPayload(
> ((Axis2MessageContext) synCtx).
> getAxis2MessageContext(),
> transformedJson, true, true);
>
> Thanks,
>
> On 27 October 2016 at 17:55, Isuru Haththotuwa <isu...@wso2.com> wrote:
>
>> Hi,
>>
>> How to do $subject? Need to modify the response payload from BE and send
>> it to the client.
>>
>> Tried [1], but did not work.
>>
>> [1].
>>String jsonPayloadToString = JsonUtil
>> .jsonPayloadToString(((Axis2MessageContext)
>> messageContext)
>> .getAxis2MessageContext());
>> try {
>> JsonUtil.getNewJsonPayload(((Axis2MessageContext)
>> messageContext).getAxis2MessageContext(),
>> jsonPayloadToString, true, true);
>> } catch (AxisFault axisFault) {
>> log.error("Error building aggregated JSON payload",
>> axisFault);
>> return false;
>> }
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajith Vitharana
>
> Senior Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94715883223
> Blog : http://lankavitharana.blogspot.com/
> <http://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Controlling access to jaggery pages by permissions
Hi Thanuja, I had a look at the way IS dashboard jaggery app restricts access to features by permissions. - It uses "*getUserInfo*" method of "*LoggedUserInfoAdmin*" admin service to retrieve all the permissions of the loggedin user and put them in the session. - Since it retrieves all the permissions of the loggedin user only once (at login time) and holds them in the session, it reduces the number of network calls and improves the performance. - It uses session cookie to invoke admin services Hence, I thought of following the same approach because it gives better performance than my previous approach. In order to call "*getUserInfo*" method of "*LoggedUserInfoAdmin*" admin service, the loggedin user should have "*/permission/admin/login*" permission. Is there any issue with assigning this permission to all the users? Thanks, Raj. On Sun, Jul 17, 2016 at 5:19 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Thanks Thanuja for the response. Will follow the current approach. > > On Fri, Jul 15, 2016 at 7:35 PM, Thanuja Jayasinghe <than...@wso2.com> > wrote: > >> >> >> On Fri, Jul 15, 2016 at 3:56 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I have a jaggery app with some pages and secured them via SAML SSO with >>> WSO2 IS. So the authentication is implemented, now I have to implement the >>> authorization. I need to control access to these jaggery pages by >>> roles/permissions of the loggedin user. Here is the approach I have >>> followed and I need to validate whether it is okay or there are better >>> ways. >>> >>>1. Created custom permissions under my application service provider >>>(one permission per one feature in my jaggery app) >>>2. When a user access a feature in the jaggery app, I am calling " >>>*isUserAuthorized*" method of "*RemoteAuthorizationManagerService*" >>>admin service to check whether the logged in user is authorized to access >>>the page. I think "isUserAuthorized" method checks whether the given user >>>has any roles with the given permission. So, if it returns true, then I >>>allow the user to access the page. >>>3. I am calling the admin service with basic authentication. Is >>>there any issues with this approach? Do I need to obtain a session cookie >>>and call the admin service using session cookie instead of >>>username/password? What is the recommended approach? >>> >>> Any issues with this approach? >>> >> Since "isUserAuthorized" method of "RemoteAuthorizationManagerService" >> requires "/permission/admin/configure/security" permission, a user >> without this permission will not able to access this service using his >> session cookie. So your current approach is correct. >> >>> Thanks, >>> Raj. >>> >>> -- >>> Rajkumar Rajaratnam >>> Committer & PMC Member, Apache Stratos >>> Senior Software Engineer, WSO2 >>> >>> Mobile : +94777568639 >>> >> >> Thanks, >> >> -- >> *Thanuja Lakmal* >> Senior Software Engineer >> WSO2 Inc. http://wso2.com/ >> *lean.enterprise.middleware* >> Mobile: +94715979891 +94758009992 >> > > > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Senior Software Engineer, WSO2 > > Mobile : +94777568639 > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Controlling access to jaggery pages by permissions
Thanks Thanuja for the response. Will follow the current approach. On Fri, Jul 15, 2016 at 7:35 PM, Thanuja Jayasinghe <than...@wso2.com> wrote: > > > On Fri, Jul 15, 2016 at 3:56 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi, >> >> I have a jaggery app with some pages and secured them via SAML SSO with >> WSO2 IS. So the authentication is implemented, now I have to implement the >> authorization. I need to control access to these jaggery pages by >> roles/permissions of the loggedin user. Here is the approach I have >> followed and I need to validate whether it is okay or there are better >> ways. >> >>1. Created custom permissions under my application service provider >>(one permission per one feature in my jaggery app) >>2. When a user access a feature in the jaggery app, I am calling " >>*isUserAuthorized*" method of "*RemoteAuthorizationManagerService*" >>admin service to check whether the logged in user is authorized to access >>the page. I think "isUserAuthorized" method checks whether the given user >>has any roles with the given permission. So, if it returns true, then I >>allow the user to access the page. >>3. I am calling the admin service with basic authentication. Is there >>any issues with this approach? Do I need to obtain a session cookie and >>call the admin service using session cookie instead of username/password? >>What is the recommended approach? >> >> Any issues with this approach? >> > Since "isUserAuthorized" method of "RemoteAuthorizationManagerService" > requires "/permission/admin/configure/security" permission, a user > without this permission will not able to access this service using his > session cookie. So your current approach is correct. > >> Thanks, >> Raj. >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Senior Software Engineer, WSO2 >> >> Mobile : +94777568639 >> > > Thanks, > > -- > *Thanuja Lakmal* > Senior Software Engineer > WSO2 Inc. http://wso2.com/ > *lean.enterprise.middleware* > Mobile: +94715979891 +94758009992 > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Controlling access to jaggery pages by permissions
Hi, I have a jaggery app with some pages and secured them via SAML SSO with WSO2 IS. So the authentication is implemented, now I have to implement the authorization. I need to control access to these jaggery pages by roles/permissions of the loggedin user. Here is the approach I have followed and I need to validate whether it is okay or there are better ways. 1. Created custom permissions under my application service provider (one permission per one feature in my jaggery app) 2. When a user access a feature in the jaggery app, I am calling " *isUserAuthorized*" method of "*RemoteAuthorizationManagerService*" admin service to check whether the logged in user is authorized to access the page. I think "isUserAuthorized" method checks whether the given user has any roles with the given permission. So, if it returns true, then I allow the user to access the page. 3. I am calling the admin service with basic authentication. Is there any issues with this approach? Do I need to obtain a session cookie and call the admin service using session cookie instead of username/password? What is the recommended approach? Any issues with this approach? Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [BPS] Getting a list of user roles
Hi Amal, On Sun, Jun 5, 2016 at 5:36 PM, Amal Gunatilake <am...@wso2.com> wrote: > Hi Manu, > > I would like to add one more suggestion, if the UI is getting built on > Jaggery or if there is a chance on using it, then you can use the built-in > functionality[1] to easily access the user management service. > Just to clarify, is this built-in user-mgt API capable of talking to remote IS? I can't see how it authenticates to the remote IS from the doc. Any idea? [1] Thanks, Raj. > > [1] http://jaggeryjs.org/documentation.jag?api=UserManager > > Best regards, > Amal. > > On Sun, Jun 5, 2016 at 9:53 PM, Hasitha Aravinda <hasi...@wso2.com> wrote: > >> >> Hi Manu, >> >> On Wed, Jun 1, 2016 at 11:56 PM, Manuranga Perera <m...@wso2.com> wrote: >> >>> What are the ways to get a list of user roles in BPS to display in UI. >>> What I can think of are : >>> 1. Use the user mgt web service >>> >>> >>> >>> >> >> T >> his is possible option in default pack. >> >> >> >>> 2. Use embedded LDAP. Do we ship embedded LDAP (like in IS) with BPS ? >>> >> >> >> >> In default pack, BPS doesn't include >> >> RemoteUserStoreManagerService >> >> [1] which is provided by IS. >> >> But this service >> >> provides much cleaner >> >> operations than >> >> which user-mgt service >> p >> rovides >> >> . >> >> If >> >> you can install >> >> RemoteUserStoreManagerService >> >> in BPS, I think better >> option is to use this services instead of user-mgt web service. >> >> >> [1] - >> https://docs.wso2.com/display/IS510/Managing+Users+and+Roles+with+APIs >> >> >> >>> Is there a better way? eg: a REST API ? >>> >> >> >> >> We haven't exposed this as an API in BPMN rest API. >> >> Thanks, >> Hasitha. >> >> >>> -- >>> With regards, >>> *Manu*ranga Perera. >>> >>> phone : 071 7 70 20 50 >>> mail : m...@wso2.com >>> >> >> >> >> -- >> -- >> Hasitha Aravinda, >> Associate Technical Lead, >> WSO2 Inc. >> Email: hasi...@wso2.com >> Mobile : +94 718 210 200 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Amal Gunatilake* > WSO2 Inc.; http://wso2.com > Lean . Enterprise . Middleware > > mobile: (+94) 773561195 > blog: amalg-blogs.blogspot.com; twitter: @daag123 > linkedIn: https://www.linkedin.com/in/amalgunatilake > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CEP] How to concatenate a string with a double quote using str:concat extension function?
Hi Dilini,
Thank you very much for the detailed explanation. Yes, I can do that in ESB
layer and send the concatenated string to CEP.
Thanks,
Raj.
On Tue, Jun 14, 2016 at 4:02 PM, Dilini Muthumala <dil...@wso2.com> wrote:
> Hi Raj,
>
> When Siddhi Compiler Tokenize a String Literal (like "t\"est" ),
> AFAIK it does not escape characters when seeing '\'. So it will read '\'
> character as just another character.
> So adding an escape character will not work.
>
> Also the Siddhi Grammar does not allow a String Literal to contain a quote
> character (' " ' or ' ' ')
> If we put such a character, the query compilation will fail.
>
> For example,
> Following query compilation will fail because "pa\"rt1" contains ' " '
> character. ('\' character will be read as a part of the String Literal)
>
>
> //-
> from inputStream
> select symbol1 , str:concat("pa\"rt1","part2") as concatString
> insert into outputStream;
>
> //-
>
> However,
> concat function *can* process String Literals with quotes.
> So, if you somehow send a String Literal (with quotes) to the Concat
> function, then concat function has no issue with processing it.
>
> For example, following query compilation will be successful,
>
> //-
> define stream inputStream (symbol1 string, symbol2 string);
>
> @info(name = 'query1')
> from inputStream
> select str:concat(symbol1,symbol2) as concatString
> insert into outputStream;
>
> //-----
>
> and if you send an inputStream event:
> symbol1=AAA
> symbol2=B"B
>
> You will get the result (concatString):
> AAAB"B
>
> Thanks,
> Dilini
>
> On Tue, Jun 14, 2016 at 2:54 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> Hi,
>>
>> $Subject please. Escaping character doesn't seems to be working.
>>
>> Thanks,
>> Raj.
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Senior Software Engineer, WSO2
>>
>> Mobile : +94777568639
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dilini Muthumala*
> Senior Software Engineer,
> WSO2 Inc.
>
> *E-mail :* dil...@wso2.com
> *Mobile: *+94 713-400-029
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [CEP] How to concatenate a string with a double quote using str:concat extension function?
Hi, $Subject please. Escaping character doesn't seems to be working. Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Senior Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have gmail and gmailRest connector?
Okay, thanks Hariprasath.
On Sun, Jun 5, 2016 at 4:14 PM, Hariprasath Thanarajah <haripras...@wso2.com
> wrote:
> Hi Rajkumar,
>
> Yes It was happened like your comment.
>
> Refer subject [1]
> [1] - Removing wso2-extension-gmail and rename
> wso2-extension-{gmailRest->gmail}
>
> On Sun, Jun 5, 2016 at 8:28 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I couldn't find gmailRest connector in the store. I think, it is renamed
>> to gmail connector and the old gmail connector is removed from the store?
>>
>> Thanks,
>> Raj.
>>
>> On Thu, May 26, 2016 at 10:49 AM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> +1 Latest connector only support all the integration use cases and
>>> seamless refresh token logic. No point keeping the the previous one
>>> since this is done at early stage.
>>>
>>> On Thu, May 26, 2016 at 2:38 PM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Currently we have two connector for gmail operations with ESB [1]
>>>>
>>>> gmail connector was implemented by using sdk and the gmailRest
>>>> connector has implemented using REST api and gmailRest connector has more
>>>> methods than gmail connector and has released with input and output schema
>>>> as well.
>>>>
>>>> Use cases covered by gmail is already covered with gmailRest in
>>>> addition to new methods.
>>>>
>>>> Can we deprecate the gmail connector?
>>>>
>>>> [1] - https://store.wso2.com/store/assets/esbconnector/?query=gmail
>>>>
>>>> --
>>>>
>>>>
>>>> *Thank you and Regards**Hariprasath Thanarajah*
>>>> Associate Software Engineer | WSO2
>>>> E: haripras...@wso2.com
>>>> M: +94752806528, 0777216903
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> <http://wso2.com/about/team/malaka-silva/>
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>>
>
>
>
> --
>
>
> *Thank you and Regards**Hariprasath Thanarajah*
> Associate Software Engineer | WSO2
> E: haripras...@wso2.com
> M: +94752806528, 0777216903
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have gmail and gmailRest connector?
Hi, I couldn't find gmailRest connector in the store. I think, it is renamed to gmail connector and the old gmail connector is removed from the store? Thanks, Raj. On Thu, May 26, 2016 at 10:49 AM, Malaka Silva <mal...@wso2.com> wrote: > +1 Latest connector only support all the integration use cases and > seamless refresh token logic. No point keeping the the previous one since > this is done at early stage. > > On Thu, May 26, 2016 at 2:38 PM, Hariprasath Thanarajah < > haripras...@wso2.com> wrote: > >> Hi, >> >> Currently we have two connector for gmail operations with ESB [1] >> >> gmail connector was implemented by using sdk and the gmailRest connector >> has implemented using REST api and gmailRest connector has more methods >> than gmail connector and has released with input and output schema as well. >> >> Use cases covered by gmail is already covered with gmailRest in addition >> to new methods. >> >> Can we deprecate the gmail connector? >> >> [1] - https://store.wso2.com/store/assets/esbconnector/?query=gmail >> >> -- >> >> >> *Thank you and Regards**Hariprasath Thanarajah* >> Associate Software Engineer | WSO2 >> E: haripras...@wso2.com >> M: +94752806528, 0777216903 >> >> > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can we manually create a "Token" object and pass it to "sendOAuthRequest" method of Jaggery's "OAuth" module?
Hi Geesara,
I'm talking about SAML2 grant type. I don't think the above doc explain how
to construct a token object from the accessTokenResponse object returned
when we exchange a SAML2 token with an OAuth token.
Thanks,
Raj
On Monday, 16 May 2016, Geesara Prathap <gees...@wso2.com> wrote:
> Hi Rajkumar,
>
> Yes, The way an *oauth2Token* object is created is wrong. Please follow this
> sample implementation <http://jaggeryjs.org/documentation.jag?api=oauth>
> which explains how to construct an oauth2Token object.
>
> 1. http://jaggeryjs.org/documentation.jag?api=oauth
>
> Thanks,
> Geesara
>
> On Sun, May 15, 2016 at 12:31 AM, Rajkumar Rajaratnam <rajkum...@wso2.com
> <javascript:_e(%7B%7D,'cvml','rajkum...@wso2.com');>> wrote:
>
>> Hi,
>>
>> I am exchanging a SAML token with OAuth token using "getTokenResponse"
>> method [1] of Jaggery's "OAuth" module. This method will return
>> "AccessTokenResponse"
>> object. But "sendOAuthRequest" method expects a "Token" object. Hence, I am
>> manually creating "Token" object and passing it to "sendOAuthRequest"
>> method, as shown below. I am referring [2] to create a "Token" object
>> manually.
>>
>>
>>
>>
>>
>>
>> *var accessTokenResponse =
>> oauthProvider.getTokenResponse(samlResp);accessToken =
>> accessTokenResponse.getAccessToken();var oauth2Token = {};
>> oauth2Token.token = accessToken;oauth2Token.secret =
>> "PkxikDuusEi67VpuqK7gpsLJlYIa";var response =
>> **oauthProvider.sendOAuthRequest(oauth2Token,
>> "GET", "https://xx.xx.xx.xx:8251/bpmn/1.0.0/repository/deployments
>> <https://xx.xx.xx.xx:8251/bpmn/1.0.0/repository/deployments>");*
>>
>> But I am getting the following exception when executing this block. I
>> think this exception is thrown from here [3].
>>
>> JavaException: org.jaggeryjs.scriptengine.exceptions.ScriptException:
>> Invalid Access Token
>>
>> I think something is wrong with constructing the "Token" object. Any
>> pointers?
>>
>> [1]
>> https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L211-L238
>> [2]
>> http://grepcode.com/file/repo1.maven.org/maven2/org.scribe/scribe/1.2.3/org/scribe/model/Token.java#Token.0token
>> [3]
>> https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L149
>>
>> Thanks,
>> Raj.
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>>
>
>
>
> --
> Geesara Prathap Kulathunga
> Software Engineer
> WSO2 Inc; http://wso2.com
> Mobile : +940772684174
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do we call "sendOAuthRequest" method of Jaggery's "OAuth" module with payload
Yes, it seems not supported. I have used Jaggery post() as an alternative. Thanks, Raj. On Mon, May 16, 2016 at 8:16 PM, Geesara Prathap <gees...@wso2.com> wrote: > Hi Rajkumar, > > Just looked into the implementation of "sendOAuthRequest"[1]. Seems to be > it does support only for the GET requests only. > > So if you have an access token, please refer to this implementation[2] > how to send a request to some APIs which is secured with OAuth. > > > 1. > https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L137 > 2. > https://github.com/wso2/carbon-dashboards/blob/master/apps/portal/controllers/apis/RESTClientInvoker.jag#L105 > > Thanks, > Geesara > > > On Tue, May 17, 2016 at 12:15 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi Geesara, >> >> No, it doesn't help. I am asking how we can pass a payload and send a >> POST request using "sendOAuthRequest" method. I don't think it is >> documented in above link. >> >> Thanks, >> Raj. >> >> On Mon, May 16, 2016 at 7:36 PM, Geesara Prathap <gees...@wso2.com> >> wrote: >> >>> Hi Rajkumar, >>> >>> >>> I hope this[1] <http://jaggeryjs.org/documentation.jag?api=oauth> will >>> help. >>> >>> 1. http://jaggeryjs.org/documentation.jag?api=oauth >>> >>> Thanks, >>> Geesara >>> >>> >>> On Mon, May 16, 2016 at 7:50 PM, Manuranga Perera <m...@wso2.com> wrote: >>> >>>> looping >>>> >>>> On Sat, May 14, 2016 at 2:45 PM, Rajkumar Rajaratnam < >>>> rajkum...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I am talking about [1]. >>>>> >>>>> Couldn't find any documentation or samples on this. How do we call >>>>> "sendOAuthRequest" method of Jaggery's "OAuth" module with POST payload? >>>>> >>>>> [1] >>>>> https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L141-L192 >>>>> >>>>> Thanks, >>>>> Raj. >>>>> >>>>> -- >>>>> Rajkumar Rajaratnam >>>>> Committer & PMC Member, Apache Stratos >>>>> Software Engineer, WSO2 >>>>> >>>>> Mobile : +94777568639 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> With regards, >>>> *Manu*ranga Perera. >>>> >>>> phone : 071 7 70 20 50 >>>> mail : m...@wso2.com >>>> >>> >>> >>> >>> -- >>> Geesara Prathap Kulathunga >>> Software Engineer >>> WSO2 Inc; http://wso2.com >>> Mobile : +940772684174 >>> >>> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> > > > > -- > Geesara Prathap Kulathunga > Software Engineer > WSO2 Inc; http://wso2.com > Mobile : +940772684174 > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do we call "sendOAuthRequest" method of Jaggery's "OAuth" module with payload
Hi Geesara, No, it doesn't help. I am asking how we can pass a payload and send a POST request using "sendOAuthRequest" method. I don't think it is documented in above link. Thanks, Raj. On Mon, May 16, 2016 at 7:36 PM, Geesara Prathap <gees...@wso2.com> wrote: > Hi Rajkumar, > > > I hope this[1] <http://jaggeryjs.org/documentation.jag?api=oauth> will > help. > > 1. http://jaggeryjs.org/documentation.jag?api=oauth > > Thanks, > Geesara > > > On Mon, May 16, 2016 at 7:50 PM, Manuranga Perera <m...@wso2.com> wrote: > >> looping >> >> On Sat, May 14, 2016 at 2:45 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I am talking about [1]. >>> >>> Couldn't find any documentation or samples on this. How do we call >>> "sendOAuthRequest" method of Jaggery's "OAuth" module with POST payload? >>> >>> [1] >>> https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L141-L192 >>> >>> Thanks, >>> Raj. >>> >>> -- >>> Rajkumar Rajaratnam >>> Committer & PMC Member, Apache Stratos >>> Software Engineer, WSO2 >>> >>> Mobile : +94777568639 >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : m...@wso2.com >> > > > > -- > Geesara Prathap Kulathunga > Software Engineer > WSO2 Inc; http://wso2.com > Mobile : +940772684174 > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How can we manually create a "Token" object and pass it to "sendOAuthRequest" method of Jaggery's "OAuth" module?
Hi,
I am exchanging a SAML token with OAuth token using "getTokenResponse"
method [1] of Jaggery's "OAuth" module. This method will return
"AccessTokenResponse"
object. But "sendOAuthRequest" method expects a "Token" object. Hence, I am
manually creating "Token" object and passing it to "sendOAuthRequest"
method, as shown below. I am referring [2] to create a "Token" object
manually.
*var accessTokenResponse =
oauthProvider.getTokenResponse(samlResp);accessToken =
accessTokenResponse.getAccessToken();var oauth2Token = {};
oauth2Token.token = accessToken;oauth2Token.secret =
"PkxikDuusEi67VpuqK7gpsLJlYIa";var response =
**oauthProvider.sendOAuthRequest(oauth2Token,
"GET", "https://xx.xx.xx.xx:8251/bpmn/1.0.0/repository/deployments
<https://xx.xx.xx.xx:8251/bpmn/1.0.0/repository/deployments>");*
But I am getting the following exception when executing this block. I think
this exception is thrown from here [3].
JavaException: org.jaggeryjs.scriptengine.exceptions.ScriptException:
Invalid Access Token
I think something is wrong with constructing the "Token" object. Any
pointers?
[1]
https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L211-L238
[2]
http://grepcode.com/file/repo1.maven.org/maven2/org.scribe/scribe/1.2.3/org/scribe/model/Token.java#Token.0token
[3]
https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L149
Thanks,
Raj.
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How do we call "sendOAuthRequest" method of Jaggery's "OAuth" module with payload
Hi, I am talking about [1]. Couldn't find any documentation or samples on this. How do we call "sendOAuthRequest" method of Jaggery's "OAuth" module with POST payload? [1] https://github.com/wso2/jaggery-extensions/blob/master/oauth/resources/org.jaggeryjs.modules.oauth/src/main/java/org/jaggeryjs/modules/oauth/OAuthHostObject.java#L141-L192 Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do I use enrich mediator with JSON payload in ESB 4.9.0?
On Tue, Mar 1, 2016 at 6:21 AM, Praneesha Chandrasiri <pranee...@wso2.com> wrote: > Hi all, > > > I removed Enrich Mediator from the list, which includes mediators that > have JSON support in docs of ESB 4.9.0 and above, as for example in [1]. > I hope Shafreen mentioned none of the mediators in this list has native JSON support, not just enrich mediator. > Also, I resolved the JIRA in [2]. > > [1] https://docs.wso2.com/display/ESB500/JSON+Support > > [2] https://wso2.org/jira/browse/DOCUMENTATION-2299 > > Thanks everyone! > > On Tue, Mar 1, 2016 at 10:21 AM, Shafreen Anfar <shafr...@wso2.com> wrote: > >> Hi Doc team, >> >> I think we need to remove this section from the aforementioned document. >> AFAIK, none of the mediators mentioned below support native json. >> >> @Others : Please correct me if am wrong :) >> >> Mediators with native JSON support >> >> Native JSON manipulation is supported for the following mediators. >> >>- Enrich mediator >>- Iterate mediator >>- Aggregate mediator >>- Clone mediator >> >> When JSON is used only the expressions of the above mediator >> configurations differ from the xml configuration. >> >> On Tue, Mar 1, 2016 at 10:13 AM, Shafreen Anfar <shafr...@wso2.com> >> wrote: >> >>> Hi Rajkumar, >>> >>> It seems there is no such native json support in Enrich mediator. Will >>> update the document. Sorry for the inconvenience. >>> >>> On Tue, Mar 1, 2016 at 1:26 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> >>> wrote: >>> >>>> >>>> >>>> On Mon, Feb 29, 2016 at 7:54 PM, Rajkumar Rajaratnam < >>>> rajkum...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> Doc [1] says enrich mediator supports native JSON manipulation. Does >>>>> that mean I can modify the JSON payload using enrich mediator? How do I do >>>>> that? Couldn't find any doc or blog. >>>>> >>>>> [1] https://docs.wso2.com/display/ESB490/JSON+Support >>>>> >>>>> Thanks, >>>>> Raj. >>>>> >>>>> -- >>>>> Rajkumar Rajaratnam >>>>> Committer & PMC Member, Apache Stratos >>>>> Software Engineer, WSO2 >>>>> >>>>> Mobile : +94777568639 >>>>> Blog : rajkumarr.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Rajkumar Rajaratnam >>>> Committer & PMC Member, Apache Stratos >>>> Software Engineer, WSO2 >>>> >>>> Mobile : +94777568639 >>>> Blog : rajkumarr.com >>>> >>> >>> >>> >>> -- >>> Regards, >>> *Shafreen* >>> Software Engineer >>> WSO2 Inc >>> Mobile : 077-556-395-1 >>> >> >> >> >> -- >> Regards, >> *Shafreen* >> Software Engineer >> WSO2 Inc >> Mobile : 077-556-395-1 >> > > > > -- > Thanks & Best Regards, > *Praneesha Chandrasiri* > *Technical Writer* > *WSO2 Inc. * > *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* > *E-mail: pranee...@wso2.com <pranee...@wso2.com>* > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blogs : wso2tech.blogspot.com, wso2tech.wordpress.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB][ScriptMediator] Can't convert a javaScript date in to ISO date format
t org.mozilla.javascript.gen.c6028._c0(:2) >>> at org.mozilla.javascript.gen.c6028.call() >>> at >>> org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) >>> at >>> org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) >>> at org.mozilla.javascript.gen.c6028.call() >>> at org.mozilla.javascript.gen.c6028.exec() >>> at >>> com.sun.phobos.script.javascript.RhinoCompiledScript.eval(RhinoCompiledScript.java:55) >>> ... 15 more >>> >>> Proxy: >>> >>> >>> http://ws.apache.org/ns/synapse; >>> name="testproxy" >>>transports="https,http" >>>statistics="disable" >>>trace="disable" >>>startOnLoad="true"> >>> >>> >>> var d=new Date(); >>> var isoFormat = d.toISOString(); >>> print(isoFormat); >>> >>> >>> >>> >>> >>> Are there any limitations in ESB Script Mediator or am I doing something >>> wrong here? >>> Any help is greatly appreciated. >>> >>> [1].http://www.w3schools.com/jsref/jsref_toisostring.asp >>> >>> Thanks & Regards >>> Lakmini. >>> >> >> >> >> -- >> >> *Nirodha Gallage* >> Associate Technical Lead, QA. >> WSO2 Inc.: http://wso2.com/ >> Mobile: +94716429078 >> > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blogs : wso2tech.blogspot.com, wso2tech.wordpress.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do I use enrich mediator with JSON payload in ESB 4.9.0?
Thanks Shafreen for the information and Praneesha for fixing the doc. On Tue, Mar 1, 2016 at 6:21 AM, Praneesha Chandrasiri <pranee...@wso2.com> wrote: > Hi all, > > > I removed Enrich Mediator from the list, which includes mediators that > have JSON support in docs of ESB 4.9.0 and above, as for example in [1]. > > Also, I resolved the JIRA in [2]. > > [1] https://docs.wso2.com/display/ESB500/JSON+Support > > [2] https://wso2.org/jira/browse/DOCUMENTATION-2299 > > Thanks everyone! > > On Tue, Mar 1, 2016 at 10:21 AM, Shafreen Anfar <shafr...@wso2.com> wrote: > >> Hi Doc team, >> >> I think we need to remove this section from the aforementioned document. >> AFAIK, none of the mediators mentioned below support native json. >> >> @Others : Please correct me if am wrong :) >> >> Mediators with native JSON support >> >> Native JSON manipulation is supported for the following mediators. >> >>- Enrich mediator >>- Iterate mediator >>- Aggregate mediator >>- Clone mediator >> >> When JSON is used only the expressions of the above mediator >> configurations differ from the xml configuration. >> >> On Tue, Mar 1, 2016 at 10:13 AM, Shafreen Anfar <shafr...@wso2.com> >> wrote: >> >>> Hi Rajkumar, >>> >>> It seems there is no such native json support in Enrich mediator. Will >>> update the document. Sorry for the inconvenience. >>> >>> On Tue, Mar 1, 2016 at 1:26 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> >>> wrote: >>> >>>> >>>> >>>> On Mon, Feb 29, 2016 at 7:54 PM, Rajkumar Rajaratnam < >>>> rajkum...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> Doc [1] says enrich mediator supports native JSON manipulation. Does >>>>> that mean I can modify the JSON payload using enrich mediator? How do I do >>>>> that? Couldn't find any doc or blog. >>>>> >>>>> [1] https://docs.wso2.com/display/ESB490/JSON+Support >>>>> >>>>> Thanks, >>>>> Raj. >>>>> >>>>> -- >>>>> Rajkumar Rajaratnam >>>>> Committer & PMC Member, Apache Stratos >>>>> Software Engineer, WSO2 >>>>> >>>>> Mobile : +94777568639 >>>>> Blog : rajkumarr.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Rajkumar Rajaratnam >>>> Committer & PMC Member, Apache Stratos >>>> Software Engineer, WSO2 >>>> >>>> Mobile : +94777568639 >>>> Blog : rajkumarr.com >>>> >>> >>> >>> >>> -- >>> Regards, >>> *Shafreen* >>> Software Engineer >>> WSO2 Inc >>> Mobile : 077-556-395-1 >>> >> >> >> >> -- >> Regards, >> *Shafreen* >> Software Engineer >> WSO2 Inc >> Mobile : 077-556-395-1 >> > > > > -- > Thanks & Best Regards, > *Praneesha Chandrasiri* > *Technical Writer* > *WSO2 Inc. * > *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* > *E-mail: pranee...@wso2.com <pranee...@wso2.com>* > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do I use enrich mediator with JSON payload in ESB 4.9.0?
On Mon, Feb 29, 2016 at 7:54 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Hi, > > Doc [1] says enrich mediator supports native JSON manipulation. Does that > mean I can modify the JSON payload using enrich mediator? How do I do that? > Couldn't find any doc or blog. > > [1] https://docs.wso2.com/display/ESB490/JSON+Support > > Thanks, > Raj. > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 > Blog : rajkumarr.com > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How do I use enrich mediator with JSON payload in ESB 4.9.0?
Hi, Doc [1] says enrich mediator supports native JSON manipulation. Does that mean I can modify the JSON payload using enrich mediator? How do I do that? Couldn't find any doc or blog. [1] https://docs.wso2.com/display/ESB490/JSON+Support Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I retrieve XMLTYPE & SDO_GEOMETRY types from an oracle database using DSS?
Thanks a lot guys for the response. Let me try the stored procedure approach and get back to you. On Tue, Feb 23, 2016 at 8:55 AM, Rajith Vitharana <raji...@wso2.com> wrote: > Hi Rajkumar, > > You may achieve this by writing a custom connector as well. Documentation > is in [1]. But it will be too complicated as you'll need to write the whole > datasource implementation. So easier thing would be to do a conversion > within stored procedure as Anjana suggested. > > [1] - https://docs.wso2.com/display/DSS350/Custom+Datasources > > Thanks, > > On Tue, Feb 23, 2016 at 5:29 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi, >> >> $Subject please. I couldn't find a way to retrieve columns of types >> XMLTYPE & SDO_GEOMETRY from an oracle database using DSS. Is there any way >> to retrieve them? >> >> Thanks, >> Raj. >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> > > > > -- > Rajith Vitharana > > Software Engineer, > WSO2 Inc. : wso2.com > Mobile : +94715883223 > Blog : http://lankavitharana.blogspot.com/ > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How can I retrieve XMLTYPE & SDO_GEOMETRY types from an oracle database using DSS?
Hi, $Subject please. I couldn't find a way to retrieve columns of types XMLTYPE & SDO_GEOMETRY from an oracle database using DSS. Is there any way to retrieve them? Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][PPaaS]Puppet Modules - Use of MySQL datasources in the default.yaml
Hi Sajith/Gayan, I and Akila have already discussed about this. We defined wso2 products' default configuration values in wso2/common.yaml *to avoid conditional checks in template files*. For example, if you check carbon.xml.erb, you will see that we don't have any default values for port offset. We defined the default port offset (0) in wso2/common.yaml and allow users to override them in product yaml files (default.yaml, manager.yaml, etc). *Hence, we decided not to allow (or discourage) users to edit wso2/common.yaml*. Intention is to prevent careless modification to default values. That is the reason why we didn't add gov/config databases to wso2/common.yaml. If we do so, then user needs to modify wso2/common.yaml, which might lead to issues explained above. However, where to add gov/config databases is upto the user, if he wants, he can add them in wso2/common.yaml too. Thanks, Raj. On Fri, Jan 8, 2016 at 5:49 PM, Gayan Gunarathne <gay...@wso2.com> wrote: > > > On Fri, Jan 8, 2016 at 5:42 PM, Sajith Kariyawasam <saj...@wso2.com> > wrote: > >> Hi Raj, >> >> On Fri, Jan 8, 2016 at 7:30 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> Hi Sajith, >>> >>> No, default.yaml doesn't need to be the exact same configurations of a >>> vanilla pack. It represents the "default" profile of a product in a >>> deployment. One can update default.yaml and point the carbon db to an >>> external MySQL db. He doesn't need to create a new yaml file to be able to >>> point the carbon db to an external MySQL db. >>> >>> As I mentioned earlier (and as Pubuddu agreed), what we should ship in >>> default.yaml by default is the exact same configurations of a vanilla pack. >>> >> >> Yes, its the same thing I was talking, from a release point of view we >> need to have a default set of configurations (which is the exact same >> configs of a vanila pack: pointing to H2 etc ), that's why I was confused >> to see config_db / gov / user-mgt related configs in default.xml, which we >> don't see in a default carbon master-datasources.xml file. >> >> Can't we move config/gov/user-mgt datasource configurations [1] into >> *common.yaml* ? (And keep the product specific datasources like bps / am >> etc in their respective default.yaml) >> Because, in a specific setup, values of master-datasources.xml file will >> be same in each product, and default.xml file would become more simpler. >> >> [1] >> https://github.com/wso2/puppet-modules/blob/master/hiera/hieradata/dev/wso2/wso2am/1.9.1/default.yaml#L52-L97 >> > > As those are common to all the products IMO we can move them to the > common.yaml. No point of duplicating the default hiera values in each > product. > >> >> >>> Other configurations, such as config/gov db, proxy ports, should be >>> commented by default. >>> >> >> Code blocks in [1] too need to be commented out, otherwise it will always >> create master-datasources.xml file with all the data sources >> >> >>> >>> Thanks, >>> Raj. >>> >>> On Fri, Jan 8, 2016 at 1:25 AM, Sajith Kariyawasam <saj...@wso2.com> >>> wrote: >>> >>>> Hi Raj, >>>> >>>> On Thu, Jan 7, 2016 at 5:40 PM, Rajkumar Rajaratnam <rajkum...@wso2.com >>>> > wrote: >>>> >>>>> >>>>> >>>>> On Thu, Jan 7, 2016 at 2:31 PM, Chamila De Alwis <chami...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi devs, >>>>>> >>>>>> In the Hiera files, the default.yaml is supposed to contain values >>>>>> for a "default" setup, representing a server running out of the box from >>>>>> a >>>>>> downloaded product. Therefore, the wso2::master_datasources should point >>>>>> to >>>>>> the H2 database. >>>>>> >>>>> >>>>> I guess we are confusing with wordings here. >>>>> >>>>> default.yaml contains configurations of a product's "default" profile >>>>> in a deployment. Similarly manager.yaml is for "manager" profile and so >>>>> on. >>>>> A user can update default.yaml according to their deployment. For example, >>>>> he can point carbon db to an external MySQL server. >>>>> >>>>> I guess you are referring that the gov/config db configurations are >>>>> added in some def
Re: [Dev] [DEV][PPaaS]Puppet Modules - Use of MySQL datasources in the default.yaml
On Thu, Jan 7, 2016 at 2:31 PM, Chamila De Alwis <chami...@wso2.com> wrote: > Hi devs, > > In the Hiera files, the default.yaml is supposed to contain values for a > "default" setup, representing a server running out of the box from a > downloaded product. Therefore, the wso2::master_datasources should point to > the H2 database. > > However, the default.yaml contains datasources pointing to a MySQL server. > IMO this should change to point to the H2 database. WDYT? > Which database are we talking about here? If it is the default carbon db, then it is already defined in wso2/common.yaml and pointing to H2 db. We don't need to define it again in default.yaml of a product. Thanks, Raj. > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][PPaaS]Puppet Modules - Use of MySQL datasources in the default.yaml
On Fri, Jan 8, 2016 at 1:25 AM, Sajith Kariyawasam <saj...@wso2.com> wrote: > Hi Raj, > > On Thu, Jan 7, 2016 at 5:40 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> >> >> On Thu, Jan 7, 2016 at 2:31 PM, Chamila De Alwis <chami...@wso2.com> >> wrote: >> >>> Hi devs, >>> >>> In the Hiera files, the default.yaml is supposed to contain values for a >>> "default" setup, representing a server running out of the box from a >>> downloaded product. Therefore, the wso2::master_datasources should point to >>> the H2 database. >>> >> >> I guess we are confusing with wordings here. >> >> default.yaml contains configurations of a product's "default" profile in >> a deployment. Similarly manager.yaml is for "manager" profile and so on. A >> user can update default.yaml according to their deployment. For example, he >> can point carbon db to an external MySQL server. >> >> I guess you are referring that the gov/config db configurations are added >> in some default.yaml and they are pointed to MySQL db. This is correct, we >> don't need to point them to H2. What we should do is, we need to comment >> these configurations and ship the hiera yaml files. Because these are not >> default configurations. >> > > Shouldn't we move wso2_config_db, wso2_gov_db, wso2user_db blocks (which > are under wso2::master_datasources), out of default.yaml because those too > are not "default" configurations, and move those into worker.yaml and > manager.yaml. > These databases are not going to change across product profiles. That is why we added them in default.yaml. If they change across profiles, then we need to add/override them in profile specific yaml files, which is the next hierarchy. In a deployment, - wso2 platform specific configurations will be added to wso2/common.yaml - wso2 product specific configurations will be added to default.yaml - wso2 product profile specific configurations will be added to .yaml - any edge case configurations will be added to .yaml Thanks, Raj. > Shouldn't default.yaml profile equal to the exact same configurations of a > fresh pack (with changing values only)? > If that's the case why those config_db, gov_db etc defined in default.yaml > ? > > >> If a user wants, he can uncomment and modify the settings. For example, >> refer [1]. >> >> [1] >> https://github.com/wso2/puppet-modules/blob/master/hiera/hieradata/dev/wso2/wso2am/1.9.1/default.yaml#L11-L33 >> >> Thanks, >> Raj. >> >> >>> However, the default.yaml contains datasources pointing to a MySQL >>> server. IMO this should change to point to the H2 database. WDYT? >>> >>> Regards, >>> Chamila de Alwis >>> Committer and PMC Member - Apache Stratos >>> Software Engineer | WSO2 | +94772207163 >>> Blog: code.chamiladealwis.com >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Sajith Kariyawasam > *Committer and PMC member, Apache Stratos, * > *WSO2 Inc.; http://wso2.com <http://wso2.com>* > *Mobile: 0772269575* > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][PPaaS]Puppet Modules - Use of MySQL datasources in the default.yaml
On Fri, Jan 8, 2016 at 7:42 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > > > On Fri, Jan 8, 2016 at 1:25 AM, Sajith Kariyawasam <saj...@wso2.com> > wrote: > >> Hi Raj, >> >> On Thu, Jan 7, 2016 at 5:40 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> >>> >>> On Thu, Jan 7, 2016 at 2:31 PM, Chamila De Alwis <chami...@wso2.com> >>> wrote: >>> >>>> Hi devs, >>>> >>>> In the Hiera files, the default.yaml is supposed to contain values for >>>> a "default" setup, representing a server running out of the box from a >>>> downloaded product. Therefore, the wso2::master_datasources should point to >>>> the H2 database. >>>> >>> >>> I guess we are confusing with wordings here. >>> >>> default.yaml contains configurations of a product's "default" profile in >>> a deployment. Similarly manager.yaml is for "manager" profile and so on. A >>> user can update default.yaml according to their deployment. For example, he >>> can point carbon db to an external MySQL server. >>> >>> I guess you are referring that the gov/config db configurations are >>> added in some default.yaml and they are pointed to MySQL db. This is >>> correct, we don't need to point them to H2. What we should do is, we need >>> to comment these configurations and ship the hiera yaml files. Because >>> these are not default configurations. >>> >> >> Shouldn't we move wso2_config_db, wso2_gov_db, wso2user_db blocks (which >> are under wso2::master_datasources), out of default.yaml because those too >> are not "default" configurations, and move those into worker.yaml and >> manager.yaml. >> > > These databases are not going to change across product profiles. That is > why we added them in default.yaml. If they change across profiles, then we > need to add/override them in profile specific yaml files, which is the next > hierarchy. > > In a deployment, > - wso2 platform specific configurations will be added to wso2/common.yaml > - wso2 product specific configurations will be added to default.yaml > - wso2 product profile specific configurations will be added to > .yaml > - any edge case configurations will be added to .yaml > This hierarchy reduces data duplication significantly. Of course, we can move config/gov db configurations to profile specific yaml files, nothing is going to break, but we are duplicating the same data in several yaml files. Thanks, Raj. > > Thanks, > Raj. > > > >> Shouldn't default.yaml profile equal to the exact same configurations of >> a fresh pack (with changing values only)? >> If that's the case why those config_db, gov_db etc defined in >> default.yaml ? >> >> >>> If a user wants, he can uncomment and modify the settings. For example, >>> refer [1]. >>> >>> [1] >>> https://github.com/wso2/puppet-modules/blob/master/hiera/hieradata/dev/wso2/wso2am/1.9.1/default.yaml#L11-L33 >>> >>> Thanks, >>> Raj. >>> >>> >>>> However, the default.yaml contains datasources pointing to a MySQL >>>> server. IMO this should change to point to the H2 database. WDYT? >>>> >>>> Regards, >>>> Chamila de Alwis >>>> Committer and PMC Member - Apache Stratos >>>> Software Engineer | WSO2 | +94772207163 >>>> Blog: code.chamiladealwis.com >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Rajkumar Rajaratnam >>> Committer & PMC Member, Apache Stratos >>> Software Engineer, WSO2 >>> >>> Mobile : +94777568639 >>> Blog : rajkumarr.com >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sajith Kariyawasam >> *Committer and PMC member, Apache Stratos, * >> *WSO2 Inc.; http://wso2.com <http://wso2.com>* >> *Mobile: 0772269575* >> > > > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 > Blog : rajkumarr.com > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][PPaaS]Puppet Modules - Use of MySQL datasources in the default.yaml
Hi Sajith, No, default.yaml doesn't need to be the exact same configurations of a vanilla pack. It represents the "default" profile of a product in a deployment. One can update default.yaml and point the carbon db to an external MySQL db. He doesn't need to create a new yaml file to be able to point the carbon db to an external MySQL db. As I mentioned earlier (and as Pubuddu agreed), what we should ship in default.yaml by default is the exact same configurations of a vanilla pack. Other configurations, such as config/gov db, proxy ports, should be commented by default. Thanks, Raj. On Fri, Jan 8, 2016 at 1:25 AM, Sajith Kariyawasam <saj...@wso2.com> wrote: > Hi Raj, > > On Thu, Jan 7, 2016 at 5:40 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> >> >> On Thu, Jan 7, 2016 at 2:31 PM, Chamila De Alwis <chami...@wso2.com> >> wrote: >> >>> Hi devs, >>> >>> In the Hiera files, the default.yaml is supposed to contain values for a >>> "default" setup, representing a server running out of the box from a >>> downloaded product. Therefore, the wso2::master_datasources should point to >>> the H2 database. >>> >> >> I guess we are confusing with wordings here. >> >> default.yaml contains configurations of a product's "default" profile in >> a deployment. Similarly manager.yaml is for "manager" profile and so on. A >> user can update default.yaml according to their deployment. For example, he >> can point carbon db to an external MySQL server. >> >> I guess you are referring that the gov/config db configurations are added >> in some default.yaml and they are pointed to MySQL db. This is correct, we >> don't need to point them to H2. What we should do is, we need to comment >> these configurations and ship the hiera yaml files. Because these are not >> default configurations. >> > > Shouldn't we move wso2_config_db, wso2_gov_db, wso2user_db blocks (which > are under wso2::master_datasources), out of default.yaml because those too > are not "default" configurations, and move those into worker.yaml and > manager.yaml. > Shouldn't default.yaml profile equal to the exact same configurations of a > fresh pack (with changing values only)? > If that's the case why those config_db, gov_db etc defined in default.yaml > ? > > >> If a user wants, he can uncomment and modify the settings. For example, >> refer [1]. >> >> [1] >> https://github.com/wso2/puppet-modules/blob/master/hiera/hieradata/dev/wso2/wso2am/1.9.1/default.yaml#L11-L33 >> >> Thanks, >> Raj. >> >> >>> However, the default.yaml contains datasources pointing to a MySQL >>> server. IMO this should change to point to the H2 database. WDYT? >>> >>> Regards, >>> Chamila de Alwis >>> Committer and PMC Member - Apache Stratos >>> Software Engineer | WSO2 | +94772207163 >>> Blog: code.chamiladealwis.com >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Sajith Kariyawasam > *Committer and PMC member, Apache Stratos, * > *WSO2 Inc.; http://wso2.com <http://wso2.com>* > *Mobile: 0772269575* > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2
Found a minor issue. The carbon.xml.template we are shipping with the installer is not the PPaaS carbon.xml. It is the API Manager carbon.xml. [1] https://github.com/wso2/product-private-paas/blob/master/tools/installer/wso2ppaas/4.1.0/template-module/templates/repository/conf/carbon.xml.template Thanks, Raj. On Tue, Dec 29, 2015 at 10:16 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Tested ESB 4.9.0 and API-M 1.9.1 cartridges on PPaaS. > > Verified following. > > 1. Application deployment and undeployment > 2. Scaling up/down > 3. Fault member detection > > [x] - Stable - go ahead and release > > Thank you! > > On Tue, Dec 29, 2015 at 9:20 PM, Isuru Haththotuwa <isu...@wso2.com> > wrote: > >> Tested the below on EC2 and K8s: >> >> Application deployment and undeployment >> MT apps - adding signups and removal of signups >> >> [x]- Stable - go ahead and release >> >> On Tue, Dec 29, 2015 at 8:04 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> Verified following on k8s; >>> - rest APIs (CRUD operations of artifacts via curl) >>> - application deployment, activation, undeployment >>> - scaling up/down >>> - fault detection >>> >>> [x] Stable - go ahead and release >>> >>> On Tue, Dec 29, 2015 at 5:40 PM, Akila Ravihansa Perera < >>> raviha...@wso2.com> wrote: >>> >>>> [x] Stable - go ahead and release >>>> >>>> Tested following; >>>> - PHP application deployment, activation and undeployment on Kubernetes >>>> - Scale up functionality >>>> - Faulty member detection >>>> - Tested APIM 1.9.1 cartridge (IS as KM) with PPaaS on Kubernetes >>>> - Tested sample application on AWS EC2 IaaS >>>> >>>> >>>> Found a minor error in one of the samples in ppaas-cartridges repo [1]. >>>> >>>> [1] >>>> https://github.com/wso2/private-paas-cartridges/blob/v4.1.3/wso2am/1.9.1/samples/kubernetes-clusters/kubernetes-cluster-1.json#L53 >>>> >>>> On Mon, Dec 28, 2015 at 7:55 PM, Thanuja Uruththirakodeeswaran < >>>> thanu...@wso2.com> wrote: >>>> >>>>> +1 for the release >>>>> >>>>> Tested ppaas in kubernetes with few wso2 product cartridges along >>>>> metering and monitering feature. >>>>> >>>>> Thanks. >>>>> >>>>> On 27 Dec 2015 21:12, "Gayan Gunarathne" <gay...@wso2.com >>>>> ) wrote:)) >>>>> >>>>> > >>>>> > >>>>> > >>>>> > On Sun, Dec 27, 2015 at 10:00 AM, Akila Ravihansa Perera < >>>>> raviha...@wso2.com> wrote: >>>>> >> >>>>> >> Hi Gayan, >>>>> >> >>>>> >> Since we have forked Python cartridge agent in PPaaS 4.1.1-RC2, >>>>> users won't be able to use Dockerfile shipped with Stratos to build >>>>> cartridge images. >>>>> > >>>>> > What do you mean by Dockerfile shipped with Stratos? >>>>> > >>>>> >> >>>>> >> Have we documented the steps needed to build cartridge Docker >>>>> images for PPaaS? >>>>> > >>>>> > We are released the Cartridges based on the PPaaS release version. >>>>> Currently released cartridges are compatible with PPaaS 4.1.0 release.With >>>>> the PPaaS 4.1.1 released our documentation need to be changed in the case >>>>> of user using the PPaaS 4.1.1 release >>>>> >> >>>>> >> >>>>> >> Thanks. >>>>> >> >>>>> >> On Fri, Dec 25, 2015 at 12:06 AM, Gayan Gunarathne <gay...@wso2.com> >>>>> wrote: >>>>> >>> >>>>> >>> IMO if the vote is success we can simply move those binaries to >>>>> the product distribution without doing any alternation to those >>>>> binaries.This is the same as the staging repo. If the vote is success we >>>>> promote the staging repo , if it is fails we drop that staging repo. >>>>> >>> >>>>> >>> Thanks, >>>>> >>> Gayan >>>>> >>> >>>>> >>> On Thu, Dec 24, 2015 at 11:47 PM, Imesh Gunaratne <im...@wso2.com> >>>>> wrote: &
Re: [Dev] [DEV][PPaaS] Puppet modules for WSO2 Products
On Wed, Dec 23, 2015 at 1:11 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > I have completed ESB 4.9.0 and G-Reg 4.6.0/5.1.0 puppet modules with > hiera. I have tested clustering, registry mounting, depsync, etc with > vagrant. > Completed PPaaS 4.1.0/4.1.1 puppet modules with hiera. Thanks, Raj. > > PS - still we are doing some improvements in hiera data structure at the > moment. > > Thanks, > Raj. > > On Wed, Dec 23, 2015 at 12:54 PM, Chamila De Alwis <chami...@wso2.com> > wrote: > >> Hi Thanuja, >> >> Sure. I'll start working on WSO2 Message Broker module. >> >> >> Regards, >> Chamila de Alwis >> Committer and PMC Member - Apache Stratos >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> >> On Wed, Dec 23, 2015 at 12:53 PM, Thanuja Uruththirakodeeswaran < >> thanu...@wso2.com> wrote: >> >>> Hi Chamila, >>> >>> I've started to work on AS puppet module. Could you please take another >>> product. >>> >>> Thanks. >>> >>> On Wed, Dec 23, 2015 at 12:42 PM, Chamila De Alwis <chami...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> I've started working on the the Puppet module for WSO2 Application >>>> Server on [1]. This is based on the generic WSO2 Base Puppet module and >>>> will follow the same pattern as the other modules. >>>> >>>> If you have started working on a module, please update with the latest >>>> status. >>>> >>>> [1] - https://github.com/wso2/puppet-modules >>>> >>>> Regards, >>>> Chamila de Alwis >>>> Committer and PMC Member - Apache Stratos >>>> Software Engineer | WSO2 | +94772207163 >>>> Blog: code.chamiladealwis.com >>>> >>>> >>>> >>> >>> >>> -- >>> Thanuja Uruththirakodeeswaran >>> Software Engineer >>> WSO2 Inc.;http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 774363167 >>> >> >> > > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 > Blog : rajkumarr.com > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2
-305?filter=12582 >> >>>>>>> >> >>>>>>> Please download, test and vote. The vote will be open for 72 >> hours or as needed. >> >>>>>>> >> >>>>>>> Source and binary distribution files: >> >>>>>>> >> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/ >> >>>>>>> >> >>>>>>> Maven staging repository: >> >>>>>>> >> >>>>>>> >> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/ >> >>>>>>> >> >>>>>>> The tag to be voted upon: >> >>>>>>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2 >> >>>>>>> >> >>>>>>> >> >>>>>>> [ ] Broken - do not release (explain why) >> >>>>>>> [ ] Stable - go ahead and release >> >>>>>>> >> >>>>>>> >> >>>>>>> Thanks, >> >>>>>>> The WSO2 Private PaaS Team >> >>>>>>> >> >>>>>>> -- >> >>>>>>> >> >>>>>>> Gayan Gunarathne >> >>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >> >>>>>>> Committer & PMC Member, Apache Stratos >> >>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> ___ >> >>>>>>> Dev mailing list >> >>>>>>> Dev@wso2.org >> >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >>>>>>> >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> Imesh Gunaratne >> >>>>>> Senior Technical Lead >> >>>>>> WSO2 Inc: http://wso2.com >> >>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >> >>>>>> W: http://imesh.gunaratne.org >> >>>>>> Lean . Enterprise . Middleware >> >>>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> >> >>>>> Gayan Gunarathne >> >>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >> >>>>> Committer & PMC Member, Apache Stratos >> >>>>> email : gay...@wso2.com | mobile : +94 775030545 >> >>>>> >> >>>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> -- >> >>>> Imesh Gunaratne >> >>>> Senior Technical Lead >> >>>> WSO2 Inc: http://wso2.com >> >>>> T: +94 11 214 5345 M: +94 77 374 2057 >> >>>> W: http://imesh.gunaratne.org >> >>>> Lean . Enterprise . Middleware >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> >> >>> Gayan Gunarathne >> >>> Technical Lead, WSO2 Inc. (http://wso2.com) >> >>> Committer & PMC Member, Apache Stratos >> >>> email : gay...@wso2.com | mobile : +94 775030545 >> >>> >> >>> >> >>> >> >>> ___ >> >>> Dev mailing list >> >>> Dev@wso2.org >> >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >>> >> >> >> >> >> >> >> >> -- >> >> Akila Ravihansa Perera >> >> WSO2 Inc.; http://wso2.com/ >> >> >> >> Blog: http://ravihansa3000.blogspot.com >> > >> > >> > >> > >> > -- >> > >> > Gayan Gunarathne >> > Technical Lead, WSO2 Inc. (http://wso2.com) >> > Committer & PMC Member, Apache Stratos >> > email : gay...@wso2.com | mobile : +94 775030545 >> > >> > >> > >> > ___ >> > Dev mailing list >> > Dev@wso2.org >> > http://wso2.org/cgi-bin/mailman/listinfo/dev >> > >> >> > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Hiera] Deeper hash merge instead of Native hash merge?
Hi Akila,
Thanks for your thought. Lets ship native hash merge data structures by
default. Those who wants deeper merging can alter the merge behavior in
hiera.yaml (:merge_behavior: deeper) and data structures in data yaml
files. This doesn't involve any changes in puppet modules.
Thanks,
Raj.
On Fri, Dec 25, 2015 at 9:44 PM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:
> Hi Raj,
>
> It is true that native hash merging has its own limitations which would
> lead to data duplication in some cases. But we need to analyze the
> trade-off between data duplication against readability and trace-ability
> aspects. IMHO, it's okay to have few data duplication if it makes things
> more simple and less error prone.
>
> My concern is that what if this accidentally leads to unexpected data
> merging? I understand that native merging will merge the top level keys as
> well, but that is less susceptible for human errors compared to N-level
> deep merge.
>
> Also have a look at Puppet official docs about deep merging [1]. Looks
> like it is mainly intended for complex data structures and converting them
> to Puppet resources.
>
> We can ask the users to create their own Hiera data structures with deeper
> merging if they are comfortable with it. But given the additional
> complexity involved in configuring and installing deep_merge library [2],
> shall we ship native merge data structures by default?
>
> [1]
> https://docs.puppetlabs.com/hiera/3.0/lookup_types.html#deep-merging-in-hiera
> [2]
> https://docs.puppetlabs.com/hiera/3.0/lookup_types.html#deep-merging-in-hiera
>
> Thanks.
>
> On Fri, Dec 25, 2015 at 10:45 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> We are using *Native* hash merge right now. *It merges only the
>> top-level keys and values in each source hash. If the same key exists in
>> both a lower priority source and a higher priority source, the higher
>> priority value will be used. *But it doesn't allow us to override a
>> nested hash.
>>
>> Lets take an example,
>>
>> *hiera.yaml*
>>
>> ---
>> :hierarchy:
>> - "wso2/%{::product_name}/%{::product_version}/default"
>> - wso2/common
>> :backends:
>> - yaml
>> :yaml:
>> :datadir: "hieradata/%{::environment}"
>>
>> *wso2/common.yaml*
>>
>> ---
>> # Deployment synchronization configuration
>> wso2::dep_sync :
>> enabled : false
>> auto_checkout : true
>> auto_commit : false
>> repository_type : svn
>> svn :
>> url : http://svnrepo.example.com/repos/
>>user : username
>>password : password
>>append_tenant_id: true
>>
>> *wso2/wso2esb/4.9.0/default.yaml*
>>
>> ---
>> wso2::dep_sync :
>> enabled : true
>> svn :
>> url : http://rajkumar.com/repos/
>>
>>
>> *Native* hash merge would return the following;
>>
>> {
>>"enabled" =>true,
>>"auto_checkout" =>true,
>>"auto_commit" =>false,
>>"repository_type" =>"svn",
>>"svn" => {
>> "url" =>"http://rajkumar.com/repos/;
>>}
>> }
>>
>> *Deeper* hash merge would return the following;
>>
>> {
>>"enabled" =>true,
>>"auto_checkout" =>true,
>> "auto_commit" =>false,
>>"repository_type" =>"svn",
>>"svn" => {
>> "url" =>"http://rajkumar.com/repos/;,
>> "user" =>"username",
>> "password" =>"password",
>> "append_tenant_id" =>true
>>}
>> }
>>
>>
>> If we use *Native* hash merging, we need to copy the complete nested
>> hash ("svn" in above example) and override it. If we use *Deeper* hash
>> merging, we can copy only a part of a nested hash and override it. As you
>> can see, *Deeper* hash merge reduces data duplication.
>>
>> Thoughts please.
>>
>> Thanks,
>> Raj.
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.; http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Hiera] Deeper hash merge instead of Native hash merge?
Hi Devs,
We are using *Native* hash merge right now. *It merges only the top-level
keys and values in each source hash. If the same key exists in both a lower
priority source and a higher priority source, the higher priority value
will be used. *But it doesn't allow us to override a nested hash.
Lets take an example,
*hiera.yaml*
---
:hierarchy:
- "wso2/%{::product_name}/%{::product_version}/default"
- wso2/common
:backends:
- yaml
:yaml:
:datadir: "hieradata/%{::environment}"
*wso2/common.yaml*
---
# Deployment synchronization configuration
wso2::dep_sync :
enabled : false
auto_checkout : true
auto_commit : false
repository_type : svn
svn :
url : http://svnrepo.example.com/repos/
user : username
password : password
append_tenant_id: true
*wso2/wso2esb/4.9.0/default.yaml*
---
wso2::dep_sync :
enabled : true
svn :
url : http://rajkumar.com/repos/
*Native* hash merge would return the following;
{
"enabled" =>true,
"auto_checkout" =>true,
"auto_commit" =>false,
"repository_type" =>"svn",
"svn" => {
"url" =>"http://rajkumar.com/repos/;
}
}
*Deeper* hash merge would return the following;
{
"enabled" =>true,
"auto_checkout" =>true,
"auto_commit" =>false,
"repository_type" =>"svn",
"svn" => {
"url" =>"http://rajkumar.com/repos/;,
"user" =>"username",
"password" =>"password",
"append_tenant_id" =>true
}
}
If we use *Native* hash merging, we need to copy the complete nested hash
("svn" in above example) and override it. If we use *Deeper* hash merging,
we can copy only a part of a nested hash and override it. As you can see,
*Deeper* hash merge reduces data duplication.
Thoughts please.
Thanks,
Raj.
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][PPaaS] Puppet modules for WSO2 Products
I have completed ESB 4.9.0 and G-Reg 4.6.0/5.1.0 puppet modules with hiera. I have tested clustering, registry mounting, depsync, etc with vagrant. PS - still we are doing some improvements in hiera data structure at the moment. Thanks, Raj. On Wed, Dec 23, 2015 at 12:54 PM, Chamila De Alwis <chami...@wso2.com> wrote: > Hi Thanuja, > > Sure. I'll start working on WSO2 Message Broker module. > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > On Wed, Dec 23, 2015 at 12:53 PM, Thanuja Uruththirakodeeswaran < > thanu...@wso2.com> wrote: > >> Hi Chamila, >> >> I've started to work on AS puppet module. Could you please take another >> product. >> >> Thanks. >> >> On Wed, Dec 23, 2015 at 12:42 PM, Chamila De Alwis <chami...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I've started working on the the Puppet module for WSO2 Application >>> Server on [1]. This is based on the generic WSO2 Base Puppet module and >>> will follow the same pattern as the other modules. >>> >>> If you have started working on a module, please update with the latest >>> status. >>> >>> [1] - https://github.com/wso2/puppet-modules >>> >>> Regards, >>> Chamila de Alwis >>> Committer and PMC Member - Apache Stratos >>> Software Engineer | WSO2 | +94772207163 >>> Blog: code.chamiladealwis.com >>> >>> >>> >> >> >> -- >> Thanuja Uruththirakodeeswaran >> Software Engineer >> WSO2 Inc.;http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 774363167 >> > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Saml assertation from oauth acces token
Hi, AFAIK, OAuth access tokens doesn't carry any identity information (about a principal). So you can't generate SAML Assertion from OAuth access tokens. But you can do the reverse - that is, you can send a valid SAML Assertion to the token endpoint of IS to request for an OAuth access token. Refer [1 , 2 & 3] for more details on this. [1] https://docs.wso2.com/display/IS500/SAML2+Bearer+Assertion+Profile+for+OAuth+2.0 [2] http://xacmlinfo.org/2014/10/31/saml2-bearer-assertion-profile-for-oauth-2-0/ [3] https://docs.wso2.com/pages/viewpage.action?pageId=47515509 Thanks, Raj. On Sat, Oct 10, 2015 at 2:49 PM, Júnior <fjunio...@gmail.com> wrote: > Hi, > Is is possible to generate a Saml assertation from a Oauth access token? > > Is there any API or service on wso2 IS that does this job? > > Thanks > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] API Manager template module seems be messed up
Hi Imesh,
Sorry for the late response. Here is the JIRA [1].
[1] https://wso2.org/jira/browse/PPC-7
Thanks,
Raj.
On Tue, Sep 22, 2015 at 9:48 PM, Imesh Gunaratne <im...@wso2.com> wrote:
> Hi Raj,
>
> Can you please report a JIRA for this with the relevant information?
>
> Thanks
>
> On Wed, Sep 16, 2015 at 12:55 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> Hi Guys,
>>
>> Have we fixed the two issues discussed in this thread? If not, better to
>> track it via a JIRA.
>>
>> Thanks,
>> Raj.
>>
>> On Thu, Sep 10, 2015 at 4:53 PM, Pubudu Gunatilaka <pubu...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> +1 for this approach
>>>
>>> What we initially thought was to list down all the parameters in the
>>> module.ini file which are not default values. User can either override
>>> those values from environment variables or use the module.ini file.
>>>
>>> Thank you!
>>>
>>> On Thu, Sep 10, 2015 at 10:16 AM, Rajkumar Rajaratnam <
>>> rajkum...@wso2.com> wrote:
>>>
>>>> What I meant is, why don't we do this?
>>>>
>>>> if CONFIG_PARAM_LOCAL_MEMBER_HOST is set {
>>>> {{ CONFIG_PARAM_LOCAL_MEMBER_HOST
>>>> }}
>>>> } else {
>>>> 127.0.0.1
>>>> }
>>>>
>>>> Thanks.
>>>>
>>>> On Thu, Sep 10, 2015 at 3:59 PM, Rajkumar Rajaratnam <
>>>> rajkum...@wso2.com> wrote:
>>>>
>>>>> Any reason to treat the following config parameters differently, than
>>>>> other config parameters?
>>>>>
>>>>> CONFIG_PARAM_CLUSTERING=false
>>>>> CONFIG_PARAM_DOMAIN=wso2.carbon.domain
>>>>> CONFIG_PARAM_WKA_MEMBERS=[127.0.0.1:4000]
>>>>> CONFIG_PARAM_LOCAL_MEMBER_HOST=127.0.0.1
>>>>> CONFIG_PARAM_LOCAL_MEMBER_PORT=4000
>>>>> CONFIG_PARAM_PORT_OFFSET=0
>>>>> CONFIG_PARAM_MB_PORT=61616
>>>>> CONFIG_PARAM_EMBEDDED_LDAP=true
>>>>>
>>>>> These are enabled in module.ini file by default, where as other
>>>>> parameters are disabled. And the default values of these config elements
>>>>> are removed from templates files and moved to module.ini.
>>>>>
>>>>> This is not consistent with other config parameters. Because of this,
>>>>> we always have to pass these parameters to configurator, even though we
>>>>> don't need to override the default ones.
>>>>>
>>>>> By accident, I commented out all the config parameters from module.ini
>>>>> and I have passed only the needed parameters to the configurator as
>>>>> environment variables via puppet. I ended up with some issues since I
>>>>> haven't pass the above parameters as environment variables (even though I
>>>>> don't want to override the default ones!). So isn't good if leave the
>>>>> default values in the template files itself? This way, we don't have
>>>>> explicitly pass the default values, just like other config parameters.
>>>>>
>>>>> wdyt?
>>>>>
>>>>> Thanks,
>>>>> Raj.
>>>>>
>>>>> On Tue, Sep 8, 2015 at 1:19 AM, Rajkumar Rajaratnam <
>>>>> rajkum...@wso2.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Sep 8, 2015 at 1:16 AM, Reka Thirunavukkarasu <r...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Raj,
>>>>>>>
>>>>>>> Yah..Seems some old reference is there in the
>>>>>>> master-datasources.xml.template which will not affect the
>>>>>>> configurations,
>>>>>>> if the parameters are defined correctly in the cartridge definition.
>>>>>>> Please
>>>>>>> ignore the section with CONFIG_PARAM_CONFIG_DB_APIM_URL.
>>>>>>>
>>>>>>> Please refer [1] for the sample configuration. We will clean this in
>>>>>>> the immediate next release(beta)..
>>>>>>>
>>>>>>
>>>>>> +1. Not a blocker or urgent.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> [1]
>>>>>>> https://github.com/wso2/product-private-paas/blob/ma
Re: [Dev] [PPaaS] private-paas-cartridges repository structure
gt;>> to set up the ppaas related stuff while ppaas cartridge installer to >>>>>>> set up >>>>>>> the cartridge specific installations. >>>>>>> >>>>>> +1. We can check whether we can modify the stratos-installer and use >>>>>> it as a ppaas-installer rather writing it from the scratch. >>>>>> >>>>>> Thanks, >>>>>> Reka >>>>>> >>>>>>> >>>>>>>> Thanks, >>>>>>>> Reka >>>>>>>> >>>>>>>> On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne <gay...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Akila, >>>>>>>>> >>>>>>>>> Common folder has all the common stuff related to the >>>>>>>>> cartridges.So if someone can navigate to the common folder and get the >>>>>>>>> stuff shared among the cartridges. >>>>>>>>> >>>>>>>>> I think it is meaningful to have those common stuff at a one >>>>>>>>> place, then someone new to this repository also have a feeling those >>>>>>>>> stuff >>>>>>>>> will be common for all the cartridges.Common PCA plugins and utils >>>>>>>>> also we >>>>>>>>> can have inside the common folder >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Gayan >>>>>>>>> >>>>>>>>> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera < >>>>>>>>> raviha...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Gayan, >>>>>>>>>> >>>>>>>>>> Wouldn't it be easier to navigate if we move those common folders >>>>>>>>>> to root folder? >>>>>>>>>> >>>>>>>>>> We can create a common folder under /plugins/ folder to keep >>>>>>>>>> common PCA plugins and util files. >>>>>>>>>> >>>>>>>>>> Just a thought...wdyt? >>>>>>>>>> >>>>>>>>>> Thanks. >>>>>>>>>> >>>>>>>>>> On Thu, Oct 1, 2015 at 10:29 AM, Gayan Gunarathne < >>>>>>>>>> gay...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Adding to the Dev list >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, Oct 1, 2015 at 7:05 AM, Imesh Gunaratne <im...@wso2.com> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Shall we move this discussion to Dev? >>>>>>>>>>>> >>>>>>>>>>>> Thanks >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Sep 30, 2015 at 11:02 PM, Gayan Gunarathne < >>>>>>>>>>>> gay...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> As puppet,init-scripts,base image are common for all the >>>>>>>>>>>>> cartridges,shall we group them under common? >>>>>>>>>>>>> Also what about the configurator?I can see two options >>>>>>>>>>>>> One option will be move the configurator to the private-paas >>>>>>>>>>>>> repository and release it with the private paas.Other option will >>>>>>>>>>>>> be we can >>>>>>>>>>>>> do the separate release for the configurator.Seems it is better >>>>>>>>>>>>> to have a >>>>>>>>>>>>> separate release for the configurator. WDYT? >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> Gayan >>>>>>>>>>>>> >>>>&
Re: [Dev] [Private PaaS] API Manager template module seems be messed up
Hi Guys,
Have we fixed the two issues discussed in this thread? If not, better to
track it via a JIRA.
Thanks,
Raj.
On Thu, Sep 10, 2015 at 4:53 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:
> Hi,
>
> +1 for this approach
>
> What we initially thought was to list down all the parameters in the
> module.ini file which are not default values. User can either override
> those values from environment variables or use the module.ini file.
>
> Thank you!
>
> On Thu, Sep 10, 2015 at 10:16 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> What I meant is, why don't we do this?
>>
>> if CONFIG_PARAM_LOCAL_MEMBER_HOST is set {
>> {{ CONFIG_PARAM_LOCAL_MEMBER_HOST
>> }}
>> } else {
>> 127.0.0.1
>> }
>>
>> Thanks.
>>
>> On Thu, Sep 10, 2015 at 3:59 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
>> wrote:
>>
>>> Any reason to treat the following config parameters differently, than
>>> other config parameters?
>>>
>>> CONFIG_PARAM_CLUSTERING=false
>>> CONFIG_PARAM_DOMAIN=wso2.carbon.domain
>>> CONFIG_PARAM_WKA_MEMBERS=[127.0.0.1:4000]
>>> CONFIG_PARAM_LOCAL_MEMBER_HOST=127.0.0.1
>>> CONFIG_PARAM_LOCAL_MEMBER_PORT=4000
>>> CONFIG_PARAM_PORT_OFFSET=0
>>> CONFIG_PARAM_MB_PORT=61616
>>> CONFIG_PARAM_EMBEDDED_LDAP=true
>>>
>>> These are enabled in module.ini file by default, where as other
>>> parameters are disabled. And the default values of these config elements
>>> are removed from templates files and moved to module.ini.
>>>
>>> This is not consistent with other config parameters. Because of this, we
>>> always have to pass these parameters to configurator, even though we don't
>>> need to override the default ones.
>>>
>>> By accident, I commented out all the config parameters from module.ini
>>> and I have passed only the needed parameters to the configurator as
>>> environment variables via puppet. I ended up with some issues since I
>>> haven't pass the above parameters as environment variables (even though I
>>> don't want to override the default ones!). So isn't good if leave the
>>> default values in the template files itself? This way, we don't have
>>> explicitly pass the default values, just like other config parameters.
>>>
>>> wdyt?
>>>
>>> Thanks,
>>> Raj.
>>>
>>> On Tue, Sep 8, 2015 at 1:19 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Tue, Sep 8, 2015 at 1:16 AM, Reka Thirunavukkarasu <r...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Raj,
>>>>>
>>>>> Yah..Seems some old reference is there in the
>>>>> master-datasources.xml.template which will not affect the configurations,
>>>>> if the parameters are defined correctly in the cartridge definition.
>>>>> Please
>>>>> ignore the section with CONFIG_PARAM_CONFIG_DB_APIM_URL.
>>>>>
>>>>> Please refer [1] for the sample configuration. We will clean this in
>>>>> the immediate next release(beta)..
>>>>>
>>>>
>>>> +1. Not a blocker or urgent.
>>>>
>>>>
>>>>>
>>>>> [1]
>>>>> https://github.com/wso2/product-private-paas/blob/master/samples/cartridges/ec2/wso2am-190/wso2am-190-gw-manager.json
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Mon, Sep 7, 2015 at 6:19 PM, Rajkumar Rajaratnam <
>>>>> rajkum...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I think API Manager's master-datasources.xml.template is messed up.
>>>>>> For example, same db username/password parameter is used for all the
>>>>>> databases and jdbc/WSO2REG_DB is defined twice with two different
>>>>>> if-checks, why?
>>>>>>
>>>>>> Please check and fix [1]. Please check other modules also.
>>>>>>
>>>>>> [1]
>>>>>> https://github.com/wso2/product-private-paas/blob/master/cartridges/templates-modules/wso2am-1.9.0/templates/repository/conf/datasources/master-datasources.xml.template
>>>>>>
>>>>>> Thanks,
>>>>>> Raj.
>>>>>>
>>>>>> --
>>>>>> Rajkumar Rajaratn
Re: [Dev] [Private PaaS] API Manager template module seems be messed up
What I meant is, why don't we do this?
if CONFIG_PARAM_LOCAL_MEMBER_HOST is set {
{{ CONFIG_PARAM_LOCAL_MEMBER_HOST
}}
} else {
127.0.0.1
}
Thanks.
On Thu, Sep 10, 2015 at 3:59 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
wrote:
> Any reason to treat the following config parameters differently, than
> other config parameters?
>
> CONFIG_PARAM_CLUSTERING=false
> CONFIG_PARAM_DOMAIN=wso2.carbon.domain
> CONFIG_PARAM_WKA_MEMBERS=[127.0.0.1:4000]
> CONFIG_PARAM_LOCAL_MEMBER_HOST=127.0.0.1
> CONFIG_PARAM_LOCAL_MEMBER_PORT=4000
> CONFIG_PARAM_PORT_OFFSET=0
> CONFIG_PARAM_MB_PORT=61616
> CONFIG_PARAM_EMBEDDED_LDAP=true
>
> These are enabled in module.ini file by default, where as other parameters
> are disabled. And the default values of these config elements are removed
> from templates files and moved to module.ini.
>
> This is not consistent with other config parameters. Because of this, we
> always have to pass these parameters to configurator, even though we don't
> need to override the default ones.
>
> By accident, I commented out all the config parameters from module.ini and
> I have passed only the needed parameters to the configurator as environment
> variables via puppet. I ended up with some issues since I haven't pass the
> above parameters as environment variables (even though I don't want to
> override the default ones!). So isn't good if leave the default values in
> the template files itself? This way, we don't have explicitly pass the
> default values, just like other config parameters.
>
> wdyt?
>
> Thanks,
> Raj.
>
> On Tue, Sep 8, 2015 at 1:19 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>>
>>
>> On Tue, Sep 8, 2015 at 1:16 AM, Reka Thirunavukkarasu <r...@wso2.com>
>> wrote:
>>
>>> Hi Raj,
>>>
>>> Yah..Seems some old reference is there in the
>>> master-datasources.xml.template which will not affect the configurations,
>>> if the parameters are defined correctly in the cartridge definition. Please
>>> ignore the section with CONFIG_PARAM_CONFIG_DB_APIM_URL.
>>>
>>> Please refer [1] for the sample configuration. We will clean this in the
>>> immediate next release(beta)..
>>>
>>
>> +1. Not a blocker or urgent.
>>
>>
>>>
>>> [1]
>>> https://github.com/wso2/product-private-paas/blob/master/samples/cartridges/ec2/wso2am-190/wso2am-190-gw-manager.json
>>>
>>> Thanks,
>>> Reka
>>>
>>> On Mon, Sep 7, 2015 at 6:19 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I think API Manager's master-datasources.xml.template is messed up. For
>>>> example, same db username/password parameter is used for all the databases
>>>> and jdbc/WSO2REG_DB is defined twice with two different if-checks, why?
>>>>
>>>> Please check and fix [1]. Please check other modules also.
>>>>
>>>> [1]
>>>> https://github.com/wso2/product-private-paas/blob/master/cartridges/templates-modules/wso2am-1.9.0/templates/repository/conf/datasources/master-datasources.xml.template
>>>>
>>>> Thanks,
>>>> Raj.
>>>>
>>>> --
>>>> Rajkumar Rajaratnam
>>>> Committer & PMC Member, Apache Stratos
>>>> Software Engineer, WSO2
>>>>
>>>> Mobile : +94777568639
>>>> Blog : rajkumarr.com
>>>>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Software Engineer, WSO2
>
> Mobile : +94777568639
> Blog : rajkumarr.com
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] API Manager template module seems be messed up
Any reason to treat the following config parameters differently, than other config parameters? CONFIG_PARAM_CLUSTERING=false CONFIG_PARAM_DOMAIN=wso2.carbon.domain CONFIG_PARAM_WKA_MEMBERS=[127.0.0.1:4000] CONFIG_PARAM_LOCAL_MEMBER_HOST=127.0.0.1 CONFIG_PARAM_LOCAL_MEMBER_PORT=4000 CONFIG_PARAM_PORT_OFFSET=0 CONFIG_PARAM_MB_PORT=61616 CONFIG_PARAM_EMBEDDED_LDAP=true These are enabled in module.ini file by default, where as other parameters are disabled. And the default values of these config elements are removed from templates files and moved to module.ini. This is not consistent with other config parameters. Because of this, we always have to pass these parameters to configurator, even though we don't need to override the default ones. By accident, I commented out all the config parameters from module.ini and I have passed only the needed parameters to the configurator as environment variables via puppet. I ended up with some issues since I haven't pass the above parameters as environment variables (even though I don't want to override the default ones!). So isn't good if leave the default values in the template files itself? This way, we don't have explicitly pass the default values, just like other config parameters. wdyt? Thanks, Raj. On Tue, Sep 8, 2015 at 1:19 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > > > On Tue, Sep 8, 2015 at 1:16 AM, Reka Thirunavukkarasu <r...@wso2.com> > wrote: > >> Hi Raj, >> >> Yah..Seems some old reference is there in the >> master-datasources.xml.template which will not affect the configurations, >> if the parameters are defined correctly in the cartridge definition. Please >> ignore the section with CONFIG_PARAM_CONFIG_DB_APIM_URL. >> >> Please refer [1] for the sample configuration. We will clean this in the >> immediate next release(beta).. >> > > +1. Not a blocker or urgent. > > >> >> [1] >> https://github.com/wso2/product-private-paas/blob/master/samples/cartridges/ec2/wso2am-190/wso2am-190-gw-manager.json >> >> Thanks, >> Reka >> >> On Mon, Sep 7, 2015 at 6:19 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I think API Manager's master-datasources.xml.template is messed up. For >>> example, same db username/password parameter is used for all the databases >>> and jdbc/WSO2REG_DB is defined twice with two different if-checks, why? >>> >>> Please check and fix [1]. Please check other modules also. >>> >>> [1] >>> https://github.com/wso2/product-private-paas/blob/master/cartridges/templates-modules/wso2am-1.9.0/templates/repository/conf/datasources/master-datasources.xml.template >>> >>> Thanks, >>> Raj. >>> >>> -- >>> Rajkumar Rajaratnam >>> Committer & PMC Member, Apache Stratos >>> Software Engineer, WSO2 >>> >>> Mobile : +94777568639 >>> Blog : rajkumarr.com >>> >>> >>> >>> _______ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Reka Thirunavukkarasu >> Senior Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: +94776442007 >> >> >> > > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 > Blog : rajkumarr.com > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Private PaaS] API Manager template module seems be messed up
Hi, I think API Manager's master-datasources.xml.template is messed up. For example, same db username/password parameter is used for all the databases and jdbc/WSO2REG_DB is defined twice with two different if-checks, why? Please check and fix [1]. Please check other modules also. [1] https://github.com/wso2/product-private-paas/blob/master/cartridges/templates-modules/wso2am-1.9.0/templates/repository/conf/datasources/master-datasources.xml.template Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] API Manager template module seems be messed up
On Tue, Sep 8, 2015 at 1:16 AM, Reka Thirunavukkarasu <r...@wso2.com> wrote: > Hi Raj, > > Yah..Seems some old reference is there in the > master-datasources.xml.template which will not affect the configurations, > if the parameters are defined correctly in the cartridge definition. Please > ignore the section with CONFIG_PARAM_CONFIG_DB_APIM_URL. > > Please refer [1] for the sample configuration. We will clean this in the > immediate next release(beta).. > +1. Not a blocker or urgent. > > [1] > https://github.com/wso2/product-private-paas/blob/master/samples/cartridges/ec2/wso2am-190/wso2am-190-gw-manager.json > > Thanks, > Reka > > On Mon, Sep 7, 2015 at 6:19 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi, >> >> I think API Manager's master-datasources.xml.template is messed up. For >> example, same db username/password parameter is used for all the databases >> and jdbc/WSO2REG_DB is defined twice with two different if-checks, why? >> >> Please check and fix [1]. Please check other modules also. >> >> [1] >> https://github.com/wso2/product-private-paas/blob/master/cartridges/templates-modules/wso2am-1.9.0/templates/repository/conf/datasources/master-datasources.xml.template >> >> Thanks, >> Raj. >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module
Hi, I think python-pip & jinja2 should be installed by configurator puppet module, not by python agent. I am using vagrant, puppet and configurator to setup my development environment, but I am not using python agent. Since $subject is not done, I had to modify configurator puppet module. It would be better if we do the $subject. Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Private PaaS] Set JAVA_HOME as part of java installation via puppet
Hi, I think we need to do $Subject. Thanks, Raj. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module
On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera <raviha...@wso2.com> wrote: > Hi Raj, > > I think we should not remove python-pip from PCA module since those > dependencies should be installed for PCA to function. > In the very similar way, python-pip should be installed for configurator to function as well :). So if I am using java agent instead of python agent, how would configurator work without python-pip? IMO, we can either move python-pip to stratos_base or use [1] to redfine python-pip package in configurator if it is not already defined anywhere else. [1] http://stackoverflow.com/questions/15266347/puppet-test-if-a-package-already-defined Thanks, Raj. > > @Anuruddha: I still see that jinja2 is packed from PCA module [1]. Shall > we move this to configurator module? > > [1] > https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/python_agent/manifests/initialize.pp#L57 > > Thanks. > > On Sat, Sep 5, 2015 at 3:21 PM, Anuruddha Liyanarachchi < > anurudd...@wso2.com> wrote: > >> Hi Raj, >> >> Thanks for pointing this out. I have now added the jinja2 dependency to >> configurator module and removed from PCA. [1] >> >> [1] >> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/configurator/manifests/init.pp#L32 >> >> On Sat, Sep 5, 2015 at 3:14 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I think python-pip & jinja2 should be installed by configurator puppet >>> module, not by python agent. >>> >>> I am using vagrant, puppet and configurator to setup my development >>> environment, but I am not using python agent. Since $subject is not done, I >>> had to modify configurator puppet module. >>> >>> It would be better if we do the $subject. >>> >>> Thanks, >>> Raj. >>> >>> -- >>> Rajkumar Rajaratnam >>> Committer & PMC Member, Apache Stratos >>> Software Engineer, WSO2 >>> >>> Mobile : +94777568639 >>> Blog : rajkumarr.com >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Thanks and Regards,* >> Anuruddha Lanka Liyanarachchi >> Software Engineer - WSO2 >> Mobile : +94 (0) 712762611 >> Tel : +94 112 145 345 >> a <thili...@wso2.com>nurudd...@wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] Set JAVA_HOME as part of java installation via puppet
Great. Thanks Anuruddha! On Sun, Sep 6, 2015 at 5:21 PM, Anuruddha Liyanarachchi <anurudd...@wso2.com > wrote: > Hi Raj, > > I have done $subject. > > On Sun, Sep 6, 2015 at 9:37 AM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi, >> >> I think we need to do $Subject. >> >> Thanks, >> Raj. >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> > > > > -- > *Thanks and Regards,* > Anuruddha Lanka Liyanarachchi > Software Engineer - WSO2 > Mobile : +94 (0) 712762611 > Tel : +94 112 145 345 > a <thili...@wso2.com>nurudd...@wso2.com > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Status update] Adding single tenant cartridge support to appfactory
Hi Anuruddha,
Cluster monitor can be created in two situations.
1) when a cluster is created for the first time (application deployment
time)
2) when stratos is restarted
If cluster monitor creation failed, it would log enough information about
it (some error logs like Monitor creation failed, even after retrying for
5 times) . You can trace back the logs and see the reason for it. I don't
think scenario 1) is the reason for the above behaviour, because the
members will not be created if the cluster monitor creation failed.
Scenario 2) can be one reason for this behaviour. If it is the reason, then
you should be able to see some error logs regarding cluster monitor
creation failed. Have you restarted stratos?
Further, *A cluster monitor is not found in autoscaler context *error
doesn't necessarily mean that cluster monitor creation failed. It can be
because cluster is undeployed and the monitor is removed before getting
this event from CEP.
If you could attach the complete log, we will be able to point out the
issue.
Thanks,
Raj.
On Mon, Aug 3, 2015 at 11:32 AM, Anuruddha Premalal anurud...@wso2.com
wrote:
Also this setup use kubernetes as the IaaS
On Mon, Aug 3, 2015 at 11:31 AM, Anuruddha Premalal anurud...@wso2.com
wrote:
Hi,
I am working on $subject.
In the current appfactory setup we have a single JVM Stratos 4.1.0
deployment. I am trying to get the autoscaling working since resetting the
SM node each time of failure consumes time. Once a member fault event
received to AS receives it but unable to continue with the following log.
When will the cluster monitor get initiated? What would are the
possibilities for failing the initialization of the cluster monitor?
*INFO {org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} -
Faulty member detected [member-id]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988
with [last time-stamp] 1438580270973 [time-out] 6 milliseconds*
*TID: [0] [SCC] [2015-08-03 11:26:38,956] INFO
{org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} -
Publishing member fault event for [member-id]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988*
*TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG
{org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver}
- Member fault event received: [member]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988
*
*TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG
{org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver}
- A cluster monitor is not found in autoscaler context [cluster]
asdevelopment.anuasdevelopment.anuasdevelopment.domain*
Thanks Regards,
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Status update] Adding single tenant cartridge support to appfactory
Monitors were not created because CompleteTopologyEvent was published
before AutoscalerComponent was activated. In the attached logs,
Line number 478 - CompleteTopologyEvent was received by AS
Line number 501 - AutoscalerComponent was activated
When AS received CompleteTopologyEvent, it didn't load the application
context from registry. Hence it just logged The application is not yet
deployed for this [application] asdevelopment (Line number 482) and
ignored the CompleteTopologyEvent. And CompleteTopologyEvent is published
only once (until topology is initialized) - so there is no way that the
monitors will be created.
It needs to be fixed.
Thanks,
Raj.
On Mon, Aug 3, 2015 at 12:06 PM, Anuruddha Premalal anurud...@wso2.com
wrote:
HI Raj,
i'm attaching the carbon log file herewith.
On Mon, Aug 3, 2015 at 11:52 AM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Hi Anuruddha,
Cluster monitor can be created in two situations.
1) when a cluster is created for the first time (application deployment
time)
2) when stratos is restarted
If cluster monitor creation failed, it would log enough information about
it (some error logs like Monitor creation failed, even after retrying for
5 times) . You can trace back the logs and see the reason for it. I don't
think scenario 1) is the reason for the above behaviour, because the
members will not be created if the cluster monitor creation failed.
Scenario 2) can be one reason for this behaviour. If it is the reason, then
you should be able to see some error logs regarding cluster monitor
creation failed. Have you restarted stratos?
Further, *A cluster monitor is not found in autoscaler context *error
doesn't necessarily mean that cluster monitor creation failed. It can be
because cluster is undeployed and the monitor is removed before getting
this event from CEP.
If you could attach the complete log, we will be able to point out the
issue.
Thanks,
Raj.
On Mon, Aug 3, 2015 at 11:32 AM, Anuruddha Premalal anurud...@wso2.com
wrote:
Also this setup use kubernetes as the IaaS
On Mon, Aug 3, 2015 at 11:31 AM, Anuruddha Premalal anurud...@wso2.com
wrote:
Hi,
I am working on $subject.
In the current appfactory setup we have a single JVM Stratos 4.1.0
deployment. I am trying to get the autoscaling working since resetting the
SM node each time of failure consumes time. Once a member fault event
received to AS receives it but unable to continue with the following log.
When will the cluster monitor get initiated? What would are the
possibilities for failing the initialization of the cluster monitor?
*INFO {org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} -
Faulty member detected [member-id]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988
with [last time-stamp] 1438580270973 [time-out] 6 milliseconds*
*TID: [0] [SCC] [2015-08-03 11:26:38,956] INFO
{org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} -
Publishing member fault event for [member-id]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988*
*TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG
{org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver}
- Member fault event received: [member]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988
*
*TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG
{org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver}
- A cluster monitor is not found in autoscaler context [cluster]
asdevelopment.anuasdevelopment.anuasdevelopment.domain*
Thanks Regards,
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Status update] Adding single tenant cartridge support to appfactory
Hi Anuruddha,
I guess we have already fixed this issue sometimes back. I went though the
log again and found that you haven't enabled Component startup
synchronizer. If you enable it, it will ensure that CompleteTopologyEvent
will be published only after SM is activated (SM will be activated only
after AS).
In your logs, have a look at line number 402 : Component startup
synchronizer enabled: false
Please check whether your bin/stratos.sh have
-Dstratos.component.startup.synchronizer.enabled=true. If not, add it.
Please let us know whether it resolves your issue.
Thanks,
Raj.
On Mon, Aug 3, 2015 at 12:59 PM, Anuruddha Premalal anurud...@wso2.com
wrote:
Hi Raj,
Thanks for the support given in finding the issue.I couldn't find a public
stratos jira for this so I've raised jira[1] to track this.
[1] https://issues.apache.org/jira/browse/STRATOS-1487
On Mon, Aug 3, 2015 at 12:43 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Monitors were not created because CompleteTopologyEvent was published
before AutoscalerComponent was activated. In the attached logs,
Line number 478 - CompleteTopologyEvent was received by AS
Line number 501 - AutoscalerComponent was activated
When AS received CompleteTopologyEvent, it didn't load the application
context from registry. Hence it just logged The application is not yet
deployed for this [application] asdevelopment (Line number 482) and
ignored the CompleteTopologyEvent. And CompleteTopologyEvent is published
only once (until topology is initialized) - so there is no way that the
monitors will be created.
It needs to be fixed.
Thanks,
Raj.
On Mon, Aug 3, 2015 at 12:06 PM, Anuruddha Premalal anurud...@wso2.com
wrote:
HI Raj,
i'm attaching the carbon log file herewith.
On Mon, Aug 3, 2015 at 11:52 AM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Hi Anuruddha,
Cluster monitor can be created in two situations.
1) when a cluster is created for the first time (application deployment
time)
2) when stratos is restarted
If cluster monitor creation failed, it would log enough information
about it (some error logs like Monitor creation failed, even after
retrying for 5 times) . You can trace back the logs and see the reason for
it. I don't think scenario 1) is the reason for the above behaviour,
because the members will not be created if the cluster monitor creation
failed. Scenario 2) can be one reason for this behaviour. If it is the
reason, then you should be able to see some error logs regarding cluster
monitor creation failed. Have you restarted stratos?
Further, *A cluster monitor is not found in autoscaler context *error
doesn't necessarily mean that cluster monitor creation failed. It can
be because cluster is undeployed and the monitor is removed before getting
this event from CEP.
If you could attach the complete log, we will be able to point out the
issue.
Thanks,
Raj.
On Mon, Aug 3, 2015 at 11:32 AM, Anuruddha Premalal anurud...@wso2.com
wrote:
Also this setup use kubernetes as the IaaS
On Mon, Aug 3, 2015 at 11:31 AM, Anuruddha Premalal
anurud...@wso2.com wrote:
Hi,
I am working on $subject.
In the current appfactory setup we have a single JVM Stratos 4.1.0
deployment. I am trying to get the autoscaling working since resetting
the
SM node each time of failure consumes time. Once a member fault event
received to AS receives it but unable to continue with the following log.
When will the cluster monitor get initiated? What would are the
possibilities for failing the initialization of the cluster monitor?
*INFO {org.apache.stratos.cep.extension.FaultHandlingWindowProcessor}
- Faulty member detected [member-id]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988
with [last time-stamp] 1438580270973 [time-out] 6 milliseconds*
*TID: [0] [SCC] [2015-08-03 11:26:38,956] INFO
{org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} -
Publishing member fault event for [member-id]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988*
*TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG
{org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver}
- Member fault event received: [member]
asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988
*
*TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG
{org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver}
- A cluster monitor is not found in autoscaler context [cluster]
asdevelopment.anuasdevelopment.anuasdevelopment.domain*
Thanks Regards,
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software
Re: [Dev] Install Stratos with kubernetes-JDK Version is not in the allowed range
Yes. JDK 1.8.x is not supported yet. Please use 1.7.x. Thanks, Raj. On Thu, Jul 30, 2015 at 4:20 AM, Heshan Jayasinghe shanu...@gmail.com wrote: Hi Devs, i use Install Stratos with Kubernetes in a Testing Environment https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Install+Stratos+with+Kubernetes+in+a+Testing+Environment to build Stratos.After git clone i do mvn clean install.it gives, Detected JDK Version: 1.8.0-40 is not in the allowed range [1.6,1.8) Do i need to downgrade my java version to install Stratos?i am useing OSX Yosemite with JDK 1.8. Thankyou! regards, Heshan jayasinghe ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Install Stratos with kubernetes-JDK Version is not in the allowed range
Also, you should ask this question on stratos dev mailing list ( d...@stratos.apache.org). On Thu, Jul 30, 2015 at 4:23 AM, Rajkumar Rajaratnam rajkum...@wso2.com wrote: Yes. JDK 1.8.x is not supported yet. Please use 1.7.x. Thanks, Raj. On Thu, Jul 30, 2015 at 4:20 AM, Heshan Jayasinghe shanu...@gmail.com wrote: Hi Devs, i use Install Stratos with Kubernetes in a Testing Environment https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Install+Stratos+with+Kubernetes+in+a+Testing+Environment to build Stratos.After git clone i do mvn clean install.it gives, Detected JDK Version: 1.8.0-40 is not in the allowed range [1.6,1.8) Do i need to downgrade my java version to install Stratos?i am useing OSX Yosemite with JDK 1.8. Thankyou! regards, Heshan jayasinghe ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
On Mon, Jul 27, 2015 at 9:24 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Thanks a lot Tharindu for confirming it. I guess it is better to update
the pre-configured pack with this change.
I meant it is better to remove TenantConfig.properties file from
pre-configured IS pack.
Thanks,
Raj.
On Mon, Jul 27, 2015 at 9:21 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
I tested the same and reproduced the issue... The fix is to delete the
TenantConfig.properties file from IS_HOME/repository/conf/ directory.
Ideally this file should not be there with Service Pack 1. I wonder how it
got there because this was introduced in patch1040 which was released after
service pack 1. If the TenantConfig.properties file is in conf directory,
then there should be the latest authentication.endpoint webapp from support
branch.
Regards,
Tharindu
On Mon, Jul 27, 2015 at 8:19 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
This was done after SP1 release. You can find the source for the custom
secret callback handler in the patch1040 [1]. But this is needed only if
the Tenat List Dropdown feature [2] in the SSO login page is enabled and
also if secure vault is added for the TenantConfig.properties file. By
default this feature is disabled. If we get the error when this feature is
disabled, it is not correct. If so we need to patch authentication.endpoint
webapp that is delivered in the pack. Let's have a review on this tomorrow.
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch1040/
[2]
http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html
On Mon, Jul 27, 2015 at 3:15 PM, Darshana Gunawardana darsh...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com
wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam
rajkum...@wso2.com wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is
added. We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next
release of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
Thanks a lot Tharindu for confirming it. I guess it is better to update the
pre-configured pack with this change.
Thanks,
Raj.
On Mon, Jul 27, 2015 at 9:21 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
I tested the same and reproduced the issue... The fix is to delete the
TenantConfig.properties file from IS_HOME/repository/conf/ directory.
Ideally this file should not be there with Service Pack 1. I wonder how it
got there because this was introduced in patch1040 which was released after
service pack 1. If the TenantConfig.properties file is in conf directory,
then there should be the latest authentication.endpoint webapp from support
branch.
Regards,
Tharindu
On Mon, Jul 27, 2015 at 8:19 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
This was done after SP1 release. You can find the source for the custom
secret callback handler in the patch1040 [1]. But this is needed only if
the Tenat List Dropdown feature [2] in the SSO login page is enabled and
also if secure vault is added for the TenantConfig.properties file. By
default this feature is disabled. If we get the error when this feature is
disabled, it is not correct. If so we need to patch authentication.endpoint
webapp that is delivered in the pack. Let's have a review on this tomorrow.
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch1040/
[2]
http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html
On Mon, Jul 27, 2015 at 3:15 PM, Darshana Gunawardana darsh...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam
rajkum...@wso2.com wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is added.
We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next release
of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178) at org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47) at org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56) at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) [1] https://docs.wso2.com/display/CLUSTER420/Configuring+the+Pre-Packaged+Identity+Server+5.0.0+with+API+Manager+1.9.0 Thanks, Raj. Regards, TharinduE On Sun, Apr 26, 2015 at 7:32 AM, Firzhan Naqash firz...@wso2.com wrote: Hi Thraindhu/Darshana, And also IMO, we should make sure it does not throw CNF errors in the console, in the event of mutual SSL authentication is disabled and it doesn't have the custom authentication jar inside the authenticanendpoint/WEB-INF/lib. Regards, Firzhan On Sat, Apr 25, 2015 at 3:49 PM, Tharindu Edirisinghe tharin...@wso2.com wrote: Hi Darshana, +1. Yes, IMO we should ship the mutual ssl authenticator with the new release so that the features like tenant list dropdown in SSO login page would work OOTB with only configuration changes. Thanks, TharinduE On Sun, Apr 26, 2015 at 2:13 AM, Darshana Gunawardana darsh...@wso2.com wrote: Hi Devs, IS 5.0.0 does not have mutual authenticator shipped with 5.0.0. But in the SP it has instructions to copy it to dropins. How about shipping it in the standard distribution from 5.1.0 onwards. Thanks, Darshana -- Regards, *Darshana Gunawardana*Software Engineer WSO2 Inc.; http://wso2.com *E-mail: darsh...@wso2.com darsh...@wso2.com* *Mobile: +94718566859 %2B94718566859*Lean . Enterprise . Middleware -- Tharindu Edirisinghe Software Engineer | WSO2 Inc Identity Server Team mobile : +94 775 181586 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Tharindu Edirisinghe Software Engineer | WSO2 Inc Identity Server Team mobile : +94 775 181586 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to find JIRA number from JIRE attachment number?
Hi, I don't how to get JIRA number from attachment number :). But here is the JIRA you are searching for. https://wso2.org/jira/browse/TOOLS-2674 Thanks, Raj. On Tue, Jun 30, 2015 at 10:02 PM, John Hawkins jo...@wso2.com wrote: Hi Folks, I'm working my way through the WSO2 training exercises and have hit a problem when redeploying the HiRollerBankProject to the ESB. The redeploy fails with a webcontext error saying that there is an unexpected colon at start of token. which appears to start in carbonserver.base.utils.CarbonServerUtils.getWebContextRoot(CarbonServerUtils.java:164) I think this may well be a known problem as a google search points me to - https://wso2.org/jira/secure/attachment/35542/ Which is the exact same message that I get. My problem is that I don't know how to get from the attachment number to the JIRA number :-( So, can anyone tell me how to find out what JIRA this attachment is related to please? I can then figure out whether it is exactly the same problem as I am seeing. many thanks ! John. John Hawkins Director: Solutions Architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to find JIRA number from JIRE attachment number?
s/ I don't how/ I don't know how On Tue, Jun 30, 2015 at 10:22 PM, Rajkumar Rajaratnam rajkum...@wso2.com wrote: Hi, I don't how to get JIRA number from attachment number :). But here is the JIRA you are searching for. https://wso2.org/jira/browse/TOOLS-2674 Thanks, Raj. On Tue, Jun 30, 2015 at 10:02 PM, John Hawkins jo...@wso2.com wrote: Hi Folks, I'm working my way through the WSO2 training exercises and have hit a problem when redeploying the HiRollerBankProject to the ESB. The redeploy fails with a webcontext error saying that there is an unexpected colon at start of token. which appears to start in carbonserver.base.utils.CarbonServerUtils.getWebContextRoot(CarbonServerUtils.java:164) I think this may well be a known problem as a google search points me to - https://wso2.org/jira/secure/attachment/35542/ Which is the exact same message that I get. My problem is that I don't know how to get from the attachment number to the JIRA number :-( So, can anyone tell me how to find out what JIRA this attachment is related to please? I can then figure out whether it is exactly the same problem as I am seeing. many thanks ! John. John Hawkins Director: Solutions Architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB] ClientApiNonBlocking Property JMS Transport
Hi, Doc [1] says that removal of ClientApiNonBlocking property could be vital when queueing transports like JMS are involved. - Does it mean that we should always remove this property when JMS is involved somewhere in our proxy? Lets say, I am consuming messages using JMS and sending it out using JMS, do I still need to remove this property? Or do we need to remove this property only if ESB consumes messages using a streaming transports (like VFS) and sending it out using JMS? If yes, then doc seems to be confusing. Please share your thoughts on this. [1] https://docs.wso2.com/display/ESB481/Generic+Properties#GenericProperties-ClientApiNonBlockingBlocking Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [WSO2 ESB 4.8.1] Getting javax.xml.stream.XMLStreamException: ParseError at [row, col]:[1, 1] Message: Premature end of file while invoking an API
) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:68) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47) at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131) at org.apache.synapse.rest.Resource.process(Resource.java:297) at org.apache.synapse.rest.API.process(API.java:298) at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:76) at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:50) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: Premature end of file. at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296) at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109) at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570) at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566) at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:129) at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107) ... 17 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1] Message: Premature end of file. at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:598) at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225) at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34) at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225) at org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138) at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214) ... 22 more [2015-05-09 12:40:46,600] INFO - LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:855ded2e-e18f-4f9d-8f5b-e40b6bac4ef8, Direction: response, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Error while building message, Envelope: ?xml version=1.0 encoding=utf-8?soapenv:Envelope xmlns:soapenv= http://www.w3.org/2003/05/soap-envelope soapenv:Body/soapenv:Body/soapenv:Envelope Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [WSO2 ESB 4.8.1] Getting javax.xml.stream.XMLStreamException: ParseError at [row, col]:[1, 1] Message: Premature end of file while invoking an API
(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.axiom.om.OMException:
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
Message: Premature end of file.
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
at
org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:129)
at
org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107)
... 17 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[1,1]
Message: Premature end of file.
at
com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:598)
at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at
org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at
org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
... 22 more
[2015-05-09 13:56:14,118] INFO - LogMediator To:
http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: ,
MessageID: urn:uuid:bd88966e-262a-4fcc-a4f2-2fe7bae1ae01, Direction:
response, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0,
ERROR_MESSAGE = Error while building message, Envelope: ?xml version=1.0
encoding=utf-8?soapenv:Envelope xmlns:soapenv=
http://www.w3.org/2003/05/soap-envelope
soapenv:Body/soapenv:Body/soapenv:Envelope
[2015-05-09 13:57:14,143] DEBUG - SourceHandler http-incoming-1: Timeout
[2015-05-09 13:57:14,143] WARN - SourceHandler Connection time out after
request is read: http-incoming-1
[2015-05-09 13:57:14,143] DEBUG - SourceConnections Shutting down
connection forcefully http-incoming-1
[2015-05-09 13:57:14,143] DEBUG - LoggingNHttpServerConnection
http-incoming-1: Shutdown connection
[2015-05-09 13:57:14,144] DEBUG - SourceHandler http-incoming-1: Closed
[2015-05-09 13:57:14,144] DEBUG - SourceHandler http-incoming-1: Keep-Alive
connection was closed: http-incoming-1
[2015-05-09 13:57:14,144] DEBUG - SourceConnections Shutting down
connection forcefully http-incoming-1
[2015-05-09 13:57:14,144] DEBUG - LoggingNHttpServerConnection
http-incoming-1: Shutdown connection
[2015-05-09 13:57:14,164] DEBUG - LoggingNHttpClientConnection
http-outgoing-1: Consume input
[2015-05-09 13:57:14,165] DEBUG - TargetHandler http-outgoing-1: End of
input
[2015-05-09 13:57:14,165] DEBUG - LoggingNHttpClientConnection
http-outgoing-1: Close connection
[2015-05-09 13:57:14,165] DEBUG - TargetHandler http-outgoing-1: Closed
[2015-05-09 13:57:14,165] DEBUG - TargetHandler http-outgoing-1: Keep-Alive
Connection closed
[2015-05-09 13:57:14,166] DEBUG - LoggingNHttpClientConnection
http-outgoing-1: Shutdown connection
On Sat, May 9, 2015 at 1:36 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Hi,
I followed
https://docs.wso2.com/display/ESB481/Configuring+Specific+Use+Cases#ConfiguringSpecificUseCases-Transformingthecontenttype
to create an API in ESB 4.8.1 to expose a service hosted on AS 5.2.1.
Full API definition is there in the above doc. I am pasting the resource
that I am invoking.
api xmlns=http://ws.apache.org/ns/synapse; name=StarbucksService
context=/Starbucks_Service
.
.
resource methods=DELETE GET uri-template=/orders/{id}
inSequence
property name=REST_URL_POSTFIX
expression=fn:concat('/orders/',get-property('
uri.var.id'))
scope=axis2/
send
endpoint
address uri=
http://localhost:9764/StarbucksService/services/Starbucks_Outlet_Service/
/
/endpoint
/send
/inSequence
outSequence
log level=full/
property name=messageType value=application/xml
scope=axis2/
send/
/outSequence
/resource
/api
When I call the API *(curl -v -X GET
http://localhost:8280/Starbucks_Service/orders/123
http://localhost:8280/Starbucks_Service/orders/123)*, I am getting the
below exception. What would be the issue here?
[2015-05
Re: [Dev] [WSO2 ESB 4.8.1] Getting javax.xml.stream.XMLStreamException: ParseError at [row, col]:[1, 1] Message: Premature end of file while invoking an API
It turned out that there was a problem in my back end service hosted on AS.
Everything works fine after fixing the back end.
Thanks.
On Sat, May 9, 2015 at 2:01 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Wire Logs;
[2015-05-09 13:56:14,068] DEBUG - SourceHandler http-incoming-1: Connected
[2015-05-09 13:56:14,069] DEBUG - LoggingNHttpServerConnection
http-incoming-1: Consume input
[2015-05-09 13:56:14,070] DEBUG - wire GET
/Starbucks_Service/orders/123 HTTP/1.1[\r][\n]
[2015-05-09 13:56:14,070] DEBUG - wire User-Agent: curl/7.35.0[\r][\n]
[2015-05-09 13:56:14,070] DEBUG - wire Host: localhost:8280[\r][\n]
[2015-05-09 13:56:14,070] DEBUG - wire Accept: */*[\r][\n]
[2015-05-09 13:56:14,070] DEBUG - wire [\r][\n]
[2015-05-09 13:56:14,072] DEBUG - headers http-incoming-1 GET
/Starbucks_Service/orders/123 HTTP/1.1
[2015-05-09 13:56:14,072] DEBUG - headers http-incoming-1 User-Agent:
curl/7.35.0
[2015-05-09 13:56:14,072] DEBUG - headers http-incoming-1 Host:
localhost:8280
[2015-05-09 13:56:14,072] DEBUG - headers http-incoming-1 Accept: */*
[2015-05-09 13:56:14,073] DEBUG - SourceHandler http-incoming-1: GET
/Starbucks_Service/orders/123 HTTP/1.1
[2015-05-09 13:56:14,078] DEBUG - ServerWorker Starting a new Server
Worker instance
[2015-05-09 13:56:14,091] INFO - TimeoutHandler This engine will expire
all callbacks after : 120 seconds, irrespective of the timeout action,
after the specified or optional timeout
[2015-05-09 13:56:14,095] DEBUG - TargetConnections Trying to get a
connection {}-http://localhost:9764
[2015-05-09 13:56:14,095] DEBUG - HostConnections Creating new connection
pool: {}-http://localhost:9764
[2015-05-09 13:56:14,096] DEBUG - ConnectCallback Connected to remote
address: localhost/127.0.0.1:9764 from local address: /127.0.0.1:38049
[2015-05-09 13:56:14,098] DEBUG - TargetHandler http-outgoing-1: Connected
(org.apache.synapse.transport.passthru.connections.HostConnections@72b5d077
)
[2015-05-09 13:56:14,099] DEBUG - HostConnections New connection {}-
http://localhost:9764 is added to the free list
[2015-05-09 13:56:14,099] DEBUG - TargetConnections Trying to get a
connection {}-http://localhost:9764
[2015-05-09 13:56:14,099] DEBUG - HostConnections Returning an existing
free connection {}-http://localhost:9764
[2015-05-09 13:56:14,099] DEBUG - DeliveryAgent Submitting new request to
the connection: http-outgoing-1
[2015-05-09 13:56:14,101] DEBUG - LoggingNHttpClientConnection
http-outgoing-1: Produce output
[2015-05-09 13:56:14,101] DEBUG - TargetHandler http-outgoing-1: Request
ready
[2015-05-09 13:56:14,103] DEBUG - LoggingNHttpClientConnection
http-outgoing-1: GET
/StarbucksService/services/Starbucks_Outlet_Service/orders/123 HTTP/1.1
[2015-05-09 13:56:14,103] DEBUG - headers http-outgoing-1 GET
/StarbucksService/services/Starbucks_Outlet_Service/orders/123 HTTP/1.1
[2015-05-09 13:56:14,103] DEBUG - headers http-outgoing-1 Accept: */*
[2015-05-09 13:56:14,103] DEBUG - headers http-outgoing-1 Host:
localhost:9764
[2015-05-09 13:56:14,103] DEBUG - headers http-outgoing-1 Connection:
Keep-Alive
[2015-05-09 13:56:14,103] DEBUG - headers http-outgoing-1 User-Agent:
Synapse-PT-HttpComponents-NIO
[2015-05-09 13:56:14,103] DEBUG - LoggingNHttpClientConnection
http-outgoing-1: Produce output
[2015-05-09 13:56:14,104] DEBUG - wire GET
/StarbucksService/services/Starbucks_Outlet_Service/orders/123
HTTP/1.1[\r][\n]
[2015-05-09 13:56:14,104] DEBUG - wire Accept: */*[\r][\n]
[2015-05-09 13:56:14,104] DEBUG - wire Host: localhost:9764[\r][\n]
[2015-05-09 13:56:14,104] DEBUG - wire Connection: Keep-Alive[\r][\n]
[2015-05-09 13:56:14,104] DEBUG - wire User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]
[2015-05-09 13:56:14,104] DEBUG - wire [\r][\n]
[2015-05-09 13:56:14,104] DEBUG - TargetHandler http-outgoing-1: Request
ready
[2015-05-09 13:56:14,105] DEBUG - LoggingNHttpClientConnection
http-outgoing-1: Consume input
[2015-05-09 13:56:14,105] DEBUG - wire HTTP/1.1 302 Found[\r][\n]
[2015-05-09 13:56:14,105] DEBUG - wire Set-Cookie:
JSESSIONID=AEAFCCBB7D2AAE182F1079F1A5987FDB; Path=/; HttpOnly[\r][\n]
[2015-05-09 13:56:14,105] DEBUG - wire Location:
https://172.17.42.1:9444/carbon/[\r][\n];
[2015-05-09 13:56:14,105] DEBUG - wire Content-Type:
text/html;charset=UTF-8[\r][\n]
[2015-05-09 13:56:14,105] DEBUG - wire Content-Length: 0[\r][\n]
[2015-05-09 13:56:14,106] DEBUG - wire Date: Sat, 09 May 2015 08:26:14
GMT[\r][\n]
[2015-05-09 13:56:14,106] DEBUG - wire Server: WSO2 Carbon
Server[\r][\n]
[2015-05-09 13:56:14,106] DEBUG - wire [\r][\n]
[2015-05-09 13:56:14,106] DEBUG - headers http-outgoing-1 HTTP/1.1 302
Found
[2015-05-09 13:56:14,106] DEBUG - headers http-outgoing-1 Set-Cookie:
JSESSIONID=AEAFCCBB7D2AAE182F1079F1A5987FDB; Path=/; HttpOnly
[2015-05-09 13:56:14,106] DEBUG - headers http-outgoing-1 Location:
https://172.17.42.1:9444/carbon/
[2015-05-09 13:56:14,106
Re: [Dev] [Private Pass] Configurator component (bash) for configuring a given Carbon server
On Tue, May 5, 2015 at 5:52 PM, Rajkumar Rajaratnam rajkum...@wso2.com wrote: Hi Anuruddha, Configurator generates carbon server configurations files? Or it just changes the parameters in default carbon server configurations files, by reading parameters from somewhere? I hope this is similar to puppet, where we keep some default carbon sever configuration template files and change parameters using tags, etc. Please confirm it. Okay. I can see that Jinja2 is a template engine (with BSD Licence). I would like to see the format of the file from which Configurator reads the configurations. Can you please paste that here? Thanks. On Tue, May 5, 2015 at 5:43 PM, Anuruddha Liyanarachchi anurudd...@wso2.com wrote: Hi Devs, I have created the $subject using python and Jinja2. Configurator is now capable of generating axis2.xml, Carbon.xml and catalina-server.xml based on clustering configurations. Following structure was used to create the configurator. Currently these configurations are read from a file. I will update the thread as I move on. . ├── Configurator.iml ├── Constants.py ├── Constants.pyc ├── Main.py ├── Output | ├── axis2.xml | ├── carbon.xml | └── catalina-server.xml └── Templates └── AppServer └── conf ├── axis2.jinja ├── carbon.jinja └── catalina-server.jinja On Thu, Apr 30, 2015 at 12:05 PM, Anuruddha Liyanarachchi anurudd...@wso2.com wrote: Hi , I am working on $subject. I am trying create a shell script which generate carbon server configuration based on parameters provided by different run times. Configurator is basically configuring perviously used puppet templates using shell. Please refer mail thread subject as [PPaaS] Private PaaS 4.1.0 Release Plan for more info. I will provide more information as I progress. -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a thili...@wso2.comnurudd...@wso2.com -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a thili...@wso2.comnurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private Pass] Configurator component (bash) for configuring a given Carbon server
On Tue, May 5, 2015 at 7:15 PM, Anuruddha Liyanarachchi anurudd...@wso2.com
wrote:
Hi Raj,
I hope this is similar to puppet, where we keep some default carbon sever
configuration template files and change parameters using tags, etc. Please
confirm it.
Configurator changes the parameters in default carbon server
configurations files by reading parameters from a file.
This is similar to puppet.
I would like to see the format of the file from which Configurator reads
the configurations. Can you please paste that here?
Please find the sample configurations file below.
[DEFAULTS]
clustering=true
members={mgt.as.wso2.com: 4100,as.wso2.com: 4300}
localMemberHost= 127.0.1.1
localMemberPort= 4100
subDomain= mgt
stratos_instance_data_worker_host_name= as.wso2.com
stratos_instance_data_mgt_host_name= mgt.as.wso2.com
portOffset=1
http_proxy_port=80
https_proxy_port=443
We should have something similar node definition in puppet right?
Otherwise, this configuration will get applied to all nodes, regardless of
whether they are AS, ESB etc? Or is there any other way to handle it?
Thanks.
On Tue, May 5, 2015 at 7:09 PM, Reka Thirunavukkarasu r...@wso2.com
wrote:
Hi Anuriddha,
Good work in getting the Configurator also with template model. As you
have mentioned, now we can process only few files. If we are to add new
files, just writing *.jinja file is enough or do we need to configure
something about this file somewhere like in puppet we mentioned in the
manifests?
Thanks,
Reka
On Tue, May 5, 2015 at 5:43 PM, Anuruddha Liyanarachchi
anurudd...@wso2.com wrote:
Hi Devs,
I have created the $subject using python and Jinja2. Configurator is now
capable of generating axis2.xml, Carbon.xml and catalina-server.xml based
on clustering configurations. Following structure was used to create the
configurator. Currently these configurations are read from a file.
I will update the thread as I move on.
.
├── Configurator.iml
├── Constants.py
├── Constants.pyc
├── Main.py
├── Output
| ├── axis2.xml
| ├── carbon.xml
| └── catalina-server.xml
└── Templates
└── AppServer
└── conf
├── axis2.jinja
├── carbon.jinja
└── catalina-server.jinja
On Thu, Apr 30, 2015 at 12:05 PM, Anuruddha Liyanarachchi
anurudd...@wso2.com wrote:
Hi ,
I am working on $subject. I am trying create a shell script which
generate carbon server configuration based on parameters provided by
different run times.
Configurator is basically configuring perviously used puppet templates
using shell.
Please refer mail thread subject as [PPaaS] Private PaaS 4.1.0 Release
Plan for more info.
I will provide more information as I progress.
--
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel : +94 112 145 345
a thili...@wso2.comnurudd...@wso2.com
--
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel : +94 112 145 345
a thili...@wso2.comnurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
--
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel : +94 112 145 345
a thili...@wso2.comnurudd...@wso2.com
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private Pass] Configurator component (bash) for configuring a given Carbon server
Hi Anuruddha, Configurator generates carbon server configurations files? Or it just changes the parameters in default carbon server configurations files, by reading parameters from somewhere? I hope this is similar to puppet, where we keep some default carbon sever configuration template files and change parameters using tags, etc. Please confirm it. I would like to see the format of the file from which Configurator reads the configurations. Can you please paste that here? Thanks. On Tue, May 5, 2015 at 5:43 PM, Anuruddha Liyanarachchi anurudd...@wso2.com wrote: Hi Devs, I have created the $subject using python and Jinja2. Configurator is now capable of generating axis2.xml, Carbon.xml and catalina-server.xml based on clustering configurations. Following structure was used to create the configurator. Currently these configurations are read from a file. I will update the thread as I move on. . ├── Configurator.iml ├── Constants.py ├── Constants.pyc ├── Main.py ├── Output | ├── axis2.xml | ├── carbon.xml | └── catalina-server.xml └── Templates └── AppServer └── conf ├── axis2.jinja ├── carbon.jinja └── catalina-server.jinja On Thu, Apr 30, 2015 at 12:05 PM, Anuruddha Liyanarachchi anurudd...@wso2.com wrote: Hi , I am working on $subject. I am trying create a shell script which generate carbon server configuration based on parameters provided by different run times. Configurator is basically configuring perviously used puppet templates using shell. Please refer mail thread subject as [PPaaS] Private PaaS 4.1.0 Release Plan for more info. I will provide more information as I progress. -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a thili...@wso2.comnurudd...@wso2.com -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a thili...@wso2.comnurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API-M] Can we create APIs via admin services in API Manager?
Hi Devs, I was able to create APIs using publisher rest API[1]. Just wanted to check whether I can do $Subject? There is an admin service RestApiAdmin in API Manager. This service has a method to add an API. When I tested it with SoapUI, the request looks like below; *soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://org.apache.axis2/xsd http://org.apache.axis2/xsd xmlns:xsd1=http://api.rest.carbon.wso2.org/xsd http://api.rest.carbon.wso2.org/xsd soapenv:Header/ soapenv:Body xsd:addApi !--Optional:-- xsd:apiData!--Optional:-- xsd1:context?/xsd1:context!--Optional:-- xsd1:fileName?/xsd1:fileName!--Optional:-- xsd1:host?/xsd1:host!--Optional:-- xsd1:name?/xsd1:name!--Optional:-- xsd1:port?/xsd1:port!--Zero or more repetitions:--xsd1:resources !--Optional:-- xsd1:contentType?/xsd1:contentType !--Optional:-- xsd1:faultSeqXml?/xsd1:faultSeqXml !--Optional:-- xsd1:faultSequenceKey?/xsd1:faultSequenceKey !--Optional:-- xsd1:inSeqXml?/xsd1:inSeqXml !--Optional:-- xsd1:inSequenceKey?/xsd1:inSequenceKey !--Zero or more repetitions:-- xsd1:methods?/xsd1:methods !--Optional:-- xsd1:outSeqXml?/xsd1:outSeqXml !--Optional:-- xsd1:outSequenceKey?/xsd1:outSequenceKey !--Optional:-- xsd1:protocol?/xsd1:protocol !--Optional:-- xsd1:uriTemplate?/xsd1:uriTemplate !--Optional:-- xsd1:urlMapping?/xsd1:urlMapping !--Optional:-- xsd1:userAgent?/xsd1:userAgent/xsd1:resources /xsd:apiData /xsd:addApi /soapenv:Body/soapenv:Envelope* But seems some important parameters like version, visibility, tiers, end-points...etc are missing here. Please advice me whether it is possible to do $Subject. 1. https://docs.wso2.com/display/AM180/Publisher+APIs Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M] Can we create APIs via admin services in API Manager?
Got it. Thanks Nuwan for the quick response! Thanks. On Wed, Apr 8, 2015 at 9:14 AM, Nuwan Dias nuw...@wso2.com wrote: Hi Rajkumar, There aren't any admin services available for adding APIs on the API Manager. What is available are the Jaggery REST APIs that you already found out. The RestAPIAdminService is used for adding APIs in the ESB. Hence the same is used internally within API Manager for creating the Synapse artifact corresponding to the API that is added through the API Publisher. Thanks, NuwanD. On Wed, Apr 8, 2015 at 7:15 AM, Rajkumar Rajaratnam rajkum...@wso2.com wrote: Hi Devs, I was able to create APIs using publisher rest API[1]. Just wanted to check whether I can do $Subject? There is an admin service RestApiAdmin in API Manager. This service has a method to add an API. When I tested it with SoapUI, the request looks like below; *soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://org.apache.axis2/xsd http://org.apache.axis2/xsd xmlns:xsd1=http://api.rest.carbon.wso2.org/xsd http://api.rest.carbon.wso2.org/xsd soapenv:Header/ soapenv:Body xsd:addApi !--Optional:-- xsd:apiData!--Optional:-- xsd1:context?/xsd1:context!--Optional:-- xsd1:fileName?/xsd1:fileName!--Optional:-- xsd1:host?/xsd1:host!--Optional:-- xsd1:name?/xsd1:name!--Optional:-- xsd1:port?/xsd1:port!--Zero or more repetitions:--xsd1:resources !--Optional:-- xsd1:contentType?/xsd1:contentType !--Optional:-- xsd1:faultSeqXml?/xsd1:faultSeqXml !--Optional:-- xsd1:faultSequenceKey?/xsd1:faultSequenceKey !--Optional:-- xsd1:inSeqXml?/xsd1:inSeqXml !--Optional:-- xsd1:inSequenceKey?/xsd1:inSequenceKey !--Zero or more repetitions:-- xsd1:methods?/xsd1:methods !--Optional:-- xsd1:outSeqXml?/xsd1:outSeqXml !--Optional:-- xsd1:outSequenceKey?/xsd1:outSequenceKey !--Optional:-- xsd1:protocol?/xsd1:protocol !--Optional:-- xsd1:uriTemplate?/xsd1:uriTemplate !--Optional:-- xsd1:urlMapping?/xsd1:urlMapping !--Optional:-- xsd1:userAgent?/xsd1:userAgent/xsd1:resources /xsd:apiData /xsd:addApi /soapenv:Body/soapenv:Envelope* But seems some important parameters like version, visibility, tiers, end-points...etc are missing here. Please advice me whether it is possible to do $Subject. 1. https://docs.wso2.com/display/AM180/Publisher+APIs Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How can a back end service validate the JWT token received from WSO2 AM?
Hi, I have hosted my service in WSO2 AS and I am exposing them as APIs in WSO2 AM. I have configured AM to send JWT tokens to the back end service. My back end service is able to receive and decode the JWT tokens. My question is, how can a service validate that JWT token was sent from valid party (Api Manager), but not from some advisory that crafted token? Please advice. Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Chamila de Alwis
Congrats Chamila !! On Fri, Mar 6, 2015 at 9:38 AM, Inshaf Mahath ins...@wso2.com wrote: Congrats Chamila. On Fri, Mar 6, 2015 at 8:34 AM, Roshan Deniyage rosh...@wso2.com wrote: Congrats Chamila!! Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Fri, Mar 6, 2015 at 8:33 AM, Thilini Cooray thili...@wso2.com wrote: Congratulations, Chamila On Fri, Mar 6, 2015 at 8:32 AM, Rasika Perera rasi...@wso2.com wrote: Congratz Chamila !!! On Thu, Mar 5, 2015 at 10:01 AM, Imesh Gunaratne im...@wso2.com wrote: Hi Devs, It's my pleasure to welcome Chamila de Alwis as a WSO2 Committer. Chamila, welcome aboard and keep up the good work! Thanks -- *Imesh Gunaratne* Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.gunaratne.org Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- With Regards, *Rasika Perera* Software Engineer M: +94 71 680 9060 E: rasi...@wso2.com LinkedIn: http://lk.linkedin.com/in/rasika90 WSO2 Inc. www.wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Thilini Cooray Software Engineer Mobile : +94 (0) 774 570 112 %2B94%20%280%29%20773%20451194 E-mail : thili...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Inshaf Mahath Associate Software Engineer Mobile: +94775907181 WSO2 Inc. Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Gayan Gunaratne
Congratulations Gayan ! On Tue, Dec 23, 2014 at 1:24 PM, Nirmal Fernando nir...@wso2.com wrote: Congratz Gayan!! On Tue, Dec 23, 2014 at 9:24 AM, Kalpa Welivitigoda kal...@wso2.com wrote: Congratulations Gayan ! On Tue, Dec 23, 2014 at 9:16 AM, Lakmal Warusawithana lak...@wso2.com wrote: Hi, It is with great pleasure that I welcome Gayan as a WSO2 committer, Congratulations and keep up with the good work! .. -- Lakmal Warusawithana Vice President, Apache Stratos Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Kalpa Welivitigoda Software Engineer, WSO2 Inc. http://wso2.com Email: kal...@wso2.com Mobile: +94776509215 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Firzhan Naqash
Congrats Firzhan !!! On Tue, Dec 23, 2014 at 1:14 PM, Waruna Jayaweera waru...@wso2.com wrote: Congratulations Firzhan :D On Tue, Dec 23, 2014 at 12:35 PM, Milinda Perera milin...@wso2.com wrote: Congratulations firzhan :) On Tue, Dec 23, 2014 at 12:14 PM, Abimaran Kugathasan abima...@wso2.com wrote: Congrats! On Tue, Dec 23, 2014 at 12:09 PM, Manula Chathurika Thantriwatte manu...@wso2.com wrote: Congratulations Firzhan. On Tue, Dec 23, 2014 at 12:08 PM, Srisunmugaraja Paraparan parapa...@wso2.com wrote: Congratz Firzan !!! On Tue, Dec 23, 2014 at 12:06 PM, Darshana Gunawardana darsh...@wso2.com wrote: Congratulations Firzhan !!!.. Keep up the good work.. On Tue, Dec 23, 2014 at 11:59 AM, Senduran Balasubramaniyam sendu...@wso2.com wrote: Congratulations Firzhan !! On Tue, Dec 23, 2014 at 11:54 AM, Anuruddha Premalal anurud...@wso2.com wrote: Congratulations Firzhan!! On Tue, Dec 23, 2014 at 11:51 AM, Aruna Karunarathna ar...@wso2.com wrote: Congratzz Firzhan...!!! On Tue, Dec 23, 2014 at 11:48 AM, Kasun De Silva kas...@wso2.com wrote: Congratz Firzan !!! *Kasun de Silva* Software Engineer | *WSO2 Inc.*; http://wso2.com lean.enterprise.middleware email : kas...@wso2.com mobile : +94 77 794 4260 On Tue, Dec 23, 2014 at 11:46 AM, Nandika Jayawardana nand...@wso2.com wrote: Hi All, It is my pleasure to welcome Firzhan as a WSO2 committer. Firzhan is a key member of Business Process Server Team and has contributed to Both BPS and IS. Welcome aboard and week up the good work ! Regards Nandika -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: ar...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Senduran * Software Engineer, WSO2, Inc.; http://wso2.com/ http://wso2.com/ Mobile: +94 77 952 6548 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, *Darshana Gunawardana*Software Engineer WSO2 Inc.; http://wso2.com *E-mail: darsh...@wso2.com darsh...@wso2.com* *Mobile: +94718566859 %2B94718566859*Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Regards -- Srisunmugaraja Paraparan Software Engineer, WSO2 Inc. - lean . enterprise . middleware | wso2.com email : parapa...@wso2.com, mobile : +94 77 0362151 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Manula Chathurika Thantriwatte Software Engineer WSO2 Inc. : http://wso2.com lean . enterprise . middleware email : manu...@wso2.com / man...@apache.org phone : +94 772492511 blog : http://manulachathurika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 773922820 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Milinda Perera Software Engineer; WSO2 Inc. http://wso2.com , Mobile: (+94) 714 115 032 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Waruna Lakshitha Jayaweera Software Engineer WSO2 Inc; http://wso2.com phone: +94713255198 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Roshan Deniyage
Congratulation Roshan!! On Fri, Dec 19, 2014 at 8:07 AM, Ravindra Ranwala ravin...@wso2.com wrote: Congrats Roshan ! On Fri, Dec 19, 2014 at 8:02 AM, Shiroshica Kulatilake sh...@wso2.com wrote: Congrats !!! On Fri, Dec 19, 2014 at 8:01 AM, Anuruddha Premalal anurud...@wso2.com wrote: Congratulation Roshan!! On Fri, Dec 19, 2014 at 6:44 AM, Kasun De Silva kas...@wso2.com wrote: Congratz Roshan!!! *Kasun de Silva* Software Engineer | *WSO2 Inc.*; http://wso2.com lean.enterprise.middleware email : kas...@wso2.com mobile : +94 77 794 4260 On Fri, Dec 19, 2014 at 1:29 AM, Thanuja Jayasinghe than...@wso2.com wrote: Congratz Roshan!!! On Thu, Dec 18, 2014 at 12:59 PM, Prabath Ariyarathna prabat...@wso2.com wrote: Congratulations Roshan On Thu, Dec 18, 2014 at 11:23 PM, Harsha Kumara hars...@wso2.com wrote: Congratulations Roshan! On Thu, Dec 18, 2014 at 10:24 PM, Vijitha Ekanayake vijit...@wso2.com wrote: Congratulations Roshan On Thu, Dec 18, 2014 at 10:10 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi all, WSO2 welcomes Roshan Deniyage as WSO2 committer! Congratulations! thanks, dimuthu -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Vijitha Ekanayake Software Engineer*, *WSO2, Inc.; http://wso2.com/ Mobile : +94 777 24 73 39 | +94 718 74 44 08 lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Prabath Ariyarathna* *Associate Technical Lead* *WSO2, Inc. * *lean . enterprise . middleware * *Email: prabat...@wso2.com prabat...@wso2.com* *Blog: http://prabu-lk.blogspot.com http://prabu-lk.blogspot.com* *Flicker : https://www.flickr.com/photos/47759189@N08 https://www.flickr.com/photos/47759189@N08* *Mobile: +94 77 699 4730 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Thanuja Lakmal* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94715979891 +94758009992 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ravindra Ranwala Software Engineer WSO2, Inc: http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg Mobile: +94714198770 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Bug in WSO2-Governance Registry admin console
Hi, Did you run the DSS before? Clear your browser cache and try again. Thanks. On Sun, Dec 7, 2014 at 11:40 PM, Farasath Ahamed farasa...@wso2.com wrote: I started up the governancy registry from the terminal and opened the admin console from the browser. The admin console has the appearance of that of the Data Services Server(including its logo), however the admin console is that of the Governance Registry. I have attached the screenshots. Can someone look into this, please? -- *Farasath Ahamed* Software Engineering Intern WSO2 Inc.; http://wso2.com Mobile: +94 777 603 866 E-Mail: farasath http://goog_1999535192a...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Per service logging with ESB
Update:
Changing the logger level to TRACE via UI is not getting effect
immediately. But DEBUG, INFO level changes are getting effects immediately.
But, If we restart the ESB after changing logger level to TRACE via UI, I
am getting TRACE level logs as well.
Seems it is a bug.
Thanks.
On Fri, Nov 28, 2014 at 11:15 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Hi,
I want to use per service logging in ESB.
I created a proxy with a simple log mediator. And I configured my log4j
properties as below.
log4j.category.SERVICE_LOGGER.MyProxy=INFO, PROXY_APPENDER
log4j.additivity.PROXY_APPENDER=false
log4j.additivity.PROXY_APPENDER.threshold=TRACE
log4j.appender.PROXY_APPENDER=org.apache.log4j.DailyRollingFileAppender
log4j.appender.PROXY_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/myproxy${instance.log}.log
log4j.appender.PROXY_APPENDER.Append=true
log4j.appender.PROXY_APPENDER.layout=org.apache.log4j.PatternLayout
log4j.appender.PROXY_APPENDER.layout.ConversionPattern=%d{ISO8601}
[%X{ip}-%X{host}] [%t] %5p %c{1} %m%n
Now I am getting the log mediator's results in myproxy.log
However, when I changed the log level to TRACE, I am not getting any trace
logs in myproxy.log.
log4j.category.SERVICE_LOGGER.MyProxy=TRACE, PROXY_APPENDER
What would be issue here?
Appreciate your help on this.
Thanks.
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ESB] Per service logging with ESB
Hi,
I want to use per service logging in ESB.
I created a proxy with a simple log mediator. And I configured my log4j
properties as below.
log4j.category.SERVICE_LOGGER.MyProxy=INFO, PROXY_APPENDER
log4j.additivity.PROXY_APPENDER=false
log4j.additivity.PROXY_APPENDER.threshold=TRACE
log4j.appender.PROXY_APPENDER=org.apache.log4j.DailyRollingFileAppender
log4j.appender.PROXY_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/myproxy${instance.log}.log
log4j.appender.PROXY_APPENDER.Append=true
log4j.appender.PROXY_APPENDER.layout=org.apache.log4j.PatternLayout
log4j.appender.PROXY_APPENDER.layout.ConversionPattern=%d{ISO8601}
[%X{ip}-%X{host}] [%t] %5p %c{1} %m%n
Now I am getting the log mediator's results in myproxy.log
However, when I changed the log level to TRACE, I am not getting any trace
logs in myproxy.log.
log4j.category.SERVICE_LOGGER.MyProxy=TRACE, PROXY_APPENDER
What would be issue here?
Appreciate your help on this.
Thanks.
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I get the TRACE logging to work?
Hi Dulanja,
Were you able to solve this issue?
I am trying to use per service logging in ESB. I enabled trace log for my
proxy service. I am not getting any trace logs in my log file. It is
discussed in [1].
Appreciate if you could share how you solved this issue.
1. [Dev][ESB] Per service logging with ESB
Thanks.
On Wed, Apr 30, 2014 at 1:17 AM, Dulanja Liyanage dula...@wso2.com wrote:
Hi All,
$subject.
Following are the defaults inside log4j.properties file
log4j.logger.trace.messages=TRACE,CARBON_TRACE_LOGFILE
# Appender config to CARBON_TRACE_LOGFILE
log4j.appender.CARBON_TRACE_LOGFILE=org.apache.log4j.DailyRollingFileAppender
log4j.appender.CARBON_TRACE_LOGFILE.File=${carbon.home}/repository/logs/${instance.log}/wso2carbon-trace-messages${instance.log}.log
log4j.appender.CARBON_TRACE_LOGFILE.Append=true
log4j.appender.CARBON_TRACE_LOGFILE.layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout
log4j.appender.CARBON_TRACE_LOGFILE.layout.ConversionPattern=[%d] %P%5p
{%c} - %x %m {%c}%n
log4j.appender.CARBON_TRACE_LOGFILE.layout.TenantPattern=%U%@%D [%T] [%S]
log4j.appender.CARBON_TRACE_LOGFILE.threshold=TRACE
log4j.additivity.trace.messages=false
I have enabled TRACE for the component as following:
log4j.logger.org.wso2.carbon.identity.application=TRACE
From code I'm calling like following:
if (log.isTraceEnabled()) {
log.trace(Inside handle());
}
I checked wso2carbon-trace-messages.log, it's empty. However, the DEBUG
logs of log4j.logger.org.wso2.carbon.identity.application are printed in
wso2carbon.log as expected.
Am I missing something here? Or is TRACE broken?
Thanks,
Dulanja
--
Dulanja Liyanage
WSO2 Inc.
M: +94776764717
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Rajkumar Rajaratnam
Committer PMC Member, Apache Stratos
Software Engineer, WSO2
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Asitha Nanayakkara
___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Buddhima Wijeweera Software Engineer; WSO2 Inc.; http://wso2.com , Mobile: +94 71 427 9966 Email: buddh...@wso2.com Blog: https://buddhimawijeweera.wordpress.com GitHub Profile: https://github.com/Buddhima ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lahiru Chandima *Senior Software Engineer* Mobile : +94 (0) 772 253283 lahi...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sajini De Silva
Congratulations !! :) On Tue, Nov 18, 2014 at 5:06 PM, Supun Sethunga sup...@wso2.com wrote: Congratz Sajini! On Tue, Nov 18, 2014 at 5:04 PM, Tharik Kanaka tha...@wso2.com wrote: Congratulations Sajini... On Tue, Nov 18, 2014 at 1:26 PM, Ramith Jayasinghe ram...@wso2.com wrote: Hi Sajini, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! thanks and best regards Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Tharik Kanaka* | Associate Software Engineer WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka Email: tha...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Supun Sethunga* Software Engineer WSO2, Inc. lean | enterprise | middleware Mobile : +94 716546324 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Milinda Perera
Congratz, Milinda! On Tue, Oct 28, 2014 at 2:57 PM, Dilan Udara Ariyaratne dil...@wso2.com wrote: Congratulations, Milinda! *Dilan U. Ariyaratne* Software Engineer WSO2 Inc. http://wso2.com/ Mobile: +94775149066 lean . enterprise . middleware On Tue, Oct 28, 2014 at 2:53 PM, Nandika Jayawardana nand...@wso2.com wrote: Hi all, It's my pleasure to announce Milinda Perera as a WSO2 Committer. Milinda has been a valuable contributor to WSO2 BPS product and in recognition of his contribution he has been voted as a WSO2 Committer. Milinda, welcome aboard and keep up the good work!. Regards Nandika -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajkumar Rajaratnam Software Engineer | WSO2, Inc. Mobile +94777568639 | +94783498120 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
