Re: [Dev] Regard JSP page errors

[Vanjikumaran Sivajothy]

+1

On Wednesday, April 9, 2014, Ajith Vitharana  wrote:

>
>
>
> On Wed, Apr 9, 2014 at 12:11 PM, Kasun Gajasinghe 
> 
> > wrote:
>
>> Hi Vanji,
>>
>> Jasper version upgrade has been discussed in previous threads, and the AS
>> jira ticket you just mentioned [1] contains a comprehensive details about
>> this upgrade.
>>
>> Since this error could be there in hundreds of JSP pages, and there is no
>> apparent gain by fixing this particular issue, I guess it's better if we
>> can stop the strict quote escape rule. You can disable this by adding the
>> following system property.
>>
>> org.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
>>
>
> +1. I'm also experiencing same issue in G-Reg pack. Shall we include this
> to start up scrip ?
>
> -Ajith
>
>
>> [1] 
>> https://wso2.org/jira/browse/WSAS-168
>>
>>
>
>> Regards,
>> KasunG
>>
>>
>> On Wed, Apr 9, 2014 at 11:38 AM, Vanjikumaran Sivajothy 
>> wrote:
>>
>> Hi,
>>
>> The latest build of ESB pack getting lots of JSP based exception, and we
>> found that there were a update on jasper version and strict enforcement on
>> the jsp rules [1]
>>
>> This change might affect other products as well,
>>
>> Thus why this is not informed? and what is the plan to fixes these kind
>> a dead pages?
>>
>> [1] https://wso2.org/jira/browse/WSAS-1687
>>
>> 2014-04-09 11:12:22,305] ERROR - ApplicationDispatcher Servlet.service()
>> for servlet bridgeservlet threw exception
>> org.apache.jasper.JasperException: /proxyservices/templates.jsp (line:
>> 73, column: 61) Attribute value template+".desc" is quoted with " which
>> must be escaped when used within the value
>>  at
>> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:42)
>>  at
>> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:443)
>> at
>> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:89)
>>  at
>> org.apache.jasper.compiler.Parser.parseAttributeValue(Parser.java:280)
>>  at org.apache.jasper.compiler.Parser.parseAttribute(Parser.java:229)
>> at org.apache.jasper.compiler.Parser.parseAttributes(Parser.java:162)
>>  at org.apache.jasper.compiler.Parser.parseAttributes(Parser.java:153)
>>  at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1236)
>> at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1452)
>>  at org.apache.jasper.compiler.Parser.parseBody(Parser.java:1664)
>>  at org.apache.jasper.compiler.Parser.parseOptionalBody(Parser.java:1002)
>> at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1274)
>>  at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1452)
>>  at org.apache.jasper.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org 
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>

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

[Dev] Could not find artifact org.wso2.maven:carbon-p2-plugin:pom:1.5.3 error while building features of App Factory

[Punnadi Gunarathna]

Hi All,

I restructured App Factory code base in order to commit to GitHub project.
I am getting this error when features are built in this new structure.

[ERROR] Plugin org.wso2.maven:carbon-p2-plugin:1.5.3 or one of its
dependencies could not be resolved: Failed to read artifact descriptor for
org.wso2.maven:carbon-p2-plugin:jar:1.5.3: Could not find artifact
org.wso2.maven:carbon-p2-plugin:pom:1.5.3 in central (
http://repo.maven.apache.org/maven2) -> [Help 1]

I have configured below repositories in root parent.

   
  
  
 wso2-nexus
 WSO2 internal Repository
 http://maven.wso2.org/nexus/content/groups/wso2-public/
 
true
daily
ignore
 
  
  
 wso2.releases
 WSO2 internal Repository
 http://maven.wso2.org/nexus/content/repositories/releases/

 
true
daily
ignore
 
  
  
 wso2.snapshots
 WSO2 Snapshot Repository
 http://maven.wso2.org/nexus/content/repositories/snapshots/

 
true
daily
 
 
false
 
  
   

I have noted the simillar kind of error in below link also.
http://builder4.us1.wso2.org:/bamboo/browse/WCB007-KER001-10/log

"org.wso2.carbon.appfactory.server.feature feature" pom file is attached
herewith.

Please share your thought if you are familiar with this error.


-- 
Thanks and Regards,

Punnadi Gunarathna
Senior Software Engineer,
WSO2, Inc.; http://wso2.com 
Blog: http://hi-my-world.blogspot.com/
Tel : 94 11 214 5345
Fax :94 11 2145300



 



http://maven.apache.org/POM/4.0.0";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>


org.wso2.carbon
appfactory-feature
1.1.0-SNAPSHOT
	../pom.xml
 


4.0.0
org.wso2.carbon.appfactory.server.feature
pom
WSO2 Carbon - AppFactory Server Feature
http://wso2.org
This feature contains the core bundles required for AppFactory back end




org.wso2.carbon
org.wso2.carbon.hostobjects.carbonutil


org.wso2.carbon
org.wso2.carbon.appfactory.hostobjects.configuration


org.wso2.carbon
org.wso2.carbon.hostobjects.sso


org.wso2.carbon
org.wso2.carbon.appfactory.application.mgt


org.wso2.carbon
org.wso2.carbon.appfactory.listners


org.wso2.carbon
org.wso2.carbon.appfactory.apiManager.integration


org.wso2.carbon
org.wso2.carbon.appfactory.bam.integration


org.wso2.carbon
org.wso2.carbon.appfactory.common


org.wso2.carbon
org.wso2.carbon.email.sender


org.wso2.carbon
org.wso2.carbon.email.verification


plexus-utils.wso2
plexus-utils


maven-invoker.wso2
maven-invoker


org.wso2.carbon
org.wso2.carbon.appfactory.login.ui


org.wso2.carbon
org.wso2.carbon.appfactory.userstore


org.wso2.carbon
org.wso2.carbon.appfactory.core

	
org.wso2.carbon
org.wso2.carbon.appfactory.deployers


org.wso2.carbon
org.wso2.carbon.appfactory.buildserver.teanant.mgt.stub


org.wso2.carbon
org.wso2.carbon.appfactory.stratos.listeners.stub

	
org.wso2.carbon
org.wso2.carbon.bpel.stub


org.wso2.carbon
org.wso2.carbon.um.ws.api.stub

	
org.wso2.carbon
org.wso2.carbon.dataservices.fileupload.stub

	
org.wso2.carbon
org.wso2.carbon.appfactory.build

  

org.apache.maven.scm.wso2
maven-scm

 

org.wso2.carbon
org.wso2.carbon.appfactory.repository.mgt.service

 
org.wso2.carbon
org.wso2.carbon.appfactory.utilities


org.apache.maven.wso2
maven-model
3.0.3.wso2v1


org.apache.maven.wso2
maven-core


org.wso2.carbon
org.wso2.carbon.appfactory.issuetracking


com.gitblit
gitblit


org.wso2.carbon
org.wso2.carbon.ide

Re: [Dev] Could not find artifact org.wso2.maven:carbon-p2-plugin:pom:1.5.3 error while building features of App Factory

[Pradeep Fernando]

I think you have to configure plugin repositories as well.

add nexus repo to plugin repositories..

the artifact is availble in the dist/nexus repos
http://dist.wso2.org/maven2/org/wso2/maven/carbon-p2-plugin/1.5.3/


On Wed, Apr 9, 2014 at 1:40 PM, Punnadi Gunarathna  wrote:

> Hi All,
>
> I restructured App Factory code base in order to commit to GitHub project.
> I am getting this error when features are built in this new structure.
>
> [ERROR] Plugin org.wso2.maven:carbon-p2-plugin:1.5.3 or one of its
> dependencies could not be resolved: Failed to read artifact descriptor for
> org.wso2.maven:carbon-p2-plugin:jar:1.5.3: Could not find artifact
> org.wso2.maven:carbon-p2-plugin:pom:1.5.3 in central (
> http://repo.maven.apache.org/maven2) -> [Help 1]
>
> I have configured below repositories in root parent.
>
>
>   
>   
>  wso2-nexus
>  WSO2 internal Repository
>  http://maven.wso2.org/nexus/content/groups/wso2-public/
> 
>  
> true
> daily
> ignore
>  
>   
>   
>  wso2.releases
>  WSO2 internal Repository
>  http://maven.wso2.org/nexus/content/repositories/releases/
> 
>  
> true
> daily
> ignore
>  
>   
>   
>  wso2.snapshots
>  WSO2 Snapshot Repository
>  http://maven.wso2.org/nexus/content/repositories/snapshots/
> 
>  
> true
> daily
>  
>  
> false
>  
>   
>
>
> I have noted the simillar kind of error in below link also.
> http://builder4.us1.wso2.org:/bamboo/browse/WCB007-KER001-10/log
>
> "org.wso2.carbon.appfactory.server.feature feature" pom file is attached
> herewith.
>
> Please share your thought if you are familiar with this error.
>
>
> --
> Thanks and Regards,
>
> Punnadi Gunarathna
> Senior Software Engineer,
> WSO2, Inc.; http://wso2.com 
> Blog: http://hi-my-world.blogspot.com/
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
>
>  
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pradeep Fernando*
Associate Technical Lead;WSO2 Inc.; http://wso2.com

blog: http://pradeepfernando.blogspot.com
m: +94776603662
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Could not find artifact org.wso2.maven:carbon-p2-plugin:pom:1.5.3 error while building features of App Factory

[Punnadi Gunarathna]

Hi Pradeep,

Yes it worked. Thank you.


On Wed, Apr 9, 2014 at 1:51 PM, Pradeep Fernando  wrote:

> I think you have to configure plugin repositories as well.
>
> add nexus repo to plugin repositories..
>
> the artifact is availble in the dist/nexus repos
> http://dist.wso2.org/maven2/org/wso2/maven/carbon-p2-plugin/1.5.3/
>
>
> On Wed, Apr 9, 2014 at 1:40 PM, Punnadi Gunarathna wrote:
>
>> Hi All,
>>
>> I restructured App Factory code base in order to commit to GitHub
>> project. I am getting this error when features are built in this new
>> structure.
>>
>> [ERROR] Plugin org.wso2.maven:carbon-p2-plugin:1.5.3 or one of its
>> dependencies could not be resolved: Failed to read artifact descriptor for
>> org.wso2.maven:carbon-p2-plugin:jar:1.5.3: Could not find artifact
>> org.wso2.maven:carbon-p2-plugin:pom:1.5.3 in central (
>> http://repo.maven.apache.org/maven2) -> [Help 1]
>>
>> I have configured below repositories in root parent.
>>
>>
>>   
>>   
>>  wso2-nexus
>>  WSO2 internal Repository
>>  http://maven.wso2.org/nexus/content/groups/wso2-public/
>> 
>>  
>> true
>> daily
>> ignore
>>  
>>   
>>   
>>  wso2.releases
>>  WSO2 internal Repository
>>  http://maven.wso2.org/nexus/content/repositories/releases/
>> 
>>  
>> true
>> daily
>> ignore
>>  
>>   
>>   
>>  wso2.snapshots
>>  WSO2 Snapshot Repository
>>  http://maven.wso2.org/nexus/content/repositories/snapshots/
>> 
>>  
>> true
>> daily
>>  
>>  
>> false
>>  
>>   
>>
>>
>> I have noted the simillar kind of error in below link also.
>> http://builder4.us1.wso2.org:/bamboo/browse/WCB007-KER001-10/log
>>
>> "org.wso2.carbon.appfactory.server.feature feature" pom file is attached
>> herewith.
>>
>> Please share your thought if you are familiar with this error.
>>
>>
>> --
>> Thanks and Regards,
>>
>> Punnadi Gunarathna
>> Senior Software Engineer,
>> WSO2, Inc.; http://wso2.com 
>> Blog: http://hi-my-world.blogspot.com/
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>>
>>  
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pradeep Fernando*
> Associate Technical Lead;WSO2 Inc.; http://wso2.com
>
> blog: http://pradeepfernando.blogspot.com
> m: +94776603662
>



-- 
Thanks and Regards,

Punnadi Gunarathna
Senior Software Engineer,
WSO2, Inc.; http://wso2.com 
Blog: http://hi-my-world.blogspot.com/
Tel : 94 11 214 5345
Fax :94 11 2145300



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

[Dev] [DEV] Publish-Subscribe Channel EIP - throws error

[Chathurika Mahaarachchi]

Hi

Created a proxy for  Publish-Subscribe Channel EIP as follows, and created
a topic as " PublisherSubsciber"

Started two sample Axis2 server instances in port 9000  and 9001

https://docs.wso2.org/display/IntegrationPatterns/Publish-Subscribe+Channel





http://ws.apache.org/ns/synapse";

name="Event"

transports="https,http"

statistics="disable"

trace="disable"

startOnLoad="true">
































Then I tried using giving the below message


http://schemas.xmlsoap.org/soap/envelope/";
xmlns:ser="http://services.samples"; xmlns:xsd="http://services.samples/xsd";>
   
   
  
 
foo
 
  
   


following error is observed in axis2 server

14/04/09 13:57:44 ERROR engine.AxisEngine: The endpoint reference (EPR) for
the Operation not found is /services/SimpleStockQuoteService and the WSA
Action = http://ws.apache.org/ws/2007/05/eventing-extended/Publish. If this
EPR was previously reachable, please contact the server administrator.

org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
not found is /services/SimpleStockQuoteService and the WSA Action =
http://ws.apache.org/ws/2007/05/eventing-extended/Publish. If this EPR was
previously reachable, please contact the server administrator.

at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)

at org.apache.axis2.engine.Phase.invoke(Phase.java:329)

at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)

at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)

at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)

at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279)

at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)

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

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

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

14/04/09 13:57:44 ERROR nhttp.ServerWorker: Error processing POST request

org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
not found is /services/SimpleStockQuoteService and the WSA Action =
http://ws.apache.org/ws/2007/05/eventing-extended/Publish. If this EPR was
previously reachable, please contact the server administrator.

at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)

at org.apache.axis2.engine.Phase.invoke(Phase.java:329)

at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)

at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)

at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)

at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279)

at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)

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

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

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

Please have a look.

Regards,

-- 
*Chathurika Mahaarachchi*
Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
lean.enterprise.middleware
Mobile: +94718223950
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Moving FE operations to BE

[Ishara Premadasa]

Hi Indika,

Your observation is correct that getAccessKey() method is not exposed to
all the users, however few clarifications to made is this method is not
configured to admin role only. According to the current permission model in
carbon we can create new roles and assign permissions to that accordingly.
However if you look at the permission tree there is only two MB related
permission options named,


MB




   -


  Add Queue







  -  Queue Details

Therefore for a user to perform other queue operations than this, we need
to provide admin--> configure permission as shown in image [1] which is the
reason getAccessKey() is bound to /permission/admin/configure level. (This
is more like for any user to work with MB it needs some admin priviledges
)Therefore IMO it would be better if we can add more options to above MB
level permissions like Browse Queue etc. so user can be authorized to
getAccessKey()
by selecting that permission rather than moving the operations into BE.


On Wed, Apr 9, 2014 at 11:48 AM, Indika Sampath  wrote:

> Hi All,
>
> There is an issue with browsing the queue for users which haven't admin
> role. The reason is following two methods restricted to the admin role in
> Axis2 level.
>
>- getCurrentUser()
>- getAccessKey()
>
> There is a way to get the current logged user from the session but there
> is no way to get the access key.
> org.wso2.carbon.andes.ui.client.QueueBrowserClient creating a queue
> connection and access the queue from the FE. We need user name and access
> key to creating queue connection. There might be some security issue with
> QueueBrowserClient as I and Hasitha had discussion with Suresh on
> yesterday. Some operations in org.wso2.carbon.andes.ui module needs to move
> to the BE. I have come up with the following implementation design.
>
> Move following methods in the QueueBrowserClient to
> org.wso2.carbon.andes.core.QueueManagerService and expose as web service
> via org.wso2.carbon.andes.admin.AndesAdminService.
>
>
>- browseQueue()
>- closeBrowser()
>- getMsgContentType()
>- getMessageContentAsString()
>
> When we change like this we need to call the BE four times for each Browse
operation and this would be same for publish sample msg, purge queue etc.
which we don't necessarily have to go for BE. Wouldn't it be an overhead
that we make several FE <--> BE calls for a single UI operation each time?

Thanks!
Ishara

[1]
https://svn.wso2.org/repos/wso2/people/isharap/permissions_non_admin_user.png


> But there are another two classes
> org.wso2.carbon.andes.ui.client.QueueReceiverClient and
> org.wso2.carbon.andes.ui.client.QueueSenderClient needs do the same thing
> as I think.
>
> Cheers!
>
> --
> Indika Sampath
> Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Problem in running ESB sample 61 and 62

[Thilini Shanika]

Hi all,

In ESB sample 61[1] and [62] configurations  contain "file:repository/conf/sample/resources/" and 'EP_LIST' file
located in 'repository/conf/sample/resources/' is required to run the
samples. But in ESB 4.8.1 release,such file location does not exist.

Following error is encountered when I tried to run the above two samples.
 [2014-04-09 14:09:32,125] WARN - SynapseConfigUtils IO Error reading from
URL :
/repository/conf/sample/resources/recipients/EP_LISTjava.io.FileNotFoundException:
/repository/conf/sample/resources/recipients/EP_LIST (No such file or
directory)

Where can I find this 'EP_LIST' file and how to resolve the issue?

[1]-
https://docs.wso2.org/display/ESB481/Sample+61%3A+Routing+a+Message+to+a+Dynamic+List+of+Recipients
[2]-
https://docs.wso2.org/display/ESB481/Sample+62%3A+Routing+a+Message+to+a+Dynamic+List+of+Recipients+and+Aggregating+Responses

-- 
Thilini Shanika
Software Engineer
WSO2, Inc.; http://wso2.com
20, Palmgrove Avenue, Colombo 3

E-mail: tgtshan...@gmail.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Problem in running ESB sample 61 and 62

[Isuru Ranawaka]

hi thilini,

Use synapse samples  61 used in wso2ESB 4.7 .Seems documentation should be
updated. [1]

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




On Wed, Apr 9, 2014 at 2:33 PM, Thilini Shanika  wrote:

>
> Hi all,
>
> In ESB sample 61[1] and [62] configurations  contain " "root">file:repository/conf/sample/resources/" and 'EP_LIST'
> file located in 'repository/conf/sample/resources/' is required to run
> the samples. But in ESB 4.8.1 release,such file location does not exist.
>
> Following error is encountered when I tried to run the above two samples.
>  [2014-04-09 14:09:32,125] WARN - SynapseConfigUtils IO Error reading
> from URL :
> /repository/conf/sample/resources/recipients/EP_LISTjava.io.FileNotFoundException:
> /repository/conf/sample/resources/recipients/EP_LIST (No such file or
> directory)
>
> Where can I find this 'EP_LIST' file and how to resolve the issue?
>
> [1]-
> https://docs.wso2.org/display/ESB481/Sample+61%3A+Routing+a+Message+to+a+Dynamic+List+of+Recipients
> [2]-
> https://docs.wso2.org/display/ESB481/Sample+62%3A+Routing+a+Message+to+a+Dynamic+List+of+Recipients+and+Aggregating+Responses
>
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 3
>
> E-mail: tgtshan...@gmail.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards
Isuru Ranawaka
phone :- +94714629880
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Moving FE operations to BE

[Suresh Attanayaka]

Hi Ishara,

I would not agree with your argument regarding the FE-BE communication
overhead, afterall most of the time it is just a java call over the
local-transport, no http cost at all. For me, consuming the JMS queue from
the UI is no different from connecting to the database over JDBC from the
UI which is not really our model.

Plus, the key shared there is a system key and exposing it over HTTP is not
a good idea. It should be shared using the OSGI service instead.

On Wed, Apr 9, 2014 at 2:30 PM, Ishara Premadasa  wrote:

> Hi Indika,
>
> Your observation is correct that getAccessKey() method is not exposed to
> all the users, however few clarifications to made is this method is not
> configured to admin role only. According to the current permission model in
> carbon we can create new roles and assign permissions to that accordingly.
> However if you look at the permission tree there is only two MB related
> permission options named,
>
>
> MB
>
>
>
>
>-
>
>
>   Add Queue
>
>
>
>
>
>
>
>   -  Queue Details
>
> Therefore for a user to perform other queue operations than this, we need
> to provide admin--> configure permission as shown in image [1] which is the
> reason getAccessKey() is bound to /permission/admin/configure level. (This
> is more like for any user to work with MB it needs some admin priviledges
> )Therefore IMO it would be better if we can add more options to above MB
> level permissions like Browse Queue etc. so user can be authorized to 
> getAccessKey()
> by selecting that permission rather than moving the operations into BE.
>
>
> On Wed, Apr 9, 2014 at 11:48 AM, Indika Sampath  wrote:
>
>> Hi All,
>>
>> There is an issue with browsing the queue for users which haven't admin
>> role. The reason is following two methods restricted to the admin role in
>> Axis2 level.
>>
>>- getCurrentUser()
>>- getAccessKey()
>>
>> There is a way to get the current logged user from the session but there
>> is no way to get the access key.
>> org.wso2.carbon.andes.ui.client.QueueBrowserClient creating a queue
>> connection and access the queue from the FE. We need user name and access
>> key to creating queue connection. There might be some security issue with
>> QueueBrowserClient as I and Hasitha had discussion with Suresh on
>> yesterday. Some operations in org.wso2.carbon.andes.ui module needs to move
>> to the BE. I have come up with the following implementation design.
>>
>> Move following methods in the QueueBrowserClient to
>> org.wso2.carbon.andes.core.QueueManagerService and expose as web service
>> via org.wso2.carbon.andes.admin.AndesAdminService.
>>
>>
>>- browseQueue()
>>- closeBrowser()
>>- getMsgContentType()
>>- getMessageContentAsString()
>>
>> When we change like this we need to call the BE four times for each
> Browse operation and this would be same for publish sample msg, purge queue
> etc. which we don't necessarily have to go for BE. Wouldn't it be an
> overhead that we make several FE <--> BE calls for a single UI operation
> each time?
>
> Thanks!
> Ishara
>
> [1]
> https://svn.wso2.org/repos/wso2/people/isharap/permissions_non_admin_user.png
>
>
>> But there are another two classes
>> org.wso2.carbon.andes.ui.client.QueueReceiverClient and
>> org.wso2.carbon.andes.ui.client.QueueSenderClient needs do the same thing
>> as I think.
>>
>> Cheers!
>>
>> --
>> Indika Sampath
>> Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>
>
> --
> Ishara Premasada
> Software Engineer,
> WSO2 Inc. http://wso2.com/
>
>
> *Blog   :  http://isharapremadasa.blogspot.com/
> Twitter   :
> https://twitter.com/ishadil  Mobile   :
> +94 714445832 <%2B94%20714445832>*
>
>
>


-- 
Suresh Attanayake
Senior Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Web : http://www.ssoarcade.com/
Facebook : https://www.facebook.com/IdentityWorld
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060
Mobile : +016166171172
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Meeting Notes:Code review for JMX Monitoring for human tasks

[Waruna Jayaweera]

Hi,

Following points were discussed in the code review for JMX Monitoring for
human tasks.

1. Include necessary interface in project class hierarchy.
2. Format the code and add doc comments to necessary classes.(ex.
DeployedTasksMXBean)
3. Rename DeplyedTasks>>HTTasksStatusMonitor
4. Rename DeployedTasksMXBean class methods with meaningful names

 showAllTaskDefinitions
 getInstanceForTaskDefinitions
 getInstanceListForTaskState
 getTaskInstanceDetails

5. Add log.error to to display error messages
6. Null and empty check when get all tasks
7. Add license text for each class .
8. Find what is the best way to get tenant ids
9. Go through all the code and remove the unnecessary codes
10. Rename methods in HTQueryBuildHelperImpl class

getTaskInstanceCountByState

11. Fix the Camel notation in declaring variables
12. Null check for task name
13. Add missing states in HtQueryCriteria class
14. Change the logic of separate task name over task definition and task
instance using regex
15. Use Lists for Arrays
16. For UI need some jsp pages


-- 
Regards,

Waruna Lakshitha Jayaweera
Software Engineer
WSO2 Inc; http://wso2.com
phone: +94713255198
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Finalyzing instrument jar list for MB code coverage

[Nuwan Wimalasekara]

Hi
As discussed with HasithaH, I have included following packages in integration
tests instrumentation file in order to get the coverage statistics for MB.
Please let us know if any other packages(which is inside the MB server)
need to be included or excluded from the list.

org.wso2.carbon.andes
org.wso2.carbon.cassandra
org.wso2.carbon.event

Herewith I have attached the coverage report with the above instrumentation
list. It lists all the packages instrumented by the emma as the
instrumentation file.


Thanks,
Nuwanw
-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
Title: EMMA Coverage Report (generated Wed Apr 09 15:06:45 IST 2014)
EMMA Coverage Report (generated Wed Apr 09 15:06:45 IST 2014)[all classes]OVERALL COVERAGE SUMMARYnameline, %block, %method, %class, %all classes2%   (1016.5/51482)2%   (3715/221001)5%   (314/6879)10%  (68/691)OVERALL STATS SUMMARYtotal packages:96total executable files:417total classes:691total methods:6879total executable lines:51482COVERAGE BREAKDOWN BY PACKAGEnameline, %block, %method, %class, %org.wso2.carbon.andes.authentication.service100% (5/5)100% (12/12)100% (2/2)100% (1/1)org.wso2.carbon.cassandra.common.cache100% (4/4)100% (9/9)100% (2/2)100% (1/1)org.wso2.carbon.andes.authentication.internal97%  (32/33)97%  (86/89)94%  (15/16)100% (2/2)org.wso2.carbon.andes.commons.internal96%  (22/23)94%  (48/51)93%  (13/14)100% (2/2)org.wso2.carbon.andes.authorization.internal91%  (32/35)87%  (91/105)93%  (14/15)100% (2/2)org.wso2.carbon.event.admin.internal.util91%  (10/11)88%  (23/26)89%  (8/9)100% (2/2)org.wso2.carbon.event.ws.internal90%  (19/21)88%  (44/50)86%  (12/14)100% (2/2)org.wso2.carbon.andes.admin.util90%  (19/21)88%  (43/49)86%  (12/14)100% (2/2)org.wso2.carbon.cassandra.server.internal86%  (59/69)85%  (205/240)95%  (19/20)100% (2/2)org.wso2.carbon.andes.core.internal.ds84%  (26/31)82%  (62/76)83%  (15/18)100% (2/2)org.wso2.carbon.cassandra.sharedkey.internal83%  (10/12)80%  (16/20)75%  (6/8)100% (1/1)org.wso2.carbon.cassandra.server.service71%  (5/7)71%  (10/14)67%  (2/3)100% (1/1)org.wso2.carbon.cassandra.server.util67%  (5.4/8)66%  (25/38)67%  (2/3)100% (1/1)org.wso2.carbon.andes.core.internal.builder67%  (2/3)67%  (6/9)50%  (1/2)100% (1/1)org.wso2.carbon.andes.authorization.service.andes63%  (48.8/77)65%  (227/349)71%  (12/17)100% (5/5)org.wso2.carbon.cassandra.common.auth63%  (19/30)51%  (76/150)33%  (2/6)67%  (2/3)org.wso2.carbon.andes.internal63%  (121.9/193)53%  (448/838)97%  (33/34)100% (2/2)org.wso2.carbon.event.core.internal.builder62%  (64.4/104)59%  (249/424)86%  (19/22)100% (4/4)org.wso2.carbon.andes.authorization.andes56%  (76.1/137)63%  (368/581)67%  (12/18)50%  (1/2)org.wso2.carbon.andes.authentication.andes50%  (35.3/70)43%  (115/267)38%  (5/13)100% (1/1)org.wso2.carbon.andes.commons.registry45%  (50.7/113)41%  (185/452)42%  (5/12)50%  (1/2)org.wso2.carbon.cassandra.server42%  (89.8/214)47%  (366/779)48%  (26/54)62%  (5/8)org.wso2.carbon.andes.service38%  (90.4/240)27%  (364/1339)57%  (20/35)100% (1/1)org.wso2.carbon.event.core.internal32%  (40.6/128)32%  (160/500)36%  (10/28)67%  (2/3)org.wso2.carbon.andes.commons27%  (13/49)43%  (87/203)12%  (3/25)33%  (1/3)org.wso2.carbon.event.core.internal.notify26%  (5/19)21%  (15/73)67%  (2/3)100% (1/1)org.wso2.carbon.event.core.qpid25%  (8/32)11%  (21/185)8%   (1/13)100% (1/1)org.wso2.carbon.event.core.internal.util25%  (20/81)18%  (62/342)60%  (12/20)100% (2/2)org.wso2.carbon.event.core.internal.subscription.registry22%  (37/168)20%  (158/783)36%  (4/11)100% (2/2)org.wso2.carbon.andes.cluster.mgt.internal21%  (12/57)15%  (28/182)31%  (8/26)33%  (2/6)org.wso2.carbon.andes.core7%   (6/92)4%   (15/421)12%  (2/17)50%  (1/2)org.wso2.carbon.event.core.internal.delivery.jms6%   (14/246)4%   (44/1048)16%  (6/37)60%  (3/5)org.wso2.carbon.event.ws.internal.notify5%   (2/39)5%   (7/131)40%  (2/5)100% (1/1)org.wso2.carbon.event.core.internal.topic.registry4%   (7/175)2%   (22/908)16%  (3/19)100% (2/2)org.wso2.carbon.andes.admin2%   (1/66)2%   (4/243)8%   (1/12)50%  (1/2)org.wso2.carbon.event.ws.internal.receivers1%   (3/271)1%   (10/1185)7%   (2/28)20%  (1/5)org.wso2.carbon.andes.cluster.mgt0%   (1/229)1%   (4/780)1%   (1/67)20%  (1/5)org.wso2.carbon.andes.service.ws0%   (0/12)0%   (0/51)0%   (0/7)100% (1/1)org.wso2.carbon.cassandra.sharedkey0%   (0/13)0%   (0/44)0%   (0/2)100% (1/1)org.wso2.carbon.event.admin.internal0%   (0/126)0%   (0/452)0%   (0/34)50%  (1/2)org.w3.www.xml._1998.namespace0%   (0/151)0%   (0/629)0%   (0/20)0%   (0/2)org.wso2.carbon.andes.admin.internal0%   (0/23)0%   (0/51)0%   (0/14)0%   (0/1)org.wso2.carbon.andes.admin.internal.Exception0%   (0/14)0%   (0/31)0%   (0/7)0%   (0/1)org.wso2.carbon.andes.cluster.mgt.internal.managementBeans0%   (0/252)0%   (0/1009)0%   (0/15)0%   (0/1)org.wso2.carbon.andes.cluster.mgt.ui0%   (0/38)0%   (0/163)0%   (0/19)0%   (0/1)org.wso2.carbon.andes.core.internal.reg

Re: [Dev] MB Cassandra profile memory allocation

[Indika Sampath]

Hi All,

The following changes I did in the MB product and achieve the $subject.

Copy the cassandra-env.sh with the changes I made to compatible with
org.wso2.carbon.core.bootup.validator.JVMValidator to the {MB_HOME}/bin
folder when pack is build
Load the cassandra-env.sh when MB start with cassandra profile
Set the -Xms  -Xmx -XX:MaxPermSize parameters dynamically as calculated in
the cassandra-env.sh

This is working in the Linux. Now I have a problem with how to make this
changes which is compatible to the Windows environment. I have already make
the .bat file to start with the cassandra profile before. But now the
problem is I couldn't load the cassandra-env.sh in Windows. Is there
something which is relevant to cassandra-env.sh in Windows environment ?

Cheers!


On Wed, Apr 9, 2014 at 11:46 AM, Prabath Abeysekera wrote:

>
> On Wed, Apr 9, 2014 at 11:16 AM, Dhanuka Ranasinghe wrote:
>
>> Hi,
>>
>> What about other important JVM tuning parameters (GC threads and
>> strategy), Are you guys consider those as well?
>>
>
> If we are to make the Cassandra profile, fully Cassandra-like, yeah, it's
> a must we include all the required/recommended JVM parameters (including
> what's used for fine tuning the functionalities) in the start-up script as
> well.
>
> Cheers,
> Prabath
>
>
>>
>> Cheers,
>> Dhanuka
>>
>> *Dhanuka Ranasinghe*
>>
>> Senior Software Engineer
>> WSO2 Inc. ; http://wso2.com
>> lean . enterprise . middleware
>>
>> phone : +94 715381915
>>
>>
>> On Wed, Apr 9, 2014 at 11:08 AM, Shammi Jayasinghe wrote:
>>
>>> Hi Deep,
>>>
>>> +1, that is what i wanted. It would be great if you can add this to the
>>> startup script of Cassandra profile.
>>>
>>> Hi Indika,
>>>
>>> Could you please talk to deep on this.
>>>
>>> thanks
>>> Shammi
>>>
>>>
>>> On Wed, Apr 9, 2014 at 10:51 AM, Deependra Ariyadewa wrote:
>>>



 On Wed, Apr 9, 2014 at 8:51 AM, Shammi Jayasinghe wrote:

>
>
>
> On Tue, Apr 8, 2014 at 7:29 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>>
>>
>>
>> On Tue, Apr 8, 2014 at 12:14 PM, Shammi Jayasinghe 
>> wrote:
>>
>>>
>>>
>>>
>>> On Tue, Apr 8, 2014 at 11:55 AM, Deependra Ariyadewa 
>>> wrote:
>>>



 On Tue, Apr 8, 2014 at 11:32 AM, Shammi Jayasinghe >>> > wrote:

> Hi ,
>
> I think we should not ask the user to change the .sh file or .bat
> file when starting with the cassandra profile. What we can do is, as
> default cassandra server does, we need to fix MB in a way that , when 
> we
> start the MB with Cassandra profile, it automatically allocates 1/3 
> of the
> total memory for MB. WDYT ?
>

 We should be able to calculate required memory in the wso2server.sh.

>>>
>>> Hi Sameera / Kishanthan,
>>>
>>>  We have  a requirement that the memory allocated when MB server
>>> starts with Cassandra profile should be a portion of the complete 
>>> memory of
>>> the server. Is it possible to do it and if it is possible, how we should
>>> proceed ?
>>>
>>
>> We currently don't use profile specific configurations (such as
>> specific start-up scripts, etc) when starting up profiles. We start
>> profiles after the java process is started and all profiles use the same
>> configurations. So this will not be possible using carbon server startup
>> scripts.
>>
>> But can't you use MB/Cassandra specific startup script for this? This
>> script should set the relevant JVM parameters and call server start-up 
>> with
>> cassandra profile.
>>
>
> Hi Kishanthan,
>
> Yes, we may able to use that scripts to fulfil this requirement.
> Actually what i wanted to know is whether we have inbuilt support from
> carbon for this requirement and thank you for clarifying.
>
> Hi Prabath/Deep,
>
> Do you have any idea on how cassandra handle the dynamic memory
> allocation for the product. I think , it will be a pain if we ask the user
> to change wso2server.sh or wso2server.bat if they want to start MB or SS
> with cassandra profile since with default memory allocation will not be
> enough for cassandra.
>

 We can add following logic use in cassandra-env.sh to Cassandra profile
 startup section to calculate the heap sized.

 calculate_heap_sizes()
 {
 case "`uname`" in
 Linux)
 system_memory_in_mb=`free -m | awk '/Mem:/ {print $2}'`
 system_cpu_cores=`egrep -c 'processor([[:space:]]+):.*'
 /proc/cpuinfo`
 ;;
 FreeBSD)
 system_memory_in_bytes=`sysctl hw.physmem | awk '{print
 $2}'`
 system_memory_in_mb=`expr $system_memory_in_bytes / 1024 /
 1024`
 system_cpu_cores=

Re: [Dev] Finalyzing instrument jar list for MB code coverage

[Shammi Jayasinghe]

Hi Nuwan,

In MB , we are only using cassandra server feature. Could you please modify
that package to org.wso2.carbon.cassandra.server. Apart from that we are
using coordination component ( zookeeper) also. Please add that to the list.

Thanks
shammi


On Wed, Apr 9, 2014 at 4:57 PM, Nuwan Wimalasekara  wrote:

> Hi
> As discussed with HasithaH, I have included following packages in integration
> tests instrumentation file in order to get the coverage statistics for
> MB. Please let us know if any other packages(which is inside the MB server)
> need to be included or excluded from the list.
>
> org.wso2.carbon.andes
> org.wso2.carbon.cassandra
> org.wso2.carbon.event
>
> Herewith I have attached the coverage report with the above
> instrumentation list. It lists all the packages instrumented by the emma as
> the instrumentation file.
>
>
> Thanks,
> Nuwanw
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 
Best Regards,

*  Shammi Jayasinghe*
Associate Tech Lead
WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] Publish-Subscribe Channel EIP - throws error

[Chanaka Fernando]

Hi Chathurika,

Did you try with the sample client?

ant stockquote -Dtrpurl=http://localhost:8280 -Dsymbol=foo


Looks like you are not sending the Action header with your request. If you
use the sample client, it will set the action header (wsa:Action).

Thanks,
Chanaka



On Wed, Apr 9, 2014 at 4:36 PM, Chathurika Mahaarachchi  wrote:

> Hi
>
> could you please have a look on this exception
>
> regards,
> Chathurika
>
> On Wed, Apr 9, 2014 at 2:20 PM, Chathurika Mahaarachchi <
> chathur...@wso2.com> wrote:
>
>> Hi
>>
>> Created a proxy for  Publish-Subscribe Channel EIP as follows, and
>> created a topic as " PublisherSubsciber"
>>
>> Started two sample Axis2 server instances in port 9000  and 9001
>>
>>
>> https://docs.wso2.org/display/IntegrationPatterns/Publish-Subscribe+Channel
>>
>>
>>
>> 
>>
>> http://ws.apache.org/ns/synapse";
>>
>> name="Event"
>>
>> transports="https,http"
>>
>> statistics="disable"
>>
>> trace="disable"
>>
>> startOnLoad="true">
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> > expression="get-property('ERROR_MESSAGE')"/>
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>>
>> Then I tried using giving the below message
>>
>>
>> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ser="
>> http://services.samples"; xmlns:xsd="http://services.samples/xsd";>
>>
>>
>>   
>>  
>> foo
>>  
>>   
>>
>> 
>>
>> following error is observed in axis2 server
>>
>> 14/04/09 13:57:44 ERROR engine.AxisEngine: The endpoint reference (EPR)
>> for the Operation not found is /services/SimpleStockQuoteService and the
>> WSA Action = http://ws.apache.org/ws/2007/05/eventing-extended/Publish.
>> If this EPR was previously reachable, please contact the server
>> administrator.
>>
>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>> Operation not found is /services/SimpleStockQuoteService and the WSA Action
>> = http://ws.apache.org/ws/2007/05/eventing-extended/Publish. If this EPR
>> was previously reachable, please contact the server administrator.
>>
>> at
>> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
>>
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>
>> at
>> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
>>
>> at
>> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279)
>>
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>>
>> at java.lang.Thread.run(Thread.java:722)
>>
>> 14/04/09 13:57:44 ERROR nhttp.ServerWorker: Error processing POST request
>>
>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>> Operation not found is /services/SimpleStockQuoteService and the WSA Action
>> = http://ws.apache.org/ws/2007/05/eventing-extended/Publish. If this EPR
>> was previously reachable, please contact the server administrator.
>>
>> at
>> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
>>
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>
>> at
>> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
>>
>> at
>> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279)
>>
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>>
>> at java.lang.Thread.run(Thread.java:722)
>>
>> Please have a look.
>>
>> Regards,
>>
>> --
>> *Chathurika Mahaarachchi*
>> Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> lean.enterprise.middleware
>> Mobile: +94718223950
>>
>
>
>
> --
> *Chathurika Mahaarachchi*
> Software Engineer, QA.
> WSO2 Inc.: http://wso2.com/
> lean.enterprise.middleware
> Mobile: +94718223950
>



-- 
--
Chanaka Fernando
Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
Wordpress:http://chanakaudaya.wordpress.com
_

Re: [Dev] Finalyzing instrument jar list for MB code coverage

[Nuwan Wimalasekara]

Hi Shammi
Thanks for the response. I will remove other
org.wso2.carbon.cassandrapackages except
org.wso2.carbon.cassandra.server. However We are running the integration
test against the standalone mode. So are coordination components used in
standalone mode? if so we can add them too

Thanks,
Nuwanw


On Wed, Apr 9, 2014 at 5:07 PM, Shammi Jayasinghe  wrote:

> Hi Nuwan,
>
> In MB , we are only using cassandra server feature. Could you please
> modify that package to org.wso2.carbon.cassandra.server. Apart from that we
> are using coordination component ( zookeeper) also. Please add that to the
> list.
>
> Thanks
> shammi
>
>
> On Wed, Apr 9, 2014 at 4:57 PM, Nuwan Wimalasekara wrote:
>
>> Hi
>> As discussed with HasithaH, I have included following packages in integration
>> tests instrumentation file in order to get the coverage statistics for
>> MB. Please let us know if any other packages(which is inside the MB server)
>> need to be included or excluded from the list.
>>
>> org.wso2.carbon.andes
>> org.wso2.carbon.cassandra
>> org.wso2.carbon.event
>>
>> Herewith I have attached the coverage report with the above
>> instrumentation list. It lists all the packages instrumented by the emma as
>> the instrumentation file.
>>
>>
>> Thanks,
>> Nuwanw
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
> Best Regards,
>
> *  Shammi Jayasinghe*
> Associate Tech Lead
> WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Time reporting support with Jira connector

[Samisa Abeysinghe]

Looking at https://docs.wso2.org/display/ESB481/JIRA+Connector there is
nothing on the lines of dealing with time reporting.

I am trying to see if I can pull time reported info from Jira using this
connector.

What is the take on this?

Thanks,
Samisa...


Samisa Abeysinghe

Vice President Developer Evangelism

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

Re: [Dev] Finalyzing instrument jar list for MB code coverage

[Shammi Jayasinghe]

Hi Nuwan,

No , in standalone mode, coordination stuff is not being used, Thanks for
the clarification

Thanks
Shammi


On Wed, Apr 9, 2014 at 5:22 PM, Nuwan Wimalasekara  wrote:

> Hi Shammi
> Thanks for the response. I will remove other 
> org.wso2.carbon.cassandrapackages except
> org.wso2.carbon.cassandra.server. However We are running the integration
> test against the standalone mode. So are coordination components used in
> standalone mode? if so we can add them too
>
> Thanks,
> Nuwanw
>
>
> On Wed, Apr 9, 2014 at 5:07 PM, Shammi Jayasinghe  wrote:
>
>> Hi Nuwan,
>>
>> In MB , we are only using cassandra server feature. Could you please
>> modify that package to org.wso2.carbon.cassandra.server. Apart from that we
>> are using coordination component ( zookeeper) also. Please add that to the
>> list.
>>
>> Thanks
>> shammi
>>
>>
>> On Wed, Apr 9, 2014 at 4:57 PM, Nuwan Wimalasekara wrote:
>>
>>> Hi
>>> As discussed with HasithaH, I have included following packages in 
>>> integration
>>> tests instrumentation file in order to get the coverage statistics for
>>> MB. Please let us know if any other packages(which is inside the MB server)
>>> need to be included or excluded from the list.
>>>
>>> org.wso2.carbon.andes
>>> org.wso2.carbon.cassandra
>>> org.wso2.carbon.event
>>>
>>> Herewith I have attached the coverage report with the above
>>> instrumentation list. It lists all the packages instrumented by the emma as
>>> the instrumentation file.
>>>
>>>
>>> Thanks,
>>> Nuwanw
>>> --
>>> Nuwan Wimalasekara
>>> Senior Software Engineer - Test Automation
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> phone: +94 71 668 4620
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> *  Shammi Jayasinghe*
>> Associate Tech Lead
>> WSO2, Inc.; http://wso2.com,
>> mobile: +94 71 4493085
>>
>>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 
Best Regards,

*  Shammi Jayasinghe*
Associate Tech Lead
WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] Publish-Subscribe Channel EIP - throws error

[Chathurika Mahaarachchi]

Thanks Chanaka,

Now its working fine.

Regards,
Chathurika


On Wed, Apr 9, 2014 at 5:13 PM, Chanaka Fernando  wrote:

> Hi Chathurika,
>
> Did you try with the sample client?
>
> ant stockquote -Dtrpurl=http://localhost:8280 -Dsymbol=foo
>
>
> Looks like you are not sending the Action header with your request. If you
> use the sample client, it will set the action header (wsa:Action).
>
> Thanks,
> Chanaka
>
>
>
> On Wed, Apr 9, 2014 at 4:36 PM, Chathurika Mahaarachchi <
> chathur...@wso2.com> wrote:
>
>> Hi
>>
>> could you please have a look on this exception
>>
>> regards,
>> Chathurika
>>
>> On Wed, Apr 9, 2014 at 2:20 PM, Chathurika Mahaarachchi <
>> chathur...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> Created a proxy for  Publish-Subscribe Channel EIP as follows, and
>>> created a topic as " PublisherSubsciber"
>>>
>>> Started two sample Axis2 server instances in port 9000  and 9001
>>>
>>>
>>> https://docs.wso2.org/display/IntegrationPatterns/Publish-Subscribe+Channel
>>>
>>>
>>>
>>> 
>>>
>>> http://ws.apache.org/ns/synapse";
>>>
>>> name="Event"
>>>
>>> transports="https,http"
>>>
>>> statistics="disable"
>>>
>>> trace="disable"
>>>
>>> startOnLoad="true">
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> >> expression="get-property('ERROR_MESSAGE')"/>
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>>
>>> Then I tried using giving the below message
>>>
>>>
>>> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ser="
>>> http://services.samples"; xmlns:xsd="http://services.samples/xsd";>
>>>
>>>
>>>   
>>>  
>>> foo
>>>  
>>>   
>>>
>>> 
>>>
>>> following error is observed in axis2 server
>>>
>>> 14/04/09 13:57:44 ERROR engine.AxisEngine: The endpoint reference (EPR)
>>> for the Operation not found is /services/SimpleStockQuoteService and the
>>> WSA Action = http://ws.apache.org/ws/2007/05/eventing-extended/Publish.
>>> If this EPR was previously reachable, please contact the server
>>> administrator.
>>>
>>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>>> Operation not found is /services/SimpleStockQuoteService and the WSA Action
>>> = http://ws.apache.org/ws/2007/05/eventing-extended/Publish. If this
>>> EPR was previously reachable, please contact the server administrator.
>>>
>>> at
>>> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
>>>
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>>
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>>
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>>
>>> at
>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>
>>> at
>>> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
>>>
>>> at
>>> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279)
>>>
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>>>
>>> at java.lang.Thread.run(Thread.java:722)
>>>
>>> 14/04/09 13:57:44 ERROR nhttp.ServerWorker: Error processing POST request
>>>
>>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>>> Operation not found is /services/SimpleStockQuoteService and the WSA Action
>>> = http://ws.apache.org/ws/2007/05/eventing-extended/Publish. If this
>>> EPR was previously reachable, please contact the server administrator.
>>>
>>> at
>>> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
>>>
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>>
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>>
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>>
>>> at
>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>
>>> at
>>> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
>>>
>>> at
>>> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:279)
>>>
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>>>
>>> at java.lang.Thread.run(Thread.java:722)
>>>
>>> Please have a look.
>>>
>>> Regards,
>>>
>>> --
>>> *Chathurika Mahaarachchi*
>>> Software Engineer, QA.
>>> WSO2 Inc.: http://wso2.com/
>>> lean.enterprise.middleware
>>> Mobile: +94718223950
>>>
>>
>>
>>
>> --
>> *Chathurika Mahaarachchi*
>> Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> lean.enterprise.middleware

Re: [Dev] Branches and workflow for jaggery

[Chan]

Shall we follow a method where there will be no branches for releases? This
way if I use 0.9.0.ALPHA4.wso2v4 version (tag) I fixed a bug. I need to use
a version higher than that or depend on the snapshot built from a
development branch (here -master) ? Otherwise the branches will diverge
with fixes to specific branches and this would be a nightmare for migration
from one version to another.


On Thu, Apr 3, 2014 at 4:44 PM, Chan  wrote:

> Yeah - I agree with most of your points. The current situation of Jaggery
> is that when somebody wants to release their product, they get a release of
> jaggery done. Let's say jaggery 0.9.0.ALPHA4.wso2v2. Now a branch is
> created and called 0.9.0.ALPHA4.wso2v2.
>
> If a person has a bug in 0.9.0.ALPHA4.wso2v2 he will fix it in that branch
> (IMO is incorrect). Then they use that branch as a dependency. I propose to
> use a tag as opposed to a branch (0.9.0.ALPHA4.wso2v2). This tag will be
> checked out and the patch will be done and sent to the develop branch. We
> make a new release tag out of that version (which is a patch version) -
> which can be 0.9.0.ALPHA4.wso2v3. But as opposed to branch -it's a tag.
>
> Cheers~
>
>
> On Thu, Apr 3, 2014 at 10:17 AM, Rushmin Fernando wrote:
>
>> The notion of tags are there in almost the all version control systems,
>> though the how they store tags is different.
>>
>> It's true that Git has some addition features to work with tags.
>>
>> But the concept of a tag is to point to a snapshot of the code base which
>> does not change.
>>
>> In Git when we checkout a tag it causes a detached head. You can checkout
>> a tag and build the code, but it is discouraged to commit to a tag since it
>> abusing the purpose.
>>
>> (But you can create a branch from a tag and use it as the bug fix branch)
>>
>> Thank you
>>
>>
>> On Thu, Apr 3, 2014 at 1:01 AM, Chan  wrote:
>>
>>> We do indeed support older releases. Git provides a cool feature for
>>> this called tagging. We tag the master branch when ever we make a release.
>>> If we want to obtain the codebase of 1.0.0 - we just checkout the tag.
>>>
>>> Cheers~
>>>
>>>
>>> On Wed, Apr 2, 2014 at 11:51 AM, Rushmin Fernando wrote:
>>>
 Just thinking aloud since im interested in release management stuff ...

 AFAIK release branches are maintained even after the release to make
 sure a bug fix for a specific release can be done without worrying about
 further releases done (may be practically half baked code as well) in
 develop branch / master.

 But this is subjected to the release pattern of the product. If we
 don't support older releases then we might not need release branches after
 the release since the latest release is reflected in master branch.

 ( But technically in Git we can create a branch from a commit. So
 deleting feature branches might not be a big deal since we can create a
 branch from a tag when a bug fix for a release is needed )


 On Wed, Apr 2, 2014 at 11:08 AM, Chan  wrote:

> Hi Rushmin,
> There will be 2 permanent branches
>
>- master
>- develop
>
> When we work on a feature - we create a branch called
> feature/feature-name on local repo. If there are collaborators we push 
> them
> to remote repo. Afterwards when the feature is complete - we merge it to
> the develop branch.
> If we have a release in 2 weeks - we create a release branch (named
> release/release-name) from the develop branch and work it. This will 
> mostly
> be stabilization work. What ever features that are completed during this
> time will not be available to the release since they are not stable. When
> we release - we merge the release branch to master and develop branch. We
> tag the master branch with release name.
>
> Cheers~
>
> (My previous email fired off with Command +Enter. Apologies to that)
>
>
> On Wed, Apr 2, 2014 at 11:05 AM, Chan  wrote:
>
>> There will be 2 permanent branches
>>
>>- master
>>- develop
>>
>>
>>
>> On Tue, Apr 1, 2014 at 9:30 PM, Rushmin Fernando wrote:
>>
>>> Hi Chan,
>>>
>>> Do you mean that there are obsolete release branches which should be
>>> deleted, after tagging the tips of them ?
>>>
>>> Thanks
>>> /rushmin
>>>
>>>
>>> On Tue, Apr 1, 2014 at 7:45 PM, Chan  wrote:
>>>
  Hi folks,
 I believe we can improve the git workflow of the jaggery
 project[1]. Currently we have many release branches (IMO bad decision 
 since
 these branches will evolve separately). They need to ideally be tags. 
 We
 have been discussing about Git Flow (check Git flow model 
 @architecture) -
 and I think we can sort out most of these troubles with git flow. WDYT?

 [1] - https://github.com/wso2/jaggery/branches
 Cheers

Re: [Dev] Finalizing instrument jar list for BRS

[Thilini Ishaka]

Hi Dharshana,

We mainly need to add drools to the list. Will have a closer look for
further missing jars and get back to you.

Thanks
Thilini


On Wed, Apr 9, 2014 at 12:15 PM, Dharshana Warusavitharana <
dharsha...@wso2.com> wrote:

> Hi ,
>
> Shall we select appropriate jars to be instrument by emma from list of
> jars short listed below.  I have shortlisted the basic set of jars related
> to BRS but we need to figure out which of 3rd party libraries actually we
> need to include for instrumentation.
>
>
> org.wso2.brs.
> org.wso2.brs.
> org.wso2.carbon.rule.
> backport-util-concurrent_3.1.0.wso2v1.jar
>
> org.wso2.carbon.application.
> org.wso2.carbon.authenticator.
> org.wso2.carbon.security.
> org.wso2.carbon.server.
> org.wso2.carbon.caching.
> org.wso2.carbon.service.
> org.wso2.carbon.event.
>
> org.wso2.carbon.throttle.
> org.wso2.carbon.feature.
> org.wso2.carbon.tracer.
> org.wso2.carbon.redirector.
> org.wso2.carbon.logging.
> ehcache_1.5.0.wso2v3.jar
>
> el-impl_2.2.0.wso2v1.jar
> geronimo-saaj_1.3_spec_1.0.0.wso2v3.jar
> httpcore_4.3.0.wso2v1.jar
> infinispan-core_5.1.2.wso2v1.jar
> janino_2.5.15.wso2v1.jar
> javasysmon_0.3.3.wso2v1.jar
> jettison_1.3.4.wso2v1.jar
> jgroups_3.0.6.wso2v1.jar
> joda-time_1.6.0.wso2v1.jar
> json_2.0.0.wso2v1.jar
> jsr107cache_1.1.0.wso2v3.jar
> jsr94_1.1.0.wso2v1.jar
> jstl_1.2.1.wso2v2.jar
>
> abdera_1.0.0.wso2v3.jar
> annogen_0.1.0.wso2v1.jar
> marshalling_1.3.6.wso2v1.jar
> org.wso2.carbon.transport.
> mvel2_2.1.0.wso2v1.jar
> neethi_2.0.4.wso2v4.jar
> opensaml2_2.4.1.wso2v1.jar
>
> org.wso2.carbon.xfer_4.2.0.jar
>
> perf4j_0.9.12.wso2v1.jar
> org.wso2.carbon.policyeditor_4.2.0.jar
>
> poi-scratchpad_3.9.0.wso2v1.jar
>
> tiles-jsp_2.0.5.wso2v1.jar
> woden_1.0.0.M8-wso2v1.jar
>
>
>
> --
>
> Dharshana Warusavitharana
> Senior Software Engineer , Test Automation
> WSO2 Inc. http://wso2.com
> email : dharsha...@wso2.com 
> Tel  : +94 11 214 5345
> Fax: +94 11 2145300
> cell : +94772202595
> blog : http://dharshanaw.blogspot.com
>
> lean . enterprise . middleware
>



-- 
Thilini Ishaka
Senior Software Engineer
Phone: +94 11 214 5345
WSO2 Inc. http://wso2.com

blog: thiliniishaka.blogspot.com
linkedin: http://lk.linkedin.com/in/thiliniishaka
twitter: https://twitter.com/#!/ThiliniIsh
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Finalyzing instrument jar list for MB code coverage

[Nuwan Wimalasekara]

Hi
Update the instrumentation as bellow and attached the new report.

org.wso2.carbon.andes
org.wso2.carbon.cassandra.server
org.wso2.carbon.event

Thanks,
Nuwanw


On Wed, Apr 9, 2014 at 5:25 PM, Shammi Jayasinghe  wrote:

> Hi Nuwan,
>
> No , in standalone mode, coordination stuff is not being used, Thanks for
> the clarification
>
> Thanks
> Shammi
>
>
> On Wed, Apr 9, 2014 at 5:22 PM, Nuwan Wimalasekara wrote:
>
>> Hi Shammi
>> Thanks for the response. I will remove other 
>> org.wso2.carbon.cassandrapackages except
>> org.wso2.carbon.cassandra.server. However We are running the integration
>> test against the standalone mode. So are coordination components used in
>> standalone mode? if so we can add them too
>>
>> Thanks,
>> Nuwanw
>>
>>
>> On Wed, Apr 9, 2014 at 5:07 PM, Shammi Jayasinghe wrote:
>>
>>> Hi Nuwan,
>>>
>>> In MB , we are only using cassandra server feature. Could you please
>>> modify that package to org.wso2.carbon.cassandra.server. Apart from that we
>>> are using coordination component ( zookeeper) also. Please add that to the
>>> list.
>>>
>>> Thanks
>>> shammi
>>>
>>>
>>> On Wed, Apr 9, 2014 at 4:57 PM, Nuwan Wimalasekara wrote:
>>>
 Hi
 As discussed with HasithaH, I have included following packages in 
 integration
 tests instrumentation file in order to get the coverage statistics for
 MB. Please let us know if any other packages(which is inside the MB server)
 need to be included or excluded from the list.

 org.wso2.carbon.andes
 org.wso2.carbon.cassandra
 org.wso2.carbon.event

 Herewith I have attached the coverage report with the above
 instrumentation list. It lists all the packages instrumented by the
 emma as the instrumentation file.


 Thanks,
 Nuwanw
 --
 Nuwan Wimalasekara
 Senior Software Engineer - Test Automation
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware

 phone: +94 71 668 4620




>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> *  Shammi Jayasinghe*
>>> Associate Tech Lead
>>> WSO2, Inc.; http://wso2.com,
>>> mobile: +94 71 4493085
>>>
>>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
> Best Regards,
>
> *  Shammi Jayasinghe*
> Associate Tech Lead
> WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
Title: EMMA Coverage Report (generated Wed Apr 09 17:47:26 IST 2014)
EMMA Coverage Report (generated Wed Apr 09 17:47:26 IST 2014)[all classes]OVERALL COVERAGE SUMMARYnameline, %block, %method, %class, %all classes3%   (983.5/38968)2%   (3614/167190)6%   (304/5214)12%  (63/528)OVERALL STATS SUMMARYtotal packages:79total executable files:319total classes:528total methods:5214total executable lines:38968COVERAGE BREAKDOWN BY PACKAGEnameline, %block, %method, %class, %org.wso2.carbon.andes.authentication.service100% (5/5)100% (12/12)100% (2/2)100% (1/1)org.wso2.carbon.andes.authentication.internal97%  (32/33)97%  (86/89)94%  (15/16)100% (2/2)org.wso2.carbon.andes.commons.internal96%  (22/23)94%  (48/51)93%  (13/14)100% (2/2)org.wso2.carbon.andes.authorization.internal91%  (32/35)87%  (91/105)93%  (14/15)100% (2/2)org.wso2.carbon.event.admin.internal.util91%  (10/11)88%  (23/26)89%  (8/9)100% (2/2)org.wso2.carbon.event.ws.internal90%  (19/21)88%  (44/50)86%  (12/14)100% (2/2)org.wso2.carbon.andes.admin.util90%  (19/21)88%  (43/49)86%  (12/14)100% (2/2)org.wso2.carbon.cassandra.server.internal86%  (59/69)85%  (205/240)95%  (19/20)100% (2/2)org.wso2.carbon.andes.core.internal.ds84%  (26/31)82%  (62/76)83%  (15/18)100% (2/2)org.wso2.carbon.cassandra.server.service71%  (5/7)71%  (10/14)67%  (2/3)100% (1/1)org.wso2.carbon.cassandra.server.util67%  (5.4/8)66%  (25/38)67%  (2/3)100% (1/1)org.wso2.carbon.andes.core.internal.builder67%  (2/3)67%  (6/9)50%  (1/2)100% (1/1)org.wso2.carbon.andes.authorization.service.andes63%  (48.8/77)65%  (227/349)71%  (12/17)100% (5/5)org.wso2.carbon.andes.internal63%  (121.9/193)53%  (448/838)97%  (33/34)100% (2/2)org.wso2.carbon.event.core.internal.builder62%  (64.4/104)59%  (249/424)86%  (19/22)100% (4/4)org.wso2.carbon.andes.authorization.andes56%  (76.1/137)63%  (368/581)67%  (12/18)50%  (1/2)org.wso2.carbon.andes.authentication.andes50%  (35.3/70)43%  (115/267)38%  (5/13)100% (1/1)org.wso2.carbon.andes.commons.registry45%  (50.7/113)41%  (185/452)42%  (5/12)50%  (1/2)org.wso2.carbon.cassandra.server42%  (89.8/214)47%  (366/779)48%  (26/54)62%  (5/8)org.wso2.carbon.andes.service38%  (90.4/240)27%  (364/1339)57%  (20/35)100% (1/1)org.wso2.carbon.event.core.internal32%  (40.6/128)32%  (160/500)36%  (10/28)67%  (2/3)org.wso2.carbon.andes.commons27%  (13/49)43%  (87/203)12%  (3/25)33%  (1/3)org.wso2.carbon.event.core.interna

Re: [Dev] [GIT]Error deploying the HT in G-Reg

[Ajith Vitharana]

Any update on this plz ?, because this is a blocker to G-Reg milestone
 release.

Thanks.
Ajith


On Wed, Apr 9, 2014 at 10:24 AM, Ajith Vitharana  wrote:

> Hi All,
>
> I have updated the scripts according the modifications in BPS, But still
> I'm getting following error deploying the HT file.
>
> Any idea to fix this ?
>
>
> [2014-04-09 10:16:26,752] ERROR
> {org.wso2.carbon.humantask.deployer.HumanTaskDeployer} -  Error deploying
> HumanTask package : WorkList.zip
> 
> org.apache.openjpa.persistence.ArgumentException: An error occurred while
> parsing the query filter "select v from TaskVersion v". Error message: The
> name "TaskVersion" is not a recognized entity or identifier. Perhaps you
> meant DeploymentUnit, which is a close match. Known entity names:
> [DeploymentUnit]
>  at
> org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parseException(AbstractExpressionBuilder.java:119)
> at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getClassMetaData(JPQLExpressionBuilder.java:194)
>  at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.resolveClassMetaData(JPQLExpressionBuilder.java:167)
> at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:242)
>  at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:212)
> at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateType(JPQLExpressionBuilder.java:205)
>  at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.access$200(JPQLExpressionBuilder.java:80)
> at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.populate(JPQLExpressionBuilder.java:2417)
>  at org.apache.openjpa.kernel.jpql.JPQLParser.populate(JPQLParser.java:61)
> at
> org.apache.openjpa.kernel.ExpressionStoreQuery.populateFromCompilation(ExpressionStoreQuery.java:162)
>  at org.apache.openjpa.kernel.QueryImpl.newCompilation(QueryImpl.java:673)
> at
> org.apache.openjpa.kernel.QueryImpl.compilationFromCache(QueryImpl.java:654)
>  at
> org.apache.openjpa.kernel.QueryImpl.compileForCompilation(QueryImpl.java:620)
> at
> org.apache.openjpa.kernel.QueryImpl.compileForExecutor(QueryImpl.java:682)
>  at org.apache.openjpa.kernel.QueryImpl.compile(QueryImpl.java:589)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:997)
>  at
> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:979)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:102)
>  at
> org.wso2.carbon.humantask.core.dao.jpa.openjpa.HumanTaskDAOConnectionImpl.getNextVersion(HumanTaskDAOConnectionImpl.java:429)
> at
> org.wso2.carbon.humantask.core.store.HumanTaskStore$3.call(HumanTaskStore.java:1112)
>  at
> org.wso2.carbon.humantask.core.store.HumanTaskStore$3.call(HumanTaskStore.java:1108)
> at
> org.wso2.carbon.humantask.core.scheduler.SimpleScheduler.execTransaction(SimpleScheduler.java:880)
>  at
> org.wso2.carbon.humantask.core.scheduler.SimpleScheduler.execTransaction(SimpleScheduler.java:829)
> at
> org.wso2.carbon.humantask.core.store.HumanTaskStore.getNextVersion(HumanTaskStore.java:1107)
>  at
> org.wso2.carbon.humantask.core.store.HumanTaskStore.deploy(HumanTaskStore.java:420)
> at
> org.wso2.carbon.humantask.deployer.HumanTaskDeployer.deploy(HumanTaskDeployer.java:68)
>  at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>  at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>  at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
>  at
> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:464)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
>  at
> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>  at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at

Re: [Dev] Finalizing instrument jar list for BRS

[Dharshana Warusavitharana]

Thanx Thilini,

Will add.


On Wed, Apr 9, 2014 at 5:54 PM, Thilini Ishaka  wrote:

> Hi Dharshana,
>
> We mainly need to add drools to the list. Will have a closer look for
> further missing jars and get back to you.
>
> Thanks
> Thilini
>
>
> On Wed, Apr 9, 2014 at 12:15 PM, Dharshana Warusavitharana <
> dharsha...@wso2.com> wrote:
>
>> Hi ,
>>
>> Shall we select appropriate jars to be instrument by emma from list of
>> jars short listed below.  I have shortlisted the basic set of jars related
>> to BRS but we need to figure out which of 3rd party libraries actually we
>> need to include for instrumentation.
>>
>>
>> org.wso2.brs.
>> org.wso2.brs.
>> org.wso2.carbon.rule.
>> backport-util-concurrent_3.1.0.wso2v1.jar
>>
>> org.wso2.carbon.application.
>> org.wso2.carbon.authenticator.
>> org.wso2.carbon.security.
>> org.wso2.carbon.server.
>> org.wso2.carbon.caching.
>> org.wso2.carbon.service.
>> org.wso2.carbon.event.
>>
>> org.wso2.carbon.throttle.
>> org.wso2.carbon.feature.
>> org.wso2.carbon.tracer.
>> org.wso2.carbon.redirector.
>> org.wso2.carbon.logging.
>> ehcache_1.5.0.wso2v3.jar
>>
>> el-impl_2.2.0.wso2v1.jar
>> geronimo-saaj_1.3_spec_1.0.0.wso2v3.jar
>> httpcore_4.3.0.wso2v1.jar
>> infinispan-core_5.1.2.wso2v1.jar
>> janino_2.5.15.wso2v1.jar
>> javasysmon_0.3.3.wso2v1.jar
>> jettison_1.3.4.wso2v1.jar
>> jgroups_3.0.6.wso2v1.jar
>> joda-time_1.6.0.wso2v1.jar
>> json_2.0.0.wso2v1.jar
>> jsr107cache_1.1.0.wso2v3.jar
>> jsr94_1.1.0.wso2v1.jar
>> jstl_1.2.1.wso2v2.jar
>>
>>
>> abdera_1.0.0.wso2v3.jar
>> annogen_0.1.0.wso2v1.jar
>> marshalling_1.3.6.wso2v1.jar
>> org.wso2.carbon.transport.
>> mvel2_2.1.0.wso2v1.jar
>> neethi_2.0.4.wso2v4.jar
>> opensaml2_2.4.1.wso2v1.jar
>>
>> org.wso2.carbon.xfer_4.2.0.jar
>>
>> perf4j_0.9.12.wso2v1.jar
>> org.wso2.carbon.policyeditor_4.2.0.jar
>>
>> poi-scratchpad_3.9.0.wso2v1.jar
>>
>> tiles-jsp_2.0.5.wso2v1.jar
>> woden_1.0.0.M8-wso2v1.jar
>>
>>
>>
>> --
>>
>> Dharshana Warusavitharana
>> Senior Software Engineer , Test Automation
>> WSO2 Inc. http://wso2.com
>> email : dharsha...@wso2.com 
>> Tel  : +94 11 214 5345
>> Fax: +94 11 2145300
>> cell : +94772202595
>> blog : http://dharshanaw.blogspot.com
>>
>> lean . enterprise . middleware
>>
>
>
>
> --
> Thilini Ishaka
> Senior Software Engineer
> Phone: +94 11 214 5345
> WSO2 Inc. http://wso2.com
>
> blog: thiliniishaka.blogspot.com
> linkedin: http://lk.linkedin.com/in/thiliniishaka
> twitter: https://twitter.com/#!/ThiliniIsh
>



-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94772202595
blog : http://dharshanaw.blogspot.com

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

[Dev] Freezing Carbon Kernel Patch 06 Development

[Anjana Fernando]

Hi,

Shall we freeze development of kernel patch6, since Turing chunk08 is
scheduled for release on 11'th. So basically, please refrain from
committing anything to patch6.

Cheers,
Anjana.
-- 
*Anjana Fernando*
Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Freezing Carbon Kernel Patch 06 Development

[Manoj Kumara]

Noted.

Thanks,
Manoj


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


On Wed, Apr 9, 2014 at 6:35 PM, Anjana Fernando  wrote:

> Hi,
>
> Shall we freeze development of kernel patch6, since Turing chunk08 is
> scheduled for release on 11'th. So basically, please refrain from
> committing anything to patch6.
>
> Cheers,
> Anjana.
> --
> *Anjana Fernando*
> Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please merge carbon4-kernel #17 pull request

[Sajith Kariyawasam]

Hi,

Please merge the following pull request

https://github.com/wso2-dev/carbon4-kernel/pull/17

Related JIRA
https://wso2.org/jira/browse/BPS-497


Thanks,
Sajith

-- 
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.*
*AMIE (SL)*
*Blog: http://sajithblogs.blogspot.com/ *
*Mobile: +94772269575*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GIT]Error deploying the HT in G-Reg

[Nandika Jayawardana]

This was due to using the wrong openjpa version.

Regards
Nandika


On Wed, Apr 9, 2014 at 6:00 PM, Ajith Vitharana  wrote:

> Any update on this plz ?, because this is a blocker to G-Reg milestone
>  release.
>
> Thanks.
> Ajith
>
>
> On Wed, Apr 9, 2014 at 10:24 AM, Ajith Vitharana  wrote:
>
>> Hi All,
>>
>> I have updated the scripts according the modifications in BPS, But still
>> I'm getting following error deploying the HT file.
>>
>> Any idea to fix this ?
>>
>>
>> [2014-04-09 10:16:26,752] ERROR
>> {org.wso2.carbon.humantask.deployer.HumanTaskDeployer} -  Error deploying
>> HumanTask package : WorkList.zip
>> 
>> org.apache.openjpa.persistence.ArgumentException: An error occurred while
>> parsing the query filter "select v from TaskVersion v". Error message: The
>> name "TaskVersion" is not a recognized entity or identifier. Perhaps you
>> meant DeploymentUnit, which is a close match. Known entity names:
>> [DeploymentUnit]
>>  at
>> org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parseException(AbstractExpressionBuilder.java:119)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getClassMetaData(JPQLExpressionBuilder.java:194)
>>  at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.resolveClassMetaData(JPQLExpressionBuilder.java:167)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:242)
>>  at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:212)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateType(JPQLExpressionBuilder.java:205)
>>  at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.access$200(JPQLExpressionBuilder.java:80)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.populate(JPQLExpressionBuilder.java:2417)
>>  at
>> org.apache.openjpa.kernel.jpql.JPQLParser.populate(JPQLParser.java:61)
>> at
>> org.apache.openjpa.kernel.ExpressionStoreQuery.populateFromCompilation(ExpressionStoreQuery.java:162)
>>  at
>> org.apache.openjpa.kernel.QueryImpl.newCompilation(QueryImpl.java:673)
>> at
>> org.apache.openjpa.kernel.QueryImpl.compilationFromCache(QueryImpl.java:654)
>>  at
>> org.apache.openjpa.kernel.QueryImpl.compileForCompilation(QueryImpl.java:620)
>> at
>> org.apache.openjpa.kernel.QueryImpl.compileForExecutor(QueryImpl.java:682)
>>  at org.apache.openjpa.kernel.QueryImpl.compile(QueryImpl.java:589)
>> at
>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:997)
>>  at
>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:979)
>> at
>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:102)
>>  at
>> org.wso2.carbon.humantask.core.dao.jpa.openjpa.HumanTaskDAOConnectionImpl.getNextVersion(HumanTaskDAOConnectionImpl.java:429)
>> at
>> org.wso2.carbon.humantask.core.store.HumanTaskStore$3.call(HumanTaskStore.java:1112)
>>  at
>> org.wso2.carbon.humantask.core.store.HumanTaskStore$3.call(HumanTaskStore.java:1108)
>> at
>> org.wso2.carbon.humantask.core.scheduler.SimpleScheduler.execTransaction(SimpleScheduler.java:880)
>>  at
>> org.wso2.carbon.humantask.core.scheduler.SimpleScheduler.execTransaction(SimpleScheduler.java:829)
>> at
>> org.wso2.carbon.humantask.core.store.HumanTaskStore.getNextVersion(HumanTaskStore.java:1107)
>>  at
>> org.wso2.carbon.humantask.core.store.HumanTaskStore.deploy(HumanTaskStore.java:420)
>> at
>> org.wso2.carbon.humantask.deployer.HumanTaskDeployer.deploy(HumanTaskDeployer.java:68)
>>  at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>>  at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>  at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
>>  at
>> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:464)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
>>  at
>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>>  at
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  at
>> sun.

Re: [Dev] [GIT]Error deploying the HT in G-Reg

[Ajith Vitharana]

On Wed, Apr 9, 2014 at 6:44 PM, Nandika Jayawardana wrote:

> This was due to using the wrong openjpa version.
>

Thanks a lot for the quick response !!

-Ajith.

>
>

> Regards
> Nandika
>
>
> On Wed, Apr 9, 2014 at 6:00 PM, Ajith Vitharana  wrote:
>
>> Any update on this plz ?, because this is a blocker to G-Reg milestone
>>  release.
>>
>> Thanks.
>> Ajith
>>
>>
>> On Wed, Apr 9, 2014 at 10:24 AM, Ajith Vitharana  wrote:
>>
>>> Hi All,
>>>
>>> I have updated the scripts according the modifications in BPS, But still
>>> I'm getting following error deploying the HT file.
>>>
>>> Any idea to fix this ?
>>>
>>>
>>> [2014-04-09 10:16:26,752] ERROR
>>> {org.wso2.carbon.humantask.deployer.HumanTaskDeployer} -  Error deploying
>>> HumanTask package : WorkList.zip
>>> 
>>> org.apache.openjpa.persistence.ArgumentException: An error occurred while
>>> parsing the query filter "select v from TaskVersion v". Error message: The
>>> name "TaskVersion" is not a recognized entity or identifier. Perhaps you
>>> meant DeploymentUnit, which is a close match. Known entity names:
>>> [DeploymentUnit]
>>>  at
>>> org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parseException(AbstractExpressionBuilder.java:119)
>>> at
>>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getClassMetaData(JPQLExpressionBuilder.java:194)
>>>  at
>>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.resolveClassMetaData(JPQLExpressionBuilder.java:167)
>>> at
>>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:242)
>>>  at
>>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(JPQLExpressionBuilder.java:212)
>>> at
>>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateType(JPQLExpressionBuilder.java:205)
>>>  at
>>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.access$200(JPQLExpressionBuilder.java:80)
>>> at
>>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.populate(JPQLExpressionBuilder.java:2417)
>>>  at
>>> org.apache.openjpa.kernel.jpql.JPQLParser.populate(JPQLParser.java:61)
>>> at
>>> org.apache.openjpa.kernel.ExpressionStoreQuery.populateFromCompilation(ExpressionStoreQuery.java:162)
>>>  at
>>> org.apache.openjpa.kernel.QueryImpl.newCompilation(QueryImpl.java:673)
>>> at
>>> org.apache.openjpa.kernel.QueryImpl.compilationFromCache(QueryImpl.java:654)
>>>  at
>>> org.apache.openjpa.kernel.QueryImpl.compileForCompilation(QueryImpl.java:620)
>>> at
>>> org.apache.openjpa.kernel.QueryImpl.compileForExecutor(QueryImpl.java:682)
>>>  at org.apache.openjpa.kernel.QueryImpl.compile(QueryImpl.java:589)
>>> at
>>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:997)
>>>  at
>>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:979)
>>> at
>>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:102)
>>>  at
>>> org.wso2.carbon.humantask.core.dao.jpa.openjpa.HumanTaskDAOConnectionImpl.getNextVersion(HumanTaskDAOConnectionImpl.java:429)
>>> at
>>> org.wso2.carbon.humantask.core.store.HumanTaskStore$3.call(HumanTaskStore.java:1112)
>>>  at
>>> org.wso2.carbon.humantask.core.store.HumanTaskStore$3.call(HumanTaskStore.java:1108)
>>> at
>>> org.wso2.carbon.humantask.core.scheduler.SimpleScheduler.execTransaction(SimpleScheduler.java:880)
>>>  at
>>> org.wso2.carbon.humantask.core.scheduler.SimpleScheduler.execTransaction(SimpleScheduler.java:829)
>>> at
>>> org.wso2.carbon.humantask.core.store.HumanTaskStore.getNextVersion(HumanTaskStore.java:1107)
>>>  at
>>> org.wso2.carbon.humantask.core.store.HumanTaskStore.deploy(HumanTaskStore.java:420)
>>> at
>>> org.wso2.carbon.humantask.deployer.HumanTaskDeployer.deploy(HumanTaskDeployer.java:68)
>>>  at
>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>>> at
>>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>>>  at
>>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>>  at
>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>>> at
>>> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
>>>  at
>>> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:464)
>>> at
>>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
>>>  at
>>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>>>  at
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreSe

[Dev] ESB 4.8.1 - sample 360 - Exception when trying to access database

[Sameera Kannangara]

Hi all,

When running ESB 4.8.1 - sample 360
[1],
I got the following exception and stack trace.

ERROR - DBLookupMediator Error executing statement : select * from company
where name =? against DataSource :
jdbc:derby://localhost:1527/esbdb;create=false
org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class
'org.apache.derby.jdbc.ClientDriver'
at
org.apache.commons.dbcp.BasicDataSource.createConnectionFactory(BasicDataSource.java:1429)
at
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1371)
at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at
org.apache.synapse.mediators.db.DBLookupMediator.processStatement(DBLookupMediator.java:44)
at
org.apache.synapse.mediators.db.AbstractDBMediator.mediate(AbstractDBMediator.java:143)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
at
org.apache.synapse.mediators.filters.InMediator.mediate(InMediator.java:61)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:228)
at
org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException:
org.apache.derby.jdbc.ClientDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.eclipse.core.runtime.internal.adaptor.ContextFinder.loadClass(ContextFinder.java:131)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.apache.commons.dbcp.BasicDataSource.createConnectionFactory(BasicDataSource.java:1420)
... 19 more

When searching for fixes for above problem I came across a youtube video
explaining how to run ESB sample 360 at
[2]
.
According the video, jar files derby.jar, derbyclient.jar and derbynet.jar
should be added to both /repository/components/extensions and
/repository/components/lib directories.
But the instruction to add above jars to the
/repository/components/extensions directory seems to be missing
in the documentation.
After adding jars to both directories ESB 4.8.1 - sample 360 runs correctly
and provides expected outputs.

Is there another way to fix this problem?

Thank you,
-- 
Sameera Kannangara,
Software Engineer,
WSO2 Inc.

[1]
https://docs.wso2.org/display/ESB481/Sample+360%3A+Introduction+to+dblookup+Mediator
[2] https://www.youtube.com/watch?v=gStDjnS0JTw
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB Cassandra profile memory allocation

[Bhathiya Jayasekara]

Hi Indika,

Currently 'Cassandra in Windows' is not production recommended. Discussed
in here [1] too. So I don't think you need to worry about memory
allocations for windows for now.

[1] "Can API Manager and BAM run on Windows server"

Thanks,
Bhathiya


On Wed, Apr 9, 2014 at 4:29 AM, Indika Sampath  wrote:

> Hi All,
>
> The following changes I did in the MB product and achieve the $subject.
>
> Copy the cassandra-env.sh with the changes I made to compatible with
> org.wso2.carbon.core.bootup.validator.JVMValidator to the {MB_HOME}/bin
> folder when pack is build
> Load the cassandra-env.sh when MB start with cassandra profile
> Set the -Xms  -Xmx -XX:MaxPermSize parameters dynamically as calculated in
> the cassandra-env.sh
>
> This is working in the Linux. Now I have a problem with how to make this
> changes which is compatible to the Windows environment. I have already make
> the .bat file to start with the cassandra profile before. But now the
> problem is I couldn't load the cassandra-env.sh in Windows. Is there
> something which is relevant to cassandra-env.sh in Windows environment ?
>
> Cheers!
>
>
> On Wed, Apr 9, 2014 at 11:46 AM, Prabath Abeysekera wrote:
>
>>
>> On Wed, Apr 9, 2014 at 11:16 AM, Dhanuka Ranasinghe wrote:
>>
>>> Hi,
>>>
>>> What about other important JVM tuning parameters (GC threads and
>>> strategy), Are you guys consider those as well?
>>>
>>
>> If we are to make the Cassandra profile, fully Cassandra-like, yeah, it's
>> a must we include all the required/recommended JVM parameters (including
>> what's used for fine tuning the functionalities) in the start-up script as
>> well.
>>
>> Cheers,
>> Prabath
>>
>>
>>>
>>> Cheers,
>>> Dhanuka
>>>
>>> *Dhanuka Ranasinghe*
>>>
>>> Senior Software Engineer
>>> WSO2 Inc. ; http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> phone : +94 715381915
>>>
>>>
>>> On Wed, Apr 9, 2014 at 11:08 AM, Shammi Jayasinghe wrote:
>>>
 Hi Deep,

 +1, that is what i wanted. It would be great if you can add this to the
 startup script of Cassandra profile.

 Hi Indika,

 Could you please talk to deep on this.

 thanks
 Shammi


 On Wed, Apr 9, 2014 at 10:51 AM, Deependra Ariyadewa wrote:

>
>
>
> On Wed, Apr 9, 2014 at 8:51 AM, Shammi Jayasinghe wrote:
>
>>
>>
>>
>> On Tue, Apr 8, 2014 at 7:29 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>>
>>>
>>>
>>> On Tue, Apr 8, 2014 at 12:14 PM, Shammi Jayasinghe 
>>> wrote:
>>>



 On Tue, Apr 8, 2014 at 11:55 AM, Deependra Ariyadewa >>> > wrote:

>
>
>
> On Tue, Apr 8, 2014 at 11:32 AM, Shammi Jayasinghe <
> sha...@wso2.com> wrote:
>
>> Hi ,
>>
>> I think we should not ask the user to change the .sh file or .bat
>> file when starting with the cassandra profile. What we can do is, as
>> default cassandra server does, we need to fix MB in a way that , 
>> when we
>> start the MB with Cassandra profile, it automatically allocates 1/3 
>> of the
>> total memory for MB. WDYT ?
>>
>
> We should be able to calculate required memory in the
> wso2server.sh.
>

 Hi Sameera / Kishanthan,

  We have  a requirement that the memory allocated when MB server
 starts with Cassandra profile should be a portion of the complete 
 memory of
 the server. Is it possible to do it and if it is possible, how we 
 should
 proceed ?

>>>
>>> We currently don't use profile specific configurations (such as
>>> specific start-up scripts, etc) when starting up profiles. We start
>>> profiles after the java process is started and all profiles use the same
>>> configurations. So this will not be possible using carbon server startup
>>> scripts.
>>>
>>> But can't you use MB/Cassandra specific startup script for this?
>>> This script should set the relevant JVM parameters and call server 
>>> start-up
>>> with cassandra profile.
>>>
>>
>> Hi Kishanthan,
>>
>> Yes, we may able to use that scripts to fulfil this requirement.
>> Actually what i wanted to know is whether we have inbuilt support from
>> carbon for this requirement and thank you for clarifying.
>>
>> Hi Prabath/Deep,
>>
>> Do you have any idea on how cassandra handle the dynamic memory
>> allocation for the product. I think , it will be a pain if we ask the 
>> user
>> to change wso2server.sh or wso2server.bat if they want to start MB or SS
>> with cassandra profile since with default memory allocation will not be
>> enough for cassandra.
>>
>
> We can add following logic use in cassandra-env.sh to Cassandra
> profile startup section 

Re: [Dev] ESB 4.8.1 - sample 360 - Exception when trying to access database

[Gayan Yalpathwala]

Hi Sameera,

In order to create derby databases, those three jars should be present in
the /repository/components/extensions directory. Secondly, the same set of
drivers should be present in /repository/components/lib directory where
dblookup mediator will pick them up. The first purpose is clearly mentioned
in [1]. I think the same thing should be mentioned in [2] as well.

@Isuru, Can you please confirm this?

[1] https://docs.wso2.org/display/ESB481/Setting+up+with+Remote+Derby
[2] https://docs.wso2.org/display/ESB481/Setting+Up+the+ESB+Samples

Thanks,


On Wed, Apr 9, 2014 at 9:28 PM, Sameera Kannangara wrote:

> Hi all,
>
> When running ESB 4.8.1 - sample 360 
> [1],
> I got the following exception and stack trace.
>
> ERROR - DBLookupMediator Error executing statement : select * from company
> where name =? against DataSource :
> jdbc:derby://localhost:1527/esbdb;create=false
> org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class
> 'org.apache.derby.jdbc.ClientDriver'
> at
> org.apache.commons.dbcp.BasicDataSource.createConnectionFactory(BasicDataSource.java:1429)
> at
> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1371)
> at
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
> at
> org.apache.synapse.mediators.db.DBLookupMediator.processStatement(DBLookupMediator.java:44)
> at
> org.apache.synapse.mediators.db.AbstractDBMediator.mediate(AbstractDBMediator.java:143)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
> at
> org.apache.synapse.mediators.filters.InMediator.mediate(InMediator.java:61)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:228)
> at
> org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
> at
> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.derby.jdbc.ClientDriver
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at
> org.eclipse.core.runtime.internal.adaptor.ContextFinder.loadClass(ContextFinder.java:131)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at
> org.apache.commons.dbcp.BasicDataSource.createConnectionFactory(BasicDataSource.java:1420)
> ... 19 more
>
> When searching for fixes for above problem I came across a youtube video
> explaining how to run ESB sample 360 at 
> [2]
> .
> According the video, jar files derby.jar, derbyclient.jar and derbynet.jar
> should be added to both /repository/components/extensions and
> /repository/components/lib directories.
> But the instruction to add above jars to the
> /repository/components/extensions directory seems to be missing
> in the documentation.
> After adding jars to both directories ESB 4.8.1 - sample 360 runs
> correctly and provides expected outputs.
>
> Is there another way to fix this problem?
>
> Thank you,
> --
> Sameera Kannangara,
> Software Engineer,
> WSO2 Inc.
>
> [1]
> https://docs.wso2.org/display/ESB481/Sample+360%3A+Introduction+to+dblookup+Mediator
> [2] https://www.youtube.com/watch?v=gStDjnS0JTw
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Gayan Kaushalya Yalpathwala*
 Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 71 8682704 


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

Re: [Dev] Regard JSP page errors

[Manoj Kumara]

Hi,

As requested I have added this property to start-up script with [1],

[1] https://wso2.org/jira/browse/CARBON-14755

Thanks,
Manoj


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


On Wed, Apr 9, 2014 at 12:16 PM, Ajith Vitharana  wrote:

>
>
>
> On Wed, Apr 9, 2014 at 12:11 PM, Kasun Gajasinghe  wrote:
>
>> Hi Vanji,
>>
>> Jasper version upgrade has been discussed in previous threads, and the AS
>> jira ticket you just mentioned [1] contains a comprehensive details about
>> this upgrade.
>>
>> Since this error could be there in hundreds of JSP pages, and there is no
>> apparent gain by fixing this particular issue, I guess it's better if we
>> can stop the strict quote escape rule. You can disable this by adding the
>> following system property.
>>
>> org.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
>>
>
> +1. I'm also experiencing same issue in G-Reg pack. Shall we include this
> to start up scrip ?
>
> -Ajith
>
>
>> [1] 
>> https://wso2.org/jira/browse/WSAS-168
>>
>>
>
>> Regards,
>> KasunG
>>
>>
>> On Wed, Apr 9, 2014 at 11:38 AM, Vanjikumaran Sivajothy 
>> wrote:
>>
>>> Hi,
>>>
>>> The latest build of ESB pack getting lots of JSP based exception, and we
>>> found that there were a update on jasper version and strict enforcement on
>>> the jsp rules [1]
>>>
>>> This change might affect other products as well,
>>>
>>> Thus why this is not informed? and what is the plan to fixes these kind
>>> a dead pages?
>>>
>>> [1] https://wso2.org/jira/browse/WSAS-1687
>>>
>>> 2014-04-09 11:12:22,305] ERROR - ApplicationDispatcher
>>> Servlet.service() for servlet bridgeservlet threw exception
>>> org.apache.jasper.JasperException: /proxyservices/templates.jsp (line:
>>> 73, column: 61) Attribute value template+".desc" is quoted with " which
>>> must be escaped when used within the value
>>>  at
>>> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:42)
>>>  at
>>> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:443)
>>> at
>>> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:89)
>>>  at
>>> org.apache.jasper.compiler.Parser.parseAttributeValue(Parser.java:280)
>>>  at org.apache.jasper.compiler.Parser.parseAttribute(Parser.java:229)
>>> at org.apache.jasper.compiler.Parser.parseAttributes(Parser.java:162)
>>>  at org.apache.jasper.compiler.Parser.parseAttributes(Parser.java:153)
>>>  at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1236)
>>> at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1452)
>>>  at org.apache.jasper.compiler.Parser.parseBody(Parser.java:1664)
>>>  at
>>> org.apache.jasper.compiler.Parser.parseOptionalBody(Parser.java:1002)
>>> at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1274)
>>>  at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1452)
>>>  at org.apache.jasper.compiler.Parser.parse(Parser.java:138)
>>> at
>>> org.apache.jasper.compiler.ParserController.doParse(ParserController.java:242)
>>>  at
>>> org.apache.jasper.compiler.ParserController.parse(ParserController.java:102)
>>>  at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198)
>>> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:373)
>>>  at org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
>>>  at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
>>> at
>>> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
>>>  at
>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
>>>  at
>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
>>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
>>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>>  at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>>  at
>>> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
>>>  at
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>  at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>>  at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>>>  at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>>  at
>>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispat

[Dev] Corrupted jaggeryjs.feature downloading from nexus

[Ajith Vitharana]

Hi All,

The registry.indexing jar which is included in [1] is corrupted. Shall we
trigger new build and deploy the feature again ?

[1]
http://maven.wso2.org/nexus/content/repositories/snapshots/org/jaggeryjs/org.jaggeryjs.feature/0.9.0.ALPHA5.wso2v1-SNAPSHOT/org.jaggeryjs.feature-0.9.0.ALPHA5.wso2v1-20140327.094039-4.zip

-Ajith.

-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB Cassandra profile memory allocation

[Hasitha Hiranya]

Hi,

Then should not we recommend to run WSO2 MB in Windows environment?
What about putting it into the docs??

Thanks.


On Wed, Apr 9, 2014 at 10:15 PM, Bhathiya Jayasekara wrote:

> Hi Indika,
>
> Currently 'Cassandra in Windows' is not production recommended. Discussed
> in here [1] too. So I don't think you need to worry about memory
> allocations for windows for now.
>
> [1] "Can API Manager and BAM run on Windows server"
>
> Thanks,
> Bhathiya
>
>
> On Wed, Apr 9, 2014 at 4:29 AM, Indika Sampath  wrote:
>
>> Hi All,
>>
>> The following changes I did in the MB product and achieve the $subject.
>>
>> Copy the cassandra-env.sh with the changes I made to compatible with
>> org.wso2.carbon.core.bootup.validator.JVMValidator to the {MB_HOME}/bin
>> folder when pack is build
>> Load the cassandra-env.sh when MB start with cassandra profile
>> Set the -Xms  -Xmx -XX:MaxPermSize parameters dynamically as calculated
>> in the cassandra-env.sh
>>
>> This is working in the Linux. Now I have a problem with how to make this
>> changes which is compatible to the Windows environment. I have already make
>> the .bat file to start with the cassandra profile before. But now the
>> problem is I couldn't load the cassandra-env.sh in Windows. Is there
>> something which is relevant to cassandra-env.sh in Windows environment ?
>>
>> Cheers!
>>
>>
>> On Wed, Apr 9, 2014 at 11:46 AM, Prabath Abeysekera wrote:
>>
>>>
>>> On Wed, Apr 9, 2014 at 11:16 AM, Dhanuka Ranasinghe wrote:
>>>
 Hi,

 What about other important JVM tuning parameters (GC threads and
 strategy), Are you guys consider those as well?

>>>
>>> If we are to make the Cassandra profile, fully Cassandra-like, yeah,
>>> it's a must we include all the required/recommended JVM parameters
>>> (including what's used for fine tuning the functionalities) in the start-up
>>> script as well.
>>>
>>> Cheers,
>>> Prabath
>>>
>>>

 Cheers,
 Dhanuka

 *Dhanuka Ranasinghe*

 Senior Software Engineer
 WSO2 Inc. ; http://wso2.com
 lean . enterprise . middleware

 phone : +94 715381915


 On Wed, Apr 9, 2014 at 11:08 AM, Shammi Jayasinghe wrote:

> Hi Deep,
>
> +1, that is what i wanted. It would be great if you can add this to
> the startup script of Cassandra profile.
>
> Hi Indika,
>
> Could you please talk to deep on this.
>
> thanks
> Shammi
>
>
> On Wed, Apr 9, 2014 at 10:51 AM, Deependra Ariyadewa wrote:
>
>>
>>
>>
>> On Wed, Apr 9, 2014 at 8:51 AM, Shammi Jayasinghe wrote:
>>
>>>
>>>
>>>
>>> On Tue, Apr 8, 2014 at 7:29 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>



 On Tue, Apr 8, 2014 at 12:14 PM, Shammi Jayasinghe >>> > wrote:

>
>
>
> On Tue, Apr 8, 2014 at 11:55 AM, Deependra Ariyadewa <
> d...@wso2.com> wrote:
>
>>
>>
>>
>> On Tue, Apr 8, 2014 at 11:32 AM, Shammi Jayasinghe <
>> sha...@wso2.com> wrote:
>>
>>> Hi ,
>>>
>>> I think we should not ask the user to change the .sh file or
>>> .bat file when starting with the cassandra profile. What we can do 
>>> is, as
>>> default cassandra server does, we need to fix MB in a way that , 
>>> when we
>>> start the MB with Cassandra profile, it automatically allocates 1/3 
>>> of the
>>> total memory for MB. WDYT ?
>>>
>>
>> We should be able to calculate required memory in the
>> wso2server.sh.
>>
>
> Hi Sameera / Kishanthan,
>
>  We have  a requirement that the memory allocated when MB server
> starts with Cassandra profile should be a portion of the complete 
> memory of
> the server. Is it possible to do it and if it is possible, how we 
> should
> proceed ?
>

 We currently don't use profile specific configurations (such as
 specific start-up scripts, etc) when starting up profiles. We start
 profiles after the java process is started and all profiles use the 
 same
 configurations. So this will not be possible using carbon server 
 startup
 scripts.

 But can't you use MB/Cassandra specific startup script for this?
 This script should set the relevant JVM parameters and call server 
 start-up
 with cassandra profile.

>>>
>>> Hi Kishanthan,
>>>
>>> Yes, we may able to use that scripts to fulfil this requirement.
>>> Actually what i wanted to know is whether we have inbuilt support from
>>> carbon for this requirement and thank you for clarifying.
>>>
>>> Hi Prabath/Deep,
>>>
>>> Do you have any idea on how cassandra handle the dynamic

Re: [Dev] Corrupted jaggeryjs.feature downloading from nexus

[Kasun G]

I have scheduled a new jaggery build.


On Thu, Apr 10, 2014 at 12:05 AM, Ajith Vitharana  wrote:

> Hi All,
>
> The registry.indexing jar which is included in [1] is corrupted. Shall we
> trigger new build and deploy the feature again ?
>
> [1]
> http://maven.wso2.org/nexus/content/repositories/snapshots/org/jaggeryjs/org.jaggeryjs.feature/0.9.0.ALPHA5.wso2v1-SNAPSHOT/org.jaggeryjs.feature-0.9.0.ALPHA5.wso2v1-20140327.094039-4.zip
>
> -Ajith.
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 

*Kasun Gajasinghe*Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build failure in chunk-09 - identity module

[Dinusha Senanayaka]

Hi,

Getting following compilation error while building
org.wso2.carbon.identity.tools.saml.validator module. Revision 199976.
Stubs are up to date. Can IS team have a look ?


[INFO] Compiling 7 source files to
/home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/target/classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[149,27]
getClaimValue(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String)
in org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil cannot be applied to
(java.lang.String,java.lang.String)
[ERROR]
/home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[264,24]
getUserClaimValues(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String[],java.lang.String)
in org.wso2.carbon.identity.sso.saml.builders.claims.ClaimsRetriever cannot
be applied to (java.lang.String,java.lang.String[],)


Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Corrupted jaggeryjs.feature downloading from nexus

[Ajith Vitharana]

On Thu, Apr 10, 2014 at 1:26 AM, Kasun G  wrote:

> I have scheduled a new jaggery build.
>

Thanks KasunG, This is fixed now.

-Ajith.


>
>
> On Thu, Apr 10, 2014 at 12:05 AM, Ajith Vitharana  wrote:
>
>> Hi All,
>>
>> The registry.indexing jar which is included in [1] is corrupted. Shall we
>> trigger new build and deploy the feature again ?
>>
>> [1]
>> http://maven.wso2.org/nexus/content/repositories/snapshots/org/jaggeryjs/org.jaggeryjs.feature/0.9.0.ALPHA5.wso2v1-SNAPSHOT/org.jaggeryjs.feature-0.9.0.ALPHA5.wso2v1-20140327.094039-4.zip
>>
>> -Ajith.
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94772217350
>>
>>
>
>
> --
>
> *Kasun Gajasinghe*Software Engineer, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>



-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in chunk-09 - identity module

[Darshana Gunawardana]

Hi Dinusha,

We are looking into this..

Thanks,


On Thu, Apr 10, 2014 at 6:50 AM, Dinusha Senanayaka wrote:

> Hi,
>
> Getting following compilation error while building
> org.wso2.carbon.identity.tools.saml.validator module. Revision 199976.
> Stubs are up to date. Can IS team have a look ?
>
>
> [INFO] Compiling 7 source files to
> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[149,27]
> getClaimValue(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String)
> in org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil cannot be applied to
> (java.lang.String,java.lang.String)
> [ERROR]
> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[264,24]
> getUserClaimValues(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String[],java.lang.String)
> in org.wso2.carbon.identity.sso.saml.builders.claims.ClaimsRetriever cannot
> be applied to (java.lang.String,java.lang.String[],)
>
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Regards,


*Darshana Gunawardana *Software Engineer
WSO2 Inc.; http://wso2.com

* E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Location for DataMapperMediator source

[Sohani Weerasinghe]

Hi,

Since I have started implementing 'DataMapperMediator', I thought of
committing the source to [1]. Is this the proper location to commit? WDYT ?

[1]
https://github.com/wso2-dev/carbon-mediation/tree/master/components/mediators/

Thanks,
Sohani


Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Migration scripts for API-M 1.6.0 to 1.7.0

[Nirodha Pramod]

Hi,

Do we have the $subject ready?

regards,
Nirodha

-- 

*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] AM tables creating issues in API-M 1.7.0 (Oracle & mssql)

[Aparna Karunarathna]

Hi All,

We have observed $subject. Server started using -Dsetup and no start-up
errors were thrown, server started successfully. When check databases we
have seen tables are getting created partially in Oracle [1] database, then
I have executed the oracle script manually and some tables were created
with errors. In mssql [2] script should be updated. Please have a look.

[1] https://wso2.org/jira/browse/APIMANAGER-2163
[2] https://wso2.org/jira/browse/APIMANAGER-2159

Regards,
-- 
*Aparna Karunarathna.*


*Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in chunk-09 - identity module

[Thanuja Jayasinghe]

Hi Dinusha,

Fixed with r19.


Thanks


On Thu, Apr 10, 2014 at 10:06 AM, Darshana Gunawardana wrote:

> Hi Dinusha,
>
> We are looking into this..
>
> Thanks,
>
>
> On Thu, Apr 10, 2014 at 6:50 AM, Dinusha Senanayaka wrote:
>
>> Hi,
>>
>> Getting following compilation error while building
>> org.wso2.carbon.identity.tools.saml.validator module. Revision 199976.
>> Stubs are up to date. Can IS team have a look ?
>>
>>
>> [INFO] Compiling 7 source files to
>> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/target/classes
>> [INFO] -
>> [ERROR] COMPILATION ERROR :
>> [INFO] -
>> [ERROR]
>> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[149,27]
>> getClaimValue(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String)
>> in org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil cannot be applied to
>> (java.lang.String,java.lang.String)
>> [ERROR]
>> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[264,24]
>> getUserClaimValues(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String[],java.lang.String)
>> in org.wso2.carbon.identity.sso.saml.builders.claims.ClaimsRetriever cannot
>> be applied to (java.lang.String,java.lang.String[],)
>>
>>
>> Regards,
>> Dinusha.
>>
>> --
>> Dinusha Dilrukshi
>> Senior Software Engineer
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana *Software Engineer
> WSO2 Inc.; http://wso2.com
>
> * E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859> *Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanuja Lakmal*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Moving FE operations to BE

[Indika Sampath]

Hi All,

We can minimize the FE-BE communication by only moving the methods which
require Queue connection to be created. Then there won't be any key shared
and exposed to the FE. So basically browseQueue() method move to the BE and
once the queue details comes to FE getMsgProperties(), getMsgContentType(),
getMessageContentAsString() can be called with those data. I think then the
communication overhead will be reduce up to considerable extent. I will
consider the other client classes methods also with the same approach. If
there is any concern with this approach please post to this thread.

Cheers!


On Wed, Apr 9, 2014 at 3:32 PM, Suresh Attanayaka  wrote:

> Hi Ishara,
>
> I would not agree with your argument regarding the FE-BE communication
> overhead, afterall most of the time it is just a java call over the
> local-transport, no http cost at all. For me, consuming the JMS queue from
> the UI is no different from connecting to the database over JDBC from the
> UI which is not really our model.
>
> Plus, the key shared there is a system key and exposing it over HTTP is
> not a good idea. It should be shared using the OSGI service instead.
>
> On Wed, Apr 9, 2014 at 2:30 PM, Ishara Premadasa  wrote:
>
>> Hi Indika,
>>
>> Your observation is correct that getAccessKey() method is not exposed to
>> all the users, however few clarifications to made is this method is not
>> configured to admin role only. According to the current permission model in
>> carbon we can create new roles and assign permissions to that accordingly.
>> However if you look at the permission tree there is only two MB related
>> permission options named,
>>
>>
>> MB
>>
>>
>>
>>
>>-
>>
>>
>>   Add Queue
>>
>>
>>
>>
>>
>>
>>
>>   -  Queue Details
>>
>> Therefore for a user to perform other queue operations than this, we need
>> to provide admin--> configure permission as shown in image [1] which is the
>> reason getAccessKey() is bound to /permission/admin/configure level. (This
>> is more like for any user to work with MB it needs some admin priviledges
>> )Therefore IMO it would be better if we can add more options to above MB
>> level permissions like Browse Queue etc. so user can be authorized to 
>> getAccessKey()
>> by selecting that permission rather than moving the operations into BE.
>>
>>
>> On Wed, Apr 9, 2014 at 11:48 AM, Indika Sampath  wrote:
>>
>>> Hi All,
>>>
>>> There is an issue with browsing the queue for users which haven't admin
>>> role. The reason is following two methods restricted to the admin role in
>>> Axis2 level.
>>>
>>>- getCurrentUser()
>>>- getAccessKey()
>>>
>>> There is a way to get the current logged user from the session but there
>>> is no way to get the access key.
>>> org.wso2.carbon.andes.ui.client.QueueBrowserClient creating a queue
>>> connection and access the queue from the FE. We need user name and access
>>> key to creating queue connection. There might be some security issue with
>>> QueueBrowserClient as I and Hasitha had discussion with Suresh on
>>> yesterday. Some operations in org.wso2.carbon.andes.ui module needs to move
>>> to the BE. I have come up with the following implementation design.
>>>
>>> Move following methods in the QueueBrowserClient to
>>> org.wso2.carbon.andes.core.QueueManagerService and expose as web service
>>> via org.wso2.carbon.andes.admin.AndesAdminService.
>>>
>>>
>>>- browseQueue()
>>>- closeBrowser()
>>>- getMsgContentType()
>>>- getMessageContentAsString()
>>>
>>> When we change like this we need to call the BE four times for each
>> Browse operation and this would be same for publish sample msg, purge queue
>> etc. which we don't necessarily have to go for BE. Wouldn't it be an
>> overhead that we make several FE <--> BE calls for a single UI operation
>> each time?
>>
>> Thanks!
>> Ishara
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/people/isharap/permissions_non_admin_user.png
>>
>>
>>> But there are another two classes
>>> org.wso2.carbon.andes.ui.client.QueueReceiverClient and
>>> org.wso2.carbon.andes.ui.client.QueueSenderClient needs do the same thing
>>> as I think.
>>>
>>> Cheers!
>>>
>>> --
>>> Indika Sampath
>>> Software Engineer
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>> Phone: +94 716 424 744
>>> Blog: http://indikasampath.blogspot.com/
>>>
>>>
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> Twitter   :
>> https://twitter.com/ishadil  Mobile   :
>> +94 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> Suresh Attanayake
> Senior Software Engineer; WSO2 Inc. http://wso2.com/
> Blog : http://sureshatt.blogspot.com/
> Web : http://www.ssoarcade.com/
> Facebook : https://www.facebook.com/IdentityWorld
> Twitter : https://twitter.com/sureshatt
> LinkedIn : http://lk.linkedin.com/in/sureshatt
> Mobile : +94755012060
> Mobile : +016166171172
>



-- 
Indik

Re: [Dev] Build failure in chunk-09 - identity module

[Dinusha Senanayaka]

Thanks Thanuja. will check.

Regards,
Dinusha.


On Thu, Apr 10, 2014 at 11:51 AM, Thanuja Jayasinghe wrote:

> Hi Dinusha,
>
> Fixed with r19.
>
>
> Thanks
>
>
> On Thu, Apr 10, 2014 at 10:06 AM, Darshana Gunawardana 
> wrote:
>
>> Hi Dinusha,
>>
>> We are looking into this..
>>
>> Thanks,
>>
>>
>> On Thu, Apr 10, 2014 at 6:50 AM, Dinusha Senanayaka wrote:
>>
>>> Hi,
>>>
>>> Getting following compilation error while building
>>> org.wso2.carbon.identity.tools.saml.validator module. Revision 199976.
>>> Stubs are up to date. Can IS team have a look ?
>>>
>>>
>>> [INFO] Compiling 7 source files to
>>> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/target/classes
>>> [INFO] -
>>> [ERROR] COMPILATION ERROR :
>>> [INFO] -
>>> [ERROR]
>>> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[149,27]
>>> getClaimValue(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String)
>>> in org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil cannot be applied to
>>> (java.lang.String,java.lang.String)
>>> [ERROR]
>>> /home/dinusha/wso2_products/turing/components/identity/org.wso2.carbon.identity.tools.saml.validator/4.2.0/src/main/java/org/wso2/carbon/identity/tools/saml/validator/processors/SAMLResponseBuilder.java:[264,24]
>>> getUserClaimValues(org.wso2.carbon.identity.sso.saml.dto.SAMLSSOAuthnReqDTO,java.lang.String[],java.lang.String)
>>> in org.wso2.carbon.identity.sso.saml.builders.claims.ClaimsRetriever cannot
>>> be applied to (java.lang.String,java.lang.String[],)
>>>
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Senior Software Engineer
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana *Software Engineer
>> WSO2 Inc.; http://wso2.com
>>
>> * E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <%2B94718566859> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanuja Lakmal*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891
>



-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Chunk 09 - Build failure

[Shammi Jayasinghe]

Hi IS Team ,

i am getting following build failure in building chunk 09 . Could you
please have a look

[INFO] BUILD FAILURE

[INFO]


[INFO] Total time: 9.009s

[INFO] Finished at: Thu Apr 10 11:54:36 IST 2014

[INFO] Final Memory: 61M/148M

[INFO]


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.identity.user.store.remote:
Compilation failure: Compilation failure:

[ERROR]
/Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[83,40]
cannot find symbol

[ERROR] symbol  : constructor
Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)

[ERROR] location: class org.wso2.carbon.user.api.Property

[ERROR]
/Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[89,28]
cannot find symbol

[ERROR] symbol  : constructor
Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)

[ERROR] location: class org.wso2.carbon.user.api.Property

[ERROR]
/Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[91,30]
cannot find symbol

[ERROR] symbol  : constructor
Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)

[ERROR] location: class org.wso2.carbon.user.api.Property

[ERROR]
/Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[97,28]
cannot find symbol

[ERROR] symbol  : constructor
Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)

[ERROR] location: class org.wso2.carbon.user.api.Property

[ERROR]
/Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[99,43]
cannot find symbol

[ERROR] symbol  : constructor
Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)

[ERROR] location: class org.wso2.carbon.user.api.Property

[ERROR]
/Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[102,43]
cannot find symbol

[ERROR] symbol  : constructor
Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)

[ERROR] location: class org.wso2.carbon.user.api.Property

[ERROR]
/Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[105,43]
cannot find symbol

[ERROR] symbol  : constructor
Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)

[ERROR] location: class org.wso2.carbon.user.api.Property

[ERROR] -> [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.

[ERROR]

[ERROR] For more information about the errors and possible solutions,
please read the following articles:

[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

[ERROR]

[ERROR] After correcting the problems, you can resume the build with the
command

-- 
Best Regards,

*  Shammi Jayasinghe*
Associate Tech Lead
WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Registry Integrity Violation Exception in Put Operation

[Thayalan]

Hi Ajith,

Sorry, I couldn't respond to you immediately as I haven't noticed this mail
somehow. I've attached the conf files to JIRA now.

Thanks,
Thayalan


On Tue, Apr 8, 2014 at 11:17 PM, Anjana Fernando  wrote:

> Thayalan, please do the needful.
>
> Cheers,
> Anjana.
>
>
> On Tue, Apr 8, 2014 at 9:16 PM, Ajith Vitharana  wrote:
>
>> Please attach your configuration files (conf dir) to the JIRA.
>>
>> -Ajith
>>
>>
>>
>>
>> On Tue, Apr 8, 2014 at 7:45 PM, Anjana Fernando  wrote:
>>
>>> Hi,
>>>
>>> There is an issue reported for BAM here [1], where in a registry put
>>> operation, a MySQL integrity constraint violation exception is thrown, can
>>> someone from GREG team please look into it.
>>>
>>> [1] https://wso2.org/jira/browse/BAM-1542
>>>
>>> Cheers,
>>> Anjana.
>>> --
>>> *Anjana Fernando*
>>> Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94772217350
>>
>>
>
>
> --
> *Anjana Fernando*
> Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



-- 
Regards,
Thayalan Sivapaleswararajah
Associate Technical Lead - QA
Mob: +94(0)777872485
Tel : +94(0)(11)2145345
Fax : +94(0)(11)2145300
Email: thaya...@wso2.com


*Disclaimer*: *This communication may contain privileged or other
confidential information and is intended exclusively for the addressee/s.
If you are not the intended recipient/s, or believe that you may have
received this communication in error, please reply to the sender indicating
that fact and delete the copy you received and in addition, you should not
print, copy, retransmit, disseminate, or otherwise use the information
contained in this communication. Internet communications cannot be
guaranteed to be timely, secure, error or virus-free. The sender does not
accept liability for any errors or omissions.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 09 - Build failure

[Shammi Jayasinghe]

Hi All,

Got this cleared off by updating and building kernel patch 0006.

Thanks
Shammi


On Thu, Apr 10, 2014 at 11:57 AM, Shammi Jayasinghe  wrote:

> Hi IS Team ,
>
> i am getting following build failure in building chunk 09 . Could you
> please have a look
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time: 9.009s
>
> [INFO] Finished at: Thu Apr 10 11:54:36 IST 2014
>
> [INFO] Final Memory: 61M/148M
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.identity.user.store.remote:
> Compilation failure: Compilation failure:
>
> [ERROR]
> /Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[83,40]
> cannot find symbol
>
> [ERROR] symbol  : constructor
> Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)
>
> [ERROR] location: class org.wso2.carbon.user.api.Property
>
> [ERROR]
> /Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[89,28]
> cannot find symbol
>
> [ERROR] symbol  : constructor
> Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)
>
> [ERROR] location: class org.wso2.carbon.user.api.Property
>
> [ERROR]
> /Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[91,30]
> cannot find symbol
>
> [ERROR] symbol  : constructor
> Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)
>
> [ERROR] location: class org.wso2.carbon.user.api.Property
>
> [ERROR]
> /Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[97,28]
> cannot find symbol
>
> [ERROR] symbol  : constructor
> Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)
>
> [ERROR] location: class org.wso2.carbon.user.api.Property
>
> [ERROR]
> /Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[99,43]
> cannot find symbol
>
> [ERROR] symbol  : constructor
> Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)
>
> [ERROR] location: class org.wso2.carbon.user.api.Property
>
> [ERROR]
> /Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[102,43]
> cannot find symbol
>
> [ERROR] symbol  : constructor
> Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)
>
> [ERROR] location: class org.wso2.carbon.user.api.Property
>
> [ERROR]
> /Users/shammi/wso2/Development/public/platform/branches/turing/components/identity/org.wso2.carbon.identity.user.store.remote/4.2.0/src/main/java/org/wso2/carbon/identity/user/store/remote/CarbonRemoteUserStoreManger.java:[105,43]
> cannot find symbol
>
> [ERROR] symbol  : constructor
> Property(java.lang.String,java.lang.String,java.lang.String,java.lang.String,)
>
> [ERROR] location: class org.wso2.carbon.user.api.Property
>
> [ERROR] -> [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.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the
> command
>
> --
> Best Regards,
>
> *  Shammi Jayasinghe*
> Associate Tech Lead
> WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>


-- 
Best Regards,

*  Shammi Jayasinghe*
Associate Tech Lead
WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] StackOverflow Error in deployment after Tenant Unloading / Loading

[Anjana Fernando]

Hi,

There is an issue reported for BAM here [1], in a scenario when tenant is
unloaded and loaded again, and when a Jaggery web app deployment happens, a
call to
"org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder()"
seems to be called recursively indefinitely, which causes a
StacKOverflowError. Can someone from the Carbon Core team please look into
it.

[1] https://wso2.org/jira/browse/BAM-1513

Cheers,
Anjana.
-- 
*Anjana Fernando*
Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev