[Dev] Equinox Luna will redesign the equinox framework and core compare to equinox kepler

[Shameera Rathnayaka]

Hi devs,

One of our major expectation with new Carbon 5 release is, use new
technologies which will last for another 10 years. Hence we are using newly
released version of equinox which is equinox kepler. But according to
equinox team, with next major release which is equinox Luna , they are
going to redesign the framework and core[1].

As we are planing to provide OSGi level multi-tenancy, which can be
implement with framework hooks going to be completely changed with
suggested framework redesign process. Not only the framework hooks there
are few more areas will be change with Luna release. There are few
limitations plus drawbacks in existing framework implementation. Tom Watson
have explained the background reason for this new redesigning
requirement[2].

If we go with kepler and migrate to Luna once it released , we need to put
the exact same effort again to adopt to new framework changes.

According to me once the Equnox Luna released kepler will be outdated
equinox implantations. I would like to know your thoughts on what is the
best way to deal with this new equinox famework redesign.

[1] http://wiki.eclipse.org/Equinox/Luna_Framework
[2]
http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/EclipseCon%202013%20-%20Equinox_0.pdf




* Thanks, Shameera.Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT apache.org
*
*phone:  +9471 922 1454 <%2B9471%20922%201454>*

*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Message Processor in esb

[Vanjikumaran Sivajothy]

Hi,

Current implementation of Message Processor deactivates after exceeding max
delivery attempts. Therefore, all future messages completely unrelated to
this one will not even get a chance to be delivered.

Do we have any machinesm to over come this?

If not isn't it a good idea to have configuration in message processor to
enable drop the message and continue with rest of the message in message
store!

OR

Since we are promising the guaranteed delivery, configure the message
processor with another store to keep the failed messages after given number
of attempt

What do you think?

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

This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions


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

[Dev] [MAM] Store listing Super Tenant's apps before Sign in

[Pandula Kariyawasam]

Hi All,

MAM Store shares the same Store Home page for both Super Tenant & Tenants
for Sign in. But Store home page listing only Super Tenant's apps. When
there are tenants with their own apps also, Tenant User will see the Super
Tenant's apps in Store home page, before Sign in. There is no place to view
the Tenant's apps to the User before Sign in.

But after Sign in, there's no problem, because everyone see their tenant's
apps only.

This will make them confused. Is this the expected behavior?

Thanks,
Pandula
-- 

*Pandula Kariyawasam K.B.*
*Senior Software Engineer - QA*
Mobile: +94772314510


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

Re: [Dev] Storage Server 1.1.0 is missing the samples folder

[Prabath Abeysekera]

Hi Pulasthi,

Yeah this is something we've intentionally done. In the context of Storage
Server, I'm afraid there wouldn't be instances where we need to ship
standalone samples as it is with ESB, DSS, etc; as it's completely a tool
that provides storage provisioning capabilities. Instead, we have the
sample scenarios, in which people can use SS, documented in the wiki. You
should be able to look around the documentation and get some idea of some
of the patterns available with SS, etc. While you're into it, please note
we're in the process of doing some major improvements to doc contents of SS
these days, so, bare with us for any inconvenience that can possibly be
caused by the aforesaid effort.


Cheers,
Prabath


On Sat, Jan 11, 2014 at 12:21 AM, Pulasthi Supun  wrote:

> Hi All,
>
> It seems that the samples folder is missing from wso2ss-1.1.0 binary files
> that are hosted in the web site. was the samples removed on purpose for
> some reason.
>
> Regards,
> Pulasthi
>
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>



-- 
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [CEP] Execution plan held in inactive state

[Mohanadarshan Vivekanandalingam]

Hi Chamila,

How many event builders do you have?
> In your Execution Plan your are using the input stream as 
> "org.wso2.log_analyzer.netflow.info1"
> , hence you should also have a Event Builder outputting
> org.wso2.log_analyzer.netflow.info1
>
>
+1.. Yes, Please check on that.. I think better if we can have a chat
tomorrow and resolve this..  If there are any documentations lack on this
then we can fix that also..

Thanks,
Mohan



> In your case Event Builder is outputting org.wso2.log_analyzer.out.
> Therefore use org.wso2.log_analyzer.out as the input stream in the
> Execution plan.
>
> Regards
> Suho
>
> On Saturday, January 11, 2014, Chamila Wijayarathna wrote:
>
>> Hi Mohan,
>> Yes I only have the above mentioned execution plan configuration.
>>
>> Event Builder -
>>
>> **
>> *> xmlns="http://wso2.org/carbon/eventbuilder
>> ">*
>> *> eventAdaptorType="wso2event">*
>> *> name="stream">org.wso2.log_analyzer.netflow.info1*
>> *1.0.0*
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>> **
>>
>> org.wso2.log_analyzer.netflow.info1 -
>>
>> StreamDefinition{ streamId='org.wso2.log_analyzer.netflow.info1:1.0.0',
>> name='org.wso2.log_analyzer.netflow.info1', version='1.0.0',
>> nickName='Statistics', description='Service statistics', tags=null,
>> metaData=[Attribute{name='referer', type=STRING}], correlationData=null,
>> payloadData=[Attribute{name='SrcIp', type=STRING}, Attribute{name='DestIp',
>> type=STRING}, Attribute{name='size', type=STRING},
>> Attribute{name='timestamp', type=STRING}], }
>>
>> out1 -
>>
>> StreamDefinition{ streamId='out1:1.0.0', name='out1', version='1.0.0',
>> nickName='', description='', tags=null, metaData=null,
>> correlationData=null, payloadData=[Attribute{name='SrcIp', type=STRING},
>> Attribute{name='DestIp', type=STRING}], }
>>
>> Thank You
>>
>>
>>
>>
>> On Sat, Jan 11, 2014 at 6:37 AM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>> Have you properly removed the invalid configs and tried again..
>> If yes then share the event builder of this config and 
>> org.wso2.log_analyzer.netflow.info1
>> stream definition
>> then we can check what went wrong and let you know..
>>
>> Thanks,
>> Mohan
>>
>>
>> On Sat, Jan 11, 2014 at 12:45 AM, Chamila Wijayarathna 
>> wrote:
>>
>> Hi Mohan,
>> I did the changes you suggested and below is the new configuration.
>>
>> **
>> *> *  trace="disable" xmlns="http://wso2.org/carbon/eventprocessor
>> ">*
>> *  *
>> *  *
>> *> name="siddhi.persistence.snapshot.time.interval.minutes">0*
>> *> name="siddhi.enable.distributed.processing">false*
>> *  *
>> *  *
>> *> version="1.0.0"/>*
>> *  *
>> *  *
>> *  *
>> **
>>
>> But I am still getting the same error. I made the out1 stream using
>> "Create Execution Plan" after writing the query.
>>
>> Thank You.
>> *  *
>> **
>>
>>
>> On Fri, Jan 10, 2014 at 5:49 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>> Hi,
>>
>> On Fri, Jan 10, 2014 at 5:25 PM, Chamila Wijayarathna 
>> wrote:
>>
>> Hello all,
>> I wrote a simple execution plan with following configuration.
>>
>> **
>> *> *  trace="enable" xmlns="http://wso2.org/carbon/eventprocessor
>> ">*
>> *  *
>> *  *
>> *> name="siddhi.persistence.snapshot.time.interval.minutes">0*
>> *> name="siddhi.enable.distributed.processing">false*
>> *  *
>> *  *
>> *> version="1.0.0"/>*
>> *  *
>> *  *
>> <
>>
>>
>
> --
>
> *S. Suhothayan *
> Associate Technical Lead,
>  *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>
>
>


-- 
*V. Mohanadarshan*
*Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] contributing to wso2 carbon on github

[Deependra Ariyadewa]

You can find the WSO2 contributor license agreement in the following
location.

http://wso2.com/licenses


On Sat, Jan 11, 2014 at 8:57 PM, Afkham Azeez  wrote:

> BTW, we also grant committership to external contributors who have been
> contributing to the project over a period of time. You have to sign a
> contributors agreement just like in the ASF. So, please keep your
> contributions coming. As a matter of fact, new WSO2 employees have to go
> through the same process of earning their karma through their
> contributions, and they do not get automatic committership.
>
> Azeez
>
>
> On Sat, Jan 11, 2014 at 7:43 PM, Afkham Azeez  wrote:
>
>>
>>
>>
>> On Sat, Jan 11, 2014 at 3:06 PM, chris snow  wrote:
>>
>>> Hi Afkham,  thanks for the response.
>>>
>>> I'm a fan of the completely open approach taken by wso2 :)
>>>
>>> As for contributions, I think getting feedback to the contributor in a
>>> reasonable time frame is key so that their interest in the project is
>>> maintained.  Whether that feedback is merging the patch, rejecting the
>>> patch, or just adding a comment to the issue.  For opensource contributors
>>> working in their own time, the feedback helps show them that the time they
>>> spend on the project is not wasted, and that they should continue giving
>>> their free time to the project.
>>>
>>
>> Thanks for the suggestions Chris. We will take the response time into
>> serious consideration.
>>
>>>
>>> Many thanks,
>>>
>>> Chris
>>>
>>>
>>> On Sat, Jan 11, 2014 at 5:37 AM, Afkham Azeez  wrote:
>>>
 Thanks Chris for you contributions. WSO2 has always been a truly open
 source company from day 1. We are firm believers in the Apache way, and
 many of us have our roots in the Apache Software Foundation. It is not just
 that he source code is open, but all our technical & architectural
 decisions are made on public mailing lists, and we would love people
 outside WSO2 to engage with us. The Carbon 5 team will merge your requests.
 Looking forward to more contributions from you & other community members.

 Thanks
 Azeez


 On Fri, Jan 10, 2014 at 11:58 PM, chris snow wrote:

> Hi Guys,
>
> Are you accepting outside contributions for carbon on github [1][2]?
>
> Many thanks,
>
> Chris
>
> [1]
> http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-C5-Kernel-codebase-is-now-moved-to-GitHub-td89010.html
> [2] https://github.com/wso2/carbon-kernel
>
> ___
> 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 <%2B94%2077%203320919> blog: *
 *http://blog.afkham.org* 
 *twitter: 
 **http://twitter.com/afkham_azeez*
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 *

 *Lean . Enterprise . Middleware*

>>>
>>>
>>>
>>> --
>>> Check out my professional profile and connect with me on LinkedIn.
>>> http://lnkd.in/cw5k69
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Deependra Ariyadewa
WSO2, Inc. http://wso2.com/ http://wso2.org

email d...@wso2.com; cell +94 71 403 5996 ;
Blog http://risenfall.wordpress.com/
PGP info: KeyID: 'DC627E6F'

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

Re: [Dev] [APIM][IS]Installing XACML features in API Manager

[Nadeesha Gamage]

Great it works, thanks Asela


On Sat, Jan 11, 2014 at 10:21 PM, Asela Pathberiya  wrote:

>
>
>
> On Sat, Jan 11, 2014 at 10:16 AM, Nadeesha Gamage wrote:
>
>> I am having issues when working with XACML features installed in the API
>> Manager. When I create a XACML policy and publish the policy to PDP the
>> policy doesnt take effect. However when the API Manager instance is
>> restarted the policy takes effect.
>>
>> Please let me know whether it is possible to the make the policy to take
>> effect immediately once the policy is promoted to the PDP.
>>
>
> Please check registry.xml. It must be updated with following handler... If
> not, Please add it and see
>
>  class="org.wso2.carbon.identity.entitlement.policy.finder.registry.RegistryPolicyHandler">
>  class="org.wso2.carbon.identity.entitlement.policy.finder.registry.RegistryPolicyMediaTypeMatcher">
>  name="mediaType">application/xacml-policy+xml
> 
> 
>
>  Thanks,
> Asela.
>
>
>>
>> Thank you,
>>
>> --
>> Nadeesha Gamage
>> Senior Engineer Technical Sales
>> +94 77 394 5706
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
> Asela
>
> ATL
> Mobile : +94 777 625 933
>



-- 
Nadeesha Gamage
Senior Engineer Technical Sales
+94 77 394 5706
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Customizing properties of jwt assertion.

[Pushpalanka Jayawardhana]

Thanks, I ll try out that.

Regards,
Pushapalanka


On Sat, Jan 11, 2014 at 1:09 AM, Suresh Attanayaka  wrote:

> If you need to have a new claim, you can define it in the correct claim
> dialect and map it to a LDAP attribute. So then the JWT claims retriever
> will add that to the JWT. For ex, in this case 
> *http://wso2.org/claims/enduserWithoutTenant
>  can be mapped to cn or uid.*
>
>
> On Saturday, January 11, 2014, Pushpalanka Jayawardhana wrote:
>
>> Hi,
>>
>> Is it possible to add a custom property to the JWT assertion as follows.
>>
>> {
>>   "iss":"wso2.org/products/am",
>>   "exp":1389378210204,
>>   "http://wso2.org/claims/subscriber":"admin";,
>>   "http://wso2.org/claims/applicationid":"1";,
>>   "http://wso2.org/claims/applicationname":"DefaultApplication";,
>>   "http://wso2.org/claims/applicationtier":"Unlimited";,
>>   "http://wso2.org/claims/apicontext":"/pizzashack/menu";,
>>   "http://wso2.org/claims/version":"1.0.0";,
>>   "http://wso2.org/claims/tier":"Bronze";,
>>   "http://wso2.org/claims/keytype":"PRODUCTION";,
>>   "http://wso2.org/claims/usertype":"APPLICATION_USER";,
>>   "http://wso2.org/claims/enduser":"admin@carbon.super";,
>>*"http://wso2.org/claims/enduserWithoutTenant
>> ":"admin",*
>>
>>
>
>
> --
> Suresh Attanayake
> Senior Software Engineer; WSO2 Inc. http://wso2.com/
> Blog : http://sureshatt.blogspot.com/
> Web : http://www.ssoarcade.com/
> Facebook : https://www.facebook.com/IdentityWorld
> Twitter : https://twitter.com/sureshatt
> LinkedIn : http://lk.linkedin.com/in/sureshatt
> Mobile : +94755012060
> Mobile : +016166171172
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [CEP] Execution plan held in inactive state

[Sriskandarajah Suhothayan]

How many event builders do you have?
In your Execution Plan your are using the input stream as
"org.wso2.log_analyzer.netflow.info1"
, hence you should also have a Event Builder outputting
org.wso2.log_analyzer.netflow.info1

In your case Event Builder is outputting org.wso2.log_analyzer.out.
Therefore use org.wso2.log_analyzer.out as the input stream in the
Execution plan.

Regards
Suho

On Saturday, January 11, 2014, Chamila Wijayarathna wrote:

> Hi Mohan,
> Yes I only have the above mentioned execution plan configuration.
>
> Event Builder -
>
> **
> * xmlns="http://wso2.org/carbon/eventbuilder
> ">*
> * eventAdaptorType="wso2event">*
> * name="stream">org.wso2.log_analyzer.netflow.info1*
> *1.0.0*
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
> **
>
> org.wso2.log_analyzer.netflow.info1 -
>
> StreamDefinition{ streamId='org.wso2.log_analyzer.netflow.info1:1.0.0',
> name='org.wso2.log_analyzer.netflow.info1', version='1.0.0',
> nickName='Statistics', description='Service statistics', tags=null,
> metaData=[Attribute{name='referer', type=STRING}], correlationData=null,
> payloadData=[Attribute{name='SrcIp', type=STRING}, Attribute{name='DestIp',
> type=STRING}, Attribute{name='size', type=STRING},
> Attribute{name='timestamp', type=STRING}], }
>
> out1 -
>
> StreamDefinition{ streamId='out1:1.0.0', name='out1', version='1.0.0',
> nickName='', description='', tags=null, metaData=null,
> correlationData=null, payloadData=[Attribute{name='SrcIp', type=STRING},
> Attribute{name='DestIp', type=STRING}], }
>
> Thank You
>
>
>
>
> On Sat, Jan 11, 2014 at 6:37 AM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
> Have you properly removed the invalid configs and tried again..
> If yes then share the event builder of this config and 
> org.wso2.log_analyzer.netflow.info1
> stream definition
> then we can check what went wrong and let you know..
>
> Thanks,
> Mohan
>
>
> On Sat, Jan 11, 2014 at 12:45 AM, Chamila Wijayarathna 
> wrote:
>
> Hi Mohan,
> I did the changes you suggested and below is the new configuration.
>
> **
> * *  trace="disable" xmlns="http://wso2.org/carbon/eventprocessor
> ">*
> *  *
> *  *
> * name="siddhi.persistence.snapshot.time.interval.minutes">0*
> * name="siddhi.enable.distributed.processing">false*
> *  *
> *  *
> * version="1.0.0"/>*
> *  *
> *  *
> *  *
> **
>
> But I am still getting the same error. I made the out1 stream using
> "Create Execution Plan" after writing the query.
>
> Thank You.
> *  *
> **
>
>
> On Fri, Jan 10, 2014 at 5:49 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
> Hi,
>
> On Fri, Jan 10, 2014 at 5:25 PM, Chamila Wijayarathna wrote:
>
> Hello all,
> I wrote a simple execution plan with following configuration.
>
> **
> * *  trace="enable" xmlns="http://wso2.org/carbon/eventprocessor
> ">*
> *  *
> *  *
> * name="siddhi.persistence.snapshot.time.interval.minutes">0*
> * name="siddhi.enable.distributed.processing">false*
> *  *
> *  *
> * version="1.0.0"/>*
> *  *
> *  *
> <
>
>

-- 

*S. Suhothayan*
Associate Technical Lead,
 *WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] IllegalStateException while running a load with multiple tenants

[Malaka Silva]

thx noted


On Sat, Jan 11, 2014 at 8:46 AM, Afkham Azeez  wrote:

> This is because of the ThreadLocal CC not being cleaned before being used.
>
> In the handler, please call PrivilegedCarbonContext#destroyCurrentContext
>
> We also need to ensure that this handler is used only when the NHTTP/PT
> transports are used and not used for servlet transport because in the case
> of servlet transport, we correctly set everything in the Tomcat valve.
>
> Azeez
>
>
> On Fri, Jan 10, 2014 at 12:28 PM, Nuwan Silva  wrote:
>
>> The following error was observed when running a simple load test on ESB
>> 4.8.1-M1 pack
>>
>> This was observed in many of the past releases. [1]
>> https://wso2.org/jira/browse/ESBJAVA-2849
>>
>> trace:
>> TID: [0] [ESB] [2014-01-10 12:16:59,748] ERROR
>> {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
>> the domain from shashika.com to 
>> nuwan.com{org.wso2.carbon.context.internal.CarbonContextDataHolder}
>> java.lang.IllegalStateException: Trying to set the domain from
>> shashika.com to nuwan.com
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantDomain(CarbonContextDataHolder.java:1636)
>> at
>> org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:245)
>> at
>> org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:234)
>> at
>> org.wso2.carbon.mediation.initializer.handler.CarbonTenantInfoConfigurator.applyTenantInfo(CarbonTenantInfoConfigurator.java:66)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:201)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processResponse(MultitenantMessageReceiver.java:146)
>> at
>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:81)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>> TID: [0] [ESB] [2014-01-10 12:16:59,750] ERROR
>> {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
>> the domain from 1 to 3
>> {org.wso2.carbon.context.internal.CarbonContextDataHolder}
>> java.lang.IllegalStateException: Trying to set the domain from 1 to 3
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1587)
>> at
>> org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208)
>> at
>> org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197)
>> at
>> org.wso2.carbon.mediation.initializer.handler.CarbonTenantInfoConfigurator.applyTenantInfo(CarbonTenantInfoConfigurator.java:67)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:201)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processResponse(MultitenantMessageReceiver.java:146)
>> at
>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:81)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>>
>> [1]
>> https://wso2.org/jira/browse/APIMANAGER-1912?jql=text%20~%20%22java.lang.IllegalStateException%3A%20Trying%20to%20set%20the%20domain%20from%22
>> Thanks,
>> NuwanS.
>>
>> --
>>
>>
>> *Nuwan Silva*
>> *Senior Software Engineer - QA*
>> Mobile: +94779804543
>>
>> WSO2 Inc.
>> lean . enterprise . middlewear.
>> http://www.wso2.com
>>
>> ___
>> 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

Re: [Dev] [CEP] Execution plan held in inactive state

[Chamila Wijayarathna]

Hi Mohan,
Yes I only have the above mentioned execution plan configuration.

Event Builder -

**
*http://wso2.org/carbon/eventbuilder
">*
**
*org.wso2.log_analyzer.netflow.info1*
*1.0.0*
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
**

org.wso2.log_analyzer.netflow.info1 -

StreamDefinition{ streamId='org.wso2.log_analyzer.netflow.info1:1.0.0',
name='org.wso2.log_analyzer.netflow.info1', version='1.0.0',
nickName='Statistics', description='Service statistics', tags=null,
metaData=[Attribute{name='referer', type=STRING}], correlationData=null,
payloadData=[Attribute{name='SrcIp', type=STRING}, Attribute{name='DestIp',
type=STRING}, Attribute{name='size', type=STRING},
Attribute{name='timestamp', type=STRING}], }

out1 -

StreamDefinition{ streamId='out1:1.0.0', name='out1', version='1.0.0',
nickName='', description='', tags=null, metaData=null,
correlationData=null, payloadData=[Attribute{name='SrcIp', type=STRING},
Attribute{name='DestIp', type=STRING}], }

Thank You




On Sat, Jan 11, 2014 at 6:37 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> Have you properly removed the invalid configs and tried again..
> If yes then share the event builder of this config and 
> org.wso2.log_analyzer.netflow.info1
> stream definition
> then we can check what went wrong and let you know..
>
> Thanks,
> Mohan
>
>
> On Sat, Jan 11, 2014 at 12:45 AM, Chamila Wijayarathna 
> wrote:
>
>> Hi Mohan,
>> I did the changes you suggested and below is the new configuration.
>>
>> **
>> *> *  trace="disable" xmlns="http://wso2.org/carbon/eventprocessor
>> ">*
>> *  *
>> *  *
>> *> name="siddhi.persistence.snapshot.time.interval.minutes">0*
>> *> name="siddhi.enable.distributed.processing">false*
>> *  *
>> *  *
>> *> version="1.0.0"/>*
>> *  *
>> *  *
>> *  *
>> **
>>
>> But I am still getting the same error. I made the out1 stream using
>> "Create Execution Plan" after writing the query.
>>
>> Thank You.
>> *  *
>> **
>>
>>
>> On Fri, Jan 10, 2014 at 5:49 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> On Fri, Jan 10, 2014 at 5:25 PM, Chamila Wijayarathna 
>>> wrote:
>>>
 Hello all,
 I wrote a simple execution plan with following configuration.

 **
 *>>> *  trace="enable" xmlns="http://wso2.org/carbon/eventprocessor
 ">*
 *  *
 *  *
 *>>> name="siddhi.persistence.snapshot.time.interval.minutes">0*
 *>>> name="siddhi.enable.distributed.processing">false*
 *  *
 *  *
 *>>> version="1.0.0"/>*
 *  *
 *  *
 *  *
 *>>> *  passthroughFlow="enable" valueOf="out" version="1.0.0"/>*
 *  *
 **

 When I deployed this execution plan, it went to inactive state and says
 as reason "[Dependency: org.wso2.log_analyzer.netflow.info1:1.0.0]". I
 have "org.wso2.log_analyzer.netflow.info1" event stream added already.
 What is the reason for it to held in inactive state?

>>>
>>> There is a config issue in the executionPlan, we are able to fix that
>>> after an offline chat..
>>> This due to unavailability of proper output stream..
>>>
>>> Thanks,
>>> Mohan
>>>
>>>
 Thank You!
 --
 *Chamila Wijayarathna*
 Engineering Intern,
 WSO2 Inc.


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


>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Software Engineer,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>> *Chamila Wijayarathna*
>> Engineering Intern,
>> WSO2 Inc.
>>
>>
>
>
> --
> *V. Mohanadarshan*
> *Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
*Chamila Wijayarathna*
Engineering Intern,
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM][IS]Installing XACML features in API Manager

[Asela Pathberiya]

On Sat, Jan 11, 2014 at 10:16 AM, Nadeesha Gamage  wrote:

> I am having issues when working with XACML features installed in the API
> Manager. When I create a XACML policy and publish the policy to PDP the
> policy doesnt take effect. However when the API Manager instance is
> restarted the policy takes effect.
>
> Please let me know whether it is possible to the make the policy to take
> effect immediately once the policy is promoted to the PDP.
>

Please check registry.xml. It must be updated with following handler... If
not, Please add it and see



application/xacml-policy+xml



 Thanks,
Asela.


>
> Thank you,
>
> --
> Nadeesha Gamage
> Senior Engineer Technical Sales
> +94 77 394 5706
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Asela

ATL
Mobile : +94 777 625 933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] contributing to wso2 carbon on github

[Afkham Azeez]

BTW, we also grant committership to external contributors who have been
contributing to the project over a period of time. You have to sign a
contributors agreement just like in the ASF. So, please keep your
contributions coming. As a matter of fact, new WSO2 employees have to go
through the same process of earning their karma through their
contributions, and they do not get automatic committership.

Azeez


On Sat, Jan 11, 2014 at 7:43 PM, Afkham Azeez  wrote:

>
>
>
> On Sat, Jan 11, 2014 at 3:06 PM, chris snow  wrote:
>
>> Hi Afkham,  thanks for the response.
>>
>> I'm a fan of the completely open approach taken by wso2 :)
>>
>> As for contributions, I think getting feedback to the contributor in a
>> reasonable time frame is key so that their interest in the project is
>> maintained.  Whether that feedback is merging the patch, rejecting the
>> patch, or just adding a comment to the issue.  For opensource contributors
>> working in their own time, the feedback helps show them that the time they
>> spend on the project is not wasted, and that they should continue giving
>> their free time to the project.
>>
>
> Thanks for the suggestions Chris. We will take the response time into
> serious consideration.
>
>>
>> Many thanks,
>>
>> Chris
>>
>>
>> On Sat, Jan 11, 2014 at 5:37 AM, Afkham Azeez  wrote:
>>
>>> Thanks Chris for you contributions. WSO2 has always been a truly open
>>> source company from day 1. We are firm believers in the Apache way, and
>>> many of us have our roots in the Apache Software Foundation. It is not just
>>> that he source code is open, but all our technical & architectural
>>> decisions are made on public mailing lists, and we would love people
>>> outside WSO2 to engage with us. The Carbon 5 team will merge your requests.
>>> Looking forward to more contributions from you & other community members.
>>>
>>> Thanks
>>> Azeez
>>>
>>>
>>> On Fri, Jan 10, 2014 at 11:58 PM, chris snow wrote:
>>>
 Hi Guys,

 Are you accepting outside contributions for carbon on github [1][2]?

 Many thanks,

 Chris

 [1]
 http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-C5-Kernel-codebase-is-now-moved-to-GitHub-td89010.html
 [2] https://github.com/wso2/carbon-kernel

 ___
 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 <%2B94%2077%203320919> blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: 
>>> **http://twitter.com/afkham_azeez*
>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> Check out my professional profile and connect with me on LinkedIn.
>> http://lnkd.in/cw5k69
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



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

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

Re: [Dev] contributing to wso2 carbon on github

[Kishanthan Thangarajah]

Hi Chris,

Thank you for your interest and contribution to WSO2.

We have reviewed your pull request at :
https://github.com/wso2/carbon-kernel/pull/5. You can continue with that,
based on the feedback given there.

Thanks,
Kishanthan.


On Sat, Jan 11, 2014 at 3:06 PM, chris snow  wrote:

> Hi Afkham,  thanks for the response.
>
> I'm a fan of the completely open approach taken by wso2 :)
>
> As for contributions, I think getting feedback to the contributor in a
> reasonable time frame is key so that their interest in the project is
> maintained.  Whether that feedback is merging the patch, rejecting the
> patch, or just adding a comment to the issue.  For opensource contributors
> working in their own time, the feedback helps show them that the time they
> spend on the project is not wasted, and that they should continue giving
> their free time to the project.
>
> Many thanks,
>
> Chris
>
>
> On Sat, Jan 11, 2014 at 5:37 AM, Afkham Azeez  wrote:
>
>> Thanks Chris for you contributions. WSO2 has always been a truly open
>> source company from day 1. We are firm believers in the Apache way, and
>> many of us have our roots in the Apache Software Foundation. It is not just
>> that he source code is open, but all our technical & architectural
>> decisions are made on public mailing lists, and we would love people
>> outside WSO2 to engage with us. The Carbon 5 team will merge your requests.
>> Looking forward to more contributions from you & other community members.
>>
>> Thanks
>> Azeez
>>
>>
>> On Fri, Jan 10, 2014 at 11:58 PM, chris snow  wrote:
>>
>>> Hi Guys,
>>>
>>> Are you accepting outside contributions for carbon on github [1][2]?
>>>
>>> Many thanks,
>>>
>>> Chris
>>>
>>> [1]
>>> http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-C5-Kernel-codebase-is-now-moved-to-GitHub-td89010.html
>>> [2] https://github.com/wso2/carbon-kernel
>>>
>>> ___
>>> 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 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] contributing to wso2 carbon on github

[Afkham Azeez]

On Sat, Jan 11, 2014 at 3:06 PM, chris snow  wrote:

> Hi Afkham,  thanks for the response.
>
> I'm a fan of the completely open approach taken by wso2 :)
>
> As for contributions, I think getting feedback to the contributor in a
> reasonable time frame is key so that their interest in the project is
> maintained.  Whether that feedback is merging the patch, rejecting the
> patch, or just adding a comment to the issue.  For opensource contributors
> working in their own time, the feedback helps show them that the time they
> spend on the project is not wasted, and that they should continue giving
> their free time to the project.
>

Thanks for the suggestions Chris. We will take the response time into
serious consideration.

>
> Many thanks,
>
> Chris
>
>
> On Sat, Jan 11, 2014 at 5:37 AM, Afkham Azeez  wrote:
>
>> Thanks Chris for you contributions. WSO2 has always been a truly open
>> source company from day 1. We are firm believers in the Apache way, and
>> many of us have our roots in the Apache Software Foundation. It is not just
>> that he source code is open, but all our technical & architectural
>> decisions are made on public mailing lists, and we would love people
>> outside WSO2 to engage with us. The Carbon 5 team will merge your requests.
>> Looking forward to more contributions from you & other community members.
>>
>> Thanks
>> Azeez
>>
>>
>> On Fri, Jan 10, 2014 at 11:58 PM, chris snow  wrote:
>>
>>> Hi Guys,
>>>
>>> Are you accepting outside contributions for carbon on github [1][2]?
>>>
>>> Many thanks,
>>>
>>> Chris
>>>
>>> [1]
>>> http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-C5-Kernel-codebase-is-now-moved-to-GitHub-td89010.html
>>> [2] https://github.com/wso2/carbon-kernel
>>>
>>> ___
>>> 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 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>



-- 
*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] contributing to wso2 carbon on github

[chris snow]

Hi Afkham,  thanks for the response.

I'm a fan of the completely open approach taken by wso2 :)

As for contributions, I think getting feedback to the contributor in a
reasonable time frame is key so that their interest in the project is
maintained.  Whether that feedback is merging the patch, rejecting the
patch, or just adding a comment to the issue.  For opensource contributors
working in their own time, the feedback helps show them that the time they
spend on the project is not wasted, and that they should continue giving
their free time to the project.

Many thanks,

Chris


On Sat, Jan 11, 2014 at 5:37 AM, Afkham Azeez  wrote:

> Thanks Chris for you contributions. WSO2 has always been a truly open
> source company from day 1. We are firm believers in the Apache way, and
> many of us have our roots in the Apache Software Foundation. It is not just
> that he source code is open, but all our technical & architectural
> decisions are made on public mailing lists, and we would love people
> outside WSO2 to engage with us. The Carbon 5 team will merge your requests.
> Looking forward to more contributions from you & other community members.
>
> Thanks
> Azeez
>
>
> On Fri, Jan 10, 2014 at 11:58 PM, chris snow  wrote:
>
>> Hi Guys,
>>
>> Are you accepting outside contributions for carbon on github [1][2]?
>>
>> Many thanks,
>>
>> Chris
>>
>> [1]
>> http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-C5-Kernel-codebase-is-now-moved-to-GitHub-td89010.html
>> [2] https://github.com/wso2/carbon-kernel
>>
>> ___
>> 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 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] how to automate provisioning a feature from the WSO2 p2 repository?

[chris snow]

Many thanks, Afkham!


On Sat, Jan 11, 2014 at 5:48 AM, Afkham Azeez  wrote:

> Sorry, I lost part of the mail when I pasted this section.
>
> This is something we have discussed on the list in the past I believe. The
> way to make the feature installation repeatable is to use the
> carbon-p2-plugin. Look in the pom.xml file of any WSO2 product (under the
> module/p2-profile-gen section)
>
>
> On Sat, Jan 11, 2014 at 11:16 AM, Afkham Azeez  wrote:
>
>> 
>> org.wso2.maven
>> carbon-p2-plugin
>> ${carbon.p2.plugin.version}
>> 
>> 
>> 2-p2-repo-generation
>> package
>> 
>> p2-repo-gen
>> 
>> 
>>
>> file:${basedir}/target/p2-repo
>>
>> file:${basedir}/target/p2-repo
>> true
>>
>> true
>> 
>> 
>>
>> org.wso2.carbon:org.wso2.carbon.core.feature:${carbon.kernel.version}
>> 
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev