[Carbon-dev] Carbon-3.0.0 Iridium - 4RC22

[Milinda Pathirage]

http://builder.wso2.org/~carbon/releases/carbon/3.0.0/4RC22/

Thanks
Milinda

-- 
Milinda Pathirage
Technical Lead and Product Manager, Business Process Server - WSO2 Inc;
http://wso2.com
Blog: http://blog.mpathirage.com

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

Re: [Carbon-dev] Carbon DB H2 Version

[Samisa Abeysinghe]

Should we update H2 version on trunk?

We are using 1.1.112
Latest is 1.2.135

Samisa...

On Sun, May 16, 2010 at 7:26 AM, Danushka Menikkumbura wrote:

> Using 1.1.112 solved the issue. Thanks Dimuthu.
>
> Danushka
>
>
> On Sat, May 15, 2010 at 7:31 PM, Dimuthu Gamage  wrote:
>
>> Here is an guide on how to configure to use remote H2.
>> http://wso2.org/project/registry/3.5.0/docs/installation_guide/db_h2.html
>>
>> Thanks
>> Dimuthu
>>
>>
>> On Sat, May 15, 2010 at 6:58 PM, Dimuthu Gamage  wrote:
>>
>>> Hi,
>>> In trunk we are using h2 1.1.112. In carbon it was possible to open an h2
>>> console by just uncommenting some entries in the carbon.xml, but it seems
>>> broken in trunk. So the other option you can do is just run the h2 server
>>> and connect h2 in the remote manner (not as embedded way). That way you can
>>> connect to h2 server from different version.
>>>
>>> Thanks
>>> Dimuthu
>>>
>>> On Sat, May 15, 2010 at 11:09 AM, Danushka Menikkumbura <
>>> danus...@wso2.com> wrote:
>>>
 I need to create a couple of new tables in the Carbon database. When I
 try to connect to the database using the H2 console I get the error [1].
 This is clearly due to connecting to an older version using a newer 
 console.
 I am using 1.2.135. Can someone please let me know the H2 version used
 in Carbon?. Any workaround would also help for the time being.

 [1] - Unsupported database file version or invalid file header in file
 "Old database:
 E:\carbon\trunk\wso2carbon-3.0.0-SNAPSHOT\repository\database\WSO2CARBON_DB.data.db
 - please convert the database to a SQL script and re-create it." 
 [90048-135]
  90048/90048

 Danushka

 --
 Danushka Menikkumbura
 Technical Lead & Product Manager, WSO2 SOA Enablement Server

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

 phone : +94 77 364 1754
 blog : http://danushka-menikkumbura.blogspot.com/

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

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


>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Danushka Menikkumbura
> Technical Lead & Product Manager, WSO2 SOA Enablement Server
>
> WSO2, Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> phone : +94 77 364 1754
> blog : http://danushka-menikkumbura.blogspot.com/
>
> Disclaimer: This communication may contain privileged or other confidential
> information and is intended exclusively for the addressee/s. If you are not
> the intended recipient/s, or believe that you may have received this
> communication in error, please reply to the sender indicating that fact and
> delete the copy you received and in addition, you should not print, copy,
> retransmit, disseminate, or otherwise use the information contained in this
> communication. Internet communications cannot be guaranteed to be timely,
> secure, error or virus-free. The sender does not accept liability for any
> errors or omissions.
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Samisa Abeysinghe]

On Fri, Jun 4, 2010 at 7:44 PM, Hiranya Jayathilaka wrote:

