Re: [Dev] [AF] Fixing uploadable jaggery applications issue

[Anuruddha Premalal]

Hi Manjula,

Thing is root context ("/") for appmgt is appmgt folder itself. So if we
give a relative path   like "*/mnt/10.100.100.5/appfactory/wso2appfactory/tmp
*", it'll try to create
the folder inside "*appmgt/mnt/10.100.100.5/appfactory/wso2appfactory/tmp
"*


On Wed, Jan 14, 2015 at 11:47 AM, Manjula Rathnayake 
wrote:

> Hi Anuruddha,
>
> On Wed, Jan 14, 2015 at 11:28 AM, Anuruddha Premalal 
> wrote:
>
>> Hi,
>>
>> Due to security reasons it's not possible to perform file operations
>> outside the web root context, so we can't store uploaded applications to
>> CARBON_HOME/tmp.
>>
> What are security issues we face? is it because end user upload the file
> directly to the CARBON_HOME/tmp? If this is done by a signed code, java
> security manager will validate and will not throw exceptions.
> Can you share the exceptions.
>
> thank you.
>
>>
>> Hence I'm trying the first option as the solution. OSGI fragment will
>> have a required bundle and it'll have the compenent.xml which needs to be
>> overridden.
>>
>> However there's an additional overhead of maintaining this fragment and
>> the fragment-dependency along with jaggery releases (cause of the version
>> changes).
>>
>> Regards,
>> Anuruddha.
>>
>>
>> On Tue, Jan 13, 2015 at 1:30 PM, Dimuthu Leelarathne 
>> wrote:
>>
>>>
>>>
>>> On Tue, Jan 13, 2015 at 12:49 PM, Anuruddha Premalal >> > wrote:
>>>
 Hi,

 Once we upload an application to appfactory it get stored temporally
 inside*
 wso2appfctory-2.1.0/repository/deployment/server/jaggeryapps/appmgt/tmp/tmpUploadedApps
 . * Notice that this location is inside jaggeryapps folder.

 Issue is if we upload a zip file it gets automatically deployed inside
 the uploaded location by the jaggerydeployer and it deletes the original
 uploaded zip.

 Initially following are the fixes that are going to try.

 * Try to override the jaggerydeployer component.xml file by writing an
 osgi fragment.
   - here component.xml file contains the information about the
 deployer. So we can  try overriding this xml and remove the zip file
 deploery.

 * Turn off hot deployment in axis2.xml
   - but this will cause issue in apptype and runtime hot deployment?


>>> * Upload the applicatoins to carbon_home/tmp location
  - This location is not visible to appmgt webapp home. Is there a way
 to pass the uploaded file to osgi back-end via jaggery?

>>>
>>> The fix is to copy the file into the temp location. And then reading the
>>> file from that location. Pass the file name is straight forward coding.
>>>
>>> thanks,
>>> dimuthu
>>>
>>>

 Appreciate your inputs in solving this issue [1].

 [1] https://wso2.org/jira/browse/APPFAC-2740

 Regards,
 --
 *Anuruddha Premalal*
 Software Eng. | WSO2 Inc.
 Mobile : +94710461070
 Web site : www.regilandvalley.com


>>>
>>>
>>> --
>>> Dimuthu Leelarathne
>>> Architect & Product Lead of App Factory
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: dimut...@wso2.com
>>> Mobile : 0773661935
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> *Anuruddha Premalal*
>> Software Eng. | WSO2 Inc.
>> Mobile : +94710461070
>> Web site : www.regilandvalley.com
>>
>>
>
>
> --
> Manjula Rathnayaka
> Software Engineer
> WSO2, Inc.
> Mobile:+94 77 743 1987
>



-- 
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [BAM] hive scripts error

[Yohanna Fernando]

Why do I get this error in the BAM console when I start BAM after
integrating BAM with APIM?


Hive history
file=/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/tmp/hive/root-querylogs/hive_job_log_yohanna_201501141226_253770516.txt

OK

OK

Total MapReduce jobs = 1

Launching Job 1 out of 1

Number of reduce tasks not specified. Estimated from input data size: 1

In order to change the average load for a reducer (in bytes):

  set hive.exec.reducers.bytes.per.reducer=

In order to limit the maximum number of reducers:

  set hive.exec.reducers.max=

In order to set a constant number of reducers:

  set mapred.reduce.tasks=

log4j:WARN No appenders could be found for logger
(org.apache.axiom.util.stax.dialect.StAXDialectDetector).

log4j:WARN Please initialize the log4j system properly.

Execution log at:
/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/repository/logs//wso2carbon.log

[2015-01-14 12:26:06,387]  WARN {org.apache.hadoop.mapred.JobClient} -  Use
GenericOptionsParser for parsing the arguments. Applications should
implement Tool for the same.

[2015-01-14 12:26:07,121]  WARN
{org.apache.hadoop.filecache.TrackerDistributedCacheManager} -  Cannot find
size and number of subdirectories of baseDir:
/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/tmp/hadoop/local/689832709

[2015-01-14 12:26:07,122]  WARN
{org.apache.hadoop.filecache.TrackerDistributedCacheManager} -  Cannot find
size and number of subdirectories of baseDir:
/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/tmp/hadoop/local/689832709

[2015-01-14 12:26:07,122]  WARN
{org.apache.hadoop.filecache.TrackerDistributedCacheManager} -  Cannot find
size and number of subdirectories of baseDir:
/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/tmp/hadoop/local/689832709

[2015-01-14 12:26:07,123]  WARN
{org.apache.hadoop.filecache.TrackerDistributedCacheManager} -  Cannot find
size and number of subdirectories of baseDir:
/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/tmp/hadoop/local/689832709

[2015-01-14 12:26:07,123]  WARN
{org.apache.hadoop.filecache.TrackerDistributedCacheManager} -  Cannot find
size and number of subdirectories of baseDir:
/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/tmp/hadoop/local/689832709

[2015-01-14 12:26:07,124]  WARN
{org.apache.hadoop.filecache.TrackerDistributedCacheManager} -  Cannot find
size and number of subdirectories of baseDir:
/Users/yohanna/Documents/Labs-Latest/wso2bam-2.5.0/tmp/hadoop/local/689832709

Job running in-process (local Hadoop)

Hadoop job information for null: number of mappers: 0; number of reducers: 0

2015-01-14 12:26:08,188 null map = 0%,  reduce = 0%

2015-01-14 12:26:11,193 null map = 100%,  reduce = 0%

2015-01-14 12:26:17,200 null map = 100%,  reduce = 100%

Ended Job = job_local_0001

Execution completed successfully

Mapred Local Task Succeeded . Convert the Join into MapJoin

OK

OK

-- 
Yohanna Fernando
Training Specialist
WSO2 Inc.
 http://wso2.com

E-mail: yoha...@wso2.com
Cell: +94779021159
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ES] Unable to create jquery related test cases using jaggery test framework

[Himasha Guruge]

Hi All,

I'm in the stage of testing an ES asset extension (chevron diagram editor)
, under both publisher and store. In .specs files initially I need to use
jquery related functions( create DOM elements) but then I'm given an error
of  $ undefined .

 With the help of Ayesha I downloaded the plugin jasmine-jquery and tried
adding references of jquery and jasmine-jqeury in ES/modules/jaggery-test/
module.xml.  It is still providing undefined error.I tried changing the
order of references but still the same result.What is the jasmine version
used in ES? According to [1] , it requires at least jasmine 2.0.

Is there any other way of testing an ES extension that has jquery related
methods?  Any insight/sample for this would be helpful.

[1] 
http://www.htmlgoodies.com/beyond/javascript/js-ref/testing-dom-events-using-jquery-and-jasmine-2.0.html


Thanks & Regards,

Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Automated Testing of Email Sending Functionality of EMM

[Dilan Udara Ariyaratne]

Hi Krishantha,

There is a problem on testing this email sending functionality using the UI
and Selenium.
This is because any error that occurs at the email sending level is not
reflected at the UI level.

What do you think?

Regards,
Dilan.


*Dilan U. Ariyaratne*
Software Engineer
WSO2 Inc. 
Mobile: +94775149066
lean . enterprise . middleware

On Tue, Jan 13, 2015 at 6:08 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Krisantha,
>
> Following are the manual steps of sending a mail to a user.
>
> [1] Fill email configuration details (SMTP Mail Server Settings) under the
> settings tab of admin console.
> [2] Add a new user to the system which will send an invitation email to
> the provided email address of the user.
>
> Herewith I am also attaching the screen-shots...
>
> Thanks.
>
>
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94775149066
> lean . enterprise . middleware
>
> On Tue, Jan 13, 2015 at 2:48 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Can you list the steps required to manually verify the scenario. We have
>> recently implemented GreenMail sever utility for test framework. We can
>> propose how to automate based on the manual steps.
>>
>> Thanks,
>> Krishantha.
>>
>> On Tue, Jan 13, 2015 at 9:14 AM, Inosh Perera  wrote:
>>
>>> Hi Krishantha,
>>> EMM 1.1.0 uses, require('email') available in Jaggery to send email.
>>> The configurations are stored in the registry. So it is not necessary to
>>> configure mail transport AFAIK.
>>> Adding the mobile team.
>>>
>>> Regards,
>>> Inosh
>>>
>>>
>>> On Mon, Jan 12, 2015 at 6:09 PM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
 Do you need to configure mail transport in this case ? if yes, in which
 file ?

 Thanks,
 Krishantha

 On Mon, Jan 12, 2015 at 3:40 PM, Dilan Udara Ariyaratne <
 dil...@wso2.com> wrote:

> Hi Folks,
>
> I am checking the feasibility of writing an automated test case for
> the email
> sending functionality of emm.
>
> When a user is created, an invitation email is sent to the
> corresponding
> user to register the device.
>
> sendEmail() is currently a jaggery function and is executed via a
> non-exposed api to the outside
> within EMM Jaggery web application.
>
> What is the best possible way to test this functionality?
> Is there a recommended SMTP mail server to use?
>
> If I am using Selenium, to verify "success", I need to capture the
> status message
> of a dialog popup. How can I do this using Selenium?
>
> Appreciate any feedback on this.
>
> Thanks.
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94775149066
> lean . enterprise . middleware
>



 --
 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


>>>
>>>
>>> --
>>> Inosh Perera
>>> Software Engineer, WSO2 Inc.
>>> Tel: 0785293686
>>>
>>
>>
>>
>> --
>> 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] Generating code coverage report for AF integration tests

[Amalka Subasinghe]

Hi all,

Currently I'm trying to $subject. Since AF integration tests runs in
platform mode, we can't generate code coverage report via our existing test
framework.

I found a blog we can use for this. [1]
as specified in the blog when I execute the xargs -n 1
$JAVA_HOME/jre/bin/java -cp emma.jar emma instr -m overwrite -cp <
jarlist.txt.
It changes file permissions on appfactory jars, because of that I can't up
the appfactory setup to run the tests.

Does anyone have ideas on how to do this?

[1]
http://charithaka.blogspot.com/2009/05/run-time-code-coverage-using-emma.html

Thanks
Amalka
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SFTP server backend for ESB integration tests

[Krishantha Samaraweera]

Hi DimuthuD,

On Wed, Jan 14, 2015 at 10:23 AM, Dimuthu De Lanerolle 
wrote:

> We are keeping track of this issue and currently on-hold due to build
> failures in the ESB and will resume once the build is stabilized.
>

Can't we go ahead with older ESB pack and verify the scenario until ESB
team fix the build, What is the exact issue from test side ?

Thanks,
Krishantha.

>
> Regards
>
>
> On Wed, Jan 14, 2015 at 9:22 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi Dimuthu,
>>
>> Were you able to resolved the issue with SFTP server implementation.
>>
>> Can you please update up on progress made so far.
>>
>> Thanks,
>> Krishantha.
>>
>>
>> On Tue, Dec 23, 2014 at 5:23 PM, Dimuthu De Lanerolle 
>> wrote:
>>
>>> Hi ,
>>>
>>> We are working on the $Subject.
>>>
>>> We have completed the implementation of the SFTP server and have added a
>>> sample test case scenario using VFS transport to test the SFTP server
>>> feasibility. We noted that when both ESB and SFTP server instances are
>>> running separately Test case scenario works as expected,  however when we
>>> run the SFTP server instance through TAF , ESB fails to perform the VFS
>>> file transfer scenario. We are currently working on solving this issue.
>>>
>>> Regards
>>> --
>>> Dimuthu De Lanerolle
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middlewear.
>>> http://wso2.com/
>>> Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>
>
>
> --
> Dimuthu De Lanerolle
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middlewear.
> http://wso2.com/
> Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
>
>


-- 
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

Re: [Dev] [AF] Fixing uploadable jaggery applications issue

[Manjula Rathnayake]

Hi Anuruddha,

On Wed, Jan 14, 2015 at 11:28 AM, Anuruddha Premalal 
wrote:

> Hi,
>
> Due to security reasons it's not possible to perform file operations
> outside the web root context, so we can't store uploaded applications to
> CARBON_HOME/tmp.
>
What are security issues we face? is it because end user upload the file
directly to the CARBON_HOME/tmp? If this is done by a signed code, java
security manager will validate and will not throw exceptions.
Can you share the exceptions.

thank you.

>
> Hence I'm trying the first option as the solution. OSGI fragment will have
> a required bundle and it'll have the compenent.xml which needs to be
> overridden.
>
> However there's an additional overhead of maintaining this fragment and
> the fragment-dependency along with jaggery releases (cause of the version
> changes).
>
> Regards,
> Anuruddha.
>
>
> On Tue, Jan 13, 2015 at 1:30 PM, Dimuthu Leelarathne 
> wrote:
>
>>
>>
>> On Tue, Jan 13, 2015 at 12:49 PM, Anuruddha Premalal 
>> wrote:
>>
>>> Hi,
>>>
>>> Once we upload an application to appfactory it get stored temporally
>>> inside*
>>> wso2appfctory-2.1.0/repository/deployment/server/jaggeryapps/appmgt/tmp/tmpUploadedApps
>>> . * Notice that this location is inside jaggeryapps folder.
>>>
>>> Issue is if we upload a zip file it gets automatically deployed inside
>>> the uploaded location by the jaggerydeployer and it deletes the original
>>> uploaded zip.
>>>
>>> Initially following are the fixes that are going to try.
>>>
>>> * Try to override the jaggerydeployer component.xml file by writing an
>>> osgi fragment.
>>>   - here component.xml file contains the information about the deployer.
>>> So we can  try overriding this xml and remove the zip file deploery.
>>>
>>> * Turn off hot deployment in axis2.xml
>>>   - but this will cause issue in apptype and runtime hot deployment?
>>>
>>>
>> * Upload the applicatoins to carbon_home/tmp location
>>>  - This location is not visible to appmgt webapp home. Is there a way to
>>> pass the uploaded file to osgi back-end via jaggery?
>>>
>>
>> The fix is to copy the file into the temp location. And then reading the
>> file from that location. Pass the file name is straight forward coding.
>>
>> thanks,
>> dimuthu
>>
>>
>>>
>>> Appreciate your inputs in solving this issue [1].
>>>
>>> [1] https://wso2.org/jira/browse/APPFAC-2740
>>>
>>> Regards,
>>> --
>>> *Anuruddha Premalal*
>>> Software Eng. | WSO2 Inc.
>>> Mobile : +94710461070
>>> Web site : www.regilandvalley.com
>>>
>>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Architect & Product Lead of App Factory
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>> Mobile : 0773661935
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> *Anuruddha Premalal*
> Software Eng. | WSO2 Inc.
> Mobile : +94710461070
> Web site : www.regilandvalley.com
>
>


-- 
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please cancel......

[Vanjikumaran Sivajothy]

Hi Bob,

If you wish to unsubscribe, Please flow the instruction given in [1]


[1]http://wso2.com/mail/

On Wed, Jan 14, 2015 at 9:11 AM, Bob Carson  wrote:

>
>
> Robert R. Carson
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
[image: Facebook]  [image: Twitter]
 [image: LinkedIn]
 [image:
Blogger]  [image: SlideShare]


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, re-transmit, 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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can't use registry checkin-client with DevStudio to commit changes to the registry

[Susankha Nirmala]

After Debug I can see registry URL, username and password set as expected.
But the problem is when accessing

* System.getProperty("carbon.home")*  and
* 
ServerConfiguration.getInstance().getFirstProperty("Axis2Config.clientAxis2XmlLocation")*

Within *newRegistry *in *ClientUtils.java *class, both return NULL.



On Wed, Jan 14, 2015 at 11:04 AM, Chandana Napagoda 
wrote:

> Hi Susankha,
>
> If you have registry URL, username and password, you can access the
> registry using RemoteRegistry. You can refer this sample[1] as well.
>
> [1].
> https://docs.wso2.com/display/Governance452/Exporting+and+Importing+a+File+to+Remote+Registry
>
> Regards,
> Chandana
>
> On Wed, Jan 14, 2015 at 10:49 AM, Pulasthi Supun 
> wrote:
>
>> [Adding Sameerak]
>>
>> On Wed, Jan 14, 2015 at 10:47 AM, Susankha Nirmala 
>> wrote:
>>
>>> Adding Azeez
>>>
>>> On Wed, Jan 14, 2015 at 10:34 AM, Susankha Nirmala 
>>> wrote:
>>>
 Hi All,

 We are using checkin-client jar with DevStudio to commit changes to the
 registry. But within checkin-client,. it is used "carbon.home" property
 and "Axis2Config.clientAxis2XmlLocation" property like below.

 ClientUtils.java
 

  ConfigurationContext context =
 ConfigurationContextFactory

 .createConfigurationContextFromFileSystem(
*
 System.getProperty("carbon.home")* +
 File.separator
 + "repository" +
 File.separator +
 "deployment" +
 File.separator + "client",

 *ServerConfiguration.getInstance().getFirstProperty("Axis2Config.clientAxis2XmlLocation")*
 );

 But within devStudio context, we can't access "carbon.home" property
 and "Axis2Config.clientAxis2XmlLocation" property( both properties are
 return null within devStudio context).
 Is there a way to set those properties within devStudio context?




 --
 Susankha Nirmala
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 Mobile : +94 77 593 2146t

>>>
>>>
>>>
>>> --
>>> Susankha Nirmala
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>> Mobile : +94 77 593 2146
>>>
>>
>>
>>
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>
>
>
> --
> *Chandana Napagoda*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com *
>
>


-- 
Susankha Nirmala
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
Mobile : +94 77 593 2146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] PizzaShack Sample: List of Pizzas not loaded in web application

[Yohanna Fernando]

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
SOAP-ENV:mustUnderstand="1">



yourn...@t-online.de

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText
">yourPassword





Unexpected character (<) at position 0.

at org.json.simple.parser.Yylex.yylex(Unknown Source)

at org.json.simple.parser.JSONParser.nextToken(Unknown Source)

at org.json.simple.parser.JSONParser.parse(Unknown Source)

at org.json.simple.parser.JSONParser.parse(Unknown Source)

at org.json.simple.parser.JSONParser.parse(Unknown Source)

at
com.pizzashack.client.web.JSONClient.getAvailablePizzaList(JSONClient.java:75)

at
com.pizzashack.client.web.MenuItemManager.getAvailablePizzaList(MenuItemManager.java:28)

at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:120)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)

at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)

at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)

at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)

at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)

at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)

at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)

at
org.wso2.carbon.statistics.webapp.RequestIntercepterValve.invoke(RequestIntercepterValve.java:43)

at
org.wso2.carbon.bam.webapp.stat.publisher.WebAppStatisticPublisherValve.invoke(WebAppStatisticPublisherValve.java:104)

at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)

at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)

at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)

at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)

at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)

at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)

at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)

at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)

at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)

at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)

at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)

at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:745)

On Wed, Jan 14, 2015 at 8:13 AM, Dinesh J Weerakkody 
wrote:

> Hi Yohanna,
>
> Do you have any error logs in your console?
>
> Thanks
>
> *Dinesh J. Weerakkody*
> Software Engineer
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 727 361788 | E : dine...@wso2.com | W : www.wso2.com
>
> On Tue, Jan 13, 2015 at 5:41 PM, Yohanna Fernando 
> wrote:
>
>>
>> As shown in diagram, the lists of pizzas are not loaded and I don't get
>> the screen which says:
>>
>> "This App will be able to"
>>
>> Has anyone come across this before and know if I'm missing something?
>> --
>> Yohanna Fernando
>> Training Specialist
>> WSO2 Inc.
>>  http://wso2.com
>>
>> E-mail: yoha...@wso2.com
>> Cell: +94779021159
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Yohanna Fernando
Training Specialist
WSO2 Inc.
 http://wso2.com

E-mail: yoha...@wso2.com
Cell: +94779021159

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Fixing uploadable jaggery applications issue

[Anuruddha Premalal]

Hi,

Due to security reasons it's not possible to perform file operations
outside the web root context, so we can't store uploaded applications to
CARBON_HOME/tmp.

Hence I'm trying the first option as the solution. OSGI fragment will have
a required bundle and it'll have the compenent.xml which needs to be
overridden.

However there's an additional overhead of maintaining this fragment and the
fragment-dependency along with jaggery releases (cause of the version
changes).

Regards,
Anuruddha.


On Tue, Jan 13, 2015 at 1:30 PM, Dimuthu Leelarathne 
wrote:

>
>
> On Tue, Jan 13, 2015 at 12:49 PM, Anuruddha Premalal 
> wrote:
>
>> Hi,
>>
>> Once we upload an application to appfactory it get stored temporally
>> inside*
>> wso2appfctory-2.1.0/repository/deployment/server/jaggeryapps/appmgt/tmp/tmpUploadedApps
>> . * Notice that this location is inside jaggeryapps folder.
>>
>> Issue is if we upload a zip file it gets automatically deployed inside
>> the uploaded location by the jaggerydeployer and it deletes the original
>> uploaded zip.
>>
>> Initially following are the fixes that are going to try.
>>
>> * Try to override the jaggerydeployer component.xml file by writing an
>> osgi fragment.
>>   - here component.xml file contains the information about the deployer.
>> So we can  try overriding this xml and remove the zip file deploery.
>>
>> * Turn off hot deployment in axis2.xml
>>   - but this will cause issue in apptype and runtime hot deployment?
>>
>>
> * Upload the applicatoins to carbon_home/tmp location
>>  - This location is not visible to appmgt webapp home. Is there a way to
>> pass the uploaded file to osgi back-end via jaggery?
>>
>
> The fix is to copy the file into the temp location. And then reading the
> file from that location. Pass the file name is straight forward coding.
>
> thanks,
> dimuthu
>
>
>>
>> Appreciate your inputs in solving this issue [1].
>>
>> [1] https://wso2.org/jira/browse/APPFAC-2740
>>
>> Regards,
>> --
>> *Anuruddha Premalal*
>> Software Eng. | WSO2 Inc.
>> Mobile : +94710461070
>> Web site : www.regilandvalley.com
>>
>>
>
>
> --
> Dimuthu Leelarathne
> Architect & Product Lead of App Factory
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Carbon - Registry Resource Properties Feature installation fails in IS Server P2 profile

[Hasintha Indrajee]

Hi all,

Please note $subject. Refer the following trace for the error message
logged.

Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - Registry Resource Properties
Feature 4.3.0.SNAPSHOT
(org.wso2.carbon.registry.resource.properties.feature.group 4.3.0.SNAPSHOT)
 Missing requirement: org.wso2.carbon.registry.admin.api 4.3.0.SNAPSHOT
(org.wso2.carbon.registry.admin.api 4.3.0.SNAPSHOT) requires 'package
javax.xml.namespace 0.0.0' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Registry Core Common Feature 4.3.0.SNAPSHOT
(org.wso2.carbon.registry.core.common.feature.group 4.3.0.SNAPSHOT)
  To: org.wso2.carbon.registry.admin.api [4.3.0.SNAPSHOT]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Registry Resource Properties Feature 4.3.0.SNAPSHOT
(org.wso2.carbon.registry.resource.properties.feature.group 4.3.0.SNAPSHOT)
  To: org.wso2.carbon.registry.core.common.feature.group
[4.3.0.SNAPSHOT,4.4.0)
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can't use registry checkin-client with DevStudio to commit changes to the registry

[Chandana Napagoda]

Hi Susankha,

If you have registry URL, username and password, you can access the
registry using RemoteRegistry. You can refer this sample[1] as well.

[1].
https://docs.wso2.com/display/Governance452/Exporting+and+Importing+a+File+to+Remote+Registry

Regards,
Chandana

On Wed, Jan 14, 2015 at 10:49 AM, Pulasthi Supun  wrote:

> [Adding Sameerak]
>
> On Wed, Jan 14, 2015 at 10:47 AM, Susankha Nirmala 
> wrote:
>
>> Adding Azeez
>>
>> On Wed, Jan 14, 2015 at 10:34 AM, Susankha Nirmala 
>> wrote:
>>
>>> Hi All,
>>>
>>> We are using checkin-client jar with DevStudio to commit changes to the
>>> registry. But within checkin-client,. it is used "carbon.home" property
>>> and "Axis2Config.clientAxis2XmlLocation" property like below.
>>>
>>> ClientUtils.java
>>> 
>>>
>>>  ConfigurationContext context =
>>> ConfigurationContextFactory
>>>
>>> .createConfigurationContextFromFileSystem(
>>>*
>>> System.getProperty("carbon.home")* +
>>> File.separator +
>>> "repository" +
>>> File.separator +
>>> "deployment" +
>>> File.separator + "client",
>>>
>>> *ServerConfiguration.getInstance().getFirstProperty("Axis2Config.clientAxis2XmlLocation")*
>>> );
>>>
>>> But within devStudio context, we can't access "carbon.home" property and
>>> "Axis2Config.clientAxis2XmlLocation" property( both properties are return
>>> null within devStudio context).
>>> Is there a way to set those properties within devStudio context?
>>>
>>>
>>>
>>>
>>> --
>>> Susankha Nirmala
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>> Mobile : +94 77 593 2146t
>>>
>>
>>
>>
>> --
>> Susankha Nirmala
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> Mobile : +94 77 593 2146
>>
>
>
>
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>



-- 
*Chandana Napagoda*
Senior Software Engineer
WSO2 Inc. - http://wso2.org

*Email  :  chand...@wso2.com **Mobile : +94718169299*

*Blog  :http://cnapagoda.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Design and implementation of ghost deployer test cases for WSO2AS

[Saneth Dharmakeerthi]

Hi Krishantha,

Implemented the  web-app as REST service  and as a Servlet  to get the
tenant load/unload information. But in both approaches, it is not retuning
the correct information.  I am currently  finding a solution for that.
Also start to write the test cases without the verification part.
Verification part needs to be added after solving the problems in the
web-app. We may have to use LogViewerClient  if the web-app approach will
not work.



Thanks and Best Regards,

Saneth Dharmakeerthi
Senior Software Engineer
WSO2, Inc.
Mobile: +94772325511

On Wed, Jan 14, 2015 at 9:32 AM, Krishantha Samaraweera  wrote:

> Hi Saneth,
>
> Can you please update us on what is going on with Ghost deployer test case
> writing..
>
> Any blockers ?
>
> Thanks,
> Krishantha.
>
> On Tue, Jan 6, 2015 at 4:39 PM, Saneth Dharmakeerthi 
> wrote:
>
>> Hi All,
>>
>> I am working on $subject which will be track through JIRA TA-591
>> .
>> Ghoest deployer will be test on WSO2AS and test scenarios will be based
>> on this document
>> 
>>
>> New web-app will be  created  to provide the information about load and
>> unload status of tenats.
>> This web-app will be deployed before the test. Test integration layer can
>> access this web-app via REST call and get the necessary informations.
>>
>>
>>
>>
>> Thanks and Best Regards,
>>
>> Saneth Dharmakeerthi
>> Senior Software Engineer
>> WSO2, Inc.
>> Mobile: +94772325511
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> 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

Re: [Dev] Can't use registry checkin-client with DevStudio to commit changes to the registry

[Pulasthi Supun]

[Adding Sameerak]

On Wed, Jan 14, 2015 at 10:47 AM, Susankha Nirmala 
wrote:

> Adding Azeez
>
> On Wed, Jan 14, 2015 at 10:34 AM, Susankha Nirmala 
> wrote:
>
>> Hi All,
>>
>> We are using checkin-client jar with DevStudio to commit changes to the
>> registry. But within checkin-client,. it is used "carbon.home" property
>> and "Axis2Config.clientAxis2XmlLocation" property like below.
>>
>> ClientUtils.java
>> 
>>
>>  ConfigurationContext context =
>> ConfigurationContextFactory
>>
>> .createConfigurationContextFromFileSystem(
>>*
>> System.getProperty("carbon.home")* +
>> File.separator +
>> "repository" +
>> File.separator +
>> "deployment" +
>> File.separator + "client",
>>
>> *ServerConfiguration.getInstance().getFirstProperty("Axis2Config.clientAxis2XmlLocation")*
>> );
>>
>> But within devStudio context, we can't access "carbon.home" property and
>> "Axis2Config.clientAxis2XmlLocation" property( both properties are return
>> null within devStudio context).
>> Is there a way to set those properties within devStudio context?
>>
>>
>>
>>
>> --
>> Susankha Nirmala
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> Mobile : +94 77 593 2146t
>>
>
>
>
> --
> Susankha Nirmala
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> Mobile : +94 77 593 2146
>



-- 
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can't use registry checkin-client with DevStudio to commit changes to the registry

[Susankha Nirmala]

Adding Azeez

On Wed, Jan 14, 2015 at 10:34 AM, Susankha Nirmala 
wrote:

> Hi All,
>
> We are using checkin-client jar with DevStudio to commit changes to the
> registry. But within checkin-client,. it is used "carbon.home" property
> and "Axis2Config.clientAxis2XmlLocation" property like below.
>
> ClientUtils.java
> 
>
>  ConfigurationContext context =
> ConfigurationContextFactory
>
> .createConfigurationContextFromFileSystem(
>*
> System.getProperty("carbon.home")* +
> File.separator +
> "repository" +
> File.separator +
> "deployment" +
> File.separator + "client",
>
> *ServerConfiguration.getInstance().getFirstProperty("Axis2Config.clientAxis2XmlLocation")*
> );
>
> But within devStudio context, we can't access "carbon.home" property and
> "Axis2Config.clientAxis2XmlLocation" property( both properties are return
> null within devStudio context).
> Is there a way to set those properties within devStudio context?
>
>
>
>
> --
> Susankha Nirmala
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> Mobile : +94 77 593 2146t
>



-- 
Susankha Nirmala
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
Mobile : +94 77 593 2146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Please merge the Pull Request for ESBJAVA-3137

[Senduran Balasubramaniyam]

Hi,

Please merge the Pull Request [1] for JIRA [2]

[1] https://github.com/wso2-dev/wso2-synapse/pull/191
[2] https://wso2.org/jira/browse/ESBJAVA-3137

Thanks
Senduran

-- 
*Senduran *
Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Can't use registry checkin-client with DevStudio to commit changes to the registry

[Susankha Nirmala]

Hi All,

We are using checkin-client jar with DevStudio to commit changes to the
registry. But within checkin-client,. it is used "carbon.home" property
and "Axis2Config.clientAxis2XmlLocation" property like below.

ClientUtils.java


 ConfigurationContext context =
ConfigurationContextFactory

.createConfigurationContextFromFileSystem(
   *
System.getProperty("carbon.home")* +
File.separator +
"repository" +
File.separator +
"deployment" +
File.separator + "client",

*ServerConfiguration.getInstance().getFirstProperty("Axis2Config.clientAxis2XmlLocation")*
);

But within devStudio context, we can't access "carbon.home" property and
"Axis2Config.clientAxis2XmlLocation" property( both properties are return
null within devStudio context).
Is there a way to set those properties within devStudio context?




-- 
Susankha Nirmala
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
Mobile : +94 77 593 2146t
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Payload mediation of JSON message using Script Mediator

[Shakila Sivagnanarajah]

Please try this configuration with this request:
curl -X POST -d "{\"origin\":\"202.37.75.130\"}" -H "Content-Type:
application/json" 

http://ws.apache.org/ns/synapse"; name="test"
context="/testScriptMediator">
   
  
 
  
  
 

   {
  "origin":"$1"
  }
  

   

 
 
var payload = mc.getPayloadJSON();
payload["IP_Address"] = payload["origin"];
delete payload.origin;
mc.setPayloadJSON(payload);

 
  
   


On Fri, Jan 9, 2015 at 11:07 AM, Keerthika Mahendralingam <
keerth...@wso2.com> wrote:

> Hi Maz,
>
> You can use payload factory mediator to mediate the payload of the message.
>
> I tried as follows. It worked for me:
>
> 
>   
>  
> 
>  
>  
> 
>{ "IP_Address": "$1"}
>
>   
>
> 
> 
>  
>   
>
>
> Request:
>
> curl -X POST -d "{\"origin\":\"202.37.75.130\"}" -H "Content-Type:
> application/json" http://192.168.0.102:8280/test
>
> Response:
>
> { "IP_Address": "202.37.75.130"}
>
>
> Thank you,
>
> On Thu, Jan 8, 2015 at 4:43 PM, Buddhima Wijeweera 
> wrote:
>
>> Hi Maz,
>>
>> There's a problem with the JS script. It should be like follows:
>>
>>  var older = mc.getPayloadJSON(); var
>> newer={"IP_Address":older['origin']}; mc.setPayloadJSON(newer);
>>
>>
>> I tried the following API (with ESB 4.8.1) to make the situation quite
>> similar to yours :
>>
>> 
>>   
>>  
>> 
>>
>> 
>> 
>>  
>>  
>> 
>>
>> 
>> var older = mc.getPayloadJSON();var
>> newer={"IP_Address":older['origin']};mc.setPayloadJSON(newer);
>> 
>>  
>>   
>>
>>
>>
>> Following image shows the request and the response:
>>
>>
>> ​
>>
>>
>>
>> For your reference I would like to point out following link:
>> http://www.w3schools.com/js/js_json.asp
>>
>> Thank You!
>>
>>
>>
>> On Thu, Jan 8, 2015 at 12:47 PM, Malaka Silva  wrote:
>>
>>> Hi Maz,
>>>
>>> Since you need to generate payload dynamically you can use script
>>> mediator for that purpose.
>>>
>>> On Thu, Jan 8, 2015 at 12:23 AM, Maz Lakadia 
>>> wrote:
>>>
 I will be mapping resources that are in a particular format into
 another format. This means I will have a lot of template mappings that I
 could load into script mediator and let it use the appropriate one for the
 task. I am unsure of how I could do that will payload factory mediator. Do
 you have any clues?

 --
 Date: Wed, 7 Jan 2015 09:07:13 +0530
 Subject: Re: [Dev] Payload mediation of JSON message using Script
 Mediator
 From: va...@wso2.com
 To: awanth...@wso2.com
 CC: mlaka...@hotmail.com; dev@wso2.org


 What is the real motivation you to use script mediator instead of
 payload factory?

 You can easly construct jaon payload with payload factory

 On Wednesday, January 7, 2015, Awanthika Senarath 
 wrote:

 Hi Maz,

 Can you follow the format at [1] and see whether it works? This
 explains the sample 351 in ESB.

 [1]
 https://docs.wso2.com/display/ESB480/Sample+351%3A+Inline+script+mediation+with+JavaScript
 

 On Wed, Jan 7, 2015 at 4:03 AM, Maz Lakadia 
 wrote:

 Hi, I'm using script mediator to mediate the response payload from my
 server. The unmediated response is:

 {"origin":"202.37.75.130"}

 I then add in a mediator via source code, that should change "origin"
 to "IP_Address":

 
 
 
 
 >>> expression="get-property('CORS_ORIGIN')" scope="transport"/>
 >>> value="Assertion,X-Jwt-Assertion,X-User-Name,X-User-Domain"
 scope="transport"/>
 
 
 
 

 However, my response remains unchanged (same as the unmediated
 response). I do not know how I can fix this. Is there an error I am making?

 Thanks,
 Maz

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791




 --
 Sent from Gmail Mobile

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/c

[Dev] [ES] Build fails giving compilation errors.

[Ayesha Dissanayaka]

Hi all,

ES local build also fails giving below compilation errors. It should be
after the changes made to carbon-governance in [1].

@Shazni: Can you please send a pull request to *wso2-dev.product-es* repo
adding necessory changes to ES source or advice how resolve those
compilation errors.

[1]
https://github.com/wso2-dev/carbon-governance/commit/3a3d244e9a67d6aaa7c027b8bd18f02f05905326

Thanks!
- Ayesha

-- Forwarded message --
From: 
Date: Wed, Jan 14, 2015 at 10:19 AM
Subject: Build failed in Jenkins: product-es » jaggery-scxml-executors #4848
To: buil...@wso2.org, ruch...@wso2.com, m...@wso2.com, ta...@wso2.com,
uda...@wso2.com, samee...@wso2.com, samee...@wso2.com, aye...@wso2.com,
man...@wso2.com


See <
https://wso2.org/jenkins/job/product-es/org.wso2.store$jaggery-scxml-executors/4848/
>

--
[...truncated 23 lines...]
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/carbon-parent/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/carbon-parent/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.ndatasource.common/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.ndatasource.common/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.ndatasource.common/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.utils/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.utils/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.utils/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.user.api/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.user.api/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.user.api/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.base/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.base/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.base/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.logging/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.logging/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.logging/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.bootstrap/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.bootstrap/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.bootstrap/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.queuing/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.queuing/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.queuing/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.securevault/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.securevault/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/org.wso2.carbon.securevault/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.registry.api/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.registry.api/4.3.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://maven.wso2

Re: [Dev] SFTP server backend for ESB integration tests

[Dimuthu De Lanerolle]

We are keeping track of this issue and currently on-hold due to build
failures in the ESB and will resume once the build is stabilized.

Regards

On Wed, Jan 14, 2015 at 9:22 AM, Krishantha Samaraweera  wrote:

> Hi Dimuthu,
>
> Were you able to resolved the issue with SFTP server implementation.
>
> Can you please update up on progress made so far.
>
> Thanks,
> Krishantha.
>
>
> On Tue, Dec 23, 2014 at 5:23 PM, Dimuthu De Lanerolle 
> wrote:
>
>> Hi ,
>>
>> We are working on the $Subject.
>>
>> We have completed the implementation of the SFTP server and have added a
>> sample test case scenario using VFS transport to test the SFTP server
>> feasibility. We noted that when both ESB and SFTP server instances are
>> running separately Test case scenario works as expected,  however when we
>> run the SFTP server instance through TAF , ESB fails to perform the VFS
>> file transfer scenario. We are currently working on solving this issue.
>>
>> Regards
>> --
>> Dimuthu De Lanerolle
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middlewear.
>> http://wso2.com/
>> Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>



-- 
Dimuthu De Lanerolle
Software Engineer
WSO2 Inc.
lean . enterprise . middlewear.
http://wso2.com/
Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Deploy APIs and Sequences in ATF runtime

[Dinesh J Weerakkody]

Thank you Krishantha. Found it in APIManagerIntegrationTest class.

Thanks

*Dinesh J. Weerakkody*
Software Engineer
WSO2 Inc.
lean | enterprise | middleware
M : +94 727 361788 | E : dine...@wso2.com | W : www.wso2.com

On Wed, Jan 14, 2015 at 9:46 AM, Krishantha Samaraweera  wrote:

> If your query is related to ESB, addAPI method in ESBIntegrationTest [1]
> base class can be used. The same class is there in APIM as well.
>
> [1]
> https://github.com/wso2-dev/product-esb/blob/master/modules/integration/test-common/integration-test-utils/src/main/java/org/wso2/esb/integration/common/utils/ESBIntegrationTest.java
>
> Thanks
> Krishantha.
>
> On Wed, Jan 14, 2015 at 9:26 AM, Dinesh J Weerakkody 
> wrote:
>
>> Hi,
>>
>> I want to deploy some API and sequence artifacts before start automation
>> test. Do we have something smiler to 
>> *serverConfigurationManager.applyConfiguration(fileName)
>> *method which we can use to deploy artifacts in runtime?
>>
>> Thanks
>>
>> *Dinesh J. Weerakkody*
>> Software Engineer
>> WSO2 Inc.
>> lean | enterprise | middleware
>> M : +94 727 361788 | E : dine...@wso2.com | W : www.wso2.com
>>
>
>
>
> --
> 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

Re: [Dev] How to enable security for a proxy service in Dev Studio

[Niranjan Karunanandham]

Thanks Susinda..

Regards,
Nira
On 13 Jan 2015 20:15, "Susinda Perera"  wrote:

> Hi Niranjan
>
> Currently there is no such option to do the same as in ESB management
> console. However you can achieve same by setting enableSec property to true
> and setting policy key. [1]
>
> [1] - https://docs.wso2.com/display/DVS371/Applying+QoS+for+a+Service
>
> We are developing this feature and will update once completed.
>
> Thanks
>
>
> On Wed, Jan 14, 2015 at 5:18 AM, Niranjan Karunanandham  > wrote:
>
>> Hi,
>>
>> Using the ESB console, we can create a simple unsecured proxy and enable
>> security using the QOS. For example: in the ESB console, I created a Pass
>> Through Proxy (say 'proxy1') and enabled "UsernameToken" security from
>> the QOS. ESB automatically creates the policy for this and saves it to the
>> registry at "
>> conf:/repository/axis2/service-groups/proxy1/services/proxy1/policies/UTOverTransport".
>>
>> In Developer Studio, can we enable the security for a proxy service?
>> i.e., is there an option where we can select the Security as "UsernameToken",
>> "Non-repudiation", etc... and the policy files are generated
>> automatically as it is done in the ESB console?
>>
>> Regards,
>> Nira
>>
>> --
>>
>> *Niranjan Karunanandham*
>> WSO2 Inc.: http://www.wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> Mobile:(+94)716049075
>
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Deploy APIs and Sequences in ATF runtime

[Krishantha Samaraweera]

If your query is related to ESB, addAPI method in ESBIntegrationTest [1]
base class can be used. The same class is there in APIM as well.

[1]
https://github.com/wso2-dev/product-esb/blob/master/modules/integration/test-common/integration-test-utils/src/main/java/org/wso2/esb/integration/common/utils/ESBIntegrationTest.java

Thanks
Krishantha.

On Wed, Jan 14, 2015 at 9:26 AM, Dinesh J Weerakkody 
wrote:

> Hi,
>
> I want to deploy some API and sequence artifacts before start automation
> test. Do we have something smiler to 
> *serverConfigurationManager.applyConfiguration(fileName)
> *method which we can use to deploy artifacts in runtime?
>
> Thanks
>
> *Dinesh J. Weerakkody*
> Software Engineer
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 727 361788 | E : dine...@wso2.com | W : www.wso2.com
>



-- 
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

Re: [Dev] How to enable security for a proxy service in Dev Studio

[Susinda Perera]

Hi Niranjan

Currently there is no such option to do the same as in ESB management
console. However you can achieve same by setting enableSec property to true
and setting policy key. [1]

[1] - https://docs.wso2.com/display/DVS371/Applying+QoS+for+a+Service

We are developing this feature and will update once completed.

Thanks


On Wed, Jan 14, 2015 at 5:18 AM, Niranjan Karunanandham 
wrote:

> Hi,
>
> Using the ESB console, we can create a simple unsecured proxy and enable
> security using the QOS. For example: in the ESB console, I created a Pass
> Through Proxy (say 'proxy1') and enabled "UsernameToken" security from
> the QOS. ESB automatically creates the policy for this and saves it to the
> registry at "
> conf:/repository/axis2/service-groups/proxy1/services/proxy1/policies/UTOverTransport".
>
> In Developer Studio, can we enable the security for a proxy service? i.e.,
> is there an option where we can select the Security as "UsernameToken", 
> "Non-repudiation",
> etc... and the policy files are generated automatically as it is done in
> the ESB console?
>
> Regards,
> Nira
>
> --
>
> *Niranjan Karunanandham*
> WSO2 Inc.: http://www.wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075

WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error in pom file

[Prabath Abeysekera]

On Wed, Jan 14, 2015 at 1:22 AM, Bhathiya Jayasekara 
wrote:

> Hi Pamod,
>
> I fixed this in wso2-dev. Please try with it now.
>
> @Prabath: Please sync wso2 repo. (carbon-storage-management repo)
>

Done.

Cheers,
Prabath


>
> Thanks,
> Bhathiya
>
> On Tue, Jan 13, 2015 at 9:52 PM, Pamod Sylvester  wrote:
>
>> Thanks for the help Sameera. The feature could be located under the
>> temporary directory created during feature extraction.
>>
>> 
>> > version="4.3.0.SNAPSHOT">
>>   This feature contains the bundles required for Cassandra
>> client
>>   %copyright
>>   %license
>>   
>>   > version="1.1.1.6"/>
>>   
>>   
>>   > version="4.3.0"/>
>>   
>>   
>>   > version="4.3.0"/>
>>   
>>   > version="4.3.0.SNAPSHOT"/>
>>   
>>   
>>* > version="0.0.0.${wso2_kernel_version}"/>*
>>   
>> 
>>
>> Thanks,
>> Pamod
>>
>> On Tue, Jan 13, 2015 at 7:14 PM, Sameera Jayasoma 
>> wrote:
>>
>>> Try this in your p2-profile-gen/target directory. This must be coming
>>> from features rather than plugins.
>>>
>>> On Tue, Jan 13, 2015 at 7:12 PM, Pamod Sylvester  wrote:
>>>
 Thanks Sameera. Tried it out. It doesn't show a manifest with the above
 string. Might be a different issue. The full log is the following

 Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 Format
 "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
 0.0.0.${wso2_kernel_version} java.lang.IllegalArgumentException: Format
 "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
 0.0.0.${wso2_kernel_version}

 Product publishing ended with the following exception:
 java.lang.IllegalArgumentException: Format
 "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
 0.0.0.${wso2_kernel_version}
 at
 org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275)
 at
 org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:89)
 at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79)
 at
 org.eclipse.equinox.p2.metadata.Version.parseVersion(Version.java:141)
 at
 org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.(FeatureEntry.java:63)
 at
 org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.createRequires(FeatureEntry.java:40)
 at
 org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.processImport(FeatureManifestParser.java:194)
 at
 org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.startElement(FeatureManifestParser.java:280)
 at
 com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
 at
 com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
 at
 com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
 at
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756)
 at
 com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
 at
 com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
 at
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
 at
 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
 at
 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
 at
 com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
 at
 com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
 at
 com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
 at
 org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.parse(FeatureManifestParser.java:126)
 at
 org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureParser.parse(FeatureParser.java:60)
 at
 org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.getFeatures(FeaturesAction.java:518)
 at
 org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.perform(FeaturesAction.java:604)
 at
 org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
 at
 org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1294)
 at
 org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
 at
 org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:283)
 at
 org.eclipse.equinox.

Re: [Dev] Design and implementation of ghost deployer test cases for WSO2AS

[Krishantha Samaraweera]

Hi Saneth,

Can you please update us on what is going on with Ghost deployer test case
writing..

Any blockers ?

Thanks,
Krishantha.

On Tue, Jan 6, 2015 at 4:39 PM, Saneth Dharmakeerthi 
wrote:

> Hi All,
>
> I am working on $subject which will be track through JIRA TA-591
> .
> Ghoest deployer will be test on WSO2AS and test scenarios will be based on 
> this
> document
> 
>
> New web-app will be  created  to provide the information about load and
> unload status of tenats.
> This web-app will be deployed before the test. Test integration layer can
> access this web-app via REST call and get the necessary informations.
>
>
>
>
> Thanks and Best Regards,
>
> Saneth Dharmakeerthi
> Senior Software Engineer
> WSO2, Inc.
> Mobile: +94772325511
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
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] Deploy APIs and Sequences in ATF runtime

[Dinesh J Weerakkody]

Hi,

I want to deploy some API and sequence artifacts before start automation
test. Do we have something smiler to
*serverConfigurationManager.applyConfiguration(fileName)
*method which we can use to deploy artifacts in runtime?

Thanks

*Dinesh J. Weerakkody*
Software Engineer
WSO2 Inc.
lean | enterprise | middleware
M : +94 727 361788 | E : dine...@wso2.com | W : www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SFTP server backend for ESB integration tests

[Krishantha Samaraweera]

Hi Dimuthu,

Were you able to resolved the issue with SFTP server implementation.

Can you please update up on progress made so far.

Thanks,
Krishantha.


On Tue, Dec 23, 2014 at 5:23 PM, Dimuthu De Lanerolle 
wrote:

> Hi ,
>
> We are working on the $Subject.
>
> We have completed the implementation of the SFTP server and have added a
> sample test case scenario using VFS transport to test the SFTP server
> feasibility. We noted that when both ESB and SFTP server instances are
> running separately Test case scenario works as expected,  however when we
> run the SFTP server instance through TAF , ESB fails to perform the VFS
> file transfer scenario. We are currently working on solving this issue.
>
> Regards
> --
> Dimuthu De Lanerolle
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middlewear.
> http://wso2.com/
> Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
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

Re: [Dev] Merge the pull request

[Malaka Silva]

Hi Maheshika,

Thx Sameera.

Can you please release this orbit bundle?


On Wed, Jan 14, 2015 at 8:58 AM, Sameera Jayasoma  wrote:

> Done
>
> On Wed, Jan 14, 2015 at 6:14 AM, Malaka Silva  wrote:
>
>> Hi Sameera,
>>
>> We will go ahead with 3.0.0.wso2v5.
>>
>> Please check and merge
>>
>> On Mon, Jan 12, 2015 at 12:29 PM, Sameera Jayasoma 
>> wrote:
>>
>>> I just noticed we are packaging bsf 3.0-beta3 are 3.0.0.wso2v5. Is this
>>> correct?  Shouldn't it be 3.0.0.beta3-wso2v5
>>>
>>> On Mon, Jan 12, 2015 at 12:14 PM, Malaka Silva  wrote:
>>>
 Hi Sameera,

 It's done. Please check now.

 On Mon, Jan 12, 2015 at 11:57 AM, Sameera Jayasoma 
 wrote:

> Hi Malaka,
>
> I can't merge this automatically for some reason. Can you remove the
> entry from the parent pom and see?
>
> Thanks,
> Sameera.
>
> On Mon, Jan 12, 2015 at 11:30 AM, Malaka Silva 
> wrote:
>
>> Hi Sameera,
>>
>> I have removed the parent pom and created a new version.
>>
>> Please check and merge.
>>
>> [1] https://github.com/wso2/orbit/pull/50
>>
>> On Mon, Jan 12, 2015 at 10:23 AM, Malaka Silva 
>> wrote:
>>
>>> Hi,
>>>
>>> Last build was Success since I have reverted the fix.
>>>
>>> I will remove the parent and send a new version of BSF.
>>>
>>> On Sun, Jan 11, 2015 at 2:39 PM, Maheshika Goonetilleke <
>>> mahesh...@wso2.com> wrote:
>>>
 Hi Malaka

 The latest build is successful[1].

 As explained by Manoj you will require removing the 'parent' from
 the pom since we don't use it anymore.

 [1] https://wso2.org/jenkins-pr-builder/job/carbon-mediation/180/

 On Sun, Jan 11, 2015 at 1:49 PM, Manoj Kumara 
 wrote:

> Hi Malaka,
>
> You need to remove the parent entry from your orbit bundle.
>
> Thanks,
> Manoj
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
> On Sun, Jan 11, 2015 at 2:07 AM, Malaka Silva 
> wrote:
>
>> Hi Sameera,
>>
>> This works fine locally. Issue is with the Jenkins builder. [1]
>>
>> What is the way forward?
>>
>> 1) Can we get orbit pom released to nexus?
>> 2) Remove the parent from [2]?
>>
>> [1]
>> https://wso2.org/jenkins-pr-builder/job/carbon-mediation/179/consoleText
>> [2]
>> https://github.com/wso2/orbit/blob/master/bsf/3.0.0.wso2v4/pom.xml
>>
>> On Sun, Jan 11, 2015 at 8:42 AM, Sameera Jayasoma <
>> same...@wso2.com> wrote:
>>
>>> You've specified orbit pom as the parent pom of the orbit
>>> bundle. But we've not released this orbit pom to nexus.
>>>
>>> Can you remove all modules in the orbit pom and build it
>>> locally? Then try to build bsf bundle.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Sat, Jan 10, 2015 at 3:43 PM, Malaka Silva 
>>> wrote:
>>>
 Hi Sameera,

 I am getting the following after upgrading the feature to
 bsf-all:jar:3.0.0.wso2v4 any idea?

 [ERROR] Failed to execute goal on project
 org.wso2.carbon.mediators.server.feature: Could not resolve 
 dependencies
 for project
 org.wso2.carbon:org.wso2.carbon.mediators.server.feature:pom:4.3.0-SNAPSHOT:
 Failed to collect dependencies for
 [org.wso2.carbon:org.wso2.carbon.mediator.clazz.services:jar:4.3.0-SNAPSHOT
 (compile),
 org.wso2.carbon:org.wso2.carbon.mediator.command.services:jar:4.3.0-SNAPSHOT
 (compile),
 org.wso2.carbon:org.wso2.carbon.mediator.router.impl:jar:4.3.0-SNAPSHOT
 (compile),
 org.wso2.carbon:org.wso2.carbon.mediator.fastXSLT:jar:4.3.0-SNAPSHOT
 (compile), org.wso2.carbon:org.wso2.carbon.ec2-client:jar:4.2.0 
 (compile),
 org.apache.bsf.wso2:bsf-all:jar:3.0.0.wso2v4 (compile),
 rhino.wso2:js:jar:1.7.0.R4.wso2v1 (compile),
 org.wso2.carbon:org.wso2.carbon.mediator.event:jar:4.3.0-SNAPSHOT
 (compile)]: Failed to read artifact descriptor for
 org.apache.bsf.wso2:bsf-all:jar:3.0.0.wso2v4: Failure to find
 org.wso2.carbon:orbit-parent:pom:4.3.0-SNAPSHOT in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was
 cached in the local repository, resolution will not be reattempted 
 until
 the update interval of wso2-nexus has elapsed or updates are 
 forced ->
 [Help 1]
>>

[Dev] Please cancel......

[Bob Carson]

Robert R. Carson



___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] [Jaggery] Using jaggery test framework

[Himasha Guruge]

Hi Ayesha,

Yes I'm using ES version 2.0.0  so it's available. Thanks for the
information and samples, now it is clear.

Thanks & Regards,

Himasha

On Tue, Jan 13, 2015 at 10:16 PM, Ayesha Dissanayaka 
wrote:

> Hi Himasha,
>
> Yes, you can add test cases for both publisher and store.
>
> What is the ES version you are working on?
> From ES-2.0.0- M4 release onwards, jaggery-test module is available under
> */modules*. So you do not need to include anything there.
>
> In [1] there are test cases written to test the ES-Publisher REST-API.
> There you can see that test cases are written in .js fiiles. (Files
> other than executor.jag). Hope you can get an idea how to write test cases
> by looking into sample .js files in [1].
> Further you can refer http://jasmine.github.io as a guidline to write
> jaggery-tests.
>
> So, if you are using ES-2.0.0- M4, you can simply add your test specs for
> publisher into
> /repository/deployment/server/jaggeryapps/publisher/test directory.
>
> For the store you will have to create a directory "test" in
> /repository/deployment/server/jaggeryapps/store, copy the content
> from[2] to a file named executor.jag into this newly created "test"
> directory and add your tests specs files there.
>
> Then add below mapping to
> /repository/deployment/server/jaggeryapps/store/jaggery.conf .
> {
> "url":"/test/*",
> "path":"/test/executer.jag"
> }
>
> In
> /repository/deployment/server/jaggeryapps/publisher/jaggery.conf[3]
> this is already available.
>
> Restart the ES server.
> You may now list the publisher tests at
> http://localhost:9763/publisher/test and store tests at
> http://localhost:9763/store/test
>
> [1]
> https://github.com/wso2-dev/product-es/tree/master/modules/apps/publisher/test
> [2]
> https://github.com/wso2-dev/product-es/blob/master/modules/apps/publisher/test/executer.jag
> [3]
> https://github.com/wso2-dev/product-es/blob/master/modules/apps/publisher/jaggery.conf
>
> If you need further help on this, let me know.
>
> Thanks!
> - Ayesha
>
>
> On Tue, Jan 13, 2015 at 6:50 PM, Himasha Guruge  wrote:
>
>> Hi All,
>>
>> I need to write some test cases for an asset extension implemented in ES.
>> I went through the following link[1] but I'm not clear on following points.
>>
>> 1. Can we add test cases for both publisher and store side?
>> 2.  What exactly do we need to add under ES(version)/ modules?
>> 3.  What other files should be listed in a created test folder other than
>> executor.jag?
>>
>> Some additional examples/ articles will be really helpful.
>>
>> [1]
>> http://madhukaudantha.blogspot.com/2013/12/how-to-user-jaggery-test-framework-in.html
>>
>> Thanks & Regards,
>>
>> Himasha Guruge
>> *Software Engineer*
>> WS*O2* *Inc.*
>> Mobile: +94 777459299
>> himas...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>



-- 
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merge the pull request

[Sameera Jayasoma]

Done

On Wed, Jan 14, 2015 at 6:14 AM, Malaka Silva  wrote:

> Hi Sameera,
>
> We will go ahead with 3.0.0.wso2v5.
>
> Please check and merge
>
> On Mon, Jan 12, 2015 at 12:29 PM, Sameera Jayasoma 
> wrote:
>
>> I just noticed we are packaging bsf 3.0-beta3 are 3.0.0.wso2v5. Is this
>> correct?  Shouldn't it be 3.0.0.beta3-wso2v5
>>
>> On Mon, Jan 12, 2015 at 12:14 PM, Malaka Silva  wrote:
>>
>>> Hi Sameera,
>>>
>>> It's done. Please check now.
>>>
>>> On Mon, Jan 12, 2015 at 11:57 AM, Sameera Jayasoma 
>>> wrote:
>>>
 Hi Malaka,

 I can't merge this automatically for some reason. Can you remove the
 entry from the parent pom and see?

 Thanks,
 Sameera.

 On Mon, Jan 12, 2015 at 11:30 AM, Malaka Silva  wrote:

> Hi Sameera,
>
> I have removed the parent pom and created a new version.
>
> Please check and merge.
>
> [1] https://github.com/wso2/orbit/pull/50
>
> On Mon, Jan 12, 2015 at 10:23 AM, Malaka Silva 
> wrote:
>
>> Hi,
>>
>> Last build was Success since I have reverted the fix.
>>
>> I will remove the parent and send a new version of BSF.
>>
>> On Sun, Jan 11, 2015 at 2:39 PM, Maheshika Goonetilleke <
>> mahesh...@wso2.com> wrote:
>>
>>> Hi Malaka
>>>
>>> The latest build is successful[1].
>>>
>>> As explained by Manoj you will require removing the 'parent' from
>>> the pom since we don't use it anymore.
>>>
>>> [1] https://wso2.org/jenkins-pr-builder/job/carbon-mediation/180/
>>>
>>> On Sun, Jan 11, 2015 at 1:49 PM, Manoj Kumara 
>>> wrote:
>>>
 Hi Malaka,

 You need to remove the parent entry from your orbit bundle.

 Thanks,
 Manoj


 *Manoj Kumara*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 *lean.enterprise.middleware*
 Mobile: +94713448188

 On Sun, Jan 11, 2015 at 2:07 AM, Malaka Silva 
 wrote:

> Hi Sameera,
>
> This works fine locally. Issue is with the Jenkins builder. [1]
>
> What is the way forward?
>
> 1) Can we get orbit pom released to nexus?
> 2) Remove the parent from [2]?
>
> [1]
> https://wso2.org/jenkins-pr-builder/job/carbon-mediation/179/consoleText
> [2]
> https://github.com/wso2/orbit/blob/master/bsf/3.0.0.wso2v4/pom.xml
>
> On Sun, Jan 11, 2015 at 8:42 AM, Sameera Jayasoma <
> same...@wso2.com> wrote:
>
>> You've specified orbit pom as the parent pom of the orbit bundle.
>> But we've not released this orbit pom to nexus.
>>
>> Can you remove all modules in the orbit pom and build it locally?
>> Then try to build bsf bundle.
>>
>> Thanks,
>> Sameera.
>>
>> On Sat, Jan 10, 2015 at 3:43 PM, Malaka Silva 
>> wrote:
>>
>>> Hi Sameera,
>>>
>>> I am getting the following after upgrading the feature to
>>> bsf-all:jar:3.0.0.wso2v4 any idea?
>>>
>>> [ERROR] Failed to execute goal on project
>>> org.wso2.carbon.mediators.server.feature: Could not resolve 
>>> dependencies
>>> for project
>>> org.wso2.carbon:org.wso2.carbon.mediators.server.feature:pom:4.3.0-SNAPSHOT:
>>> Failed to collect dependencies for
>>> [org.wso2.carbon:org.wso2.carbon.mediator.clazz.services:jar:4.3.0-SNAPSHOT
>>> (compile),
>>> org.wso2.carbon:org.wso2.carbon.mediator.command.services:jar:4.3.0-SNAPSHOT
>>> (compile),
>>> org.wso2.carbon:org.wso2.carbon.mediator.router.impl:jar:4.3.0-SNAPSHOT
>>> (compile),
>>> org.wso2.carbon:org.wso2.carbon.mediator.fastXSLT:jar:4.3.0-SNAPSHOT
>>> (compile), org.wso2.carbon:org.wso2.carbon.ec2-client:jar:4.2.0 
>>> (compile),
>>> org.apache.bsf.wso2:bsf-all:jar:3.0.0.wso2v4 (compile),
>>> rhino.wso2:js:jar:1.7.0.R4.wso2v1 (compile),
>>> org.wso2.carbon:org.wso2.carbon.mediator.event:jar:4.3.0-SNAPSHOT
>>> (compile)]: Failed to read artifact descriptor for
>>> org.apache.bsf.wso2:bsf-all:jar:3.0.0.wso2v4: Failure to find
>>> org.wso2.carbon:orbit-parent:pom:4.3.0-SNAPSHOT in
>>> http://maven.wso2.org/nexus/content/groups/wso2-public/ was
>>> cached in the local repository, resolution will not be reattempted 
>>> until
>>> the update interval of wso2-nexus has elapsed or updates are forced 
>>> ->
>>> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>> with the -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>> logging.
>>>
>>>
>>> On Wed, Jan 7, 2015 at 6:13 AM, 

Re: [Dev] [APIM] PizzaShack Sample: List of Pizzas not loaded in web application

[Dinesh J Weerakkody]

Hi Yohanna,

Do you have any error logs in your console?

Thanks

*Dinesh J. Weerakkody*
Software Engineer
WSO2 Inc.
lean | enterprise | middleware
M : +94 727 361788 | E : dine...@wso2.com | W : www.wso2.com

On Tue, Jan 13, 2015 at 5:41 PM, Yohanna Fernando  wrote:

>
> As shown in diagram, the lists of pizzas are not loaded and I don't get
> the screen which says:
>
> "This App will be able to"
>
> Has anyone come across this before and know if I'm missing something?
> --
> Yohanna Fernando
> Training Specialist
> WSO2 Inc.
>  http://wso2.com
>
> E-mail: yoha...@wso2.com
> Cell: +94779021159
> 
>
> ___
> 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] Cluster-wide Test Case Suggestion

[Sajini De Silva]

Noted

On Tue, Jan 13, 2015 at 6:31 PM, Hasitha Hiranya  wrote:

> Hi Sajini,
>
> Like to suggest a test case as follows.
>
> For a client I developed a feature such that if enabled, multiple
> subscribers can exist by same clientID for the same topic.
> A new test case must be added so that,
>
> 1. Restart pack with "multipleSubscribersEnabled".
> 2. Clusterwide put two durable topic subs with same clientID.
>
> See messages are consumed as queues (if we push 1000 messages together
> both subs should receive 1000, not 2000, not nothing, not only one get 1000
> and other just sits there)
>
> Thanks
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>


-- 
Sajini De SIlva
Software Engineer; WSO2 Inc.; http://wso2.com ,
Email: saj...@wso2.com
Blog: http://sajinid.blogspot.com/
Git hub profile: https://github.com/sajinidesilva

Phone: +94 712797729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merge the pull request

[Malaka Silva]

Hi Sameera,

We will go ahead with 3.0.0.wso2v5.

Please check and merge

On Mon, Jan 12, 2015 at 12:29 PM, Sameera Jayasoma  wrote:

> I just noticed we are packaging bsf 3.0-beta3 are 3.0.0.wso2v5. Is this
> correct?  Shouldn't it be 3.0.0.beta3-wso2v5
>
> On Mon, Jan 12, 2015 at 12:14 PM, Malaka Silva  wrote:
>
>> Hi Sameera,
>>
>> It's done. Please check now.
>>
>> On Mon, Jan 12, 2015 at 11:57 AM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Malaka,
>>>
>>> I can't merge this automatically for some reason. Can you remove the
>>> entry from the parent pom and see?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Mon, Jan 12, 2015 at 11:30 AM, Malaka Silva  wrote:
>>>
 Hi Sameera,

 I have removed the parent pom and created a new version.

 Please check and merge.

 [1] https://github.com/wso2/orbit/pull/50

 On Mon, Jan 12, 2015 at 10:23 AM, Malaka Silva  wrote:

> Hi,
>
> Last build was Success since I have reverted the fix.
>
> I will remove the parent and send a new version of BSF.
>
> On Sun, Jan 11, 2015 at 2:39 PM, Maheshika Goonetilleke <
> mahesh...@wso2.com> wrote:
>
>> Hi Malaka
>>
>> The latest build is successful[1].
>>
>> As explained by Manoj you will require removing the 'parent' from the
>> pom since we don't use it anymore.
>>
>> [1] https://wso2.org/jenkins-pr-builder/job/carbon-mediation/180/
>>
>> On Sun, Jan 11, 2015 at 1:49 PM, Manoj Kumara  wrote:
>>
>>> Hi Malaka,
>>>
>>> You need to remove the parent entry from your orbit bundle.
>>>
>>> Thanks,
>>> Manoj
>>>
>>>
>>> *Manoj Kumara*
>>> Software Engineer
>>> WSO2 Inc. http://wso2.com/
>>> *lean.enterprise.middleware*
>>> Mobile: +94713448188
>>>
>>> On Sun, Jan 11, 2015 at 2:07 AM, Malaka Silva 
>>> wrote:
>>>
 Hi Sameera,

 This works fine locally. Issue is with the Jenkins builder. [1]

 What is the way forward?

 1) Can we get orbit pom released to nexus?
 2) Remove the parent from [2]?

 [1]
 https://wso2.org/jenkins-pr-builder/job/carbon-mediation/179/consoleText
 [2]
 https://github.com/wso2/orbit/blob/master/bsf/3.0.0.wso2v4/pom.xml

 On Sun, Jan 11, 2015 at 8:42 AM, Sameera Jayasoma >>> > wrote:

> You've specified orbit pom as the parent pom of the orbit bundle.
> But we've not released this orbit pom to nexus.
>
> Can you remove all modules in the orbit pom and build it locally?
> Then try to build bsf bundle.
>
> Thanks,
> Sameera.
>
> On Sat, Jan 10, 2015 at 3:43 PM, Malaka Silva 
> wrote:
>
>> Hi Sameera,
>>
>> I am getting the following after upgrading the feature to
>> bsf-all:jar:3.0.0.wso2v4 any idea?
>>
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.mediators.server.feature: Could not resolve 
>> dependencies
>> for project
>> org.wso2.carbon:org.wso2.carbon.mediators.server.feature:pom:4.3.0-SNAPSHOT:
>> Failed to collect dependencies for
>> [org.wso2.carbon:org.wso2.carbon.mediator.clazz.services:jar:4.3.0-SNAPSHOT
>> (compile),
>> org.wso2.carbon:org.wso2.carbon.mediator.command.services:jar:4.3.0-SNAPSHOT
>> (compile),
>> org.wso2.carbon:org.wso2.carbon.mediator.router.impl:jar:4.3.0-SNAPSHOT
>> (compile),
>> org.wso2.carbon:org.wso2.carbon.mediator.fastXSLT:jar:4.3.0-SNAPSHOT
>> (compile), org.wso2.carbon:org.wso2.carbon.ec2-client:jar:4.2.0 
>> (compile),
>> org.apache.bsf.wso2:bsf-all:jar:3.0.0.wso2v4 (compile),
>> rhino.wso2:js:jar:1.7.0.R4.wso2v1 (compile),
>> org.wso2.carbon:org.wso2.carbon.mediator.event:jar:4.3.0-SNAPSHOT
>> (compile)]: Failed to read artifact descriptor for
>> org.apache.bsf.wso2:bsf-all:jar:3.0.0.wso2v4: Failure to find
>> org.wso2.carbon:orbit-parent:pom:4.3.0-SNAPSHOT in
>> http://maven.wso2.org/nexus/content/groups/wso2-public/ was
>> cached in the local repository, resolution will not be reattempted 
>> until
>> the update interval of wso2-nexus has elapsed or updates are forced 
>> ->
>> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven
>> with the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>>
>>
>> On Wed, Jan 7, 2015 at 6:13 AM, Malaka Silva 
>> wrote:
>>
>>> Great Thx. Will Check
>>>
>>> On Tue, Jan 6, 2015 at 11:37 PM, Maheshika Goonetilleke <
>>> mahesh...@wso2.com> wrote:
>>>
 Hi Sameera and Malaka
>

[Dev] How to enable security for a proxy service in Dev Studio

[Niranjan Karunanandham]

Hi,

Using the ESB console, we can create a simple unsecured proxy and enable
security using the QOS. For example: in the ESB console, I created a Pass
Through Proxy (say 'proxy1') and enabled "UsernameToken" security from the
QOS. ESB automatically creates the policy for this and saves it to the
registry at "
conf:/repository/axis2/service-groups/proxy1/services/proxy1/policies/UTOverTransport".

In Developer Studio, can we enable the security for a proxy service? i.e.,
is there an option where we can select the Security as
"UsernameToken", "Non-repudiation",
etc... and the policy files are generated automatically as it is done in
the ESB console?

Regards,
Nira

-- 

*Niranjan Karunanandham*
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error in pom file

[Bhathiya Jayasekara]

Hi Pamod,

I fixed this in wso2-dev. Please try with it now.

@Prabath: Please sync wso2 repo. (carbon-storage-management repo)

Thanks,
Bhathiya

On Tue, Jan 13, 2015 at 9:52 PM, Pamod Sylvester  wrote:

> Thanks for the help Sameera. The feature could be located under the
> temporary directory created during feature extraction.
>
> 
>  version="4.3.0.SNAPSHOT">
>   This feature contains the bundles required for Cassandra
> client
>   %copyright
>   %license
>   
>version="1.1.1.6"/>
>   
>   
>version="4.3.0"/>
>   
>   
>version="4.3.0"/>
>   
>version="4.3.0.SNAPSHOT"/>
>   
>   
>*  version="0.0.0.${wso2_kernel_version}"/>*
>   
> 
>
> Thanks,
> Pamod
>
> On Tue, Jan 13, 2015 at 7:14 PM, Sameera Jayasoma 
> wrote:
>
>> Try this in your p2-profile-gen/target directory. This must be coming
>> from features rather than plugins.
>>
>> On Tue, Jan 13, 2015 at 7:12 PM, Pamod Sylvester  wrote:
>>
>>> Thanks Sameera. Tried it out. It doesn't show a manifest with the above
>>> string. Might be a different issue. The full log is the following
>>>
>>> Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 Format
>>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>>> 0.0.0.${wso2_kernel_version} java.lang.IllegalArgumentException: Format
>>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>>> 0.0.0.${wso2_kernel_version}
>>>
>>> Product publishing ended with the following exception:
>>> java.lang.IllegalArgumentException: Format
>>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>>> 0.0.0.${wso2_kernel_version}
>>> at
>>> org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275)
>>> at
>>> org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:89)
>>> at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79)
>>> at org.eclipse.equinox.p2.metadata.Version.parseVersion(Version.java:141)
>>> at
>>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.(FeatureEntry.java:63)
>>> at
>>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.createRequires(FeatureEntry.java:40)
>>> at
>>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.processImport(FeatureManifestParser.java:194)
>>> at
>>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.startElement(FeatureManifestParser.java:280)
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
>>> at
>>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
>>> at
>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756)
>>> at
>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
>>> at
>>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
>>> at
>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
>>> at
>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
>>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
>>> at
>>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.parse(FeatureManifestParser.java:126)
>>> at
>>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureParser.parse(FeatureParser.java:60)
>>> at
>>> org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.getFeatures(FeaturesAction.java:518)
>>> at
>>> org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.perform(FeaturesAction.java:604)
>>> at
>>> org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
>>> at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1294)
>>> at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
>>> at
>>> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:283)
>>> at
>>> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:253)
>>> at
>>> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.start(AbstractPublisherApplication.java:315)
>>> at
>>> org.eclipse.eq

Re: [Dev] [ES] 4.3.0 based server hang at startup.

[Maheshika Goonetilleke]

Hi Hasitha

The carbon-identity and carbon-governance build are successful now.

On Tue, Jan 13, 2015 at 6:39 PM, Hasintha Indrajee 
wrote:

> Hi Maheshika,
>
> The jenkins build has failed due to the reason stated in the thread
> "Compilation errors due to Jenkins killing forked VMs?".  Can you please
> trigger the jenkins build manually ?
>
>
> On Tue, Jan 13, 2015 at 5:34 PM, Supun Malinga  wrote:
>
>> Thanks Hasintha.
>>
>> Apparently identity repo build has failed last couple of times.
>> https://wso2.org/jenkins/job/carbon-identity/
>>
>> Can we make sure we get a snapshot deployment to nexus from this pls..
>>
>> thanks,
>>
>> On Tue, Jan 13, 2015 at 5:19 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Hi Supun,
>>>
>>> Changes are merged to org repo .
>>>
>>> On Tue, Jan 13, 2015 at 5:07 PM, Supun Malinga  wrote:
>>>
 Hi,

 Can we merge the changes into org repo as well pls ?

 thanks,

 On Tue, Jan 13, 2015 at 1:15 PM, Ayesha Dissanayaka 
 wrote:

> Hi Pulasthi, Hasintha,
>
> Thanks a lot for the quick response. :)
>
> On Tue, Jan 13, 2015 at 12:33 PM, Hasintha Indrajee  > wrote:
>
>> Hi Ayesha,
>>
>> Required changes are done in wso2-dev repo.
>>
>>
>>
>>
>> On Tue, Jan 13, 2015 at 12:17 PM, Pulasthi Mahawithana <
>> pulast...@wso2.com> wrote:
>>
>>> Hi Ayesha,
>>>
>>> Some of the changes that were made in the pull request has been
>>> reverted when the kernel 4.3.0 release merge is done. Hasintha will add 
>>> the
>>> required changes back.
>>>
>>> On Tue, Jan 13, 2015 at 12:11 PM, Ayesha Dissanayaka <
>>> aye...@wso2.com> wrote:
>>>
 Hi all,

 ES server build on carbon.kernal.version- 4.3.0 server startup
 hangs giving following stack trace.

 Carbon initialization is delayed due to the following unsatisfied
 items:
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 Module: org.wso2.carbon.security.mgt-4.3.0-SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGiAxis2Service: org.wso2.carbon.identity.sso.saml-4.3.0.SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGiAxis2Service: org.wso2.carbon.registry.ws.api-4.3.0.SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 Module: rampart-trust-1.6.1.wso2v13-SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 Module: rampart-core-1.6.1.wso2v13-SNAPSHOT
 [2015-01-13 11:55:19,239]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGi Service: org.apache.axis2.engine.AxisObserver
 [2015-01-13 11:55:19,239]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGiAxis2Service: org.wso2.carbon.security.mgt-4.3.0.SNAPSHOT

 I see that the same issue is discussed in threads [1] and [2].

 I noticed that there are two wss4j jars, in the latest ES pack.
 wss4j_1.5.11.wso2v7
 wss4j_1.5.11.wso2v8-SNAPSHOT

 According to thread [2] , there it is fixed in [3]. But, this
 change seems not available in current wso2-dev/carbon-identity repo.[4]

 Due to this ES build fails at automation test modules.

 [1] [Dev] Carbon 4.3.0 snapshot based server hangs
 [2] [Dev] [Important] wss4j 1.5.11.wso2v7 bundle does not contain
 Dynamic Imports
 [3]
 https://github.com/pulasthi7/carbon-identity/commit/d843ae38178fbb66a0fa8386f7f183d8b71c621d
 [4] https://github.com/wso2-dev/carbon-identity/blob/master/pom.xml
 Thanks!
 -Ayesha
 --
 *Ayesha Dissanayaka*
 Software Engineer,
 WSO2, Inc : http://wso2.com
 
 20, Palmgrove Avenue, Colombo 3
 E-Mail: aye...@wso2.com 

>>>
>>>
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022
>>> Blog: http://blog.pulasthi.org
>>>
>>
>>
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>
> ___
> Dev mailing l

[Dev] [G-Reg ] Please review and merge the pull request - G-Reg Tagging Handle Sample

[Sithumini Senevirathne]

Hi,

Please review and merge the pull request [1].

[1] https://github.com/wso2-dev/product-greg/pull/63

Jira : https://wso2.org/jira/browse/REGISTRY-2379

Thanks,
Sithumini
-- 
-- 
Sithumini Senevirathne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: sithumi...@wso2.com,   mobile: +94 756977999
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] [Jaggery] Using jaggery test framework

[Ayesha Dissanayaka]

Hi Himasha,

Yes, you can add test cases for both publisher and store.

What is the ES version you are working on?
>From ES-2.0.0- M4 release onwards, jaggery-test module is available under
*/modules*. So you do not need to include anything there.

In [1] there are test cases written to test the ES-Publisher REST-API.
There you can see that test cases are written in .js fiiles. (Files
other than executor.jag). Hope you can get an idea how to write test cases
by looking into sample .js files in [1].
Further you can refer http://jasmine.github.io as a guidline to write
jaggery-tests.

So, if you are using ES-2.0.0- M4, you can simply add your test specs for
publisher into
/repository/deployment/server/jaggeryapps/publisher/test directory.

For the store you will have to create a directory "test" in
/repository/deployment/server/jaggeryapps/store, copy the content
from[2] to a file named executor.jag into this newly created "test"
directory and add your tests specs files there.

Then add below mapping to
/repository/deployment/server/jaggeryapps/store/jaggery.conf .
{
"url":"/test/*",
"path":"/test/executer.jag"
}

In
/repository/deployment/server/jaggeryapps/publisher/jaggery.conf[3]
this is already available.

Restart the ES server.
You may now list the publisher tests at http://localhost:9763/publisher/test
and store tests at http://localhost:9763/store/test

[1]
https://github.com/wso2-dev/product-es/tree/master/modules/apps/publisher/test
[2]
https://github.com/wso2-dev/product-es/blob/master/modules/apps/publisher/test/executer.jag
[3]
https://github.com/wso2-dev/product-es/blob/master/modules/apps/publisher/jaggery.conf

If you need further help on this, let me know.

Thanks!
- Ayesha


On Tue, Jan 13, 2015 at 6:50 PM, Himasha Guruge  wrote:

> Hi All,
>
> I need to write some test cases for an asset extension implemented in ES.
> I went through the following link[1] but I'm not clear on following points.
>
> 1. Can we add test cases for both publisher and store side?
> 2.  What exactly do we need to add under ES(version)/ modules?
> 3.  What other files should be listed in a created test folder other than
> executor.jag?
>
> Some additional examples/ articles will be really helpful.
>
> [1]
> http://madhukaudantha.blogspot.com/2013/12/how-to-user-jaggery-test-framework-in.html
>
> Thanks & Regards,
>
> Himasha Guruge
> *Software Engineer*
> WS*O2* *Inc.*
> Mobile: +94 777459299
> himas...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error in pom file

[Pamod Sylvester]

Thanks for the help Sameera. The feature could be located under the
temporary directory created during feature extraction.



  This feature contains the bundles required for Cassandra
client
  %copyright
  %license
  
  
  
  
  
  
  
  
  
  
  
  
   * *
  


Thanks,
Pamod

On Tue, Jan 13, 2015 at 7:14 PM, Sameera Jayasoma  wrote:

> Try this in your p2-profile-gen/target directory. This must be coming from
> features rather than plugins.
>
> On Tue, Jan 13, 2015 at 7:12 PM, Pamod Sylvester  wrote:
>
>> Thanks Sameera. Tried it out. It doesn't show a manifest with the above
>> string. Might be a different issue. The full log is the following
>>
>> Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 Format
>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>> 0.0.0.${wso2_kernel_version} java.lang.IllegalArgumentException: Format
>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>> 0.0.0.${wso2_kernel_version}
>>
>> Product publishing ended with the following exception:
>> java.lang.IllegalArgumentException: Format
>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>> 0.0.0.${wso2_kernel_version}
>> at
>> org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275)
>> at
>> org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:89)
>> at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79)
>> at org.eclipse.equinox.p2.metadata.Version.parseVersion(Version.java:141)
>> at
>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.(FeatureEntry.java:63)
>> at
>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.createRequires(FeatureEntry.java:40)
>> at
>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.processImport(FeatureManifestParser.java:194)
>> at
>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.startElement(FeatureManifestParser.java:280)
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
>> at
>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
>> at
>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.parse(FeatureManifestParser.java:126)
>> at
>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureParser.parse(FeatureParser.java:60)
>> at
>> org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.getFeatures(FeaturesAction.java:518)
>> at
>> org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.perform(FeaturesAction.java:604)
>> at
>> org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
>> at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1294)
>> at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
>> at
>> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:283)
>> at
>> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:253)
>> at
>> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.start(AbstractPublisherApplication.java:315)
>> at
>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>> at
>> org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26)
>> at java.lang.Thread.run(Thread.java:662)
>>
>> Product publisher application was executed with the following arguments:
>> -source
>>
>> /home/pamod/Desktop/dev/dev_playground/Release_Test_3.0.0/product-mb/modules/p2-profile/target/tmp.1421155711761/featureExtract
>> -metadataRepository
>>
>> file:/home/pamod/Desktop/dev/d

Re: [Dev] Error in pom file

[Sameera Jayasoma]

Try this in your p2-profile-gen/target directory. This must be coming from
features rather than plugins.

On Tue, Jan 13, 2015 at 7:12 PM, Pamod Sylvester  wrote:

> Thanks Sameera. Tried it out. It doesn't show a manifest with the above
> string. Might be a different issue. The full log is the following
>
> Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 Format
> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
> 0.0.0.${wso2_kernel_version} java.lang.IllegalArgumentException: Format
> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
> 0.0.0.${wso2_kernel_version}
>
> Product publishing ended with the following exception:
> java.lang.IllegalArgumentException: Format
> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
> 0.0.0.${wso2_kernel_version}
> at
> org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275)
> at
> org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:89)
> at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79)
> at org.eclipse.equinox.p2.metadata.Version.parseVersion(Version.java:141)
> at
> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.(FeatureEntry.java:63)
> at
> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.createRequires(FeatureEntry.java:40)
> at
> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.processImport(FeatureManifestParser.java:194)
> at
> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.startElement(FeatureManifestParser.java:280)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
> at
> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.parse(FeatureManifestParser.java:126)
> at
> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureParser.parse(FeatureParser.java:60)
> at
> org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.getFeatures(FeaturesAction.java:518)
> at
> org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.perform(FeaturesAction.java:604)
> at
> org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
> at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1294)
> at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
> at
> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:283)
> at
> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:253)
> at
> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.start(AbstractPublisherApplication.java:315)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at
> org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26)
> at java.lang.Thread.run(Thread.java:662)
>
> Product publisher application was executed with the following arguments:
> -source
>
> /home/pamod/Desktop/dev/dev_playground/Release_Test_3.0.0/product-mb/modules/p2-profile/target/tmp.1421155711761/featureExtract
> -metadataRepository
>
> file:/home/pamod/Desktop/dev/dev_playground/Release_Test_3.0.0/product-mb/modules/p2-profile/target/p2-repo
> -metadataRepositoryName
> wso2mb-p2-profile
> -artifactRepository
>
> file:/home/pamod/Desktop/dev/dev_playground/Release_Test_3.0.0/product-mb/modules/p2-profile/target/p2-repo
> -artifactRepositoryName
> wso2mb-p2-profile
> -publishArtifacts
> -publishArtifactRepository
> -compress
> -append
> [ERROR] P2 publisher return code was 1
> org.apache.m

Re: [Dev] Error in pom file

[Pamod Sylvester]

Thanks Sameera. Tried it out. It doesn't show a manifest with the above
string. Might be a different issue. The full log is the following

Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 Format
"format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
0.0.0.${wso2_kernel_version} java.lang.IllegalArgumentException: Format
"format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
0.0.0.${wso2_kernel_version}

Product publishing ended with the following exception:
java.lang.IllegalArgumentException: Format
"format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
0.0.0.${wso2_kernel_version}
at
org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275)
at
org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:89)
at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79)
at org.eclipse.equinox.p2.metadata.Version.parseVersion(Version.java:141)
at
org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.(FeatureEntry.java:63)
at
org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.createRequires(FeatureEntry.java:40)
at
org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.processImport(FeatureManifestParser.java:194)
at
org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.startElement(FeatureManifestParser.java:280)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at
com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at
org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.parse(FeatureManifestParser.java:126)
at
org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureParser.parse(FeatureParser.java:60)
at
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.getFeatures(FeaturesAction.java:518)
at
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.perform(FeaturesAction.java:604)
at
org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
at
org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1294)
at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
at
org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:283)
at
org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:253)
at
org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.start(AbstractPublisherApplication.java:315)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26)
at java.lang.Thread.run(Thread.java:662)

Product publisher application was executed with the following arguments:
-source
/home/pamod/Desktop/dev/dev_playground/Release_Test_3.0.0/product-mb/modules/p2-profile/target/tmp.1421155711761/featureExtract
-metadataRepository
file:/home/pamod/Desktop/dev/dev_playground/Release_Test_3.0.0/product-mb/modules/p2-profile/target/p2-repo
-metadataRepositoryName
wso2mb-p2-profile
-artifactRepository
file:/home/pamod/Desktop/dev/dev_playground/Release_Test_3.0.0/product-mb/modules/p2-profile/target/p2-repo
-artifactRepositoryName
wso2mb-p2-profile
-publishArtifacts
-publishArtifactRepository
-compress
-append
[ERROR] P2 publisher return code was 1
org.apache.maven.plugin.MojoFailureException: P2 publisher return code was 1
at
org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
at
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
at org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
at
org.apache.maven.plugin.DefaultBuildPluginManage

[Dev] [ES] [Jaggery] Using jaggery test framework

[Himasha Guruge]

Hi All,

I need to write some test cases for an asset extension implemented in ES. I
went through the following link[1] but I'm not clear on following points.

1. Can we add test cases for both publisher and store side?
2.  What exactly do we need to add under ES(version)/ modules?
3.  What other files should be listed in a created test folder other than
executor.jag?

Some additional examples/ articles will be really helpful.

[1]
http://madhukaudantha.blogspot.com/2013/12/how-to-user-jaggery-test-framework-in.html

Thanks & Regards,

Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] 4.3.0 based server hang at startup.

[Hasintha Indrajee]

Hi Maheshika,

The jenkins build has failed due to the reason stated in the thread
"Compilation errors due to Jenkins killing forked VMs?".  Can you please
trigger the jenkins build manually ?


On Tue, Jan 13, 2015 at 5:34 PM, Supun Malinga  wrote:

> Thanks Hasintha.
>
> Apparently identity repo build has failed last couple of times.
> https://wso2.org/jenkins/job/carbon-identity/
>
> Can we make sure we get a snapshot deployment to nexus from this pls..
>
> thanks,
>
> On Tue, Jan 13, 2015 at 5:19 PM, Hasintha Indrajee 
> wrote:
>
>> Hi Supun,
>>
>> Changes are merged to org repo .
>>
>> On Tue, Jan 13, 2015 at 5:07 PM, Supun Malinga  wrote:
>>
>>> Hi,
>>>
>>> Can we merge the changes into org repo as well pls ?
>>>
>>> thanks,
>>>
>>> On Tue, Jan 13, 2015 at 1:15 PM, Ayesha Dissanayaka 
>>> wrote:
>>>
 Hi Pulasthi, Hasintha,

 Thanks a lot for the quick response. :)

 On Tue, Jan 13, 2015 at 12:33 PM, Hasintha Indrajee 
 wrote:

> Hi Ayesha,
>
> Required changes are done in wso2-dev repo.
>
>
>
>
> On Tue, Jan 13, 2015 at 12:17 PM, Pulasthi Mahawithana <
> pulast...@wso2.com> wrote:
>
>> Hi Ayesha,
>>
>> Some of the changes that were made in the pull request has been
>> reverted when the kernel 4.3.0 release merge is done. Hasintha will add 
>> the
>> required changes back.
>>
>> On Tue, Jan 13, 2015 at 12:11 PM, Ayesha Dissanayaka > > wrote:
>>
>>> Hi all,
>>>
>>> ES server build on carbon.kernal.version- 4.3.0 server startup hangs
>>> giving following stack trace.
>>>
>>> Carbon initialization is delayed due to the following unsatisfied
>>> items:
>>> [2015-01-13 11:55:19,238]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> Module: org.wso2.carbon.security.mgt-4.3.0-SNAPSHOT
>>> [2015-01-13 11:55:19,238]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> OSGiAxis2Service: org.wso2.carbon.identity.sso.saml-4.3.0.SNAPSHOT
>>> [2015-01-13 11:55:19,238]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> OSGiAxis2Service: org.wso2.carbon.registry.ws.api-4.3.0.SNAPSHOT
>>> [2015-01-13 11:55:19,238]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> Module: rampart-trust-1.6.1.wso2v13-SNAPSHOT
>>> [2015-01-13 11:55:19,238]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> Module: rampart-core-1.6.1.wso2v13-SNAPSHOT
>>> [2015-01-13 11:55:19,239]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> OSGi Service: org.apache.axis2.engine.AxisObserver
>>> [2015-01-13 11:55:19,239]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> OSGiAxis2Service: org.wso2.carbon.security.mgt-4.3.0.SNAPSHOT
>>>
>>> I see that the same issue is discussed in threads [1] and [2].
>>>
>>> I noticed that there are two wss4j jars, in the latest ES pack.
>>> wss4j_1.5.11.wso2v7
>>> wss4j_1.5.11.wso2v8-SNAPSHOT
>>>
>>> According to thread [2] , there it is fixed in [3]. But, this change
>>> seems not available in current wso2-dev/carbon-identity repo.[4]
>>>
>>> Due to this ES build fails at automation test modules.
>>>
>>> [1] [Dev] Carbon 4.3.0 snapshot based server hangs
>>> [2] [Dev] [Important] wss4j 1.5.11.wso2v7 bundle does not contain
>>> Dynamic Imports
>>> [3]
>>> https://github.com/pulasthi7/carbon-identity/commit/d843ae38178fbb66a0fa8386f7f183d8b71c621d
>>> [4] https://github.com/wso2-dev/carbon-identity/blob/master/pom.xml
>>> Thanks!
>>> -Ayesha
>>> --
>>> *Ayesha Dissanayaka*
>>> Software Engineer,
>>> WSO2, Inc : http://wso2.com
>>> 
>>> 20, Palmgrove Avenue, Colombo 3
>>> E-Mail: aye...@wso2.com 
>>>
>>
>>
>>
>> --
>> *Pulasthi Mahawithana*
>> Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022
>> Blog: http://blog.pulasthi.org
>>
>
>


 --
 *Ayesha Dissanayaka*
 Software Engineer,
 WSO2, Inc : http://wso2.com
 
 20, Palmgrove Avenue, Colombo 3
 E-Mail: aye...@wso2.com 

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Supun Malinga,
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> email: sup...@wso2.com 
>>> mobile: +94 (0)71 56 91 321
>>>
>>
>>
>
>
> --
> Supun Malinga,
>
> Senior Software Enginee

[Dev] Cluster-wide Test Case Suggestion

[Hasitha Hiranya]

Hi Sajini,

Like to suggest a test case as follows.

For a client I developed a feature such that if enabled, multiple
subscribers can exist by same clientID for the same topic.
A new test case must be added so that,

1. Restart pack with "multipleSubscribersEnabled".
2. Clusterwide put two durable topic subs with same clientID.

See messages are consumed as queues (if we push 1000 messages together both
subs should receive 1000, not 2000, not nothing, not only one get 1000 and
other just sits there)

Thanks

-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can a single WSDL file be generated for two Axis2 service classes?

[Rajeevan Vimalanathan]

Hi Sagara,

Thanks for the response.
Currently, WSO2 DevStudio supports more than one service class to be
created in an Axis2 service project. Also, DevStudio allows user to select
an Axis2 service project and execute a generate WSDL command. In that case,
only one WSDL file will be generated for the first service defined in
services.xml (inside 'serviceGroup').
It seems like it is not the correct way to handle according to your answer.
What could be the best approach [1 or 2] to resolve this issue?
[1] Allow user to select a service class and execute a generate WSDL
command, not by selecting an Axis2 service project
[2] Allow user to select an Axis2 project and execute a generate WSDL
command, and in a intermediate window showing available service classes to
select

Thanks,
Rajeevan

On Tue, Jan 13, 2015 at 6:01 PM, Sagara Gunathunga  wrote:

>
>
> On Tue, Jan 13, 2015 at 5:33 PM, Rajeevan Vimalanathan  > wrote:
>
>> Hi,
>>
>> I am looking into a JIRA[1] that relates to generating a WSDL file for an
>> Axis2 service project in DevStudio. In this scenario, services.xml file
>> contains two service elements inside a serviceGroup element. So the Axis2
>> project contains two service classes.
>>
>> [1]https://wso2.org/jira/browse/TOOLS-2378
>>
>> Is it possible to generate a single WSDL file that describes both
>> services in the project?
>> Appreciate your response on this.
>>
>
> Generally in code-first approach web services frameworks assume one Java
> class is map to one web service hence one WSDL per one service class, Axis2
> also use same approach.
>
> Thanks !
>
>>
>> Thanks,
>> Rajeevan
>>
>> --
>> Best Regards,
>> V.Rajeevan
>> Software Engineer,
>> WSO2 Inc. :http://wso2.com
>>
>> Mobile : +94 773090875
>> Email : rajeev...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
Best Regards,
V.Rajeevan
Software Engineer,
WSO2 Inc. :http://wso2.com

Mobile : +94 773090875
Email : rajeev...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Urgent] Updating carbon-apimgt to use kernel version 4.3.0 instead of 4.3.0-SNAPSHOT

[Nuwan Dias]

Done.

On Tue, Jan 13, 2015 at 6:23 PM, Roshan Wijesena  wrote:

> Thanks for bring this up and I have fixed it.
>
> Hi NuwanD,
>
> Please merge this pull request  [1] to wso2-dev repo.
>
> [1] https://github.com/wso2-dev/carbon-apimgt/pull/15
>
> Regards
> Roshan.
>
>
>
> On Tue, Jan 13, 2015 at 3:40 PM, Pulasthi Supun  wrote:
>
>> Hi Roshan,
>>
>> We are still getting errors during feature installations.
>>
>> Installing org.wso2.carbon.tenant.deployment.feature.group 4.3.0.SNAPSHOT.
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - API Store Feature 4.3.0.SNAPSHOT
>> (org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT)
>>  Missing requirement: WSO2 Carbon - API Store Feature 4.3.0.SNAPSHOT
>> (org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT) requires
>> 'org.wso2.carbon.core.server.feature.group [4.3.0.SNAPSHOT,4.4.0)' but it
>> could not be found
>> Application failed, log file location:
>> /home/greg/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1421140548600.log
>>
>> These also need to be corrected.
>>
>> Best Regards,
>> Pulasthi
>>
>> On Sun, Jan 11, 2015 at 10:59 PM, Pulasthi Supun 
>> wrote:
>>
>>> Hi Nuwan/Ruwan
>>>
>>> Can someone merge this pull ASAP. And btw the build still seems to fail
>>> under a clean repo build.
>>>
>>> Best Regards,
>>> Pulasthi
>>>
>>> On Sat, Jan 10, 2015 at 8:12 PM, Roshan Wijesena 
>>> wrote:
>>>
 Thanks Prabath.

 Hi NuwanD,

 I have added more fixes to carbon-apimgt  now we can build
 carbon-apimgt components without any compilation errors.Further I updated
 corresponded carbon versions and added  latest APIM changes also. I have
 made a pull request [1] please merge it to the [2] repo. After that  please
 send the Pull request to [3].


 [1] https://github.com/wso2-dev/carbon-apimgt/pull/14
 [2] https://github.com/wso2-dev/carbon-apimgt
 [3] https://github.com/wso2/carbon-apimgt

 let me know any concerns.

 Regards
 Roshan.


 On Sat, Jan 10, 2015 at 11:38 AM, Prabath Abeysekera >>> > wrote:

> Hi Everyone,
>
> Geeth and I had already fixed most of these issues in
> wso2-dev/carbon-apimgt repository. Appreciate if someone who's got access
> sending PRs to wso2/carbon-apimgt, can merge these changes.
>
> Cheers,
> Prabath
>
> On Fri, Jan 9, 2015 at 11:07 PM, Pulasthi Supun 
> wrote:
>
>> Hi Roshan,
>>
>> We are installing several apim features in our product build. below
>> is the list of features we are installing.
>>
>> org.wso2.carbon:org.wso2.carbon.apimgt.core.feature
>> org.wso2.carbon:org.wso2.carbon.apimgt.interceptor.feature
>> org.wso2.carbon:org.wso2.carbon.apimgt.publisher.feature
>> org.wso2.carbon:org.wso2.carbon.apimgt.store.feature
>> org.wso2.carbon:org.wso2.carbon.apimgt.startup.publisher.feature
>>
>> if we can get these features built even locally ( for now ) that
>> would be great.
>>
>> Best Regards,
>> Pulasthi
>>
>>
>> On Fri, Jan 9, 2015 at 10:40 PM, Roshan Wijesena 
>> wrote:
>>
>>> Hi Pulasthi,
>>>
>>> What are the components you guys have tried to build in Greg product?
>>> please share the repos if possible. Then I can test it  locally  my 
>>> self to
>>> make sure things are working after the fix.
>>>
>>> Regards
>>> Roshan
>>>
>>> On Fri, Jan 9, 2015 at 9:38 PM, Pulasthi Supun 
>>> wrote:
>>>
 Hi Roshan,

 Great, Thanks.

 Best Regards,
 Pulasthi

 On Fri, Jan 9, 2015 at 8:40 PM, Roshan Wijesena 
 wrote:

> Hi All,
>
> I had a look into this issue. While working on this I have
> encountered multiple compilation errors in carbon-apimgt. I have to 
> fix
> them first. However, I will  update the progress here by tomorrow.
>
> Regards
> Roshan.
>
>
>
> On Fri, Jan 9, 2015 at 6:35 PM, Nuwan Dias 
> wrote:
>
>> Adding Roshan. He will look into it.
>>
>> Thanks,
>> NuwanD.
>>
>> On Fri, Jan 9, 2015 at 4:26 PM, Pulasthi Supun > > wrote:
>>
>>> Hi All,
>>>
>>> The carbon-apimgt needs to be updated corresponding to the
>>> kernel release. We are getting the following error when building 
>>> the Greg
>>> product and this is a blocker for us. The versions need to be 
>>> updated.
>>>
>>> 
>>> Installing org.wso2.carbon.tenant.deployment.feature.group
>>> 4.3.0.SNAPSHOT.
>>> Installation failed.
>>> Cannot complete the install b

Re: [Dev] [Urgent] Updating carbon-apimgt to use kernel version 4.3.0 instead of 4.3.0-SNAPSHOT

[Roshan Wijesena]

Thanks for bring this up and I have fixed it.

Hi NuwanD,

Please merge this pull request  [1] to wso2-dev repo.

[1] https://github.com/wso2-dev/carbon-apimgt/pull/15

Regards
Roshan.



On Tue, Jan 13, 2015 at 3:40 PM, Pulasthi Supun  wrote:

> Hi Roshan,
>
> We are still getting errors during feature installations.
>
> Installing org.wso2.carbon.tenant.deployment.feature.group 4.3.0.SNAPSHOT.
> Installation failed.
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: WSO2 Carbon - API Store Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT)
>  Missing requirement: WSO2 Carbon - API Store Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT) requires
> 'org.wso2.carbon.core.server.feature.group [4.3.0.SNAPSHOT,4.4.0)' but it
> could not be found
> Application failed, log file location:
> /home/greg/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1421140548600.log
>
> These also need to be corrected.
>
> Best Regards,
> Pulasthi
>
> On Sun, Jan 11, 2015 at 10:59 PM, Pulasthi Supun 
> wrote:
>
>> Hi Nuwan/Ruwan
>>
>> Can someone merge this pull ASAP. And btw the build still seems to fail
>> under a clean repo build.
>>
>> Best Regards,
>> Pulasthi
>>
>> On Sat, Jan 10, 2015 at 8:12 PM, Roshan Wijesena  wrote:
>>
>>> Thanks Prabath.
>>>
>>> Hi NuwanD,
>>>
>>> I have added more fixes to carbon-apimgt  now we can build carbon-apimgt
>>> components without any compilation errors.Further I updated corresponded
>>> carbon versions and added  latest APIM changes also. I have made a pull
>>> request [1] please merge it to the [2] repo. After that  please send the
>>> Pull request to [3].
>>>
>>>
>>> [1] https://github.com/wso2-dev/carbon-apimgt/pull/14
>>> [2] https://github.com/wso2-dev/carbon-apimgt
>>> [3] https://github.com/wso2/carbon-apimgt
>>>
>>> let me know any concerns.
>>>
>>> Regards
>>> Roshan.
>>>
>>>
>>> On Sat, Jan 10, 2015 at 11:38 AM, Prabath Abeysekera 
>>> wrote:
>>>
 Hi Everyone,

 Geeth and I had already fixed most of these issues in
 wso2-dev/carbon-apimgt repository. Appreciate if someone who's got access
 sending PRs to wso2/carbon-apimgt, can merge these changes.

 Cheers,
 Prabath

 On Fri, Jan 9, 2015 at 11:07 PM, Pulasthi Supun 
 wrote:

> Hi Roshan,
>
> We are installing several apim features in our product build. below is
> the list of features we are installing.
>
> org.wso2.carbon:org.wso2.carbon.apimgt.core.feature
> org.wso2.carbon:org.wso2.carbon.apimgt.interceptor.feature
> org.wso2.carbon:org.wso2.carbon.apimgt.publisher.feature
> org.wso2.carbon:org.wso2.carbon.apimgt.store.feature
> org.wso2.carbon:org.wso2.carbon.apimgt.startup.publisher.feature
>
> if we can get these features built even locally ( for now ) that would
> be great.
>
> Best Regards,
> Pulasthi
>
>
> On Fri, Jan 9, 2015 at 10:40 PM, Roshan Wijesena 
> wrote:
>
>> Hi Pulasthi,
>>
>> What are the components you guys have tried to build in Greg product?
>> please share the repos if possible. Then I can test it  locally  my self 
>> to
>> make sure things are working after the fix.
>>
>> Regards
>> Roshan
>>
>> On Fri, Jan 9, 2015 at 9:38 PM, Pulasthi Supun 
>> wrote:
>>
>>> Hi Roshan,
>>>
>>> Great, Thanks.
>>>
>>> Best Regards,
>>> Pulasthi
>>>
>>> On Fri, Jan 9, 2015 at 8:40 PM, Roshan Wijesena 
>>> wrote:
>>>
 Hi All,

 I had a look into this issue. While working on this I have
 encountered multiple compilation errors in carbon-apimgt. I have to fix
 them first. However, I will  update the progress here by tomorrow.

 Regards
 Roshan.



 On Fri, Jan 9, 2015 at 6:35 PM, Nuwan Dias  wrote:

> Adding Roshan. He will look into it.
>
> Thanks,
> NuwanD.
>
> On Fri, Jan 9, 2015 at 4:26 PM, Pulasthi Supun 
> wrote:
>
>> Hi All,
>>
>> The carbon-apimgt needs to be updated corresponding to the kernel
>> release. We are getting the following error when building the Greg 
>> product
>> and this is a blocker for us. The versions need to be updated.
>>
>> 
>> Installing org.wso2.carbon.tenant.deployment.feature.group
>> 4.3.0.SNAPSHOT.
>> Installation failed.
>> Cannot complete the install because one or more required items
>> could not be found.
>>  Software being installed: WSO2 Carbon - Api management Server
>> Interceptor Feature 4.3.0.SNAPSHOT
>> (org.wso2.carbon.apimgt.interceptor.feature.group 4.3.0.SNAPSHOT)
>> 

Re: [Dev] Error in pom file

[Sameera Jayasoma]

Very easy :) Place this inside the $CARBON_HOME directory and run.

Then inside the extracted-jars directory, do a grep

#!/bin/sh


find repository/components/plugins -iname *.jar > jar-list.txt


mkdir extracted-jars

cd extracted-jars


while read p; do

  a=${p#repository/components/plugins/}

  unzip ../$p -d $a

done < ../jar-list.txt

On Tue, Jan 13, 2015 at 6:01 PM, Pamod Sylvester  wrote:

> Hi All,
>
> When building we're experiencing the following,
>
> Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 Format
> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
> 0.0.0.${wso2_kernel_version} java.lang.IllegalArgumentException: Format
> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
> 0.0.0.${wso2_kernel_version}
>
> SupunM pointed out its possibly due to the property not being grabbed from
> the parent pom, as a solution it requires to search through the jars and
> figure out which jar has the string {wso2_kernel_version} in Manifest
> instead of the version. By any chance do any of you have a script written
> already to do that ?
>
> Thanks,
> Pamod
>
>
> On Tue, Jan 13, 2015 at 9:10 AM, Chandana Napagoda 
> wrote:
>
>> Thanks Kasun.
>>
>> Regards,
>> Chandana
>>
>> On Tue, Jan 13, 2015 at 9:06 AM, KasunG Gajasinghe 
>> wrote:
>>
>>> Hi Chandana,
>>>
>>> Merged the PR.
>>>
>>> On Tue, Jan 13, 2015 at 9:05 AM, Chandana Napagoda 
>>> wrote:
>>>
 Adding Dev,

 On Tue, Jan 13, 2015 at 6:54 AM, Chandana Napagoda 
 wrote:

> Hi Kalpa,
>
> Your PR was not automatically merged into wso2 repo. Can you please
> merge it[1]?
>
> [1]. https://github.com/wso2/carbon-qos/pull/10
>
> Thanks
>
>
>
> On Wed, Jan 7, 2015 at 3:58 PM, Kalpa Welivitigoda 
> wrote:
>
>> Hi Pulasthi,
>>
>> Fixed it and sent a PR https://github.com/wso2-dev/carbon-qos/pull/7
>>
>> On Wed, Jan 7, 2015 at 3:15 PM, Pulasthi Supun 
>> wrote:
>>
>>> Hi,
>>>
>>> The greg build is falling with the following error. It seems this is
>>> because the version in the pom [1] is missing a "}". please check line 
>>> 76
>>> in the pom.xml. please correct this ASAP.
>>>
>>>
>>> [INFO] Running Equinox P2 Publisher Application for Repository
>>> Generation
>>> [INFO] Command line:
>>> /bin/sh -c cd
>>> /home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen 
>>> &&
>>> /home/pulasthi/software/java/jdk1.6.0_45/jre/bin/java -jar
>>> /home/pulasthi/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
>>> -nosplash -application
>>> org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher -source
>>> /home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen/target/tmp.1420622170707/featureExtract
>>> -metadataRepository
>>> file:/home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen/target/p2-repo
>>> -metadataRepositoryName governance-profile-gen -artifactRepository
>>> file:/home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen/target/p2-repo
>>> -artifactRepositoryName governance-profile-gen -publishArtifacts
>>> -publishArtifactRepository -compress -append
>>> Generating metadata for ..
>>> Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0
>>> Format "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to 
>>> parse
>>> 0.0.0.${carbon_kernel_version java.lang.IllegalArgumentException: Format
>>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>>> 0.0.0.${carbon_kernel_version
>>>
>>> Product publishing ended with the following exception:
>>> java.lang.IllegalArgumentException: Format
>>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>>> 0.0.0.${carbon_kernel_version
>>> at
>>> org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275)
>>> at
>>> org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:89)
>>> at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79)
>>> at
>>> org.eclipse.equinox.p2.metadata.Version.parseVersion(Version.java:141)
>>> at
>>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.(FeatureEntry.java:63)
>>> at
>>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.createRequires(FeatureEntry.java:40)
>>> at
>>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.processImport(FeatureManifestParser.java:194)
>>> at
>>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.startElement(FeatureManifestParser.java:280)
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
>>> at
>>> com.sun.org.apach

Re: [Dev] WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature installation fails in IS Server P2 profile

[Gokul Balakrishnan]

Tested this now with Hasintha and the feature is installable now without
any issue. Since the versions are correctly specified in the modules, I
suspect this may have been because the proper archives were not present in
nexus and they have been synced up now.

On 13 January 2015 at 17:38, Hasintha Indrajee  wrote:

> [adding Gokul and Gihan]
>
> On Mon, Jan 12, 2015 at 2:37 PM, Hasintha Indrajee 
> wrote:
>
>> Hi all,
>>
>> Please note $subject. Refer the following trace for the error message
>> logged.
>>
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Data Bridge - Data Publisher
>> Aggregate Feature 4.3.0.SNAPSHOT
>> (org.wso2.carbon.databridge.datapublisher.feature.group 4.3.0.SNAPSHOT)
>>  Missing requirement: WSO2 Carbon - Data Bridge - Thrift Commons Server
>> Feature 4.3.0.SNAPSHOT
>> (org.wso2.carbon.databridge.commons.thrift.server.feature.group
>> 4.3.0.SNAPSHOT) requires 'org.wso2.carbon.core.server.feature.group
>> [4.3.0.SNAPSHOT,4.4.0)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature
>> 4.3.0.SNAPSHOT (org.wso2.carbon.databridge.datapublisher.feature.group
>> 4.3.0.SNAPSHOT)
>>   To: org.wso2.carbon.databridge.commons.thrift.server.feature.group
>> [4.3.0.SNAPSHOT]
>>
>>
>


-- 
*Balakrishnan Gokulakrishnan*
Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can a single WSDL file be generated for two Axis2 service classes?

[Sagara Gunathunga]

On Tue, Jan 13, 2015 at 5:33 PM, Rajeevan Vimalanathan 
wrote:

> Hi,
>
> I am looking into a JIRA[1] that relates to generating a WSDL file for an
> Axis2 service project in DevStudio. In this scenario, services.xml file
> contains two service elements inside a serviceGroup element. So the Axis2
> project contains two service classes.
>
> [1]https://wso2.org/jira/browse/TOOLS-2378
>
> Is it possible to generate a single WSDL file that describes both services
> in the project?
> Appreciate your response on this.
>

Generally in code-first approach web services frameworks assume one Java
class is map to one web service hence one WSDL per one service class, Axis2
also use same approach.

Thanks !

>
> Thanks,
> Rajeevan
>
> --
> Best Regards,
> V.Rajeevan
> Software Engineer,
> WSO2 Inc. :http://wso2.com
>
> Mobile : +94 773090875
> Email : rajeev...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error in pom file

[Pamod Sylvester]

Hi All,

When building we're experiencing the following,

Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 Format
"format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
0.0.0.${wso2_kernel_version} java.lang.IllegalArgumentException: Format
"format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
0.0.0.${wso2_kernel_version}

SupunM pointed out its possibly due to the property not being grabbed from
the parent pom, as a solution it requires to search through the jars and
figure out which jar has the string {wso2_kernel_version} in Manifest
instead of the version. By any chance do any of you have a script written
already to do that ?

Thanks,
Pamod


On Tue, Jan 13, 2015 at 9:10 AM, Chandana Napagoda 
wrote:

> Thanks Kasun.
>
> Regards,
> Chandana
>
> On Tue, Jan 13, 2015 at 9:06 AM, KasunG Gajasinghe 
> wrote:
>
>> Hi Chandana,
>>
>> Merged the PR.
>>
>> On Tue, Jan 13, 2015 at 9:05 AM, Chandana Napagoda 
>> wrote:
>>
>>> Adding Dev,
>>>
>>> On Tue, Jan 13, 2015 at 6:54 AM, Chandana Napagoda 
>>> wrote:
>>>
 Hi Kalpa,

 Your PR was not automatically merged into wso2 repo. Can you please
 merge it[1]?

 [1]. https://github.com/wso2/carbon-qos/pull/10

 Thanks



 On Wed, Jan 7, 2015 at 3:58 PM, Kalpa Welivitigoda 
 wrote:

> Hi Pulasthi,
>
> Fixed it and sent a PR https://github.com/wso2-dev/carbon-qos/pull/7
>
> On Wed, Jan 7, 2015 at 3:15 PM, Pulasthi Supun 
> wrote:
>
>> Hi,
>>
>> The greg build is falling with the following error. It seems this is
>> because the version in the pom [1] is missing a "}". please check line 76
>> in the pom.xml. please correct this ASAP.
>>
>>
>> [INFO] Running Equinox P2 Publisher Application for Repository
>> Generation
>> [INFO] Command line:
>> /bin/sh -c cd
>> /home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen &&
>> /home/pulasthi/software/java/jdk1.6.0_45/jre/bin/java -jar
>> /home/pulasthi/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
>> -nosplash -application
>> org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher -source
>> /home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen/target/tmp.1420622170707/featureExtract
>> -metadataRepository
>> file:/home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen/target/p2-repo
>> -metadataRepositoryName governance-profile-gen -artifactRepository
>> file:/home/pulasthi/wso2/gitsource/greg/product-greg/modules/p2-profile-gen/target/p2-repo
>> -artifactRepositoryName governance-profile-gen -publishArtifacts
>> -publishArtifactRepository -compress -append
>> Generating metadata for ..
>> Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0
>> Format "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to 
>> parse
>> 0.0.0.${carbon_kernel_version java.lang.IllegalArgumentException: Format
>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>> 0.0.0.${carbon_kernel_version
>>
>> Product publishing ended with the following exception:
>> java.lang.IllegalArgumentException: Format
>> "format(n[.n=0;[.n=0;[.S=[A-Za-z0-9_-];='';]]])" was unable to parse
>> 0.0.0.${carbon_kernel_version
>> at
>> org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275)
>> at
>> org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:89)
>> at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79)
>> at
>> org.eclipse.equinox.p2.metadata.Version.parseVersion(Version.java:141)
>> at
>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.(FeatureEntry.java:63)
>> at
>> org.eclipse.equinox.p2.publisher.eclipse.FeatureEntry.createRequires(FeatureEntry.java:40)
>> at
>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.processImport(FeatureManifestParser.java:194)
>> at
>> org.eclipse.equinox.internal.p2.publisher.eclipse.FeatureManifestParser.startElement(FeatureManifestParser.java:280)
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
>> at
>> com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
>> at
>> com.sun.org.apache.xerces.i

Re: [Dev] Build failed in Jenkins: product-es #4755

[Ayesha Dissanayaka]

Hi all,

Local build of product-es[1] is successful now. Necessary changes are
pushed to master branch[1]. We need to build carbon-governance[2] and
carbon-identity [3] repos locally, since their latest changes are not yet
merged into Jenkins build repos.

Once all these changes are merged into Jenkins repo, hopefully Jenkins
product-es build will also be successful.

[1] https://github.com/wso2-dev/product-es
[2] https://github.com/wso2-dev/carbon-governance
[3] https://github.com/wso2-dev/carbon-identity/

Thanks!
- Ayesha

On Tue, Jan 13, 2015 at 9:00 AM, Akalanka Pagoda Arachchi <
darsha...@wso2.com> wrote:

> Hi all,
>
> Due to this we're also not able to create a custom bundle for client. The
> product-esb dev build fails as follows.
>
> Installing org.wso2.carbon.service.mgt.server.feature.group 4.3.0.SNAPSHOT.
>
> Installation failed.
>
> Cannot complete the install because one or more required items could not
> be found.
>
>  Software being installed: WSO2 Carbon - Smooks Mediator Aggregated
> Feature 4.3.0.SNAPSHOT (org.wso2.carbon.smooks.feature.group 4.3.0.SNAPSHOT)
>
>  Missing requirement: WSO2 Carbon - Datasource Management Core Feature
> 4.3.0.SNAPSHOT (org.wso2.carbon.datasource.server.feature.group
> 4.3.0.SNAPSHOT) requires 'org.wso2.carbon.core.server.feature.group
> [4.3.0.SNAPSHOT,4.4.0)' but it could not be found
>
>  Cannot satisfy dependency:
>
>   From: WSO2 Carbon - Mediation Initializer Server Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.mediation.initializer.server.feature.group 4.3.0.SNAPSHOT)
>
>   To: org.wso2.carbon.datasource.server.feature.group [4.3.0,4.4.0)
>
>  Cannot satisfy dependency:
>
>   From: WSO2 Carbon - Smooks Mediator Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.mediator.smooks.server.feature.group 4.3.0.SNAPSHOT)
>
>   To: org.wso2.carbon.mediation.initializer.server.feature.group
> [4.3.0.SNAPSHOT,4.4.0)
>
>  Cannot satisfy dependency:
>
>   From: WSO2 Carbon - Smooks Mediator Aggregated Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.smooks.feature.group 4.3.0.SNAPSHOT)
>
>   To: org.wso2.carbon.mediator.smooks.server.feature.group [4.3.0.SNAPSHOT]
> Thanks,
> Akalanka
>
> On Mon, Jan 12, 2015 at 5:12 PM, Thushara Ranawaka 
> wrote:
>
>> Hi,
>>
>> Due to $subject we are unable to build product greg as well.
>>
>> Installing org.wso2.carbon.tenant.deployment.feature.group 4.3.0.SNAPSHOT.
>>
>> Installation failed.
>>
>> Cannot complete the install because one or more required items could not
>> be found.
>>
>>  Software being installed: WSO2 Enterprise Store Feature 2.0.0.SNAPSHOT
>> (org.wso2.es.feature.group 2.0.0.SNAPSHOT)
>>
>>  Missing requirement: WSO2 Enterprise Store Feature 2.0.0.SNAPSHOT
>> (org.wso2.es.feature.group 2.0.0.SNAPSHOT) requires
>> 'org.wso2.carbon.social.feature.group [1.1.0.SNAPSHOT,1.2.0)' but it could
>> not be found
>>
>> Application failed, log file location:
>> /Users/thushara/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1421061991962.log
>>
>>
>> Please look into the issue.
>>
>> On Mon, Jan 12, 2015 at 4:56 PM, Ayesha Dissanayaka 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are still getting the earlier mentioned ES build error, similar error
>>> discussed in [1].
>>> I have updated the carbon.kernel.version to 4.3.0 locally as mentioned
>>> earlier and in some-other relevant version changes. I built
>>> carbon-registry[2] and carbon-governance[3] repos locally with latest
>>> changes.
>>>
>>> When I tried to build BPS[4] locally it fails giving below error stack.
>>>
>>> Installation failed.
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Attachment Management Server
>>> Feature 4.3.0.SNAPSHOT (org.wso2.carbon.attachment.mgt.feature.group
>>> 4.3.0.SNAPSHOT)
>>>  Missing requirement: WSO2 Carbon - Attachment Management Server Feature
>>> 4.3.0.SNAPSHOT (org.wso2.carbon.attachment.mgt.feature.group
>>> 4.3.0.SNAPSHOT) requires 'org.wso2.carbon.core.feature.group
>>> [4.3.0.SNAPSHOT,4.4.0)' but it could not be found
>>> Application failed, log file location:
>>> /home/ayesha/WORK/cleanm3/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1421058011430.log
>>>
>>> Hence, we cannot pass the build fail point in ES at,
>>> Installation failed.
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Data Bridge - Data Publisher
>>> Aggregate Feature 4.3.0.SNAPSHOT
>>> (org.wso2.carbon.databridge.datapublisher.feature.group 4.3.0.SNAPSHOT)
>>>  Missing requirement: WSO2 Carbon - Data Bridge - Thrift Commons Server
>>> Feature 4.3.0.SNAPSHOT
>>> (org.wso2.carbon.databridge.commons.thrift.server.feature.group
>>> 4.3.0.SNAPSHOT) requires 'org.wso2.carbon.core.server.feature.group
>>> [4.3.0.SNAPSHOT,4.4.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature
>>> 4.

[Dev] [APIM] PizzaShack Sample: List of Pizzas not loaded in web application

[Yohanna Fernando]

As shown in diagram, the lists of pizzas are not loaded and I don't get the
screen which says:

"This App will be able to"

Has anyone come across this before and know if I'm missing something?
-- 
Yohanna Fernando
Training Specialist
WSO2 Inc.
 http://wso2.com

E-mail: yoha...@wso2.com
Cell: +94779021159

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature installation fails in IS Server P2 profile

[Hasintha Indrajee]

[adding Gokul and Gihan]

On Mon, Jan 12, 2015 at 2:37 PM, Hasintha Indrajee 
wrote:

> Hi all,
>
> Please note $subject. Refer the following trace for the error message
> logged.
>
> Installation failed.
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: WSO2 Carbon - Data Bridge - Data Publisher
> Aggregate Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.databridge.datapublisher.feature.group 4.3.0.SNAPSHOT)
>  Missing requirement: WSO2 Carbon - Data Bridge - Thrift Commons Server
> Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.databridge.commons.thrift.server.feature.group
> 4.3.0.SNAPSHOT) requires 'org.wso2.carbon.core.server.feature.group
> [4.3.0.SNAPSHOT,4.4.0)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature
> 4.3.0.SNAPSHOT (org.wso2.carbon.databridge.datapublisher.feature.group
> 4.3.0.SNAPSHOT)
>   To: org.wso2.carbon.databridge.commons.thrift.server.feature.group
> [4.3.0.SNAPSHOT]
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] 4.3.0 based server hang at startup.

[Supun Malinga]

Thanks Hasintha.

Apparently identity repo build has failed last couple of times.
https://wso2.org/jenkins/job/carbon-identity/

Can we make sure we get a snapshot deployment to nexus from this pls..

thanks,

On Tue, Jan 13, 2015 at 5:19 PM, Hasintha Indrajee 
wrote:

> Hi Supun,
>
> Changes are merged to org repo .
>
> On Tue, Jan 13, 2015 at 5:07 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> Can we merge the changes into org repo as well pls ?
>>
>> thanks,
>>
>> On Tue, Jan 13, 2015 at 1:15 PM, Ayesha Dissanayaka 
>> wrote:
>>
>>> Hi Pulasthi, Hasintha,
>>>
>>> Thanks a lot for the quick response. :)
>>>
>>> On Tue, Jan 13, 2015 at 12:33 PM, Hasintha Indrajee 
>>> wrote:
>>>
 Hi Ayesha,

 Required changes are done in wso2-dev repo.




 On Tue, Jan 13, 2015 at 12:17 PM, Pulasthi Mahawithana <
 pulast...@wso2.com> wrote:

> Hi Ayesha,
>
> Some of the changes that were made in the pull request has been
> reverted when the kernel 4.3.0 release merge is done. Hasintha will add 
> the
> required changes back.
>
> On Tue, Jan 13, 2015 at 12:11 PM, Ayesha Dissanayaka 
> wrote:
>
>> Hi all,
>>
>> ES server build on carbon.kernal.version- 4.3.0 server startup hangs
>> giving following stack trace.
>>
>> Carbon initialization is delayed due to the following unsatisfied
>> items:
>> [2015-01-13 11:55:19,238]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>> Module: org.wso2.carbon.security.mgt-4.3.0-SNAPSHOT
>> [2015-01-13 11:55:19,238]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>> OSGiAxis2Service: org.wso2.carbon.identity.sso.saml-4.3.0.SNAPSHOT
>> [2015-01-13 11:55:19,238]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>> OSGiAxis2Service: org.wso2.carbon.registry.ws.api-4.3.0.SNAPSHOT
>> [2015-01-13 11:55:19,238]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>> Module: rampart-trust-1.6.1.wso2v13-SNAPSHOT
>> [2015-01-13 11:55:19,238]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>> Module: rampart-core-1.6.1.wso2v13-SNAPSHOT
>> [2015-01-13 11:55:19,239]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>> OSGi Service: org.apache.axis2.engine.AxisObserver
>> [2015-01-13 11:55:19,239]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>> OSGiAxis2Service: org.wso2.carbon.security.mgt-4.3.0.SNAPSHOT
>>
>> I see that the same issue is discussed in threads [1] and [2].
>>
>> I noticed that there are two wss4j jars, in the latest ES pack.
>> wss4j_1.5.11.wso2v7
>> wss4j_1.5.11.wso2v8-SNAPSHOT
>>
>> According to thread [2] , there it is fixed in [3]. But, this change
>> seems not available in current wso2-dev/carbon-identity repo.[4]
>>
>> Due to this ES build fails at automation test modules.
>>
>> [1] [Dev] Carbon 4.3.0 snapshot based server hangs
>> [2] [Dev] [Important] wss4j 1.5.11.wso2v7 bundle does not contain
>> Dynamic Imports
>> [3]
>> https://github.com/pulasthi7/carbon-identity/commit/d843ae38178fbb66a0fa8386f7f183d8b71c621d
>> [4] https://github.com/wso2-dev/carbon-identity/blob/master/pom.xml
>> Thanks!
>> -Ayesha
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>
>
>
> --
> *Pulasthi Mahawithana*
> Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022
> Blog: http://blog.pulasthi.org
>


>>>
>>>
>>> --
>>> *Ayesha Dissanayaka*
>>> Software Engineer,
>>> WSO2, Inc : http://wso2.com
>>> 
>>> 20, Palmgrove Avenue, Colombo 3
>>> E-Mail: aye...@wso2.com 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> email: sup...@wso2.com 
>> mobile: +94 (0)71 56 91 321
>>
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Can a single WSDL file be generated for two Axis2 service classes?

[Rajeevan Vimalanathan]

Hi,

I am looking into a JIRA[1] that relates to generating a WSDL file for an
Axis2 service project in DevStudio. In this scenario, services.xml file
contains two service elements inside a serviceGroup element. So the Axis2
project contains two service classes.

[1]https://wso2.org/jira/browse/TOOLS-2378

Is it possible to generate a single WSDL file that describes both services
in the project?
Appreciate your response on this.

Thanks,
Rajeevan

-- 
Best Regards,
V.Rajeevan
Software Engineer,
WSO2 Inc. :http://wso2.com

Mobile : +94 773090875
Email : rajeev...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] 4.3.0 based server hang at startup.

[Hasintha Indrajee]

Hi Supun,

Changes are merged to org repo .

On Tue, Jan 13, 2015 at 5:07 PM, Supun Malinga  wrote:

> Hi,
>
> Can we merge the changes into org repo as well pls ?
>
> thanks,
>
> On Tue, Jan 13, 2015 at 1:15 PM, Ayesha Dissanayaka 
> wrote:
>
>> Hi Pulasthi, Hasintha,
>>
>> Thanks a lot for the quick response. :)
>>
>> On Tue, Jan 13, 2015 at 12:33 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Hi Ayesha,
>>>
>>> Required changes are done in wso2-dev repo.
>>>
>>>
>>>
>>>
>>> On Tue, Jan 13, 2015 at 12:17 PM, Pulasthi Mahawithana <
>>> pulast...@wso2.com> wrote:
>>>
 Hi Ayesha,

 Some of the changes that were made in the pull request has been
 reverted when the kernel 4.3.0 release merge is done. Hasintha will add the
 required changes back.

 On Tue, Jan 13, 2015 at 12:11 PM, Ayesha Dissanayaka 
 wrote:

> Hi all,
>
> ES server build on carbon.kernal.version- 4.3.0 server startup hangs
> giving following stack trace.
>
> Carbon initialization is delayed due to the following unsatisfied
> items:
> [2015-01-13 11:55:19,238]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> Module: org.wso2.carbon.security.mgt-4.3.0-SNAPSHOT
> [2015-01-13 11:55:19,238]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGiAxis2Service: org.wso2.carbon.identity.sso.saml-4.3.0.SNAPSHOT
> [2015-01-13 11:55:19,238]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGiAxis2Service: org.wso2.carbon.registry.ws.api-4.3.0.SNAPSHOT
> [2015-01-13 11:55:19,238]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> Module: rampart-trust-1.6.1.wso2v13-SNAPSHOT
> [2015-01-13 11:55:19,238]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> Module: rampart-core-1.6.1.wso2v13-SNAPSHOT
> [2015-01-13 11:55:19,239]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.apache.axis2.engine.AxisObserver
> [2015-01-13 11:55:19,239]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGiAxis2Service: org.wso2.carbon.security.mgt-4.3.0.SNAPSHOT
>
> I see that the same issue is discussed in threads [1] and [2].
>
> I noticed that there are two wss4j jars, in the latest ES pack.
> wss4j_1.5.11.wso2v7
> wss4j_1.5.11.wso2v8-SNAPSHOT
>
> According to thread [2] , there it is fixed in [3]. But, this change
> seems not available in current wso2-dev/carbon-identity repo.[4]
>
> Due to this ES build fails at automation test modules.
>
> [1] [Dev] Carbon 4.3.0 snapshot based server hangs
> [2] [Dev] [Important] wss4j 1.5.11.wso2v7 bundle does not contain
> Dynamic Imports
> [3]
> https://github.com/pulasthi7/carbon-identity/commit/d843ae38178fbb66a0fa8386f7f183d8b71c621d
> [4] https://github.com/wso2-dev/carbon-identity/blob/master/pom.xml
> Thanks!
> -Ayesha
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>



 --
 *Pulasthi Mahawithana*
 Software Engineer
 WSO2 Inc., http://wso2.com/
 Mobile: +94-71-5179022
 Blog: http://blog.pulasthi.org

>>>
>>>
>>
>>
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] 4.3.0 based server hang at startup.

[Supun Malinga]

Hi,

Can we merge the changes into org repo as well pls ?

thanks,

On Tue, Jan 13, 2015 at 1:15 PM, Ayesha Dissanayaka  wrote:

> Hi Pulasthi, Hasintha,
>
> Thanks a lot for the quick response. :)
>
> On Tue, Jan 13, 2015 at 12:33 PM, Hasintha Indrajee 
> wrote:
>
>> Hi Ayesha,
>>
>> Required changes are done in wso2-dev repo.
>>
>>
>>
>>
>> On Tue, Jan 13, 2015 at 12:17 PM, Pulasthi Mahawithana <
>> pulast...@wso2.com> wrote:
>>
>>> Hi Ayesha,
>>>
>>> Some of the changes that were made in the pull request has been reverted
>>> when the kernel 4.3.0 release merge is done. Hasintha will add the required
>>> changes back.
>>>
>>> On Tue, Jan 13, 2015 at 12:11 PM, Ayesha Dissanayaka 
>>> wrote:
>>>
 Hi all,

 ES server build on carbon.kernal.version- 4.3.0 server startup hangs
 giving following stack trace.

 Carbon initialization is delayed due to the following unsatisfied items:
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 Module: org.wso2.carbon.security.mgt-4.3.0-SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGiAxis2Service: org.wso2.carbon.identity.sso.saml-4.3.0.SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGiAxis2Service: org.wso2.carbon.registry.ws.api-4.3.0.SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 Module: rampart-trust-1.6.1.wso2v13-SNAPSHOT
 [2015-01-13 11:55:19,238]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 Module: rampart-core-1.6.1.wso2v13-SNAPSHOT
 [2015-01-13 11:55:19,239]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGi Service: org.apache.axis2.engine.AxisObserver
 [2015-01-13 11:55:19,239]  WARN
 {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
 OSGiAxis2Service: org.wso2.carbon.security.mgt-4.3.0.SNAPSHOT

 I see that the same issue is discussed in threads [1] and [2].

 I noticed that there are two wss4j jars, in the latest ES pack.
 wss4j_1.5.11.wso2v7
 wss4j_1.5.11.wso2v8-SNAPSHOT

 According to thread [2] , there it is fixed in [3]. But, this change
 seems not available in current wso2-dev/carbon-identity repo.[4]

 Due to this ES build fails at automation test modules.

 [1] [Dev] Carbon 4.3.0 snapshot based server hangs
 [2] [Dev] [Important] wss4j 1.5.11.wso2v7 bundle does not contain
 Dynamic Imports
 [3]
 https://github.com/pulasthi7/carbon-identity/commit/d843ae38178fbb66a0fa8386f7f183d8b71c621d
 [4] https://github.com/wso2-dev/carbon-identity/blob/master/pom.xml
 Thanks!
 -Ayesha
 --
 *Ayesha Dissanayaka*
 Software Engineer,
 WSO2, Inc : http://wso2.com
 
 20, Palmgrove Avenue, Colombo 3
 E-Mail: aye...@wso2.com 

>>>
>>>
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022
>>> Blog: http://blog.pulasthi.org
>>>
>>
>>
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading jcifs from 0.8.3 to 1.3.17

[Sandamal Weerasinghe]

Hi all,

I found the required file in the following location.

http://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jcifs/0.8.3-wso2v1/

Thanks.

Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd

Mobile - +94-77-144-9640

On Tue, Jan 13, 2015 at 4:43 PM, Sandamal Weerasinghe 
wrote:

> Hi all,
>
> I'm in the process of upgrading the jcifs jar in order to fix [1]. The
> jcifs_0.8.3.wso2v1.jar has been released with Carbon 3.1.0. My I know the
> svn location of branch 3.1.0 in the public svn repository?
>
> [1] https://wso2.org/jira/browse/ESBJAVA-3449
>
> Thanks.
>
> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
>
> Mobile - +94-77-144-9640
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Upgrading jcifs from 0.8.3 to 1.3.17

[Sandamal Weerasinghe]

Hi all,

I'm in the process of upgrading the jcifs jar in order to fix [1]. The
jcifs_0.8.3.wso2v1.jar has been released with Carbon 3.1.0. My I know the
svn location of branch 3.1.0 in the public svn repository?

[1] https://wso2.org/jira/browse/ESBJAVA-3449

Thanks.

Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd

Mobile - +94-77-144-9640
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Please review and commit patch

[Abimaran Kugathasan]

Hi Nuwan


Please commit following JIRA

1. https://wso2.org/jira/browse/APIMANAGER-3204


-- 
Thanks
Abimaran Kugathasan

Software Engineer | WSO2 Inc
Data & APIs Technologies Team
Mobile : +94 773922820


  
  
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Please review and comit patches

[Abimaran Kugathasan]

Hi Nuwan,


These JIRAs are not commited yet. Please commit them.

On Mon, Dec 22, 2014 at 2:33 PM, Abimaran Kugathasan 
wrote:

> $subject please for following JIRAs
>
> 1. https://wso2.org/jira/browse/APIMANAGER-2780
> 2. https://wso2.org/jira/browse/APIMANAGER-2965
> 3. https://wso2.org/jira/browse/APIMANAGER-3228
> 4. https://wso2.org/jira/browse/APIMANAGER-3231
>
> --
> Thanks
> Abimaran Kugathasan
>
> Software Engineer | WSO2 Inc
> Data & APIs Technologies Team
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>


-- 
Thanks
Abimaran Kugathasan

Software Engineer | WSO2 Inc
Data & APIs Technologies Team
Mobile : +94 773922820


  
  
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Urgent] Updating carbon-apimgt to use kernel version 4.3.0 instead of 4.3.0-SNAPSHOT

[Pulasthi Supun]

Hi Roshan,

We are still getting errors during feature installations.

Installing org.wso2.carbon.tenant.deployment.feature.group 4.3.0.SNAPSHOT.
Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - API Store Feature 4.3.0.SNAPSHOT
(org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT)
 Missing requirement: WSO2 Carbon - API Store Feature 4.3.0.SNAPSHOT
(org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT) requires
'org.wso2.carbon.core.server.feature.group [4.3.0.SNAPSHOT,4.4.0)' but it
could not be found
Application failed, log file location:
/home/greg/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1421140548600.log

These also need to be corrected.

Best Regards,
Pulasthi

On Sun, Jan 11, 2015 at 10:59 PM, Pulasthi Supun  wrote:

> Hi Nuwan/Ruwan
>
> Can someone merge this pull ASAP. And btw the build still seems to fail
> under a clean repo build.
>
> Best Regards,
> Pulasthi
>
> On Sat, Jan 10, 2015 at 8:12 PM, Roshan Wijesena  wrote:
>
>> Thanks Prabath.
>>
>> Hi NuwanD,
>>
>> I have added more fixes to carbon-apimgt  now we can build carbon-apimgt
>> components without any compilation errors.Further I updated corresponded
>> carbon versions and added  latest APIM changes also. I have made a pull
>> request [1] please merge it to the [2] repo. After that  please send the
>> Pull request to [3].
>>
>>
>> [1] https://github.com/wso2-dev/carbon-apimgt/pull/14
>> [2] https://github.com/wso2-dev/carbon-apimgt
>> [3] https://github.com/wso2/carbon-apimgt
>>
>> let me know any concerns.
>>
>> Regards
>> Roshan.
>>
>>
>> On Sat, Jan 10, 2015 at 11:38 AM, Prabath Abeysekera 
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> Geeth and I had already fixed most of these issues in
>>> wso2-dev/carbon-apimgt repository. Appreciate if someone who's got access
>>> sending PRs to wso2/carbon-apimgt, can merge these changes.
>>>
>>> Cheers,
>>> Prabath
>>>
>>> On Fri, Jan 9, 2015 at 11:07 PM, Pulasthi Supun 
>>> wrote:
>>>
 Hi Roshan,

 We are installing several apim features in our product build. below is
 the list of features we are installing.

 org.wso2.carbon:org.wso2.carbon.apimgt.core.feature
 org.wso2.carbon:org.wso2.carbon.apimgt.interceptor.feature
 org.wso2.carbon:org.wso2.carbon.apimgt.publisher.feature
 org.wso2.carbon:org.wso2.carbon.apimgt.store.feature
 org.wso2.carbon:org.wso2.carbon.apimgt.startup.publisher.feature

 if we can get these features built even locally ( for now ) that would
 be great.

 Best Regards,
 Pulasthi


 On Fri, Jan 9, 2015 at 10:40 PM, Roshan Wijesena 
 wrote:

> Hi Pulasthi,
>
> What are the components you guys have tried to build in Greg product?
> please share the repos if possible. Then I can test it  locally  my self 
> to
> make sure things are working after the fix.
>
> Regards
> Roshan
>
> On Fri, Jan 9, 2015 at 9:38 PM, Pulasthi Supun 
> wrote:
>
>> Hi Roshan,
>>
>> Great, Thanks.
>>
>> Best Regards,
>> Pulasthi
>>
>> On Fri, Jan 9, 2015 at 8:40 PM, Roshan Wijesena 
>> wrote:
>>
>>> Hi All,
>>>
>>> I had a look into this issue. While working on this I have
>>> encountered multiple compilation errors in carbon-apimgt. I have to fix
>>> them first. However, I will  update the progress here by tomorrow.
>>>
>>> Regards
>>> Roshan.
>>>
>>>
>>>
>>> On Fri, Jan 9, 2015 at 6:35 PM, Nuwan Dias  wrote:
>>>
 Adding Roshan. He will look into it.

 Thanks,
 NuwanD.

 On Fri, Jan 9, 2015 at 4:26 PM, Pulasthi Supun 
 wrote:

> Hi All,
>
> The carbon-apimgt needs to be updated corresponding to the kernel
> release. We are getting the following error when building the Greg 
> product
> and this is a blocker for us. The versions need to be updated.
>
> 
> Installing org.wso2.carbon.tenant.deployment.feature.group
> 4.3.0.SNAPSHOT.
> Installation failed.
> Cannot complete the install because one or more required items
> could not be found.
>  Software being installed: WSO2 Carbon - Api management Server
> Interceptor Feature 4.3.0.SNAPSHOT
> (org.wso2.carbon.apimgt.interceptor.feature.group 4.3.0.SNAPSHOT)
>  Missing requirement: org.wso2.carbon.apimgt.interceptor
> 4.3.0.SNAPSHOT (org.wso2.carbon.apimgt.interceptor 4.3.0.SNAPSHOT) 
> requires
> 'package org.wso2.carbon.core 4.3.0.SNAPSHOT' but it could not be 
> found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Api management Server Interceptor Feature
> 4.3.0.SNAPSHOT (org.wso2.carbon.apimgt.intercept

Re: [Dev] How to find the coordinator node of a cluster using hazelcast agent.

[Afkham Azeez]

if(hazelcastClusteringAgent.isCoordinator()){
primaryHazelcastInstance.getCluster().getLocalMember().
getSocketAddress()
}

On Tue, Jan 13, 2015 at 3:04 PM, Sajini De Silva  wrote:

> Hi Azeez,
>
> primaryHazelcastInstance.getCluster().getLocalMember().getSocketAddress()
> will give the socket address of the node which this method is calling.
>
> Is there a way to get the coordinator node's IP address and port for the
> nodes other than the coordinator? In my knowledge currently this feature is
> not supported by kernel.
>
> Thank you,
> Sajini
>
> On Tue, Jan 13, 2015 at 2:44 PM, Afkham Azeez  wrote:
>
>>
>> primaryHazelcastInstance.getCluster().getLocalMember().getSocketAddress()
>>
>>
>> On Tue, Jan 13, 2015 at 1:40 PM, Hemika Kodikara  wrote:
>>
>>> Hi Azeez,
>>>
>>> Yes, HazelcastInstance is there. But it doesn't provide a method to get
>>> the coordinator node IP address and so.
>>>
>>> Thanks,
>>> Hemika
>>>
>>> Hemika Kodikara
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middleware
>>> http://wso2.com
>>>
>>> Mobile : +9477762
>>>
>>> On Tue, Jan 13, 2015 at 1:30 PM, Afkham Azeez  wrote:
>>>
 Yes, get the HazelcastInstance OSGi service, and then using Hazelcast
 APIs you should be able to get the required information.

 Azeez

 On Tue, Jan 13, 2015 at 1:25 PM, Hemika Kodikara 
 wrote:

> Looping in Azeez, Sameera and Kishanthan.
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Tue, Jan 13, 2015 at 12:35 PM, Hemika Kodikara 
> wrote:
>
>> Hi All,
>>
>> I have a requirement to show the IP addresses and ports of the nodes
>> in a cluster on a UI page. But I also have to indicate which node is the
>> coordinator node. Currently I am only able to to find whether the current
>> node is the coordinator node or not using the "isCoordinator" method in
>> "HazelcastClusteringAgent" class.
>>
>> Is there way to find the coordinator node's IP address and port of
>> the cluster?
>>
>> Regards,
>> Hemika
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>
>


 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * *
 *email: **az...@wso2.com* 
 * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
 *http://blog.afkham.org* 
 *twitter: **http://twitter.com/afkham_azeez*
 
 *linked-in: **http://lk.linkedin.com/in/afkhamazeez
 *

 *Lean . Enterprise . Middleware*

>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Sajini De SIlva
> Software Engineer; WSO2 Inc.; http://wso2.com ,
> Email: saj...@wso2.com
> Blog: http://sajinid.blogspot.com/
> Git hub profile: https://github.com/sajinidesilva
>
> Phone: +94 712797729
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to find the coordinator node of a cluster using hazelcast agent.

[Sajini De Silva]

Hi Azeez,

primaryHazelcastInstance.getCluster().getLocalMember().getSocketAddress()
will give the socket address of the node which this method is calling.

Is there a way to get the coordinator node's IP address and port for the
nodes other than the coordinator? In my knowledge currently this feature is
not supported by kernel.

Thank you,
Sajini

On Tue, Jan 13, 2015 at 2:44 PM, Afkham Azeez  wrote:

>
> primaryHazelcastInstance.getCluster().getLocalMember().getSocketAddress()
>
>
> On Tue, Jan 13, 2015 at 1:40 PM, Hemika Kodikara  wrote:
>
>> Hi Azeez,
>>
>> Yes, HazelcastInstance is there. But it doesn't provide a method to get
>> the coordinator node IP address and so.
>>
>> Thanks,
>> Hemika
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>> On Tue, Jan 13, 2015 at 1:30 PM, Afkham Azeez  wrote:
>>
>>> Yes, get the HazelcastInstance OSGi service, and then using Hazelcast
>>> APIs you should be able to get the required information.
>>>
>>> Azeez
>>>
>>> On Tue, Jan 13, 2015 at 1:25 PM, Hemika Kodikara 
>>> wrote:
>>>
 Looping in Azeez, Sameera and Kishanthan.

 Hemika Kodikara
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middleware
 http://wso2.com

 Mobile : +9477762

 On Tue, Jan 13, 2015 at 12:35 PM, Hemika Kodikara 
 wrote:

> Hi All,
>
> I have a requirement to show the IP addresses and ports of the nodes
> in a cluster on a UI page. But I also have to indicate which node is the
> coordinator node. Currently I am only able to to find whether the current
> node is the coordinator node or not using the "isCoordinator" method in
> "HazelcastClusteringAgent" class.
>
> Is there way to find the coordinator node's IP address and port of the
> cluster?
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * *
>>> *email: **az...@wso2.com* 
>>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: **http://twitter.com/afkham_azeez*
>>> 
>>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919blog: **http://blog.afkham.org*
> 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Sajini De SIlva
Software Engineer; WSO2 Inc.; http://wso2.com ,
Email: saj...@wso2.com
Blog: http://sajinid.blogspot.com/
Git hub profile: https://github.com/sajinidesilva

Phone: +94 712797729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Refresh Proxy UI after adding new mediator

[Maheeka Jayasuriya]

Hi All,

Is there any solution on this?


Thanks,

Maheeka Jayasuriya
Software Engineer
Mobile : +9450661

On Wed, Jan 7, 2015 at 10:34 AM, Maheeka Jayasuriya 
wrote:

> Hi All,
>
> I am developing a new mediator for ESB, ForEach Mediator and have
> successfully have it working in an ESB snapshot.
>
> The behavior of the UI is somewhat similar to Iterate Mediator, where at
> the time of saving the configurations for the mediator, a target is
> automatically added to the ForEach Mediator. However, in this case,
> although the target is added, it is not visible in the Design View, until
> it is refreshed (by another event like adding/removing another mediator).
> How do I fix this to refresh the UI at the time of saving?
>
> Thanks,
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Automated Testing of Email Sending Functionality of EMM

[Krishantha Samaraweera]

Can you list the steps required to manually verify the scenario. We have
recently implemented GreenMail sever utility for test framework. We can
propose how to automate based on the manual steps.

Thanks,
Krishantha.

On Tue, Jan 13, 2015 at 9:14 AM, Inosh Perera  wrote:

> Hi Krishantha,
> EMM 1.1.0 uses, require('email') available in Jaggery to send email. The
> configurations are stored in the registry. So it is not necessary to
> configure mail transport AFAIK.
> Adding the mobile team.
>
> Regards,
> Inosh
>
>
> On Mon, Jan 12, 2015 at 6:09 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Do you need to configure mail transport in this case ? if yes, in which
>> file ?
>>
>> Thanks,
>> Krishantha
>>
>> On Mon, Jan 12, 2015 at 3:40 PM, Dilan Udara Ariyaratne 
>> wrote:
>>
>>> Hi Folks,
>>>
>>> I am checking the feasibility of writing an automated test case for the
>>> email
>>> sending functionality of emm.
>>>
>>> When a user is created, an invitation email is sent to the corresponding
>>> user to register the device.
>>>
>>> sendEmail() is currently a jaggery function and is executed via a
>>> non-exposed api to the outside
>>> within EMM Jaggery web application.
>>>
>>> What is the best possible way to test this functionality?
>>> Is there a recommended SMTP mail server to use?
>>>
>>> If I am using Selenium, to verify "success", I need to capture the
>>> status message
>>> of a dialog popup. How can I do this using Selenium?
>>>
>>> Appreciate any feedback on this.
>>>
>>> Thanks.
>>>
>>> *Dilan U. Ariyaratne*
>>> Software Engineer
>>> WSO2 Inc. 
>>> Mobile: +94775149066
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> 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
>>
>>
>
>
> --
> Inosh Perera
> Software Engineer, WSO2 Inc.
> Tel: 0785293686
>



-- 
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

Re: [Dev] How to find the coordinator node of a cluster using hazelcast agent.

[Afkham Azeez]

primaryHazelcastInstance.getCluster().getLocalMember().getSocketAddress()


On Tue, Jan 13, 2015 at 1:40 PM, Hemika Kodikara  wrote:

> Hi Azeez,
>
> Yes, HazelcastInstance is there. But it doesn't provide a method to get
> the coordinator node IP address and so.
>
> Thanks,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Tue, Jan 13, 2015 at 1:30 PM, Afkham Azeez  wrote:
>
>> Yes, get the HazelcastInstance OSGi service, and then using Hazelcast
>> APIs you should be able to get the required information.
>>
>> Azeez
>>
>> On Tue, Jan 13, 2015 at 1:25 PM, Hemika Kodikara  wrote:
>>
>>> Looping in Azeez, Sameera and Kishanthan.
>>>
>>> Hemika Kodikara
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middleware
>>> http://wso2.com
>>>
>>> Mobile : +9477762
>>>
>>> On Tue, Jan 13, 2015 at 12:35 PM, Hemika Kodikara 
>>> wrote:
>>>
 Hi All,

 I have a requirement to show the IP addresses and ports of the nodes in
 a cluster on a UI page. But I also have to indicate which node is the
 coordinator node. Currently I am only able to to find whether the current
 node is the coordinator node or not using the "isCoordinator" method in
 "HazelcastClusteringAgent" class.

 Is there way to find the coordinator node's IP address and port of the
 cluster?

 Regards,
 Hemika

 Hemika Kodikara
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middleware
 http://wso2.com

 Mobile : +9477762

>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Creating a tool to take thread dumps and analyze thread info

[Buddhi Senarathna]

Hi krishantha.

noted and thanks.

On Tue, Jan 13, 2015 at 2:41 PM, Krishantha Samaraweera  wrote:

> Please follow standard maven directory structure to add tests, you can use
> src/test/ directory.
>
> Better to generate jar file at run time using maven and get it copied to
> src/test/resources directory.
>
> Thanks,
> Krishantha.
>
> On Tue, Jan 13, 2015 at 9:12 AM, Buddhi Senarathna 
> wrote:
>
>> Hi krishantha.
>>
>> Where should i have to add this test case and where should i have to
>> place this deadlock.jar file.
>>
>> please give me an advise.
>>
>> thanks.
>>
>> On Tue, Jan 13, 2015 at 8:18 AM, Buddhi Senarathna 
>> wrote:
>>
>>> Hi krishantha,
>>>
>>> sure thing. i'll do that.
>>>
>>> thanks
>>>
>>> On Tue, Jan 13, 2015 at 8:15 AM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
 Hi Buddhi,

 Please add deadlock sample as a test case for your work.

 +1 for using Runtime.exec to trigger the class.

 Thanks,
 Krishantha.

 On Tue, Jan 13, 2015 at 7:51 AM, Buddhi Senarathna 
 wrote:

> Hi krishantha,
>
> as you guided, i had started to create the thread analyses sample.
> creating deadlock part is already done.
>
> 1. what else should i have to do?
> 2. I'm thinking of bundle this class as a jar file and use java
> Processbuilder class or Runtime.exec methods to execute it as a new
> process. what is your opinion on that?
>
> note: please find my last github pull request bellow here:
> https://github.com/wso2-dev/carbon-platform-integration/pull/23/files
> 
>
> thanks.
>
> On Wed, Jan 7, 2015 at 11:09 AM, Buddhi Senarathna 
> wrote:
>
>> Hi all,
>> after having a first code review, it has been suggested to do
>> following changes.
>>
>>1. rename the class name according to the purpose
>>2. change pid to integer type variable
>>3. use enum values provided by the API where its possible
>>4. mbeanobject return set, but returns only one object
>>5. change methods to use query filter and not
>>6. no need to return list in getThreadmxbeanobjects
>>7. pass the thread type as a parameter
>>8. getallthreadids - pass the bean as a parameter to filter
>>inside the method
>>9. change parameter  as  in the getthreadcount
>>method
>>10. rename input parameters in methods to meaningful names
>>11. getthreaddump public
>>12. overload gethreaddump method/ use this where ever can be used
>>13. save the original thread dump, do not append additional info
>>14. do not override the dump file with same name, append the time
>>stamp
>>15. move file-name to global parameter
>>16. close the streams in finnaly block
>>17. assign fullthreaddump to null after finish process
>>18. getdeadlockthreads public
>>19. check for null value in createthreaddumpfile.
>>
>> now i'm currently working on this.
>> thanks.
>>
>> On Tue, Jan 6, 2015 at 10:16 AM, Buddhi Senarathna 
>> wrote:
>>
>>> hi all,
>>>
>>>
>>> My task of creating a tool to take thread dumps and analyze thread
>>> info as test framework utility is almost finished.
>>>
>>> to had cover these task.
>>>
>>>1. access to a process remotely using process id.
>>>2. get thread dump of that remote process .
>>>3. expose necessary informations of thread dump using some
>>>methods in realtime.
>>>4. give a method to write thread dump into a file.
>>>
>>> to do this I used JMX Api and tools.jar library which provides JDK.
>>> used java version is 1.6.0_32.
>>>
>>> thank you.
>>>
>>> On Wed, Dec 24, 2014 at 11:23 AM, Buddhi Senarathna <
>>> budd...@wso2.com> wrote:
>>>
 Hi krishantha,
 noted and will change it in next update.

 thanks

 On Wed, Dec 24, 2014 at 11:21 AM, Buddhi Senarathna <
 budd...@wso2.com> wrote:

> Hi hasitha,
> thanks a lot, but i'm using JMX api for this. j
>
> On Tue, Dec 23, 2014 at 6:27 PM, Hasitha Aravinda <
> hasi...@wso2.com> wrote:
>
>> Hi Buddi,
>>
>> Are you using JStack ? By default, java thread dump does not
>> record lock owners for locks. If you use jstack, use "-l"
>> parameter as well [1]. (eg: jstack -l "pid"  ). This params
>>  records lock owner information only for synchronized blocks.
>> Which is usefull to detect possible deadlocks.
>>
>> [1] -
>> http://docs.oracle.com/javase/7/docs/technotes/tools/share/jstack.html
>>
>>

Re: [Dev] Creating a tool to take thread dumps and analyze thread info

[Krishantha Samaraweera]

Please follow standard maven directory structure to add tests, you can use
src/test/ directory.

Better to generate jar file at run time using maven and get it copied to
src/test/resources directory.

Thanks,
Krishantha.

On Tue, Jan 13, 2015 at 9:12 AM, Buddhi Senarathna  wrote:

> Hi krishantha.
>
> Where should i have to add this test case and where should i have to place
> this deadlock.jar file.
>
> please give me an advise.
>
> thanks.
>
> On Tue, Jan 13, 2015 at 8:18 AM, Buddhi Senarathna 
> wrote:
>
>> Hi krishantha,
>>
>> sure thing. i'll do that.
>>
>> thanks
>>
>> On Tue, Jan 13, 2015 at 8:15 AM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Hi Buddhi,
>>>
>>> Please add deadlock sample as a test case for your work.
>>>
>>> +1 for using Runtime.exec to trigger the class.
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>> On Tue, Jan 13, 2015 at 7:51 AM, Buddhi Senarathna 
>>> wrote:
>>>
 Hi krishantha,

 as you guided, i had started to create the thread analyses sample.
 creating deadlock part is already done.

 1. what else should i have to do?
 2. I'm thinking of bundle this class as a jar file and use java
 Processbuilder class or Runtime.exec methods to execute it as a new
 process. what is your opinion on that?

 note: please find my last github pull request bellow here:
 https://github.com/wso2-dev/carbon-platform-integration/pull/23/files
 

 thanks.

 On Wed, Jan 7, 2015 at 11:09 AM, Buddhi Senarathna 
 wrote:

> Hi all,
> after having a first code review, it has been suggested to do
> following changes.
>
>1. rename the class name according to the purpose
>2. change pid to integer type variable
>3. use enum values provided by the API where its possible
>4. mbeanobject return set, but returns only one object
>5. change methods to use query filter and not
>6. no need to return list in getThreadmxbeanobjects
>7. pass the thread type as a parameter
>8. getallthreadids - pass the bean as a parameter to filter inside
>the method
>9. change parameter  as  in the getthreadcount
>method
>10. rename input parameters in methods to meaningful names
>11. getthreaddump public
>12. overload gethreaddump method/ use this where ever can be used
>13. save the original thread dump, do not append additional info
>14. do not override the dump file with same name, append the time
>stamp
>15. move file-name to global parameter
>16. close the streams in finnaly block
>17. assign fullthreaddump to null after finish process
>18. getdeadlockthreads public
>19. check for null value in createthreaddumpfile.
>
> now i'm currently working on this.
> thanks.
>
> On Tue, Jan 6, 2015 at 10:16 AM, Buddhi Senarathna 
> wrote:
>
>> hi all,
>>
>>
>> My task of creating a tool to take thread dumps and analyze thread
>> info as test framework utility is almost finished.
>>
>> to had cover these task.
>>
>>1. access to a process remotely using process id.
>>2. get thread dump of that remote process .
>>3. expose necessary informations of thread dump using some
>>methods in realtime.
>>4. give a method to write thread dump into a file.
>>
>> to do this I used JMX Api and tools.jar library which provides JDK.
>> used java version is 1.6.0_32.
>>
>> thank you.
>>
>> On Wed, Dec 24, 2014 at 11:23 AM, Buddhi Senarathna > > wrote:
>>
>>> Hi krishantha,
>>> noted and will change it in next update.
>>>
>>> thanks
>>>
>>> On Wed, Dec 24, 2014 at 11:21 AM, Buddhi Senarathna <
>>> budd...@wso2.com> wrote:
>>>
 Hi hasitha,
 thanks a lot, but i'm using JMX api for this. j

 On Tue, Dec 23, 2014 at 6:27 PM, Hasitha Aravinda >>> > wrote:

> Hi Buddi,
>
> Are you using JStack ? By default, java thread dump does not
> record lock owners for locks. If you use jstack, use "-l"
> parameter as well [1]. (eg: jstack -l "pid"  ). This params
>  records lock owner information only for synchronized blocks.
> Which is usefull to detect possible deadlocks.
>
> [1] -
> http://docs.oracle.com/javase/7/docs/technotes/tools/share/jstack.html
>
> Thanks,
> Hasitha.
>
> On Tue, Dec 23, 2014 at 6:02 PM, Buddhi Senarathna <
> budd...@wso2.com> wrote:
>
>> hi all,
>>
>> I'm working on creating a tool to take thread dumps and analyze
>> thread info as carbon

Re: [Dev] How to find the coordinator node of a cluster using hazelcast agent.

[Hemika Kodikara]

Hi Azeez,

Yes, HazelcastInstance is there. But it doesn't provide a method to get the
coordinator node IP address and so.

Thanks,
Hemika

Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Tue, Jan 13, 2015 at 1:30 PM, Afkham Azeez  wrote:

> Yes, get the HazelcastInstance OSGi service, and then using Hazelcast APIs
> you should be able to get the required information.
>
> Azeez
>
> On Tue, Jan 13, 2015 at 1:25 PM, Hemika Kodikara  wrote:
>
>> Looping in Azeez, Sameera and Kishanthan.
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>> On Tue, Jan 13, 2015 at 12:35 PM, Hemika Kodikara 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have a requirement to show the IP addresses and ports of the nodes in
>>> a cluster on a UI page. But I also have to indicate which node is the
>>> coordinator node. Currently I am only able to to find whether the current
>>> node is the coordinator node or not using the "isCoordinator" method in
>>> "HazelcastClusteringAgent" class.
>>>
>>> Is there way to find the coordinator node's IP address and port of the
>>> cluster?
>>>
>>> Regards,
>>> Hemika
>>>
>>> Hemika Kodikara
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middleware
>>> http://wso2.com
>>>
>>> Mobile : +9477762
>>>
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to find the coordinator node of a cluster using hazelcast agent.

[Afkham Azeez]

Yes, get the HazelcastInstance OSGi service, and then using Hazelcast APIs
you should be able to get the required information.

Azeez

On Tue, Jan 13, 2015 at 1:25 PM, Hemika Kodikara  wrote:

> Looping in Azeez, Sameera and Kishanthan.
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Tue, Jan 13, 2015 at 12:35 PM, Hemika Kodikara  wrote:
>
>> Hi All,
>>
>> I have a requirement to show the IP addresses and ports of the nodes in a
>> cluster on a UI page. But I also have to indicate which node is the
>> coordinator node. Currently I am only able to to find whether the current
>> node is the coordinator node or not using the "isCoordinator" method in
>> "HazelcastClusteringAgent" class.
>>
>> Is there way to find the coordinator node's IP address and port of the
>> cluster?
>>
>> Regards,
>> Hemika
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Fixing uploadable jaggery applications issue

[Dimuthu Leelarathne]

On Tue, Jan 13, 2015 at 12:49 PM, Anuruddha Premalal 
wrote:

> Hi,
>
> Once we upload an application to appfactory it get stored temporally inside*
> wso2appfctory-2.1.0/repository/deployment/server/jaggeryapps/appmgt/tmp/tmpUploadedApps
> . * Notice that this location is inside jaggeryapps folder.
>
> Issue is if we upload a zip file it gets automatically deployed inside the
> uploaded location by the jaggerydeployer and it deletes the original
> uploaded zip.
>
> Initially following are the fixes that are going to try.
>
> * Try to override the jaggerydeployer component.xml file by writing an
> osgi fragment.
>   - here component.xml file contains the information about the deployer.
> So we can  try overriding this xml and remove the zip file deploery.
>
> * Turn off hot deployment in axis2.xml
>   - but this will cause issue in apptype and runtime hot deployment?
>
>
* Upload the applicatoins to carbon_home/tmp location
>  - This location is not visible to appmgt webapp home. Is there a way to
> pass the uploaded file to osgi back-end via jaggery?
>

The fix is to copy the file into the temp location. And then reading the
file from that location. Pass the file name is straight forward coding.

thanks,
dimuthu


>
> Appreciate your inputs in solving this issue [1].
>
> [1] https://wso2.org/jira/browse/APPFAC-2740
>
> Regards,
> --
> *Anuruddha Premalal*
> Software Eng. | WSO2 Inc.
> Mobile : +94710461070
> Web site : www.regilandvalley.com
>
>


-- 
Dimuthu Leelarathne
Architect & Product Lead of App Factory

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com
Mobile : 0773661935

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev