Re: [Dev] Some API Changes to the API Manager

[Sumedha Rubasinghe]

On Mon, May 7, 2012 at 11:21 PM, Hiranya Jayathilaka wrote:

> Sumedha and the API Manager team,
>
> In order to improve the internal design  I'd like to propose following API
> changes to the API manager implementation:
>
> 1. Add following 2 new methods to the APIManager interface (Some variants
> of these method are already available in the APIManagerImpl class, but they
> are not part of the API. I think we should make the following generalized
> methods part of the core API and use them from the host objects as required)
> InputStream getIcon(APIIdentifier id)
> void addIcon(APIIdentifier id, InputStream in, String
> contentType)
>
> 2. Move the getSubscriberAPIs method from APIConsumer to APIManager (This
> method is already used by the API provider host object. Clearly it's
> required by API consumers as well as API providers)
>
> 3. Introduce a new username argument (String) to the addComment and
> rateAPI methods. We need to perform these operations using the governance
> user registry of the corresponding users. Otherwise the system will not
> properly keep track of the comment authors. To make the core API more
> generic I think we should introduce the username argument to the above
> methods.
>
> If you don't see any issues with these changes, I'll get started with
> refactoring. In order to handle authorization what I thought was to
> implement a new wrapper for the existing impl classes. The wrapper will
> imply extend the classes providing the necessary authorization logic
> (permission checking) where necessary. I've spawned a new thread regarding
> this on the mailing list. If we don't get any better ideas we can implement
> that.
>

+1 for all.

>
> Thanks
> --
> Hiranya Jayathilaka
> Senior Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



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

Re: [Dev] [Level 1 issue] Cannot find features in a p2-repo added from bamboo

[Dileepa Jayakody]

Hi Chamara,

I'm looking into this.

Thanks,
Dileepa

On Tue, May 8, 2012 at 12:02 PM, Chamara Ariyarathne wrote:

> I tried adding the p2 repository from
>
> http://wso2.org/bamboo/artifact/WSO2CARBON-P2REPO/JOB1/build-78/P2-Repo/p2-repo
> to
> WSO2 Data Services Server v3.0.0-SNAPSHOT
> and it was added at the second attempt.
>
> But when I try Find Features it gives "Error occured while quering
> installable features" in the UI and in the backend
>
> [2012-05-08 20:04:36,684] ERROR
> {org.wso2.carbon.feature.mgt.services.prov.RepositoryAdminService} -  Error
> occured while quering installable features
> java.lang.NullPointerException
>  at
> org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.getCategoryTypeInstallableUnits(ProvisioningUtils.java:215)
> at
> org.wso2.carbon.feature.mgt.services.prov.RepositoryAdminService.getInstallableFeatures(RepositoryAdminService.java:190)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
>  at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>  at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>  at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>  at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>  at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
>  at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>  at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
>  at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:109)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
>  at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>  at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
>  at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
>  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)
> [2012-05-08 20:04:36,688] ERROR
> {org.wso2.carbon.feature.mgt.ui.RepositoryAdminServiceClient} -  Error
> occured while quering installable features
> org.apache.axis2.AxisFault: Error occured while quering installable
> features
> at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
>  at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
>  at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>  at
> org.wso2.carbon.feature.mgt.stub.RepositoryAdminServiceStub.getInstallableFeatures(RepositoryAdminServiceStub

[Dev] [Level 1 issue] Cannot find features in a p2-repo added from bamboo

[Chamara Ariyarathne]

I tried adding the p2 repository from
http://wso2.org/bamboo/artifact/WSO2CARBON-P2REPO/JOB1/build-78/P2-Repo/p2-repo
to
WSO2 Data Services Server v3.0.0-SNAPSHOT
and it was added at the second attempt.

But when I try Find Features it gives "Error occured while quering
installable features" in the UI and in the backend

[2012-05-08 20:04:36,684] ERROR
{org.wso2.carbon.feature.mgt.services.prov.RepositoryAdminService} -  Error
occured while quering installable features
java.lang.NullPointerException
 at
org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.getCategoryTypeInstallableUnits(ProvisioningUtils.java:215)
at
org.wso2.carbon.feature.mgt.services.prov.RepositoryAdminService.getInstallableFeatures(RepositoryAdminService.java:190)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
 at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
 at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
 at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:109)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
 at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
 at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
 at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
 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)
[2012-05-08 20:04:36,688] ERROR
{org.wso2.carbon.feature.mgt.ui.RepositoryAdminServiceClient} -  Error
occured while quering installable features
org.apache.axis2.AxisFault: Error occured while quering installable features
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
 at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
 at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
org.wso2.carbon.feature.mgt.stub.RepositoryAdminServiceStub.getInstallableFeatures(RepositoryAdminServiceStub.java:1488)
at
org.wso2.carbon.feature.mgt.ui.RepositoryAdminServiceClient.getInstallableFeatures(RepositoryAdminServiceClient.java:207)
 at
org.apache.jsp.feature_002dmgt.available_005ffeatures_002dajaxprocessor_jsp._jspService(available_005ffeatures_002dajaxprocessor_jsp.java:120)
 at org.apache.jasper.runtime.Htt

Re: [Dev] Do we still use wso2cloud-server.sh script in Stratos Serices?

[Sameera Jayasoma]

On Mon, May 7, 2012 at 8:01 PM, Sanjaya Ratnaweera  wrote:

>
>
> On Mon, May 7, 2012 at 6:36 PM, Afkham Azeez  wrote:
>
>> wso2cloud-server.sh has production optimization stuff & also enables the
>> Java Security Manager. So we need the settings in that for production use.
>> I'm not sure whether it is used in Stratos Live. Sanjaya?
>>
>>
> Nope, we are using wso2server.sh written to start with nohup, adding
> Security Manager parameters.
>

Shall we get rid of this? Each and every Stratos Server contains a copy of
the wso2server.sh as wso2cloud-server.sh. Looks like, we never
have maintained this file.

Sameera.

>
> Thanks
>
> ~sanjaya
>
>
>>  On Mon, May 7, 2012 at 5:43 PM, Sameera Jayasoma wrote:
>>
>>>  Most of the wso2cloud-server.sh files in the stratos services contain
>>> invalid stuff. We need to update them if we are using, or else we can
>>> remove them.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Mon, May 7, 2012 at 2:34 PM, Sameera Jayasoma wrote:
>>>
 Subject please.

 Thanks,
 Sameera.

 --
 Sameera Jayasoma
 Technical Lead

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://tech.jayasoma.org

 Lean . Enterprise . Middleware

>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma
>>> Technical Lead
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://tech.jayasoma.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Sanjaya Ratnaweera
> Senior Software Engineer; WSO2 Inc; http://www.wso2.com/.
>
> blog: http://www.samudura.org
> homepage: http://www.samudura.net
> twitter: http://twitter.com/sanjayar
>
>
> Lean . Enterprise . Middleware
>



-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Dev] Inserting Categories in p2 Repo

[Sameera Jayasoma]

On Tue, May 8, 2012 at 11:07 AM, Prabath Abeysekera wrote:

> Hi Sameera,
>
> On Tue, May 8, 2012 at 10:55 AM, Sameera Jayasoma wrote:
>
>> Hi Dileepa,
>>
>> The idea here is to install a particular category onto a Carbon server
>> right?. e.g. Installing AS category onto Carbon would result in an WSO2
>> Application Server.
>>
>> If thats the case, we need to add more features to these categories.
>>
>
>>
> All products contains logging feature, system statistics, etc.
>>
>
> Would it make sense to introduce a common feature category containing all
> such features (such as logging, etc) that are there in every product? I
> believe that would make the profiles less redundant too.
>

This is a good suggestion. But the problem is, we don't support
sub-categories yet. So for the moment, we have go with former approach.

Thanks,
Sameera.

>
>
>
>> You can find the complete list of features which makes a products by
>> looking at the pom.xml of the p2-profile-gen module of a product.
>>
>> Thanks,
>> Sameera.
>>
>> On Mon, May 7, 2012 at 6:19 PM, Dileepa Jayakody wrote:
>>
>>> Hi All,
>>>
>>> When improving the kernel feature manager to accommodate
>>> feature-groups(categories), we grouped some features in
>>> platform/trunk/features/repository into sample categories for demo purposes.
>>> Primarily the grouping was done based on product level categorisation,
>>> so that the users can easily identify and install products on carbon server.
>>>
>>> I think this sample list can be improved as the actual list of feature
>>> categories in Carbon platform. So please add missing features to relevant
>>> categories or introduce new categories as appropriate. Please note that a
>>> feature may belong to 1 or many categories.
>>>
>>> *AS*
>>>
>>>- org.wso2.carbon.jarservices
>>>- org.wso2.carbon.jaxwsservices
>>>- org.wso2.carbon.repomanager.axis2
>>>- org.wso2.carbon.security.mgt
>>>- org.wso2.carbon.service.mgt
>>>- org.wso2.carbon.servicehosting
>>>- org.wso2.carbon.springservices
>>>- org.wso2.carbon.webapp.mgt
>>>
>>> *BAM *
>>>
>>>- org.wso2.carbon.bam.data.publisher.activity.mediation
>>>- org.wso2.carbon.bam.data.publisher.activity.service
>>>- org.wso2.carbon.bam.data.publisher.mediationstats
>>>- org.wso2.carbon.bam.data.publisher.servicestats
>>>- org.wso2.carbon.bam
>>>
>>> *Data*
>>>
>>>- org.wso2.carbon.dataservices
>>>- org.wso2.carbon.datasource
>>>
>>> *ESB*
>>>
>>>- org.wso2.carbon.deployment.synchronizer
>>>- org.wso2.carbon.endpoint
>>>- org.wso2.carbon.esb.mediation
>>>- org.wso2.carbon.localentry
>>>- org.wso2.carbon.mediation.artifactuploader
>>>- org.wso2.carbon.mediation.configadmin
>>>- org.wso2.carbon.mediation.initializer
>>>- org.wso2.carbon.mediation.statistics
>>>- org.wso2.carbon.mediation.templates
>>>- org.wso2.carbon.mediation.tracer
>>>- org.wso2.carbon.message.flows
>>>- org.wso2.carbon.message.processor
>>>- org.wso2.carbon.message.store
>>>- org.wso2.carbon.messagebox
>>>- org.wso2.carbon.priority
>>>- org.wso2.carbon.proxyadmin
>>>- org.wso2.carbon.rest.api
>>>- org.wso2.carbon.sequences
>>>- org.wso2.carbon.smooks
>>>- org.wso2.carbon.statistics.transport
>>>- org.wso2.carbon.transport.mgt
>>>
>>>  * IS*
>>>
>>>- org.wso2.carbon.directory.service.mgr
>>>- org.wso2.carbon.identity.authenticator.saml2.sso
>>>- org.wso2.carbon.identity.authenticator.token
>>>- org.wso2.carbon.identity.core
>>>- org.wso2.carbon.identity.oauth
>>>- org.wso2.carbon.identity.provider.openid.admin
>>>- org.wso2.carbon.identity.provider
>>>- org.wso2.carbon.identity.relying.party
>>>- org.wso2.carbon.identity.self.registration
>>>- org.wso2.carbon.identity.sso.saml
>>>- org.wso2.carbon.identity.user.profile
>>>- org.wso2.carbon.identity.xacml
>>>- org.wso2.carbon.ldap.server
>>>
>>> *Registry*
>>>
>>>- org.wso2.carbon.governance.gadgets
>>>- org.wso2.carbon.governance.lifecycle.management
>>>- org.wso2.carbon.governance.metadata
>>>- org.wso2.carbon.governance.notifications.configuration
>>>- org.wso2.carbon.registry.activities
>>>- org.wso2.carbon.registry.associations.dependencies
>>>- org.wso2.carbon.registry.community.features
>>>- org.wso2.carbon.registry.contentsearch
>>>- org.wso2.carbon.registry.core
>>>- org.wso2.carbon.registry.extensions
>>>- org.wso2.carbon.registry.handler.configuration
>>>- org.wso2.carbon.registry.profiles
>>>- org.wso2.carbon.registry.resource.properties
>>>- org.wso2.carbon.registry.social
>>>- org.wso2.carbon.registry.ui.menu.governance
>>>- org.wso2.carbon.registry.ui.menu
>>>- org.wso2.carbon.registry.ws
>>>
>>> *Tools*
>>>
>>>- org.wso2.carbon.tryit
>>>- org.wso2.carbon.wsdl.tools
>>>
>>> Thanks,
>>>
>>> Dileepa
>>> On Wed, May 2, 2012 at 4:26 PM, Chethiya Abeysinghe 
>>> wrote:
>>>
 Hi,

Re: [Dev] Missing requirement when installing logging-mgt feature

[Isuru Wimalasundera]

The issues seems to be fixed now. Sorry for the false alarm :)

On Tue, May 8, 2012 at 10:57 AM, Isuru Wimalasundera wrote:

> Hi
>
> Getting the same error while building GREG p2 profile generation.
> What is the status of this.
>
> On Sun, May 6, 2012 at 11:43 PM, Denis Weerasiri  wrote:
>
>> Hi,
>> Getting this error at BPS p2 profile generation in trunk.
>>
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Logging Management Feature
>> 4.0.0.SNAPSHOT (org.wso2.carbon.logging.mgt.feature.group 4.0.0.SNAPSHOT)
>>  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
>> 1.1.0.wso2v1) requires 'package org.antlr.runtime 3.2.0.wso2v1' but it
>> could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Feature 4.0.0.SNAPSHOT
>> (org.wso2.carbon.logging.mgt.feature.group 4.0.0.SNAPSHOT)
>>   To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.0.SNAPSHOT]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Core Feature 4.0.0.SNAPSHOT
>> (org.wso2.carbon.logging.mgt.server.feature.group 4.0.0.SNAPSHOT)
>>   To: apache-cassandra [1.1.0.wso2v1]
>>
>>
>>
>> --
>> Thanks,
>> Denis
>> --
>> *Denis Weerasiri*
>> Senior Software Engineer
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com,
>> *email: denis ** [AT] wso2.com 
>> *
>> *phone: +94117639629
>> *
>> *site: 
>> **https://sites.google.com/site/ddweerasiri/*
>> *blog: **http://ddweerasiri.blogspot.com*
>> *
>> twitter: **http://twitter.com/ddweerasiri*
>> *
>> linked-in: 
>> **http://lk.linkedin.com/in/ddweerasiri*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Isuru Wimalasundera*
> Software Engineer;  WSO2, Inc.; http://wso2.com,
>  mobile: +94 77 920 5641
>
>


-- 
*Isuru Wimalasundera*
Software Engineer;  WSO2, Inc.; http://wso2.com,
 mobile: +94 77 920 5641
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Usage of build.properties file in p2 features

[Pradeep Fernando]

Hi,

purpose was to identify the conf directory while feature install. Not
sure whether this is required anymore (AFAIR it doesnt get used during
C4 feature installation)

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

Re: [Dev] Missing requirement when installing logging-mgt feature

[Denis Weerasiri]

This was fixed. Please svn up the logging.mgt feature.

On Tue, May 8, 2012 at 10:57 AM, Isuru Wimalasundera wrote:

> Hi
>
> Getting the same error while building GREG p2 profile generation.
> What is the status of this.
>
> On Sun, May 6, 2012 at 11:43 PM, Denis Weerasiri  wrote:
>
>> Hi,
>> Getting this error at BPS p2 profile generation in trunk.
>>
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Logging Management Feature
>> 4.0.0.SNAPSHOT (org.wso2.carbon.logging.mgt.feature.group 4.0.0.SNAPSHOT)
>>  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
>> 1.1.0.wso2v1) requires 'package org.antlr.runtime 3.2.0.wso2v1' but it
>> could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Feature 4.0.0.SNAPSHOT
>> (org.wso2.carbon.logging.mgt.feature.group 4.0.0.SNAPSHOT)
>>   To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.0.SNAPSHOT]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Core Feature 4.0.0.SNAPSHOT
>> (org.wso2.carbon.logging.mgt.server.feature.group 4.0.0.SNAPSHOT)
>>   To: apache-cassandra [1.1.0.wso2v1]
>>
>>
>>
>> --
>> Thanks,
>> Denis
>> --
>> *Denis Weerasiri*
>> Senior Software Engineer
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com,
>> *email: denis ** [AT] wso2.com 
>> *
>> *phone: +94117639629
>> *
>> *site: 
>> **https://sites.google.com/site/ddweerasiri/*
>> *blog: **http://ddweerasiri.blogspot.com*
>> *
>> twitter: **http://twitter.com/ddweerasiri*
>> *
>> linked-in: 
>> **http://lk.linkedin.com/in/ddweerasiri*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Isuru Wimalasundera*
> Software Engineer;  WSO2, Inc.; http://wso2.com,
>  mobile: +94 77 920 5641
>
>


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Senior Software Engineer
Integration Technologies Team, WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Inserting Categories in p2 Repo

[Prabath Abeysekera]

Hi Sameera,

On Tue, May 8, 2012 at 10:55 AM, Sameera Jayasoma  wrote:

> Hi Dileepa,
>
> The idea here is to install a particular category onto a Carbon server
> right?. e.g. Installing AS category onto Carbon would result in an WSO2
> Application Server.
>
> If thats the case, we need to add more features to these categories.
>

>
All products contains logging feature, system statistics, etc.
>

Would it make sense to introduce a common feature category containing all
such features (such as logging, etc) that are there in every product? I
believe that would make the profiles less redundant too.



> You can find the complete list of features which makes a products by
> looking at the pom.xml of the p2-profile-gen module of a product.
>
> Thanks,
> Sameera.
>
> On Mon, May 7, 2012 at 6:19 PM, Dileepa Jayakody  wrote:
>
>> Hi All,
>>
>> When improving the kernel feature manager to accommodate
>> feature-groups(categories), we grouped some features in
>> platform/trunk/features/repository into sample categories for demo purposes.
>> Primarily the grouping was done based on product level categorisation, so
>> that the users can easily identify and install products on carbon server.
>>
>> I think this sample list can be improved as the actual list of feature
>> categories in Carbon platform. So please add missing features to relevant
>> categories or introduce new categories as appropriate. Please note that a
>> feature may belong to 1 or many categories.
>>
>> *AS*
>>
>>- org.wso2.carbon.jarservices
>>- org.wso2.carbon.jaxwsservices
>>- org.wso2.carbon.repomanager.axis2
>>- org.wso2.carbon.security.mgt
>>- org.wso2.carbon.service.mgt
>>- org.wso2.carbon.servicehosting
>>- org.wso2.carbon.springservices
>>- org.wso2.carbon.webapp.mgt
>>
>> *BAM *
>>
>>- org.wso2.carbon.bam.data.publisher.activity.mediation
>>- org.wso2.carbon.bam.data.publisher.activity.service
>>- org.wso2.carbon.bam.data.publisher.mediationstats
>>- org.wso2.carbon.bam.data.publisher.servicestats
>>- org.wso2.carbon.bam
>>
>> *Data*
>>
>>- org.wso2.carbon.dataservices
>>- org.wso2.carbon.datasource
>>
>> *ESB*
>>
>>- org.wso2.carbon.deployment.synchronizer
>>- org.wso2.carbon.endpoint
>>- org.wso2.carbon.esb.mediation
>>- org.wso2.carbon.localentry
>>- org.wso2.carbon.mediation.artifactuploader
>>- org.wso2.carbon.mediation.configadmin
>>- org.wso2.carbon.mediation.initializer
>>- org.wso2.carbon.mediation.statistics
>>- org.wso2.carbon.mediation.templates
>>- org.wso2.carbon.mediation.tracer
>>- org.wso2.carbon.message.flows
>>- org.wso2.carbon.message.processor
>>- org.wso2.carbon.message.store
>>- org.wso2.carbon.messagebox
>>- org.wso2.carbon.priority
>>- org.wso2.carbon.proxyadmin
>>- org.wso2.carbon.rest.api
>>- org.wso2.carbon.sequences
>>- org.wso2.carbon.smooks
>>- org.wso2.carbon.statistics.transport
>>- org.wso2.carbon.transport.mgt
>>
>>  * IS*
>>
>>- org.wso2.carbon.directory.service.mgr
>>- org.wso2.carbon.identity.authenticator.saml2.sso
>>- org.wso2.carbon.identity.authenticator.token
>>- org.wso2.carbon.identity.core
>>- org.wso2.carbon.identity.oauth
>>- org.wso2.carbon.identity.provider.openid.admin
>>- org.wso2.carbon.identity.provider
>>- org.wso2.carbon.identity.relying.party
>>- org.wso2.carbon.identity.self.registration
>>- org.wso2.carbon.identity.sso.saml
>>- org.wso2.carbon.identity.user.profile
>>- org.wso2.carbon.identity.xacml
>>- org.wso2.carbon.ldap.server
>>
>> *Registry*
>>
>>- org.wso2.carbon.governance.gadgets
>>- org.wso2.carbon.governance.lifecycle.management
>>- org.wso2.carbon.governance.metadata
>>- org.wso2.carbon.governance.notifications.configuration
>>- org.wso2.carbon.registry.activities
>>- org.wso2.carbon.registry.associations.dependencies
>>- org.wso2.carbon.registry.community.features
>>- org.wso2.carbon.registry.contentsearch
>>- org.wso2.carbon.registry.core
>>- org.wso2.carbon.registry.extensions
>>- org.wso2.carbon.registry.handler.configuration
>>- org.wso2.carbon.registry.profiles
>>- org.wso2.carbon.registry.resource.properties
>>- org.wso2.carbon.registry.social
>>- org.wso2.carbon.registry.ui.menu.governance
>>- org.wso2.carbon.registry.ui.menu
>>- org.wso2.carbon.registry.ws
>>
>> *Tools*
>>
>>- org.wso2.carbon.tryit
>>- org.wso2.carbon.wsdl.tools
>>
>> Thanks,
>>
>> Dileepa
>> On Wed, May 2, 2012 at 4:26 PM, Chethiya Abeysinghe wrote:
>>
>>> Hi,
>>>
>>> We have changed the p2-repo-gen to generate the repository with category
>>> information. So you can simply define categories and include appropriate
>>> features into those categories. Once that repo with category information is
>>> imported to the feature manger, you can see those defined categories in the
>>> UI.
>>>
>>> To feed in these information, you have to

Re: [Dev] Missing requirement when installing logging-mgt feature

[Isuru Wimalasundera]

Hi

Getting the same error while building GREG p2 profile generation.
What is the status of this.

On Sun, May 6, 2012 at 11:43 PM, Denis Weerasiri  wrote:

> Hi,
> Getting this error at BPS p2 profile generation in trunk.
>
> Installation failed.
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: WSO2 Carbon - Logging Management Feature
> 4.0.0.SNAPSHOT (org.wso2.carbon.logging.mgt.feature.group 4.0.0.SNAPSHOT)
>  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
> 1.1.0.wso2v1) requires 'package org.antlr.runtime 3.2.0.wso2v1' but it
> could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Logging Management Feature 4.0.0.SNAPSHOT
> (org.wso2.carbon.logging.mgt.feature.group 4.0.0.SNAPSHOT)
>   To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.0.SNAPSHOT]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Logging Management Core Feature 4.0.0.SNAPSHOT
> (org.wso2.carbon.logging.mgt.server.feature.group 4.0.0.SNAPSHOT)
>   To: apache-cassandra [1.1.0.wso2v1]
>
>
>
> --
> Thanks,
> Denis
> --
> *Denis Weerasiri*
> Senior Software Engineer
> Integration Technologies Team, WSO2 Inc.; http://wso2.com,
> *email: denis ** [AT] wso2.com *
> *phone: +94117639629
> *
> *site: 
> **https://sites.google.com/site/ddweerasiri/*
> *blog: **http://ddweerasiri.blogspot.com*
> *
> twitter: **http://twitter.com/ddweerasiri*
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Wimalasundera*
Software Engineer;  WSO2, Inc.; http://wso2.com,
 mobile: +94 77 920 5641
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Inserting Categories in p2 Repo

[Sameera Jayasoma]

Hi Dileepa,

The idea here is to install a particular category onto a Carbon server
right?. e.g. Installing AS category onto Carbon would result in an WSO2
Application Server.

If thats the case, we need to add more features to these categories. All
products contains logging feature, system statistics, etc. You can find the
complete list of features which makes a products by looking at the pom.xml
of the p2-profile-gen module of a product.

Thanks,
Sameera.

On Mon, May 7, 2012 at 6:19 PM, Dileepa Jayakody  wrote:

> Hi All,
>
> When improving the kernel feature manager to accommodate
> feature-groups(categories), we grouped some features in
> platform/trunk/features/repository into sample categories for demo purposes.
> Primarily the grouping was done based on product level categorisation, so
> that the users can easily identify and install products on carbon server.
>
> I think this sample list can be improved as the actual list of feature
> categories in Carbon platform. So please add missing features to relevant
> categories or introduce new categories as appropriate. Please note that a
> feature may belong to 1 or many categories.
>
> *AS*
>
>- org.wso2.carbon.jarservices
>- org.wso2.carbon.jaxwsservices
>- org.wso2.carbon.repomanager.axis2
>- org.wso2.carbon.security.mgt
>- org.wso2.carbon.service.mgt
>- org.wso2.carbon.servicehosting
>- org.wso2.carbon.springservices
>- org.wso2.carbon.webapp.mgt
>
> *BAM *
>
>- org.wso2.carbon.bam.data.publisher.activity.mediation
>- org.wso2.carbon.bam.data.publisher.activity.service
>- org.wso2.carbon.bam.data.publisher.mediationstats
>- org.wso2.carbon.bam.data.publisher.servicestats
>- org.wso2.carbon.bam
>
> *Data*
>
>- org.wso2.carbon.dataservices
>- org.wso2.carbon.datasource
>
> *ESB*
>
>- org.wso2.carbon.deployment.synchronizer
>- org.wso2.carbon.endpoint
>- org.wso2.carbon.esb.mediation
>- org.wso2.carbon.localentry
>- org.wso2.carbon.mediation.artifactuploader
>- org.wso2.carbon.mediation.configadmin
>- org.wso2.carbon.mediation.initializer
>- org.wso2.carbon.mediation.statistics
>- org.wso2.carbon.mediation.templates
>- org.wso2.carbon.mediation.tracer
>- org.wso2.carbon.message.flows
>- org.wso2.carbon.message.processor
>- org.wso2.carbon.message.store
>- org.wso2.carbon.messagebox
>- org.wso2.carbon.priority
>- org.wso2.carbon.proxyadmin
>- org.wso2.carbon.rest.api
>- org.wso2.carbon.sequences
>- org.wso2.carbon.smooks
>- org.wso2.carbon.statistics.transport
>- org.wso2.carbon.transport.mgt
>
>  * IS*
>
>- org.wso2.carbon.directory.service.mgr
>- org.wso2.carbon.identity.authenticator.saml2.sso
>- org.wso2.carbon.identity.authenticator.token
>- org.wso2.carbon.identity.core
>- org.wso2.carbon.identity.oauth
>- org.wso2.carbon.identity.provider.openid.admin
>- org.wso2.carbon.identity.provider
>- org.wso2.carbon.identity.relying.party
>- org.wso2.carbon.identity.self.registration
>- org.wso2.carbon.identity.sso.saml
>- org.wso2.carbon.identity.user.profile
>- org.wso2.carbon.identity.xacml
>- org.wso2.carbon.ldap.server
>
> *Registry*
>
>- org.wso2.carbon.governance.gadgets
>- org.wso2.carbon.governance.lifecycle.management
>- org.wso2.carbon.governance.metadata
>- org.wso2.carbon.governance.notifications.configuration
>- org.wso2.carbon.registry.activities
>- org.wso2.carbon.registry.associations.dependencies
>- org.wso2.carbon.registry.community.features
>- org.wso2.carbon.registry.contentsearch
>- org.wso2.carbon.registry.core
>- org.wso2.carbon.registry.extensions
>- org.wso2.carbon.registry.handler.configuration
>- org.wso2.carbon.registry.profiles
>- org.wso2.carbon.registry.resource.properties
>- org.wso2.carbon.registry.social
>- org.wso2.carbon.registry.ui.menu.governance
>- org.wso2.carbon.registry.ui.menu
>- org.wso2.carbon.registry.ws
>
> *Tools*
>
>- org.wso2.carbon.tryit
>- org.wso2.carbon.wsdl.tools
>
> Thanks,
>
> Dileepa
> On Wed, May 2, 2012 at 4:26 PM, Chethiya Abeysinghe wrote:
>
>> Hi,
>>
>> We have changed the p2-repo-gen to generate the repository with category
>> information. So you can simply define categories and include appropriate
>> features into those categories. Once that repo with category information is
>> imported to the feature manger, you can see those defined categories in the
>> UI.
>>
>> To feed in these information, you have to edit the
>> carbon/platform/trunk/features/repository/pom.xml file in svn by adding
>>  element. An example of such a category is shown below. You can
>> include multiple  elements.
>>
>> 
>>  
>> org.wso2.carbon.broker.category
>>  WSO2 Broker Category
>> broker category
>>
>> 
>>   
>>org.wso2.carbon.broker
>> ${carbon.version}
>>   
>>
>>   
>> org.wso2.carbon.brokermanager
>>${carbon.version}
>>   
>>  

Re: [Dev] Removing Java Service Wrapper from Carbon

[Sameera Jayasoma]

On Tue, May 8, 2012 at 9:46 AM, Chintana Wilamuna  wrote:

> Hi,
>
> Have a blog - http://engwar.com/post/678. Probably better to have a KB
> item as well.
>

+1 for a KB item. We can link it from the Carbon documentation as well.

Thanks,
Sameera.

>
> -Chintana
>
>
> On Monday, May 7, 2012, Sameera Jayasoma wrote:
>
>> Hi Chinthana,
>>
>> On Mon, Feb 27, 2012 at 12:12 PM, Chintana Wilamuna wrote:
>>
>>>
>>>
>>> On Mon, Feb 27, 2012 at 11:49 AM, Sameera Jayasoma wrote:
>>>
>>> Yeah 20MB is bit of a concern.   Btw, we had an offline discussion with
 Azeez and decided to remove Java Service Wrapper.

 Shall we go ahead with nohup thing?

>>>
>>> Nohup works ok in Linux. Problem is running it as a service in Windows.
>>>
>>> For Windows, may be we can point to an OT article about how to download
>>> YAJSW and install/configure it as a service?
>>>
>>
>> We have removed JSW from Carbon. In Linux, we use nohup now. For Window,
>> we need something like YAJSW. Do we have an article or blog on how to
>> integrate YAJSW with Carbon?  If not we might have to write one.
>>
>> Thanks,
>> Sameera.
>>
>>
>>>
>>> -Chintana
>>>
>>> --
>>> Chintana Wilamuna
>>> Associate Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> phone: +94 75 211 1106
>>> blog: http://engwar.com/
>>> photos: http://flickr.com/photos/chintana
>>> linkedin: http://www.linkedin.com/in/engwar
>>> twitter: twitter.com/std_err
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> carbon-...@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>
>
> --
> Chintana Wilamuna
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> phone: +94 75 211 1106
> blog: http://engwar.com/
> photos: http://flickr.com/photos/chintana
> linkedin: http://www.linkedin.com/in/engwar
> twitter: twitter.com/std_err
>
>


-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Dev] Deployment issue in jaggery apps

[Nuwan Bandara]

Why do you have a web.xml in a jaggery app ? can you send the application
ur trying to deploy.

On Mon, May 7, 2012 at 5:36 PM, Ashansa Perera  wrote:

> Hi,
> I'm trying to add a new jaggery app using the management console, but only
> the part of it is copied to repository/deployment/server/jaggeryapps, hence
> the app is not working. Is this a known issue or am I missing anything? I
> get the following error log [1] in server, but the deployed zip file has
> /WEB-INF/web.xml file.
>
> [1]
> [2012-05-07 08:03:20,670] ERROR
> {org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin} -  Could not unzip the
> Jaggery App Archive {org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin}
> java.io.FileNotFoundException:
> /opt/idtme/servers/wso2appfactory-3.0.0-SNAPSHOT/repository/deployment/server/jaggeryapps/project-mgt-tool/WEB-INF/web.xml
> (No such file or directory)
> at java.io.FileOutputStream.open(Native Method)
>  at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:70)
>  at
> org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin.unZip(JaggeryAppAdmin.java:740)
> at
> org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin.uploadWebapp(JaggeryAppAdmin.java:614)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>  at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>  at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>  at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>  at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>  at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
>  at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>  at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
>  at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:140)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>  at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:50)
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> [2012-05-07 08:03:22,375]  INFO
> {org.wso2.carbon.tomcat.internal.CarbonTomcat} -  web application context:
> StandardEngine[Catalina].StandardHost[localhost].StandardContext[/project-mgt-tool]
> {org.wso2.carbon.tomcat.internal.CarbonTomcat}
> [2012-05-07 08:03:22,375]  INFO
> {org.wso2.carbon.jaggery.app.mgt.TomcatJaggeryWebappsDeployer} -  Deployed
> Jaggery App:
> StandardEngine[Ca

Re: [Dev] Inserting Categories in p2 Repo

[Dileepa Jayakody]

joining in Isabelle to the discussion.

Thanks,
Dileepa

On Mon, May 7, 2012 at 6:19 PM, Dileepa Jayakody  wrote:

> Hi All,
>
> When improving the kernel feature manager to accommodate
> feature-groups(categories), we grouped some features in
> platform/trunk/features/repository into sample categories for demo purposes.
> Primarily the grouping was done based on product level categorisation, so
> that the users can easily identify and install products on carbon server.
>
> I think this sample list can be improved as the actual list of feature
> categories in Carbon platform. So please add missing features to relevant
> categories or introduce new categories as appropriate. Please note that a
> feature may belong to 1 or many categories.
>
> *AS*
>
>- org.wso2.carbon.jarservices
>- org.wso2.carbon.jaxwsservices
>- org.wso2.carbon.repomanager.axis2
>- org.wso2.carbon.security.mgt
>- org.wso2.carbon.service.mgt
>- org.wso2.carbon.servicehosting
>- org.wso2.carbon.springservices
>- org.wso2.carbon.webapp.mgt
>
> *BAM *
>
>- org.wso2.carbon.bam.data.publisher.activity.mediation
>- org.wso2.carbon.bam.data.publisher.activity.service
>- org.wso2.carbon.bam.data.publisher.mediationstats
>- org.wso2.carbon.bam.data.publisher.servicestats
>- org.wso2.carbon.bam
>
> *Data*
>
>- org.wso2.carbon.dataservices
>- org.wso2.carbon.datasource
>
> *ESB*
>
>- org.wso2.carbon.deployment.synchronizer
>- org.wso2.carbon.endpoint
>- org.wso2.carbon.esb.mediation
>- org.wso2.carbon.localentry
>- org.wso2.carbon.mediation.artifactuploader
>- org.wso2.carbon.mediation.configadmin
>- org.wso2.carbon.mediation.initializer
>- org.wso2.carbon.mediation.statistics
>- org.wso2.carbon.mediation.templates
>- org.wso2.carbon.mediation.tracer
>- org.wso2.carbon.message.flows
>- org.wso2.carbon.message.processor
>- org.wso2.carbon.message.store
>- org.wso2.carbon.messagebox
>- org.wso2.carbon.priority
>- org.wso2.carbon.proxyadmin
>- org.wso2.carbon.rest.api
>- org.wso2.carbon.sequences
>- org.wso2.carbon.smooks
>- org.wso2.carbon.statistics.transport
>- org.wso2.carbon.transport.mgt
>
>  * IS*
>
>- org.wso2.carbon.directory.service.mgr
>- org.wso2.carbon.identity.authenticator.saml2.sso
>- org.wso2.carbon.identity.authenticator.token
>- org.wso2.carbon.identity.core
>- org.wso2.carbon.identity.oauth
>- org.wso2.carbon.identity.provider.openid.admin
>- org.wso2.carbon.identity.provider
>- org.wso2.carbon.identity.relying.party
>- org.wso2.carbon.identity.self.registration
>- org.wso2.carbon.identity.sso.saml
>- org.wso2.carbon.identity.user.profile
>- org.wso2.carbon.identity.xacml
>- org.wso2.carbon.ldap.server
>
> *Registry*
>
>- org.wso2.carbon.governance.gadgets
>- org.wso2.carbon.governance.lifecycle.management
>- org.wso2.carbon.governance.metadata
>- org.wso2.carbon.governance.notifications.configuration
>- org.wso2.carbon.registry.activities
>- org.wso2.carbon.registry.associations.dependencies
>- org.wso2.carbon.registry.community.features
>- org.wso2.carbon.registry.contentsearch
>- org.wso2.carbon.registry.core
>- org.wso2.carbon.registry.extensions
>- org.wso2.carbon.registry.handler.configuration
>- org.wso2.carbon.registry.profiles
>- org.wso2.carbon.registry.resource.properties
>- org.wso2.carbon.registry.social
>- org.wso2.carbon.registry.ui.menu.governance
>- org.wso2.carbon.registry.ui.menu
>- org.wso2.carbon.registry.ws
>
> *Tools*
>
>- org.wso2.carbon.tryit
>- org.wso2.carbon.wsdl.tools
>
> Thanks,
>
> Dileepa
> On Wed, May 2, 2012 at 4:26 PM, Chethiya Abeysinghe wrote:
>
>> Hi,
>>
>> We have changed the p2-repo-gen to generate the repository with category
>> information. So you can simply define categories and include appropriate
>> features into those categories. Once that repo with category information is
>> imported to the feature manger, you can see those defined categories in the
>> UI.
>>
>> To feed in these information, you have to edit the
>> carbon/platform/trunk/features/repository/pom.xml file in svn by adding
>>  element. An example of such a category is shown below. You can
>> include multiple  elements.
>>
>> 
>>  
>> org.wso2.carbon.broker.category
>>  WSO2 Broker Category
>> broker category
>>
>> 
>>   
>>org.wso2.carbon.broker
>> ${carbon.version}
>>   
>>
>>   
>> org.wso2.carbon.brokermanager
>>${carbon.version}
>>   
>>  
>>  
>> 
>>
>> Please note that,  and  are required to include a feature to
>> a category.  is the same ID used with p2-feature-gen goal of the
>> carbon-p2-plugin. You can find that if you look at the pom.xml of any
>> particular feature you want.
>>
>> A sample pom.xml file to reside in repository folder is attached here.
>>
>> Real pom file has a long list of features and hope people who are
>> mana

Re: [Dev] Checking Permissions in a Java API

[Thilina Buddhika]

isUserAuthorized() method in Authorization Manager can be used for this.

For example,

realm.getAuthorizationManager().
isUserAuthorized(username, "/permission/admin/login",
CarbonConstants.UI_PERMISSION_ACTION);

Thanks,
Thilina

On Mon, May 7, 2012 at 10:40 PM, Hiranya Jayathilaka wrote:

> Hi,
>
> I want to check whether a given user has a particular permission. Is there
> some API in Carbon to do this?
>
> Our requirement is that we have a Java API and we want to make  sure that
> some of the methods in this API can only be invoked by users with
> particular permissions. What is the best way to implement something like
> this?
>
> Thanks,
> Hirana
>
> --
> Hiranya Jayathilaka
> Senior Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thilina Buddhika
Associate Technical Lead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 77 44 88 727
blog : http://blog.thilinamb.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Usage of build.properties file in p2 features

[Denis Weerasiri]

Hi,
There's this file build.properties [1],[2] etc in many p2 features. Does
anyone know where it's used in the feature life-cycle?

[1] -
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/features/bpel/org.wso2.carbon.bpel.server.feature/resources/build.properties
[2] -
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/features/broker-manager/org.wso2.carbon.brokermanager.server.feature/resources/build.properties

-- 
Thanks,
Denis
--
*Denis Weerasiri*
Senior Software Engineer
Integration Technologies Team, WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Failed to add features for Carbon server in trunk.

[Dileepa Jayakody]

Hi Lahiru,

Have you disabled 'Group features by category' option? This is enabled by
default in the feature manager.
The mentioned p2 repos don't have categorised feature groups, hence the
feature list is empty when you find features with 'Group features by
category' option enabled.
We need to group the features in our repo into categories, for this default
option to work.
You can list down all the features (without category info), if you disable
the 'Group features by category' and find features.

Thanks,
Dileepa

On Mon, May 7, 2012 at 5:55 PM, Lahiru Sandaruwan  wrote:

> Hi,
>
> I tried to add features to Carbon server in trunk. But it says "No
> Available Features." after i clicked find features. I tried adding several
> repos(3.2.0, 3.2.2, 3.2.3, 3.2.4, and [1] ) but failed.
>
> I got the svn up and built the 'orbit' and 'kernal'.
>
> Please help.
>
> [1]
> http://wso2.org/bamboo/artifact/WSO2CARBON-P2REPO/JOB1/build-77/P2-Repo/p2-repo
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Cloud Team,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahi...@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware

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

Re: [Dev] ESB 4.0.3 product Build Error

[Nirmal Fernando]

Hi Susara,

On Mon, May 7, 2012 at 5:35 PM, Susara De Saram wrote:

> Hi,
>
> I checked out the trunk (Kernel, Orbit and Platform) and tried to build
> the Kernel on Linux. But I got the following error. Any help for this would
> be truly appreciated.
>

You've to build orbit first, then kernel and then platform.

Also please note that carbon-dev@ is deprecated, use dev@wso2.org instead !


> [INFO]
> 
>
> [ERROR] BUILD ERROR
>
> [INFO]
> 
>
> [INFO] Failed to resolve artifact.
>
> ytgh
>
> Missing:
>
> --
>
> 1) asm:asm:jar:3.0
>
>
>
>   Try downloading the file manually from the project website.
>
>
>
>   Then, install it using the command:
>
>   mvn install:install-file -DgroupId=asm -DartifactId=asm
> -Dversion=3.0 -Dpackaging=jar -Dfile=/path/to/file
>
>
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>
>   mvn deploy:deploy-file -DgroupId=asm -DartifactId=asm -Dversion=3.0
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
>
>   Path to dependency:
>
>1) org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0
>
>2) org.apache.maven.shared:maven-dependency-analyzer:jar:1.0
>
>3) asm:asm:jar:3.0
>
>
>
> --
>
> 1 required artifact is missing.
>
>
>
> for artifact:
>
>   org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0
>
>
>
> from the specified remote repositories:
>
>   apache.snapshots (http://repository.apache.org/snapshots),
>
>   repository.dev.java.net-maven2 (http://download.java.net/maven/2/),
>
>   central (http://repo1.maven.org/maven2),
>
>   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository)
>
>
>
>
>
>
>
> [INFO]
> 
>
> [INFO] For more information, run Maven with the -e switch
>
> [INFO]
> 
>
> [INFO] Total time: 41 minutes 8 seconds
>
> [INFO] Finished at: Mon May 07 14:34:31 IST 2012
>
> [INFO] Final Memory: 130M/325M
>
> [INFO]
> 
>
>
>
> Thank you.
>
>
> On Thu, Apr 19, 2012 at 10:31 AM, Srinath Perera  wrote:
>
>> Hi Susara,
>>
>> Lets try the trunk. Checkout each of the following 3 and run mvn clean
>> install -Dmaven.test.skip=true
>>
>> https://svn.wso2.org/repos/wso2/carbon/kernel/trunk
>> https://svn.wso2.org/repos/wso2/carbon/orbit/trunk
>> https://svn.wso2.org/repos/wso2/carbon/platform/trunk
>>
>> If you get any, error respond to the mail.
>>
>> --Srinath
>>
>>
>>
>> On Thu, Apr 19, 2012 at 7:34 AM, Susara De Saram 
>> wrote:
>>
>>> Hi al!
>>>   I need to build WSO2 ESB from source. I successfully built
>>> dependencies, carbon orbit, carbon core, carbon components
>>> and carbon features. Finally I tried building ESB product
>>> (products/esb/4.3.0). But it keeps giving me an error. Any help would be
>>> truly appreciated. The error and the contents of the log file is given
>>> below.
>>> Thank you.
>>>
>>> [INFO] Installing org.wso2.carbon.ec2-client.feature.group 3.2.0.
>>> [INFO] Installing org.wso2.carbon.deployment.synchronizer.feature.group
>>> 3.2.2.
>>> [INFO] Installing
>>> org.wso2.carbon.deployment.synchronizer.subversion.feature.gro
>>> up 3.2.2.
>>> [INFO] Installing org.wso2.carbon.reporting.server.feature.group 3.2.3.
>>> [INFO] Installing org.wso2.carbon.reporting.ui.feature.group 3.2.2.
>>> [ERROR] Cannot complete the install because one or more required items
>>> could not
>>>  be found.
>>> [ERROR]  Software being installed: WSO2 Carbon - Synapse Config Admin
>>> Feature 3.
>>> 2.3 (org.wso2.carbon.mediation.configadmin.feature.group 3.2.3)
>>> [ERROR]  Missing requirement: WSO2 Carbon - Synapse Config Admin Core
>>> Feature 3.
>>> 2.3 (org.wso2.carbon.mediation.configadmin.server.feature.group 3.2.3)
>>> requires
>>> 'org.apache.synapse.wso2.feature.group [2.1.0.wso2v5,2.2.0)' but it
>>> could not be
>>>  found
>>> [ERROR]  Cannot satisfy dependency:
>>> [ERROR]   From: WSO2 Carbon - Synapse Config Admin Feature 3.2.3
>>> (org.wso2.carbo
>>> n.mediation.configadmin.feature.group 3.2.3)
>>> [ERROR]   To: org.wso2.carbon.mediation.configadmin.server.feature.group
>>> [3.2.3]
>>>
>>> [ERROR] Application failed, log file location:
>>> D:\source1-esb\products\esb\4.0.3
>>>
>>> \modules\p2-profile\product\target\p2-agent\configuration\1334799971979.log
>>> [INFO]
>>> 
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> 
>>> [INFO]
>>>
>>> [INFO]
>>> 
>>> [INFO] For more information, run Maven with the -e switch
>>> [INFO]
>>> --

Re: [Dev] Removing Java Service Wrapper from Carbon

[Chintana Wilamuna]

Hi,

Have a blog - http://engwar.com/post/678. Probably better to have a KB item
as well.

-Chintana

On Monday, May 7, 2012, Sameera Jayasoma wrote:

> Hi Chinthana,
>
> On Mon, Feb 27, 2012 at 12:12 PM, Chintana Wilamuna 
> 
> > wrote:
>
>>
>>
>> On Mon, Feb 27, 2012 at 11:49 AM, Sameera Jayasoma 
>> 
>> > wrote:
>>
>> Yeah 20MB is bit of a concern.   Btw, we had an offline discussion with
>>> Azeez and decided to remove Java Service Wrapper.
>>>
>>> Shall we go ahead with nohup thing?
>>>
>>
>> Nohup works ok in Linux. Problem is running it as a service in Windows.
>>
>> For Windows, may be we can point to an OT article about how to download
>> YAJSW and install/configure it as a service?
>>
>
> We have removed JSW from Carbon. In Linux, we use nohup now. For Window,
> we need something like YAJSW. Do we have an article or blog on how to
> integrate YAJSW with Carbon?  If not we might have to write one.
>
> Thanks,
> Sameera.
>
>
>>
>> -Chintana
>>
>> --
>> Chintana Wilamuna
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> phone: +94 75 211 1106
>> blog: http://engwar.com/
>> photos: http://flickr.com/photos/chintana
>> linkedin: http://www.linkedin.com/in/engwar
>> twitter: twitter.com/std_err
>>
>>
>> ___
>> Carbon-dev mailing list
>> carbon-...@wso2.org 
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com 
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>


-- 
Chintana Wilamuna
Associate Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

phone: +94 75 211 1106
blog: http://engwar.com/
photos: http://flickr.com/photos/chintana
linkedin: http://www.linkedin.com/in/engwar
twitter: twitter.com/std_err
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What would be the WSO2 LB product version?

[Nirmal Fernando]

On Tue, May 8, 2012 at 12:06 AM, Sameera Jayasoma  wrote:

> Hi Folks,
>
> At the moment the version is specified as 1.0.0-SNAPSHOT. We need to
> change this.
>
> We released 1.0.0, 1.0.1, 1.0.2 versions AFAIK. But in this release we
> have many more new features and enhancements.
>
> Shall we call 2.0? WDYT?
>

+1, LB has a totally new look now :)


> Thanks,
> Sameera.
>
> --
> Sameera Jayasoma
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks & regards,
Nirmal

Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Hadoop core build failure in windows

[Selvaratnam Uthaiyashankar]

$subject. It uses "sed" command.


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.6:run (default) on
project hadoop-core: An Ant BuildException has occured: The following
error occurred while executing th
is line:
[ERROR] E:\src\java\carbon_trunk\platform\dependencies\hadoop\build.xml:75:
Execute failed: java.io.IOException: Cannot run program "sed" (in
directory "E:\src\java\carbon_trunk\platform\dependencies\
hadoop"): CreateProcess error=2, The system cannot find the file specified
[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/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :hadoop-core

-- 
S.Uthaiyashankar
Senior Software Architect
Chair, Management Committee – Cloud Technologies
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

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

Re: [Dev] Hive build failure in windows

[Selvaratnam Uthaiyashankar]

On Tue, May 8, 2012 at 8:23 AM, Selvaratnam Uthaiyashankar
 wrote:
> $subject. It tries to create a symlink with "ln". This is not valid in
> windows. Please fix this.

Note that ant symlink task can work only in unix based platforms[1].


[1] http://ant.apache.org/manual/Tasks/symlink.html


>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on
> project hive-deploy: An Ant BuildException has occured: The following
> error occurred while executing th
> is line:
> [ERROR] E:\src\java\carbon_trunk\platform\dependencies\hive\build.xml:520:
> Could not launch ln: java.io.IOException: Cannot run program "ln":
> CreateProcess error=2, The system cannot find the file spe
> cified
> [ERROR] around Ant part ... antfile="E:\src\java\carbon_trunk\platform\dependencies\hive\deploy/../build.xml"
> target="package">... @ 4:107 in
> E:\src\java\carbon_trunk\platform\dependencies\hive\de
> ploy\target\antrun\build-main.xml
> [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/MojoExecutionException
>
>
> --
> S.Uthaiyashankar
> Senior Software Architect
> Chair, Management Committee – Cloud Technologies
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> Phone: +94 714897591



-- 
S.Uthaiyashankar
Senior Software Architect
Chair, Management Committee – Cloud Technologies
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

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

[Dev] Hive build failure in windows

[Selvaratnam Uthaiyashankar]

$subject. It tries to create a symlink with "ln". This is not valid in
windows. Please fix this.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on
project hive-deploy: An Ant BuildException has occured: The following
error occurred while executing th
is line:
[ERROR] E:\src\java\carbon_trunk\platform\dependencies\hive\build.xml:520:
Could not launch ln: java.io.IOException: Cannot run program "ln":
CreateProcess error=2, The system cannot find the file spe
cified
[ERROR] around Ant part .. @ 4:107 in
E:\src\java\carbon_trunk\platform\dependencies\hive\de
ploy\target\antrun\build-main.xml
[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/MojoExecutionException


-- 
S.Uthaiyashankar
Senior Software Architect
Chair, Management Committee – Cloud Technologies
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

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

Re: [Dev] C4 beta release on 9 th May 2012

[Sameera Jayasoma]

On Mon, May 7, 2012 at 11:01 AM, Sameera Jayasoma  wrote:

> Hi Pradeep,
>
> I am working on the following issues. Should be able to fix them today.
>
> https://wso2.org/jira/browse/CARBON-13031
> https://wso2.org/jira/browse/CARBON-12899
>

Fixed and committed to the trunk.  Now working on
https://wso2.org/jira/browse/CARBON-13012

Sameera.

>
> Thanks,
> Sameera.
>
>
> On Thu, May 3, 2012 at 12:47 PM, Pradeep Fernando wrote:
>
>> Hi folks,
>>
>> please note the $subject.
>>
>> Altogether there are 10 L1 s to be fixed (Carbon-core). I have listed
>> down the L1s. Owners are expected to send constant progress updates to
>> this thread.
>>
>> CARBON-13009 G-Reg - e-Mail, SOAP, HMTL notifications are not sent
>> for resources when LC transitions happen between environments
>> CARBON-12973HTTP 405 error is thrown when accessing mgmt console
>> without '/' at the end of URL (if there is a webcontextroot)
>> CARBON-12909While the user is logged in to Management console, If
>> the server is restated and Management console page is refreshed, UI
>> becomes unusable and throws errors continually.
>> CARBON-12902ESB throws "System failed to authorize" when it's ideal
>> for few minutes.
>> CARBON-12899axis2-transport-base is included in two jars in the
>> products
>> CARBON-12820EJB service invocation fails due to an NPE
>> (windows/jdk1.7)
>> CARBON-12818AS -- HTTPS Transport configuration directs to a dead page
>> CARBON-12739Tomcat is not generating servlet classes for jsp files
>> which are mapped in webXml
>> CARBON-11056wsdl2java tool is not working fro wsdl2.0 in AS 4.1.0
>> CARBON-11044Non-terminated threads while unloading a webapp which
>> does external WS calls through Axis2 client API
>>
>>
>>
>>
>> I'm working on ,
>>
>> CARBON-12739Tomcat is not generating servlet classes for jsp files
>> which are mapped in webXml
>>
>> thanks,
>> --Pradeep
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Sameera Jayasoma
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>



-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Dev] [Carbon-dev] Removing Java Service Wrapper from Carbon

[Sameera Jayasoma]

Hi Chinthana,

On Mon, Feb 27, 2012 at 12:12 PM, Chintana Wilamuna wrote:

>
>
> On Mon, Feb 27, 2012 at 11:49 AM, Sameera Jayasoma wrote:
>
> Yeah 20MB is bit of a concern.   Btw, we had an offline discussion with
>> Azeez and decided to remove Java Service Wrapper.
>>
>> Shall we go ahead with nohup thing?
>>
>
> Nohup works ok in Linux. Problem is running it as a service in Windows.
>
> For Windows, may be we can point to an OT article about how to download
> YAJSW and install/configure it as a service?
>

We have removed JSW from Carbon. In Linux, we use nohup now. For Window, we
need something like YAJSW. Do we have an article or blog on how to
integrate YAJSW with Carbon?  If not we might have to write one.

Thanks,
Sameera.


>
> -Chintana
>
> --
> Chintana Wilamuna
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> phone: +94 75 211 1106
> blog: http://engwar.com/
> photos: http://flickr.com/photos/chintana
> linkedin: http://www.linkedin.com/in/engwar
> twitter: twitter.com/std_err
>
>
> ___
> Carbon-dev mailing list
> carbon-...@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

[Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #220 has FAILED (2 tests failed). Change made by sameera.

[Bamboo]

---
WSO2 Carbon > Kernel > #220 failed.
---
Code has been updated by sameera.
2/2800 tests failed.

http://wso2.org/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-220/


--
Failing Jobs
--
  - Default Job (Default Stage): 2 of 2800 tests failed.


--
Code Changes
--
sameera (126716):

>fixing https://wso2.org/jira/browse/CARBON-12899

sameera (126696):

>Removing JSW - https://wso2.org/jira/browse/CARBON-13031

sameera (126695):

>Removing JSW - https://wso2.org/jira/browse/CARBON-13031



--
Tests
--
New Test Failures (2)
   - ServerRestartTestCase: Graceful server restart
   - ServerRestartTestCase: Server restart

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Replacing JSW with nohup

[Sameera Jayasoma]

This change is applied to the trunk.

Thanks,
Sameera.

On Fri, Mar 30, 2012 at 9:52 PM, Jorge Infante Osorio wrote:

> +1 for nohup. 
>
> ** **
>
> I used it in our production servers in the university for several weeks
> without any problem.
>
> ** **
>
> Saludos,
>
> Ing. Jorge Infante Osorio.
>
> J´Dpto Soluciones SOA.
>
> CDAE.
>
> Fac. 5.
>
> UCI.
>
> ** **
>
> *De:* dev-boun...@wso2.org [mailto:dev-boun...@wso2.org] *En nombre de 
> *Sameera
> Jayasoma
> *Enviado el:* martes, 27 de marzo de 2012 1:04
> *Para:* WSO2 Developers' List; Sanjaya Ratnaweera; Chintana Wilamuna
> *Asunto:* [Dev] Replacing JSW with nohup
>
> ** **
>
> Hi Devs,
>
> ** **
>
> We've been having many issues due to the JSW(Java Service Wrapper).
> Therefore we thought of removing JSW from the Carbon 4.0.0. release. But we
> will be adding the nohup [1] support.
>
> ** **
>
> WDYT?
>
> ** **
>
> If all agreed, following are the action items.
>
> ** **
>
> * Remove JSW and all the related files.
>
> * Improve wso2server.sh to support nohup (Sanjaya has already made the
> changes, I guess)  Sanjaya, can you please explain?
>
> * For Windows, Chinthana has a solution. Can you please explain?  
>
> ** **
>
> ** **
>
> Thanks,
>
> Sameera.
>
> ** **
>
> [1] http://en.wikipedia.org/wiki/Nohup
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
>   
>
>


-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Dev] API for handling multipart/form-data in Jaggery

[Samisa Abeysinghe]

Are we not feature frozen for 1.0 by now?

On Tue, May 8, 2012 at 6:53 AM, Nuwan Bandara  wrote:

> So ur suggesting we drop FileUpload API (what we have now) and have it
> coupled with request object itself ?
>
> Regards,
> /Nuwan
>
> On Tue, May 8, 2012 at 2:53 AM, Ruchira Wageesha  wrote:
>
>> Hi,
>>
>> It seems in servlets, the request parameter handling is not consistent
>> across all request content types. i.e. When the content type is
>> multipart/form-data, we can't access parameters just using
>> request.getParameter("foo"). In order to handle multipart/form-data,
>> best practice would be to use commons-fileupload.
>>
>> So, it would be better if we can give an easier API to handle
>> multipart/form-data in Jaggery. In Jaggery, we also have
>> request.getParameter("foo") method to get string params sent with
>> application/x-www-form-urlencoded request. But it fails at the moment with
>> multiparts, but can be handled it properly using commons-fileupload.
>>
>> In Jaggery API level, we can have the following. Please reply with your
>> suggessions.
>>
>> request.getParameter("foo"); //return either string or File object
>> depending on the content type/field type
>>
>> or
>>
>>
>> request.getFile("foo"); //instead of using getParameter() method, we can
>> have this method to get file uploads
>>
>>
>> Further, following methods too would be useful.
>>
>> request.getFileMap(); // which will return list of file fields
>> request.getParameterMap();//list of all parameters in the request
>> request.isMultipart();
>>
>> As we now have a Stream Hostobject to effiently deal with stream
>> contents, we can make the returned File object to directly deal with the
>> uploaded stream. So, we can just pass the uploaded file stream to any other
>> HO which deals with streams or save to the disk.
>>
>> In order to save it, what would be the better method?
>>
>> file.save("/foo.jpg"); or file.move("/foo.jpg");
>>
>> Confusion between save() vs move() is due to the write() method we have
>> in File HO. i.e. If we opened a file with
>>
>> var file = new File("myFile.tx");
>>
>> then file.write(content); instantly save content to the file and 
>> save()function won't needed in that case. But move() is valid always. So, 
>> what
>> would be the more appropriate method?
>>
>> The last question, in order to convert the content of a Stream object to
>> a string, what would be the better method name?
>>
>> stream.serialize() or stream.toString()
>>
>> --
>> Ruchira Wageesha
>> Software Engineer - WSO2 Inc. www.wso2.com
>>
>> Email: ruch...@wso2.com Blog: ruchirawagee...@blogspot.com
>> Mobile: +94775493444
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
> Thanks,
Samisa...

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

[Dev] [Bamboo-Build] WSO2 Carbon > platform > #171 was SUCCESSFUL (with 2033 tests). Change made by 13 authors.

[Bamboo]

---
WSO2 Carbon > platform > #171 was successful.
---
This build occurred because it is a dependant of 
WSO2CARBON-CARBONCOREKERNELBUILD-219.
2033 tests in total.

http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-171/


--
Code Changes
--
sameera (126697):

>Removing JSW - https://wso2.org/jira/browse/CARBON-13031

sameera (126700):

>Removing JSW - https://wso2.org/jira/browse/CARBON-13031

kasunw (126692):

>Fixed style issue in bam and also changed bam version from Alpha to Snapshot



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API for handling multipart/form-data in Jaggery

[Nuwan Bandara]

So ur suggesting we drop FileUpload API (what we have now) and have it
coupled with request object itself ?

Regards,
/Nuwan

On Tue, May 8, 2012 at 2:53 AM, Ruchira Wageesha  wrote:

> Hi,
>
> It seems in servlets, the request parameter handling is not consistent
> across all request content types. i.e. When the content type is
> multipart/form-data, we can't access parameters just using
> request.getParameter("foo"). In order to handle multipart/form-data, best
> practice would be to use commons-fileupload.
>
> So, it would be better if we can give an easier API to handle
> multipart/form-data in Jaggery. In Jaggery, we also have
> request.getParameter("foo") method to get string params sent with
> application/x-www-form-urlencoded request. But it fails at the moment with
> multiparts, but can be handled it properly using commons-fileupload.
>
> In Jaggery API level, we can have the following. Please reply with your
> suggessions.
>
> request.getParameter("foo"); //return either string or File object
> depending on the content type/field type
>
> or
>
>
> request.getFile("foo"); //instead of using getParameter() method, we can
> have this method to get file uploads
>
>
> Further, following methods too would be useful.
>
> request.getFileMap(); // which will return list of file fields
> request.getParameterMap();//list of all parameters in the request
> request.isMultipart();
>
> As we now have a Stream Hostobject to effiently deal with stream contents,
> we can make the returned File object to directly deal with the uploaded
> stream. So, we can just pass the uploaded file stream to any other HO which
> deals with streams or save to the disk.
>
> In order to save it, what would be the better method?
>
> file.save("/foo.jpg"); or file.move("/foo.jpg");
>
> Confusion between save() vs move() is due to the write() method we have
> in File HO. i.e. If we opened a file with
>
> var file = new File("myFile.tx");
>
> then file.write(content); instantly save content to the file and 
> save()function won't needed in that case. But move() is valid always. So, what
> would be the more appropriate method?
>
> The last question, in order to convert the content of a Stream object to a
> string, what would be the better method name?
>
> stream.serialize() or stream.toString()
>
> --
> Ruchira Wageesha
> Software Engineer - WSO2 Inc. www.wso2.com
>
> Email: ruch...@wso2.com Blog: ruchirawagee...@blogspot.com
> Mobile: +94775493444
>
> Lean . Enterprise . Middleware
>



-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

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

Re: [Dev] [Architecture] API for handling multipart/form-data in Jaggery

[Srinath Perera]

On Tue, May 8, 2012 at 2:53 AM, Ruchira Wageesha  wrote:
> Hi,
>
> It seems in servlets, the request parameter handling is not consistent
> across all request content types. i.e. When the content type is
> multipart/form-data, we can't access parameters just using
> request.getParameter("foo"). In order to handle multipart/form-data, best
> practice would be to use commons-fileupload.
>
> So, it would be better if we can give an easier API to handle
> multipart/form-data in Jaggery. In Jaggery, we also have
> request.getParameter("foo") method to get string params sent with
> application/x-www-form-urlencoded request. But it fails at the moment with
> multiparts, but can be handled it properly using commons-fileupload.
>
> In Jaggery API level, we can have the following. Please reply with your
> suggessions.
>
> request.getParameter("foo"); //return either string or File object depending
> on the content type/field type
>
> or
>
>
> request.getFile("foo"); //instead of using getParameter() method, we can
> have this method to get file uploads

I prefer getFile(..) .. I guess if there is no file, it can return null

>
> Further, following methods too would be useful.
>
> request.getFileMap(); // which will return list of file fields
> request.getParameterMap();//list of all parameters in the request
> request.isMultipart();
>
> As we now have a Stream Hostobject to effiently deal with stream contents,
> we can make the returned File object to directly deal with the uploaded
> stream. So, we can just pass the uploaded file stream to any other HO which
> deals with streams or save to the disk.
>
> In order to save it, what would be the better method?
>
> file.save("/foo.jpg"); or file.move("/foo.jpg");
>
> Confusion between save() vs move() is due to the write() method we have in
> File HO. i.e. If we opened a file with
>
> var file = new File("myFile.tx");
>
> then file.write(content); instantly save content to the file and save()
> function won't needed in that case. But move() is valid always. So, what
> would be the more appropriate method?
How about "SaveAs" .. note that move have the additional semantic of
deleting the current file

>
> The last question, in order to convert the content of a Stream object to a
> string, what would be the better method name?
>
> stream.serialize() or stream.toString()
toString() ;)

--Srinath

>
> --
> Ruchira Wageesha
> Software Engineer - WSO2 Inc. www.wso2.com
>
> Email: ruch...@wso2.com Blog: ruchirawagee...@blogspot.com
> Mobile: +94775493444
>
> Lean . Enterprise . Middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>



-- 

Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #219 was SUCCESSFUL (with 2800 tests). Change made by kishanthan.

[Bamboo]

---
WSO2 Carbon > Kernel > #219 was successful.
---
Code has been updated by kishanthan.
2800 tests in total.

http://wso2.org/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-219/


--
Code Changes
--
kishanthan (126669):

>

kishanthan (126671):

>Add Ghost deployer registry only if ghost is on in TenantAxisConfigurator



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] API for handling multipart/form-data in Jaggery

[Ruchira Wageesha]

Hi,

It seems in servlets, the request parameter handling is not consistent
across all request content types. i.e. When the content type is
multipart/form-data, we can't access parameters just using
request.getParameter("foo"). In order to handle multipart/form-data, best
practice would be to use commons-fileupload.

So, it would be better if we can give an easier API to handle
multipart/form-data in Jaggery. In Jaggery, we also have
request.getParameter("foo") method to get string params sent with
application/x-www-form-urlencoded request. But it fails at the moment with
multiparts, but can be handled it properly using commons-fileupload.

In Jaggery API level, we can have the following. Please reply with your
suggessions.

request.getParameter("foo"); //return either string or File object
depending on the content type/field type

or


request.getFile("foo"); //instead of using getParameter() method, we can
have this method to get file uploads


Further, following methods too would be useful.

request.getFileMap(); // which will return list of file fields
request.getParameterMap();//list of all parameters in the request
request.isMultipart();

As we now have a Stream Hostobject to effiently deal with stream contents,
we can make the returned File object to directly deal with the uploaded
stream. So, we can just pass the uploaded file stream to any other HO which
deals with streams or save to the disk.

In order to save it, what would be the better method?

file.save("/foo.jpg"); or file.move("/foo.jpg");

Confusion between save() vs move() is due to the write() method we have in
File HO. i.e. If we opened a file with

var file = new File("myFile.tx");

then file.write(content); instantly save content to the file and
save()function won't needed in that case. But move() is valid always.
So, what
would be the more appropriate method?

The last question, in order to convert the content of a Stream object to a
string, what would be the better method name?

stream.serialize() or stream.toString()

-- 
Ruchira Wageesha
Software Engineer - WSO2 Inc. www.wso2.com

Email: ruch...@wso2.com Blog: ruchirawagee...@blogspot.com
Mobile: +94775493444

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

Re: [Dev] Build failure when building Coordination Feature

[Denis Weerasiri]

Hi Dinusha,
Still the error exist in the latest build.

[ERROR] Failed to execute goal on project
org.wso2.carbon.coordination.feature: Could not resolve dependencies for
project
org.wso2.carbon:org.wso2.carbon.coordination.feature:pom:4.0.0-SNAPSHOT:
Could not find artifact
org.wso2.carbon:org.wso2.carbon.coordination.core.feature:zip:4.0.0-SNAPSHOT
in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
[Help 1]

On Mon, May 7, 2012 at 11:58 AM, Prabath Abeysekera wrote:

> Hi Ranga,
>
> On Mon, May 7, 2012 at 11:15 AM, Ranga Siriwardena  wrote:
>
>> Hi,
>>
>> I'm getting following error when building with a clean repo. Please let
>> me know if I'm missing something.
>>
>
> I ll have a look.
>
>
>>
>>
>> [INFO]
>> 
>> [INFO] Building WSO2 Carbon - Coordination Feature 4.0.0-SNAPSHOT
>> [INFO]
>> 
>> [WARNING] The POM for
>> org.wso2.carbon:org.wso2.carbon.coordination.core.feature:zip:4.0.0-SNAPSHOT
>> is missing, no dependency information available
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 Carbon - Coordination Feature Aggregator Module  SUCCESS
>> [0.465s]
>> [INFO] WSO2 Carbon - Coordination Server Feature . SUCCESS
>> [1.875s]
>> [INFO] WSO2 Carbon - Coordination Feature  FAILURE
>> [0.103s]
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 2.878s
>> [INFO] Finished at: Mon May 07 11:11:01 IST 2012
>> [INFO] Final Memory: 14M/981M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.coordination.feature: Could not resolve dependencies for
>> project
>> org.wso2.carbon:org.wso2.carbon.coordination.feature:pom:4.0.0-SNAPSHOT:
>> Failure to find
>> org.wso2.carbon:org.wso2.carbon.coordination.core.feature:zip:4.0.0-SNAPSHOT
>> in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
>> the local repository, resolution will not be reattempted until the update
>> interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [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/DependencyResolutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :org.wso2.carbon.coordination.feature
>>
>>
>>
>> Thank You.
>>  Ranga.
>> --
>> Ranga Siriwardena
>> Software Engineer
>> WSO2 Inc.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Prabath Abeysekara
> Software Engineer
> WSO2 Inc.
> Email: praba...@wso2.com 
> Mobile: +94774171471
>
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Senior Software Engineer
Integration Technologies Team, WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] What would be the WSO2 LB product version?

[Sameera Jayasoma]

Hi Folks,

At the moment the version is specified as 1.0.0-SNAPSHOT. We need to change
this.

We released 1.0.0, 1.0.1, 1.0.2 versions AFAIK. But in this release we have
many more new features and enhancements.

Shall we call 2.0? WDYT?

Thanks,
Sameera.

-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Dev] Some API Changes to the API Manager

[Ajith Vitharana]

On Mon, May 7, 2012 at 11:21 PM, Hiranya Jayathilaka wrote:

> Sumedha and the API Manager team,
>
> In order to improve the internal design  I'd like to propose following API
> changes to the API manager implementation:
>
> 1. Add following 2 new methods to the APIManager interface (Some variants
> of these method are already available in the APIManagerImpl class, but they
> are not part of the API. I think we should make the following generalized
> methods part of the core API and use them from the host objects as required)
> InputStream getIcon(APIIdentifier id)
> void addIcon(APIIdentifier id, InputStream in, String
> contentType)
>

+1 .After that we can remove the addApiThumb() method  from  APIManagerImpl.


>
> 2. Move the getSubscriberAPIs method from APIConsumer to APIManager (This
> method is already used by the API provider host object. Clearly it's
> required by API consumers as well as API providers).
>

+1. The functions which are commonly used should be inside the APIManager.


> 3. Introduce a new username argument (String) to the addComment and
> rateAPI methods. We need to perform these operations using the governance
> user registry of the corresponding users. Otherwise the system will not
> properly keep track of the comment authors. To make the core API more
> generic I think we should introduce the username argument to the above
> methods.
>

 Shall we pass UserRegistry instead of user name?


> If you don't see any issues with these changes, I'll get started with
> refactoring. In order to handle authorization what I thought was to
> implement a new wrapper for the existing impl classes. The wrapper will
> imply extend the classes providing the necessary authorization logic
> (permission checking) where necessary. I've spawned a new thread regarding
> this on the mailing list. If we don't get any better ideas we can implement
> that.
>
> Thanks
> --
> Hiranya Jayathilaka
> Senior Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.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 : +94714631794
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Some API Changes to the API Manager

[Hiranya Jayathilaka]

Sumedha and the API Manager team,

In order to improve the internal design  I'd like to propose following API
changes to the API manager implementation:

1. Add following 2 new methods to the APIManager interface (Some variants
of these method are already available in the APIManagerImpl class, but they
are not part of the API. I think we should make the following generalized
methods part of the core API and use them from the host objects as required)
InputStream getIcon(APIIdentifier id)
void addIcon(APIIdentifier id, InputStream in, String
contentType)

2. Move the getSubscriberAPIs method from APIConsumer to APIManager (This
method is already used by the API provider host object. Clearly it's
required by API consumers as well as API providers)

3. Introduce a new username argument (String) to the addComment and rateAPI
methods. We need to perform these operations using the governance user
registry of the corresponding users. Otherwise the system will not properly
keep track of the comment authors. To make the core API more generic I
think we should introduce the username argument to the above methods.

If you don't see any issues with these changes, I'll get started with
refactoring. In order to handle authorization what I thought was to
implement a new wrapper for the existing impl classes. The wrapper will
imply extend the classes providing the necessary authorization logic
(permission checking) where necessary. I've spawned a new thread regarding
this on the mailing list. If we don't get any better ideas we can implement
that.

Thanks
-- 
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon > platform > #170 has FAILED. Change made by 19 authors.

[Bamboo]

---
WSO2 Carbon > platform > #170 failed.
---
This build was manually triggered by BambooBuilder.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-170/


--
Failing Jobs
--
  - Default Job (Default Stage): 2033 tests passed.


--
Code Changes
--
chanaka (126625):

>Fixing API Store UI issues

sanjeewa (126617):

>add endpoint service component to internal package

hasithah (126594):

>added new images for user guide.



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Registry based Deployment Synchronizer does not work [was Fwd: https://wso2.org/jira/browse/CARBON-12801]

[Hiranya Jayathilaka]

On Mon, May 7, 2012 at 10:06 PM, Charitha Kankanamge wrote:

> Why should we enable axis2 clustering in order to get registry based
> deployment synchronizer working?


This might be due to the improvements Azeez implemented recently. Basically
we use the clustering group comm mechanism to pass events among the nodes
and these events fire the synchronizer activities.

Thanks,
Hiranya


>
>
> On Monday, May 7, 2012, Subash Chaturanga wrote:
>
>>
>>
>> On Mon, May 7, 2012 at 2:19 PM, Charitha Kankanamge wrote:
>>
>>> Has anyone got registry based deployment working with C4 alpha packs? I
>>> tried with setting up a 2 node ESB cluster with registry based synchronizer
>>> but it does not seem to work. The artifacts are synchronized across cluster
>>> nodes only if the nodes are restarted.
>>>
>>>
>> Hi Charitha,
>> I was able to get this working on C4 alpha packs.
>> I also setup a two node master slave ESB cluster with a shared registry
>> which runs on mysql (*without using the admin console).
>>
>> But with the given instructions to reproduce this in the 
>> CARBON-13044,
>> I also could not get this working. Because the clustering should be enabled
>> in the axis2 level.
>> With that I got deployment sync working.
>>
>> (The UI seems to be broken and gives me exceptions (and thus I did it
>> from xml configs), but still it shows that the deployment sync created).
>>  Did you enabled clustering in axis2.xml ?
>>
>> [1]https://wso2.org/jira/browse/CARBON-13044
>>>
>>> Please have a look at this and resolve if there is a bug. This is very
>>> important for us to proceed with production test setups.
>>>
>>> /Charitha
>>>
>>> -- Forwarded message --
>>> From: *Kasun Gajasinghe* 
>>> Date: Wed, Apr 25, 2012 at 8:34 PM
>>> Subject: Re: https://wso2.org/jira/browse/CARBON-12801
>>> To: Hiranya Jayathilaka 
>>> Cc: Charitha Kankanamge , Dimuthu Leelarathne <
>>> dimut...@wso2.com>, Afkham Azeez , support-dev-group <
>>> support-dev-gr...@wso2.com>
>>>
>>>
>>>
>>>
>>> On Wed, Apr 25, 2012 at 12:23 AM, Hiranya Jayathilaka 
>>> wrote:
>>>
>>>
>>>
>>> On Tue, Apr 24, 2012 at 6:13 PM, Kasun Gajasinghe wrote:
>>>
>>>
>>> We should find a way to resolve the conflicts. Current implementation
>>> doesn't support conflict resolving. As I found out, for svn-based depsync,
>>> the svn conflict resolver is not implemented in Svnclient.
>>>
>>>
>>> It is implemented.
>>>
>>>
>>>
>>> Let me clarify what I meant to say. Yes, 'resolved' subcommand is
>>> implemented. Though it's deprecated in favor of 'resolve' subcommand, the
>>> functionality is there. What's not there is a way to resolve conflicts *the
>>> moment it happens in commandline adapter*. There's a callback
>>> functionality implemented (DefaultConflictResolver), but this callback
>>> isn't used because the underlying methods are marked as TODO.
>>>
>>>
>>> I think this should be implemented, or bring in a new underlying
>>> dependency for Svnclient like svnkit instead of current CommandLine
>>> adapter that already has the needed implementation.
>>>
>>>
>>> We can't take a dependency on SVN Kit and redistribute it due to
>>> licensing matters. But SVN client adapter allows you  to use SVN Kit as a
>>> drop-in. That's what we do in SLive.
>>>
>>>
>>> Yes, the license is a problem. Seems they are using a custom license
>>> called TMate license. In this case, the ideal path is to implement the
>>> needed implementation for commandline adapter. The code seems to be easy to
>>> understand as well. I believe there must be a way to automatically resolve
>>> conflicts because when that happens, that node can no longer commit. And,
>>> when there's xml files, the structure is broken because svn adds content
>>> like the following to conflicted xml files.
>>>
>>> >> .mine
>>> ---
>>> <
>>> ---
>>>
>>> Thanks,
>>> --KasunG
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>> ___
>>>
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>
> --
> Charitha Kankanamge
> cell: +94 718 359 265
> blog: http://charithaka.blogspot.com 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding proxy services using the UI

[Hiranya Jayathilaka]

Hi,

On Mon, May 7, 2012 at 6:08 PM, Afkham Azeez  wrote:

>
>
> On Mon, May 7, 2012 at 6:03 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Mon, May 7, 2012 at 5:11 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, May 7, 2012 at 3:09 PM, Afkham Azeez  wrote:
>>>
 Folks.,
 Any feedback on this? Does this make sense?

>>>
>>> I don't think so. We have a very clear separation between named
>>> sequences/endpoints and anonymous sequences/endpoints. Anonymous objects
>>> are local to a particular proxy service or an API and they are not visible
>>> to other services. Sort of like a private method. Named objects on the
>>> other hand are visible to everybody, can be shared/reused extensively and
>>> do show up in the Synape global namespace. Both have specific, well-defined
>>> use cases and I don't see a strong use case for having named sequences
>>> inside a proxy or an API.
>>>
>>
>> What about the service chaining scenario? We unnecessarily have to define
>> sequences in the global space even though those will be needed only by one
>> particular proxy service. Take a look at the example at
>> http://blog.afkham.org/2012/05/wso2-esb-service-chaining.html. I had to
>> define personInfoSeq & creditSeq at the global level even though I
>> needed them only within the proxy service. Is there a way to achieve the
>> same thing while keeping everything local (without following the old state
>> property based case handling)?
>>
>
> In other words, is there a way to set the "receive" attribute of the send
> mediator to an anonymous (local to proxy service) sequence?
>

Send mediator can only lookup named sequences. And in the current Synapse
registry implementation, all named objects are kept in a global scope. So
what you're suggesting is to implement a new service/API scope for Synapse
language. This should be possible, but I'm not sure how much effort it's
going to take. However the question is, how badly do we want to do this?
What are the other use cases we might have?

Thanks,
Hiranya


-- 
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Checking Permissions in a Java API

[Hiranya Jayathilaka]

Hi,

I want to check whether a given user has a particular permission. Is there
some API in Carbon to do this?

Our requirement is that we have a Java API and we want to make  sure that
some of the methods in this API can only be invoked by users with
particular permissions. What is the best way to implement something like
this?

Thanks,
Hirana

-- 
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Jaggery new Dir structure changes are committed to the trunk

[Madhuka Udantha]

Hi,

Would be great if some windows folks try to build and run this.
I tried this on windows (Windows 7) it works.

here is new Structure, in jaggery from Windows Look

├───apps
│   ├───docs
│   │   ├───apidocs
│   │   ├───css
│   │   ├───edit_area
│   │   │   ├───images
│   │   │   ├───langs
│   │   │   └───reg_syntax
│   │   ├───images
│   │   ├───includes
│   │   ├───js
│   │   │   └───google-code-prettify
│   │   ├───lib
│   │   ├───tmp
│   │   └───tryit
│   ├───freshometer
│   │   ├───images
│   │   └───js
│   ├───sample
│   │   └───bar
│   └───shout
│   ├───css
│   ├───fancybox
│   ├───font
│   ├───images
│   └───js
├───bin
├───carbon
│   ├───bin
│   │   └───native
│   ├───dbscripts
│   ├───lib
│   │   ├───endorsed
│   │   ├───patches
│   │   ├───tomcat
│   │   │   ├───conf
│   │   │   │   └───Catalina
│   │   │   │   └───localhost
│   │   │   ├───webapps
│   │   │   └───work
│   │   │   └───Catalina
│   │   │   └───localhost
│   │   │   ├───docs
│   │   │   ├───freshometer
│   │   │   ├───sample
│   │   │   ├───shout
│   │   │   └───_
│   │   │   └───proxytemp
│   │   │   ├───hc_1013142561
│   │   │   └───hc_1715274790
│   │   └───xboot
│   ├───repository
│   │   ├───components
│   │   │   ├───configuration
│   │   │   │   ├───org.eclipse.core.runtime
│   │   │   │   │   └───.manager
│   │   │   │   ├───org.eclipse.equinox.app
│   │   │   │   │   └───.manager
│   │   │   │   ├───org.eclipse.equinox.simpleconfigurator
│   │   │   │   ├───org.eclipse.osgi
│   │   │   │   │   ├───.manager
│   │   │   │   │   └───bundles
│   │   │   │   │   ├───11
│   │   │   │   │   │   └───1
│   │   │   │   │   │   └───.cp
│   │   │   │   │   ├───110
│   │   │   │   │   │   └───1
│   │   │   │   │   │   └───.cp
│   │   │   │   │   ├───181
│   │   │   │   │   │   └───1
│   │   │   │   │   │   └───.cp
│   │   │   │   │   ├───187
│   │   │   │   │   │   └───1
│   │   │   │   │   │   └───.cp
│   │   │   │   │   ├───30
│   │   │   │   │   │   └───1
│   │   │   │   │   │   └───.cp
│   │   │   │   │   └───65
│   │   │   │   │   └───data
│   │   │   │   └───org.eclipse.update
│   │   │   ├───dropins
│   │   │   ├───extensions
│   │   │   ├───features
│   │   │   │   ├───org.wso2.carbon.core.common_4.0.0.SNAPSHOT
│   │   │   │   │   └───META-INF
│   │   │   │   ├───org.wso2.carbon.core.runtime_4.0.0.SNAPSHOT
│   │   │   │   │   └───META-INF
│   │   │   │   ├───org.wso2.carbon.core.server_4.0.0.SNAPSHOT
│   │   │   │   │   └───META-INF
│   │   │   │   ├───org.wso2.carbon.core.ui_4.0.0.SNAPSHOT
│   │   │   │   │   └───META-INF
│   │   │   │   ├───org.wso2.carbon.core_4.0.0.SNAPSHOT
│   │   │   │   │   └───META-INF
│   │   │   │   ├───org.wso2.carbon.jaggery.server_1.0.0.SNAPSHOT
│   │   │   │   │   └───META-INF
│   │   │   │   ├───org.wso2.carbon.jaggery.ui_1.0.0.SNAPSHOT
│   │   │   │   │   └───META-INF
│   │   │   │   └───org.wso2.jaggery.styles_1.0.0.SNAPSHOT_M4
│   │   │   │   └───META-INF
│   │   │   ├───lib
│   │   │   ├───p2
│   │   │   │   ├───org.eclipse.equinox.p2.core
│   │   │   │   │   └───cache
│   │   │   │   └───org.eclipse.equinox.p2.engine
│   │   │   │   ├───.settings
│   │   │   │   └───profileRegistry
│   │   │   │   └───WSO2CarbonProfile.profile
│   │   │   ├───patches
│   │   │   └───plugins
│   │   │
├───org.eclipse.equinox.launcher.gtk.linux.x86_1.1.100.v20110505
│   │   │   │   └───META-INF
│   │   │   └───org.eclipse.equinox.p2.publisher.eclipse_1.0.0.v20110511
│   │   │   ├───ant_tasks
│   │   │   └───META-INF
│   │   ├───conf
│   │   │   ├───axis2
│   │   │   ├───email
│   │   │   ├───etc
│   │   │   ├───security
│   │   │   └───tomcat
│   │   ├───data
│   │   ├───database
│   │   ├───deployment
│   │   │   ├───client
│   │   │   │   ├───modules
│   │   │   │   └───services
│   │   │   └───server
│   │   │   ├───axis2modules
│   │   │   ├───axis2services
│   │   │   └───carbonapps
│   │   ├───logs
│   │   ├───resources
│   │   │   └───security
│   │   │   └───tokenstore
│   │   └───tenants
│   └───tmp
│   ├───axis2-tmp-8791009663577736617.tmp
│   ├───bundles_info_33a559c4-dbc7-409b-9c7c-09db4c686338
│   ├───carbonapps
│   ├───jarsToBundles
│   │   └───13363922365570.07911588552738402
│   │   └───META-INF
│   └───work
├───modulemetafiles
└───modules

Thank you

On Mon, May 7, 2012 at 4:16 PM, Nuwan Bandara  wrote:

> Hi All,
>
> I have done the required changes to create the proposed jaggery Directory
> structure. Please take an update and build the jaggery product to see the
> changes. Would be great if some windows folks try to build and run this.
>
> if there are any error please do report.
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Memb

Re: [Dev] Registry based Deployment Synchronizer does not work [was Fwd: https://wso2.org/jira/browse/CARBON-12801]

[Charitha Kankanamge]

Why should we enable axis2 clustering in order to get registry based
deployment synchronizer working?

On Monday, May 7, 2012, Subash Chaturanga wrote:

>
>
> On Mon, May 7, 2012 at 2:19 PM, Charitha Kankanamge 
> 
> > wrote:
>
>> Has anyone got registry based deployment working with C4 alpha packs? I
>> tried with setting up a 2 node ESB cluster with registry based synchronizer
>> but it does not seem to work. The artifacts are synchronized across cluster
>> nodes only if the nodes are restarted.
>>
>>
> Hi Charitha,
> I was able to get this working on C4 alpha packs.
> I also setup a two node master slave ESB cluster with a shared registry
> which runs on mysql (*without using the admin console).
>
> But with the given instructions to reproduce this in the 
> CARBON-13044,
> I also could not get this working. Because the clustering should be enabled
> in the axis2 level.
> With that I got deployment sync working.
>
> (The UI seems to be broken and gives me exceptions (and thus I did it from
> xml configs), but still it shows that the deployment sync created).
> Did you enabled clustering in axis2.xml ?
>
> [1]https://wso2.org/jira/browse/CARBON-13044
>>
>> Please have a look at this and resolve if there is a bug. This is very
>> important for us to proceed with production test setups.
>>
>> /Charitha
>>
>> -- Forwarded message --
>> From: *Kasun Gajasinghe* 
>> Date: Wed, Apr 25, 2012 at 8:34 PM
>> Subject: Re: https://wso2.org/jira/browse/CARBON-12801
>> To: Hiranya Jayathilaka 
>> Cc: Charitha Kankanamge , Dimuthu Leelarathne <
>> dimut...@wso2.com>, Afkham Azeez , support-dev-group <
>> support-dev-gr...@wso2.com>
>>
>>
>>
>>
>> On Wed, Apr 25, 2012 at 12:23 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>
>>
>> On Tue, Apr 24, 2012 at 6:13 PM, Kasun Gajasinghe wrote:
>>
>>
>> We should find a way to resolve the conflicts. Current implementation
>> doesn't support conflict resolving. As I found out, for svn-based depsync,
>> the svn conflict resolver is not implemented in Svnclient.
>>
>>
>> It is implemented.
>>
>>
>>
>> Let me clarify what I meant to say. Yes, 'resolved' subcommand is
>> implemented. Though it's deprecated in favor of 'resolve' subcommand, the
>> functionality is there. What's not there is a way to resolve conflicts *the
>> moment it happens in commandline adapter*. There's a callback
>> functionality implemented (DefaultConflictResolver), but this callback
>> isn't used because the underlying methods are marked as TODO.
>>
>>
>> I think this should be implemented, or bring in a new underlying
>> dependency for Svnclient like svnkit instead of current CommandLine
>> adapter that already has the needed implementation.
>>
>>
>> We can't take a dependency on SVN Kit and redistribute it due to
>> licensing matters. But SVN client adapter allows you  to use SVN Kit as a
>> drop-in. That's what we do in SLive.
>>
>>
>> Yes, the license is a problem. Seems they are using a custom license
>> called TMate license. In this case, the ideal path is to implement the
>> needed implementation for commandline adapter. The code seems to be easy to
>> understand as well. I believe there must be a way to automatically resolve
>> conflicts because when that happens, that node can no longer commit. And,
>> when there's xml files, the structure is broken because svn adds content
>> like the following to conflicted xml files.
>>
>> >> .mine
>> ---
>> <
>> ---
>>
>> Thanks,
>> --KasunG
>>
>> Thanks,
>> Hiranya
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org 
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com 
> phone - 077 2225922
>
>

-- 
Charitha Kankanamge
cell: +94 718 359 265
blog: http://charithaka.blogspot.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Do we still use wso2cloud-server.sh script in Stratos Serices?

[Sanjaya Ratnaweera]

On Mon, May 7, 2012 at 6:36 PM, Afkham Azeez  wrote:

> wso2cloud-server.sh has production optimization stuff & also enables the
> Java Security Manager. So we need the settings in that for production use.
> I'm not sure whether it is used in Stratos Live. Sanjaya?
>
>
Nope, we are using wso2server.sh written to start with nohup, adding
Security Manager parameters.

Thanks

~sanjaya


>  On Mon, May 7, 2012 at 5:43 PM, Sameera Jayasoma wrote:
>
>>  Most of the wso2cloud-server.sh files in the stratos services contain
>> invalid stuff. We need to update them if we are using, or else we can
>> remove them.
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Mon, May 7, 2012 at 2:34 PM, Sameera Jayasoma wrote:
>>
>>> Subject please.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> --
>>> Sameera Jayasoma
>>> Technical Lead
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://tech.jayasoma.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Sanjaya Ratnaweera
Senior Software Engineer; WSO2 Inc; http://www.wso2.com/.

blog: http://www.samudura.org
homepage: http://www.samudura.net
twitter: http://twitter.com/sanjayar

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

Re: [Dev] WSO2 Committers += Chethiya

[Pradeep Fernando]

Hi,

Congratz!!! and welcome aboard!!

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

Re: [Dev] C4 beta release on 9 th May 2012

[Charitha Kankanamge]

Appreciate the deployment synchronizer bugs [1][2] can be fixed. These are
blockers for production test setups

[1]https://wso2.org/jira/browse/CARBON-13044
[2]https://wso2.org/jira/browse/CARBON-13045

/Charitha

On Mon, May 7, 2012 at 2:46 PM, Pradeep Fernando  wrote:

> Hi,
>
> Subash is looking in to the registry related issues. Altogether there
> are 7 issues.
>
> CARBON-12977 Governance collection has gone missing after
> restarting ESB cluster nodes
> CARBON-12974 G-Reg - Resources/collections added from a mounted
> instance, not visible through governance registry instance unless a
> new collection is added OR the G-Reg server is restarted
> CARBON-12871 Performance improvements related to G-Reg 4.1.1
> CARBON-12840 Add comments for configurations in registry.xml
> CARBON-12790 ESB - Dead page returned when saving edited WSDLs/Schemas
> CARBON-12758 BackwardAssociationHandlerTestCase and WSDLTestCase are
> failing
> CARBON-12658 UDDI not Working after Carbon lib folder restructuring
>
>
> --Pradeep
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #218 has FAILED

[Bamboo]

---
WSO2 Carbon > Kernel > #218 failed.
---
This build was manually triggered by BambooBuilder.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-218/


--
Failing Jobs
--
  - Default Job (Default Stage): 2800 tests passed.



--
Tests
--
Fixed Tests (1)
   - ServerShutdownTestCase: Server shutdown

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Do we still use wso2cloud-server.sh script in Stratos Serices?

[Afkham Azeez]

wso2cloud-server.sh has production optimization stuff & also enables the
Java Security Manager. So we need the settings in that for production use.
I'm not sure whether it is used in Stratos Live. Sanjaya?

On Mon, May 7, 2012 at 5:43 PM, Sameera Jayasoma  wrote:

> Most of the wso2cloud-server.sh files in the stratos services contain
> invalid stuff. We need to update them if we are using, or else we can
> remove them.
>
> Thanks,
> Sameera.
>
>
> On Mon, May 7, 2012 at 2:34 PM, Sameera Jayasoma  wrote:
>
>> Subject please.
>>
>> Thanks,
>> Sameera.
>>
>> --
>> Sameera Jayasoma
>> Technical Lead
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Sameera Jayasoma
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Inserting Categories in p2 Repo

[Dileepa Jayakody]

Hi All,

When improving the kernel feature manager to accommodate
feature-groups(categories), we grouped some features in
platform/trunk/features/repository into sample categories for demo purposes.
Primarily the grouping was done based on product level categorisation, so
that the users can easily identify and install products on carbon server.

I think this sample list can be improved as the actual list of feature
categories in Carbon platform. So please add missing features to relevant
categories or introduce new categories as appropriate. Please note that a
feature may belong to 1 or many categories.

*AS*

   - org.wso2.carbon.jarservices
   - org.wso2.carbon.jaxwsservices
   - org.wso2.carbon.repomanager.axis2
   - org.wso2.carbon.security.mgt
   - org.wso2.carbon.service.mgt
   - org.wso2.carbon.servicehosting
   - org.wso2.carbon.springservices
   - org.wso2.carbon.webapp.mgt

*BAM *

   - org.wso2.carbon.bam.data.publisher.activity.mediation
   - org.wso2.carbon.bam.data.publisher.activity.service
   - org.wso2.carbon.bam.data.publisher.mediationstats
   - org.wso2.carbon.bam.data.publisher.servicestats
   - org.wso2.carbon.bam

*Data*

   - org.wso2.carbon.dataservices
   - org.wso2.carbon.datasource

*ESB*

   - org.wso2.carbon.deployment.synchronizer
   - org.wso2.carbon.endpoint
   - org.wso2.carbon.esb.mediation
   - org.wso2.carbon.localentry
   - org.wso2.carbon.mediation.artifactuploader
   - org.wso2.carbon.mediation.configadmin
   - org.wso2.carbon.mediation.initializer
   - org.wso2.carbon.mediation.statistics
   - org.wso2.carbon.mediation.templates
   - org.wso2.carbon.mediation.tracer
   - org.wso2.carbon.message.flows
   - org.wso2.carbon.message.processor
   - org.wso2.carbon.message.store
   - org.wso2.carbon.messagebox
   - org.wso2.carbon.priority
   - org.wso2.carbon.proxyadmin
   - org.wso2.carbon.rest.api
   - org.wso2.carbon.sequences
   - org.wso2.carbon.smooks
   - org.wso2.carbon.statistics.transport
   - org.wso2.carbon.transport.mgt

 * IS*

   - org.wso2.carbon.directory.service.mgr
   - org.wso2.carbon.identity.authenticator.saml2.sso
   - org.wso2.carbon.identity.authenticator.token
   - org.wso2.carbon.identity.core
   - org.wso2.carbon.identity.oauth
   - org.wso2.carbon.identity.provider.openid.admin
   - org.wso2.carbon.identity.provider
   - org.wso2.carbon.identity.relying.party
   - org.wso2.carbon.identity.self.registration
   - org.wso2.carbon.identity.sso.saml
   - org.wso2.carbon.identity.user.profile
   - org.wso2.carbon.identity.xacml
   - org.wso2.carbon.ldap.server

*Registry*

   - org.wso2.carbon.governance.gadgets
   - org.wso2.carbon.governance.lifecycle.management
   - org.wso2.carbon.governance.metadata
   - org.wso2.carbon.governance.notifications.configuration
   - org.wso2.carbon.registry.activities
   - org.wso2.carbon.registry.associations.dependencies
   - org.wso2.carbon.registry.community.features
   - org.wso2.carbon.registry.contentsearch
   - org.wso2.carbon.registry.core
   - org.wso2.carbon.registry.extensions
   - org.wso2.carbon.registry.handler.configuration
   - org.wso2.carbon.registry.profiles
   - org.wso2.carbon.registry.resource.properties
   - org.wso2.carbon.registry.social
   - org.wso2.carbon.registry.ui.menu.governance
   - org.wso2.carbon.registry.ui.menu
   - org.wso2.carbon.registry.ws

*Tools*

   - org.wso2.carbon.tryit
   - org.wso2.carbon.wsdl.tools

Thanks,

Dileepa
On Wed, May 2, 2012 at 4:26 PM, Chethiya Abeysinghe wrote:

> Hi,
>
> We have changed the p2-repo-gen to generate the repository with category
> information. So you can simply define categories and include appropriate
> features into those categories. Once that repo with category information is
> imported to the feature manger, you can see those defined categories in the
> UI.
>
> To feed in these information, you have to edit the
> carbon/platform/trunk/features/repository/pom.xml file in svn by adding
>  element. An example of such a category is shown below. You can
> include multiple  elements.
>
> 
>  
> org.wso2.carbon.broker.category
>  WSO2 Broker Category
> broker category
>
> 
>   
>org.wso2.carbon.broker
> ${carbon.version}
>   
>
>   
> org.wso2.carbon.brokermanager
>${carbon.version}
>   
>  
>  
> 
>
> Please note that,  and  are required to include a feature to
> a category.  is the same ID used with p2-feature-gen goal of the
> carbon-p2-plugin. You can find that if you look at the pom.xml of any
> particular feature you want.
>
> A sample pom.xml file to reside in repository folder is attached here.
>
> Real pom file has a long list of features and hope people who are managing
> individual features will insert their respective category information also
> to this file.
>
> Thanks,
>
> --
> Chethiya Abeysinghe
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> email: cheth...@wso2.com phone: +94 777444891
> blog: chethiya3000.blogspot.com
>
>
>
> ___
> Dev mailing list
> D

Re: [Dev] Adding proxy services using the UI

[Afkham Azeez]

On Mon, May 7, 2012 at 6:03 PM, Afkham Azeez  wrote:

>
>
> On Mon, May 7, 2012 at 5:11 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, May 7, 2012 at 3:09 PM, Afkham Azeez  wrote:
>>
>>> Folks.,
>>> Any feedback on this? Does this make sense?
>>>
>>
>> I don't think so. We have a very clear separation between named
>> sequences/endpoints and anonymous sequences/endpoints. Anonymous objects
>> are local to a particular proxy service or an API and they are not visible
>> to other services. Sort of like a private method. Named objects on the
>> other hand are visible to everybody, can be shared/reused extensively and
>> do show up in the Synape global namespace. Both have specific, well-defined
>> use cases and I don't see a strong use case for having named sequences
>> inside a proxy or an API.
>>
>
> What about the service chaining scenario? We unnecessarily have to define
> sequences in the global space even though those will be needed only by one
> particular proxy service. Take a look at the example at
> http://blog.afkham.org/2012/05/wso2-esb-service-chaining.html. I had to
> define personInfoSeq & creditSeq at the global level even though I needed
> them only within the proxy service. Is there a way to achieve the same
> thing while keeping everything local (without following the old state
> property based case handling)?
>

In other words, is there a way to set the "receive" attribute of the send
mediator to an anonymous (local to proxy service) sequence?
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding proxy services using the UI

[Afkham Azeez]

On Mon, May 7, 2012 at 5:11 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 7, 2012 at 3:09 PM, Afkham Azeez  wrote:
>
>> Folks.,
>> Any feedback on this? Does this make sense?
>>
>
> I don't think so. We have a very clear separation between named
> sequences/endpoints and anonymous sequences/endpoints. Anonymous objects
> are local to a particular proxy service or an API and they are not visible
> to other services. Sort of like a private method. Named objects on the
> other hand are visible to everybody, can be shared/reused extensively and
> do show up in the Synape global namespace. Both have specific, well-defined
> use cases and I don't see a strong use case for having named sequences
> inside a proxy or an API.
>

What about the service chaining scenario? We unnecessarily have to define
sequences in the global space even though those will be needed only by one
particular proxy service. Take a look at the example at
http://blog.afkham.org/2012/05/wso2-esb-service-chaining.html. I had to
define personInfoSeq & creditSeq at the global level even though I needed
them only within the proxy service. Is there a way to achieve the same
thing while keeping everything local (without following the old state
property based case handling)?


> Thanks,
> Hiranya
>
>
>>
>>
>> On Sun, May 6, 2012 at 3:48 PM, Afkham Azeez  wrote:
>>
>>> I think it will be a good idea to allow defining named sequences inside
>>> proxy services. Otherwise, even if a single proxy service needs use a named
>>> sequence, it has to be defined at a global level, which will cause
>>> unnecessary clutter. Just like the inSequence & outSequence can be defined
>>> inside a proxy service (at a per proxy service level), we should allow
>>> definition of named sequences also inside a proxy service.
>>>
>>>
>>> On Sun, May 6, 2012 at 3:10 PM, Afkham Azeez  wrote:
>>>
 Sorry, my mistake. I have defined the sequence inside the proxy service.


 On Sun, May 6, 2012 at 3:05 PM, Afkham Azeez  wrote:

> I added the attached proxy service which contains 2 named sequences
> using the ESB proxy service UI. However, when I rechecked using edit proxy
> service, both the named sequences had disappeared. Is this a known issue?
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: 
> **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


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


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Senior Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
De

[Dev] Jaggery M4 java.lang.ClassNotFoundException: org.wso2.carbon.hostobjects.email.SenderHostObject

[Ashansa Perera]

Hi,
I got a deployment issue as posted in the mail subjected to "Deployment
issue in jaggery apps". Temporarily I copied the extracted folder to
repository/deployment/server/jaggeryapps/ and tried to access that. That
 is also giving me java.lang.ClassNotFoundException:
org.wso2.carbon.hostobjects.email.SenderHostObject which I do not use in my
app.  (this worked when I tried locally with no such host object in
droppings) I copied the jaggery docs to the same path, but that also ended
up with the same exception.
Any help is appreciated.

This is the full error log
[2012-05-07 08:28:35,004] ERROR
{org.wso2.carbon.scriptengine.util.HostObjectUtil} -  Error while
registering the hostobject :
org.wso2.carbon.hostobjects.email.SenderHostObject
{org.wso2.carbon.scriptengine.util.HostObjectUtil}
java.lang.ClassNotFoundException:
org.wso2.carbon.hostobjects.email.SenderHostObject
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:467)
 at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
 at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
 at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
 at
org.wso2.carbon.scriptengine.util.HostObjectUtil.registerHostObject(HostObjectUtil.java:236)
at
org.wso2.carbon.jaggery.core.modules.ModuleManager.initHostObjects(ModuleManager.java:200)
 at
org.wso2.carbon.jaggery.core.modules.ModuleManager.initModules(ModuleManager.java:87)
at
org.wso2.carbon.jaggery.core.modules.ModuleManager.init(ModuleManager.java:51)
 at
org.wso2.carbon.jaggery.core.modules.ModuleManager.(ModuleManager.java:44)
at
org.wso2.carbon.jaggery.core.manager.CommonManager.init(CommonManager.java:78)
 at
org.wso2.carbon.jaggery.core.manager.CommonManager.(CommonManager.java:54)
at
org.wso2.carbon.jaggery.core.manager.WebAppManager.(WebAppManager.java:44)
 at org.wso2.carbon.jaggery.core.JaggeryServlet.init(JaggeryServlet.java:33)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
 at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:857)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:136)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
 at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:140)
 at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
 at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:50)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
 at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
 at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
[2012-05-07 08:28:35,006] ERROR
{org.wso2.carbon.jaggery.core.modules.ModuleManager} -  Error registering
HostObject. Constructor cannot be found, name : Sender, class :
org.wso2.carbon.hostobjects.email.SenderHostObject
{org.wso2.carbon.jaggery.core.modules.ModuleManager}
[2012-05-07 08:28:35,007] ERROR
{org.wso2.carbon.jaggery.core.JaggeryServlet} -  Error registering
HostObject. Constructor cannot be found, name : Sender, class :
org.wso2.carbon.hostobjects.email.SenderHostObject
{org.wso2.carbon.jaggery.core.JaggeryServlet}
org.wso2.carbon.scriptengine.exceptions.ScriptException: Error registering
HostObject. Constructor cannot be found, name : Sender, class :
org.wso2.carbon.hostobjects.email.SenderHostObject
at
org.wso2.carbon.jaggery.core.modules.ModuleManager.initHostObjects(ModuleManager.java:207)
 at
org.wso2.carbon.jaggery.core.modules.ModuleManager.initModules(ModuleManager.java:87)
at
org.wso2.carbon.jaggery.core.modules.ModuleManager.init(ModuleManager.java:51)
 at
org.wso2.carbon.jaggery.core.modules.ModuleManager.(ModuleManager.java:44)
at
org.wso2.carbon.jaggery.core.manager.CommonManager.init(CommonManage

[Dev] Failed to add features for Carbon server in trunk.

[Lahiru Sandaruwan]

Hi,

I tried to add features to Carbon server in trunk. But it says "No
Available Features." after i clicked find features. I tried adding several
repos(3.2.0, 3.2.2, 3.2.3, 3.2.4, and [1] ) but failed.

I got the svn up and built the 'orbit' and 'kernal'.

Please help.

[1]
http://wso2.org/bamboo/artifact/WSO2CARBON-P2REPO/JOB1/build-77/P2-Repo/p2-repo
Thanks.

-- 
--
Lahiru Sandaruwan
Software Engineer,
Cloud Team,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahi...@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dashboard return a dead page

[Achala Aponso]

Hi,

Recently the shindig version was changed to an older version
(1.1.0.wso2v5).  This issue might be caused due to the current version of
'org.json'. Using an older version of json may solve the issue. Will
further look into this in order to find a proper fix.

Thanks,
Achala

On Mon, May 7, 2012 at 4:53 PM, Achala Aponso  wrote:

> Hi KasunW,
>
> I am looking into this.
>
> Thanks,
> Achala
>
>
> On Mon, May 7, 2012 at 3:11 PM, Kasun Weranga  wrote:
>
>> Hi Achala,
>>
>> Now dashboard is working, but I am getting the following exception when
>> starting the bam.
>>
>> [2012-05-07 15:06:13,552] ERROR
>> {org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent} -
>>  Guice creation errors:
>>
>> 1) Error injecting constructor, org.json.JSONException: A JSONObject text
>> must begin with '{' at character 1
>>   at
>> org.apache.shindig.social.sample.spi.JsonDbOpensocialService.(JsonDbOpensocialService.java:121)
>>   while locating
>> org.apache.shindig.social.sample.spi.JsonDbOpensocialService
>> for field at
>> org.apache.shindig.social.sample.oauth.SampleRealm.jsonDbService(SampleRealm.java:43)
>>
>> 1 error
>> com.google.inject.CreationException: Guice creation errors:
>>
>> 1) Error injecting constructor, org.json.JSONException: A JSONObject text
>> must begin with '{' at character 1
>>   at
>> org.apache.shindig.social.sample.spi.JsonDbOpensocialService.(JsonDbOpensocialService.java:121)
>>   while locating
>> org.apache.shindig.social.sample.spi.JsonDbOpensocialService
>> for field at
>> org.apache.shindig.social.sample.oauth.SampleRealm.jsonDbService(SampleRealm.java:43)
>>
>> 1 error
>> at
>> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:354)
>> at
>> com.google.inject.InjectorBuilder.injectDynamically(InjectorBuilder.java:173)
>>  at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:113)
>> at com.google.inject.Guice.createInjector(Guice.java:92)
>>  at
>> org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent.initShindig(DashboardUiServiceComponent.java:149)
>> at
>> org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent.activate(DashboardUiServiceComponent.java:87)
>>  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:252)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>>  at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
>>  at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>  at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
>> at
>> org.wso2.carbon.ui.internal.CarbonUIServiceComponent.start(CarbonUIServiceComponent.java:300)
>>  at
>> org.wso2.carbon.ui.internal.CarbonUIServiceComponent.activate(CarbonUIServiceComponent.java:121)
>> 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:252)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a

Re: [Dev] Autoscaling with LXCs demo -2

[Afkham Azeez]

Currently all the Tropos related code live under components/tropos. May be
we should move it to a better place in the SVN.

On Mon, May 7, 2012 at 4:32 PM, Sanjiva Weerawarana wrote:

> So is Tropos effectively an IaaS (for autoscaling within a set of worker
> nodes via LXCs) .. if so we should carefully separate Tropos out as a
> separate project. In that case Tropos Controller is fine.
>
> Sanjiva.
>
>
> On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez  wrote:
>
>> Controller might not be the best term to use, but what we discussed was,
>> all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, controller
>> has a special meaning as per the Gartner definition & includes
>> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this
>> Tropos controller will be OK, and there will be no confusion since this is
>> at the IaaS layer.
>>
>>
>> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote:
>>
>>>
>>>
>>> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana wrote:
>>>
 Damitha you guys can't take the name "Stratos Controller" .. that's
 what we're using for the full group of stuff that "controls" Stratos:
 manager, IS, G-Reg, BAM, B&M etc..
>>>
>>>  What we've decided in the last demo meeting was to call this "Tropos
>>> controller" since the Stratos controller is given to above.
>>>

 Please review the slide deck on Stratos scaling and you'll see the
 terms. We used to call that whole thing the manager but that made no sense
 because we have a thing inside called manager too.

 Sanjiva.

 On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote:

> And it was discussed that we should have a controller pack as part of
> the release
>
> Thanks,
> Damitha
>
>
> On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam wrote:
>
>> Further, we will need to investigate as to why it takes more than
>> expected time for the LB to receive the 'Join' message when an app server
>> is started inside a container
>>
>> Also, it was suggested that we should test this with multiple domains
>> (not only AS, but also ESB.. etc)
>>
>> Regarding the introductory presentation, I think its better to add
>> Agent registration part and some of the controller's functionalities
>> (persistence) so that the overall picture gets more clearer.
>>
>>
>> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote:
>>
>>> Hi All,
>>>
>>> Today we had another demo.
>>>
>>> Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera,
>>> Pradeep, Ranga, Lahiru, Sajith and myself.
>>>
>>> First we gave a brief overview of the autoscaling architecture. Then
>>> we started the demo.
>>>
>>> We were able to demo end-end (LB -> Controller --> Agent) scenario
>>> for spawning an instance (through LB sanity check) and termination of an
>>> instance (through scaling down call) within a LXC container.
>>>
>>> Few suggestions came up:
>>>
>>> 1. Create separate carbon instances (rather than using Appservers)
>>> for controller and agent.
>>> 2. Create a simple UI for controller to show instances spawned in
>>> each adapter, instances belong to a particular domain etc.
>>> 3. Fixing the domain related issue in AutoscaleInMediator (This
>>> arose with the changes in loadbalancer.conf to reflect tenant aware load
>>> balancing).
>>> 4. Fixing the routing issue using Azeez's fix to Axis2.
>>> 5. Make scaling up demonstrable using a back-end service which has
>>> some processing (or having a Thread.sleep(..) call).
>>>
>>> Please add anything I've missed!
>>>
>>> PS: We'll repeat the demo next week (hopefully with some more
>>> improvements next week, for Sanjiva, Paul and anyone interested).
>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> __
> Damitha Kumarage
> Technical Leader; WSO2 Inc.
> Oxygenating the Web Service Platform
> http://www.wso2.com/
> blog:
> http://damithakumarage.wordpress.com/
> __
>
> ___
> De

Re: [Dev] How to connect to an external Cassandra Server using Cassandra feature?

[Shelan Perera]

Hi,

You need to set the following system variable and disable server startup.
-Ddisable.cassandra.server.startup=true

Thanks


On Mon, May 7, 2012 at 4:41 PM, Shelan Perera  wrote:

> Hi,
>
> I removed Cassandra Server feature since it starts up the embedded
> cassandra server. And then when i try to list the keyspaces it throws
> followng CNF. Can i disable server starting up using a configuration file?
>
> [2012-05-07 16:38:53,809]  INFO
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  'admin'
> logged in at [2012-05-07 16:38:53,0809] from IP address 10.200.3.152
> [2012-05-07 16:38:55,696] ERROR
> {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
>  org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
> java.lang.NoClassDefFoundError:
> org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
> at
> org.wso2.carbon.cassandra.sharedkey.SharedKeyPublisher.injectAccessKey(SharedKeyPublisher.java:15)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>  at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
>  at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
>  at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>  at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
>  at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:60)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException:
> org.wso2.carbon.cassandra.server.CarbonCassandraAuthenticator
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
>  at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
>  at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>  ... 37 more
> [2012-05-07 16:38:55,711] ERROR
> {org.wso2.carbon.cassandra.mgt.CassandraKeyspaceAdmin} -
>  org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
> org.apache.axis2.AxisFault:
> org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
> at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageCo

Re: [Dev] Do we still use wso2cloud-server.sh script in Stratos Serices?

[Sameera Jayasoma]

Most of the wso2cloud-server.sh files in the stratos services contain
invalid stuff. We need to update them if we are using, or else we can
remove them.

Thanks,
Sameera.

On Mon, May 7, 2012 at 2:34 PM, Sameera Jayasoma  wrote:

> Subject please.
>
> Thanks,
> Sameera.
>
> --
> Sameera Jayasoma
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>



-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

[Dev] Deployment issue in jaggery apps

[Ashansa Perera]

Hi,
I'm trying to add a new jaggery app using the management console, but only
the part of it is copied to repository/deployment/server/jaggeryapps, hence
the app is not working. Is this a known issue or am I missing anything? I
get the following error log [1] in server, but the deployed zip file has
/WEB-INF/web.xml file.

[1]
[2012-05-07 08:03:20,670] ERROR
{org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin} -  Could not unzip the
Jaggery App Archive {org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin}
java.io.FileNotFoundException:
/opt/idtme/servers/wso2appfactory-3.0.0-SNAPSHOT/repository/deployment/server/jaggeryapps/project-mgt-tool/WEB-INF/web.xml
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
 at java.io.FileOutputStream.(FileOutputStream.java:179)
at java.io.FileOutputStream.(FileOutputStream.java:70)
 at
org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin.unZip(JaggeryAppAdmin.java:740)
at
org.wso2.carbon.jaggery.app.mgt.JaggeryAppAdmin.uploadWebapp(JaggeryAppAdmin.java:614)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
 at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
 at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
 at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:140)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
 at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:50)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
 at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2012-05-07 08:03:22,375]  INFO
{org.wso2.carbon.tomcat.internal.CarbonTomcat} -  web application context:
StandardEngine[Catalina].StandardHost[localhost].StandardContext[/project-mgt-tool]
{org.wso2.carbon.tomcat.internal.CarbonTomcat}
[2012-05-07 08:03:22,375]  INFO
{org.wso2.carbon.jaggery.app.mgt.TomcatJaggeryWebappsDeployer} -  Deployed
Jaggery App:
StandardEngine[Catalina].StandardHost[localhost].StandardContext[/project-mgt-tool].File[/opt/idtme/servers/wso2appfactory-3.0.0-SNAPSHOT/repository/deployment/server/jaggeryapps/project-mgt-tool]
{org.wso2.carbon.jaggery.app.mgt.TomcatJaggeryWebappsDeployer}


-- 
Thanks & Regards,

Ashansa Perera
Software Engineer
WSO2, Inc

Re: [Dev] Autoscaling with LXCs demo -2

[Sajith Kariyawasam]

Infact, we are planning to move Tropos controller, LB and hostmachine
related code under one source tree..

For eg,

components/tropos/controller/service/autoscalerservice
components/tropos/controller/service/agentmgtservice
components/tropos/agent
components/tropos/lb

etc ..

Regards
Sajith

On Mon, May 7, 2012 at 4:32 PM, Sanjiva Weerawarana wrote:

> So is Tropos effectively an IaaS (for autoscaling within a set of worker
> nodes via LXCs) .. if so we should carefully separate Tropos out as a
> separate project. In that case Tropos Controller is fine.
>
> Sanjiva.
>
>
> On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez  wrote:
>
>> Controller might not be the best term to use, but what we discussed was,
>> all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, controller
>> has a special meaning as per the Gartner definition & includes
>> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this
>> Tropos controller will be OK, and there will be no confusion since this is
>> at the IaaS layer.
>>
>>
>> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote:
>>
>>>
>>>
>>> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana wrote:
>>>
 Damitha you guys can't take the name "Stratos Controller" .. that's
 what we're using for the full group of stuff that "controls" Stratos:
 manager, IS, G-Reg, BAM, B&M etc..
>>>
>>>  What we've decided in the last demo meeting was to call this "Tropos
>>> controller" since the Stratos controller is given to above.
>>>

 Please review the slide deck on Stratos scaling and you'll see the
 terms. We used to call that whole thing the manager but that made no sense
 because we have a thing inside called manager too.

 Sanjiva.

 On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote:

> And it was discussed that we should have a controller pack as part of
> the release
>
> Thanks,
> Damitha
>
>
> On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam wrote:
>
>> Further, we will need to investigate as to why it takes more than
>> expected time for the LB to receive the 'Join' message when an app server
>> is started inside a container
>>
>> Also, it was suggested that we should test this with multiple domains
>> (not only AS, but also ESB.. etc)
>>
>> Regarding the introductory presentation, I think its better to add
>> Agent registration part and some of the controller's functionalities
>> (persistence) so that the overall picture gets more clearer.
>>
>>
>> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote:
>>
>>> Hi All,
>>>
>>> Today we had another demo.
>>>
>>> Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera,
>>> Pradeep, Ranga, Lahiru, Sajith and myself.
>>>
>>> First we gave a brief overview of the autoscaling architecture. Then
>>> we started the demo.
>>>
>>> We were able to demo end-end (LB -> Controller --> Agent) scenario
>>> for spawning an instance (through LB sanity check) and termination of an
>>> instance (through scaling down call) within a LXC container.
>>>
>>> Few suggestions came up:
>>>
>>> 1. Create separate carbon instances (rather than using Appservers)
>>> for controller and agent.
>>> 2. Create a simple UI for controller to show instances spawned in
>>> each adapter, instances belong to a particular domain etc.
>>> 3. Fixing the domain related issue in AutoscaleInMediator (This
>>> arose with the changes in loadbalancer.conf to reflect tenant aware load
>>> balancing).
>>> 4. Fixing the routing issue using Azeez's fix to Axis2.
>>> 5. Make scaling up demonstrable using a back-end service which has
>>> some processing (or having a Thread.sleep(..) call).
>>>
>>> Please add anything I've missed!
>>>
>>> PS: We'll repeat the demo next week (hopefully with some more
>>> improvements next week, for Sanjiva, Paul and anyone interested).
>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> __
> Damitha Kumarage
> Technical Leader; WSO2 Inc.
> Oxygenating the Web Service Platform
> http://www.wso2.com/
> blog:
> http://d

Re: [Dev] Autoscaling with LXCs demo -2

[Sanjeewa Malalgoda]

Hi,
I have fixed the issue mentioned above (Domain related issue in
AutoscaleInMediator -This arose with the changes in loadbalancer.conf to
reflect tenant aware load balancing) by adding method to get clustering
domain from tenatId and host name.

Thanks.

On Mon, May 7, 2012 at 5:16 PM, Damitha Kumarage  wrote:

>
>
> On Mon, May 7, 2012 at 4:32 PM, Sanjiva Weerawarana wrote:
>
>> So is Tropos effectively an IaaS (for autoscaling within a set of worker
>> nodes via LXCs)
>
> Of course, Tropos autoscale withina set of *Host Machines* via LXCs.
>
> Damitha
>
>> .. if so we should carefully separate Tropos out as a separate project.
>> In that case Tropos Controller is fine.
>>
>> Sanjiva.
>>
>>
>> On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez  wrote:
>>
>>> Controller might not be the best term to use, but what we discussed was,
>>> all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, controller
>>> has a special meaning as per the Gartner definition & includes
>>> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this
>>> Tropos controller will be OK, and there will be no confusion since this is
>>> at the IaaS layer.
>>>
>>>
>>> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote:
>>>


 On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana 
 wrote:

> Damitha you guys can't take the name "Stratos Controller" .. that's
> what we're using for the full group of stuff that "controls" Stratos:
> manager, IS, G-Reg, BAM, B&M etc..

  What we've decided in the last demo meeting was to call this "Tropos
 controller" since the Stratos controller is given to above.

>
> Please review the slide deck on Stratos scaling and you'll see the
> terms. We used to call that whole thing the manager but that made no sense
> because we have a thing inside called manager too.
>
> Sanjiva.
>
> On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote:
>
>> And it was discussed that we should have a controller pack as part of
>> the release
>>
>> Thanks,
>> Damitha
>>
>>
>> On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam 
>> wrote:
>>
>>> Further, we will need to investigate as to why it takes more than
>>> expected time for the LB to receive the 'Join' message when an app 
>>> server
>>> is started inside a container
>>>
>>> Also, it was suggested that we should test this with multiple
>>> domains (not only AS, but also ESB.. etc)
>>>
>>> Regarding the introductory presentation, I think its better to add
>>> Agent registration part and some of the controller's functionalities
>>> (persistence) so that the overall picture gets more clearer.
>>>
>>>
>>> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote:
>>>
 Hi All,

 Today we had another demo.

 Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera,
 Pradeep, Ranga, Lahiru, Sajith and myself.

 First we gave a brief overview of the autoscaling architecture.
 Then we started the demo.

 We were able to demo end-end (LB -> Controller --> Agent) scenario
 for spawning an instance (through LB sanity check) and termination of 
 an
 instance (through scaling down call) within a LXC container.

 Few suggestions came up:

 1. Create separate carbon instances (rather than using Appservers)
 for controller and agent.
 2. Create a simple UI for controller to show instances spawned in
 each adapter, instances belong to a particular domain etc.
 3. Fixing the domain related issue in AutoscaleInMediator (This
 arose with the changes in loadbalancer.conf to reflect tenant aware 
 load
 balancing).
 4. Fixing the routing issue using Azeez's fix to Axis2.
 5. Make scaling up demonstrable using a back-end service which has
 some processing (or having a Thread.sleep(..) call).

 Please add anything I've missed!

 PS: We'll repeat the demo next week (hopefully with some more
 improvements next week, for Sanjiva, Paul and anyone interested).


 --

 Thanks & regards,
 Nirmal

 Software Engineer- Platform Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/

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


>>>
>>>
>>> --
>>> *Sajith Kariyawasam*
>>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/

Re: [Dev] Are we running Bamboo with clean repo?

[Shammi Jayasinghe]

Hi ,
We have clean the repository of bamboo and it is running with a clean repo
now.

Note: Orbit buid #88 is with this clean repo
http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CARBONKERNELBUILD-88/

Thanks
Shammi

On Mon, May 7, 2012 at 2:44 PM, Ranga Siriwardena  wrote:

> Hi Dimuthu,
>
> On Mon, May 7, 2012 at 2:07 PM, Dimuthu Leelarathne wrote:
>
>> Hi Ranga,
>>
>> No we don't. AFAIK, the last time we ran bamboo with clean repo was on
>> the week starting from 23rd April.
>>
>> On Mon, May 7, 2012 at 12:39 PM, Ranga Siriwardena wrote:
>>
>>> Hi,
>>>
>>> $Subject. Found few issues when building with a clean repo.
>>>
>>
>> Did you manage to fix these issues? If so we can start a build on a clean
>> repo.
>>
>
> We were managed to fix LB related issue. Shall we start with a clean repo.
> So we can identify if any issues still there.
>
>
>>
>> thanks,
>> dimuthu
>>
>>
>>> Thank You.
>>> Ranga.
>>>
>>> --
>>> Ranga Siriwardena
>>> Software Engineer
>>> WSO2 Inc.
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Technical Lead
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>>
>> Lean . Enterprise . Middleware
>>
>>
>
> Thank You.
> Ranga.
> --
> Ranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; 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] Autoscaling with LXCs demo -2

[Damitha Kumarage]

On Mon, May 7, 2012 at 4:32 PM, Sanjiva Weerawarana wrote:

> So is Tropos effectively an IaaS (for autoscaling within a set of worker
> nodes via LXCs)

Of course, Tropos autoscale withina set of *Host Machines* via LXCs.

Damitha

> .. if so we should carefully separate Tropos out as a separate project. In
> that case Tropos Controller is fine.
>
> Sanjiva.
>
>
> On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez  wrote:
>
>> Controller might not be the best term to use, but what we discussed was,
>> all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, controller
>> has a special meaning as per the Gartner definition & includes
>> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this
>> Tropos controller will be OK, and there will be no confusion since this is
>> at the IaaS layer.
>>
>>
>> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote:
>>
>>>
>>>
>>> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana wrote:
>>>
 Damitha you guys can't take the name "Stratos Controller" .. that's
 what we're using for the full group of stuff that "controls" Stratos:
 manager, IS, G-Reg, BAM, B&M etc..
>>>
>>>  What we've decided in the last demo meeting was to call this "Tropos
>>> controller" since the Stratos controller is given to above.
>>>

 Please review the slide deck on Stratos scaling and you'll see the
 terms. We used to call that whole thing the manager but that made no sense
 because we have a thing inside called manager too.

 Sanjiva.

 On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote:

> And it was discussed that we should have a controller pack as part of
> the release
>
> Thanks,
> Damitha
>
>
> On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam wrote:
>
>> Further, we will need to investigate as to why it takes more than
>> expected time for the LB to receive the 'Join' message when an app server
>> is started inside a container
>>
>> Also, it was suggested that we should test this with multiple domains
>> (not only AS, but also ESB.. etc)
>>
>> Regarding the introductory presentation, I think its better to add
>> Agent registration part and some of the controller's functionalities
>> (persistence) so that the overall picture gets more clearer.
>>
>>
>> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote:
>>
>>> Hi All,
>>>
>>> Today we had another demo.
>>>
>>> Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera,
>>> Pradeep, Ranga, Lahiru, Sajith and myself.
>>>
>>> First we gave a brief overview of the autoscaling architecture. Then
>>> we started the demo.
>>>
>>> We were able to demo end-end (LB -> Controller --> Agent) scenario
>>> for spawning an instance (through LB sanity check) and termination of an
>>> instance (through scaling down call) within a LXC container.
>>>
>>> Few suggestions came up:
>>>
>>> 1. Create separate carbon instances (rather than using Appservers)
>>> for controller and agent.
>>> 2. Create a simple UI for controller to show instances spawned in
>>> each adapter, instances belong to a particular domain etc.
>>> 3. Fixing the domain related issue in AutoscaleInMediator (This
>>> arose with the changes in loadbalancer.conf to reflect tenant aware load
>>> balancing).
>>> 4. Fixing the routing issue using Azeez's fix to Axis2.
>>> 5. Make scaling up demonstrable using a back-end service which has
>>> some processing (or having a Thread.sleep(..) call).
>>>
>>> Please add anything I've missed!
>>>
>>> PS: We'll repeat the demo next week (hopefully with some more
>>> improvements next week, for Sanjiva, Paul and anyone interested).
>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> __
> Damitha Kumarage
> Technical Leader; WSO2 Inc.
> Oxygenating the Web Service Platform
> http://www.wso2.com/
> blog:
> http://damithakumarage.wordpress.com/
> __
>
> ___
> Dev mailing list
> Dev@wso2.org
> ht

[Dev] [Bamboo-Build] WSO2 Carbon > Orbit > #88 was SUCCESSFUL

[Bamboo]

---
WSO2 Carbon > Orbit > #88 was successful.
---
This build was manually triggered by BambooBuilder.

http://wso2.org/bamboo/browse/WSO2CARBON-CARBONKERNELBUILD-88/



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding proxy services using the UI

[Hiranya Jayathilaka]

On Mon, May 7, 2012 at 3:09 PM, Afkham Azeez  wrote:

> Folks.,
> Any feedback on this? Does this make sense?
>

I don't think so. We have a very clear separation between named
sequences/endpoints and anonymous sequences/endpoints. Anonymous objects
are local to a particular proxy service or an API and they are not visible
to other services. Sort of like a private method. Named objects on the
other hand are visible to everybody, can be shared/reused extensively and
do show up in the Synape global namespace. Both have specific, well-defined
use cases and I don't see a strong use case for having named sequences
inside a proxy or an API.

Thanks,
Hiranya


>
>
> On Sun, May 6, 2012 at 3:48 PM, Afkham Azeez  wrote:
>
>> I think it will be a good idea to allow defining named sequences inside
>> proxy services. Otherwise, even if a single proxy service needs use a named
>> sequence, it has to be defined at a global level, which will cause
>> unnecessary clutter. Just like the inSequence & outSequence can be defined
>> inside a proxy service (at a per proxy service level), we should allow
>> definition of named sequences also inside a proxy service.
>>
>>
>> On Sun, May 6, 2012 at 3:10 PM, Afkham Azeez  wrote:
>>
>>> Sorry, my mistake. I have defined the sequence inside the proxy service.
>>>
>>>
>>> On Sun, May 6, 2012 at 3:05 PM, Afkham Azeez  wrote:
>>>
 I added the attached proxy service which contains 2 named sequences
 using the ESB proxy service UI. However, when I rechecked using edit proxy
 service, both the named sequences had disappeared. Is this a known issue?



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


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


-- 
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dashboard return a dead page

[Achala Aponso]

Hi KasunW,

I am looking into this.

Thanks,
Achala

On Mon, May 7, 2012 at 3:11 PM, Kasun Weranga  wrote:

> Hi Achala,
>
> Now dashboard is working, but I am getting the following exception when
> starting the bam.
>
> [2012-05-07 15:06:13,552] ERROR
> {org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent} -
>  Guice creation errors:
>
> 1) Error injecting constructor, org.json.JSONException: A JSONObject text
> must begin with '{' at character 1
>   at
> org.apache.shindig.social.sample.spi.JsonDbOpensocialService.(JsonDbOpensocialService.java:121)
>   while locating
> org.apache.shindig.social.sample.spi.JsonDbOpensocialService
> for field at
> org.apache.shindig.social.sample.oauth.SampleRealm.jsonDbService(SampleRealm.java:43)
>
> 1 error
> com.google.inject.CreationException: Guice creation errors:
>
> 1) Error injecting constructor, org.json.JSONException: A JSONObject text
> must begin with '{' at character 1
>   at
> org.apache.shindig.social.sample.spi.JsonDbOpensocialService.(JsonDbOpensocialService.java:121)
>   while locating
> org.apache.shindig.social.sample.spi.JsonDbOpensocialService
> for field at
> org.apache.shindig.social.sample.oauth.SampleRealm.jsonDbService(SampleRealm.java:43)
>
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:354)
> at
> com.google.inject.InjectorBuilder.injectDynamically(InjectorBuilder.java:173)
>  at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:113)
> at com.google.inject.Guice.createInjector(Guice.java:92)
>  at
> org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent.initShindig(DashboardUiServiceComponent.java:149)
> at
> org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent.activate(DashboardUiServiceComponent.java:87)
>  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:252)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
>  at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>  at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
> at
> org.wso2.carbon.ui.internal.CarbonUIServiceComponent.start(CarbonUIServiceComponent.java:300)
>  at
> org.wso2.carbon.ui.internal.CarbonUIServiceComponent.activate(CarbonUIServiceComponent.java:121)
> 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:252)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>  at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
> at
> org.eclipse.equinox.in

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #217 has FAILED (1 tests failed). Change made by dileepa.

[Shammi Jayasinghe]

Hi ,

 We manually stopped the build in order to build the complete platform
(orbit,kernel,platform) with a clean repo.

Thanks
Shammi

On Mon, May 7, 2012 at 4:31 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 Carbon›
> Kernel ›
> #217 
> failed
>
> Code has been updated by dileepa
> .
>
> *1/2800* tests failed.
>   Failing 
> Jobs
> Job Duration Tests[image: Failed]  Default 
> Job 
> (Default
> Stage)  104 minutes  1 of 2800 failed  
> Logs|
> Artifacts
>  Code
> Changes
>   View
> full change 
> details
> dileepa 
> fixing https://wso2.org/jira/browse/CARBON-12973 by removing the logic to
> append customWarContext in the redirectURL, so that the web-context will
> not be added twice in the redirectURL  126614 
> Tests
>   View
> full test 
> details
>1
> New Test Failures  Test Job ServerShutdownTestCase 
> testServerShutdown
>   Default
> Job
>  View
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian Bamboo .
>
> If you wish to stop receiving these emails edit your user 
> profileor notify
> your administrator .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,*

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

[Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #217 has FAILED (1 tests failed). Change made by dileepa.

[Bamboo]

---
WSO2 Carbon > Kernel > #217 failed.
---
Code has been updated by dileepa.
1/2800 tests failed.

http://wso2.org/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-217/


--
Failing Jobs
--
  - Default Job (Default Stage): 1 of 2800 tests failed.


--
Code Changes
--
dileepa (126614):

>fixing https://wso2.org/jira/browse/CARBON-12973 by removing the logic to 
>append customWarContext in the redirectURL, so that the web-context will not 
>be added twice in the redirectURL



--
Tests
--
New Test Failures (1)
   - ServerShutdownTestCase: Server shutdown

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while building Manager in trunk.

[Muhammed Shariq]

On Mon, May 7, 2012 at 10:46 AM, Achala Aponso  wrote:

> Hi Shariq,
>
> Seems like this error is not due to your previous fix. When i removed the
> bundleDef also am getting that error in the p2-profile. Will further look
> into this.
>
OK, thanks for verifying. So this issue must have been introduced by some
other commit ...

>
> On Mon, May 7, 2012 at 9:43 AM, Muhammed Shariq  wrote:
>
>> I managed to build both GS and Manager and test the stuff locally, anyway
>> lets have a look when your in office and fix it. Might have to move the
>> google-collect bundleDef to Manager feature perhaps ..
>>
>>
>> On Sun, May 6, 2012 at 12:25 PM, Achala Aponso  wrote:
>>
>>> Hi,
>>>
>>> I took a svn up and tried to build GS. I am getting the following error.
>>>
>>> Installing org.wso2.carbon.admin.mgt.server.feature.group 4.0.0.SNAPSHOT.
>>> Installing org.wso2.carbon.admin.mgt.ui.feature.group 4.0.0.SNAPSHOT.
>>>
>>> Installation failed.
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Registry Social Feature
>>> 4.0.0.SNAPSHOT (org.wso2.carbon.registry.social.feature.group
>>> 4.0.0.SNAPSHOT)
>>>  Missing requirement: WSO2 Carbon - Registry - Social 4.0.0.SNAPSHOT
>>> (org.wso2.carbon.registry.social.api 4.0.0.SNAPSHOT) requires 'package
>>> com.google.common.collect [0.0.0,1.0.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Registry Social Feature 4.0.0.SNAPSHOT
>>> (org.wso2.carbon.registry.social.feature.group 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.registry.social.api [4.0.0.SNAPSHOT]
>>> Application failed, log file location:
>>> /home/achala/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1336286288674.log
>>>
>>> [INFO]
>>> 
>>>
>>>
>>>
>>>
>>>
>>> On Fri, May 4, 2012 at 5:58 PM, Muhammed Shariq  wrote:
>>>
 Hi,

 I have fixed this issue now. Basically changed the dashboard common
 bundle import version to refer to the old google-collect bundle. Also in
 Manager we only use the dashboard server feature, so I had to add
 the google-collect:1.0.0.wso2v2 bundle as a bundleDef in dashboard server
 feature. With this changes in place  I could build Manager and also render
 the gadget portal with no issue. Sorry about the inconvenience though!

 @Achala - Can you please svn up and build components/dashboard and
 features/dashboard and verify that the fix works ?


 On Fri, May 4, 2012 at 2:50 PM, Achala Aponso  wrote:

>
>
> On Fri, May 4, 2012 at 2:28 PM, Muhammed Shariq wrote:
>
>> On Fri, May 4, 2012 at 12:44 PM, Achala Aponso wrote:
>>
>>> Hi,
>>>
>>> The dashboard is not working due to the above commit.
>>>
>> So basically the dashboard component depends on the older version of
>> google-collect? In that case better revert the commit for the moment. It
>> would most certainly break the manager build though.
>>
>
> Yes, dashboard component depends on the older version of
> google-collect. When the google-collect (which is given from guava) is 
> used
> , the dashboard is not working.
>
>
>
>
>>> Thanks,
>>> Achala
>>>
>>> On Fri, Apr 20, 2012 at 5:46 PM, Muhammed Shariq wrote:
>>>
 On Fri, Apr 20, 2012 at 5:43 PM, Nuwan Bandara wrote:

> try building the updated stubs

 Will do!

>
>
> On Fri, Apr 20, 2012 at 5:39 PM, Muhammed Shariq 
> wrote:
>
>> On Fri, Apr 20, 2012 at 5:26 PM, Nuwan Bandara wrote:
>>
>>> Shariq, I think you havent build the whole platform. this is
>>> something after the changes done to activation
>>
>>
>> AFAIK the source is up to date. I updated it last evening as well
>> as in the morning while checking the Manager build issue and have 
>> built
>> upto features. Anyway can you point me to where exactly I need to 
>> update
>> and build, so i can double check ...
>>
>>>
>>>
>>> On Fri, Apr 20, 2012 at 5:07 PM, Muhammed Shariq <
>>> sha...@wso2.com> wrote:
>>>
 I tried building GS but I am getting the following error, looks
 like another osgi import issue? :(

  Cannot complete the install because one or more required
 items could not be found.
  Software being installed: WSO2 Carbon - Gadget Repository
 Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.dashboard.mgt.gadgetrepo.feature.group 
 4.0.0.SNAPSHOT)
  Missing requirement:
 org.wso2.carbon.dashboard.mgt.gadgetrepo.stub 4.0.0.SNAPSHOT
 (org.wso2.carbon.dashboard.mgt.gadget

Re: [Dev] How to connect to an external Cassandra Server using Cassandra feature?

[Shelan Perera]

Hi,

I removed Cassandra Server feature since it starts up the embedded
cassandra server. And then when i try to list the keyspaces it throws
followng CNF. Can i disable server starting up using a configuration file?

[2012-05-07 16:38:53,809]  INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  'admin'
logged in at [2012-05-07 16:38:53,0809] from IP address 10.200.3.152
[2012-05-07 16:38:55,696] ERROR
{org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
 org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
java.lang.NoClassDefFoundError:
org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
at
org.wso2.carbon.cassandra.sharedkey.SharedKeyPublisher.injectAccessKey(SharedKeyPublisher.java:15)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
 at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
 at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
 at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
 at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
 at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:60)
 at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
 at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException:
org.wso2.carbon.cassandra.server.CarbonCassandraAuthenticator
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
 at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
 at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 ... 37 more
[2012-05-07 16:38:55,711] ERROR
{org.wso2.carbon.cassandra.mgt.CassandraKeyspaceAdmin} -
 org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
org.apache.axis2.AxisFault:
org/wso2/carbon/cassandra/server/CarbonCassandraAuthenticator
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
 at
org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
 at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.O

Re: [Dev] Connecting to mysql from Jaggery

[Nuwan Bandara]

Sure will work on it before we publish the site live. since its a API
change better publish the right one from the very first version.

Regards,
/Nuwan

On Mon, May 7, 2012 at 4:29 PM, Sanjiva Weerawarana wrote:

> I think that's ok - and if the choice is between that an exposing Java its
> a no-brainer.
>
> In fact even the PHP world was the same.
>
> Sanjiva.
>
>
> On Mon, May 7, 2012 at 1:46 PM, Nuwan Bandara  wrote:
>
>> Yeah, thats a solution too, then we will have to provide a API for each
>> DB, mysql, oracle, h2 etc
>>
>>
>> On Mon, May 7, 2012 at 1:36 PM, Tharindu Mathew wrote:
>>
>>> Hi,
>>>
>>> We can adjust the API to look something like http://nodejsdb.org/ and
>>> construct the jdbc url in the background.
>>>
>>> Otherwise, we would always be exposing the "java way".
>>>
>>> On Mon, May 7, 2012 at 11:58 AM, Anjana Fernando wrote:
>>>
 Hi,

 On Mon, May 7, 2012 at 7:40 AM, Nuwan Bandara  wrote:

> Hi Sameera,
>
> Right now I am using the default Datasources component for my Database
> API, it mandates to specify the Driver name. which is a limitation in
> tomcat. Anjana will provide  patch so it will accommodate JDBC4 features.
>
> @Anjana please provide more context if I have missed any.
>

 Yeah, as Nuwan said, the jdbc-pool library makes it mandatory to
 provider a driver name, which seems to be wrong, because mainly, they tried
 to keep backward compatibility with DBCP by the same pooling properties and
 all, but they have left out this functionality. I've created an issue here
 [1], the fix is a very trivial one, hopefully it will be fixed soon.

 [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=53198

 Cheers,
 Anjana.


>
> Regards,
> /Nuwan
>
> On Mon, May 7, 2012 at 10:56 AM, Sameera Jayasoma wrote:
>
>> Hi Nuwan,
>>
>> Can you please try putting the JDBC driver to the
>> repository/components/extensions directory? Please clear the drivers in 
>> the
>> lib and dropins first. I've found some links which discussed this issue.
>> This is a typical OSGi world issue. The service provider factory SPI
>> concept in Java does not work in OSGi :)
>>
>> Thanks,
>> Sameera.
>>
>> http://hwellmann.blogspot.com/2009/04/jdbc-drivers-in-osgi.html
>>
>>
>> On Fri, May 4, 2012 at 5:01 PM, Nuwan Bandara  wrote:
>>
>>> Hi
>>>
>>> On Fri, May 4, 2012 at 4:54 PM, Sameera Jayasoma 
>>> wrote:
>>>
 Hi Nuwan,

 How did you fix this? by passing DB driver name?

>>>
>>> Yeah :( had no choice, The driver name is optional in JDBC4, but the
>>> tomcat datasource IMPL has written making it mandatory. Anjana told 
>>> that he
>>> will submit a patch for that. even so, I dont think it will work in our
>>> OSGI environment.
>>>
>>> SO even though its ugly to specify a java class name in a Javascript
>>> API, we got no other option for now.
>>>
>>> Regards,
>>> /Nuwan
>>>
>>>

 Thanks,
 Sameera.


 On Fri, May 4, 2012 at 4:08 PM, Nuwan Bandara wrote:

> Hi Tharindu,
>
> This is now been fixed. the new API is documented in jaggery docs.
>
> Regards,
> /Nuwan
>
>
> On Tue, May 1, 2012 at 7:59 PM, Nuwan Bandara wrote:
>
>> Hi
>>
>> On Tue, May 1, 2012 at 1:02 PM, Tharindu Mathew <
>> thari...@wso2.com> wrote:
>>
>>> Created jira for this: https://wso2.org/jira/browse/JAGGERY-209 (
>>> A blocker IMO)
>>
>>
>> Will look into this.
>>
>>
>>>
>>> Also, how can I set properties of the DB connection such as
>>> maxactive, minidle, timeouts? A minimum set of these should be 
>>> supported by
>>> the API.
>>>
>>
>> You can append the properties to the connection URL.
>>
>>
>>>
>>> Another question is how do I close the connection? I assume
>>> db.query() always opens and closes a DB connection. That is 
>>> inefficient if
>>> I have a number of queries to run.
>>>
>>
>> True, will check on this.
>> https://wso2.org/jira/browse/JAGGERY-210 created.
>>
>> Thanks for the feedback Tharindu
>>
>> Regards,
>> /Nuwan
>>
>>
>>>
>>>
>>> On Tue, May 1, 2012 at 1:42 AM, Tharindu Mathew <
>>> thari...@wso2.com> wrote:
>>>
 Hi,

 Can $subject be done? It reports that the driver is missing. I
 don't see anything in the docs about setting driver class name.

 Note: I added the jdbc driver to repositor

Re: [Dev] Autoscaling with LXCs demo -2

[Sanjiva Weerawarana]

So is Tropos effectively an IaaS (for autoscaling within a set of worker
nodes via LXCs) .. if so we should carefully separate Tropos out as a
separate project. In that case Tropos Controller is fine.

Sanjiva.

On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez  wrote:

> Controller might not be the best term to use, but what we discussed was,
> all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, controller
> has a special meaning as per the Gartner definition & includes
> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this
> Tropos controller will be OK, and there will be no confusion since this is
> at the IaaS layer.
>
>
> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote:
>
>>
>>
>> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana wrote:
>>
>>> Damitha you guys can't take the name "Stratos Controller" .. that's what
>>> we're using for the full group of stuff that "controls" Stratos: manager,
>>> IS, G-Reg, BAM, B&M etc..
>>
>>  What we've decided in the last demo meeting was to call this "Tropos
>> controller" since the Stratos controller is given to above.
>>
>>>
>>> Please review the slide deck on Stratos scaling and you'll see the
>>> terms. We used to call that whole thing the manager but that made no sense
>>> because we have a thing inside called manager too.
>>>
>>> Sanjiva.
>>>
>>> On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote:
>>>
 And it was discussed that we should have a controller pack as part of
 the release

 Thanks,
 Damitha


 On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam wrote:

> Further, we will need to investigate as to why it takes more than
> expected time for the LB to receive the 'Join' message when an app server
> is started inside a container
>
> Also, it was suggested that we should test this with multiple domains
> (not only AS, but also ESB.. etc)
>
> Regarding the introductory presentation, I think its better to add
> Agent registration part and some of the controller's functionalities
> (persistence) so that the overall picture gets more clearer.
>
>
> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote:
>
>> Hi All,
>>
>> Today we had another demo.
>>
>> Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera,
>> Pradeep, Ranga, Lahiru, Sajith and myself.
>>
>> First we gave a brief overview of the autoscaling architecture. Then
>> we started the demo.
>>
>> We were able to demo end-end (LB -> Controller --> Agent) scenario
>> for spawning an instance (through LB sanity check) and termination of an
>> instance (through scaling down call) within a LXC container.
>>
>> Few suggestions came up:
>>
>> 1. Create separate carbon instances (rather than using Appservers)
>> for controller and agent.
>> 2. Create a simple UI for controller to show instances spawned in
>> each adapter, instances belong to a particular domain etc.
>> 3. Fixing the domain related issue in AutoscaleInMediator (This arose
>> with the changes in loadbalancer.conf to reflect tenant aware load
>> balancing).
>> 4. Fixing the routing issue using Azeez's fix to Axis2.
>> 5. Make scaling up demonstrable using a back-end service which has
>> some processing (or having a Thread.sleep(..) call).
>>
>> Please add anything I've missed!
>>
>> PS: We'll repeat the demo next week (hopefully with some more
>> improvements next week, for Sanjiva, Paul and anyone interested).
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sajith Kariyawasam*
> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 __
 Damitha Kumarage
 Technical Leader; WSO2 Inc.
 Oxygenating the Web Service Platform
 http://www.wso2.com/
 blog:
 http://damithakumarage.wordpress.com/
 __

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


>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| +1
>>> 650 265 8311
>>> blog: http://sanjiva.weerawar

[Dev] Jaggery new Dir structure changes are committed to the trunk

[Nuwan Bandara]

Hi All,

I have done the required changes to create the proposed jaggery Directory
structure. Please take an update and build the jaggery product to see the
changes. Would be great if some windows folks try to build and run this.

if there are any error please do report.

-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

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

Re: [Dev] How to connect to an external Cassandra Server using Cassandra feature?

[Kasun Weranga]

Hi Shelan,

You need to have cassandra-component.xml and in their you can specify the
ips and ports of the external Cassandra nodes.

Thanks,
KasunW.

On Mon, May 7, 2012 at 3:07 PM, Shelan Perera  wrote:

> Hi,
>
> If i need to connect to an existing server without starting the embedded
> server in the feature. How can we perform that? What are the configurations
> that i need to add?
>
> Thanks
>
> --
> *Shelan Perera*
>
> Software Engineer
> **
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Home Page*  :shelan.org
> *Blog* : blog.shelan.org
> *Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kasun Weranga*
Software Engineer
**
*WSO2, Inc.
*lean.enterprise.middleware.
mobile : +94 772314602
blog
:
http://kasunweranga.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Chethiya

[Chethiya Abeysinghe]

Hi,

Thanks for making me a committer.  Looking forward to contribute more.

 - Chethiya


On Mon, May 7, 2012 at 3:01 PM, Dimuthu Leelarathne wrote:

> Hi Chethiya,
>
> Congratulations!
>
> It is with great pleasure that we welcome you as a WSO2 committer. Thank
> you for your contributions.
>
> thanks and best regards,
> Dimuthu
>
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>


-- 
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.;  http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dashboard return a dead page

[Kasun Weranga]

Hi Achala,

Now dashboard is working, but I am getting the following exception when
starting the bam.

[2012-05-07 15:06:13,552] ERROR
{org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent} -
 Guice creation errors:

1) Error injecting constructor, org.json.JSONException: A JSONObject text
must begin with '{' at character 1
  at
org.apache.shindig.social.sample.spi.JsonDbOpensocialService.(JsonDbOpensocialService.java:121)
  while locating
org.apache.shindig.social.sample.spi.JsonDbOpensocialService
for field at
org.apache.shindig.social.sample.oauth.SampleRealm.jsonDbService(SampleRealm.java:43)

1 error
com.google.inject.CreationException: Guice creation errors:

1) Error injecting constructor, org.json.JSONException: A JSONObject text
must begin with '{' at character 1
  at
org.apache.shindig.social.sample.spi.JsonDbOpensocialService.(JsonDbOpensocialService.java:121)
  while locating
org.apache.shindig.social.sample.spi.JsonDbOpensocialService
for field at
org.apache.shindig.social.sample.oauth.SampleRealm.jsonDbService(SampleRealm.java:43)

1 error
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:354)
at
com.google.inject.InjectorBuilder.injectDynamically(InjectorBuilder.java:173)
 at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:113)
at com.google.inject.Guice.createInjector(Guice.java:92)
 at
org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent.initShindig(DashboardUiServiceComponent.java:149)
at
org.wso2.carbon.dashboard.ui.internal.DashboardUiServiceComponent.activate(DashboardUiServiceComponent.java:87)
 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:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
 at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
 at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
 at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
 at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
 at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
 at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
 at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
 at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.ui.internal.CarbonUIServiceComponent.start(CarbonUIServiceComponent.java:300)
 at
org.wso2.carbon.ui.internal.CarbonUIServiceComponent.activate(CarbonUIServiceComponent.java:121)
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:252)
 at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
 at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
 at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
 at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
org.eclipse.osgi.framework

Re: [Dev] Adding proxy services using the UI

[Afkham Azeez]

Folks.,
Any feedback on this? Does this make sense?

On Sun, May 6, 2012 at 3:48 PM, Afkham Azeez  wrote:

> I think it will be a good idea to allow defining named sequences inside
> proxy services. Otherwise, even if a single proxy service needs use a named
> sequence, it has to be defined at a global level, which will cause
> unnecessary clutter. Just like the inSequence & outSequence can be defined
> inside a proxy service (at a per proxy service level), we should allow
> definition of named sequences also inside a proxy service.
>
>
> On Sun, May 6, 2012 at 3:10 PM, Afkham Azeez  wrote:
>
>> Sorry, my mistake. I have defined the sequence inside the proxy service.
>>
>>
>> On Sun, May 6, 2012 at 3:05 PM, Afkham Azeez  wrote:
>>
>>> I added the attached proxy service which contains 2 named sequences
>>> using the ESB proxy service UI. However, when I rechecked using edit proxy
>>> service, both the named sequences had disappeared. Is this a known issue?
>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to connect to an external Cassandra Server using Cassandra feature?

[Shelan Perera]

Hi,

If i need to connect to an existing server without starting the embedded
server in the feature. How can we perform that? What are the configurations
that i need to add?

Thanks

-- 
*Shelan Perera*

Software Engineer
**
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Home Page*  :shelan.org
*Blog* : blog.shelan.org
*Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

*Mobile*  : +94 772 604 402
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Chethiya

[Dimuthu Leelarathne]

Hi Chethiya,

Congratulations!

It is with great pleasure that we welcome you as a WSO2 committer. Thank
you for your contributions.

thanks and best regards,
Dimuthu


-- 
Dimuthu Leelarathne
Technical Lead

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

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

Re: [Dev] C4 beta release on 9 th May 2012

[Pradeep Fernando]

Hi,

Subash is looking in to the registry related issues. Altogether there
are 7 issues.

CARBON-12977 Governance collection has gone missing after
restarting ESB cluster nodes
CARBON-12974 G-Reg - Resources/collections added from a mounted
instance, not visible through governance registry instance unless a
new collection is added OR the G-Reg server is restarted
CARBON-12871 Performance improvements related to G-Reg 4.1.1
CARBON-12840 Add comments for configurations in registry.xml
CARBON-12790 ESB - Dead page returned when saving edited WSDLs/Schemas
CARBON-12758 BackwardAssociationHandlerTestCase and WSDLTestCase are failing
CARBON-12658 UDDI not Working after Carbon lib folder restructuring


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

Re: [Dev] Are we running Bamboo with clean repo?

[Ranga Siriwardena]

Hi Dimuthu,

On Mon, May 7, 2012 at 2:07 PM, Dimuthu Leelarathne wrote:

> Hi Ranga,
>
> No we don't. AFAIK, the last time we ran bamboo with clean repo was on the
> week starting from 23rd April.
>
> On Mon, May 7, 2012 at 12:39 PM, Ranga Siriwardena  wrote:
>
>> Hi,
>>
>> $Subject. Found few issues when building with a clean repo.
>>
>
> Did you manage to fix these issues? If so we can start a build on a clean
> repo.
>

We were managed to fix LB related issue. Shall we start with a clean repo.
So we can identify if any issues still there.


>
> thanks,
> dimuthu
>
>
>> Thank You.
>> Ranga.
>>
>> --
>> Ranga Siriwardena
>> Software Engineer
>> WSO2 Inc.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>

Thank You.
Ranga.
-- 
Ranga Siriwardena
Software Engineer
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Compilation errors from Apache-Hive dependency

[Buddhika Chamith]

This happens due to build target folder not being cleaned up properly so
will not happen for first time builders. I have added a clean target now so
it should be fine now.

Regards
Buddhika

On Mon, May 7, 2012 at 12:21 PM, Buddhika Chamith wrote:

> Hi,
>
> Yes I have switched antlr versions used by Hive due to some OSGi issues
> when used with Cassandra. However I fixed this build error due to version
> switch. Can you take a svn up and try?
>
> Regards
> Buddhika
>
>
> On Mon, May 7, 2012 at 11:46 AM, Denis Weerasiri  wrote:
>
>> Hi Buddhika,
>> I'm getting this errors in trunk. Are we using the correct antrl-runtime
>> api?
>>
>> compile:
>>  [echo] Project: ql
>> [javac] Compiling 7 source files to
>> /opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/build/ql/classes
>> [javac]
>> /opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/ql/src/java/org/apache/hadoop/hive/ql/parse/ParseDriver.java:317:
>> recoverFromMismatchedSet(org.antlr.runtime.IntStream,org.antlr.runtime.RecognitionException,org.antlr.runtime.BitSet)
>> in org.apache.hadoop.hive.ql.parse.ParseDriver.HiveParserX cannot override
>> recoverFromMismatchedSet(org.antlr.runtime.IntStream,org.antlr.runtime.RecognitionException,org.antlr.runtime.BitSet)
>> in org.antlr.runtime.BaseRecognizer; attempting to use incompatible return
>> type
>> [javac] found   : java.lang.Object
>> [javac] required: void
>> [javac] public Object recoverFromMismatchedSet(IntStream input,
>> [javac]   ^
>> [javac]
>> /opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/ql/src/java/org/apache/hadoop/hive/ql/parse/ParseDriver.java:316:
>> method does not override or implement a method from a supertype
>> [javac] @Override
>> [javac] ^
>> [javac] 2 errors
>>
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project
>> hive-deploy: An Ant BuildException has occured: The following error
>> occurred while executing this line:
>> [ERROR]
>> /opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/build.xml:297:
>> The following error occurred while executing this line:
>> [ERROR]
>> /opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/build.xml:151:
>> The following error occurred while executing this line:
>> [ERROR]
>> /opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/ql/build.xml:192:
>> Compile failed; see the compiler error output for details.
>> [ERROR] around Ant part ...> antfile="/opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/deploy/../build.xml"
>> target="package">... @ 4:125 in
>> /opt/installations/wso2/trunk/carbon/platform/trunk/dependencies/hive/deploy/target/antrun/build-main.xml
>> [ERROR] -> [Help 1]
>> [ERROR]
>>
>>
>> --
>> Thanks,
>> Denis
>> --
>> *Denis Weerasiri*
>> Senior Software Engineer
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com,
>> *email: denis ** [AT] wso2.com 
>> *
>> *phone: +94117639629
>> *
>> *site: 
>> **https://sites.google.com/site/ddweerasiri/*
>> *blog: **http://ddweerasiri.blogspot.com*
>> *
>> twitter: **http://twitter.com/ddweerasiri*
>> *
>> linked-in: 
>> **http://lk.linkedin.com/in/ddweerasiri*
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Do we still use wso2cloud-server.sh script in Stratos Serices?

[Sameera Jayasoma]

Subject please.

Thanks,
Sameera.

-- 
Sameera Jayasoma
Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

[Dev] [Bamboo-Build] WSO2 Carbon > platform > #169 has FAILED. Change made by nuwanw.

[Bamboo]

---
WSO2 Carbon > platform > #169 failed.
---
Code has been updated by nuwanw.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-169/


--
Failing Jobs
--
  - Default Job (Default Stage): 1340 tests passed.


--
Code Changes
--
nuwanw (126590):

>startMultipleServers() refactored and change boolean statement

nuwanw (126589):

>update login



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Are we running Bamboo with clean repo?

[Dimuthu Leelarathne]

Hi Ranga,

No we don't. AFAIK, the last time we ran bamboo with clean repo was on the
week starting from 23rd April.

On Mon, May 7, 2012 at 12:39 PM, Ranga Siriwardena  wrote:

> Hi,
>
> $Subject. Found few issues when building with a clean repo.
>

Did you manage to fix these issues? If so we can start a build on a clean
repo.

thanks,
dimuthu


> Thank You.
> Ranga.
>
> --
> Ranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dimuthu Leelarathne
Technical Lead

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

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

Re: [Dev] Connecting to mysql from Jaggery

[Nuwan Bandara]

Yeah, thats a solution too, then we will have to provide a API for each DB,
mysql, oracle, h2 etc

On Mon, May 7, 2012 at 1:36 PM, Tharindu Mathew  wrote:

> Hi,
>
> We can adjust the API to look something like http://nodejsdb.org/ and
> construct the jdbc url in the background.
>
> Otherwise, we would always be exposing the "java way".
>
> On Mon, May 7, 2012 at 11:58 AM, Anjana Fernando  wrote:
>
>> Hi,
>>
>> On Mon, May 7, 2012 at 7:40 AM, Nuwan Bandara  wrote:
>>
>>> Hi Sameera,
>>>
>>> Right now I am using the default Datasources component for my Database
>>> API, it mandates to specify the Driver name. which is a limitation in
>>> tomcat. Anjana will provide  patch so it will accommodate JDBC4 features.
>>>
>>> @Anjana please provide more context if I have missed any.
>>>
>>
>> Yeah, as Nuwan said, the jdbc-pool library makes it mandatory to provider
>> a driver name, which seems to be wrong, because mainly, they tried to keep
>> backward compatibility with DBCP by the same pooling properties and all,
>> but they have left out this functionality. I've created an issue here [1],
>> the fix is a very trivial one, hopefully it will be fixed soon.
>>
>> [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=53198
>>
>> Cheers,
>> Anjana.
>>
>>
>>>
>>> Regards,
>>> /Nuwan
>>>
>>> On Mon, May 7, 2012 at 10:56 AM, Sameera Jayasoma wrote:
>>>
 Hi Nuwan,

 Can you please try putting the JDBC driver to the
 repository/components/extensions directory? Please clear the drivers in the
 lib and dropins first. I've found some links which discussed this issue.
 This is a typical OSGi world issue. The service provider factory SPI
 concept in Java does not work in OSGi :)

 Thanks,
 Sameera.

 http://hwellmann.blogspot.com/2009/04/jdbc-drivers-in-osgi.html


 On Fri, May 4, 2012 at 5:01 PM, Nuwan Bandara  wrote:

> Hi
>
> On Fri, May 4, 2012 at 4:54 PM, Sameera Jayasoma wrote:
>
>> Hi Nuwan,
>>
>> How did you fix this? by passing DB driver name?
>>
>
> Yeah :( had no choice, The driver name is optional in JDBC4, but the
> tomcat datasource IMPL has written making it mandatory. Anjana told that 
> he
> will submit a patch for that. even so, I dont think it will work in our
> OSGI environment.
>
> SO even though its ugly to specify a java class name in a Javascript
> API, we got no other option for now.
>
> Regards,
> /Nuwan
>
>
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Fri, May 4, 2012 at 4:08 PM, Nuwan Bandara  wrote:
>>
>>> Hi Tharindu,
>>>
>>> This is now been fixed. the new API is documented in jaggery docs.
>>>
>>> Regards,
>>> /Nuwan
>>>
>>>
>>> On Tue, May 1, 2012 at 7:59 PM, Nuwan Bandara wrote:
>>>
 Hi

 On Tue, May 1, 2012 at 1:02 PM, Tharindu Mathew 
 wrote:

> Created jira for this: https://wso2.org/jira/browse/JAGGERY-209 (
> A blocker IMO)


 Will look into this.


>
> Also, how can I set properties of the DB connection such as
> maxactive, minidle, timeouts? A minimum set of these should be 
> supported by
> the API.
>

 You can append the properties to the connection URL.


>
> Another question is how do I close the connection? I assume
> db.query() always opens and closes a DB connection. That is 
> inefficient if
> I have a number of queries to run.
>

 True, will check on this. https://wso2.org/jira/browse/JAGGERY-210
  created.

 Thanks for the feedback Tharindu

 Regards,
 /Nuwan


>
>
> On Tue, May 1, 2012 at 1:42 AM, Tharindu Mathew  > wrote:
>
>> Hi,
>>
>> Can $subject be done? It reports that the driver is missing. I
>> don't see anything in the docs about setting driver class name.
>>
>> Note: I added the jdbc driver to repository/components/lib as
>> well and checked
>>
>> Stacktrace:
>>
>> [2012-05-01 01:31:36,865] ERROR
>> {org.wso2.carbon.scriptengine.engine.RhinoEngine} -
>>  org.mozilla.javascript.WrappedException: Wrapped
>> org.wso2.carbon.scriptengine.exceptions.ScriptException: Error 
>> connecting
>> to the database : jdbc:mysql://localhost:3306/gadgetgen
>> (/gadgetgen/gadgetgen.jag#11)
>> [2012-05-01 01:31:36,865] ERROR
>> {org.wso2.carbon.jaggery.core.manager.WebAppManager} -
>>  org.mozilla.javascript.WrappedException: Wrapped
>> org.wso2.carbon.scriptengine.exceptions.ScriptException: Error 
>> connecting
>> to the database : jdbc:mysql://localhost

Re: [Dev] Connecting to mysql from Jaggery

[Tharindu Mathew]

Hi,

We can adjust the API to look something like http://nodejsdb.org/ and
construct the jdbc url in the background.

Otherwise, we would always be exposing the "java way".

On Mon, May 7, 2012 at 11:58 AM, Anjana Fernando  wrote:

> Hi,
>
> On Mon, May 7, 2012 at 7:40 AM, Nuwan Bandara  wrote:
>
>> Hi Sameera,
>>
>> Right now I am using the default Datasources component for my Database
>> API, it mandates to specify the Driver name. which is a limitation in
>> tomcat. Anjana will provide  patch so it will accommodate JDBC4 features.
>>
>> @Anjana please provide more context if I have missed any.
>>
>
> Yeah, as Nuwan said, the jdbc-pool library makes it mandatory to provider
> a driver name, which seems to be wrong, because mainly, they tried to keep
> backward compatibility with DBCP by the same pooling properties and all,
> but they have left out this functionality. I've created an issue here [1],
> the fix is a very trivial one, hopefully it will be fixed soon.
>
> [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=53198
>
> Cheers,
> Anjana.
>
>
>>
>> Regards,
>> /Nuwan
>>
>> On Mon, May 7, 2012 at 10:56 AM, Sameera Jayasoma wrote:
>>
>>> Hi Nuwan,
>>>
>>> Can you please try putting the JDBC driver to the
>>> repository/components/extensions directory? Please clear the drivers in the
>>> lib and dropins first. I've found some links which discussed this issue.
>>> This is a typical OSGi world issue. The service provider factory SPI
>>> concept in Java does not work in OSGi :)
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> http://hwellmann.blogspot.com/2009/04/jdbc-drivers-in-osgi.html
>>>
>>>
>>> On Fri, May 4, 2012 at 5:01 PM, Nuwan Bandara  wrote:
>>>
 Hi

 On Fri, May 4, 2012 at 4:54 PM, Sameera Jayasoma wrote:

> Hi Nuwan,
>
> How did you fix this? by passing DB driver name?
>

 Yeah :( had no choice, The driver name is optional in JDBC4, but the
 tomcat datasource IMPL has written making it mandatory. Anjana told that he
 will submit a patch for that. even so, I dont think it will work in our
 OSGI environment.

 SO even though its ugly to specify a java class name in a Javascript
 API, we got no other option for now.

 Regards,
 /Nuwan


>
> Thanks,
> Sameera.
>
>
> On Fri, May 4, 2012 at 4:08 PM, Nuwan Bandara  wrote:
>
>> Hi Tharindu,
>>
>> This is now been fixed. the new API is documented in jaggery docs.
>>
>> Regards,
>> /Nuwan
>>
>>
>> On Tue, May 1, 2012 at 7:59 PM, Nuwan Bandara  wrote:
>>
>>> Hi
>>>
>>> On Tue, May 1, 2012 at 1:02 PM, Tharindu Mathew 
>>> wrote:
>>>
 Created jira for this: https://wso2.org/jira/browse/JAGGERY-209 (
 A blocker IMO)
>>>
>>>
>>> Will look into this.
>>>
>>>

 Also, how can I set properties of the DB connection such as
 maxactive, minidle, timeouts? A minimum set of these should be 
 supported by
 the API.

>>>
>>> You can append the properties to the connection URL.
>>>
>>>

 Another question is how do I close the connection? I assume
 db.query() always opens and closes a DB connection. That is 
 inefficient if
 I have a number of queries to run.

>>>
>>> True, will check on this. https://wso2.org/jira/browse/JAGGERY-210
>>>  created.
>>>
>>> Thanks for the feedback Tharindu
>>>
>>> Regards,
>>> /Nuwan
>>>
>>>


 On Tue, May 1, 2012 at 1:42 AM, Tharindu Mathew 
 wrote:

> Hi,
>
> Can $subject be done? It reports that the driver is missing. I
> don't see anything in the docs about setting driver class name.
>
> Note: I added the jdbc driver to repository/components/lib as well
> and checked
>
> Stacktrace:
>
> [2012-05-01 01:31:36,865] ERROR
> {org.wso2.carbon.scriptengine.engine.RhinoEngine} -
>  org.mozilla.javascript.WrappedException: Wrapped
> org.wso2.carbon.scriptengine.exceptions.ScriptException: Error 
> connecting
> to the database : jdbc:mysql://localhost:3306/gadgetgen
> (/gadgetgen/gadgetgen.jag#11)
> [2012-05-01 01:31:36,865] ERROR
> {org.wso2.carbon.jaggery.core.manager.WebAppManager} -
>  org.mozilla.javascript.WrappedException: Wrapped
> org.wso2.carbon.scriptengine.exceptions.ScriptException: Error 
> connecting
> to the database : jdbc:mysql://localhost:3306/gadgetgen
> (/gadgetgen/gadgetgen.jag#11)
> org.wso2.carbon.scriptengine.exceptions.ScriptException:
> org.mozilla.javascript.WrappedException: Wrapped
> org.wso2.carbon.scriptengine.exceptions.ScriptException: Error 
> connecting
> to the database : jdbc:mysql://localhost

Re: [Dev] Passthru HTTP transport for WSO2 Load Balancer ?

[Hiranya Jayathilaka]

Dushan deployed this in SLive Staging a few months ago. Sanjaya and Dushan
should know the details.

Thanks,
Hiranya

On Mon, May 7, 2012 at 12:55 PM, Afkham Azeez  wrote:

> ESB folks,
> Can we have a response please?
>
>
> On Sat, Apr 28, 2012 at 10:52 AM, Afkham Azeez  wrote:
>
>> Folks,
>> Is the passthru transport stable enough to be integrated with the LB? Can
>> we make it the default? What needs to be done to integrate & enable it in
>> the LB?
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Hadoop download in platform/trunk/dependencies/hive clog the build

[Tharindu Mathew]

Can't cache these on nexus, because this is an ant build. Is there a way to
cache this, so it's accessible in the local network? This would save a lot
of bandwidth, since everyone will be downloading this.

On Mon, May 7, 2012 at 12:06 PM, Tharindu Mathew  wrote:

> Can we cache it locally on nexus? This is an issue with the Hive build,
> and I don't want to spend too much time fixing this.
>
>
> On Mon, May 7, 2012 at 12:03 PM, Sumedha Rubasinghe wrote:
>
>>
>>
>> On Mon, May 7, 2012 at 11:58 AM, Buddhika Chamith wrote:
>>
>>> Hi,
>>>
>>> It will not download these distributions on subsequent builds since it
>>> caches them. I think it is using these different hadoop versions to run
>>> compatibility tests with those hadoop versions. However I will look in to
>>> whether we can make this picked from nexus.
>>>
>>
>> yes.. But this will be a nuisance when everyone start building
>> /sumedha
>>
>>
>>>
>>> Regards
>>> Buddhika
>>>
>>> On Mon, May 7, 2012 at 12:10 PM, Sumedha Rubasinghe wrote:
>>>
 And again.. a different version..

 [ivy:retrieve] downloading
 http://mirror.facebook.net/facebook/hive-deps/hadoop/core/hadoop-0.23.0/hadoop-0.23.0.tar.gz...



 On Mon, May 7, 2012 at 10:39 AM, Sumedha Rubasinghe 
 wrote:

> And, we seem be downloading another version soon after.
> [ivy:retrieve] downloading
> http://mirror.facebook.net/facebook/hive-deps/hadoop/core/hadoop-0.20.3-CDH3-SNAPSHOT/hadoop-0.20.3-CDH3-SNAPSHOT.tar.gz...
>
> Can we use the latest & stop previous download?
>
>
> On Mon, May 7, 2012 at 10:35 AM, Sumedha Rubasinghe 
> wrote:
>
>> Hive build downloads Hadoop from
>> http://mirror.facebook.net/facebook/hive-deps/hadoop/core/hadoop-0.20.1/hadoop-0.20.1.tar.gzand
>>  this is close to 40 mb in size. The link seems to be very slow even
>> accessing from browser URL.
>>
>>
>> --
>> /sumedha
>> +94 773017743
>>
>
>
>
> --
> /sumedha
> +94 773017743
>



 --
 /sumedha
 +94 773017743

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


>>>
>>
>>
>> --
>> /sumedha
>> +94 773017743
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +9459908
>
>


-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Passthru HTTP transport for WSO2 Load Balancer ?

[Afkham Azeez]

ESB folks,
Can we have a response please?

On Sat, Apr 28, 2012 at 10:52 AM, Afkham Azeez  wrote:

> Folks,
> Is the passthru transport stable enough to be integrated with the LB? Can
> we make it the default? What needs to be done to integrate & enable it in
> the LB?
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Are we running Bamboo with clean repo?

[Ranga Siriwardena]

Hi,

$Subject. Found few issues when building with a clean repo.

Thank You.
Ranga.

-- 
Ranga Siriwardena
Software Engineer
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev