Re: [Carbon-dev] Qpid and Derby Issues

[Danushka Menikkumbura]

Hi Hiranya,

Just had a chat with Sameera. If the self-contained bundle has an explicit
rule not to import whichever embedded, it should not get wired to external
bundles. Shall we try that out and see?. Ideally we should have a single
Derby bundle but I am little reluctant to do changes to Qpid due to obvious
reasons ;-).

Thanks,
Danushka

On Mon, May 9, 2011 at 11:55 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 9, 2011 at 11:49 AM, Danushka Menikkumbura 
> wrote:
>
>> Even when the self-contained bundle does not import packages that are
>> embedded?
>>
>
> Seems that's the case. May be Sameera can explain this better?
>
> Thanks,
> Hiranya
>
>
>>
>> Danushka
>>
>>
>> On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura <
>>> danus...@wso2.com> wrote:
>>>
 +1.

 I wonder why the Qpid bundle gets wired to the other Derby lib instead
 of which is embedded?

>>>
>>> I had a chat with Sameera about this. Apparently that's the normal OSGi
>>> behavior. Packages exported by other bundles get precedence over private
>>> packages.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Danushka

 On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka 
 wrote:

> I think the right solution is to introduce a separate Derby bundle
> (currently it's embedded in qpid). This bundle should contain everything
> needed for Qpid and ESB samples.
>
> Thanks,
> Hiranya
>
>
> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka  > wrote:
>
>> Hi,
>>
>> We are having some issues testing the DB mediator samples in ESB (with
>> Derby). When we deploy derby client libraries to the ESB, Qpid component
>> fails. Reason is when we deploy derby libraries to the ESB, the qpid
>> component gets wired to that instead of the embedded derby binaries. Any
>> idea how to fix this?
>>
>> Thanks
>> --
>> 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
>>
>
>
>
> --
> 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Show/Hide Menu in Web Console

[Anjana Fernando]

Hi Azeez,

I see, yeah, that is true in the case of extensibility, but if the sole
purpose is for to simply hide the panel, the most adopted approach - as I've
experienced - is the use of a small button (I agree it should be a better
one than earlier, should be smaller), or a thin line in the middle which has
arrows which separate the two panels.

Cheers,
Anjana.

On Mon, May 9, 2011 at 11:00 AM, Afkham Azeez  wrote:

>
>
> On Mon, May 9, 2011 at 10:30 AM, Chanaka Jayasena wrote:
>
>> Hi Anjana,
>>
>> Thank you for your suggestion. I change the toggle button from the initial
>> one to this one base on some offline discussions. The concept is taken from
>> the IntelliJ IDEA UI. The strip is only taking 20px on the horizontal space.
>> Also as in the IDEA UI, we have the option of adding more items in this
>> strip. But I also think this text "Menu" is misleading. Any suggestions?
>>
>
> Yeah, that was my suggestion I guess. This allows for extensibility. Also,
> the left side options are Menu items. We have been calling this the left
> Menu for sometime. We could make this bar a bit thinner, perhaps. Just
> having a button without such a bar was ugly, and that button looked out of
> place.
>
>
>>
>> thanks,
>> Chanaka
>>
>> On Sun, May 8, 2011 at 8:43 PM, Anjana Fernando  wrote:
>>
>>> Hi,
>>>
>>> Small suggestion, the show/hide menu option we've on the web console,
>>> isn't it like taking too much of the real-estate of the UI, there's a full
>>> strip which takes about 50px width. Can't we put a small <,> button in the
>>> side, where the arrow changes according to the state (I think there was
>>> something similar before and was removed). And also, it sort of gives a
>>> wrong impression, since it's named "Menu", that you get a menu when you
>>> click it.
>>>
>>> Cheers,
>>> Anjana.
>>> --
>>> *Anjana Fernando*
>>> Senior Software Engineer
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] New set of packs available for Smoke Tests

[Sameera Jayasoma]

Guys, this is bit urgent. Please do a round of smoke testing. It seems this
set of build are stable. Please confirm it soon.

Thanks,
Sameera

On Mon, May 9, 2011 at 12:05 PM, Sameera Jayasoma  wrote:

> RMs, please smoke test the builds in[1] and update the doc[2].
>
> Thanks,
> Sameera.
>
> [1] http://10.100.1.43/~carbon/releases/carbon/3.2.0/stable/
> [2]
> https://spreadsheets0.google.com/a/wso2.com/spreadsheet/ccc?hl=en&key=tl_FPa9OvQjAGPEv60s8MeA&hl=en#gid=0
>
>
> On Mon, May 9, 2011 at 12:01 PM, Sameera Jayasoma wrote:
>
>> RMs, please smoke these this build and update the doc[1].
>>
>> Thanks,
>> Sameera.
>>
>> [1]
>> https://spreadsheets0.google.com/a/wso2.com/spreadsheet/ccc?hl=en&key=tl_FPa9OvQjAGPEv60s8MeA&hl=en#gid=0
>>
>>
>> On Mon, May 9, 2011 at 12:00 PM, Denis Weerasiri  wrote:
>>
>>> Hi,
>>> $subject at http://10.100.1.43/~carbon/releases/carbon/3.2.0/latest/ .
>>> These packs include commits until r93682.
>>>
>>> --
>>> Thanks,
>>> Denis
>>> --
>>> *Denis Weerasiri*
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> *email: denis ** [AT] wso2.com*
>>> *
>>> blog: **http://ddweerasiri.blogspot.com*
>>> *
>>> twitter: **http://twitter.com/ddweerasiri*
>>> *
>>> linked-in: 
>>> **http://lk.linkedin.com/in/ddweerasiri*
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead and Product Manager, WSO2 Carbon
>>
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>



-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

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

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

Re: [Carbon-dev] New set of packs available for Smoke Tests

[Sameera Jayasoma]

RMs, please smoke test the builds in[1] and update the doc[2].

Thanks,
Sameera.

[1] http://10.100.1.43/~carbon/releases/carbon/3.2.0/stable/
[2]
https://spreadsheets0.google.com/a/wso2.com/spreadsheet/ccc?hl=en&key=tl_FPa9OvQjAGPEv60s8MeA&hl=en#gid=0

On Mon, May 9, 2011 at 12:01 PM, Sameera Jayasoma  wrote:

> RMs, please smoke these this build and update the doc[1].
>
> Thanks,
> Sameera.
>
> [1]
> https://spreadsheets0.google.com/a/wso2.com/spreadsheet/ccc?hl=en&key=tl_FPa9OvQjAGPEv60s8MeA&hl=en#gid=0
>
>
> On Mon, May 9, 2011 at 12:00 PM, Denis Weerasiri  wrote:
>
>> Hi,
>> $subject at http://10.100.1.43/~carbon/releases/carbon/3.2.0/latest/ .
>> These packs include commits until r93682.
>>
>> --
>> Thanks,
>> Denis
>> --
>> *Denis Weerasiri*
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> *email: denis ** [AT] wso2.com*
>> *
>> blog: **http://ddweerasiri.blogspot.com*
>> *
>> twitter: **http://twitter.com/ddweerasiri*
>> *
>> linked-in: 
>> **http://lk.linkedin.com/in/ddweerasiri*
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>



-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

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

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

Re: [Carbon-dev] New set of packs available for Smoke Tests

[Sameera Jayasoma]

RMs, please smoke these this build and update the doc[1].

Thanks,
Sameera.

[1]
https://spreadsheets0.google.com/a/wso2.com/spreadsheet/ccc?hl=en&key=tl_FPa9OvQjAGPEv60s8MeA&hl=en#gid=0

On Mon, May 9, 2011 at 12:00 PM, Denis Weerasiri  wrote:

> Hi,
> $subject at http://10.100.1.43/~carbon/releases/carbon/3.2.0/latest/ .
> These packs include commits until r93682.
>
> --
> Thanks,
> Denis
> --
> *Denis Weerasiri*
> Software Engineer; WSO2 Inc.; http://wso2.com,
> *email: denis ** [AT] wso2.com* 
> *
> blog: **http://ddweerasiri.blogspot.com*
> *
> twitter: **http://twitter.com/ddweerasiri*
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

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

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

[Carbon-dev] New set of packs available for Smoke Tests

[Denis Weerasiri]

Hi,
$subject at http://10.100.1.43/~carbon/releases/carbon/3.2.0/latest/ .
These packs include commits until r93682.

-- 
Thanks,
Denis
--
*Denis Weerasiri*
Software Engineer; WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com* *
blog: **http://ddweerasiri.blogspot.com* *
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid and Derby Issues

[Hiranya Jayathilaka]

On Mon, May 9, 2011 at 11:49 AM, Danushka Menikkumbura wrote:

> Even when the self-contained bundle does not import packages that are
> embedded?
>

Seems that's the case. May be Sameera can explain this better?

Thanks,
Hiranya


>
> Danushka
>
>
> On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura > > wrote:
>>
>>> +1.
>>>
>>> I wonder why the Qpid bundle gets wired to the other Derby lib instead of
>>> which is embedded?
>>>
>>
>> I had a chat with Sameera about this. Apparently that's the normal OSGi
>> behavior. Packages exported by other bundles get precedence over private
>> packages.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Danushka
>>>
>>> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka 
>>> wrote:
>>>
 I think the right solution is to introduce a separate Derby bundle
 (currently it's embedded in qpid). This bundle should contain everything
 needed for Qpid and ESB samples.

 Thanks,
 Hiranya


 On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka 
 wrote:

> Hi,
>
> We are having some issues testing the DB mediator samples in ESB (with
> Derby). When we deploy derby client libraries to the ESB, Qpid component
> fails. Reason is when we deploy derby libraries to the ESB, the qpid
> component gets wired to that instead of the embedded derby binaries. Any
> idea how to fix this?
>
> Thanks
> --
> 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
>



 --
 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
 http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://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
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid and Derby Issues

[Danushka Menikkumbura]

Even when the self-contained bundle does not import packages that are
embedded?

Danushka

On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura 
> wrote:
>
>> +1.
>>
>> I wonder why the Qpid bundle gets wired to the other Derby lib instead of
>> which is embedded?
>>
>
> I had a chat with Sameera about this. Apparently that's the normal OSGi
> behavior. Packages exported by other bundles get precedence over private
> packages.
>
> Thanks,
> Hiranya
>
>
>>
>> Danushka
>>
>> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka wrote:
>>
>>> I think the right solution is to introduce a separate Derby bundle
>>> (currently it's embedded in qpid). This bundle should contain everything
>>> needed for Qpid and ESB samples.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka 
>>> wrote:
>>>
 Hi,

 We are having some issues testing the DB mediator samples in ESB (with
 Derby). When we deploy derby client libraries to the ESB, Qpid component
 fails. Reason is when we deploy derby libraries to the ESB, the qpid
 component gets wired to that instead of the embedded derby binaries. Any
 idea how to fix this?

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

>>>
>>>
>>>
>>> --
>>> 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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid and Derby Issues

[Hiranya Jayathilaka]

On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura wrote:

> +1.
>
> I wonder why the Qpid bundle gets wired to the other Derby lib instead of
> which is embedded?
>

I had a chat with Sameera about this. Apparently that's the normal OSGi
behavior. Packages exported by other bundles get precedence over private
packages.

Thanks,
Hiranya


>
> Danushka
>
> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka wrote:
>
>> I think the right solution is to introduce a separate Derby bundle
>> (currently it's embedded in qpid). This bundle should contain everything
>> needed for Qpid and ESB samples.
>>
>> Thanks,
>> Hiranya
>>
>>
>> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka wrote:
>>
>>> Hi,
>>>
>>> We are having some issues testing the DB mediator samples in ESB (with
>>> Derby). When we deploy derby client libraries to the ESB, Qpid component
>>> fails. Reason is when we deploy derby libraries to the ESB, the qpid
>>> component gets wired to that instead of the embedded derby binaries. Any
>>> idea how to fix this?
>>>
>>> Thanks
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> 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
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid and Derby Issues

[Danushka Menikkumbura]

+1.

I wonder why the Qpid bundle gets wired to the other Derby lib instead of
which is embedded?

Danushka

On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka wrote:

> I think the right solution is to introduce a separate Derby bundle
> (currently it's embedded in qpid). This bundle should contain everything
> needed for Qpid and ESB samples.
>
> Thanks,
> Hiranya
>
>
> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka wrote:
>
>> Hi,
>>
>> We are having some issues testing the DB mediator samples in ESB (with
>> Derby). When we deploy derby client libraries to the ESB, Qpid component
>> fails. Reason is when we deploy derby libraries to the ESB, the qpid
>> component gets wired to that instead of the embedded derby binaries. Any
>> idea how to fix this?
>>
>> Thanks
>> --
>> 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
>>
>
>
>
> --
> 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid and Derby Issues

[Hiranya Jayathilaka]

I think the right solution is to introduce a separate Derby bundle
(currently it's embedded in qpid). This bundle should contain everything
needed for Qpid and ESB samples.

Thanks,
Hiranya

On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka wrote:

> Hi,
>
> We are having some issues testing the DB mediator samples in ESB (with
> Derby). When we deploy derby client libraries to the ESB, Qpid component
> fails. Reason is when we deploy derby libraries to the ESB, the qpid
> component gets wired to that instead of the embedded derby binaries. Any
> idea how to fix this?
>
> Thanks
> --
> 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
>



-- 
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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Qpid and Derby Issues

[Hiranya Jayathilaka]

Hi,

We are having some issues testing the DB mediator samples in ESB (with
Derby). When we deploy derby client libraries to the ESB, Qpid component
fails. Reason is when we deploy derby libraries to the ESB, the qpid
component gets wired to that instead of the embedded derby binaries. Any
idea how to fix this?

Thanks
-- 
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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/greg"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/features/repository"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build was SUCCESSFUL"

[WSO2 Release-Builder]

total 252
drwxr-xr-x 5 release release   4096 2011-05-08 18:37 appserver
drwxr-xr-x 5 release release   4096 2011-05-08 19:47 bam
drwxr-xr-x 6 release release   4096 2011-05-08 20:25 bps
drwxr-xr-x 5 release release   4096 2011-05-08 20:34 brs
drwxr-xr-x 5 release release   4096 2011-05-08 18:01 carbon
drwxr-xr-x 5 release release   4096 2011-05-08 20:52 cep
drwxr-xr-x 5 release release   4096 2011-05-08 19:35 dss
drwxr-xr-x 5 release release   4096 2011-05-08 19:57 esb
drwxr-xr-x 5 release release   4096 2011-05-08 18:03 greg
drwxr-xr-x 5 release release   4096 2011-05-08 19:05 gs
drwxr-xr-x 7 release release   4096 2011-05-08 18:26 is
drwxr-xr-x 7 release release   4096 2011-05-08 21:09 manager
drwxr-xr-x 5 release release   4096 2011-05-08 21:01 mb
drwxr-xr-x 5 release release   4096 2011-05-08 19:17 ms
-rw--- 1 release release 173267 2011-05-08 00:13 nohup.out
-rw-r--r-- 1 release release   6792 2011-05-06 12:13 pom.xml
drwxr-xr-x 4 release release   4096 2011-05-06 12:09 wsf
-rw-r--r-- 1 release release   4783 2011-05-08 21:18 zips
date '+%Y-%m-%d_%H-%M-%S'
2011-05-09_11-05-29
rm: cannot remove `/home/carbon/public_html/releases/carbon/3.2.0/latest': No 
such file or directory
Error: JAVA_HOME is not defined correctly.
  We cannot execute /home/carbon/ebay/java/jdk1.6.0_21/jdk1.6.0_21/bin/java
2011-05-09_11-05-29
Carbon  packs are available at : 
http://10.100.1.43/~carbon/releases/carbon/3.2.0/latest/
tail -n50 $CARBON_SRC_HOME/build.log
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/carbon"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/mb"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/manager"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/brs"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/dss"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/esb"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/bam"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/gs"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/bps"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/ms"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/cep"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/appserver"

[WSO2 Release-Builder]

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/is"

[WSO2 Release-Builder]

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

Re: [Carbon-dev] Directory Server Error While Shutting Down

[Hiranya Jayathilaka]

On Mon, May 9, 2011 at 11:03 AM, Amila Jayasekara  wrote:

> On Mon, May 9, 2011 at 10:48 AM, Hiranya Jayathilaka 
> wrote:
> > [2011-05-09 10:47:01,346] ERROR - DefaultDirectoryService ERR_74
> SynchWorker
> > failed to synch directory.
> > java.util.ConcurrentModificationException
> > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
> > at java.util.HashMap$ValueIterator.next(HashMap.java:822)
> > at
> >
> org.apache.directory.server.core.partition.DefaultPartitionNexus.sync(DefaultPartitionNexus.java:477)
> > at
> >
> org.apache.directory.server.core.DefaultDirectoryService$SynchWorker.run(DefaultDirectoryService.java:268)
> > at java.lang.Thread.run(Thread.java:619)
> > [2011-05-09 10:47:02,039]  INFO - ApacheLDAPServer LDAP server stopped.
> >
> Problem is intermittent :(
>
> Looking into this. Any clue on how to reproduce this issue ?
>

I was just testing a bunch of samples and was starting and shutting down the
ESB quite frequently. This happened all the sudden.

Thanks,
Hiranya


> Thanks
> AmilaJ
>
> >
> > Thanks
> > --
> > 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
> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Directory Server Error While Shutting Down

[Amila Jayasekara]

On Mon, May 9, 2011 at 10:48 AM, Hiranya Jayathilaka  wrote:
> [2011-05-09 10:47:01,346] ERROR - DefaultDirectoryService ERR_74 SynchWorker
> failed to synch directory.
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
> at java.util.HashMap$ValueIterator.next(HashMap.java:822)
> at
> org.apache.directory.server.core.partition.DefaultPartitionNexus.sync(DefaultPartitionNexus.java:477)
> at
> org.apache.directory.server.core.DefaultDirectoryService$SynchWorker.run(DefaultDirectoryService.java:268)
> at java.lang.Thread.run(Thread.java:619)
> [2011-05-09 10:47:02,039]  INFO - ApacheLDAPServer LDAP server stopped.
>
Problem is intermittent :(

Looking into this. Any clue on how to reproduce this issue ?
Thanks
AmilaJ

>
> Thanks
> --
> 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Show/Hide Menu in Web Console

[Afkham Azeez]

On Mon, May 9, 2011 at 10:30 AM, Chanaka Jayasena  wrote:

> Hi Anjana,
>
> Thank you for your suggestion. I change the toggle button from the initial
> one to this one base on some offline discussions. The concept is taken from
> the IntelliJ IDEA UI. The strip is only taking 20px on the horizontal space.
> Also as in the IDEA UI, we have the option of adding more items in this
> strip. But I also think this text "Menu" is misleading. Any suggestions?
>

Yeah, that was my suggestion I guess. This allows for extensibility. Also,
the left side options are Menu items. We have been calling this the left
Menu for sometime. We could make this bar a bit thinner, perhaps. Just
having a button without such a bar was ugly, and that button looked out of
place.


>
> thanks,
> Chanaka
>
> On Sun, May 8, 2011 at 8:43 PM, Anjana Fernando  wrote:
>
>> Hi,
>>
>> Small suggestion, the show/hide menu option we've on the web console,
>> isn't it like taking too much of the real-estate of the UI, there's a full
>> strip which takes about 50px width. Can't we put a small <,> button in the
>> side, where the arrow changes according to the state (I think there was
>> something similar before and was removed). And also, it sort of gives a
>> wrong impression, since it's named "Menu", that you get a menu when you
>> click it.
>>
>> Cheers,
>> Anjana.
>> --
>> *Anjana Fernando*
>> Senior Software Engineer
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

[Carbon-dev] Directory Server Error While Shutting Down

[Hiranya Jayathilaka]

[2011-05-09 10:47:01,346] ERROR - DefaultDirectoryService ERR_74 SynchWorker
failed to synch directory.
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$ValueIterator.next(HashMap.java:822)
at
org.apache.directory.server.core.partition.DefaultPartitionNexus.sync(DefaultPartitionNexus.java:477)
at
org.apache.directory.server.core.DefaultDirectoryService$SynchWorker.run(DefaultDirectoryService.java:268)
at java.lang.Thread.run(Thread.java:619)
[2011-05-09 10:47:02,039]  INFO - ApacheLDAPServer LDAP server stopped.


Problem is intermittent :(

Thanks
-- 
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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[Afkham Azeez]

On Mon, May 9, 2011 at 7:05 AM, Samisa Abeysinghe  wrote:

> Done!
>
> But why is this failing???
>

Looks like some file system errors


>
>
> On Sun, May 8, 2011 at 4:49 PM, Denis Weerasiri  wrote:
>
>>
>>
>> On Sun, May 8, 2011 at 3:13 PM, Afkham Azeez  wrote:
>>
>>> Somebody who has access to this instance please stop this process. It is
>>> just spamming this mailing list.
>>
>> Noted.
>>
>>>
>>>
>>> On Sun, May 8, 2011 at 2:55 PM, WSO2 EC2 Stratos Builder <
>>> cbuil...@wso2.org> wrote:
>>>
 [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
 [INFO] [install:install {execution: default-install}]
 [INFO] Installing /home/stratos/carbon/dependencies/rampart/pom.xml to
 /home/stratos/.m2/repository/org/apache/rampart/rampart-project/1.6.1-wso2v1/rampart-project-1.6.1-wso2v1.pom
 [INFO]
 
 [INFO] Building Rampart - Policy
 [INFO]task-segment: [clean, install]
 [INFO]
 
 [INFO] [clean:clean {execution: default-clean}]
 [INFO] Deleting
 /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
 [INFO] [incremental-build:incremental-build {execution: default}]
 [INFO] Verifying module descriptor ...
 [INFO] Pom descriptor modification detected.
 [INFO] Deleting
 /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
 [INFO] [remote-resources:process {execution: default}]
 [INFO] [resources:resources {execution: default-resources}]
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 1 resource
 [INFO] Copying 3 resources
 [INFO] [compiler:compile {execution: default-compile}]
 Compiling 92 source files to
 /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target/classes
 [INFO] [resources:testResources {execution: default-testResources}]
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/src/test/resources
 [INFO] Copying 3 resources
 [INFO] [compiler:testCompile {execution: default-testCompile}]
 [INFO] Not compiling test sources
 [INFO] [surefire:test {execution: default-test}]
 [INFO] Tests are skipped.
 [INFO] [jar:jar {execution: default-jar}]
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Error assembling JAR

 Embedded error: Failed to read filesystem attributes for:
 /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/pom.xml
 [INFO]
 
 [INFO] For more information, run Maven with the -e switch
 [INFO]
 
 [INFO] Total time: 34 minutes 54 seconds
 [INFO] Finished at: Sun May 08 09:25:35 UTC 2011
 [INFO] Final Memory: 1192M/1820M
 [INFO]
 
 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Denis
>> --
>> *Denis Weerasiri*
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> *email: denis ** [AT] wso2.com*
>> *
>> blog: **http://ddweerasiri.blogspot.com*
>> *
>> twitter: **http://twitter.com/ddweerasiri*
>> *
>> linked-in: 
>> **http://lk.linkedin.com/in/ddweerasiri*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
>
> __

Re: [Carbon-dev] QueueService and MessageQueue

[Hiranya Jayathilaka]

On Mon, May 9, 2011 at 10:33 AM, Supun Kamburugamuva  wrote:

> Are we going to implement the all transport concept for this release?
>

No this is not the time to introduce changes to Axis2.


> If not it is better to make these two services exposed only in HTTP/S.
> Anyway these two services cannot be exposed in any other transport so
> having that in the services.xml is quite natural.
>

+1

Thanks,
Hiranya


>
> Thanks,
> Supun.
>
> On Sun, May 8, 2011 at 5:39 PM, Hiranya Jayathilaka 
> wrote:
> > Hi,
> >
> > On Sun, May 8, 2011 at 4:08 PM, Amila Suriarachchi 
> wrote:
> >>
> >>
> >> On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez  wrote:
> >>>
> >>> We have discussed this extensively. The proper solution is to add a
> >>> parameter to axis2.xml which specifies the behavior of the transports
> >>> element not being present in the services.xml. Either this could mean,
> >>> expose on all transports, or don't expose on any transports. If this is
> >>> don't expose on any transport, the services.xml should declare the
> >>> transports on which this service has to be exposed. In either case, the
> >>> user's existing services will not simply work OOTB without some
> changes.
> >>
> >> I think the correct solution is define the default export transports in
> >> the axis2.xml. By default we make it http https and local. (we can use
> the
> >> same element in the services.xml) if some one wants to add another
> transport
> >> it has to declare in the services.xml. Need to do a disscussion at the
> axis2
> >> level for this.
> >
> > +1 This is what I meant by making 'all transports' configurable.
> Basically
> > we should be able to define the default set of transports.
> >
> >>
> >> For these two services we will make it only available with http/s since
> >> other are not configured anyway.
> >
> > +1
> > Thanks,
> > Hiranya
> >
> >>
> >> thanks,
> >> Amila.
> >>
> >>
> >>
> >>>
> >>> ___
> >>> Carbon-dev mailing list
> >>> Carbon-dev@wso2.org
> >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>
> >>
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> http://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
> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
>
>
> --
> Supun Kamburugamuva
> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
> Member, Apache Software Foundation; http://www.apache.org
> WSO2 Inc.;  http://wso2.org
> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> Blog: http://supunk.blogspot.com
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] QueueService and MessageQueue

[Supun Kamburugamuva]

Are we going to implement the all transport concept for this release?
If not it is better to make these two services exposed only in HTTP/S.
Anyway these two services cannot be exposed in any other transport so
having that in the services.xml is quite natural.

Thanks,
Supun.

On Sun, May 8, 2011 at 5:39 PM, Hiranya Jayathilaka  wrote:
> Hi,
>
> On Sun, May 8, 2011 at 4:08 PM, Amila Suriarachchi  wrote:
>>
>>
>> On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez  wrote:
>>>
>>> We have discussed this extensively. The proper solution is to add a
>>> parameter to axis2.xml which specifies the behavior of the transports
>>> element not being present in the services.xml. Either this could mean,
>>> expose on all transports, or don't expose on any transports. If this is
>>> don't expose on any transport, the services.xml should declare the
>>> transports on which this service has to be exposed. In either case, the
>>> user's existing services will not simply work OOTB without some changes.
>>
>> I think the correct solution is define the default export transports in
>> the axis2.xml. By default we make it http https and local. (we can use the
>> same element in the services.xml) if some one wants to add another transport
>> it has to declare in the services.xml. Need to do a disscussion at the axis2
>> level for this.
>
> +1 This is what I meant by making 'all transports' configurable. Basically
> we should be able to define the default set of transports.
>
>>
>> For these two services we will make it only available with http/s since
>> other are not configured anyway.
>
> +1
> Thanks,
> Hiranya
>
>>
>> thanks,
>> Amila.
>>
>>
>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 
Supun Kamburugamuva
Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org
WSO2 Inc.;  http://wso2.org
E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Show/Hide Menu in Web Console

[Chanaka Jayasena]

Hi Anjana,

Thank you for your suggestion. I change the toggle button from the initial
one to this one base on some offline discussions. The concept is taken from
the IntelliJ IDEA UI. The strip is only taking 20px on the horizontal space.
Also as in the IDEA UI, we have the option of adding more items in this
strip. But I also think this text "Menu" is misleading. Any suggestions?

thanks,
Chanaka

On Sun, May 8, 2011 at 8:43 PM, Anjana Fernando  wrote:

> Hi,
>
> Small suggestion, the show/hide menu option we've on the web console, isn't
> it like taking too much of the real-estate of the UI, there's a full strip
> which takes about 50px width. Can't we put a small <,> button in the side,
> where the arrow changes according to the state (I think there was something
> similar before and was removed). And also, it sort of gives a wrong
> impression, since it's named "Menu", that you get a menu when you click it.
>
> Cheers,
> Anjana.
> --
> *Anjana Fernando*
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Error when svn updating MB product

[Dimuthu Leelarathne]

Hi,

On Mon, May 9, 2011 at 9:22 AM, Sameera Jayasoma  wrote:

> This seems to be a network problem.
>
>
But the same error  occurs at the same line. So I took a checkout to a
separate place. Now fine.

-dimuthu


> Sameera.
>
> On Mon, May 9, 2011 at 9:15 AM, Dimuthu Leelarathne wrote:
>
>> Hi,
>>
>> I am getting an error when svn updating products/mb. I tried deleting mb
>> from local file system and getting the svn up again. But it fails.
>>
>> Dmb/modules/samples/product/jmsclient/ReadMe.txt
>> Amb/modules/samples/product/jmsclient/README.txt
>> Dmb/modules/samples/product/wsclient/ReadMe.txt
>> Amb/modules/samples/product/wsclient/README.txt
>> svn: REPORT of '/repos/wso2/!svn/vcc/default': Could not read chunk
>> delimiter: Secure connection truncated (https://svn.wso2.org)
>> muthulee@muthulee-laptop:~/work/tcarbon-platform/products$ svn up
>> svn: REPORT of '/repos/wso2/!svn/vcc/default': 404 Not Found (
>> https://svn.wso2.org)
>>
>> Anyone else facing this problem?
>>
>> tx,
>> dimuthu
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Error when svn updating MB product

[Sameera Jayasoma]

This seems to be a network problem.

Sameera.

On Mon, May 9, 2011 at 9:15 AM, Dimuthu Leelarathne wrote:

> Hi,
>
> I am getting an error when svn updating products/mb. I tried deleting mb
> from local file system and getting the svn up again. But it fails.
>
> Dmb/modules/samples/product/jmsclient/ReadMe.txt
> Amb/modules/samples/product/jmsclient/README.txt
> Dmb/modules/samples/product/wsclient/ReadMe.txt
> Amb/modules/samples/product/wsclient/README.txt
> svn: REPORT of '/repos/wso2/!svn/vcc/default': Could not read chunk
> delimiter: Secure connection truncated (https://svn.wso2.org)
> muthulee@muthulee-laptop:~/work/tcarbon-platform/products$ svn up
> svn: REPORT of '/repos/wso2/!svn/vcc/default': 404 Not Found (
> https://svn.wso2.org)
>
> Anyone else facing this problem?
>
> tx,
> dimuthu
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

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

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

Re: [Carbon-dev] P2 does not work via a proxy server?

[Sameera Jayasoma]

Hi Samisa,

This seems to be beyond our control. We can see some queries in the P2
mailing list also.  Anyway Pradeep was working on this. He will update the
thread.

Thanks,
Sameera

On Mon, May 9, 2011 at 8:09 AM, Samisa Abeysinghe  wrote:

> Have we fixed this on the trunk?
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

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

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

[Carbon-dev] Error when svn updating MB product

[Dimuthu Leelarathne]

Hi,

I am getting an error when svn updating products/mb. I tried deleting mb
from local file system and getting the svn up again. But it fails.

Dmb/modules/samples/product/jmsclient/ReadMe.txt
Amb/modules/samples/product/jmsclient/README.txt
Dmb/modules/samples/product/wsclient/ReadMe.txt
Amb/modules/samples/product/wsclient/README.txt
svn: REPORT of '/repos/wso2/!svn/vcc/default': Could not read chunk
delimiter: Secure connection truncated (https://svn.wso2.org)
muthulee@muthulee-laptop:~/work/tcarbon-platform/products$ svn up
svn: REPORT of '/repos/wso2/!svn/vcc/default': 404 Not Found (
https://svn.wso2.org)

Anyone else facing this problem?

tx,
dimuthu
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] P2 does not work via a proxy server?

[Samisa Abeysinghe]

Have we fixed this on the trunk?

Thanks,
Samisa...

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

Re: [Carbon-dev] Remove multi-instance feature

[Afkham Azeez]

We have noticed that IO becomes a bottleneck, and this can lead to failure
of multiple JVMs. For example, the AS was failing very frequently when the
LB and AS instance were running on the same machine. After separating it
out, we were able to handle higher loads. In fact, this is how we are
planning to setup Mars 1.0. Having the LB & worker node on the same instance
does not work properly.

--
Sent from APD
On May 9, 2011 6:02 AM, "Sanjiva Weerawarana"  wrote:
> Should we not be using it in Stratos? I've been thinking of trying that as
> an alternative to using VMs basically .. take a big machine and run a
bunch
> of elastically scaling processes rather than VMs.
>
> If its broken of course then that needs to be fixed before such an
> experiment can be tried. At least it would be a useful research experiment
> to compare VMs vs. not. In our world we control all the VMs so the
security
> disadvantages of processes is essentially gone IMO.
>
> Sanjiva.
>
> On Sun, May 8, 2011 at 11:33 AM, Afkham Azeez  wrote:
>
>> This is a feature that never gets tested, nobody seems to know how to use
>> it, and it is badly broken. Nobody seems to be using it in the real world
>> anyway. Shall we remove it? We can get rid of the confusing
ports-config.xml
>> file as well.
>>
>> --
>> *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*<
http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 |
+1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[Samisa Abeysinghe]

Done!

But why is this failing???

On Sun, May 8, 2011 at 4:49 PM, Denis Weerasiri  wrote:

>
>
> On Sun, May 8, 2011 at 3:13 PM, Afkham Azeez  wrote:
>
>> Somebody who has access to this instance please stop this process. It is
>> just spamming this mailing list.
>
> Noted.
>
>>
>>
>> On Sun, May 8, 2011 at 2:55 PM, WSO2 EC2 Stratos Builder <
>> cbuil...@wso2.org> wrote:
>>
>>> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
>>> [INFO] [install:install {execution: default-install}]
>>> [INFO] Installing /home/stratos/carbon/dependencies/rampart/pom.xml to
>>> /home/stratos/.m2/repository/org/apache/rampart/rampart-project/1.6.1-wso2v1/rampart-project-1.6.1-wso2v1.pom
>>> [INFO]
>>> 
>>> [INFO] Building Rampart - Policy
>>> [INFO]task-segment: [clean, install]
>>> [INFO]
>>> 
>>> [INFO] [clean:clean {execution: default-clean}]
>>> [INFO] Deleting
>>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
>>> [INFO] [incremental-build:incremental-build {execution: default}]
>>> [INFO] Verifying module descriptor ...
>>> [INFO] Pom descriptor modification detected.
>>> [INFO] Deleting
>>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
>>> [INFO] [remote-resources:process {execution: default}]
>>> [INFO] [resources:resources {execution: default-resources}]
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] Copying 1 resource
>>> [INFO] Copying 3 resources
>>> [INFO] [compiler:compile {execution: default-compile}]
>>> Compiling 92 source files to
>>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target/classes
>>> [INFO] [resources:testResources {execution: default-testResources}]
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] skip non existing resourceDirectory
>>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/src/test/resources
>>> [INFO] Copying 3 resources
>>> [INFO] [compiler:testCompile {execution: default-testCompile}]
>>> [INFO] Not compiling test sources
>>> [INFO] [surefire:test {execution: default-test}]
>>> [INFO] Tests are skipped.
>>> [INFO] [jar:jar {execution: default-jar}]
>>> [INFO]
>>> 
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> 
>>> [INFO] Error assembling JAR
>>>
>>> Embedded error: Failed to read filesystem attributes for:
>>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/pom.xml
>>> [INFO]
>>> 
>>> [INFO] For more information, run Maven with the -e switch
>>> [INFO]
>>> 
>>> [INFO] Total time: 34 minutes 54 seconds
>>> [INFO] Finished at: Sun May 08 09:25:35 UTC 2011
>>> [INFO] Final Memory: 1192M/1820M
>>> [INFO]
>>> 
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks,
> Denis
> --
> *Denis Weerasiri*
> Software Engineer; WSO2 Inc.; http://wso2.com,
> *email: denis ** [AT] wso2.com* 
> *
> blog: **http://ddweerasiri.blogspot.com*
> *
> twitter: **http://twitter.com/ddweerasiri*
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 EC2 Carbon Builder]

[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.initializer.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.statistics.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.statistics.transport.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.configadmin.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.artifactuploader.feature:3.2.0-SNAPSHOT:
 checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.tracer.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.localentry.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.endpoint.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.sequences.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.proxyadmin.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediators.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.rule.mediator.feature:3.2.0-SNAPSHOT: checking 
for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.rule.engine.drools.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.rule.engine.jsr94.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot org.wso2.esb:org.wso2.esb.styles.feature:4.0.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.priority.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot org.wso2.carbon:org.wso2.carbon.relay.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot org.wso2.esb:org.wso2.esb.samples.feature:4.0.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.identity.oauth.mediator.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.identity.xacml.mediator.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot org.wso2.carbon:org.wso2.carbon.smooks.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.application.mgt.synapse.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.application.deployer.synapse.feature:3.2.0-SNAPSHOT:
 checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.transports.relay.feature:1.0.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.templates.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.message.store.feature:3.2.0-SNAPSHOT: checking 
for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.message.processor.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.transports.hl7.feature:3.2.0-SNAPSHOT: checking 
for updates from wso2-nexus
Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.transports.hl7.feature/3.2.0-SNAPSHOT/org.wso2.carbon.transports.hl7.feature-3.2.0-SNAPSHOT.zip
[INFO] Unable to find resource 
'org.wso2.carbon:org.wso2.carbon.transports.hl7.feature:zip:3.2.0-SNAPSHOT' in 
repository wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
[ERROR] ERROR
org.apache.maven.plugin.MojoExecutionException: ERROR
at 
org.wso2.maven.p2.generate.utils.MavenUtils.getResolvedArtifact(MavenUtils.java:43)
at 
org.wso2.maven.p2.RepositoryGenMojo.getProcessedFeatureArtifacts(RepositoryGenMojo.java:360)
at 
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:193)
at 
org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:187)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLi

Re: [Carbon-dev] Remove multi-instance feature

[Sanjiva Weerawarana]

Should we not be using it in Stratos? I've been thinking of trying that as
an alternative to using VMs basically .. take a big machine and run a bunch
of elastically scaling processes rather than VMs.

If its broken of course then that needs to be fixed before such an
experiment can be tried. At least it would be a useful research experiment
to compare VMs vs. not. In our world we control all the VMs so the security
disadvantages of processes is essentially gone IMO.

Sanjiva.

On Sun, May 8, 2011 at 11:33 AM, Afkham Azeez  wrote:

> This is a feature that never gets tested, nobody seems to know how to use
> it, and it is badly broken. Nobody seems to be using it in the real world
> anyway. Shall we remove it? We can get rid of the confusing ports-config.xml
> file as well.
>
> --
> *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*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

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

[Carbon-dev] please fix spelling mistake: Sunccessfully

[Sanjiva Weerawarana]

http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=Sunccessfully#hl=en&biw=1440&bih=758&sa=X&ei=3c_GTezIHserrAf50MmzBA&ved=0CBQQvgUoAA&q=Sunccessfully+%2Bsite%3Awso2.org&nfpr=1&bav=on.2,or.r_gc.r_pw.&fp=263951646445c969

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

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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 EC2 Carbon Builder]

[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.initializer.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.statistics.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.statistics.transport.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.configadmin.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.artifactuploader.feature:3.2.0-SNAPSHOT:
 checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.tracer.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.localentry.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.endpoint.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.sequences.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.proxyadmin.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediators.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.rule.mediator.feature:3.2.0-SNAPSHOT: checking 
for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.rule.engine.drools.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.rule.engine.jsr94.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot org.wso2.esb:org.wso2.esb.styles.feature:4.0.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.priority.feature:3.2.0-SNAPSHOT: checking for 
updates from wso2-nexus
[INFO] snapshot org.wso2.carbon:org.wso2.carbon.relay.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot org.wso2.esb:org.wso2.esb.samples.feature:4.0.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.identity.oauth.mediator.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.identity.xacml.mediator.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot org.wso2.carbon:org.wso2.carbon.smooks.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.application.mgt.synapse.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.application.deployer.synapse.feature:3.2.0-SNAPSHOT:
 checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.transports.relay.feature:1.0.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.mediation.templates.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.message.store.feature:3.2.0-SNAPSHOT: checking 
for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.message.processor.feature:3.2.0-SNAPSHOT: 
checking for updates from wso2-nexus
[INFO] snapshot 
org.wso2.carbon:org.wso2.carbon.transports.hl7.feature:3.2.0-SNAPSHOT: checking 
for updates from wso2-nexus
Downloading: 
http://maven.wso2.org/nexus/content/groups/wso2-public//org/wso2/carbon/org.wso2.carbon.transports.hl7.feature/3.2.0-SNAPSHOT/org.wso2.carbon.transports.hl7.feature-3.2.0-SNAPSHOT.zip
[INFO] Unable to find resource 
'org.wso2.carbon:org.wso2.carbon.transports.hl7.feature:zip:3.2.0-SNAPSHOT' in 
repository wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
[ERROR] ERROR
org.apache.maven.plugin.MojoExecutionException: ERROR
at 
org.wso2.maven.p2.generate.utils.MavenUtils.getResolvedArtifact(MavenUtils.java:43)
at 
org.wso2.maven.p2.RepositoryGenMojo.getProcessedFeatureArtifacts(RepositoryGenMojo.java:360)
at 
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:193)
at 
org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:187)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLi

[Carbon-dev] Show/Hide Menu in Web Console

[Anjana Fernando]

Hi,

Small suggestion, the show/hide menu option we've on the web console, isn't
it like taking too much of the real-estate of the UI, there's a full strip
which takes about 50px width. Can't we put a small <,> button in the side,
where the arrow changes according to the state (I think there was something
similar before and was removed). And also, it sort of gives a wrong
impression, since it's named "Menu", that you get a menu when you click it.

Cheers,
Anjana.
-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Testing on Websphere

[Charitha Kankanamge]

Can you send your carbon.xml? Also send me WebSphere server.xml (
${PROFILE_HOME}/config/cells/${CELL}/nodes/${NODE}/servers/${SERVER}/server.xml)

/Charitha

On Sun, May 8, 2011 at 8:31 PM, Chamara Ariyarathne wrote:

> I have set the context root in the installing process. When start invoked
> it hanged forever.
>
>
> On Sun, May 8, 2011 at 8:28 PM, Charitha Kankanamge wrote:
>
>> According to the second image, you have not started the web app
>> (wso2.war). Or you have not specified web app context root. Please check
>> again.
>>
>> /Charitha
>>
>> On Sun, May 8, 2011 at 6:30 PM, Chamara Ariyarathne wrote:
>>
>>> *I'm stuck in here,
>>> Im getting this page for the wsas webapp url; [attachement- serverpage]*
>>> SRVE0255E: A WebGroup/Virtual Host to handle /wso2/carbon/ has not been
>>> defined.SRVE0255E: A WebGroup/Virtual Host to handle
>>> 111.223.167.209:9450 has not been defined. *IBM WebSphere Application
>>> Server*
>>>
>>>
>>> *The service starting process is hanged in the Websphere Enterprise
>>> Applications page;  *[attachement- installing]
>>>
>>> *The server log says;*
>>>
>>> [5/8/11 16:01:21:445 IST] 0028 PermissionUpd I
>>> org.wso2.carbon.core.internal.permission.update.PermissionUpdater update
>>> Permission cache updated for tenant 0
>>> [5/8/11 16:01:21:448 IST] 0028 CarbonServerM I
>>> org.wso2.carbon.core.init.CarbonServerManager initializeCarbon
>>> ConfigurationContextService registered in 512ms
>>> [5/8/11 16:01:21:455 IST] 0028 HttpTransport I
>>> org.wso2.carbon.core.transports.http.HttpTransportListener start HTTP
>>> port: 9087
>>> [5/8/11 16:01:21:458 IST] 0028 HttpsTranspor I
>>> org.wso2.carbon.core.transports.http.HttpsTransportListener start HTTPS
>>> port   : 9450
>>> [5/8/11 16:01:25:900 IST] 0028 BasicTilesCon I
>>> org.apache.tiles.impl.BasicTilesContainer init Initializing Tiles2
>>> container. . .
>>> [5/8/11 16:01:25:949 IST] 0028 BasicTilesCon I
>>> org.apache.tiles.impl.BasicTilesContainer initializeDefinitionsFactory
>>> Tiles2 container initialization complete.
>>> [5/8/11 16:01:25:954 IST] 0028 TilesAccess   I
>>> org.apache.tiles.access.TilesAccess setContainer Publishing TilesContext for
>>> context: org.apache.tiles.web.util.ServletContextAdapter
>>> [5/8/11 16:01:26:067 IST] 0028 CarbonUIServi I
>>> org.wso2.carbon.ui.internal.CarbonUIServiceComponent activate Mgt Console
>>> URL  : https://111.223.167.209:9450/wso2/carbon/
>>> [5/8/11 16:01:26:080 IST] 0028 EventBrokerBu I
>>> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS activate
>>> Successfully registered the event broker
>>> [5/8/11 16:01:26:091 IST] 0028 StartupFinali I
>>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent
>>> completeInitialization Started Transport Listener Manager
>>> [5/8/11 16:01:26:094 IST] 0028 StartupFinali I
>>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent printInfo
>>> Server   :  WSO2 Application Server-4.1.0
>>> [5/8/11 16:01:26:097 IST] 0028 StartupFinali I
>>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent printInfo
>>> WSO2 Carbon started in 41 sec
>>> [5/8/11 16:13:08:462 IST] 001d ThreadMonitor W   WSVR0605W: Thread
>>> "WebContainer : 3" (001a) has been active for 746264 milliseconds and
>>> may be hung.  There is/are 1 thread(s) in total in the server that may be
>>> hung.
>>> at java.lang.Object.wait(Native Method)
>>> at java.lang.Object.wait(Object.java:196)
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.Semaphore.acquire(Semaphore.java:55)
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.updateSplash(EclipseStarter.java:1256)
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.setStartLevel(EclipseStarter.java:1231)
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:313)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>>> at java.lang.reflect.Method.invoke(Method.java:600)
>>> at
>>> org.wso2.carbon.bridge.EquinoxFrameworkLauncher.start(EquinoxFrameworkLauncher.java:289)
>>> at org.wso2.carbon.bridge.BridgeServlet.init(BridgeServlet.java:94)
>>>
>>> at javax.servlet.GenericServlet.init(GenericServlet.java:241)
>>> at
>>> com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
>>> at
>>> com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
>>> at
>>> com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1807)
>>> at
>>> com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
>>> at
>>> com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1011)
>>>

Re: [Carbon-dev] Testing on Websphere

[Charitha Kankanamge]

According to the second image, you have not started the web app (wso2.war).
Or you have not specified web app context root. Please check again.

/Charitha

On Sun, May 8, 2011 at 6:30 PM, Chamara Ariyarathne wrote:

> *I'm stuck in here,
> Im getting this page for the wsas webapp url; [attachement- serverpage]*
> SRVE0255E: A WebGroup/Virtual Host to handle /wso2/carbon/ has not been
> defined.SRVE0255E: A WebGroup/Virtual Host to handle 111.223.167.209:9450has 
> not been defined.
> *IBM WebSphere Application Server*
>
>
> *The service starting process is hanged in the Websphere Enterprise
> Applications page;  *[attachement- installing]
>
> *The server log says;*
>
> [5/8/11 16:01:21:445 IST] 0028 PermissionUpd I
> org.wso2.carbon.core.internal.permission.update.PermissionUpdater update
> Permission cache updated for tenant 0
> [5/8/11 16:01:21:448 IST] 0028 CarbonServerM I
> org.wso2.carbon.core.init.CarbonServerManager initializeCarbon
> ConfigurationContextService registered in 512ms
> [5/8/11 16:01:21:455 IST] 0028 HttpTransport I
> org.wso2.carbon.core.transports.http.HttpTransportListener start HTTP
> port: 9087
> [5/8/11 16:01:21:458 IST] 0028 HttpsTranspor I
> org.wso2.carbon.core.transports.http.HttpsTransportListener start HTTPS
> port   : 9450
> [5/8/11 16:01:25:900 IST] 0028 BasicTilesCon I
> org.apache.tiles.impl.BasicTilesContainer init Initializing Tiles2
> container. . .
> [5/8/11 16:01:25:949 IST] 0028 BasicTilesCon I
> org.apache.tiles.impl.BasicTilesContainer initializeDefinitionsFactory
> Tiles2 container initialization complete.
> [5/8/11 16:01:25:954 IST] 0028 TilesAccess   I
> org.apache.tiles.access.TilesAccess setContainer Publishing TilesContext for
> context: org.apache.tiles.web.util.ServletContextAdapter
> [5/8/11 16:01:26:067 IST] 0028 CarbonUIServi I
> org.wso2.carbon.ui.internal.CarbonUIServiceComponent activate Mgt Console
> URL  : https://111.223.167.209:9450/wso2/carbon/
> [5/8/11 16:01:26:080 IST] 0028 EventBrokerBu I
> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS activate
> Successfully registered the event broker
> [5/8/11 16:01:26:091 IST] 0028 StartupFinali I
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent
> completeInitialization Started Transport Listener Manager
> [5/8/11 16:01:26:094 IST] 0028 StartupFinali I
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent printInfo
> Server   :  WSO2 Application Server-4.1.0
> [5/8/11 16:01:26:097 IST] 0028 StartupFinali I
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent printInfo
> WSO2 Carbon started in 41 sec
> [5/8/11 16:13:08:462 IST] 001d ThreadMonitor W   WSVR0605W: Thread
> "WebContainer : 3" (001a) has been active for 746264 milliseconds and
> may be hung.  There is/are 1 thread(s) in total in the server that may be
> hung.
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:196)
> at
> org.eclipse.core.runtime.internal.adaptor.Semaphore.acquire(Semaphore.java:55)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.updateSplash(EclipseStarter.java:1256)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.setStartLevel(EclipseStarter.java:1231)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:313)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at java.lang.reflect.Method.invoke(Method.java:600)
> at
> org.wso2.carbon.bridge.EquinoxFrameworkLauncher.start(EquinoxFrameworkLauncher.java:289)
> at org.wso2.carbon.bridge.BridgeServlet.init(BridgeServlet.java:94)
>
> at javax.servlet.GenericServlet.init(GenericServlet.java:241)
> at
> com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
> at
> com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
> at
> com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1807)
> at
> com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
> at
> com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1011)
> at
> com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:932)
> at
> com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:611)
> at
> com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:429)
> at
> com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:304)
> at
> com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
> at
> com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
> at
> com.ibm.ws.webconta

Re: [Carbon-dev] QueueService and MessageQueue

[Hiranya Jayathilaka]

Hi,

On Sun, May 8, 2011 at 4:08 PM, Amila Suriarachchi  wrote:

>
>
> On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez  wrote:
>
>> We have discussed this extensively. The proper solution is to add a
>> parameter to axis2.xml which specifies the behavior of the transports
>> element not being present in the services.xml. Either this could mean,
>> expose on all transports, or don't expose on any transports. If this is
>> don't expose on any transport, the services.xml should declare the
>> transports on which this service has to be exposed. In either case, the
>> user's existing services will not simply work OOTB without some changes.
>>
>
> I think the correct solution is define the default export transports in the
> axis2.xml. By default we make it http https and local. (we can use the same
> element in the services.xml) if some one wants to add another transport it
> has to declare in the services.xml. Need to do a disscussion at the axis2
> level for this.
>

+1 This is what I meant by making 'all transports' configurable. Basically
we should be able to define the default set of transports.


>
> For these two services we will make it only available with http/s since
> other are not configured anyway.
>

+1

Thanks,
Hiranya


>
> thanks,
> Amila.
>
>
>
>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Continuous Build was SUCCESSFUL"

[WSO2 Release-Builder]

[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.sts.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.servicehosting.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.dataservices.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.mgt.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.jms.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.mail.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.statistics.transport.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.client.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.discovery.core.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.mediation.ext.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.proxy.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.discovery.ui.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.wsdl.tools.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.wsdl.tools.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.wsdl.tools.ui.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.xkms.mgt.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.multiple.instance.feature
[INFO] Extracting feature org.wso2.esb:org.wso2.esb.styles.feature
[INFO] Extracting feature org.wso2.governance:org.wso2.governance.styles.feature
[INFO] Extracting feature org.wso2.gs:org.wso2.gs.styles.feature
[INFO] Extracting feature org.wso2.gs:org.wso2.gs.menu.feature
[INFO] Extracting feature org.wso2.identity:org.wso2.identity.styles.feature
[INFO] Extracting feature org.wso2.identity:org.wso2.identity.utils.feature
[INFO] Extracting feature org.wso2.ms:org.wso2.ms.styles.feature
[INFO] Extracting feature org.wso2.appserver:org.wso2.appserver.styles.feature
[INFO] Extracting feature org.wso2.appserver:org.wso2.appserver.utils.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.cloud.csg.agent.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.cloud.csg.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.application.mgt.webapp.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.application.deployer.webapp.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.unifiedendpoint.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.event.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.messagebox.feature
[INFO] Copying resources
[INFO] Running Equinox P2 Publisher Application for Repository Generation
[INFO] Generating metadata for ..
[INFO] Generation completed with success [37 seconds].
[INFO] Running Equinox P2 Category Publisher Application for the Generated 
Repository
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/release/carbon/features/repository/pom.xml to 
/home/release/.m2/repository/org/wso2/carbon/wso2carbon-feature-repository/3.2.0-SNAPSHOT/wso2carbon-feature-repository-3.2.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 1 minute 25 seconds
[INFO] Finished at: Sun May 08 17:34:30 IST 2011
[INFO] Final Memory: 31M/1962M
[INFO] 
2011-05-08_17-32-53
Carbon  packs are available at : 
http://10.100.1.43/~carbon/releases/carbon/3.2.0/latest/
tail -n50 $CARBON_SRC_HOME/build.log
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[Denis Weerasiri]

On Sun, May 8, 2011 at 3:13 PM, Afkham Azeez  wrote:

> Somebody who has access to this instance please stop this process. It is
> just spamming this mailing list.

Noted.

>
>
> On Sun, May 8, 2011 at 2:55 PM, WSO2 EC2 Stratos Builder <
> cbuil...@wso2.org> wrote:
>
>> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
>> [INFO] [install:install {execution: default-install}]
>> [INFO] Installing /home/stratos/carbon/dependencies/rampart/pom.xml to
>> /home/stratos/.m2/repository/org/apache/rampart/rampart-project/1.6.1-wso2v1/rampart-project-1.6.1-wso2v1.pom
>> [INFO]
>> 
>> [INFO] Building Rampart - Policy
>> [INFO]task-segment: [clean, install]
>> [INFO]
>> 
>> [INFO] [clean:clean {execution: default-clean}]
>> [INFO] Deleting
>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
>> [INFO] [incremental-build:incremental-build {execution: default}]
>> [INFO] Verifying module descriptor ...
>> [INFO] Pom descriptor modification detected.
>> [INFO] Deleting
>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
>> [INFO] [remote-resources:process {execution: default}]
>> [INFO] [resources:resources {execution: default-resources}]
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] Copying 1 resource
>> [INFO] Copying 3 resources
>> [INFO] [compiler:compile {execution: default-compile}]
>> Compiling 92 source files to
>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target/classes
>> [INFO] [resources:testResources {execution: default-testResources}]
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] skip non existing resourceDirectory
>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/src/test/resources
>> [INFO] Copying 3 resources
>> [INFO] [compiler:testCompile {execution: default-testCompile}]
>> [INFO] Not compiling test sources
>> [INFO] [surefire:test {execution: default-test}]
>> [INFO] Tests are skipped.
>> [INFO] [jar:jar {execution: default-jar}]
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Error assembling JAR
>>
>> Embedded error: Failed to read filesystem attributes for:
>> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/pom.xml
>> [INFO]
>> 
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> 
>> [INFO] Total time: 34 minutes 54 seconds
>> [INFO] Finished at: Sun May 08 09:25:35 UTC 2011
>> [INFO] Final Memory: 1192M/1820M
>> [INFO]
>> 
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Software Engineer; WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com* *
blog: **http://ddweerasiri.blogspot.com* *
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 EC2 Stratos Builder]

[INFO] skip non existing resourceDirectory 
/home/stratos/carbon/dependencies/axis2/modules/webapp/src/test/resources
[INFO] Copying 2 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Not compiling test sources
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[axis2-webapp] in 
[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2-1.6.1-wso2v1]
[INFO] Processing war project
[INFO] Copying webapp 
webResources[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/webResources]
 
to[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2-1.6.1-wso2v1]
[INFO] Copying webapp 
webResources[/home/stratos/carbon/dependencies/axis2/modules/webapp/../../legal]
 
to[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2-1.6.1-wso2v1]
[INFO] Copying webapp 
resources[/home/stratos/carbon/dependencies/axis2/modules/webapp/src/main/webapp]
[INFO] Webapp assembled in [36722 msecs]
[INFO] Building war: 
/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2.war
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2.war to 
/home/stratos/.m2/repository/org/apache/axis2/axis2-webapp/1.6.1-wso2v1/axis2-webapp-1.6.1-wso2v1.war
[INFO] 
[INFO] Building Apache Axis2 - Root
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting /home/stratos/carbon/dependencies/axis2/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting /home/stratos/carbon/dependencies/axis2/target
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error when interpolating site descriptor

Embedded error: IOException: cannot interpolate environment properties: Cannot 
run program "env": java.io.IOException: error=12, Cannot allocate memory
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 25 minutes 52 seconds
[INFO] Finished at: Sun May 08 11:09:38 UTC 2011
[INFO] Final Memory: 1051M/1763M
[INFO] 
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Where the syslogConfig.xml comes from?

[Amani Soysa]

On Sun, May 8, 2011 at 11:15 AM, Afkham Azeez  wrote:

> Amani,
> when you name files, XML tags etc. you have to look at the conventions
> followed by the existing files, and should not deviate from it. AFAIK, we
> don't have camel cased config XML file names.
>

I will change it accordingly

>
> On Fri, May 6, 2011 at 2:42 PM, Danushka Menikkumbura 
> wrote:
>
>> I can not build the ESB because of missing syslogConfig.xml file. Most
>> probably I have not built a required feature, I can not locate it inside any
>> feature, though.
>>
>> Any idea?
>>
>> Thanks,
>> Danushka
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Where the syslogConfig.xml comes from?

[Kathiravelu Pradeeban]

On Sun, May 8, 2011 at 4:11 PM, Supun Kamburugamuva  wrote:

> On Sun, May 8, 2011 at 12:20 PM, Kathiravelu Pradeeban
>  wrote:
> >
> >
> > On Sun, May 8, 2011 at 10:31 AM, Kathiravelu Pradeeban <
> pradee...@wso2.com>
> > wrote:
> >>
> >> Hi Amani,
> >> I am creating a stripped down profile of esb (named as lb) consisting of
> >> load balancing components used in ESB. For this, I have removed
> logging-mgt
> >> feature from the p2 profile of lb, as I don't need that. Now I am
> getting
> >> the same error when building *lb*.
> >>
> >> [INFO] Failed to create assembly: Error adding file to archive:
> >>
> /home/pradeeban/trunk/stratos/carbon/products/lb/modules/distribution/product/../../p2-profile/product/target/wso2carbon-core-3.2.0-SNAPSHOT/repository/conf/advanced/syslogConfig.xml
> >> isn't a file.
> >>
> >> Did I miss something? I would appreciate your thoughts on this.
> >
> > Fixed by removing syslogConfig.xml related entry from
> > lb/modules/distribution/product/src/main/assembly/bin.xml.
>
> Hi Preadeeban,
>
> Did you try to start the ESB after this change?
>

Hi Supun,
I didn't change ESB. I am creating a new profile for product LB. For this, I
am incrementally removing the features from the profile copied from ESB. It
is taking me more time, as I am busy this weekend, in some personal stuff. I
will commit LB, once I verified it.

Let me know, if there is something I should take care of, in creating this
new profile for elastic load balancing for Stratos.

Thank you.
Regards,
Pradeeban.

>
> Thanks,
> Supun//
>
> >
> > Thank you.
> > Regards,
> > Pradeeban.
> >
> >>
> >> P.S: My ESB builds fine.
> >>
> >> Thank you.
> >> Regards,
> >> Pradeeban.
> >>
> >> On Fri, May 6, 2011 at 2:46 PM, Amani Soysa  wrote:
> >>>
> >>> Hi
> >>>
> >>> Its comming from the logging-mgt feature . please take an svn up in
> >>> logging-mgt feature and build.
> >>>
> >>> Regards,
> >>> Amani
> >>>
> >>> On Fri, May 6, 2011 at 2:42 PM, Danushka Menikkumbura <
> danus...@wso2.com>
> >>> wrote:
> 
>  I can not build the ESB because of missing syslogConfig.xml file. Most
>  probably I have not built a required feature, I can not locate it
> inside any
>  feature, though.
> 
>  Any idea?
> 
>  Thanks,
>  Danushka
> 
>  ___
>  Carbon-dev mailing list
>  Carbon-dev@wso2.org
>  http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> 
> >>>
> >>>
> >>> ___
> >>> Carbon-dev mailing list
> >>> Carbon-dev@wso2.org
> >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Kathiravelu Pradeeban.
> >> Software Engineer.
> >> WSO2 Inc.
> >>
> >> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
> >
> >
> >
> > --
> > Kathiravelu Pradeeban.
> > Software Engineer.
> > WSO2 Inc.
> >
> > Blog: [Llovizna] http://kkpradeeban.blogspot.com/
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
>
>
> --
> Supun Kamburugamuva
> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
> Member, Apache Software Foundation; http://www.apache.org
> WSO2 Inc.;  http://wso2.org
> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> Blog: http://supunk.blogspot.com
>



-- 
Kathiravelu Pradeeban.
Software Engineer.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] QueueService and MessageQueue

[Afkham Azeez]

On Sun, May 8, 2011 at 4:08 PM, Amila Suriarachchi  wrote:

>
>
> On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez  wrote:
>
>> We have discussed this extensively. The proper solution is to add a
>> parameter to axis2.xml which specifies the behavior of the transports
>> element not being present in the services.xml. Either this could mean,
>> expose on all transports, or don't expose on any transports. If this is
>> don't expose on any transport, the services.xml should declare the
>> transports on which this service has to be exposed. In either case, the
>> user's existing services will not simply work OOTB without some changes.
>>
>
> I think the correct solution is define the default export transports in the
> axis2.xml. By default we make it http https and local. (we can use the same
> element in the services.xml) if some one wants to add another transport it
> has to declare in the services.xml. Need to do a disscussion at the axis2
> level for this.
>

+1


>
> For these two services we will make it only available with http/s since
> other are not configured anyway.
>

+1


>
> thanks,
> Amila.
>
>
>
>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

Re: [Carbon-dev] Where the syslogConfig.xml comes from?

[Supun Kamburugamuva]

On Sun, May 8, 2011 at 12:20 PM, Kathiravelu Pradeeban
 wrote:
>
>
> On Sun, May 8, 2011 at 10:31 AM, Kathiravelu Pradeeban 
> wrote:
>>
>> Hi Amani,
>> I am creating a stripped down profile of esb (named as lb) consisting of
>> load balancing components used in ESB. For this, I have removed logging-mgt
>> feature from the p2 profile of lb, as I don't need that. Now I am getting
>> the same error when building *lb*.
>>
>> [INFO] Failed to create assembly: Error adding file to archive:
>> /home/pradeeban/trunk/stratos/carbon/products/lb/modules/distribution/product/../../p2-profile/product/target/wso2carbon-core-3.2.0-SNAPSHOT/repository/conf/advanced/syslogConfig.xml
>> isn't a file.
>>
>> Did I miss something? I would appreciate your thoughts on this.
>
> Fixed by removing syslogConfig.xml related entry from
> lb/modules/distribution/product/src/main/assembly/bin.xml.

Hi Preadeeban,

Did you try to start the ESB after this change?

Thanks,
Supun//

>
> Thank you.
> Regards,
> Pradeeban.
>
>>
>> P.S: My ESB builds fine.
>>
>> Thank you.
>> Regards,
>> Pradeeban.
>>
>> On Fri, May 6, 2011 at 2:46 PM, Amani Soysa  wrote:
>>>
>>> Hi
>>>
>>> Its comming from the logging-mgt feature . please take an svn up in
>>> logging-mgt feature and build.
>>>
>>> Regards,
>>> Amani
>>>
>>> On Fri, May 6, 2011 at 2:42 PM, Danushka Menikkumbura 
>>> wrote:

 I can not build the ESB because of missing syslogConfig.xml file. Most
 probably I have not built a required feature, I can not locate it inside 
 any
 feature, though.

 Any idea?

 Thanks,
 Danushka

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

>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> Kathiravelu Pradeeban.
>> Software Engineer.
>> WSO2 Inc.
>>
>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>
>
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 
Supun Kamburugamuva
Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org
WSO2 Inc.;  http://wso2.org
E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] QueueService and MessageQueue

[Amila Suriarachchi]

On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez  wrote:

> We have discussed this extensively. The proper solution is to add a
> parameter to axis2.xml which specifies the behavior of the transports
> element not being present in the services.xml. Either this could mean,
> expose on all transports, or don't expose on any transports. If this is
> don't expose on any transport, the services.xml should declare the
> transports on which this service has to be exposed. In either case, the
> user's existing services will not simply work OOTB without some changes.
>

I think the correct solution is define the default export transports in the
axis2.xml. By default we make it http https and local. (we can use the same
element in the services.xml) if some one wants to add another transport it
has to declare in the services.xml. Need to do a disscussion at the axis2
level for this.

For these two services we will make it only available with http/s since
other are not configured anyway.

thanks,
Amila.




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

Re: [Carbon-dev] QueueService and MessageQueue

[Hiranya Jayathilaka]

On Sun, May 8, 2011 at 1:26 PM, Afkham Azeez  wrote:

> The other problem is, even for user deployed services, when these
> transports are enabled, the service will be marked faulty. The user cannot
> use the UI to change the transports of faulty services. Think about some
> service which does not support services.xml files.


If it's a user defined service then there should be some kind of a service
descriptor to work with right? Axis2 services have the services.xml. Proxy
services have a Synapse configuration file. Data services have a dbs file
and so on.


> In such a case, how would you selectively enable only certain transports,
> when the deployment fails?


I agree that this needs to be fixed at Axis2 level proper. But right now we
have these two services always complaining about transports. No other admin
service or hidden service has this problem. So I think we should fix these 2
services right away. Since they are built-in stuff user has no choice but to
live with them.

Thanks,
Hiranya


>
>
> On Sun, May 8, 2011 at 11:49 AM, Hiranya Jayathilaka wrote:
>
>> Hi Azeez,
>>
>> On Sun, May 8, 2011 at 11:43 AM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Sun, May 8, 2011 at 11:40 AM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Sun, May 8, 2011 at 11:36 AM, Afkham Azeez  wrote:

>
>
> On Sun, May 8, 2011 at 11:34 AM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez  wrote:
>>
>>> We have discussed this extensively. The proper solution is to add a
>>> parameter to axis2.xml which specifies the behavior of the transports
>>> element not being present in the services.xml. Either this could mean,
>>> expose on all transports, or don't expose on any transports.
>>
>>
>> IIRC the idea was to make it configurable what 'all transports' mean.
>>
>>
>>
>>> If this is don't expose on any transport, the services.xml should
>>> declare the transports on which this service has to be exposed. In 
>>> either
>>> case, the user's existing services will not simply work OOTB without 
>>> some
>>> changes.
>>>
>>
>> Agreed. However I'm not too concerned about user defined services at
>> this point. User knows through which transports a service needs to be
>> exposed and he can use the features provided in our UI (service-mgt,
>> transport-mgt) to configure the services to fit his exact needs. If a
>> service needs to be exposed over a transport like VFS or mail, he can add
>> the required parameters to the service. If he doesn't, service will only 
>> be
>> exposed over HTTP/S which is not bad either.
>>
>> The problem is with our built-in admin services. User has no control
>> over these. So trying to expose them over transports for which they are 
>> not
>> configured isn't correct.
>>
>
> Admin services are supposed to be exposed only via HTTPS.
>

 I think these 2 particular services are just marked as hidden services
 (they don't show up in the UI).

>>>
>>> Is there any issue in making VFSTransport optional. Can't you keep it
>>> commented out?
>>>
>>
>> VFS transport is optional. It is commented out and not enabled by default,
>> if that's what you mean. But the above warning shows up as soon as I enable
>> it in the axis2.xml (or from the UI). And as I said it's not just for VFS.
>> Happens for just about any transport (Mail, FIX etc). Most users will be
>> concerned to see these unnecessary warnings in the log, particularly when
>> they cannot really see these services in the system.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>>

 Thanks,
 Hiranya




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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED /home/release/carbon/products/manager"

[WSO2 Release-Builder]

[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.dataservices.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.datasource.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.service.mgt.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.transport.mgt.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.event.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.event.common.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.registry.core.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.registry.core.common.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.registry.resource.properties.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.bam.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.reporting.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.reporting.ui.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.identity.relying.party.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.identity.relying.party.ui.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.identity.core.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.identity.core.ui.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.datasource.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.issue.tracker.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.load.balance.agent.server.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.load.balance.agent.ui.feature
[INFO] Copying resources
[INFO] Running Equinox P2 Publisher Application for Repository Generation
[INFO] Generating metadata for ..
[INFO] Generation completed with success [6 seconds].
[INFO] Running Equinox P2 Category Publisher Application for the Generated 
Repository
[INFO] [carbon-p2:p2-profile-gen {execution: 3-p2-profile-generation}]
[INFO] Running Equinox P2 Director Application
[ERROR] Unable to load repositories.
[ERROR] Application failed, log file location: 
/home/release/carbon/products/manager/modules/p2-profile-gen/service/target/p2-agent/configuration/1304849030703.log
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] 

[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: 
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: 
at org.wso2.maven.p2.ProfileGenMojo.execute(ProfileGenMojo.java:170)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.plugin.MojoExecutionException: 
at 
org.wso2.maven.p2.ProfileGenMojo.installFeatures(ProfileGenMojo.java:221)
at org.wso2.maven.p2.ProfileGenMojo.execute(ProfileGenMojo.java:163)
... 19 more
[INFO] 
[INFO] Total time: 1 minute 19 seco

Re: [Carbon-dev] Testing on Websphere

[Afkham Azeez]

How is the progress on this?


On Sat, May 7, 2011 at 7:20 PM, Charitha Kankanamge wrote:

> If you are getting the same error again and again, do not use the same
> profile. Always use a new profile.
>
> /Charitha
>
>
>
> On Sat, May 7, 2011 at 7:08 PM, Chamara Ariyarathne wrote:
>
>> Yes Charitha,
>>
>> I have followed the Exact procedure for couple of times, but i get the
>> same error over and over again. I'm afraid whether there is any
>> configuration mismatch (or whatever an error) in the Websphere installation
>> in my local machine.
>>
>>
>>
>>
>> On Sat, May 7, 2011 at 6:56 PM, Charitha Kankanamge wrote:
>>
>>> 1. First, check whether you have created websphere profile as mentioned
>>> in [1]. Do not start WebSphere as a windows service
>>> 2. Next, install 3.2.0 product as instructed in [2]. The differences of
>>> 3.0.1 to 3.2.0 are;
>>>
>>> - webapps directory is located at CARBON_HOME/lib/core
>>> - No resources directory. resources directory is inside repository dir
>>> - You need to copy the jars inside CARBON_HOME/lib/api to the webapp lib
>>> directory (CARBON_HOME/lib/core/WEB-INF/lib)
>>>
>>> Do not miss any instruction. The issue you are facing should be a config
>>> error because I was able to install DSS build on WebSphere 7 in our test
>>> setup without any issue.
>>>
>>> [1]http://wso2.org/library/2735#pre_webs
>>> [2]
>>> http://wso2.org/library/knowledge-base/2011/02/running-wso2-carbon301-based-products-ibm-websphere-61
>>>
>>> /Charitha
>>>
>>>
>>>
>>> On Sat, May 7, 2011 at 3:49 PM, Chamara Ariyarathne 
>>> wrote:
>>>
 Sorry, The error at Websphere log is [1]
 Charitha, please help me on this.

 [1]
 [5/7/11 15:37:16:993 IST] 0019 webappE
 com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet
 Error]-[bridgeservlet]: java.lang.IllegalStateException: instance already
 set
 at
 org.wso2.carbon.bridge.BridgeServlet.setInstance(BridgeServlet.java:218)
 at org.wso2.carbon.bridge.BridgeServlet.init(BridgeServlet.java:56)
 at javax.servlet.GenericServlet.init(GenericServlet.java:241)
 at
 com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
 at
 com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
 at
 com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:737)
 at
 com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
 at
 com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
 at
 com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3826)
 at
 com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
 at
 com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
 at
 com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
 at
 com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
 at
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
 at
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
 at
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:272)
 at
 com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1016)
 at
 com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:639)
 at
 com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1772)
 at
 com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
 at
 com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
 at
 com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
 at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
 at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
 at
 com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
 at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)



 On Sat, May 7, 2011 at 3:44 PM, Chamara Ariyarathne 
 wrote:

> Hi,
>
> After all the configurations and start of the carbon server as a
> service on Websphere i get this error when accessing the carbon server 
> url;
>
> Error 500: javax.servlet.ServletException: SRVE0207E: Uncaught
> initialization exception created by servlet
>
> I'm still looking into this
>
>
>
>
>
>
> O

Re: [Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[Afkham Azeez]

Somebody who has access to this instance please stop this process. It is
just spamming this mailing list.


On Sun, May 8, 2011 at 2:55 PM, WSO2 EC2 Stratos Builder
wrote:

> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> [INFO] [install:install {execution: default-install}]
> [INFO] Installing /home/stratos/carbon/dependencies/rampart/pom.xml to
> /home/stratos/.m2/repository/org/apache/rampart/rampart-project/1.6.1-wso2v1/rampart-project-1.6.1-wso2v1.pom
> [INFO]
> 
> [INFO] Building Rampart - Policy
> [INFO]task-segment: [clean, install]
> [INFO]
> 
> [INFO] [clean:clean {execution: default-clean}]
> [INFO] Deleting
> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
> [INFO] [incremental-build:incremental-build {execution: default}]
> [INFO] Verifying module descriptor ...
> [INFO] Pom descriptor modification detected.
> [INFO] Deleting
> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
> [INFO] [remote-resources:process {execution: default}]
> [INFO] [resources:resources {execution: default-resources}]
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO] [compiler:compile {execution: default-compile}]
> Compiling 92 source files to
> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target/classes
> [INFO] [resources:testResources {execution: default-testResources}]
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/src/test/resources
> [INFO] Copying 3 resources
> [INFO] [compiler:testCompile {execution: default-testCompile}]
> [INFO] Not compiling test sources
> [INFO] [surefire:test {execution: default-test}]
> [INFO] Tests are skipped.
> [INFO] [jar:jar {execution: default-jar}]
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error assembling JAR
>
> Embedded error: Failed to read filesystem attributes for:
> /home/stratos/carbon/dependencies/rampart/modules/rampart-policy/pom.xml
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 34 minutes 54 seconds
> [INFO] Finished at: Sun May 08 09:25:35 UTC 2011
> [INFO] Final Memory: 1192M/1820M
> [INFO]
> 
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



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

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 EC2 Stratos Builder]

[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/stratos/carbon/dependencies/rampart/pom.xml to 
/home/stratos/.m2/repository/org/apache/rampart/rampart-project/1.6.1-wso2v1/rampart-project-1.6.1-wso2v1.pom
[INFO] 
[INFO] Building Rampart - Policy
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting 
/home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting 
/home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
Compiling 92 source files to 
/home/stratos/carbon/dependencies/rampart/modules/rampart-policy/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/stratos/carbon/dependencies/rampart/modules/rampart-policy/src/test/resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Not compiling test sources
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error assembling JAR

Embedded error: Failed to read filesystem attributes for: 
/home/stratos/carbon/dependencies/rampart/modules/rampart-policy/pom.xml
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 34 minutes 54 seconds
[INFO] Finished at: Sun May 08 09:25:35 UTC 2011
[INFO] Final Memory: 1192M/1820M
[INFO] 
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] QueueService and MessageQueue

[Afkham Azeez]

The other problem is, even for user deployed services, when these transports
are enabled, the service will be marked faulty. The user cannot use the UI
to change the transports of faulty services. Think about some service which
does not support services.xml files. In such a case, how would you
selectively enable only certain transports, when the deployment fails?


On Sun, May 8, 2011 at 11:49 AM, Hiranya Jayathilaka wrote:

> Hi Azeez,
>
> On Sun, May 8, 2011 at 11:43 AM, Afkham Azeez  wrote:
>
>>
>>
>> On Sun, May 8, 2011 at 11:40 AM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Sun, May 8, 2011 at 11:36 AM, Afkham Azeez  wrote:
>>>


 On Sun, May 8, 2011 at 11:34 AM, Hiranya Jayathilaka 
 wrote:

>
>
> On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez  wrote:
>
>> We have discussed this extensively. The proper solution is to add a
>> parameter to axis2.xml which specifies the behavior of the transports
>> element not being present in the services.xml. Either this could mean,
>> expose on all transports, or don't expose on any transports.
>
>
> IIRC the idea was to make it configurable what 'all transports' mean.
>
>
>> If this is don't expose on any transport, the services.xml should
>> declare the transports on which this service has to be exposed. In either
>> case, the user's existing services will not simply work OOTB without some
>> changes.
>>
>
> Agreed. However I'm not too concerned about user defined services at
> this point. User knows through which transports a service needs to be
> exposed and he can use the features provided in our UI (service-mgt,
> transport-mgt) to configure the services to fit his exact needs. If a
> service needs to be exposed over a transport like VFS or mail, he can add
> the required parameters to the service. If he doesn't, service will only 
> be
> exposed over HTTP/S which is not bad either.
>
> The problem is with our built-in admin services. User has no control
> over these. So trying to expose them over transports for which they are 
> not
> configured isn't correct.
>

 Admin services are supposed to be exposed only via HTTPS.

>>>
>>> I think these 2 particular services are just marked as hidden services
>>> (they don't show up in the UI).
>>>
>>
>> Is there any issue in making VFSTransport optional. Can't you keep it
>> commented out?
>>
>
> VFS transport is optional. It is commented out and not enabled by default,
> if that's what you mean. But the above warning shows up as soon as I enable
> it in the axis2.xml (or from the UI). And as I said it's not just for VFS.
> Happens for just about any transport (Mail, FIX etc). Most users will be
> concerned to see these unnecessary warnings in the log, particularly when
> they cannot really see these services in the system.
>
> Thanks,
> Hiranya
>
>
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>>
>>>


>
> Thanks,
> Hiranya
>
>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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


 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://bl

[Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[WSO2 EC2 Stratos Builder]

[INFO] Not compiling test sources
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[axis2-webapp] in 
[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2-1.6.1-wso2v1]
[INFO] Processing war project
[INFO] Copying webapp 
webResources[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/webResources]
 
to[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2-1.6.1-wso2v1]
[INFO] Copying webapp 
webResources[/home/stratos/carbon/dependencies/axis2/modules/webapp/../../legal]
 
to[/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2-1.6.1-wso2v1]
[INFO] Copying webapp 
resources[/home/stratos/carbon/dependencies/axis2/modules/webapp/src/main/webapp]
[INFO] Webapp assembled in [20278 msecs]
[INFO] Building war: 
/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2.war
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/stratos/carbon/dependencies/axis2/modules/webapp/target/axis2.war to 
/home/stratos/.m2/repository/org/apache/axis2/axis2-webapp/1.6.1-wso2v1/axis2-webapp-1.6.1-wso2v1.war
[INFO] 
[INFO] Building Apache Axis2 - Root
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting /home/stratos/carbon/dependencies/axis2/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting /home/stratos/carbon/dependencies/axis2/target
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] Parent project loaded from repository.
[INFO] [assembly:single {execution: package-jar}]
[INFO] Reading assembly descriptor: src/main/assembly/jar.xml
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to create assembly: Failed to retrieve OS environment variables. 
Reason: Cannot run program "env": java.io.IOException: error=12, Cannot 
allocate memory

[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 27 minutes 25 seconds
[INFO] Finished at: Sun May 08 07:21:18 UTC 2011
[INFO] Final Memory: 1064M/1754M
[INFO] 
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev