On Mon, Aug 25, 2014 at 1:44 PM, Srinath Perera wrote:
> Hi All,
>
> BAM capacity planning it bit involved than other products. I was doing one
> such case with Mifan and following are steps we followed. Please comment.
>
> 1. Need to know roughly how much data you need to handle. One way to get
Hi Jayanga,
Why can't register the "CarbonServerShutdownPrepareService" in normal OSGi
service registration manner (without registering it in server shutdown)? Is
that because you need to have synchronized manner or any other particular
reason to do so?
Thanks,
Best Regards,
Lakshitha Harshan
S
Hi Amila,
Sorry about the confusion.
Generally, in OSGi bundles, we register services provided by a particular
bundle in the bundle activation, That is true.
But in this scenario, I am registering the
"CarbonServerShutdownPrepareService" in the
org.wso2.carbon.core.init.CarbonServerManager.shutdo
Yes IMO that's a better plan for the initial setup, since I have tried
using a separate build server for some other feature of AF and it needs lot
of effort. So better to go with the same build server which we use to build
apps for now.
Regards,
Kasun
*Kasun de Silva*
Software Engineer | *WSO2 In
Hi Kasun,
We want to run selenium test in headless mode, this requires the build
server instance to be installed in an environment with browser launching
capabilities. And it doesn't mean we cannot use the same server which we
used to build apps. We'll use this existing one as for the initial ste
Hi All,
We had an issue with codeplex hook subscription where it returns 500
internal server error when we subscribe for a "Code Change" event and
enable it. So we have informed this matter to codeplex and waiting for a
response. Anyway we will proceed with developments of hook subscription
create
Hi Anuruddha,
Is the build server mentioned above for the test cases to run is a separate
one or the one we already have inside AF?
*Kasun de Silva*
Software Engineer | *WSO2 Inc.*; http://wso2.com
lean.enterprise.middleware
email : kas...@wso2.com
mobile : +94 77 794 4260
On Sun, Sep 14, 20
Sumedha,
sure, I understand: I also developed products that had to support multiple
RDBMS. But we ended up developing RDBMS specific code for performance
reasons. This of course depends on customer requirements, i.e. as long as
there are no customer complains, you are doing the right things :-)
Frank,
To make testing and development simple, we try to avoid database specific
code as much as possible with in Carbon platform. Currently most of the
products support close to 9 RDBMS engines.
99% of the SQLs we have in our DAO classes are ANSI compatible. However
there are database specific D
This is true in general: even a simple statement like SELECT behaves a bit
differently in different RDBMS implementations. I.e. minor differences in
SQL statements is not restricted to triggers, however we use RDBMS...
Best regards,
Frank
2014-09-12 10:24 GMT+02:00 Sumedha Rubasinghe :
> If yo
Prabath,
I agree that triggers make comprehending code a bit more difficult. But
triggers are a mechanism to achieve active database features, something
that is very difficult to get without triggers. Thus, I would not say that
they should not be used. I don't understand the statement that trigger
11 matches
Mail list logo