Hi Sameera,
On Mon, Mar 5, 2012 at 12:57 PM, Sameera Jayasoma same...@wso2.com wrote:
Hi Subash,
What is the status of this error? Would you be able to have a look?
I was able to reproduce Endpoint test failures initially. And couldn't find
a exact reason for the failures after going
On Mon, Mar 5, 2012 at 1:42 PM, Subash Chaturanga sub...@wso2.com wrote:
Hi Sameera,
On Mon, Mar 5, 2012 at 12:57 PM, Sameera Jayasoma same...@wso2.comwrote:
Hi Subash,
What is the status of this error? Would you be able to have a look?
Mistaken the thread for governance api test
I suggest that while keeping; https://svn.wso2.org/repos/wso2/trunk as it
is, to come up with the new structure.
1. https://svn.wso2.org/repos/wso2/carbon/kernel/[trunk | branches | tags]
2. https://svn.wso2.org/repos/wso2/carbon/platform/[trunk | branches | tags]
3.
Hi All,
I noticed this behavior in some bundle.
This pom [1] file hasn't defined any abdera packages in
Export-Package section
, but some abdera packages has mentioned in MANIFEST.MF as exported
packages.
Export-Package
org.wso2.carbon.hostobjects.atom.*;
/Export-Package
[1]
Sorry i forgot to add a svn log for this commit. Pressed enter by mistake
before i type the log message.
This is part of the process of creating MB2 Alpha i m in the process of
creating MB pack with new dependencies.
--Charith
On Mon, Mar 5, 2012 at 2:47 PM, char...@wso2.com wrote:
Author:
On Mon, Mar 5, 2012 at 12:47 PM, Deependra Ariyadewa d...@wso2.com wrote:
On Mon, Mar 5, 2012 at 12:33 PM, Rajika Kumarasiri raj...@wso2.comwrote:
It seems the Cassandra version that you are using tightly couple into the
an older version of the thrift. In that case we will have to maintain
Are we not using OSGi for these dependencies? Its meant to solve these sort
of problems!
Paul
On 5 March 2012 07:17, Deependra Ariyadewa d...@wso2.com wrote:
On Mon, Mar 5, 2012 at 12:33 PM, Rajika Kumarasiri raj...@wso2.comwrote:
It seems the Cassandra version that you are using tightly
Hi Ajith,
This occurs due indirect dependencies. If you look at the Export-Package
header carefully, you would see that all these indirect dependencies are
mentioned under the uses directive.
Thanks,
Sameera.
On Mon, Mar 5, 2012 at 2:58 PM, Ajith Vitharana aji...@wso2.com wrote:
Hi All,
I
Yes, it means that people have not specified the correct package import
export versions. The different versions of these OSGi bundles can coexist.
Can we fix these import-export versions at least for these bundles?
On Mon, Mar 5, 2012 at 3:10 PM, Paul Fremantle p...@wso2.com wrote:
Are we not
Hi,
I am experiencing this in a clean repo build from the src revision 121949.
Have any body came across with this ?
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 8.872s
[INFO] Finished at: Mon Mar 05 15:41:18 IST 2012
Asela, could you check whether you can fix the problem without removing the
jar?
We will have to maintain two versions if two components have version
specific dependencies...
On Mon, Mar 5, 2012 at 3:23 PM, Afkham Azeez az...@wso2.com wrote:
Yes, it means that people have not specified the
On Mon, Mar 5, 2012 at 3:56 PM, Tharindu Mathew thari...@wso2.com wrote:
Asela, could you check whether you can fix the problem without removing
the jar?
We will have to maintain two versions if two components have version
specific dependencies...
Yes will look. As Azeez mentioned, There
On Revision: 121992
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.webapp.mgt: Compilation
failure: Compilation failure:
[ERROR]
Hi Isuru,
On Mon, Mar 5, 2012 at 10:37 AM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
Hi Isuru,
On Mon, Mar 5, 2012 at 8:09 AM, Isuru Suriarachchi is...@wso2.com wrote:
Hi Kishanthan,
As we are done with the context.xml support and other Tomcat samples,
please trigger a build and
Hi,
This can be skipped when building from graphite level instead of building
each module separately.
On Mon, Mar 5, 2012 at 3:44 PM, Subash Chaturanga sub...@wso2.com wrote:
Hi,
I am experiencing this in a clean repo build from the src
revision 121949. Have any body came across with this
Got resolved after updating Carbon core.
/sumedha
On Mon, Mar 5, 2012 at 4:36 PM, Sumedha Rubasinghe sume...@wso2.com wrote:
On Revision: 121992
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project
Hi All,
Please advice if the below plans could be cleared/deleted from the Bamboo
Dashboard as they are non-active;
- BAM2 [1]
- Reporting [2]
- WSO2 Carbon 3.2.0 [3]
- WSO2 Carbon trunk [4]
[1] http://wso2.org/bamboo/browse/BAM2
[2] http://wso2.org/bamboo/browse/REPORTING
[3]
Also [4] can be removed as well because we have a new plan for the trunk.
On Mon, Mar 5, 2012 at 6:00 PM, Sanjaya Vithanagama sanja...@wso2.comwrote:
Hi Maheshika,
You can delete [1] from Bamboo. It was created for the BAM2 alpha release
and it was moved to a new builder machine.
Thanks
We will need new plans once we finalize complete the SVN moves.
On Mon, Mar 5, 2012 at 6:04 PM, Sanjaya Vithanagama sanja...@wso2.comwrote:
Also [4] can be removed as well because we have a new plan for the trunk.
On Mon, Mar 5, 2012 at 6:00 PM, Sanjaya Vithanagama sanja...@wso2.comwrote:
If everybody agrees on this, can we go ahead with the new restructuring?
On Mon, Mar 5, 2012 at 2:26 PM, Afkham Azeez az...@wso2.com wrote:
I suggest that while keeping; https://svn.wso2.org/repos/wso2/trunk as it
is, to come up with the new structure.
1.
Hi Senaka,Pradeep
On Sun, Mar 4, 2012 at 7:26 PM, Senaka Fernando sen...@wso2.com wrote:
Hi Subash,
Let's try to do a build on a clean repo tomorrow and see whether this can
be reproduced. If we cannot, we can clean the repo of the builder and try.
I use the same src revision 121949 which
Hi all,
I am working on extending smooks functionality on WSO2 ESB Smooks Mediator.
When implementing JPA support with hibernate on smooks mediator, I am
facing an issue of not being able to find the persistence provider. I
placed the persistence.xml file inside a jar which contains the entity
Hi subash,
looks like this issue is local to the bamboo. The latest build had some
other issue.
thanks,
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
I'm +1. This is the structure we decided during the first discussion. shall
we wait till sameera confirms. He was talking about some other structuring
mechanism few days ago.
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
In old releases we could load certain config files by placing them in the
webapps/WEB-INF/classes directory. Not sure whether that's a viable option
anymore though.
Thanks,
Hiranya
On Mon, Mar 5, 2012 at 6:30 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi all,
I am working on extending
On Mon, Mar 5, 2012 at 6:38 PM, Krishantha Samaraweera
krishan...@wso2.comwrote:
Hi,
I see following error on G-Reg console while starting up. The server
doesn't get started.
Hi Krishantha,
I also able to reproduce the same in a clean repo build greg pack.
Pradeep,
Is this due to the
Hi all,
The JPA uses provider architecture. There it loads providers using java spi
mechanism. The problem is with unique classLoaders, this does not work in
OSGi. (earlier we used to load them all using application/carbon-bootstrap
classLoader by placing them in outer lib)
two viable options.
Hi,
no not really. I did that weeks ago. The root cause is ,
shindig bundle exports its own version of org.xml.stax.
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Are we not cutting too close to the release to do this now? How much time
will it take to do this and stabilize?
Also, what are the implications of current branching strategy when we do
this?
Also, we need a new svn server hosted for this, where we can control access
to specific locations at a
On Mon, Mar 5, 2012 at 7:26 PM, Samisa Abeysinghe sam...@wso2.com wrote:
Are we not cutting too close to the release to do this now? How much time
will it take to do this and stabilize?
Even now the kernel, platform orbit POMs are independent. So, doing SVN
moves to different locations will
What is reporting? I see no use of that - do we really use that?
Also, tooling is missing in Bamboo. Should we not have it in there?
Bam2, jaggery should be really built using this. Not using builders. I
thought we got rid of the script based builders. Did we not?
On Mon, Mar 5, 2012 at 6:08
Hi,
i thought reporting is used for sonar reports.
we got to have another bamboo instance if we are going to schedule BAM2,
Jaggery, etc.
otherwise carbon-trunk build cycle get extended. (if we are running this in
the same instance. we have to execute them sequentially to avoid port
binding
Hi,
You are correct. I was referring to *separate* BAM2 build plan.
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Cannot treat a number param as a number.
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
Reason I am saying is that I wrote a cal to demo session and
the param could not be added out of the box. I have to make use of ' *
parseFloat'*
See code below.
%
var operation = request.getParameter(operation);
var value1 = parseFloat( request.getParameter(value1) );
var value2 =
Can we detect these kinds of errors with integration tests?
On Mon, Mar 5, 2012 at 8:04 PM, Afkham Azeez az...@wso2.com wrote:
We need to find fix all such buggy bundles that duplicate stuff.
On Mon, Mar 5, 2012 at 7:05 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
no not really. I
On Mon, Mar 5, 2012 at 8:13 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
i thought reporting is used for sonar reports.
we got to have another bamboo instance if we are going to schedule BAM2,
Jaggery, etc.
otherwise carbon-trunk build cycle get extended. (if we are running this
in
There are a bunch. Please make sure every issue is assigned to a milestone.
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
I was able to get this resolved by making the CXF bundle a fragment of the
tomcat bundle. This is the only option to deal with the CXF + Spring
combination. I think this is good enough for the initial implementation.
However, while investigating the possible options, there are two other
Hi all.
I design an asynchrony process but when I create the instance it give me
the error
[2012-03-05 10:26:54,188] ERROR - AxisEngine - *The [action] cannot be
processed at the receiver.*
I check with the SOAP Message Tracer and the error look like this
soapenv:Envelope
On Mon, Mar 5, 2012 at 9:14 PM, Isuru Suriarachchi is...@wso2.com wrote:
I was able to get this resolved by making the CXF bundle a fragment of the
tomcat bundle. This is the only option to deal with the CXF + Spring
combination. I think this is good enough for the initial implementation.
Hi,
Shall we use a clean repo + clean checkout for each of
orbit/carbon-kernel/carbon-platform builds. IMHO, we should trigger builds
periodically instead of triggering them based on commits. Shall we do the
$subject. Any concerns ?
thanks,
--Pradeep
Hi,
On Mon, Mar 5, 2012 at 9:29 AM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
Shall we use a clean repo + clean checkout for each of
orbit/carbon-kernel/carbon-platform builds. IMHO, we should trigger builds
periodically instead of triggering them based on commits.
+1
also please make
I don't think it is possible to differentiate request parameters as
strings, integers, floats etc. i.e. when we pass something as a request
param from the client side, we don't consider their types.
If I have understand your question properly, what is would be the rationale
behind identifying
On Tue, Mar 6, 2012 at 8:07 AM, Ruchira Wageesha ruch...@wso2.com wrote:
I don't think it is possible to differentiate request parameters as
strings, integers, floats etc. i.e. when we pass something as a request
param from the client side, we don't consider their types.
If I have understand
Hi all,
Thanks all for the suggestions. I tried out what Hiranya has mentioned but
it doesn't solve the problem. Will further look into the options suggested
by Pradeep to get this work.
Thanks,
Lakmali
On Mon, Mar 5, 2012 at 7:03 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi all,
The JPA
Hi Samisa,
When you take the parameters from the request they are not type bound. they
will be always String, and if you are sure that some parameter is an
Integer you can cast it to a Integer and do math operations on it.
It goes same for Java HTTPServletRequest [1]
[1]
On Mon, Mar 5, 2012 at 8:52 PM, Samisa Abeysinghe sam...@wso2.com wrote:
There are a bunch. Please make sure every issue is assigned to a
milestone.
Will do
Regards,
/Nuwan
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
I was also thinking the same. But since this is JavaScript, doesn't the
type conversion automatically happen? Perhaps not. How will it know whether
1 is a String or int.
On Tue, Mar 6, 2012 at 9:33 AM, Nuwan Bandara nu...@wso2.com wrote:
Hi Samisa,
When you take the parameters from the
On Mon, Mar 5, 2012 at 10:00 PM, Pradeep Fernando prad...@wso2.com wrote:
On Mon, Mar 5, 2012 at 9:14 PM, Isuru Suriarachchi is...@wso2.com wrote:
I was able to get this resolved by making the CXF bundle a fragment of
the tomcat bundle. This is the only option to deal with the CXF + Spring
On Tue, Mar 6, 2012 at 9:50 AM, Afkham Azeez az...@wso2.com wrote:
I was also thinking the same. But since this is JavaScript, doesn't the
type conversion automatically happen? Perhaps not. How will it know whether
1 is a String or int.
That's correct. And I think it's ok too. This is
yap, When u getting params from URL it give String not float,
so when we get string
we must able to convert string to float as samisa code.
Seems it is not working.
But if we pass it host object, It automatically make string to Float or Int
This worked.
On Tue, Mar 6, 2012 at 9:50 AM, Afkham
On Mon, Mar 5, 2012 at 7:03 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi all,
The JPA uses provider architecture. There it loads providers using java
spi mechanism. The problem is with unique classLoaders, this does not work
in OSGi. (earlier we used to load them all using
Request parameters are string. Its beyond the scope of jaggery to fix this
imo
Regards,
Tharindu
Sent from Transformer
On Mar 6, 2012 10:00 AM, Hiranya Jayathilaka hira...@wso2.com wrote:
On Tue, Mar 6, 2012 at 9:50 AM, Afkham Azeez az...@wso2.com wrote:
I was also thinking the same. But
Hi All,
I dont think, we should think about the Java API when you are programming
in Javascript. In JavaScript you have 4 premitive types (literals)
1. null
2. boolean
3. numaric
4. string
And you have Objects as well for these with more operations associated see
[1] so if you want
How come this happen suddenly ? Shindig was not changed recently.
Regards,
/Nuwan
On Mon, Mar 5, 2012 at 8:48 PM, Samisa Abeysinghe sam...@wso2.com wrote:
Can we detect these kinds of errors with integration tests?
On Mon, Mar 5, 2012 at 8:04 PM, Afkham Azeez az...@wso2.com wrote:
We need
Hi Pradeep,
Can you please apply the proper patch for this into Carbon core?
~Isuru
On Wed, Feb 29, 2012 at 6:47 PM, Isuru Suriarachchi is...@wso2.com wrote:
Sameera fixed the issue and now everything looks fine..
Thanks,
~Isuru
On Wed, Feb 29, 2012 at 5:53 PM, Isuru Suriarachchi
OK.. Lets assume that we provided getParameterAsFloat(),
getParameterAsInt() methods, then in order to use them, we must know the
types of the parameters during the development time and it is not doing any
automatic type detection or casting. What it does is, it tries to cast the
param to the
On Tue, Mar 6, 2012 at 11:03 AM, Ruchira Wageesha ruch...@wso2.com wrote:
OK.. Lets assume that we provided getParameterAsFloat(),
getParameterAsInt() methods,
I think this is overkill. I am happy to type cast and be done with this as
I have done in the code I sent, as a user.
I was trying
Applied the patch, days ago. The changes are in tomcat module, not in
tomcat.ext module.
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Ok thanks..
On Tue, Mar 6, 2012 at 11:19 AM, Pradeep Fernando prad...@wso2.com wrote:
Applied the patch, days ago. The changes are in tomcat module, not in
tomcat.ext module.
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
We can support OSGi webapp bundles as an experimental (alpha level)
feature. However, we will not be able to provide that for tenants.
On Tue, Mar 6, 2012 at 9:57 AM, Isuru Suriarachchi is...@wso2.com wrote:
On Mon, Mar 5, 2012 at 10:00 PM, Pradeep Fernando prad...@wso2.comwrote:
On Mon,
Hi All,
WSO2 Application Server M2 released !!
Packs can be found at [1].
New features included in this release,
- Added support for server descriptor file (server.xml) for embedded
tomcat.
- Added support for webapp specific context descriptor file
(context.xml) for webapps.
-
On Tue, Mar 6, 2012 at 11:55 AM, Afkham Azeez az...@wso2.com wrote:
We can support OSGi webapp bundles as an experimental (alpha level)
feature. However, we will not be able to provide that for tenants.
Yes of course, both those improvements are not for tenants. But I think
those are nice to
Are we going ahead with $subject for the next release? IMO, GD will get
better tested if it is enabled at ST level since more people are involved
in day to day testing of standalone products.
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software
65 matches
Mail list logo
