Hi All,
The implementation, $subject is adding some scripting support for Siddhi.
It is as follows,
1. Scripting languages are going to be JavaScript and Scala.
2. New language feature is to be introduced like below,
Define script[Language]{//script implementation goes here}
3. Siddhi user
Hi,
Thanks Anjana and Lahiru for the suggestions. Please find below the found
observations.
Following are the DB actions.
- DB creation (IF NOT EXIST)
- Table creation (IF NOT EXIST)
- Insert data to table
- update data to table
Since all the DBMS's are using same DDL and DML query formats we
+1 looks good
Suho
On Mon, Dec 1, 2014 at 4:57 PM, Ayash ayashkan...@wso2.com wrote:
Hi All,
The implementation, $subject is adding some scripting support for Siddhi.
It is as follows,
1. Scripting languages are going to be JavaScript and Scala.
2. New language feature is to be
Hi,
please note above varchar length will be given as default. eg:-
varchar(250).
Regards,
damith.
On Mon, Dec 1, 2014 at 5:10 PM, Damith Wickramasinghe dami...@wso2.com
wrote:
Hi,
Thanks Anjana and Lahiru for the suggestions. Please find below the found
observations.
Following are the
Hi Damith,
I'm personally biased towards just using the whole queries in the XML,
where we may get some subtle changes in queries that may not be possible
with your parameterized approach. For example, in MySQL, you can give the
storage table engine as a part in the DDL query. Likewise, there
Hi Damitha,
As Anjana suggested, separating only the data types would lead to some
confusions. Furthermore might, sometimes lead to not using a specific
database system to it's fullest potential. For example, given that there
are a huge amount of built-in functions in MSSQL we might be able to
Hi,
Thanks Anjana and Akalanka for the suggestions. @Anjana As per the off-line
discussion we had, I will add the necessary for the implementation.
Regards,
Damith.
On Mon, Dec 1, 2014 at 5:49 PM, Akalanka Pagoda Arachchi darsha...@wso2.com
wrote:
Hi Damitha,
As Anjana suggested,
Hi All,
We are trying to implement a feature on AF which enables the user to deploy
their customized app types, Currently this configuration is available
in *appfactory.xml
*under *Deployer* tag the content would be as [1], likewise we have for
each app types. Hence this wouldn't be editable by
Hi Rajeevan,
Please see my comments below.
On Mon, Dec 1, 2014 at 10:46 PM, Aiyadurai Rajeevan rajeev...@wso2.com
wrote:
Hi All,
We are trying to implement a feature on AF which enables the user to
deploy their customized app types, Currently this configuration is
available in
Please find the PR https://github.com/wso2/cipher-tool/pull/4
On Mon, Dec 1, 2014 at 3:05 PM, Nirmal Fernando nir...@wso2.com wrote:
We gonna introduce following properties file to hold the configuration
parameters of the ciphertool.
cipher-tool-config.properties
Content:
# this file
Hi,
On a side note, I would call it s/Deployment/Runtime. I think it is a more
suitable name.
thanks,
dimuthu
On Tue, Dec 2, 2014 at 8:45 AM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi Rajeevan,
Please see my comments below.
On Mon, Dec 1, 2014 at 10:46 PM, Aiyadurai Rajeevan
Hi,
+1 with the proposals. I couldn't find the appfactory-plugin.xml, though.
Did you mean to say the jelly files(conf.jelly and global.jelly) which is
inside the AppfactoryPluginManager?
Thanks Regards,
S.A.Rajeevan
Software Engineer WSO2 Inc
E-Mail: rajeev...@wso2.com | Mobile : +94776411636
Appending
Day 1 Notes:
*Goals*
1. Identify a CDM Core that's device/platform agnostic
2. Properly modularize the product (continuing the discussion in the
thread [1])
3. Evaluate how CDM can able to support Dynamic policies and policy
merging which are frequently requested
Hi,
We used to have a *plugin*.xml file. I can't find it anymore. Perhaps it is
time to re-introduce it.
thanks,
dimuthu
On Tue, Dec 2, 2014 at 10:31 AM, Aiyadurai Rajeevan rajeev...@wso2.com
wrote:
Hi,
+1 with the proposals. I couldn't find the appfactory-plugin.xml, though.
Did you mean
HI Dimuthu
Please find my comments inline
On Tue, Dec 2, 2014 at 8:45 AM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi Rajeevan,
Please see my comments below.
On Mon, Dec 1, 2014 at 10:46 PM, Aiyadurai Rajeevan rajeev...@wso2.com
wrote:
Hi All,
We are trying to implement a feature
Hi Shazni,
I checked the code for removeCache method and found that cacheKey is
calculated as below.
*String connectionId = (dataBaseConfiguration.getUserName() != null?
dataBaseConfiguration.getUserName().split(@)[0]:dataBaseConfiguration.getUserName())
+ @ + dataBaseConfiguration.getDbUrl();
Hi Manjula,
As my understanding cacheKey is a RegistryCacheKey object, which is
different from the cacheId. So we don't need to read the cacheId.
Thanks.
Mahendran Pirinthapan
Software Engineer | WSO2 Inc.
Mobile +94772378732.
On Tue, Dec 2, 2014 at 12:01 PM, Manjula Rathnayake
Hi Danushka,
Please see my comments below.
On Tue, Dec 2, 2014 at 12:01 PM, Danushka Fernando danush...@wso2.com
wrote:
HI Dimuthu
Please find my comments inline
On Tue, Dec 2, 2014 at 8:45 AM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi Rajeevan,
Please see my comments below.
Hi Manjula,
Yes. The cacheId that you specify is not the the '*connectionId*' that we
create in the method. When a resource is added to the cache we take the '
*connectionId*' the way it is implemented to create the cache key.
Therefore while retrieving the cache we should use the same way.
19 matches
Mail list logo