>
>
> On Fri, Jun 4, 2010 at 7:42 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Fri, Jun 4, 2010 at 7:30 PM, Supun Kamburugamuva wrote:
>>
>>> On Fri, Jun 4, 2010 at 4:52 AM, Hiranya Jayathilaka 
>>> wrote:
>>> > Hi,
>>> >
>>> > On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva 
>>> wrote:
>>> >>
>>> >> When we try to update the ESB 3.0.0 configuration some times it takes
>>> >> a very long time. Also sometimes there are errors printing on the
>>> >> console saying invalid XML configurations without no apparent reason.
>>> >
>>> > I think you are talking about the popup dialog that occurs at times in
>>> the
>>> > UI. There is a UI level validation which checks the XML input for
>>> accuracy
>>> > before invoking the admin services. This is what shows the above error.
>>> It
>>> > is a simple JavaScript validation and hence it cannot log the error to
>>> the
>>> > log files. It can only show an error dialog.
>>> > However if it does show you the above error, that's definitely because
>>> there
>>> > was something wrong in the input XML. Please check the isValidXML
>>> method in
>>> > configcommon.js for details.
>>>
>>> As far as I remember the error didn't come from the front end. If so I
>>> wouldn't even talk about it here. It was a back-end error.
>>>
>>
>> That's strange. We only use AXIOM at the backend to handle XML. So this
>> means there is either some bug in one of our serializers (which produces
>> invalid xml) or there's a bug in AXIOM.
>>
>
> Since hand edited XML is involved in this scenario it could be due to a
> wrong input too.
>

Then we can reproduce, can't we?

Samisa...


>
> Thanks,
> Hiranya
>
>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Thanks,
>>> Supun..
>>>
>>> > Thanks,
>>> > Hiranya
>>> >
>>> >>
>>> >> When this happens ESB becomes unstable. I think these are issues that
>>> >> we need to figure out and fix.
>>> >>
>>> >> I'll create Jira's for these.
>>> >>
>>> >> Thanks,
>>> >> Supun..
>>> >>
>>> >> ___
>>> >> Carbon-dev mailing list
>>> >> Carbon-dev@wso2.org
>>> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >
>>> >
>>> >
>>> > --
>>> > Hiranya Jayathilaka
>>> > Senior Software Engineer;
>>> > WSO2 Inc.;  http://wso2.org
>>> > E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> > Blog: http://techfeast-hiranya.blogspot.com
>>> >
>>> > ___
>>> > Carbon-dev mailing list
>>> > Carbon-dev@wso2.org
>>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >
>>> >
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Hiranya Jayathilaka]

On Fri, Jun 4, 2010 at 7:42 PM, Hiranya Jayathilaka wrote:

>
>
> On Fri, Jun 4, 2010 at 7:30 PM, Supun Kamburugamuva wrote:
>
>> On Fri, Jun 4, 2010 at 4:52 AM, Hiranya Jayathilaka 
>> wrote:
>> > Hi,
>> >
>> > On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva 
>> wrote:
>> >>
>> >> When we try to update the ESB 3.0.0 configuration some times it takes
>> >> a very long time. Also sometimes there are errors printing on the
>> >> console saying invalid XML configurations without no apparent reason.
>> >
>> > I think you are talking about the popup dialog that occurs at times in
>> the
>> > UI. There is a UI level validation which checks the XML input for
>> accuracy
>> > before invoking the admin services. This is what shows the above error.
>> It
>> > is a simple JavaScript validation and hence it cannot log the error to
>> the
>> > log files. It can only show an error dialog.
>> > However if it does show you the above error, that's definitely because
>> there
>> > was something wrong in the input XML. Please check the isValidXML method
>> in
>> > configcommon.js for details.
>>
>> As far as I remember the error didn't come from the front end. If so I
>> wouldn't even talk about it here. It was a back-end error.
>>
>
> That's strange. We only use AXIOM at the backend to handle XML. So this
> means there is either some bug in one of our serializers (which produces
> invalid xml) or there's a bug in AXIOM.
>

Since hand edited XML is involved in this scenario it could be due to a
wrong input too.

Thanks,
Hiranya


> Thanks,
> Hiranya
>
>
>>
>> Thanks,
>> Supun..
>>
>> > Thanks,
>> > Hiranya
>> >
>> >>
>> >> When this happens ESB becomes unstable. I think these are issues that
>> >> we need to figure out and fix.
>> >>
>> >> I'll create Jira's for these.
>> >>
>> >> Thanks,
>> >> Supun..
>> >>
>> >> ___
>> >> Carbon-dev mailing list
>> >> Carbon-dev@wso2.org
>> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> > --
>> > Hiranya Jayathilaka
>> > Senior Software Engineer;
>> > WSO2 Inc.;  http://wso2.org
>> > E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> > Blog: http://techfeast-hiranya.blogspot.com
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



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

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Hiranya Jayathilaka]

On Fri, Jun 4, 2010 at 7:30 PM, Supun Kamburugamuva  wrote:

> On Fri, Jun 4, 2010 at 4:52 AM, Hiranya Jayathilaka 
> wrote:
> > Hi,
> >
> > On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva 
> wrote:
> >>
> >> When we try to update the ESB 3.0.0 configuration some times it takes
> >> a very long time. Also sometimes there are errors printing on the
> >> console saying invalid XML configurations without no apparent reason.
> >
> > I think you are talking about the popup dialog that occurs at times in
> the
> > UI. There is a UI level validation which checks the XML input for
> accuracy
> > before invoking the admin services. This is what shows the above error.
> It
> > is a simple JavaScript validation and hence it cannot log the error to
> the
> > log files. It can only show an error dialog.
> > However if it does show you the above error, that's definitely because
> there
> > was something wrong in the input XML. Please check the isValidXML method
> in
> > configcommon.js for details.
>
> As far as I remember the error didn't come from the front end. If so I
> wouldn't even talk about it here. It was a back-end error.
>

That's strange. We only use AXIOM at the backend to handle XML. So this
means there is either some bug in one of our serializers (which produces
invalid xml) or there's a bug in AXIOM.

Thanks,
Hiranya


>
> Thanks,
> Supun..
>
> > Thanks,
> > Hiranya
> >
> >>
> >> When this happens ESB becomes unstable. I think these are issues that
> >> we need to figure out and fix.
> >>
> >> I'll create Jira's for these.
> >>
> >> Thanks,
> >> Supun..
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
> >
> > --
> > Hiranya Jayathilaka
> > Senior Software Engineer;
> > WSO2 Inc.;  http://wso2.org
> > E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> > Blog: http://techfeast-hiranya.blogspot.com
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



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

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Supun Kamburugamuva]

On Fri, Jun 4, 2010 at 4:52 AM, Hiranya Jayathilaka  wrote:
> Hi,
>
> On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva  wrote:
>>
>> When we try to update the ESB 3.0.0 configuration some times it takes
>> a very long time. Also sometimes there are errors printing on the
>> console saying invalid XML configurations without no apparent reason.
>
> I think you are talking about the popup dialog that occurs at times in the
> UI. There is a UI level validation which checks the XML input for accuracy
> before invoking the admin services. This is what shows the above error. It
> is a simple JavaScript validation and hence it cannot log the error to the
> log files. It can only show an error dialog.
> However if it does show you the above error, that's definitely because there
> was something wrong in the input XML. Please check the isValidXML method in
> configcommon.js for details.

As far as I remember the error didn't come from the front end. If so I
wouldn't even talk about it here. It was a back-end error.

Thanks,
Supun..

> Thanks,
> Hiranya
>
>>
>> When this happens ESB becomes unstable. I think these are issues that
>> we need to figure out and fix.
>>
>> I'll create Jira's for these.
>>
>> Thanks,
>> Supun..
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

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

Re: [Carbon-dev] [Code Review] 2010/03/24 Gadget Dashboard

[Nuwan Bandara]

Hi,

The Due tasks are completed.

On Fri, Jun 4, 2010 at 11:25 AM, Nuwan Bandara  wrote:

> Hi Azeez,
>
> Due to the release work on 3.0.0 and cloud GS, I could not adopt the major
> changes we have discussed. I will be able to complete the rest of tasks by
> next week. Completed tasks are as follows.
>
>  On Wed, Mar 24, 2010 at 5:39 PM, Ruchira Wageesha wrote:
>
>>
>>- Need proper documentation for creating and configuring dashboard.xml
>>
>>
>>- Structure of dashboard.xml should be easily understandable/readable
>>
>>
>>- Using JSON format for dashboard.xml would not be appropriate, a
>>   proper xml structure should be there
>>   - Anyway, using JSON for gadgets and xml for the layout might be
>>   appropriate
>>
>> We are planing to replace the entire dashboard.xml model with our coming
> up template system. Hence did not invest much time on this, however I will
> write a wiki page, for the use of previous dashboard versions.
>

Done | http://wso2.org/wiki/display/GS/WSO2+Dashboard+Architecture

>
>>- Get rid of common bundle
>>
>> Since this is a major change in dashboard components we postponed this
> till the release is done. I will incorporate these changes by next week.
>

Done.

>
>>- Need to check whether debug is enabled before logging
>>
>>  Done.
>
>>
>>- Exceptions should be properly handled
>>
>>
>>-  Should be able to quickly identify any error with stacktrace and
>>   logs
>>
>> Done, all exceptions are logged with a message and the stack-trace.
>
>>
>>-  Logging message should be added to the exception
>>
>> Done.
>
>>
>>-  Exceptions shouldn't be swallowed, if not in any case, should be
>>   properly commented the reason
>>
>> Done.
>
>>
>>-  Throwing AxisFault with an error code/message and handing it
>>   accordingly
>>
>> Need to complete, since we had to change most of the dashboard server and
> UI bundles, to handle axis faults from the FE, we postponed it till the
> release work is over.
>

Added the necessary changes

>
>>- Need to think about distributed nature
>>
>>
>>- Availability of resources should be checked properly before using
>>   them.
>>
>> Done.
>
>>
>>- i.e. we should check whether the registry is available and failure
>>   conditions should be handled
>>
>> Done.
>
>>
>>- Add a mothod into carbon utils to get backend http port
>>
>> Done

>
>>
>>
>>- Proper coding to avoid unnecessary memory usage.
>>
>>
>>- e.g. defining error message separatly and passing it into the
>>   debug() method
>>
>> Done.
>
>>
>>- Using readable variable names
>>
>>
>>- e.g. boolean variable names should start with is, "isNewUser"
>>
>> Done.
>
>>
>>- Using primitive data types where possible as object initiation
>>wastes more resources
>>
>> Done.
>
>>
>>- Remove unnecessary parenthesis
>>
>> Done.
>
>>
>>- Extract repetitive codes and use methods instead
>>
>>
>>- both in Java and Javascript
>>
>> Done.
>
>>
>>- Remove redundant varialbes
>>
>> Done.
>
>>
>>- Comments should be added
>>
>>
>>- At Java class declaration(describing the class)
>>   - In Javascripts codes
>>
>> Done.
>
>>
>>- Proper coding convension should be followed across the plaltform for
>>Javascripts
>>
>> I reviewed few coding standards on JS, I will send a mail regarding that
> to @Archtecture ASAP
>
>>
>>
>>
>>- Get rid of using CDATA in gadgets as it is difficult to validate the
>>JS code
>>
>>
>>- Separate JS code into files and use references to those files
>>   instead
>>
>> This should be practised by all gadget developers, in referent product
> teams. Gadgets in GS are quite primitives and does not need external JS
> links.
>
>>
>> *Proposed Features*
>>
>>- User specific gadget repo (i.e. giving users a registry space to
>>store gadgets) and gadget sharing
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>

Thanks & Regards
-- 
Nuwan Bandara
Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware

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

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Hiranya Jayathilaka]

On Fri, Jun 4, 2010 at 3:14 PM, Samisa Abeysinghe  wrote:

> It is kind of pointless to validate if the validation cannot say what is
> wrong. Specially with something like XML, it is hard for the user to locate
> the error if the error message is not precise.


This validation has been around as long as I've known. If it is needless we
can get rid of it for a future release. May be we can do some Java
validation in the ConfigAdminClient instead?

Thanks,
Hiranya


>
> JS validation is good for simple fields, not that useful for something
> which is a bit complex like this.
> Note that, most users are not XML experts like we developers are, so they
> find it difficult to loacte problems without telling them where the problem
> really is.
>
> Samisa...
>
>
> On Fri, Jun 4, 2010 at 2:22 PM, Hiranya Jayathilaka wrote:
>
>> Hi,
>>
>> On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva wrote:
>>
>>> When we try to update the ESB 3.0.0 configuration some times it takes
>>> a very long time. Also sometimes there are errors printing on the
>>> console saying invalid XML configurations without no apparent reason.
>>>
>>
>> I think you are talking about the popup dialog that occurs at times in the
>> UI. There is a UI level validation which checks the XML input for accuracy
>> before invoking the admin services. This is what shows the above error. It
>> is a simple JavaScript validation and hence it cannot log the error to the
>> log files. It can only show an error dialog.
>>
>> However if it does show you the above error, that's definitely because
>> there was something wrong in the input XML. Please check the isValidXML
>> method in configcommon.js for details.
>>
>>  Thanks,
>> Hiranya
>>
>>
>>> When this happens ESB becomes unstable. I think these are issues that
>>> we need to figure out and fix.
>>>
>>> I'll create Jira's for these.
>>>
>>> Thanks,
>>> Supun..
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Samisa Abeysinghe]

It is kind of pointless to validate if the validation cannot say what is
wrong. Specially with something like XML, it is hard for the user to locate
the error if the error message is not precise.

JS validation is good for simple fields, not that useful for something which
is a bit complex like this.
Note that, most users are not XML experts like we developers are, so they
find it difficult to loacte problems without telling them where the problem
really is.

Samisa...


On Fri, Jun 4, 2010 at 2:22 PM, Hiranya Jayathilaka wrote:

> Hi,
>
> On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva wrote:
>
>> When we try to update the ESB 3.0.0 configuration some times it takes
>> a very long time. Also sometimes there are errors printing on the
>> console saying invalid XML configurations without no apparent reason.
>>
>
> I think you are talking about the popup dialog that occurs at times in the
> UI. There is a UI level validation which checks the XML input for accuracy
> before invoking the admin services. This is what shows the above error. It
> is a simple JavaScript validation and hence it cannot log the error to the
> log files. It can only show an error dialog.
>
> However if it does show you the above error, that's definitely because
> there was something wrong in the input XML. Please check the isValidXML
> method in configcommon.js for details.
>
> Thanks,
> Hiranya
>
>
>> When this happens ESB becomes unstable. I think these are issues that
>> we need to figure out and fix.
>>
>> I'll create Jira's for these.
>>
>> Thanks,
>> Supun..
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Error on ESB startup

[Isuru Suriarachchi]

[2010-06-04 14:39:21,621]  INFO - XMLConfigurationBuilder Generating the
Synapse configuration model by parsing the XML configuration
[2010-06-04 14:39:21,707] ERROR - ConfigurationFactoryAndSerializerFinder
Unknown Configuration type referenced by configuration element : {
http://ws.apache.org/ns/synapse}definitions
[2010-06-04 14:39:21,708] FATAL - ServiceBusInitializer Couldn't initialize
the ESB...
org.apache.synapse.SynapseException: Unknown Configuration type referenced
by configuration element : {http://ws.apache.org/ns/synapse}definitions
at
org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.getConfiguration(ConfigurationFactoryAndSerializerFinder.java:155)
at
org.apache.synapse.config.xml.XMLConfigurationBuilder.getConfiguration(XMLConfigurationBuilder.java:46)
at
org.apache.synapse.config.xml.MultiXMLConfigurationBuilder.createConfigurationFromSynapseXML(MultiXMLConfigurationBuilder.java:132)
at
org.apache.synapse.config.xml.MultiXMLConfigurationBuilder.getConfiguration(MultiXMLConfigurationBuilder.java:96)
at
org.apache.synapse.config.SynapseConfigurationBuilder.getConfiguration(SynapseConfigurationBuilder.java:96)
at
org.apache.synapse.Axis2SynapseController.createSynapseConfiguration(Axis2SynapseController.java:381)
at
org.wso2.carbon.mediation.initializer.CarbonSynapseController.createSynapseConfiguration(CarbonSynapseController.java:100)
at org.apache.synapse.ServerManager.start(ServerManager.java:181)
at
org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:342)
at
org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:133)
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)


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

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Hiranya Jayathilaka]

Hi,

On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva  wrote:

> When we try to update the ESB 3.0.0 configuration some times it takes
> a very long time. Also sometimes there are errors printing on the
> console saying invalid XML configurations without no apparent reason.
>

I think you are talking about the popup dialog that occurs at times in the
UI. There is a UI level validation which checks the XML input for accuracy
before invoking the admin services. This is what shows the above error. It
is a simple JavaScript validation and hence it cannot log the error to the
log files. It can only show an error dialog.

However if it does show you the above error, that's definitely because there
was something wrong in the input XML. Please check the isValidXML method in
configcommon.js for details.

Thanks,
Hiranya


> When this happens ESB becomes unstable. I think these are issues that
> we need to figure out and fix.
>
> I'll create Jira's for these.
>
> Thanks,
> Supun..
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



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

Re: [Carbon-dev] Experiencing long delays while updating ESB configurations

[Evanthika Amarasiri]

Hi Supun,

Could you provide some more information about your cluster configuration?
E.g.:- No of active nodes in the cluster, etc.

Thanks,
Evanthika

On Thu, Jun 3, 2010 at 11:35 PM, Supun Kamburugamuva  wrote:

> Red Hat Enterprise Linux Server release 5.4 (Tikanga)
> 2.6.18-128.el5 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
>
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
>
> Thanks,
> Supun..
>
> On Thu, Jun 3, 2010 at 11:22 PM, Charitha Kankanamge 
> wrote:
> > Hi,
> >
> > What is the OS and JDK version? We will try to reproduce however please
> try
> > to capture the logs and provide us with the exact steps (specially the
> > details about cluster setup) when you encounter the issue again.
> Evanthika
> > has already tried to reproduce an error you guys have faced with, but she
> > could not.
> >
> > Regards
> > Charitha
> >
> >
> >
> > On Thu, Jun 3, 2010 at 11:11 PM, Supun Kamburugamuva 
> wrote:
> >>
> >> This happens when we go to the source view and update the
> >> configurations. It seems random. Most of the time update happens
> >> correctly. But sometimes it takes a lot of time.
> >>
> >> We are in a cluster. We have mounted the ESB configuration registry
> >> and ESB governance registry to a mySql database.
> >>
> >> Thanks,
> >> Supun..
> >>
> >> On Thu, Jun 3, 2010 at 11:02 PM, Samisa Abeysinghe 
> >> wrote:
> >> > What elements did you try to update? How?
> >> > How can this be reproduced?
> >> > Samisa...
> >> >
> >> > On Thu, Jun 3, 2010 at 10:46 PM, Supun Kamburugamuva 
> >> > wrote:
> >> >>
> >> >> When we try to update the ESB 3.0.0 configuration some times it takes
> >> >> a very long time. Also sometimes there are errors printing on the
> >> >> console saying invalid XML configurations without no apparent reason.
> >> >> When this happens ESB becomes unstable. I think these are issues that
> >> >> we need to figure out and fix.
> >> >>
> >> >> I'll create Jira's for these.
> >> >>
> >> >> Thanks,
> >> >> Supun..
> >> >>
> >> >> ___
> >> >> Carbon-dev mailing list
> >> >> Carbon-dev@wso2.org
> >> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >> >
> >> > Samisa Abeysinghe
> >> > VP Engineering
> >> > WSO2 Inc.
> >> > http://wso2.com
> >> > http://wso2.org
> >> >
> >> > ___
> >> > Carbon-dev mailing list
> >> > Carbon-dev@wso2.org
> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >> >
> >> >
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Code -Review]- 2010/03/31 - Reporting Component

[Ajith Vitharana]

I have created the JIRAs for pending tasks.

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

Re: [Carbon-dev] [Code -Review]- 2010/03/31 - Reporting Component

[Afkham Azeez]

Please create JIRAs for pending items, and let us know by when these can be
completed.

Thanks
Azeez

On Fri, Jun 4, 2010 at 12:27 PM, Ajith Vitharana  wrote:

> Hi Azeez,
>
> On Wed, Mar 31, 2010 at 5:06 PM, Heshan Suriyaarachchi wrote:
>
>> Code Review notes for Reporting Component.
>>
>> 1) Jasper report project files should go into svn.
>>
> * Done
>
>> 2) DeployedServicesReportDataCollector class:
>> Multiple people can call the AdmiService therefore report generation
>> should not be static. It should be associated  with session.
>>
>>-  Display upto date report vs. display report from the data available
>>in the UI (rather than doing a backend call).
>>-  The report should be request scoped.
>>
>> * Done
>
>>
>>-
>>
>> 3) DeployedServicesReportBean class:
>> variable scopes should be private.
>>
>>- Use idea shortcuts to generate javadoc comments.
>>
>> * temporary removed this class from service-mgt.
>
>>
>>-
>>
>> 4) Consider generating customisable reports. Consider Multitency when
>> doing this.
>
>  * pending
>
>>
>> 5) report.xml file should be renamed to reports.xml
>>
>>- Change the element flow in the reports.xml
>>- Under the report element there should be an attribute called
>>datasource.
>>- Treat report as a first class (first level) element.
>>
>> * reports.xml configuration file removed from reporting component.
>
>
>> 6) service_mgt.jsp
>>
>>- Create a taglib. This is a much cleaner approach. Therefore by
>>including this taglib a user can get this behavior.
>>- Don't hard code the report name. Name the report according to the
>>query. Dynamically pass a value and generate the report name. If a value 
>> is
>>not passed throw an exception.
>>
>> * Done
>
>> 7) Remove service-mgt stuff from the reporting component.
>
> * Done
>
>> 8) Before rendering the report, the .jasper file is generated at a temp
>> location.  Move this .jasper file to a correct location.
>
> * pending
>
>>
>> 9) Merge the reporting.commons and reporting.utils bundles and create
>> reporting.api bundle.
>>
>>- Move the ReportingException class and ReportingDataSource Interface
>>to reporting.api bundle.
>>
>> * Done
>
>>
>>-
>>
>> 10) Use generics when using Collections.
>>
> * Done
>
>> 11) ReportDataSorce class:
>>
>>- Refactor the return type from Collection to a List, in the
>>generateBeanCollectionDataSource().
>>
>> * Done
>
>>
>>
>>  12) BeanCollectionReport class:
>>
>>- Method comments should be a single block.
>>- Class attributes should be private.
>>- Rather than traversing the whole OM structure to find the details
>>you want; Build the object model and then do the operations. it's much 
>> more
>>efficient.
>>- Do not log the excpetion here, just throw the exception up.
>>- Instead of having multiple try catch blocks, merge the try blocks to
>>one try block.
>>
>> * Done
>
>>
>>-
>>
>> 13) Modify the logic in the BeanCollectionDataSourceManager in accordance
>> to above mentioned changes.
>>
>>- validateDataSource() should be renamed to toJRDataSource().
>>
>> *  Directly creating  JRDataSource bean collection  validation part
> removed.
>
>>
>>-
>>
>> 14) Move the ReportDefinitionOmGen's methods to a utility class.
>>
>>- Remove blank lines between lines.
>>- After the log.error, wrap it and throw an exception.
>>- Remember to throw exception with the context and let the consumer
>>handle the exception.
>>
>> *  Done ,ReportDefinitionOmGen renamed to createOMElement
>
>>
>>-
>>
>>
>> NOTE: Code review stopped at line # 115 of BeanCollectionReport class.
>> Next Code Review session will start from there onwards.
>>
>>
>> --
>> Regards,
>> Heshan Suriyaarachchi
>> WSO2, Inc.: http://www.wso2.com/
>>
>> Blog: http://heshans.blogspot.com/
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Afkham Azeez
Senior Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.;
http://wso2.com, Lean . Enterprise . Middleware
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
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Exception at Server startup

[Nuwan Bandara]

Hi guys,

I am getting the following exception while starting the server.

[2010-06-04 12:33:23,146]  WARN -  Error registering a MBean with objectname
' org.apache.axis2:Type=Transport,ConnectorName=tcp-sender ' for JMX
management
javax.management.InstanceAlreadyExistsException:
org.apache.axis2:Type=Transport,ConnectorName=tcp-sender
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at
org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
at
org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
at
org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
at
org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
at
org.wso2.carbon.core.init.CarbonServerManager.getClientConfigurationContext(CarbonServerManager.java:480)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:386)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:242)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)

This is a new trunk built GS. any idea ?

Thanks & regards
-- 
Nuwan Bandara
Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware

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