Re: [Dev] Issue when running mysql db script - APIM analytics HA setup
Created a JIRA to track this task. https://wso2.org/jira/browse/DOCUMENTATION-6396 Regards, Mariangela *Mariangela Hills* Associate Lead Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 <https://wso2.com/signature> On Tue, Nov 7, 2017 at 4:22 PM, Sanjeewa Malalgoda <sanje...@wso2.com> wrote: > MySQL script on default product pack do not work as expected with mysql > 5.7.19 . Please find updated one here. > > Thanks > sanjeewa. > > On Tue, Nov 7, 2017 at 3:39 PM, Mariangela Hills <mariang...@wso2.com> > wrote: > >> - Removing dev@wso2.org >> >> Ack for docs! >> >> Regards, >> Mariangela >> >> >> *Mariangela Hills* >> Associate Lead Technical Writer - WSO2, Inc. http://wso2.com >> Committer and PMC member - Apache Stratos >> email:mariang...@wso2.com | mobile: +94 773 500185 >> <https://wso2.com/signature> >> >> On Tue, Nov 7, 2017 at 3:37 PM, Damith Wickramasinghe <dami...@wso2.com> >> wrote: >> >>> As Harsha mentioned it should be some where common to all places. >>> >>> Regards, >>> Damith >>> >>> On Tue, Nov 7, 2017 at 3:35 PM, Harsha Kumara <hars...@wso2.com> wrote: >>> >>>> >>>> >>>> On Tue, Nov 7, 2017 at 3:18 PM, Chamalee De Silva <chama...@wso2.com> >>>> wrote: >>>> >>>>> Hi Damith, >>>>> >>>>> mysql5.7.sql script has been added for MySQL 5.7 and later versions of >>>>> databases. >>>>> This is clearly described in the documentation on setting up MySQL >>>>> documentation in [1]. >>>>> >>>>> If we are going to add this special note, we may have to add this >>>>> everywhere where mysql is used. >>>>> >>>>> @team, What is the best option ? >>>>> >>>> Best option would be to point to setting up database link as it >>>> contains required information. >>>> >>>>> >>>>> >>>>> [1] https://docs.wso2.com/display/AM200/Setting+up+MySQL >>>>> >>>>> >>>>> On Tue, Nov 7, 2017 at 2:20 PM, Damith Wickramasinghe < >>>>> dami...@wso2.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I'm using mysql version 5.7.20. In order to populate userdb and regdb >>>>>> i need to run mysql scripts and i have used the scripts in APIM analytics >>>>>> pack(mysql.sql). When run below issue arises, >>>>>> >>>>>> ERROR 1067 (42000): Invalid default value for 'REG_CREATED_TIME' >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> ERROR 1067 (42000): Invalid default value for 'REG_LAST_UPDATED_TIME' >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist >>>>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>>>> >>>>>> Searching the issue found out i need to run NOT mysql.sql but >>>>>> mysql5.7.sql. So for wt version does the mysql.sql works ? versions other >>>>>> than 5.7 ? IF so we need to mention this clearly in the >>>>>> docs . I found the same issue has been occurred for a customer as >>>>>> well. I followed [1]. >>>>>> >>>>>> [1] - https://docs.wso2.com/display/AM210/Minimum+High+Availabilit >>>>>> y+Deployment+for+WSO2+APIM+Analytics >>>>>> >>>>>> Regards, >>>>>> Damith. >>>>>> >>>>>> -- >>>>>> Senior Software Engineer >>>>>> WSO2 Inc.; http://wso2.com >>>>>&
Re: [Dev] Issue when running mysql db script - APIM analytics HA setup
- Removing dev@wso2.org Ack for docs! Regards, Mariangela *Mariangela Hills* Associate Lead Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 <https://wso2.com/signature> On Tue, Nov 7, 2017 at 3:37 PM, Damith Wickramasinghe <dami...@wso2.com> wrote: > As Harsha mentioned it should be some where common to all places. > > Regards, > Damith > > On Tue, Nov 7, 2017 at 3:35 PM, Harsha Kumara <hars...@wso2.com> wrote: > >> >> >> On Tue, Nov 7, 2017 at 3:18 PM, Chamalee De Silva <chama...@wso2.com> >> wrote: >> >>> Hi Damith, >>> >>> mysql5.7.sql script has been added for MySQL 5.7 and later versions of >>> databases. >>> This is clearly described in the documentation on setting up MySQL >>> documentation in [1]. >>> >>> If we are going to add this special note, we may have to add this >>> everywhere where mysql is used. >>> >>> @team, What is the best option ? >>> >> Best option would be to point to setting up database link as it contains >> required information. >> >>> >>> >>> [1] https://docs.wso2.com/display/AM200/Setting+up+MySQL >>> >>> >>> On Tue, Nov 7, 2017 at 2:20 PM, Damith Wickramasinghe <dami...@wso2.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> I'm using mysql version 5.7.20. In order to populate userdb and regdb i >>>> need to run mysql scripts and i have used the scripts in APIM analytics >>>> pack(mysql.sql). When run below issue arises, >>>> >>>> ERROR 1067 (42000): Invalid default value for 'REG_CREATED_TIME' >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> ERROR 1067 (42000): Invalid default value for 'REG_LAST_UPDATED_TIME' >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist >>>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist >>>> >>>> Searching the issue found out i need to run NOT mysql.sql but >>>> mysql5.7.sql. So for wt version does the mysql.sql works ? versions other >>>> than 5.7 ? IF so we need to mention this clearly in the >>>> docs . I found the same issue has been occurred for a customer as >>>> well. I followed [1]. >>>> >>>> [1] - https://docs.wso2.com/display/AM210/Minimum+High+Availabilit >>>> y+Deployment+for+WSO2+APIM+Analytics >>>> >>>> Regards, >>>> Damith. >>>> >>>> -- >>>> Senior Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >>>> lean.enterprise.middleware >>>> >>>> mobile: *+94728671315 <+94%2072%20867%201315>* >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "WSO2 Documentation Group" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to documentation+unsubscr...@wso2.com. >>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Thanks & Regards, >>> >>> *Chamalee De Silva* >>> Software Engineer >>> *WS**O2* Inc. :http://wso2.com/ >>> >>> Office :- *+94 11 2145345 <%2B94%2011%202145345>* >>> mobile :- *+94 7 <%2B94%2077%202782039>1 4315942* >>> >>> >> >> >> -- >> Harsha Kumara >> Software Engineer, WSO2 Inc. >> Mobile: +94775505618 <+94%2077%20550%205618> >> Blog:harshcreationz.blogspot.com >> > > > > -- > Senior Software Engineer > WSO2 Inc.; http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > lean.enterprise.middleware > > mobile: *+94728671315 <+94%2072%20867%201315>* > > -- > You received this message because you are subscribed to the Google Groups > "WSO2 Documentation Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to documentation+unsubscr...@wso2.com. > For more options, visit https://groups.google.com/a/wso2.com/d/optout. > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Read only source view not allowed to edit single API
Thanks for reporting! I updated [1] and [2] as follows: - Removed the instructions that explain how to update the API source code via the source view UI in order to engage a custom API to a specific set of APIs. - Mentioned that the velocity_template should be used to engage a custom handler to a specific set of APIs - Added the following note. "It is not recommended to update the API source code via the source view UI or file system when engaging a custom handler to selected APIs, because the customizations get overridden by the publisher updates. " [1] https://docs.wso2.com/display/AM200/Writing+Custom+Handlers [2] https://docs.wso2.com/display/AM210/Writing+Custom+Handlers Regards, Mariangela *Mariangela Hills* Associate Lead Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 <https://wso2.com/signature> On Tue, Apr 18, 2017 at 12:59 PM, Mariangela Hills <mariang...@wso2.com> wrote: > Ack for docs! > > Regards, > Mariangela > > > *Mariangela Hills* > Associate Lead Technical Writer - WSO2, Inc. http://wso2.com > Committer and PMC member - Apache Stratos > email:mariang...@wso2.com | mobile: +94 773 500185 > <https://wso2.com/signature> > > On Tue, Apr 18, 2017 at 11:22 AM, Lakmali Baminiwatta <lakm...@wso2.com> > wrote: > >> Hi Lakshman, >> >> It is not recommended to update the API source code via source view UI or >> file system since it will get overridden by publisher updates. We have to >> update the docs by removing that part. >> The recommended way is to add it via the velocity template. If there is a >> requirement to add it only to a specific API, what we can do is write some >> logic in the velocity template. >> >> Thanks, >> Lakmali >> >> On 16 April 2017 at 21:51, Shazni Nazeer <sha...@wso2.com> wrote: >> >>> May be this is bug. >>> >>> In addition despite you add the handler via source view or through file >>> system in API level, and then if you happen to update the API in publisher, >>> all custom handler (or any property) that you add get vanished as the API >>> gets updated, the new synapse file overwrite it. So you'll have to add it >>> once again. So wouldn't it be good if the handler is added to >>> velocity-tempate.xml file if the handler is applicable to all the API? But >>> if it's not the case, I'm npt sure how to handle it. is there a way to >>> handle it it easily without always have to re-edit the API synapse file? >>> >>> On Sat, Apr 15, 2017 at 8:17 PM, Lakshman Udayakantha < >>> lakshm...@wso2.com> wrote: >>> >>>> Hi Folks, >>>> >>>> I was trying to add a custom handler to a single API in API Manager. >>>> According to [1], we can edit the source view of API and add customer >>>> handler in handler section. Anyway, I can't do that in APIM 2.0.0 because >>>> source view is read-only. This can be done in earlier versions like 1.10.0. >>>> Any way we can edit API file from the file system and engage the handler. >>>> What is the reason for making ESB source view read only? If it should be >>>> read only then we have to update the documentation and point a way to add >>>> handlers for single API as well. >>>> >>>> [1] https://docs.wso2.com/display/AM200/Writing+Custom+Handlers >>>> >>>> -- >>>> Lakshman Udayakantha >>>> WSO2 Inc. www.wso2.com >>>> lean.enterprise.middleware >>>> Mobile: *0717429601* >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Shazni Nazeer >>> >>> Mob : +94 37331 >>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>> Blog : http://shazninazeer.blogspot.com >>> >>> <http://wso2.com/signature> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Lakmali Baminiwatta >> Associate Technical Lead >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> mobile: +94 71 2335936 >> blog : lakmali.com >> >> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Read only source view not allowed to edit single API
Ack for docs! Regards, Mariangela *Mariangela Hills* Associate Lead Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 <https://wso2.com/signature> On Tue, Apr 18, 2017 at 11:22 AM, Lakmali Baminiwatta <lakm...@wso2.com> wrote: > Hi Lakshman, > > It is not recommended to update the API source code via source view UI or > file system since it will get overridden by publisher updates. We have to > update the docs by removing that part. > The recommended way is to add it via the velocity template. If there is a > requirement to add it only to a specific API, what we can do is write some > logic in the velocity template. > > Thanks, > Lakmali > > On 16 April 2017 at 21:51, Shazni Nazeer <sha...@wso2.com> wrote: > >> May be this is bug. >> >> In addition despite you add the handler via source view or through file >> system in API level, and then if you happen to update the API in publisher, >> all custom handler (or any property) that you add get vanished as the API >> gets updated, the new synapse file overwrite it. So you'll have to add it >> once again. So wouldn't it be good if the handler is added to >> velocity-tempate.xml file if the handler is applicable to all the API? But >> if it's not the case, I'm npt sure how to handle it. is there a way to >> handle it it easily without always have to re-edit the API synapse file? >> >> On Sat, Apr 15, 2017 at 8:17 PM, Lakshman Udayakantha <lakshm...@wso2.com >> > wrote: >> >>> Hi Folks, >>> >>> I was trying to add a custom handler to a single API in API Manager. >>> According to [1], we can edit the source view of API and add customer >>> handler in handler section. Anyway, I can't do that in APIM 2.0.0 because >>> source view is read-only. This can be done in earlier versions like 1.10.0. >>> Any way we can edit API file from the file system and engage the handler. >>> What is the reason for making ESB source view read only? If it should be >>> read only then we have to update the documentation and point a way to add >>> handlers for single API as well. >>> >>> [1] https://docs.wso2.com/display/AM200/Writing+Custom+Handlers >>> >>> -- >>> Lakshman Udayakantha >>> WSO2 Inc. www.wso2.com >>> lean.enterprise.middleware >>> Mobile: *0717429601* >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Shazni Nazeer >> >> Mob : +94 37331 >> LinkedIn : http://lk.linkedin.com/in/shazninazeer >> Blog : http://shazninazeer.blogspot.com >> >> <http://wso2.com/signature> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Lakmali Baminiwatta > Associate Technical Lead > WSO2, Inc.: http://wso2.com > lean.enterprise.middleware > mobile: +94 71 2335936 > blog : lakmali.com > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Pubudu Gunatilaka
Congrats, Pubudu! Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Wed, Dec 2, 2015 at 12:22 PM, Lahiru Sandaruwan <lahi...@wso2.com> wrote: > Congratz Pubudu! > > On Mon, Nov 30, 2015 at 10:47 PM, Imesh Gunaratne <im...@wso2.com> wrote: > >> Hi Devs, >> >> It's my pleasure to announce Pubudu as a WSO2 committer. Pubudu has made >> great contributions to Apache Stratos & WSO2 Private PaaS. As a recognition >> of his work he has been voted as a WSO2 committer. >> >> Pubudu, welcome aboard! Keep up the good work! >> >> Thanks >> -- >> *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 >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > -- > Lahiru Sandaruwan > Committer and PMC member, Apache Stratos, > Senior Software Engineer, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > phone: +94773325954 > email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 > > > ___ > 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
Re: [Dev] Unable to download wso2 agent for android device
Hi Kasun, I updated the note in step 2 in the "WSO2 EMM Agent configurations to enroll and manage devices" section in [1] based on your feedback. [1] https://docs.wso2.com/display/EMM200/General+Server+Configurations#GeneralServerConfigurations-WSO2EMMAgentconfigurationstoenrollandmanagedevices Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Mon, Dec 14, 2015 at 10:22 AM, Sashika Wijesinghe <sash...@wso2.com> wrote: > Hi Kasun, > > When I changed the host entry to HTTP, download link redirects to 'No data > received' error page. Is there any other configuration change required to > get the enrollment successful? > > Thanks & Regards, > > On Sun, Dec 13, 2015 at 1:12 PM, Kasun Dananjaya Delgolla <kas...@wso2.com > > wrote: > >> Hi Shashika, >> >> This is because you have given https your for generalConfig->host entry >> in config.json in emm-web-agent. It should be HTTP. Android doesn't allow >> HTTPS unless server has a trusted CA installed. Please change the config to >> HTTP and re-check. >> >> @Shavindri - This needs to be changed in the documentation as well. (Also >> mention in prod mode, change this to HTTPS) >> >> Thanks >> >> On Sat, Dec 12, 2015 at 5:12 PM, Sashika Wijesinghe <sash...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I was unable to download wso2 agent for android device due to agent >>> download failure. In the download link it appears as 'unknown' (image >>> attached). >>> >>> Before starting the server I have configured below files with domain ip >>> address. (Configuration files attached ) >>> May I know whether I missed any mandatory configurations? >>> >>>- cdm-config.xml >>>- carbon.xml >>>- config.json file at >>>'/repository/deployment/server/jaggeryapps/emm/config' location >>>- config.json file at >>> >>> '/repository/deployment/server/jaggeryapps/emm-web-agent/config' >>>location >>> >>> Any help is highly appreciated. >>> >>> Thanks & Regards, >>> -- >>> >>> *Sashika WijesingheSoftware Engineer - QA Team* >>> Mobile : +94 (0) 774537487 >>> sash...@wso2.com >>> >> >> >> >> -- >> Kasun Dananjaya Delgolla >> >> Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> Tel: +94 11 214 5345 >> Fax: +94 11 2145300 >> Mob: + 94 771 771 015 >> Blog: http://kddcodingparadise.blogspot.com >> Linkedin: *http://lk.linkedin.com/in/kasundananjaya >> <http://lk.linkedin.com/in/kasundananjaya>* >> > > > > -- > > *Sashika WijesingheSoftware Engineer - QA Team* > Mobile : +94 (0) 774537487 > sash...@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
[Dev] [PPaaS] Issues identified related to cartridge payload parameters and template modules
I identified the following issues when documenting the cartridge payload parameters. - The PPaaS Template Modules need to be generalized due to the following reasons: See JIRA PAAS-310 [1] <https://wso2.org/jira/browse/PAAS-310> for more information. - The concept used for the placeholder for the CONFIG_PARAM_REG_DB_URL, CONFIG_PARAM_CONFIG_DB_URL and CONFIG_PARAM_USER_MGT_DB_URL payload parameters vary in different cartridges. - The payload parameter names differ between cartridges. - The REGISTRY_DB_DRIVER, CONFIG_DB_DRIVER and USER_MGT_DB_DRIVER values are hard coded in some of the cartridge template modules (e.g., ESB and BRS); while, this is not the case in the rest of the cartridges. Ideally, the values for these parameters should not be hard coded. - Some cartridge JSONs that correspond to specific IaaS are missing some payload parameters. See JIRA PAAS-311 [2] <https://wso2.org/jira/browse/PAAS-311> for more information. - There are typos in some BPS cartridge payload parameters. See JIRA PAAS-312 [3] <https://wso2.org/jira/browse/PAAS-312> for more information. [1] https://wso2.org/jira/browse/PAAS-310 [2] https://wso2.org/jira/browse/PAAS-311 [3] https://wso2.org/jira/browse/PAAS-312 Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [PPaaS] Issues identified related to cartridge payload parameters and template modules
Pubudu, thanks for your quick response! I was not aware that there was a separate JIRA project for PPaaS cartridges. I will keep this in mind in the future. Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Mon, Nov 16, 2015 at 6:39 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Mari, > > Thank you for bringing this up. It would be more useful to have a generic > template module and have the same config parameter names. In the future we > will try to come up with a generic template module for this. > > We do have a separate jira project for Private Paas Cartridges. I have > moved reported jiras to Private Paas Cartridges jira project as [1]. [2] > and [3]. Number [3] is not a typo issue. Activiti is an engine used in > BPMN in BPS. > > [1] - https://wso2.org/jira/browse/PPC-86 > [2] - https://wso2.org/jira/browse/PPC-87 > [3] - https://wso2.org/jira/browse/PPC-88 > > Thank you! > > On Mon, Nov 16, 2015 at 5:48 PM, Mariangela Hills <mariang...@wso2.com> > wrote: > >> I identified the following issues when documenting the cartridge payload >> parameters. >> >>- The PPaaS Template Modules need to be generalized due to the >>following reasons: >>See JIRA PAAS-310 [1] <https://wso2.org/jira/browse/PAAS-310> for >>more information. >> >> >>- The concept used for the placeholder for the CONFIG_PARAM_REG_DB_URL, >> CONFIG_PARAM_CONFIG_DB_URL and CONFIG_PARAM_USER_MGT_DB_URL >> payload parameters vary in different cartridges. >> >> - The payload parameter names differ between cartridges. >> >> >>- The REGISTRY_DB_DRIVER, CONFIG_DB_DRIVER and USER_MGT_DB_DRIVER values >> are hard coded in some of the cartridge template modules (e.g., ESB and >> BRS); while, this is not the case in the rest of the cartridges. >> Ideally, >> the values for these parameters should not be hard coded. >> >> - Some cartridge JSONs that correspond to specific IaaS are >>missing some payload parameters. >>See JIRA PAAS-311 [2] <https://wso2.org/jira/browse/PAAS-311> for >>more information. >> >>- There are typos in some BPS cartridge payload parameters. >>See JIRA PAAS-312 [3] <https://wso2.org/jira/browse/PAAS-312> for >>more information. >> >> >> [1] https://wso2.org/jira/browse/PAAS-310 >> [2] https://wso2.org/jira/browse/PAAS-311 >> [3] https://wso2.org/jira/browse/PAAS-312 >> >> >> >> Regards, >> Mariangela >> >> >> *Mariangela Hills* >> Senior Technical Writer - WSO2, Inc. http://wso2.com >> Committer and PMC member - Apache Stratos >> email:mariang...@wso2.com | mobile: +94 773 500185 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "WSO2 Documentation Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to documentation+unsubscr...@wso2.com. >> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >> > > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774079049 <%2B94772207163> > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Private PaaS 4.1.0 EC2 Demo AMI
Hi Imesh, +1 I have created a JIRA [1] to track this task. [1] https://wso2.org/jira/browse/DOCUMENTATION-2672 Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Thu, Nov 5, 2015 at 1:07 AM, Imesh Gunaratne <im...@wso2.com> wrote: > Great work Akila!! > Indeed this is the most convenient method for users to try out WSO2 > Private PaaS 4.1.0 on AWS. > > A quick question, have we published the AMIs publicly in different > regions? If so we can have a page in the Wiki mentioning them. > > @Mari: Shall we add this guideline to the documentation? > > Thanks > > On Wed, Nov 4, 2015 at 6:47 AM, Akila Ravihansa Perera <raviha...@wso2.com > > wrote: > >> Hi, >> >> I've created an EC2 AMI preconfigured with WSO2 Private PaaS 4.1.0 and >> WSO2 cartridges. The demo AMI contains init scripts to configure PPaaS, >> ActiveMQ and Nginx load-balancer extension. You need to pass PPaaS specific >> parameters as user data when launching this demo AMI and the init script >> will configure the products, deploy artifacts and cartridges. >> It will also configure WSO2 DAS with PPaaS gadgets which is used to >> provide monitoring and metering related information. >> >> This will be a very convenient method for users to get started with >> Private PaaS since it reduces most of the configuration related tasks. I've >> written a blog post [1] explaining how to setup WSO2 Private PaaS 4.1.0 >> with this demo AMI. >> >> [1] >> http://blog.ravihansa3000.com/2015/11/deploying-wso2-private-paas-410-using.html >> >> Thanks. >> >> -- >> Akila Ravihansa Perera >> WSO2 Inc.; http://wso2.com/ >> >> Blog: http://ravihansa3000.blogspot.com >> > > > > -- > *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 > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need help in customizing a script
Hi Dakshika,
Awesome, it works now! Thanks loads for taking the time to come up with a
solution!
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <daksh...@wso2.com>
wrote:
> Hi,
>
> I fixed your issue. please check
>
>
> jQuery(document).ready(function() {
> jQuery(".wiki-content a").each(function (){
> if(jQuery(this).context.hash == ''){
> jQuery(this).attr("target", "_blank");
> }
> });
> });
>
>
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills <mariang...@wso2.com>
> wrote:
>
>> Hi Imesh, Dakshika and Nisrin,
>>
>> Thanks for all your feedback and help!
>>
>> *@Dakshika* - I tried the script but it did not work, because when I
>> used it all the links were opening in the same page.
>>
>> *@Imesh -* Thanks for the info!
>>
>> *@Nisrin* - When a user is new to docs, they will tend to always click
>> on a link as opposed to right-clicking on a link. Furthermore, I was going
>> on the assumption that they will close a link after they are done with a
>> certain set of steps (but I guess it will not always be the case).
>>
>> As a workaround, I added an "expand macro" and pulled the child content
>> into the expand macro using the "Include Page" macro, so that the user will
>> not have to see a ton of instructions all at once.
>>
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff <nis...@wso2.com> wrote:
>>
>>> Hi Mari,
>>>
>>> Wouldn't this result in too many tabs opening up as there will be a new
>>> tab opening whenever a users clicks on a link.
>>>
>>> With how it is now, if a user wants to view the linked section in a new
>>> tab, they can always right click and then click *Open Link in New Tab*/*Open
>>> Link in New Window* right.
>>>
>>> So do you think we really need this?
>>>
>>> Thank you.
>>>
>>> Best Regards,
>>> Nisrin
>>>
>>> Nisrin Sheriff
>>> Senior Technical Writer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>> mobile: +94 776 24 84 56
>>> http://wso2.com
>>>
>>> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <daksh...@wso2.com
>>> > wrote:
>>>
>>>> Hi Mari,
>>>>
>>>> I have notice that you are using target="_blank" for internal page
>>>> links as wel. remove that attribute from links to navigate within page.
>>>>
>>>> >>> href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
>>>> *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
>>>> (CEP)
>>>>
>>>> *Dakshika Jayathilaka*
>>>> PMC Member & Committer of Apache Stratos
>>>> Senior Software Engineer
>>>> WSO2, Inc.
>>>> lean.enterprise.middleware
>>>> 0771100911
>>>>
>>>> On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka <
>>>> daksh...@wso2.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> IMO open a webpage in new tab or page is recommended depending on your
>>>>> use case. AFAIK giving a pop up link will block by browser due to security
>>>>> reason.
>>>>>
>>>>> So what you can do is, append simple class to "a"(anchor) to prevent
>>>>> all links opening in new page.
>>>>> Use below code snippet for Pages that you want to open in new page or
>>>>> tab.
>>>>>
>>>>> for HTML link:
>>>>>
>>>>> this is an external link
>>>>>
>>>>>
>>>>> for other links
>>>>>
>>>>> default
>>>>>
>>>>> Script:
>>>>>
>>
Re: [Dev] Need help in customizing a script
Hi Imesh,
The following is the actual page that I was planning on adding this script
to. However, now, instead of navigating the user off to separate pages I
have pulled the content from those pages into the main page, so that the
respective sub content will appear within the main page when the user
clicks on the respective expand link for instructions.
https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne <im...@wso2.com> wrote:
> Mari, can you please share a link to this page to have a look.
>
> Thanks
>
> On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake <shavin...@wso2.com
> > wrote:
>
>> Thank you Dakshika, this is great!
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills <mariang...@wso2.com>
>> wrote:
>>
>>> Hi Dakshika,
>>>
>>> Awesome, it works now! Thanks loads for taking the time to come up with
>>> a solution!
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <daksh...@wso2.com
>>> > wrote:
>>>
>>>> Hi,
>>>>
>>>> I fixed your issue. please check
>>>>
>>>>
>>>> jQuery(document).ready(function() {
>>>>jQuery(".wiki-content a").each(function (){
>>>> if(jQuery(this).context.hash == ''){
>>>> jQuery(this).attr("target", "_blank");
>>>> }
>>>> });
>>>> });
>>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>> *Dakshika Jayathilaka*
>>>> PMC Member & Committer of Apache Stratos
>>>> Senior Software Engineer
>>>> WSO2, Inc.
>>>> lean.enterprise.middleware
>>>> 0771100911
>>>>
>>>> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills <mariang...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Imesh, Dakshika and Nisrin,
>>>>>
>>>>> Thanks for all your feedback and help!
>>>>>
>>>>> *@Dakshika* - I tried the script but it did not work, because when I
>>>>> used it all the links were opening in the same page.
>>>>>
>>>>> *@Imesh -* Thanks for the info!
>>>>>
>>>>> *@Nisrin* - When a user is new to docs, they will tend to always
>>>>> click on a link as opposed to right-clicking on a link. Furthermore, I was
>>>>> going on the assumption that they will close a link after they are done
>>>>> with a certain set of steps (but I guess it will not always be the case).
>>>>>
>>>>> As a workaround, I added an "expand macro" and pulled the child
>>>>> content into the expand macro using the "Include Page" macro, so that the
>>>>> user will not have to see a ton of instructions all at once.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Mariangela
>>>>>
>>>>>
>>>>> *Mariangela Hills*
>>>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>>>> Committer and PMC member - Apache Stratos
>>>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>>>
>>>>> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff <nis...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Mari,
>>>>>>
>>>>>> Wouldn't this result in too many tabs opening up as there will be a
>>>>>> new tab opening whenever a users clicks on a link.
>>>>>>
>>>>>> With how it is now, if a user wants to view the linked section in a
>>>>>> new tab, they can always right click and then click *Open Link in
>>>>>> New Tab*/*Open Link in New Window* right.
>>>>>>
>>>>>> So do you think we
Re: [Dev] Need help in customizing a script
*@Imesh & Jerad* - Thanks for your feedback! Imesh, we will change the
border color to a more subtle color.
*@Shavi* - Shavi, there is no need to say sorry! Even though it can look a
bit contrasting it matches the header.
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Fri, Oct 23, 2015 at 9:51 AM, Shavindri Dissanayake <shavin...@wso2.com>
wrote:
> Hi Imesh,
>
> I put that border, sorry my bad actually (was trying to match the header
> color). Shall remove it :)
>
> Thanks & Regards
> Shavindri Dissanayake
> Technical Writer
>
> WSO2 Inc.
> lean.enterprise.middleware
>
> On Fri, Oct 23, 2015 at 7:50 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> Thanks Mari! It looks good.
>> A quick thought: the blue colour border that we have used, for me its too
>> contrasting. WDYT?
>>
>> Thanks
>>
>> On Fri, Oct 23, 2015 at 5:35 AM, Mariangela Hills <mariang...@wso2.com>
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> The following is the actual page that I was planning on adding this
>>> script to. However, now, instead of navigating the user off to separate
>>> pages I have pulled the content from those pages into the main page, so
>>> that the respective sub content will appear within the main page when the
>>> user clicks on the respective expand link for instructions.
>>>
>>> https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>
>>>> Mari, can you please share a link to this page to have a look.
>>>>
>>>> Thanks
>>>>
>>>> On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake <
>>>> shavin...@wso2.com> wrote:
>>>>
>>>>> Thank you Dakshika, this is great!
>>>>>
>>>>> Thanks & Regards
>>>>> Shavindri Dissanayake
>>>>> Technical Writer
>>>>>
>>>>> WSO2 Inc.
>>>>> lean.enterprise.middleware
>>>>>
>>>>> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills <mariang...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi Dakshika,
>>>>>>
>>>>>> Awesome, it works now! Thanks loads for taking the time to come up
>>>>>> with a solution!
>>>>>>
>>>>>> Regards,
>>>>>> Mariangela
>>>>>>
>>>>>>
>>>>>> *Mariangela Hills*
>>>>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>>>>> Committer and PMC member - Apache Stratos
>>>>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>>>>
>>>>>> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <
>>>>>> daksh...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I fixed your issue. please check
>>>>>>>
>>>>>>>
>>>>>>> jQuery(document).ready(function() {
>>>>>>> jQuery(".wiki-content a").each(function (){
>>>>>>> if(jQuery(this).context.hash == ''){
>>>>>>> jQuery(this).attr("target", "_blank");
>>>>>>> }
>>>>>>> });
>>>>>>> });
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> *Dakshika Jayathilaka*
>>>>>>> PMC Member & Committer of Apache Stratos
>>>>>>> Senior Software Engineer
>>>>>>> WSO2, Inc.
>>>>>>> lean.enterprise.middleware
>>>>>>> 0771100911
>>>>>>>
>>>>>>> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills <
>>>>>>> mariang...@wso2.com> wrote:
>>>>>>>
>>>>>>>>
Re: [Dev] Need help in customizing a script
Hi Imesh, Dakshika and Nisrin,
Thanks for all your feedback and help!
*@Dakshika* - I tried the script but it did not work, because when I used
it all the links were opening in the same page.
*@Imesh -* Thanks for the info!
*@Nisrin* - When a user is new to docs, they will tend to always click on a
link as opposed to right-clicking on a link. Furthermore, I was going on
the assumption that they will close a link after they are done with a
certain set of steps (but I guess it will not always be the case).
As a workaround, I added an "expand macro" and pulled the child content
into the expand macro using the "Include Page" macro, so that the user will
not have to see a ton of instructions all at once.
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff <nis...@wso2.com> wrote:
> Hi Mari,
>
> Wouldn't this result in too many tabs opening up as there will be a new
> tab opening whenever a users clicks on a link.
>
> With how it is now, if a user wants to view the linked section in a new
> tab, they can always right click and then click *Open Link in New Tab*/*Open
> Link in New Window* right.
>
> So do you think we really need this?
>
> Thank you.
>
> Best Regards,
> Nisrin
>
> Nisrin Sheriff
> Senior Technical Writer
>
> *WSO2, Inc.*lean.enterprise.middleware.
> mobile: +94 776 24 84 56
> http://wso2.com
>
> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <daksh...@wso2.com>
> wrote:
>
>> Hi Mari,
>>
>> I have notice that you are using target="_blank" for internal page links
>> as wel. remove that attribute from links to navigate within page.
>>
>> > href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
>> *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
>> (CEP)
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka <daksh...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> IMO open a webpage in new tab or page is recommended depending on your
>>> use case. AFAIK giving a pop up link will block by browser due to security
>>> reason.
>>>
>>> So what you can do is, append simple class to "a"(anchor) to prevent all
>>> links opening in new page.
>>> Use below code snippet for Pages that you want to open in new page or
>>> tab.
>>>
>>> for HTML link:
>>>
>>> this is an external link
>>>
>>> for other links
>>>
>>> default
>>>
>>> Script:
>>>
>>>
>>> jQuery(document).ready(function() {
>>> jQuery(".wiki-content a.new-page").attr("target", "_blank");
>>> });
>>>
>>>
>>> Thank you,
>>>
>>> Regards,
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Oct 22, 2015 at 7:02 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>
>>>> Hi Mari,
>>>>
>>>> Opening a new tab or a new browser window is not recommended. Most of
>>>> the browsers block this by default due to security reasons. May be we need
>>>> to think of a different approach.
>>>>
>>>> Thanks
>>>>
>>>> On Thu, Oct 22, 2015 at 6:38 AM, Mariangela Hills <mariang...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> When working with the Wiki (Confluence) docs, there are times when we
>>>>> have to point off to sub-pages within a main set of instructions, so that
>>>>> the main page does not get too bulky. This means that when a user clicks
>>>>> these links, they will be redirected to those new pages within the same
>>>>> tab. Instead, it will be better if such links can be opened in a new
>>>>> tab/page, so that the user can always have the main set of instructions at
>>>>> hand.
>>>>>
>>>>> I found the following code block in [1], which needs to be added to a
>>>>> HTML
[Dev] Need help in customizing a script
Hi,
When working with the Wiki (Confluence) docs, there are times when we have
to point off to sub-pages within a main set of instructions, so that the
main page does not get too bulky. This means that when a user clicks these
links, they will be redirected to those new pages within the same tab.
Instead, it will be better if such links can be opened in a new tab/page,
so that the user can always have the main set of instructions at hand.
I found the following code block in [1], which needs to be added to a HTML
macro, to open external links and internal links in a new page. However,
the drawback when using this code block is that even the links in the table
of contents open in a new window :(
Will someone please be able to help by tweaking this code to stop links in
the table of contents opening in a new page?
Please note that I have created a set of sample pages in my wiki sandbox in
[2], so that you can test the tweaked code if needed.
jQuery(document).ready(function() {
jQuery(".wiki-content a").attr("target", "_blank");
});
[1]
https://confluence.atlassian.com/display/CONFKB/How+to+force+links+to+open+in+a+new+window
[2] https://docs.wso2.com/display/SM100/Main+page+with+instructions
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Error] Unable to add an application policy via UI
[Adding dev@wso2.org]
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Tue, Oct 13, 2015 at 12:21 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
> Hi,
>
> On Tue, Oct 13, 2015 at 12:03 PM, Mariangela Hills <mariang...@wso2.com>
> wrote:
>
>> Hi Pubudu & Akila,
>>
>> Pubudu, based on our offline discussion I signed out and signed in again,
>> and now it shows the application policy that mysteriously disappeared :)
>> Other users too might get confused in a scenario like this, because
>> normally when there is a session timeout the user is directed to the login
>> page. I wonder how I wasn't directed to the login page in this instance.
>>
>
> In that case we need to handle session timeout.
>
> @Dakshika, is it possible to redirect the page into the login page in the
> case of the session timeout?
>
>
>> Thanks, for the help Pubudu and Akila!
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Tue, Oct 13, 2015 at 12:02 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> [Looping Dakshika]
>>>
>>> But shouldn't the console app renew the authentication cookie on session
>>> timeout?
>>>
>>> On Tue, Oct 13, 2015 at 11:57 AM, Pubudu Gunatilaka <pubu...@wso2.com>
>>> wrote:
>>>
>>>> This is due to the session timeout.
>>>>
>>>> On Tue, Oct 13, 2015 at 11:55 AM, Akila Ravihansa Perera <
>>>> raviha...@wso2.com> wrote:
>>>>
>>>>> Hi Mari,
>>>>>
>>>>> Can you try the same via curl command and check the response you get?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Tue, Oct 13, 2015 at 11:48 AM, Mariangela Hills <
>>>>> mariang...@wso2.com> wrote:
>>>>>
>>>>>> Hi Team,
>>>>>>
>>>>>> Initially, I successfully added an application policy [1] via the
>>>>>> PPaaS Console. After sometime it disappeared from the application
>>>>>> policies
>>>>>> main page, so I assumed that I accidentally deleted it and tried adding
>>>>>> it
>>>>>> again, but I keep getting an error (The endpoint requires
>>>>>> authentication). Note that no message appears in the logs that I
>>>>>> deleted the application policy, which makes me wonder whether I actually
>>>>>> deleted it, and no message gets printed in the logs stating that there in
>>>>>> an issue with the application policy that I am trying to add.
>>>>>>
>>>>>> Can someone please let me know how I can resolve this issue that I am
>>>>>> facing.
>>>>>>
>>>>>>
>>>>>> [1]
>>>>>> https://github.com/wso2/private-paas-cartridges/blob/master/wso2am/1.9.0/samples/application-policies/mock/application-policy-1.json
>>>>>>
>>>>>> [2]
>>>>>>
>>>>>> [2015-10-12 16:34:29,239] INFO
>>>>>> {org.apache.stratos.cloud.controller.services.impl.CloudControllerServiceImpl}
>>>>>> - Adding cartridge: [cartridge-type] wso2am-190-gw-worker
>>>>>> [2015-10-12 16:34:29,272] INFO
>>>>>> {org.apache.stratos.cloud.controller.messaging.publisher.TopologyEventPublisher}
>>>>>> - Publishing service created event: [service-name] wso2am-190-gw-worker
>>>>>> [2015-10-12 16:34:29,289] INFO
>>>>>> {org.apache.stratos.messaging.message.processor.topology.ServiceCreatedMessageProcessor}
>>>>>> - Service created: [service] wso2am-190-gw-worker
>>>>>> [2015-10-12 16:34:29,292] INFO
>>>>>> {org.apache.stratos.cloud.controller.services.impl.CloudControllerServiceImpl}
>>>>>> - Successfully added cartridge: [cartridge-type] wso2am-190-gw-worker
>>>>>> [2015-10-12 16:35:15,820] INFO
>>>>>> {org.apache.stratos.cloud.controller.services.impl.CloudControllerServiceImpl}
>>>>>> - Adding cartridge: [cartridge-type] wso2am-190-km
>>>>>> [2015-10-12 16:35:15,842] I
[Dev] [Suggestion] Add JSON editor to add a cartridge group & application in PPaaS
Hi Devs, The JSON editor appears when viewing details of a cartridge group and application. However, it is not available at the time of adding a cartridge group or application. The current topology aspect to add a cartridge group or application is nice. However, IMO it will be really useful if we can also provide the user with the JSON editor function when adding a cartridge group and application via the PPaaS Console, because there will be users who will prefer to use this function. For example, if a user wants to tryout sample configurations using a step-by-step approach via the UI and has all the JSON definitions with him/her, he/she will look at simply copying and pasting the JSON definition in the JSON editor, rather than having to analyze the sample and figure the dependancies etc. to use the topology approach. https://wso2.org/jira/browse/PAAS-263 Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store
Hi Shabir, Please note that I have updated [1] based on the feedback in this thread and also based on the points we came up with after testing this tutorial in-depth. Thanks, for all the help! [1] https://docs.wso2.com/display/ES200/Adding+a+Sample+Asset+for+a+New+Asset+Type+at+Server+Startup Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Wed, Sep 16, 2015 at 10:27 AM, Mariangela Hills <mariang...@wso2.com> wrote: > *@Shabir* > Sorry, for the late reply! I will add these common mistakes as tips in the > ES wiki docs. > > *@Jackie* > Jackie, thanks for your feedback! Yes, I too think that adding this > information in a "Tips" macro will be useful to the user. In addition, I > will do the other corrections that you mentioned. > > Regards, > Mariangela > > > *Mariangela Hills* > Senior Technical Writer - WSO2, Inc. http://wso2.com > Committer and PMC member - Apache Stratos > email:mariang...@wso2.com | mobile: +94 773 500185 > > On Wed, Sep 16, 2015 at 5:22 AM, Jackie Wheeler <jac...@wso2.com> wrote: > >> I think we can add a "Tips" section at the bottom and have a bulleted >> list of these items, such as "Be sure to add the lifecycle definition to >> the path." >> >> Mari, the note in the middle of the page is missing content in the second >> sentence. Currently it says: >> >> You need to define the latter mentioned asset specific attributes in a >> JSON file, which has the same name as the asset type RXT (e.g., >> RXT_NAME.json). In this case >> >> Also, at the end of the page, the last sentence is missing a word: >> >> In this tutorial, as we have set the lifecycle status to the artifact >> is visible in the Store. >> >> Cheers, >> Jackie >> >> >> On Mon, Sep 14, 2015 at 7:44 AM, Shabir Mohamed <sha...@wso2.com> wrote: >> >>> Hi Mariangela, >>> >>> I thought the "Common Mistakes"would also be useful for someone who >>> reads the documentation. >>> >>> Isn't it within our documentation guidelines to add something like >>> that??? If so that's fine :D >>> >>> - >>> *Shabir Mohamed* >>> *Software Engineer* >>> WSO2 Inc.; http://wso2.com >>> Email: sha...@wso2.com <ayy...@wso2.com> >>> Mobile: +94 77 3516019 | +94 71 6583393 >>> >>> On Mon, Sep 14, 2015 at 8:09 PM, Shabir Mohamed <sha...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> Thanks a lot:D >>>> >>>> Regards >>>> >>>> - >>>> *Shabir Mohamed* >>>> *Software Engineer* >>>> WSO2 Inc.; http://wso2.com >>>> Email: sha...@wso2.com <ayy...@wso2.com> >>>> Mobile: +94 77 3516019 | +94 71 6583393 >>>> >>>> On Mon, Sep 14, 2015 at 6:45 PM, Mariangela Hills <mariang...@wso2.com> >>>> wrote: >>>> >>>>> Hi Shabir, >>>>> I have documented this in [1]. >>>>> >>>>> [1] >>>>> https://docs.wso2.com/display/ES200/Adding+a+New+Sample+Asset+for+an+Asset+Type+at+Server+Startup >>>>> >>>>> Regards, >>>>> Mariangela >>>>> >>>>> >>>>> *Mariangela Hills* >>>>> Senior Technical Writer - WSO2, Inc. http://wso2.com >>>>> Committer and PMC member - Apache Stratos >>>>> email:mariang...@wso2.com | mobile: +94 773 500185 >>>>> >>>>> On Fri, Sep 11, 2015 at 3:32 PM, Mariangela Hills <mariang...@wso2.com >>>>> > wrote: >>>>> >>>>>> I created a JIRA [1] to track this task. >>>>>> >>>>>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2366 >>>>>> >>>>>> Regards, >>>>>> Mariangela >>>>>> >>>>>> >>>>>> *Mariangela Hills* >>>>>> Senior Technical Writer - WSO2, Inc. http://wso2.com >>>>>> Committer and PMC member - Apache Stratos >>>>>> email:mariang...@wso2.com | mobile: +94 773 500185 >>>>>> >>>>>> On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills < >>>>>> mariang...@wso2.com> wrote: >>>>>> >>>>&g
Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store
*@Shabir* Sorry, for the late reply! I will add these common mistakes as tips in the ES wiki docs. *@Jackie* Jackie, thanks for your feedback! Yes, I too think that adding this information in a "Tips" macro will be useful to the user. In addition, I will do the other corrections that you mentioned. Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Wed, Sep 16, 2015 at 5:22 AM, Jackie Wheeler <jac...@wso2.com> wrote: > I think we can add a "Tips" section at the bottom and have a bulleted list > of these items, such as "Be sure to add the lifecycle definition to the > path." > > Mari, the note in the middle of the page is missing content in the second > sentence. Currently it says: > > You need to define the latter mentioned asset specific attributes in a > JSON file, which has the same name as the asset type RXT (e.g., > RXT_NAME.json). In this case > > Also, at the end of the page, the last sentence is missing a word: > > In this tutorial, as we have set the lifecycle status to the artifact is > visible in the Store. > > Cheers, > Jackie > > > On Mon, Sep 14, 2015 at 7:44 AM, Shabir Mohamed <sha...@wso2.com> wrote: > >> Hi Mariangela, >> >> I thought the "Common Mistakes"would also be useful for someone who reads >> the documentation. >> >> Isn't it within our documentation guidelines to add something like >> that??? If so that's fine :D >> >> - >> *Shabir Mohamed* >> *Software Engineer* >> WSO2 Inc.; http://wso2.com >> Email: sha...@wso2.com <ayy...@wso2.com> >> Mobile: +94 77 3516019 | +94 71 6583393 >> >> On Mon, Sep 14, 2015 at 8:09 PM, Shabir Mohamed <sha...@wso2.com> wrote: >> >>> Hi, >>> >>> Thanks a lot:D >>> >>> Regards >>> >>> - >>> *Shabir Mohamed* >>> *Software Engineer* >>> WSO2 Inc.; http://wso2.com >>> Email: sha...@wso2.com <ayy...@wso2.com> >>> Mobile: +94 77 3516019 | +94 71 6583393 >>> >>> On Mon, Sep 14, 2015 at 6:45 PM, Mariangela Hills <mariang...@wso2.com> >>> wrote: >>> >>>> Hi Shabir, >>>> I have documented this in [1]. >>>> >>>> [1] >>>> https://docs.wso2.com/display/ES200/Adding+a+New+Sample+Asset+for+an+Asset+Type+at+Server+Startup >>>> >>>> Regards, >>>> Mariangela >>>> >>>> >>>> *Mariangela Hills* >>>> Senior Technical Writer - WSO2, Inc. http://wso2.com >>>> Committer and PMC member - Apache Stratos >>>> email:mariang...@wso2.com | mobile: +94 773 500185 >>>> >>>> On Fri, Sep 11, 2015 at 3:32 PM, Mariangela Hills <mariang...@wso2.com> >>>> wrote: >>>> >>>>> I created a JIRA [1] to track this task. >>>>> >>>>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2366 >>>>> >>>>> Regards, >>>>> Mariangela >>>>> >>>>> >>>>> *Mariangela Hills* >>>>> Senior Technical Writer - WSO2, Inc. http://wso2.com >>>>> Committer and PMC member - Apache Stratos >>>>> email:mariang...@wso2.com | mobile: +94 773 500185 >>>>> >>>>> On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills < >>>>> mariang...@wso2.com> wrote: >>>>> >>>>>> Thanks, Shabir! I will add this to the docs! >>>>>> >>>>>> Regards, >>>>>> Mariangela >>>>>> >>>>>> >>>>>> *Mariangela Hills* >>>>>> Senior Technical Writer - WSO2, Inc. http://wso2.com >>>>>> Committer and PMC member - Apache Stratos >>>>>> email:mariang...@wso2.com | mobile: +94 773 500185 >>>>>> >>>>>> On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed <sha...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Also to be added to *Common Mistakes:* >>>>>>> >>>>>>> >>>>>>>- The *"name" *attribute and the *"overview_name"* attribute, >>>>>>>both needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry >>>>>>> Pi'
Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store
Hi Shabir, I have documented this in [1]. [1] https://docs.wso2.com/display/ES200/Adding+a+New+Sample+Asset+for+an+Asset+Type+at+Server+Startup Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Fri, Sep 11, 2015 at 3:32 PM, Mariangela Hills <mariang...@wso2.com> wrote: > I created a JIRA [1] to track this task. > > [1] https://wso2.org/jira/browse/DOCUMENTATION-2366 > > Regards, > Mariangela > > > *Mariangela Hills* > Senior Technical Writer - WSO2, Inc. http://wso2.com > Committer and PMC member - Apache Stratos > email:mariang...@wso2.com | mobile: +94 773 500185 > > On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills <mariang...@wso2.com> > wrote: > >> Thanks, Shabir! I will add this to the docs! >> >> Regards, >> Mariangela >> >> >> *Mariangela Hills* >> Senior Technical Writer - WSO2, Inc. http://wso2.com >> Committer and PMC member - Apache Stratos >> email:mariang...@wso2.com | mobile: +94 773 500185 >> >> On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed <sha...@wso2.com> wrote: >> >>> Also to be added to *Common Mistakes:* >>> >>> >>>- The *"name" *attribute and the *"overview_name"* attribute, both >>>needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry Pi' will >>> not >>>work). *"name"* is the Artifact-Name and "*overview_name*" is the >>>value used when creating the resource path in the registry. >>> >>> >>> - >>> *Shabir Mohamed* >>> *Software Engineer* >>> WSO2 Inc.; http://wso2.com >>> Email: sha...@wso2.com <ayy...@wso2.com> >>> Mobile: +94 77 3516019 | +94 71 6583393 >>> >>> On Thu, Sep 10, 2015 at 9:10 PM, Shabir Mohamed <sha...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> I have been trying to do $subject and found no relevant documentation. >>>> Hence, I backtracked the path as to how the existing sample-artifacts of >>>> the default asset-types (i.e.: gadget & site) are added when running the >>>> WSO2 - Enterprise Store 2.0. >>>> >>>> *As per my study these are the necessary steps required to do $subject:* >>>> >>>> Say the Asset-type for which we want to add a sample artifact has its >>>> *"RXT"* name as *"device.rxt". **(sample txt attached in the email)* >>>> >>>> 1. *The sample artifacts per asset-type are found at path:* >>>> >>>>- >>>> >>>> */repository/deployment/server/jaggeryapps/publisher/samples/assets* >>>>- Create a folder by the plural-name of the asset-type(rxt) in this >>>>path. In this example we make a folder by the name *"devices"*. >>>>- All sample/default artifacts of asset-type *"device" *shall go >>>>into this folder. >>>> >>>> 2. The parent installation script - *"install.js"* - for all samples >>>> is found at the above mentioned path. Any *"install.js"* scripts found >>>> within sub-folders *(ex: devices, gadgets & sites)* of this path will >>>> over-ride the parent script to perform any specific operations relavant to >>>> that asset-type. >>>> >>>>- copy the sample asset-specific *"install.js"** (attached with >>>>this email)* into the folder created in the previous step. >>>>- search and change the following tags appropriately in the copied >>>>script: >>>> >>>> ** : LifeCycle definition to which >>>> the asset-type *(in this example "device") *needs to be attached to *(ex: >>>> DeviceLifeCycle)*. Should be one of the lifecycle definitions found >>>> inside: >>>> */repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles/* >>>> ** : The *"rxt"* name of the >>>> asset-type for which the samples are to be made *(in this >>>> example "device"). * >>>> >>>>- Save and close the *"install.js"* script. >>>> >>>> 3. Create a folder by the name of the sample-artifact inside the >>>> asset-specific-parent-folder created in Step 1. In this example lets ca
Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store
I created a JIRA [1] to track this task. [1] https://wso2.org/jira/browse/DOCUMENTATION-2366 Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills <mariang...@wso2.com> wrote: > Thanks, Shabir! I will add this to the docs! > > Regards, > Mariangela > > > *Mariangela Hills* > Senior Technical Writer - WSO2, Inc. http://wso2.com > Committer and PMC member - Apache Stratos > email:mariang...@wso2.com | mobile: +94 773 500185 > > On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed <sha...@wso2.com> wrote: > >> Also to be added to *Common Mistakes:* >> >> >>- The *"name" *attribute and the *"overview_name"* attribute, both >>needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry Pi' will not >>work). *"name"* is the Artifact-Name and "*overview_name*" is the >>value used when creating the resource path in the registry. >> >> >> - >> *Shabir Mohamed* >> *Software Engineer* >> WSO2 Inc.; http://wso2.com >> Email: sha...@wso2.com <ayy...@wso2.com> >> Mobile: +94 77 3516019 | +94 71 6583393 >> >> On Thu, Sep 10, 2015 at 9:10 PM, Shabir Mohamed <sha...@wso2.com> wrote: >> >>> Hi, >>> >>> I have been trying to do $subject and found no relevant documentation. >>> Hence, I backtracked the path as to how the existing sample-artifacts of >>> the default asset-types (i.e.: gadget & site) are added when running the >>> WSO2 - Enterprise Store 2.0. >>> >>> *As per my study these are the necessary steps required to do $subject:* >>> >>> Say the Asset-type for which we want to add a sample artifact has its >>> *"RXT"* name as *"device.rxt". **(sample txt attached in the email)* >>> >>> 1. *The sample artifacts per asset-type are found at path:* >>> >>>- >>> >>> */repository/deployment/server/jaggeryapps/publisher/samples/assets* >>>- Create a folder by the plural-name of the asset-type(rxt) in this >>>path. In this example we make a folder by the name *"devices"*. >>>- All sample/default artifacts of asset-type *"device" *shall go >>>into this folder. >>> >>> 2. The parent installation script - *"install.js"* - for all samples is >>> found at the above mentioned path. Any *"install.js"* scripts found >>> within sub-folders *(ex: devices, gadgets & sites)* of this path will >>> over-ride the parent script to perform any specific operations relavant to >>> that asset-type. >>> >>>- copy the sample asset-specific *"install.js"** (attached with this >>>email)* into the folder created in the previous step. >>>- search and change the following tags appropriately in the copied >>>script: >>> >>> ** : LifeCycle definition to which >>> the asset-type *(in this example "device") *needs to be attached to *(ex: >>> DeviceLifeCycle)*. Should be one of the lifecycle definitions found >>> inside: >>> */repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles/* >>> ** : The *"rxt"* name of the >>> asset-type for which the samples are to be made *(in this >>> example "device"). * >>> >>>- Save and close the *"install.js"* script. >>> >>> 3. Create a folder by the name of the sample-artifact inside the >>> asset-specific-parent-folder created in Step 1. In this example lets call >>> our sample artifact of asset-type *"device"* as *"firealarm"*. We can >>> continue adding any number of folders *per artifact* of the asset-type *(ex: >>> firearm, raspberryPi, arduino & etc)*. Artifact specific details go >>> into these folders. >>> >>> *The folder structure >>> at- /repository/deployment/server/jaggeryapps/publisher/samples >>> should >>> look as follows:* >>> >>> *.* >>> >>> *└── samples* >>> >>> *└── assets* >>> >>> *├── devices* >>> >>> *│ ├── firealarm* >>> >>> *│ │ ├── banner.png* >>> >>> *│ │ ├── dev
Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store
Thanks, Shabir! I will add this to the docs! Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed <sha...@wso2.com> wrote: > Also to be added to *Common Mistakes:* > > >- The *"name" *attribute and the *"overview_name"* attribute, both >needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry Pi' will not >work). *"name"* is the Artifact-Name and "*overview_name*" is the >value used when creating the resource path in the registry. > > > - > *Shabir Mohamed* > *Software Engineer* > WSO2 Inc.; http://wso2.com > Email: sha...@wso2.com <ayy...@wso2.com> > Mobile: +94 77 3516019 | +94 71 6583393 > > On Thu, Sep 10, 2015 at 9:10 PM, Shabir Mohamed <sha...@wso2.com> wrote: > >> Hi, >> >> I have been trying to do $subject and found no relevant documentation. >> Hence, I backtracked the path as to how the existing sample-artifacts of >> the default asset-types (i.e.: gadget & site) are added when running the >> WSO2 - Enterprise Store 2.0. >> >> *As per my study these are the necessary steps required to do $subject:* >> >> Say the Asset-type for which we want to add a sample artifact has its >> *"RXT"* name as *"device.rxt". **(sample txt attached in the email)* >> >> 1. *The sample artifacts per asset-type are found at path:* >> >>- >> >> */repository/deployment/server/jaggeryapps/publisher/samples/assets* >>- Create a folder by the plural-name of the asset-type(rxt) in this >>path. In this example we make a folder by the name *"devices"*. >>- All sample/default artifacts of asset-type *"device" *shall go into >>this folder. >> >> 2. The parent installation script - *"install.js"* - for all samples is >> found at the above mentioned path. Any *"install.js"* scripts found >> within sub-folders *(ex: devices, gadgets & sites)* of this path will >> over-ride the parent script to perform any specific operations relavant to >> that asset-type. >> >>- copy the sample asset-specific *"install.js"** (attached with this >>email)* into the folder created in the previous step. >>- search and change the following tags appropriately in the copied >>script: >> >> ** : LifeCycle definition to which >> the asset-type *(in this example "device") *needs to be attached to *(ex: >> DeviceLifeCycle)*. Should be one of the lifecycle definitions found >> inside: >> */repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles/* >> ** : The *"rxt"* name of the >> asset-type for which the samples are to be made *(in this >> example "device"). * >> >>- Save and close the *"install.js"* script. >> >> 3. Create a folder by the name of the sample-artifact inside the >> asset-specific-parent-folder created in Step 1. In this example lets call >> our sample artifact of asset-type *"device"* as *"firealarm"*. We can >> continue adding any number of folders *per artifact* of the asset-type *(ex: >> firearm, raspberryPi, arduino & etc)*. Artifact specific details go into >> these folders. >> >> *The folder structure >> at- /repository/deployment/server/jaggeryapps/publisher/samples >> should >> look as follows:* >> >> *.* >> >> *└── samples* >> >> *└── assets* >> >> *├── devices* >> >> *│ ├── firealarm* >> >> *│ │ ├── banner.png* >> >> *│ │ ├── device.json* >> >> *│ │ └── thumbnail.png* >> >> *│ └── install.js* >> >> *└── install.js* >> >> >> 4. Now we have to specify the asset specific attributes to be used when >> creating our sample (firealarm) artifact. These details are provided as a >> *"json" >> *file with the same name as the asset-type/rxt *(.json)*. >> >> >>- In our example this is found inside the *"firealarm"* artifact >>folder as *"device.json"*. For every additional artifact-folder that >>is declared, there will be a corresponding *"device.json" *file with >>relevant attribute details. *(The one used for
Re: [Dev] [Documentation][Jaggery][UAE] Unrelated Hyperlink
Adding Manu! Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 On Wed, Sep 9, 2015 at 12:43 PM, Sachith Punchihewa <sachi...@wso2.com> wrote: > Hi Documentation/UAE teams, > > In the XML section of Jaggery Documentation which you can find in[1]. > > The hyperlink for E4X is currently redirecting to a document which is > related to > *Case for 120 mmHVD-ROM disk from ECMA International.* > The article can be found in [2]. > > According to my understanding the redirection must be to the *E4X Quick > Start Guide* in *WSO2 MS Distribution Documentation*[3]. > > [1] http://jaggeryjs.org/documentation.jag?api=xml > [2] > http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-375.pdf > [3] http://wso2.com/project/mashup/2.2.0/docs/e4xquickstart.html > > Thanks & Regards. > > Kamidu Sachith Punchihewa > *Software Engineer* > WSO2, Inc. > lean . enterprise . middleware > Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194> > > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, retransmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > > -- > You received this message because you are subscribed to the Google Groups > "WSO2 Documentation Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to documentation+unsubscr...@wso2.com. > For more options, visit https://groups.google.com/a/wso2.com/d/optout. > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES] Can't publish in Enterprise store
Thanks, Kathees and Manuranga!
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Wed, Sep 2, 2015 at 4:11 PM, Manuranga Perera <m...@wso2.com> wrote:
> Hi Mariangela,
> this fix is for ES 1.2. this issue is already addressed in 2.0.0.
>
> On Wed, Sep 2, 2015 at 3:59 PM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>> HI Mariangela,
>>
>> I increased the count and paginationLimit values in
>> WSO2ES_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/pages/list.jag.
>>
>>
>> var DEFAULT_PAGIN = {
>> 'start': 0,
>> 'count': 1000,
>> 'sortOrder': 'DESC',
>> 'sortBy': 'overview_createdtime',
>> 'paginationLimit':1000
>> };
>>
>> Thanks,
>> Kathees
>>
>> On Wed, Sep 2, 2015 at 3:49 PM, Mariangela Hills <mariang...@wso2.com>
>> wrote:
>>
>>> Hi Kathees,
>>>
>>> Can you please let me know the exact changes that you made in the list.jag
>>> file, so that I can document this in the ES wiki docs.
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Wed, Sep 2, 2015 at 10:25 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Good Job Kathees. :)
>>>>
>>>> This became complete blocker for the store release and thx for fixing
>>>> it quickly.
>>>>
>>>> On Wed, Sep 2, 2015 at 10:19 AM, Kathees Rajendram <kath...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Manuranga/Sameera,
>>>>>
>>>>> I have fixed the issue by changing the value in the following jaggery
>>>>> file.
>>>>>
>>>>> WSO2ES_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/pages/list.jag
>>>>>
>>>>> Thanks,
>>>>> Kathees
>>>>>
>>>>> On Wed, Sep 2, 2015 at 8:05 AM, Sameera Medagammaddegedara <
>>>>> samee...@wso2.com> wrote:
>>>>>
>>>>>> EDIT: My apologies, I did not notice that you were talking about the
>>>>>> Publisher application.
>>>>>>
>>>>>> On Tue, Sep 1, 2015 at 10:21 PM, Sameera Medagammaddegedara <
>>>>>> samee...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Kathees,
>>>>>>>
>>>>>>> If I remember correctly the above code snippet is not invoked from
>>>>>>> the Store application.The AssetManager is not utilized in the Store
>>>>>>> application of the ES pack that you are using.
>>>>>>>
>>>>>>> Thank You,
>>>>>>> Sameera
>>>>>>>
>>>>>>> On Fri, Aug 28, 2015 at 1:02 AM, Kathees Rajendram <kath...@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi Manuranga,
>>>>>>>>
>>>>>>>> The count and paginationLimit values are 1000 but 100 asserts only
>>>>>>>> are listed. I tried to increase the number. The changes are not picked
>>>>>>>> up.
>>>>>>>>
>>>>>>>> ../modules/rxt/scripts/asset/asset.js
>>>>>>>>
>>>>>>>> function AssetManager(registry, type, rxtManager, renderer) {
>>>>>>>> this.registry = registry;
>>>>>>>> this.rxtManager = rxtManager;
>>>>>>>> this.rxtTemplate = rxtManager.getRxtDefinition(type);
>>>>>>>> this.type = type;
>>>>>>>> this.r = renderer;
>>>>>>>> this.am = null;
>>>>>>>> this.defaultPaging = {
>>>>>>>> 'start': 0,
>>>>>>>> 'count': 1000,
>>>>>>>> 'sortOrder': 'desc',
>>>>>>>> 'sortBy': 'overview_createdtime',
>>>>>>>> 'paginationLimit': 1000
>>>>>
Re: [Dev] [ES] Can't publish in Enterprise store
Hi Kathees,
Can you please let me know the exact changes that you made in the list.jag
file, so that I can document this in the ES wiki docs.
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Wed, Sep 2, 2015 at 10:25 AM, Malaka Silva <mal...@wso2.com> wrote:
> Good Job Kathees. :)
>
> This became complete blocker for the store release and thx for fixing it
> quickly.
>
> On Wed, Sep 2, 2015 at 10:19 AM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>> Hi Manuranga/Sameera,
>>
>> I have fixed the issue by changing the value in the following jaggery
>> file.
>>
>> WSO2ES_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/pages/list.jag
>>
>> Thanks,
>> Kathees
>>
>> On Wed, Sep 2, 2015 at 8:05 AM, Sameera Medagammaddegedara <
>> samee...@wso2.com> wrote:
>>
>>> EDIT: My apologies, I did not notice that you were talking about the
>>> Publisher application.
>>>
>>> On Tue, Sep 1, 2015 at 10:21 PM, Sameera Medagammaddegedara <
>>> samee...@wso2.com> wrote:
>>>
>>>> Hi Kathees,
>>>>
>>>> If I remember correctly the above code snippet is not invoked from the
>>>> Store application.The AssetManager is not utilized in the Store application
>>>> of the ES pack that you are using.
>>>>
>>>> Thank You,
>>>> Sameera
>>>>
>>>> On Fri, Aug 28, 2015 at 1:02 AM, Kathees Rajendram <kath...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Manuranga,
>>>>>
>>>>> The count and paginationLimit values are 1000 but 100 asserts only are
>>>>> listed. I tried to increase the number. The changes are not picked up.
>>>>>
>>>>> ../modules/rxt/scripts/asset/asset.js
>>>>>
>>>>> function AssetManager(registry, type, rxtManager, renderer) {
>>>>> this.registry = registry;
>>>>> this.rxtManager = rxtManager;
>>>>> this.rxtTemplate = rxtManager.getRxtDefinition(type);
>>>>> this.type = type;
>>>>> this.r = renderer;
>>>>> this.am = null;
>>>>> this.defaultPaging = {
>>>>> 'start': 0,
>>>>> 'count': 1000,
>>>>> 'sortOrder': 'desc',
>>>>> 'sortBy': 'overview_createdtime',
>>>>> 'paginationLimit': 1000
>>>>> };
>>>>> }
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Kathees
>>>>>
>>>>> On Thu, Aug 27, 2015 at 10:21 PM, Manuranga Perera <m...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> number 100 is hard-coded in modules dir please grep and fix. can you
>>>>>> meet me tomorrow?
>>>>>>
>>>>>> On Thu, Aug 27, 2015 at 6:40 PM, Kathees Rajendram <kath...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Adding Manuranga,
>>>>>>>
>>>>>>> On Thu, Aug 27, 2015 at 6:23 PM, Kathees Rajendram <kath...@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> In ESB connector store, we are unable to publish the new
>>>>>>>> connectors. The ESB connector store publisher is restricted to view
>>>>>>>> only
>>>>>>>> 100 connectors. We are having more than 100 connectors to add to the
>>>>>>>> store.
>>>>>>>> Can you suggest how to increase the limit in the wso2es-1.2.0-SNAPSHOT?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Kathees
>>>>>>>> --
>>>>>>>> Kathees
>>>>>>>> Software Engineer,
>>>>>>>> email: kath...@wso2.com
>>>>>>>> mobile: +94772596173
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Kathees
>>>>>>> Software Engineer,
>>>>>>> email: kath...@wso2.com
>>>>>>> mobile: +94772596173
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> With regards,
>>>>>> *Manu*ranga Perera.
>>>>>>
>>>>>> phone : 071 7 70 20 50
>>>>>> mail : m...@wso2.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Kathees
>>>>> Software Engineer,
>>>>> email: kath...@wso2.com
>>>>> mobile: +94772596173
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sameera Medagammaddegedara
>>>> Software Engineer
>>>>
>>>> Contact:
>>>> Email: samee...@wso2.com
>>>> Mobile: + 94 077 255 3005
>>>>
>>>
>>>
>>>
>>> --
>>> Sameera Medagammaddegedara
>>> Software Engineer
>>>
>>> Contact:
>>> Email: samee...@wso2.com
>>> Mobile: + 94 077 255 3005
>>>
>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
>
> 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/>
>
> 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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES] - Error adding Assets without Name and Version, when Version and Name are not Required fields in the RXT definition.
Nadeesha, this is a good catch! I will update the ES docs appropriately
when a conclusion is reached in this regard!
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Fri, Aug 21, 2015 at 11:39 AM, Nadeesha Meegoda nadees...@wso2.com
wrote:
Hi ES team,
We all are aware that assets cannot be created without an *Asset Name*
and *Version *since they are mandatory in the perspective of adding an
asset. But in user perspective since the RXT is customizable they can
remove the *Required =True* for those * Name* and *Version* fields
and with that RXT configuration if they try to add an asset without those
fields, backend Error is thrown which is noted in [1].
If we make those fields *Not Required* from RXT, these will be
reflected in Asset creation UI as *Not Required *fields which is
misleading to the end users as they are actually Not required fields but
when actually adding the asset, backend error is thrown since they should
be saved in storagePath.
Can we have a feasible solution for this please? The following are few
suggestions from QA.
1. Though the Required=true is removed for Name and Version from RXT
definition, we can show it as mandatory in asset creation UI and when they
are values for those fields are not entered give a feasible UI error message
2. We can validate the RXT whether those fields are always Required =
True and without those fields Required = True the RXT cannot be saved
.
In QA's point of view this is an issue that should be given attention to.
The jira added for this is noted in [2]. But ths jira was added only
considering version field.
Any feedback on this is highly appreciated!
[1] - [2015-06-12 14:33:54,310] ERROR
{org.wso2.carbon.governance.api.util.GovernanceUtils}
- Value for required attribute overview_version found empty.
[2015-06-12 14:33:54,315] ERROR
{org.wso2.carbon.governance.api.common.GovernanceArtifactManager}
- Failed to add artifact: artifact id:
176cd77f-3604-42b5-976e-2b2bd09c57eb. Value for required attribute
overview_version found empty.
org.wso2.carbon.governance.api.exception.GovernanceException: Value for
required attribute overview_version found empty.
at
org.wso2.carbon.governance.api.util.GovernanceUtils.getPathFromPathExpression(GovernanceUtils.java:1303)
at
org.wso2.carbon.governance.api.common.GovernanceArtifactManager.addGovernanceArtifact(GovernanceArtifactManager.java:185)
at
org.wso2.carbon.governance.api.generic.GenericArtifactManager.addGenericArtifact(GenericArtifactManager.java:215)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.carbon.\scripts\registry.c0._c_anonymous_20(carbon\scripts\registry\artifacts.js:299)
at
org.jaggeryjs.rhino.carbon.\scripts\registry.c0.call(carbon\scripts\registry\artifacts.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.rxt.\scripts\asset.c0._c_anonymous_11(rxt\scripts\asset\asset.js:202)
at
org.jaggeryjs.rhino.rxt.\scripts\asset.c0.call(rxt\scripts\asset\asset.js)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1473)
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:815)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:109)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c4._c_anonymous_13(/publisher/modules/asset-api.js:234)
at
org.jaggeryjs.rhino.publisher.modules.c4.call(/publisher/modules/asset-api.js)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.extensions.assets.default.apis.c0._c_anonymous_1(/publisher/extensions/assets/default/apis/assets.jag:71)
at
org.jaggeryjs.rhino.publisher.extensions.assets.default.apis.c0.call(/publisher/extensions/assets/default/apis/assets.jag)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at org.mozilla.javascript.optimizer.OptRuntime.call2
[Dev] Current implementation of the defaultLifecycleEnabled property might confuse ES users
Hi Manu, In an offline discussion with Ayesha, I learnt the following regarding the defaultLifecycleEnabled property: - defaultLifecycleEnabled: *true *This property needs to be set to true in the asset extension (asset.js) when a user wants to attach a lifecycle to an asset type. This is in the event that the user has not already defined a lifecycle when creating the asset type. - defaultLifecycleEnabled: false This property needs to be set to false when the user has defined a lifecycle when creating the asset type. Based on the latter mentioned, ES considers the lifecycle defined in the asset extension (asset.js) as the default lifecycle for the asset type. However, GREG refers to the lifecycle defined in the RXT as the default lifecycle [1]. Is it really necessary to deviate from the concept that GREG uses? This can end-up confusing the user. As the initial impression that the user gets when seeing the defaultLifecycleEnabled property is that if this property is set to true, the lifecycle defined in the RXT will be considered, and if we set this property to false, the lifecycle defined in the asset extension will be considered. However, ES has been designed to work wise versa, which is confusing, because we are telling the user to consider a lifecycle defined in an extension as the default as opposed to the lifecycle that is defined in the RXT, which is the root source for an asset type. I do understand that it is not mandatory to define a lifecycle in the RXT. However, it might be better to change the current ES implementation, so that defaultLifecycleEnabled: true refers to the lifecycle in the RXT. WDYT? [1] https://docs.wso2.com/display/Governance460/Governance+Artifacts+Configuration+Model+Elements#GovernanceArtifactsConfigurationModelElements-ThelifecycleElement Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Clarification needed on the properties returned by the asset.configure callback method
Hi team,
Can you please clarify the following doubts:
1) How come the field name appears in three consecutive nested levels in
the default
ES_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/asset.js
[1] file?
2) In an offline chat, you mentioned that the properties returned by the
asset.configure callback function were as follows: name, label, type,
readonly, hidden, updatable. As the field label appears at a different
level when compared to the other fields, is it correct to have label too
as a property that is returned by the asset.configure callback method? If
'label' is actually a property that is returned, shouldn't it be defined at
the same level as the other properties that are returned?
[1]
asset.configure = function() {
return {
table: {
overview: {
fields: {
provider: {
auto: true
},
name: {
name: {
name: 'name',
label: 'Name'
},
updatable: false,
validation: function() {}
},
version: {
name: {
label: 'Version'
}
},
createdtime: {
hidden: true
}
}
},
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Need list of methods retuned by asset.render callback method
Hi Sameera, As the methods returned by the asset.render callback method was not available in [1], I looked in the asset.js files in the ES code in [2] [3] and [4] to identify these methods, as this information is needed for the ES wiki docs [5]. Similar to asset.manager, I expected to find the entire list of methods returned by asset.render in [2]. However, I noticed that [2] had methods that were not available in the publisher [3] or store asset.js [4] files (e.g., buildAssetPageUrl, buildUrl, lifecycle etc.) and also that some of the methods in the publisher and store were not found in [2] (e.g., populateTags, tags etc.). Shouldn't all the possible methods that are returned by the asset.render callback method appear in [2]? Where can I identify the entire list of methods that are returned by the asset.render callback method? [1] https://docs.google.com/document/d/1_blb4u8aFn-6jTpHx6fynTgohAI4KQgUaEE-so5IxSg/edit# [2] ES_HOME/modules/rxt/scripts/asset/asset.js file [3] ES_HOME/ repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/asset.js file [4] ES_HOME/ repository/deployment/server/jaggeryapps/store/extensions/assets/default/asset.js file [5] https://docs.wso2.com/display/ES200/asset.render+Property+Definitions Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Stratos] CloudControllerServiceCartridgeNotFoundExceptionException when adding the application
Fixed this issue in the following pages:
-
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Single+Cartridge+on+EC2
-
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Single+Cartridge+on+Kubernetes
-
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Single+Cartridge+on+OpenStack
Regards,
Mariangela
*--*
Mariangela Hills
Senior Technical Writer
*WSO2, Inc.*lean.enterprise.middleware.
m: +94 773 500185
w: http://wso2.com
http://wso2.com/events/
On Fri, Feb 20, 2015 at 11:19 AM, Udara Liyanage ud...@wso2.com wrote:
Hi Mari,
Issue still exist in other IaaSes such as Openstack. Need to fix them too.
On Wed, Feb 18, 2015 at 3:55 PM, Mariangela Hills mariang...@wso2.com
wrote:
This has been fixed in [1]. Thanks, for reporting!
[1] https://issues.apache.org/jira/browse/STRATOS-1198
Regards,
Mariangela
*--*
Mariangela Hills
Senior Technical Writer
*WSO2, Inc.*lean.enterprise.middleware.
m: +94 773 500185
w: http://wso2.com
http://wso2.com/events/
On Wed, Feb 18, 2015 at 2:34 PM, Udara Liyanage ud...@wso2.com wrote:
Hi Mari,
There was an mistake in the doc mentioned. It should deploy php
cartridge instead of tomcat.
On Wed, Feb 18, 2015 at 2:33 PM, Sajith Abeywardhana saji...@wso2.com
wrote:
Hi Udara,
Yes, Application refers to php cartilage, but stratos do have only
tomcat cartilage. I suggest your team to correct the document. In 4th
number curl command should execute the php.json file instead of tomcat.json
as you pointed out.
*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com mahe...@wso2.com | Web: www.wso2.com
On Wed, Feb 18, 2015 at 2:12 PM, Udara Liyanage ud...@wso2.com wrote:
Hi,
It seems the cartridge you refereed in your application is not added.
Can you share your artefacts.
On Wed, Feb 18, 2015 at 1:59 PM, Sajith Abeywardhana saji...@wso2.com
wrote:
Hi All,
I'm trying to deploy an application in PaaS 4.1.0 as for this
documentation [1]. When I execute the 5th number curl command I got the
below exception.
[1] -
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Single+Cartridge+on+Mock+IaaS
[2015-02-18 13:40:15,296] INFO
{org.apache.stratos.autoscaler.services.impl.AutoscalerServiceImpl} -
Adding application: [application-id] single-cartridge-app
[2015-02-18 13:40:15,361] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,361+0530]
[2015-02-18 13:40:15,391] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,391+0530]
[2015-02-18 13:40:15,405] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,405+0530]
[2015-02-18 13:40:15,432] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,432+0530]
[2015-02-18 13:40:15,461] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,461+0530]
[2015-02-18 13:40:16,097] ERROR
{org.apache.stratos.autoscaler.client.CloudControllerClient} -
CloudControllerServiceCartridgeNotFoundExceptionException
org.apache.stratos.cloud.controller.stub.CloudControllerServiceCartridgeNotFoundExceptionException:
CloudControllerServiceCartridgeNotFoundExceptionException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:357)
at java.lang.Class.newInstance(Class.java:310)
at
org.apache.stratos.cloud.controller.stub.CloudControllerServiceStub.getCartridgeInfo(CloudControllerServiceStub.java:4171)
at
org.apache.stratos.autoscaler.client.CloudControllerClient.getCartrdgeInformation(CloudControllerClient.java:316)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.getCartridge(DefaultApplicationParser.java:887)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.createClusterDataMap(DefaultApplicationParser.java:461)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.parseLeafLevelSubscriptions(DefaultApplicationParser.java:340)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.buildCompositeAppStructure(DefaultApplicationParser.java:299)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.parse(DefaultApplicationParser.java:104
Re: [Dev] [Stratos] CloudControllerServiceCartridgeNotFoundExceptionException when adding the application
This has been fixed in [1]. Thanks, for reporting!
[1] https://issues.apache.org/jira/browse/STRATOS-1198
Regards,
Mariangela
*--*
Mariangela Hills
Senior Technical Writer
*WSO2, Inc.*lean.enterprise.middleware.
m: +94 773 500185
w: http://wso2.com
http://wso2.com/events/
On Wed, Feb 18, 2015 at 2:34 PM, Udara Liyanage ud...@wso2.com wrote:
Hi Mari,
There was an mistake in the doc mentioned. It should deploy php cartridge
instead of tomcat.
On Wed, Feb 18, 2015 at 2:33 PM, Sajith Abeywardhana saji...@wso2.com
wrote:
Hi Udara,
Yes, Application refers to php cartilage, but stratos do have only tomcat
cartilage. I suggest your team to correct the document. In 4th number curl
command should execute the php.json file instead of tomcat.json as
you pointed out.
*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com mahe...@wso2.com | Web: www.wso2.com
On Wed, Feb 18, 2015 at 2:12 PM, Udara Liyanage ud...@wso2.com wrote:
Hi,
It seems the cartridge you refereed in your application is not added.
Can you share your artefacts.
On Wed, Feb 18, 2015 at 1:59 PM, Sajith Abeywardhana saji...@wso2.com
wrote:
Hi All,
I'm trying to deploy an application in PaaS 4.1.0 as for this
documentation [1]. When I execute the 5th number curl command I got the
below exception.
[1] -
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Single+Cartridge+on+Mock+IaaS
[2015-02-18 13:40:15,296] INFO
{org.apache.stratos.autoscaler.services.impl.AutoscalerServiceImpl} -
Adding application: [application-id] single-cartridge-app
[2015-02-18 13:40:15,361] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,361+0530]
[2015-02-18 13:40:15,391] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,391+0530]
[2015-02-18 13:40:15,405] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,405+0530]
[2015-02-18 13:40:15,432] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,432+0530]
[2015-02-18 13:40:15,461] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2015-02-18
13:40:15,461+0530]
[2015-02-18 13:40:16,097] ERROR
{org.apache.stratos.autoscaler.client.CloudControllerClient} -
CloudControllerServiceCartridgeNotFoundExceptionException
org.apache.stratos.cloud.controller.stub.CloudControllerServiceCartridgeNotFoundExceptionException:
CloudControllerServiceCartridgeNotFoundExceptionException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:357)
at java.lang.Class.newInstance(Class.java:310)
at
org.apache.stratos.cloud.controller.stub.CloudControllerServiceStub.getCartridgeInfo(CloudControllerServiceStub.java:4171)
at
org.apache.stratos.autoscaler.client.CloudControllerClient.getCartrdgeInformation(CloudControllerClient.java:316)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.getCartridge(DefaultApplicationParser.java:887)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.createClusterDataMap(DefaultApplicationParser.java:461)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.parseLeafLevelSubscriptions(DefaultApplicationParser.java:340)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.buildCompositeAppStructure(DefaultApplicationParser.java:299)
at
org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParser.parse(DefaultApplicationParser.java:104)
at
org.apache.stratos.autoscaler.services.impl.AutoscalerServiceImpl.addApplication(AutoscalerServiceImpl.java:202)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive
Re: [Dev] A doubt in one of the field names in Add Policy of EMM
I will look into this! Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com http://wso2.com/events/ On Fri, Oct 31, 2014 at 1:54 PM, Chathura Dilan chathu...@wso2.com wrote: I think documentation need to be updated On Tue, Oct 28, 2014 at 5:43 PM, Pasanthi Amarasekera pasan...@wso2.com wrote: Hi, In Operation Restrictions of Add Policy in EMM, what is meant by Change Screen Lock Passcode field ? In documentation ( https://docs.wso2.com/display/EMM110/EMM+Policy+Settings) it says The end-user's device passcode lock will be automatically cleared. But this doesn't give a clear idea on what to enter there when creating the policy. Thank you. Regards, Pasanthi. -- Pasanthi Amarasekera WSO2 Inc: http://wso2.com lean.enterprise.middleware Mobile: +94 77 9541735 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Chatura Dilan Perera *(Senior Software Engineer** - WSO2 Inc.* * [Mobile])* www.dilan.me ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB build error
Hi Trishan, Praneesha, has raised a JIRA [1] in this regard and we are in the process of updating the docs. [1] https://wso2.org/jira/browse/DOCUMENTATION-1104 Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com http://wso2.com/events/ On Thu, Oct 9, 2014 at 1:05 PM, Tishan Dahanayakage tis...@wso2.com wrote: Hi all, Sorry. I hit enter accidentally. Appending to previous mail. [2] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/ On Thu, Oct 9, 2014 at 1:02 PM, Tishan Dahanayakage tis...@wso2.com wrote: Hi Chamin, I assume you checked out the source for chunk 04. (eg:svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk04 local-platform-directory-2) Before start building particular product in the chunk make sure you have build all respective kernel patches. Refer [1] to know what kernel patches need to be build for a given chunk. You can checkout kernel patches from here[2]. For your case you should build patch 001 and 002. After that try building from chunk. It should work. @Documentation However relevant documentation need to be upgraded mentioning that users need to build kernel patches also. Praneesha fixed this in CEP documentation. That change should reflect upon every product documentation under chunk releases. [1] http://wso2.com/products/carbon/release-matrix/ On Thu, Oct 9, 2014 at 12:09 PM, Chamin Nalinda cha...@wso2.com wrote: Hi Ranwala, location is : product-releases/chunk-04/products/pom.xml here's the error stack (some artifacts are missing) start [INFO] [INFO] [INFO] Building WSO2 ESB - Samples 4.8.1 [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] WSO2 ESB - Aggregator Module .. SUCCESS [0.367s] [INFO] WSO2 ESB - Styles Parent .. SUCCESS [0.010s] [INFO] WSO2 ESB - Styles . SUCCESS [1.668s] [INFO] WSO2 Stratos ESB - Styles . SUCCESS [0.232s] [INFO] WSO2 ESB - Samples Parent . SUCCESS [0.010s] [INFO] WSO2 ESB - Samples FAILURE [1.185s] [INFO] WSO2 Stratos ESB - Samples SKIPPED [INFO] WSO2 ESB - Features Parent SKIPPED [INFO] WSO2 ESB - Features Aggregator Module . SKIPPED [INFO] WSO2 ESB - Styles Features SKIPPED [INFO] WSO2 ESB - Samples Features ... SKIPPED [INFO] WSO2 Stratos ESB - Login User Interface ... SKIPPED [INFO] WSO2 Stratos ESB - Features Aggregator Module . SKIPPED [INFO] WSO2 Stratos ESB - Login UI Feature ... SKIPPED [INFO] WSO2 Stratos ESB - Styles Features SKIPPED [INFO] WSO2 Stratos ESB - Samples Features ... SKIPPED [INFO] WSO2 ESB - P2 Profile Generation .. SKIPPED [INFO] WSO2 ESB - Distribution ... SKIPPED [INFO] WSO2 ESB - Integration Parent . SKIPPED [INFO] ESB Test Service Module ... SKIPPED [INFO] Integration Commons Module - ESB test Module .. SKIPPED [INFO] WSO2 ESB Integration Test Core SKIPPED [INFO] ESB Mediators Test Module - 1 . SKIPPED [INFO] ESB Mediators Test Module - 2 . SKIPPED [INFO] ESB test Module - Sample .. SKIPPED [INFO] ESB test Module-Transport . SKIPPED [INFO] ESB test Module-Other . SKIPPED [INFO] ESB test Module-Service ... SKIPPED [INFO] ESB UI Test Module SKIPPED [INFO] Integration Test Reporting SKIPPED [INFO] WSO2 Carbon - Releases - products - Aggregator Module SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.050s [INFO] Finished at: Thu Oct 09 12:00:05 IST 2014 [INFO] Final Memory: 19M/736M [INFO] [ERROR] Failed to execute goal on project org.wso2.esb.samples: Could not resolve dependencies for project org.wso2.esb:org.wso2.esb.samples:bundle:4.8.1: Failed to collect dependencies for [org.apache.synapse:synapse-core:jar:2.1.2-wso2v1 (compile), org.apache.synapse:synapse-commons:jar:2.1.2-wso2v1 (compile), org.apache.ws.security.wso2:wss4j:jar:1.5.11.wso2v3 (compile), org.apache.rampart.wso2
Re: [Dev] ESB build error
Hi Tishan, Praneesha, has raised a JIRA [1] in this regard and we are in the process of updating the docs. [1] https://wso2.org/jira/browse/DOCUMENTATION-1104 Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com http://wso2.com/events/ On Thu, Oct 9, 2014 at 1:34 PM, Mariangela Hills mariang...@wso2.com wrote: Hi Trishan, Praneesha, has raised a JIRA [1] in this regard and we are in the process of updating the docs. [1] https://wso2.org/jira/browse/DOCUMENTATION-1104 Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com http://wso2.com/events/ On Thu, Oct 9, 2014 at 1:05 PM, Tishan Dahanayakage tis...@wso2.com wrote: Hi all, Sorry. I hit enter accidentally. Appending to previous mail. [2] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/ On Thu, Oct 9, 2014 at 1:02 PM, Tishan Dahanayakage tis...@wso2.com wrote: Hi Chamin, I assume you checked out the source for chunk 04. (eg:svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk04 local-platform-directory-2) Before start building particular product in the chunk make sure you have build all respective kernel patches. Refer [1] to know what kernel patches need to be build for a given chunk. You can checkout kernel patches from here[2]. For your case you should build patch 001 and 002. After that try building from chunk. It should work. @Documentation However relevant documentation need to be upgraded mentioning that users need to build kernel patches also. Praneesha fixed this in CEP documentation. That change should reflect upon every product documentation under chunk releases. [1] http://wso2.com/products/carbon/release-matrix/ On Thu, Oct 9, 2014 at 12:09 PM, Chamin Nalinda cha...@wso2.com wrote: Hi Ranwala, location is : product-releases/chunk-04/products/pom.xml here's the error stack (some artifacts are missing) start [INFO] [INFO] [INFO] Building WSO2 ESB - Samples 4.8.1 [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] WSO2 ESB - Aggregator Module .. SUCCESS [0.367s] [INFO] WSO2 ESB - Styles Parent .. SUCCESS [0.010s] [INFO] WSO2 ESB - Styles . SUCCESS [1.668s] [INFO] WSO2 Stratos ESB - Styles . SUCCESS [0.232s] [INFO] WSO2 ESB - Samples Parent . SUCCESS [0.010s] [INFO] WSO2 ESB - Samples FAILURE [1.185s] [INFO] WSO2 Stratos ESB - Samples SKIPPED [INFO] WSO2 ESB - Features Parent SKIPPED [INFO] WSO2 ESB - Features Aggregator Module . SKIPPED [INFO] WSO2 ESB - Styles Features SKIPPED [INFO] WSO2 ESB - Samples Features ... SKIPPED [INFO] WSO2 Stratos ESB - Login User Interface ... SKIPPED [INFO] WSO2 Stratos ESB - Features Aggregator Module . SKIPPED [INFO] WSO2 Stratos ESB - Login UI Feature ... SKIPPED [INFO] WSO2 Stratos ESB - Styles Features SKIPPED [INFO] WSO2 Stratos ESB - Samples Features ... SKIPPED [INFO] WSO2 ESB - P2 Profile Generation .. SKIPPED [INFO] WSO2 ESB - Distribution ... SKIPPED [INFO] WSO2 ESB - Integration Parent . SKIPPED [INFO] ESB Test Service Module ... SKIPPED [INFO] Integration Commons Module - ESB test Module .. SKIPPED [INFO] WSO2 ESB Integration Test Core SKIPPED [INFO] ESB Mediators Test Module - 1 . SKIPPED [INFO] ESB Mediators Test Module - 2 . SKIPPED [INFO] ESB test Module - Sample .. SKIPPED [INFO] ESB test Module-Transport . SKIPPED [INFO] ESB test Module-Other . SKIPPED [INFO] ESB test Module-Service ... SKIPPED [INFO] ESB UI Test Module SKIPPED [INFO] Integration Test Reporting SKIPPED [INFO] WSO2 Carbon - Releases - products - Aggregator Module SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.050s [INFO] Finished at: Thu Oct 09 12:00:05 IST 2014 [INFO] Final Memory: 19M/736M [INFO
Re: [Dev] WSO2 Committers += Waruna Perera
Congratulations Waruna! Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc. *lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com http://wso2.com/events/ On Fri, Aug 1, 2014 at 1:22 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi all, It's my distinct pleasure to welcome Waruna Perera as a WSO2 Committer. He has been a valuable contributor for test automation and WSO2 product platform. In acknowledgement of his contributions, he's been voted as a WSO2 Committer. Welcome aboard and keep up the good work! Thanks, Krishantha. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ 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
