Re: [Carbon-dev] GS version in carbon 3.0.1 branch

[Tyrell Perera]

On Fri, Aug 27, 2010 at 12:03 PM, Samisa Abeysinghe  wrote:

>
>
> On Fri, Aug 27, 2010 at 11:58 AM, Tyrell Perera  wrote:
>
>> That is correct 1.2.0 will be our next version, which will have OAuth
>> support and Customisable Themes along with other fixes. This justifies this
>> version number.
>>
>
> This is a mere patch release. So it has to be 1.1.1 I think.
>
> We are not adding any features, are we? If not it is not correct to
> increase minor number. Rather we should only increase patch number.
>

We are adding features as I wrote.

  1. OAuth support and Admin UI
  2. Teming support and Admin UI


Tyrell




>
>
>>
>> The release targeted towards the end of this year will have much more
>> features such as OpenSocial (which is a huge addition), Customisable JSON
>> layouts and possible SAML based auth for gadgets. We are also looking at
>> enhancing the Gadget Directory user experience as well. These mandate a
>> 2.0.0 version number for that release.
>>
>>
>> Tyrell
>>
>>
>>
>>
>> On Fri, Aug 27, 2010 at 11:44 AM, Asela Pathberiya wrote:
>>
>>> Hi Tyrell,
>>>
>>> What should be the version of GS in 3.0.1 branch (last released version
>>> was 1.1.0 with Carbon 3.0.0) ? In svn of 3.0.1 branch, it is 1.2.0.
>>>
>>> Thanks,
>>> Asela.
>>>
>>>
>>>
>>
>>
>> --
>> Tyrell Perera
>> Product Manager - WSO2 Mashup Server, WSO2 Gadget Server
>>
>> WSO2, Inc.; http://www.wso2.com/
>> "Lean Enterprise Middleware"
>>
>> http://www.tyrell.co
>> http://www.linkedin.com/in/tyrell
>> http://twitter.com/tyrellperera
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Tyrell Perera
Product Manager - WSO2 Mashup Server, WSO2 Gadget Server

WSO2, Inc.; http://www.wso2.com/
"Lean Enterprise Middleware"

http://www.tyrell.co
http://www.linkedin.com/in/tyrell
http://twitter.com/tyrellperera
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] GS version in carbon 3.0.1 branch

[Samisa Abeysinghe]

On Fri, Aug 27, 2010 at 11:58 AM, Tyrell Perera  wrote:

> That is correct 1.2.0 will be our next version, which will have OAuth
> support and Customisable Themes along with other fixes. This justifies this
> version number.
>

This is a mere patch release. So it has to be 1.1.1 I think.

We are not adding any features, are we? If not it is not correct to increase
minor number. Rather we should only increase patch number.


>
> The release targeted towards the end of this year will have much more
> features such as OpenSocial (which is a huge addition), Customisable JSON
> layouts and possible SAML based auth for gadgets. We are also looking at
> enhancing the Gadget Directory user experience as well. These mandate a
> 2.0.0 version number for that release.
>
>
> Tyrell
>
>
>
>
> On Fri, Aug 27, 2010 at 11:44 AM, Asela Pathberiya  wrote:
>
>> Hi Tyrell,
>>
>> What should be the version of GS in 3.0.1 branch (last released version
>> was 1.1.0 with Carbon 3.0.0) ? In svn of 3.0.1 branch, it is 1.2.0.
>>
>> Thanks,
>> Asela.
>>
>>
>>
>
>
> --
> Tyrell Perera
> Product Manager - WSO2 Mashup Server, WSO2 Gadget Server
>
> WSO2, Inc.; http://www.wso2.com/
> "Lean Enterprise Middleware"
>
> http://www.tyrell.co
> http://www.linkedin.com/in/tyrell
> http://twitter.com/tyrellperera
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

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

Re: [Carbon-dev] GS version in carbon 3.0.1 branch

[Tyrell Perera]

That is correct 1.2.0 will be our next version, which will have OAuth
support and Customisable Themes along with other fixes. This justifies this
version number.

The release targeted towards the end of this year will have much more
features such as OpenSocial (which is a huge addition), Customisable JSON
layouts and possible SAML based auth for gadgets. We are also looking at
enhancing the Gadget Directory user experience as well. These mandate a
2.0.0 version number for that release.


Tyrell



On Fri, Aug 27, 2010 at 11:44 AM, Asela Pathberiya  wrote:

> Hi Tyrell,
>
> What should be the version of GS in 3.0.1 branch (last released version
> was 1.1.0 with Carbon 3.0.0) ? In svn of 3.0.1 branch, it is 1.2.0.
>
> Thanks,
> Asela.
>
>
>


-- 
Tyrell Perera
Product Manager - WSO2 Mashup Server, WSO2 Gadget Server

WSO2, Inc.; http://www.wso2.com/
"Lean Enterprise Middleware"

http://www.tyrell.co
http://www.linkedin.com/in/tyrell
http://twitter.com/tyrellperera
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] GS version in carbon 3.0.1 branch

[Asela Pathberiya]

Hi Tyrell,

What should be the version of GS in 3.0.1 branch (last released version was
1.1.0 with Carbon 3.0.0) ? In svn of 3.0.1 branch, it is 1.2.0.

Thanks,
Asela.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] How to add the register function into the WSAS?

[Prabath Siriwardana]

Sorry, I missed the link

[1]:
http://blog.facilelogin.com/2010/05/managing-users-and-roles-with-wso2.html

Thanks & regards;
-Prabath

2010/8/27 Prabath Siriwardana prab...@wso2.com

> Not quite sure about the requirement.. Are you planning to add users via
> the service API ? and manage those users - if so [1] will be helpful.
>
> Thanks & regards;
> -Prabath
>
> 2010/8/27 dzh045 dzh...@163.com
>
>>   Hi:
>> Now  I  want to  add  the   register  function   into  the  WSAS.
>>  Then   I  canuse  this  function  to   register  an new  account ,so
>>   I  can   use   the   account  newly  registered  to   sign in  the
>> WSAS.
>>
>> How  to  add  ?
>> Thanks!
>>
>>
>>
>>
>> --
>> 您想拥有和网易免费邮箱一样强大的软件吗？ 
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath Siriwardena
>
> http://blog.facilelogin.com
> http://RampartFAQ.com 
>



-- 
Thanks & Regards,
Prabath Siriwardena

http://blog.facilelogin.com
http://RampartFAQ.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Module versioning in Carbon

[Isuru Suriarachchi]

On Fri, Aug 27, 2010 at 10:51 AM, Isuru Suriarachchi  wrote:

>
>
> On Fri, Aug 27, 2010 at 10:32 AM, Ruwan Linton  wrote:
>
>>  On 8/27/10 10:17 AM, Isuru Suriarachchi wrote:
>>
>>
>>
>> On Thu, Aug 26, 2010 at 8:53 PM, Ruwan Linton  wrote:
>>
>>>  On 8/26/10 3:47 PM, Isuru Suriarachchi wrote:
>>>
>>> Hi all,
>>>
>>> I've noticed that the version for an Axis2 module which comes through an
>>> OSGi bundle is calculated form the bundle version. But for most of the
>>> module bundles in carbon, bundle version is equal to the carbon version.
>>> Therefore module versions are same as Carbon version.
>>>
>>> Ex: In trunk,
>>>
>>> addressing - 3.10-SNAPSHOT
>>> throttling - 3.10-SNAPSHOT
>>> caching - 3.10-SNAPSHOT
>>>
>>> But I think this is wrong. The module version should be the original
>>> module version. Ex: addressing 1.6-SNAPSHOT.
>>>
>>> This problems doesn't exist for modules which comes through orbit bundles
>>> (Ex : rampart). That is because in orbit, we have used the original version
>>> instead of Carbon version.
>>>
>>> So I think the cleaner solution for this is to have orbit bundles for all
>>> external sources. For example, addressing module should come from axis2
>>> orbit bundle, throttling module should come from an orbit bundle which wraps
>>> commons/throttling etc..
>>>
>>> WDYT??
>>>
>>>  Regarding throttling and caching, they have to be moved to the
>>> respective component itself. Basically it is pointless to have a caching
>>> library which is not OSGi in WSO2 svn and then have an orbit bundle to
>>> convert it to caching-orbit and then use that in the component. Instead we
>>> should move that code into the component itself. Let the version of that to
>>> be the component version.
>>>
>>
>> If we move those into components, those modules will be supported only
>> through OSGi. But there may be users who want to use the throttling/caching
>> modules with Axis2. So where are we going to maintain the mar maven modules?
>>
>> Good question, but not sure whether it is a valid question, do we know of
>> some one who uses caching or throttling without one of the WSO2 products. We
>> shouldn't try to solve a non existing problem.
>>
>
> I also haven't heard about such users :). But theoretically, it's a valid
> use case. Caching/throttling are basically Axis2 modules. So I think those
> should have a .mar version as well.
>

And also this applies to xfer and mex modules as well. Those are standard
specifications. So those should have .mar versions.

Thanks,
~Isuru


>
> Thanks,
> ~Isuru
>
>
>>
>> Ruwan
>>
>>
>>
>>>
>>> For addressing +1 for adding it to orbit.
>>>
>>
>> It should be the same for sandesha as well.
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>> Ruwan
>>>
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>> --
>>> Isuru Suriarachchi
>>> Technical Lead & Product Manager, WSO2 Web Services Application Server
>>> WSO2 Inc. http://wso2.com
>>> email : is...@wso2.com
>>> blog : http://isurues.wordpress.com/
>>>
>>> lean . enterprise . middleware
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> carbon-...@wso2.orghttps://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>>
>>> --
>>> Ruwan Linton
>>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>>
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> phone: +1 408 754 7388 ext 51789
>>> email: ru...@wso2.com; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>>
>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>> tweet: http://twitter.com/ruwanlinton
>>>
>>>
>>
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead & Product Manager, WSO2 Web Services Application Server
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.com
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> tweet: http://twitter.com/ruwanlinton
>>
>>
>
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Web Services Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>


-- 
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] How to add the register function into the WSAS?

[Prabath Siriwardana]

Not quite sure about the requirement.. Are you planning to add users via the
service API ? and manage those users - if so [1] will be helpful.

Thanks & regards;
-Prabath

2010/8/27 dzh045 dzh...@163.com

> Hi:
> Now  I  want to  add  the   register  function   into  the  WSAS.  Then
>   I  canuse  this  function  to   register  an new  account ,so
>   I  can   use   the   account  newly  registered  to   sign in  the WSAS.
>
> How  to  add  ?
> Thanks!
>
>
>
>
> --
> 您想拥有和网易免费邮箱一样强大的软件吗？ 
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks & Regards,
Prabath Siriwardena

http://blog.facilelogin.com
http://RampartFAQ.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Module versioning in Carbon

[Isuru Suriarachchi]

On Fri, Aug 27, 2010 at 10:32 AM, Ruwan Linton  wrote:

>  On 8/27/10 10:17 AM, Isuru Suriarachchi wrote:
>
>
>
> On Thu, Aug 26, 2010 at 8:53 PM, Ruwan Linton  wrote:
>
>>  On 8/26/10 3:47 PM, Isuru Suriarachchi wrote:
>>
>> Hi all,
>>
>> I've noticed that the version for an Axis2 module which comes through an
>> OSGi bundle is calculated form the bundle version. But for most of the
>> module bundles in carbon, bundle version is equal to the carbon version.
>> Therefore module versions are same as Carbon version.
>>
>> Ex: In trunk,
>>
>> addressing - 3.10-SNAPSHOT
>> throttling - 3.10-SNAPSHOT
>> caching - 3.10-SNAPSHOT
>>
>> But I think this is wrong. The module version should be the original
>> module version. Ex: addressing 1.6-SNAPSHOT.
>>
>> This problems doesn't exist for modules which comes through orbit bundles
>> (Ex : rampart). That is because in orbit, we have used the original version
>> instead of Carbon version.
>>
>> So I think the cleaner solution for this is to have orbit bundles for all
>> external sources. For example, addressing module should come from axis2
>> orbit bundle, throttling module should come from an orbit bundle which wraps
>> commons/throttling etc..
>>
>> WDYT??
>>
>>  Regarding throttling and caching, they have to be moved to the respective
>> component itself. Basically it is pointless to have a caching library which
>> is not OSGi in WSO2 svn and then have an orbit bundle to convert it to
>> caching-orbit and then use that in the component. Instead we should move
>> that code into the component itself. Let the version of that to be the
>> component version.
>>
>
> If we move those into components, those modules will be supported only
> through OSGi. But there may be users who want to use the throttling/caching
> modules with Axis2. So where are we going to maintain the mar maven modules?
>
> Good question, but not sure whether it is a valid question, do we know of
> some one who uses caching or throttling without one of the WSO2 products. We
> shouldn't try to solve a non existing problem.
>

I also haven't heard about such users :). But theoretically, it's a valid
use case. Caching/throttling are basically Axis2 modules. So I think those
should have a .mar version as well.

Thanks,
~Isuru


>
> Ruwan
>
>
>
>>
>> For addressing +1 for adding it to orbit.
>>
>
> It should be the same for sandesha as well.
>
> Thanks,
> ~Isuru
>
>
>>
>> Ruwan
>>
>>
>> Thanks,
>> ~Isuru
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead & Product Manager, WSO2 Web Services Application Server
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> carbon-...@wso2.orghttps://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>
>> WSO2 Inc.; http://wso2.com
>>
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>>
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> tweet: http://twitter.com/ruwanlinton
>>
>>
>
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Web Services Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.com
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> tweet: http://twitter.com/ruwanlinton
>
>


-- 
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] How to add the register function into the WSAS?

[dzh045]

Hi:
Now  I  want to  add  the   register  function   into  the  WSAS.  Then   I 
 canuse  this  function  to   register  an new  account ,so
  I  can   use   the   account  newly  registered  to   sign in  the WSAS.

How  to  add  ?
Thanks!
 

___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Module versioning in Carbon

[Ruwan Linton]

 On 8/27/10 10:17 AM, Isuru Suriarachchi wrote:



On Thu, Aug 26, 2010 at 8:53 PM, Ruwan Linton > wrote:


On 8/26/10 3:47 PM, Isuru Suriarachchi wrote:

Hi all,

I've noticed that the version for an Axis2 module which comes
through an OSGi bundle is calculated form the bundle version. But
for most of the module bundles in carbon, bundle version is equal
to the carbon version. Therefore module versions are same as
Carbon version.

Ex: In trunk,

addressing - 3.10-SNAPSHOT
throttling - 3.10-SNAPSHOT
caching - 3.10-SNAPSHOT

But I think this is wrong. The module version should be the
original module version. Ex: addressing 1.6-SNAPSHOT.

This problems doesn't exist for modules which comes through orbit
bundles (Ex : rampart). That is because in orbit, we have used
the original version instead of Carbon version.

So I think the cleaner solution for this is to have orbit bundles
for all external sources. For example, addressing module should
come from axis2 orbit bundle, throttling module should come from
an orbit bundle which wraps commons/throttling etc..

WDYT??

Regarding throttling and caching, they have to be moved to the
respective component itself. Basically it is pointless to have a
caching library which is not OSGi in WSO2 svn and then have an
orbit bundle to convert it to caching-orbit and then use that in
the component. Instead we should move that code into the component
itself. Let the version of that to be the component version.


If we move those into components, those modules will be supported only 
through OSGi. But there may be users who want to use the 
throttling/caching modules with Axis2. So where are we going to 
maintain the mar maven modules?
Good question, but not sure whether it is a valid question, do we know 
of some one who uses caching or throttling without one of the WSO2 
products. We shouldn't try to solve a non existing problem.


Ruwan



For addressing +1 for adding it to orbit.


It should be the same for sandesha as well.

Thanks,
~Isuru


Ruwan


Thanks,
~Isuru

-- 
Isuru Suriarachchi

Technical Lead & Product Manager, WSO2 Web Services Application
Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com 
blog : http://isurues.wordpress.com/

lean . enterprise . middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org 
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev



-- Ruwan Linton Software Architect & Product Manager, WSO2 ESB;
http://wso2.org/esb
WSO2 Inc.; http://wso2.com


Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email:ru...@wso2.com  ; cell: +94 77 341 3097
blog:http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton tweet:
http://twitter.com/ruwanlinton




--
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com 
blog : http://isurues.wordpress.com/

lean . enterprise . middleware




--
Ruwan Linton
Software Architect&  Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton

___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Module versioning in Carbon

[Isuru Suriarachchi]

On Thu, Aug 26, 2010 at 8:53 PM, Ruwan Linton  wrote:

>  On 8/26/10 3:47 PM, Isuru Suriarachchi wrote:
>
> Hi all,
>
> I've noticed that the version for an Axis2 module which comes through an
> OSGi bundle is calculated form the bundle version. But for most of the
> module bundles in carbon, bundle version is equal to the carbon version.
> Therefore module versions are same as Carbon version.
>
> Ex: In trunk,
>
> addressing - 3.10-SNAPSHOT
> throttling - 3.10-SNAPSHOT
> caching - 3.10-SNAPSHOT
>
> But I think this is wrong. The module version should be the original module
> version. Ex: addressing 1.6-SNAPSHOT.
>
> This problems doesn't exist for modules which comes through orbit bundles
> (Ex : rampart). That is because in orbit, we have used the original version
> instead of Carbon version.
>
> So I think the cleaner solution for this is to have orbit bundles for all
> external sources. For example, addressing module should come from axis2
> orbit bundle, throttling module should come from an orbit bundle which wraps
> commons/throttling etc..
>
> WDYT??
>
> Regarding throttling and caching, they have to be moved to the respective
> component itself. Basically it is pointless to have a caching library which
> is not OSGi in WSO2 svn and then have an orbit bundle to convert it to
> caching-orbit and then use that in the component. Instead we should move
> that code into the component itself. Let the version of that to be the
> component version.
>

If we move those into components, those modules will be supported only
through OSGi. But there may be users who want to use the throttling/caching
modules with Axis2. So where are we going to maintain the mar maven modules?


>
> For addressing +1 for adding it to orbit.
>

It should be the same for sandesha as well.

Thanks,
~Isuru


>
> Ruwan
>
>
> Thanks,
> ~Isuru
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Web Services Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
> ___
> Carbon-dev mailing list
> carbon-...@wso2.orghttps://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>
> WSO2 Inc.; http://wso2.com
>
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> linkedin: http://www.linkedin.com/in/ruwanlinton
> tweet: http://twitter.com/ruwanlinton
>
>


-- 
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Fresh build on windows fails with ODE build

[Milinda Pathirage]

Hi Ruwan,

ode-bpel-dao dependency is there in ode-dao-hibernate module and we changed
the group id to org.wso2.bpel because we want to avoid version collisions.

Thanks
Milinda

On Thu, Aug 26, 2010 at 8:56 PM, Ruwan Linton  wrote:

>  On 8/26/10 4:38 PM, Samisa Abeysinghe wrote:
>
> hmmm OK. I can build dependencies one by one. Does anyone know how to fix
> maven to do the right thing?
>
> Seems like the build order went wrong, can you check whether
> ode-dao-hibernate module has a dependency to the ode-bpel-dao? Anyway why is
> this org.wso2.bpel group id?
>
> Ruwan
>
>
> On Thu, Aug 26, 2010 at 4:29 PM, Milinda Pathirage wrote:
>
>> Looks like a issue with Axis2 transports build. dependencies/transports
>> should be build before building ODE. We have came across these kind of
>> issues with Maven where maven didn't build dependency projects first. Can
>> you try to build dependencies/transports first and then build ODE.
>>
>>  Thanks
>> Milinda
>>
>>  On Thu, Aug 26, 2010 at 2:22 PM, Samisa Abeysinghe wrote:
>>
>>>  I am trying to build the default profile for dependencies, and I get
>>> the following errors:
>>>
>>>  [ERROR] BUILD ERROR
>>> [INFO]
>>> 
>>> [INFO] Failed to resolve artifact.
>>>
>>>  Missing:
>>> --
>>> 1) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>>>
>>>Try downloading the file manually from the project website.
>>>
>>>Then, install it using the command:
>>>   mvn install:install-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>Alternatively, if you host your own repository you can deploy the
>>> file there:
>>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -Drepo
>>> sitoryId=[id]
>>>
>>>Path to dependency:
>>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>>>
>>>  2) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>>>
>>>Try downloading the file manually from the project website.
>>>
>>>Then, install it using the command:
>>>   mvn install:install-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>Alternatively, if you host your own repository you can deploy the
>>> file there:
>>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -Drepo
>>> sitoryId=[id]
>>>
>>>Path to dependency:
>>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>>> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>>>
>>>  3) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT
>>>
>>>Try downloading the file manually from the project website.
>>>
>>>Then, install it using the command:
>>>   mvn install:install-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>Alternatively, if you host your own repository you can deploy the
>>> file there:
>>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -Dreposit
>>> oryId=[id]
>>>
>>>Path to dependency:
>>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>>> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>>> 4) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT
>>>
>>>  4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT
>>>
>>>Try downloading the file manually from the project website.
>>>
>>>Then, install it using the command:
>>>   mvn install:install-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file
>>>
>>>Alternatively, if you host your own repository you can deploy the
>>> file there:
>>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>>> -Dfile=/path/to/file -Durl=[url] -D
>>> repositoryId=[id]
>>>
>>>Path to dependency:
>>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>>> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>>> 4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT
>>>
>>>  5) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT
>>>
>>>Try downloading the file manually from the project website.
>>>
>>>Then, install it using the command:
>>>   mvn install:install-file -DgroupId=org.wso2.bpel
>>> -DartifactId=ode-bpel-obj -Dversion=1.3.5-SNAPSH

Re: [Carbon-dev] Fresh build on windows fails with ODE build

[Ruwan Linton]

 On 8/26/10 4:38 PM, Samisa Abeysinghe wrote:
hmmm OK. I can build dependencies one by one. Does anyone know how to 
fix maven to do the right thing?
Seems like the build order went wrong, can you check whether 
ode-dao-hibernate module has a dependency to the ode-bpel-dao? Anyway 
why is this org.wso2.bpel group id?


Ruwan


On Thu, Aug 26, 2010 at 4:29 PM, Milinda Pathirage > wrote:


Looks like a issue with Axis2 transports build.
dependencies/transports should be build before building ODE. We
have came across these kind of issues with Maven where maven
didn't build dependency projects first. Can you try to build
dependencies/transports first and then build ODE.

Thanks
Milinda

On Thu, Aug 26, 2010 at 2:22 PM, Samisa Abeysinghe
mailto:sam...@wso2.com>> wrote:

I am trying to build the default profile for dependencies, and
I get the following errors:

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can
deploy the file there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepo
sitoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT

2) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can
deploy the file there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepo
sitoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT

3) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can
deploy the file there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Dreposit
oryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
4) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT

4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can
deploy the file there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -D
repositoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT

5) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-obj 

Re: [Carbon-dev] Module versioning in Carbon

[Ruwan Linton]

 On 8/26/10 3:47 PM, Isuru Suriarachchi wrote:

Hi all,

I've noticed that the version for an Axis2 module which comes through 
an OSGi bundle is calculated form the bundle version. But for most of 
the module bundles in carbon, bundle version is equal to the carbon 
version. Therefore module versions are same as Carbon version.


Ex: In trunk,

addressing - 3.10-SNAPSHOT
throttling - 3.10-SNAPSHOT
caching - 3.10-SNAPSHOT

But I think this is wrong. The module version should be the original 
module version. Ex: addressing 1.6-SNAPSHOT.


This problems doesn't exist for modules which comes through orbit 
bundles (Ex : rampart). That is because in orbit, we have used the 
original version instead of Carbon version.


So I think the cleaner solution for this is to have orbit bundles for 
all external sources. For example, addressing module should come from 
axis2 orbit bundle, throttling module should come from an orbit bundle 
which wraps commons/throttling etc..


WDYT??
Regarding throttling and caching, they have to be moved to the 
respective component itself. Basically it is pointless to have a caching 
library which is not OSGi in WSO2 svn and then have an orbit bundle to 
convert it to caching-orbit and then use that in the component. Instead 
we should move that code into the component itself. Let the version of 
that to be the component version.


For addressing +1 for adding it to orbit.

Ruwan


Thanks,
~Isuru

--
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com 
blog : http://isurues.wordpress.com/

lean . enterprise . middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev



--
Ruwan Linton
Software Architect&  Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton

___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] synapse-commons:jar missing

[Ruwan Linton]

 On 8/26/10 2:20 PM, Samisa Abeysinghe wrote:

What should be the version?

It has to be 2.0.0-SNAPSHOT.

The billing dependency synapse version has to be changed to this.

Ruwan


On Thu, Aug 26, 2010 at 1:17 PM, Senaka Fernando > wrote:


Hi Samisa,

On Thu, Aug 26, 2010 at 12:55 PM, Samisa Abeysinghe
mailto:sam...@wso2.com>> wrote:

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT


I think the version is wrong.

Thanks,
Senaka.


 Try downloading the file manually from the project website.

 Then, install it using the command:
 mvn install:install-file -DgroupId=org.apache.synapse
-DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file

 Alternatively, if you host your own repository you can deploy
the file there:
 mvn deploy:deploy-file -DgroupId=org.apache.synapse
-DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

 Path to dependency:
   1)
org.wso2.stratos:org.wso2.stratos.billing.mgt:bundle:1.0.0-SNAPSHOT
   2)
org.wso2.carbon:org.wso2.carbon.billing.core:jar:3.1.0-SNAPSHOT
   3) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org


___
Carbon-dev mailing list
Carbon-dev@wso2.org 
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev




-- 
Senaka Fernando

Associate Technical Lead
WSO2 Inc.
E-mail: senaka AT wso2.com ;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"

___
Carbon-dev mailing list
Carbon-dev@wso2.org 
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org



___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev



--
Ruwan Linton
Software Architect&  Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton

___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Build Failure in Dashboard BE in Carbon 3.0.1 branch

[Nuwan Bandara]

Hi Asela,

It should be fixed now :) sorry for the trouble. I have missed to commit a
property in components root pom

Regards
/Nuwan

On Thu, Aug 26, 2010 at 4:31 PM, Asela Pathberiya  wrote:

> Hi,
>
> Following compilation error, building
> components/dashboard/org.wso2.carbon.dashboard.
>
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
>
> /home/carbon/carbon-3.0.0/carbon/components/dashboard/org.wso2.carbon.dashboard/3.0.2/src/main/java/org/wso2/carbon/dashboard/deployer/GadgetDeployer.java:[196,34]
> cannot find symbol
> symbol  : method formatPath(java.lang.String)
> location: class org.wso2.carbon.application.deployer.AppDeployerUtils
>
> /home/carbon/carbon-3.0.0/carbon/components/dashboard/org.wso2.carbon.dashboard/3.0.2/src/main/java/org/wso2/carbon/dashboard/deployer/GadgetDeployer.java:[198,48]
> APP_UNZIP_DIR has private access in
> org.wso2.carbon.application.deployer.AppDeployerUtils
>
> Thanks,
> Asela.
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Nuwan Bandara
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware

http://www.nuwanbando.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] BAM data publishers broken

[ratha]

Fixed..
sorry for the inconvenience..
Thanks.
-Ratha.
Samisa Abeysinghe wrote:
> [INFO] Compiling 10 source files to 
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/target/classes
> [INFO] 
> 
> [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[32,52]
>  
> cannot find symbol
> symbol  : class Counter
> location: package org.wso2.carbon.bam.data.publishers.activity
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/modules/ActivityIDHandler.java:[43,52]
>  
> cannot find symbol
> symbol  : class Counter
> location: package org.wso2.carbon.bam.data.publishers.activity
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[163,33]
>  
> cannot find symbol
> symbol  : class Counter
> location: class 
> org.wso2.carbon.bam.data.publishers.activity.PublisherUtils
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[164,30]
>  
> cannot find symbol
> symbol  : class Counter
> location: class 
> org.wso2.carbon.bam.data.publishers.activity.PublisherUtils
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[174,14]
>  
> cannot find symbol
> symbol  : class Counter
> location: class 
> org.wso2.carbon.bam.data.publishers.activity.PublisherUtils
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[175,35]
>  
> cannot find symbol
> symbol  : class Counter
> location: class 
> org.wso2.carbon.bam.data.publishers.activity.PublisherUtils
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[192,12]
>  
> cannot find symbol
> symbol  : class Counter
> location: class 
> org.wso2.carbon.bam.data.publishers.activity.PublisherUtils
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[192,41]
>  
> cannot find symbol
> symbol  : class Counter
> location: class 
> org.wso2.carbon.bam.data.publishers.activity.PublisherUtils
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/modules/ActivityIDHandler.java:[184,49]
>  
> cannot find symbol
> symbol  : class Counter
> location: class 
> org.wso2.carbon.bam.data.publishers.activity.modules.ActivityIDHandler
>
> /home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/modules/ActivityIDHandler.java:[185,34]
>  
> cannot find symbol
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc. 
> http://wso2.com
> http://wso2.org
>
>  
>
> 
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] BAM data publishers broken

[Samisa Abeysinghe]

[INFO] Compiling 10 source files to
/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/target/classes
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Compilation failure

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[32,52]
cannot find symbol
symbol  : class Counter
location: package org.wso2.carbon.bam.data.publishers.activity

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/modules/ActivityIDHandler.java:[43,52]
cannot find symbol
symbol  : class Counter
location: package org.wso2.carbon.bam.data.publishers.activity

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[163,33]
cannot find symbol
symbol  : class Counter
location: class org.wso2.carbon.bam.data.publishers.activity.PublisherUtils

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[164,30]
cannot find symbol
symbol  : class Counter
location: class org.wso2.carbon.bam.data.publishers.activity.PublisherUtils

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[174,14]
cannot find symbol
symbol  : class Counter
location: class org.wso2.carbon.bam.data.publishers.activity.PublisherUtils

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[175,35]
cannot find symbol
symbol  : class Counter
location: class org.wso2.carbon.bam.data.publishers.activity.PublisherUtils

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[192,12]
cannot find symbol
symbol  : class Counter
location: class org.wso2.carbon.bam.data.publishers.activity.PublisherUtils

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/PublisherUtils.java:[192,41]
cannot find symbol
symbol  : class Counter
location: class org.wso2.carbon.bam.data.publishers.activity.PublisherUtils

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/modules/ActivityIDHandler.java:[184,49]
cannot find symbol
symbol  : class Counter
location: class
org.wso2.carbon.bam.data.publishers.activity.modules.ActivityIDHandler

/home/stratos/build/carbon/components/bam-data-publishers/org.wso2.carbon.bam.data.publishers.activity/src/main/java/org/wso2/carbon/bam/data/publishers/activity/modules/ActivityIDHandler.java:[185,34]
cannot find symbol

Thanks,
Samisa...

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

Re: [Carbon-dev] Carbon 3.0.1 Alpha3 build

[Asela Pathberiya]

On Thu, Aug 26, 2010 at 1:37 PM, Asela Pathberiya  wrote:

> Hi all,
>
> Please find the 3.0.1 alpha3 build of ESB,WSAS,GREG and IS here[1].
>

Please find BPS build from same location.


>
> [1]http://builder.wso2.org/~carbon/releases/carbon/3.0.1/Alpha3/
>
> Thanks,
> Asela.
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Error on BPS startup in 3.0.1 branch

[Waruna Ranasinghe]

On Thu, Aug 26, 2010 at 2:18 PM, Asela Pathberiya  wrote:

> Hi Waruna,
>
> I getting following, Please have a look.
>
Fixed.


Thanks,
Waruna


>
> org.osgi.framework.BundleException: The bundle could not be resolved.
> Reason: Missing Constraint: Import-Package: javax.annotation.processing;
> version="0.0.0"
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
> at
> org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
> at
> org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
> at
> org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
> at
> org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
> at
> org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
>
> Thanks,
> Asela.
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
-
Waruna Ranasinghe
Senior Software Engineer, WSO2

Mobile: +94 724 318285
BLOG: http://warunapw.blogspot.com

www.wso2.com - "Lean . Enterprise . Middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Fresh build on windows fails with ODE build

[Samisa Abeysinghe]

hmmm OK. I can build dependencies one by one. Does anyone know how to fix
maven to do the right thing?

On Thu, Aug 26, 2010 at 4:29 PM, Milinda Pathirage  wrote:

> Looks like a issue with Axis2 transports build. dependencies/transports
> should be build before building ODE. We have came across these kind of
> issues with Maven where maven didn't build dependency projects first. Can
> you try to build dependencies/transports first and then build ODE.
>
> Thanks
> Milinda
>
> On Thu, Aug 26, 2010 at 2:22 PM, Samisa Abeysinghe wrote:
>
>> I am trying to build the default profile for dependencies, and I get the
>> following errors:
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> --
>> 1) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>   mvn install:install-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>   Alternatively, if you host your own repository you can deploy the file
>> there:
>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -Drepo
>> sitoryId=[id]
>>
>>   Path to dependency:
>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>>
>> 2) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>   mvn install:install-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>   Alternatively, if you host your own repository you can deploy the file
>> there:
>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -Drepo
>> sitoryId=[id]
>>
>>   Path to dependency:
>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>>
>> 3) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>   mvn install:install-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>   Alternatively, if you host your own repository you can deploy the file
>> there:
>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -Dreposit
>> oryId=[id]
>>
>>   Path to dependency:
>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>> 4) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT
>>
>> 4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>   mvn install:install-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>   Alternatively, if you host your own repository you can deploy the file
>> there:
>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -D
>> repositoryId=[id]
>>
>>   Path to dependency:
>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>> 4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT
>>
>> 5) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>   mvn install:install-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-obj -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>   Alternatively, if you host your own repository you can deploy the file
>> there:
>>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
>> -DartifactId=ode-bpel-obj -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -Drepo
>> sitoryId=[id]
>>
>>   Path to dependency:
>> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
>> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>> 4) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT
>>
>> 6) org.wso2.bpel:ode

[Carbon-dev] Build Failure in Dashboard BE in Carbon 3.0.1 branch

[Asela Pathberiya]

Hi,

Following compilation error, building
components/dashboard/org.wso2.carbon.dashboard.

[ERROR] BUILD FAILURE
[INFO]

[INFO] Compilation failure

/home/carbon/carbon-3.0.0/carbon/components/dashboard/org.wso2.carbon.dashboard/3.0.2/src/main/java/org/wso2/carbon/dashboard/deployer/GadgetDeployer.java:[196,34]
cannot find symbol
symbol  : method formatPath(java.lang.String)
location: class org.wso2.carbon.application.deployer.AppDeployerUtils

/home/carbon/carbon-3.0.0/carbon/components/dashboard/org.wso2.carbon.dashboard/3.0.2/src/main/java/org/wso2/carbon/dashboard/deployer/GadgetDeployer.java:[198,48]
APP_UNZIP_DIR has private access in
org.wso2.carbon.application.deployer.AppDeployerUtils

Thanks,
Asela.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Fresh build on windows fails with ODE build

[Milinda Pathirage]

Looks like a issue with Axis2 transports build. dependencies/transports
should be build before building ODE. We have came across these kind of
issues with Maven where maven didn't build dependency projects first. Can
you try to build dependencies/transports first and then build ODE.

Thanks
Milinda

On Thu, Aug 26, 2010 at 2:22 PM, Samisa Abeysinghe  wrote:

> I am trying to build the default profile for dependencies, and I get the
> following errors:
>
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -Drepo
> sitoryId=[id]
>
>   Path to dependency:
> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
>
> 2) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -Drepo
> sitoryId=[id]
>
>   Path to dependency:
> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
>
> 3) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel -DartifactId=ode-utils
> -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -Dreposit
> oryId=[id]
>
>   Path to dependency:
> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
> 4) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT
>
> 4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -D
> repositoryId=[id]
>
>   Path to dependency:
> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
> 4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT
>
> 5) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-obj -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>   mvn deploy:deploy-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-obj -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -Drepo
> sitoryId=[id]
>
>   Path to dependency:
> 1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
> 2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
> 3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
> 4) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT
>
> 6) org.wso2.bpel:ode-bpel-ql:jar:1.3.5-SNAPSHOT
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.wso2.bpel
> -DartifactId=ode-bpel-ql -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>   Alternat

[Carbon-dev] Module versioning in Carbon

[Isuru Suriarachchi]

Hi all,

I've noticed that the version for an Axis2 module which comes through an
OSGi bundle is calculated form the bundle version. But for most of the
module bundles in carbon, bundle version is equal to the carbon version.
Therefore module versions are same as Carbon version.

Ex: In trunk,

addressing - 3.10-SNAPSHOT
throttling - 3.10-SNAPSHOT
caching - 3.10-SNAPSHOT

But I think this is wrong. The module version should be the original module
version. Ex: addressing 1.6-SNAPSHOT.

This problems doesn't exist for modules which comes through orbit bundles
(Ex : rampart). That is because in orbit, we have used the original version
instead of Carbon version.

So I think the cleaner solution for this is to have orbit bundles for all
external sources. For example, addressing module should come from axis2
orbit bundle, throttling module should come from an orbit bundle which wraps
commons/throttling etc..

WDYT??

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Error on BPS startup in 3.0.1 branch

[Waruna Ranasinghe]

Working on it.


~Waruna

On Thu, Aug 26, 2010 at 2:18 PM, Asela Pathberiya  wrote:

> Hi Waruna,
>
> I getting following, Please have a look.
>
> org.osgi.framework.BundleException: The bundle could not be resolved.
> Reason: Missing Constraint: Import-Package: javax.annotation.processing;
> version="0.0.0"
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
> at
> org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
> at
> org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
> at
> org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
> at
> org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
> at
> org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
>
> Thanks,
> Asela.
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
-
Waruna Ranasinghe
Senior Software Engineer, WSO2

Mobile: +94 724 318285
BLOG: http://warunapw.blogspot.com

www.wso2.com - "Lean . Enterprise . Middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Fresh build on windows fails with ODE build

[Samisa Abeysinghe]

I am trying to build the default profile for dependencies, and I get the
following errors:

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-dao -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -Drepo
sitoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT

2) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-api -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -Drepo
sitoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT

3) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-utils -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel -DartifactId=ode-utils
-Dversion=1.3.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-Dreposit
oryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
4) org.wso2.bpel:ode-utils:jar:1.3.5-SNAPSHOT

4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-schemas -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -D
repositoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
4) org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-SNAPSHOT

5) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-obj -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-obj -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -Drepo
sitoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-dao:jar:1.3.5-SNAPSHOT
3) org.wso2.bpel:ode-bpel-api:jar:1.3.5-SNAPSHOT
4) org.wso2.bpel:ode-bpel-obj:jar:1.3.5-SNAPSHOT

6) org.wso2.bpel:ode-bpel-ql:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-ql -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.wso2.bpel
-DartifactId=ode-bpel-ql -Dversion=1.3.5-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -Drepos
itoryId=[id]

  Path to dependency:
1) org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-SNAPSHOT
2) org.wso2.bpel:ode-bpel-ql:jar:1.3.5-SNAPSHOT

7) org.wso2.bpel:ode-bpel-compiler:jar:1.3.5-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org

Re: [Carbon-dev] synapse-commons:jar missing

[Samisa Abeysinghe]

What should be the version?

On Thu, Aug 26, 2010 at 1:17 PM, Senaka Fernando  wrote:

> Hi Samisa,
>
> On Thu, Aug 26, 2010 at 12:55 PM, Samisa Abeysinghe wrote:
>
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> --
>> 1) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT
>>
>
> I think the version is wrong.
>
> Thanks,
> Senaka.
>
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>  mvn install:install-file -DgroupId=org.apache.synapse
>> -DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>  mvn deploy:deploy-file -DgroupId=org.apache.synapse
>> -DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>1)
>> org.wso2.stratos:org.wso2.stratos.billing.mgt:bundle:1.0.0-SNAPSHOT
>>2) org.wso2.carbon:org.wso2.carbon.billing.core:jar:3.1.0-SNAPSHOT
>>3) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Senaka Fernando
> Associate Technical Lead
> WSO2 Inc.
> E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818
>
> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

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

[Carbon-dev] Error on BPS startup in 3.0.1 branch

[Asela Pathberiya]

Hi Waruna,

I getting following, Please have a look.

org.osgi.framework.BundleException: The bundle could not be resolved.
Reason: Missing Constraint: Import-Package: javax.annotation.processing;
version="0.0.0"
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
at
org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)

Thanks,
Asela.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Carbon 3.0.1 Alpha3 build

[Asela Pathberiya]

Hi all,

Please find the 3.0.1 alpha3 build of ESB,WSAS,GREG and IS here[1].

[1]http://builder.wso2.org/~carbon/releases/carbon/3.0.1/Alpha3/

Thanks,
Asela.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Securing WSAS service with policy from G-Reg

[Hiranya Jayathilaka]

On Thu, Aug 26, 2010 at 4:40 AM, Tharindu Mathew  wrote:

> Thanks Ruwan.
>
> Yes the mode of G-Reg as the central repository is strengthened more that
> way.
>
> If WSAS follows the same model as the ESB does when engaging security i.e.
> pointing to a policy on the Registry it will be very convenient.
>

+1

Currently ESB allows to specify a random security policy using a registry
key. Would be nice to have a similar feature in WSAS.

Thanks,
Hiranya


>
>
> On Wed, Aug 25, 2010 at 4:01 PM, Ruwan Linton  wrote:
>
>>  +1, it is a nice feature to have, when you have your policies defined in
>> the governance registry it is a valid usecase to browse and point the policy
>> to be used.
>>
>> but, AFAIK we cannot do this on WSAS.
>>
>> Ruwan
>>
>>
>> On 8/26/10 12:02 AM, Tharindu Mathew wrote:
>>
>> Hi Prabath,
>>
>>  Thanks for the reply. My question is whether the inverse of this can be
>> done?
>>
>>  Can we refer to a policy in G-Reg to be applied to the service that
>> needs to be secured? That would be a nice thing to have specially if most of
>> the services would be using the same security policy.
>>
>> On Wed, Aug 25, 2010 at 10:59 AM, Prabath Siriwardana 
>> wrote:
>>
>>> Hi Tharindu;
>>>
>>> When you follow the security wizard - the applied policy get stored in
>>> the registry it self..
>>>
>>> Thanks & regards.
>>> -Prabath
>>>
>>>   On Wed, Aug 25, 2010 at 11:09 PM, Tharindu Mathew 
>>> wrote:
>>>
  Hi All,

  I have secured a service in WSAS using UsernameToken.

  Is there a way to secure the service by referring to a policy stored
 in G-Reg?

 --
 Regards,

 Tharindu

  ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Prabath Siriwardena
>>>
>>> http://blog.facilelogin.com
>>> http://RampartFAQ.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>>
>> ___
>> Carbon-dev mailing 
>> listcarbon-...@wso2.orghttps://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.com
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> tweet: http://twitter.com/ruwanlinton
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Regards,
>
> Tharindu
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

Re: [Carbon-dev] synapse-commons:jar missing

[Senaka Fernando]

Hi Samisa,

On Thu, Aug 26, 2010 at 12:55 PM, Samisa Abeysinghe  wrote:

> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT
>

I think the version is wrong.

Thanks,
Senaka.

>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>  mvn install:install-file -DgroupId=org.apache.synapse
> -DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>  mvn deploy:deploy-file -DgroupId=org.apache.synapse
> -DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>1)
> org.wso2.stratos:org.wso2.stratos.billing.mgt:bundle:1.0.0-SNAPSHOT
>2) org.wso2.carbon:org.wso2.carbon.billing.core:jar:3.1.0-SNAPSHOT
>3) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Senaka Fernando
Associate Technical Lead
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] synapse-commons:jar missing

[Samisa Abeysinghe]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT

 Try downloading the file manually from the project website.

 Then, install it using the command:
 mvn install:install-file -DgroupId=org.apache.synapse
-DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file

 Alternatively, if you host your own repository you can deploy the file
there:
 mvn deploy:deploy-file -DgroupId=org.apache.synapse
-DartifactId=synapse-commons -Dversion=1.4.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

 Path to dependency:
   1)
org.wso2.stratos:org.wso2.stratos.billing.mgt:bundle:1.0.0-SNAPSHOT
   2) org.wso2.carbon:org.wso2.carbon.billing.core:jar:3.1.0-SNAPSHOT
   3) org.apache.synapse:synapse-commons:jar:1.4.0-SNAPSHOT

Thanks,
Samisa...

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