Hi,
On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando prad...@wso2.com wrote:
+1 agreed with danushka. Adding default configuration is not the
solution for what dimuthu has encountered. In this case dimuthu is
responsible for making the stratos distribution. Anybody working on
wso2 product
Hi
On Fri, Apr 1, 2011 at 10:47 AM, Danushka Menikkumbura danus...@wso2.comwrote:
But I think we have a fundamental issue in the way we build products. We
manually copy stuff (mostly configuration files) from the generated carbon
distribution to the product pack we build. As I learned from
hi,
On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne dimut...@wso2.com wrote:
Hi,
On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando prad...@wso2.com wrote:
+1 agreed with danushka. Adding default configuration is not the
solution for what dimuthu has encountered. In this case dimuthu is
On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi,
On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando prad...@wso2.comwrote:
+1 agreed with danushka. Adding default configuration is not the
solution for what dimuthu has encountered. In this case dimuthu is
As I believe adding configuration files into a product is the responsibility
of the product team. Not yours. In fact what we do is to add an entry into
the bin.xml to copy qpid configuration files into the product distribution
from the carbon core distribution that is built in the middle (which is
On Fri, Apr 1, 2011 at 12:49 PM, Manjula Rathnayake manju...@wso2.comwrote:
On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi,
On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando prad...@wso2.comwrote:
+1 agreed with danushka. Adding default configuration is
Hi Danushka,
We have to agree what is the unit of sharing in our platform. I am
think that is the component, and if so, adding the component should be
good enough to install something. If feature is the unit of sharing,
what you say do make sense.
--Srinath
On Fri, Apr 1, 2011 at 10:47 AM,
On Fri, Apr 1, 2011 at 12:51 PM, Danushka Menikkumbura danus...@wso2.comwrote:
As I believe adding configuration files into a product is the
responsibility of the product team. Not yours.
Dhanushka,
I don't understand your statement. What we build is small pieces of a
platform. The products
As I believe adding configuration files into a product is the
responsibility of the product team. Not yours.
Sumedha,
Let me rephrase.
You do not have to do anything extra to get Qpid to work in your product. In
fact it is installable as a feature.
What I meant was when we pack our
Has anyone tested adding Qpid using p2 as a feature into a product that
doesn't have it? Does that work?
Paul
On 31 March 2011 06:59, Tharindu Mathew thari...@wso2.com wrote:
I updated bam and built and I believe this is fixed now. All qpid configs
are in place, so we are good.
Also, as I
hi,
it is working fine when it is installed as a feature. (they copu the
conf files using p2.inf). feature manager and the feature installation
during the product building uses the same strategy.
--Pradeep
___
Carbon-dev mailing list
Is there a way to hard-code defaults that the code uses when it can't find
the conf files? I know a lot of systems do that (even Axis2 if I remember
correctly). We could print a line to INFO log saying we are using built in
defaults.
Paul
On 31 March 2011 07:25, Pradeep Fernando prad...@wso2.com
On Thu, Mar 31, 2011 at 11:58 AM, Paul Fremantle p...@wso2.com wrote:
Is there a way to hard-code defaults that the code uses when it can't find
the conf files? I know a lot of systems do that (even Axis2 if I remember
correctly). We could print a line to INFO log saying we are using built in
On Thu, Mar 31, 2011 at 11:58 AM, Paul Fremantle p...@wso2.com wrote:
Is there a way to hard-code defaults that the code uses when it can't find
the conf files? I know a lot of systems do that (even Axis2 if I remember
correctly). We could print a line to INFO log saying we are using built in
a) it is your responsibility!
b) we have to fix this. Installing means adding the component, nothing
else.
OK. Let me give you an example.
If you use an installer that comes with a piece of software to install it,
you do not have to worry about copying libraries or configuration files,
On Fri, Apr 1, 2011 at 10:47 AM, Danushka Menikkumbura
danus...@wso2.com wrote:
a) it is your responsibility!
b) we have to fix this. Installing means adding the component, nothing
else.
OK. Let me give you an example.
If you use an installer that comes with a piece of software to install
Hi,
I am having a really hard time coping with Qpid instability. I did an svn up
yesterday and build everything. Since BAM didn't start up, I did an svn up
of all Qpid related artifacts and build them again.
But still BAM doesn't start up because of Qpid config files !
#$%$^%^%$#%
Here are
Danushka or whoever is responsible for creating these issues, please fix
this asap. We don't want to see this tomorrow morning !
On Mar 30, 2011 10:39 PM, Dimuthu Leelarathne dimut...@wso2.com wrote:
Hi,
I am having a really hard time coping with Qpid instability. I did an svn
up
yesterday and
Even though qpid files are not present BAM starts up.
[2011-03-30 22:44:47,554] INFO
{org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS
port : 9443
[2011-03-30 22:44:47,555] INFO
{org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
port: 9763
Hi,
As Manjula pointed out (offline) I had to build features/event as well.
Now the server starts.
tx,
dimuthu
On Wed, Mar 30, 2011 at 10:46 PM, Tharindu Mathew thari...@wso2.com wrote:
Even though qpid files are not present BAM starts up.
[2011-03-30 22:44:47,554] INFO
The event team has repeatedly pointed out that qpid gets installed as a
result of installing event. No product does use qpid alone as far as I know.
Even in that case it is your responsibility to install what you need. Also
you guys not reading mails is your problem. I do not want to pay the price
Hi,
On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura
danus...@wso2.comwrote:
The event team has repeatedly pointed out that qpid gets installed as a
result of installing event. No product does use qpid alone as far as I know.
Even in that case it is your responsibility to install what
On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura
danus...@wso2.comwrote:
The event team has repeatedly pointed out that qpid gets installed as a
result of installing event. No product does use qpid alone as far as I know.
Even in that case it is your responsibility to install what you
Hi Samisa,
I hope your meant self-containing configuration files. I tried that but
failed as the root configuration file uses two other files in it which are
compiled by the configuration builder when the configuration context is
built.
This was fixed across products. The issue was not building
copes qpid configuration files into the product.
I meant to say qpid libs.
Thanks,
Danushka
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
On Thu, Mar 31, 2011 at 6:52 AM, Danushka Menikkumbura danus...@wso2.comwrote:
Hi Samisa,
I hope your meant self-containing configuration files. I tried that but
failed as the root configuration file uses two other files in it which are
compiled by the configuration builder when the
Danushka, to our carbon story to hold we have to be able to compose
components. That means defaults should be right, and Qpid MUST work
out of the box (whether it is added) directly, through eventing, or
indirectly by something else.
So
a) it is your responsibility!
b) we have to fix this.
I updated bam and built and I believe this is fixed now. All qpid configs
are in place, so we are good.
Also, as I showed you in my earlier mail, even if qpid can't find the
configs the server does not fail, which is the proper thing that should
happen.
It would be good if everyone else also see
28 matches
Mail list logo
