: rajkumarr.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Lochana Menikarachchi
Senior Tech Lead
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi
--
Lochana Menikarachchi
Senior Tech Lead
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:705)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at
org.wso2.carbon.ml.model.DatabaseHandler.getDatabaseHandler(DatabaseHandler.java:62)
--
Lochana Menikarachchi
Senior Tech Lead
WSO2 Inc
, Lochana Menikarachchi loch...@wso2.com
wrote:
Is it possible access a database within osgi bundle's start method?
public void start(BundleContext context) throws Exception {
ModelService modelService = new ModelService();
context.registerService
)
at java.lang.Thread.run(Thread.java:745)
--
Lochana Menikarachchi
Senior Tech Lead
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Correction.. I get this with a Carbon 4.3.0-SNAPSHOT based product.. I have
ldap, carbon remote user management features and jaggery features installed
in it.
On Wed, Nov 5, 2014 at 9:26 AM, Lochana Menikarachchi loch...@wso2.com
wrote:
I run into this error intermittently
, 2014 at 9:49 AM, Lochana Menikarachchi loch...@wso2.com
wrote:
Correction.. I get this with a Carbon 4.3.0-SNAPSHOT based product.. I
have ldap, carbon remote user management features and jaggery features
installed in it.
This is a known issue in 4.3.0. I think the jaggery feature is causing
Hi,
Need to bundle jaggery feature with the carbon 4.3.0-SNAPSHOT based product
we are building. What is the repo and what are the features required?
Thanks.
--
Lochana Menikarachchi
Senior Tech Lead
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http
standard to write to files and read files.
Cheers~
On Tue, Oct 7, 2014 at 12:41 PM, Lochana Menikarachchi loch...@wso2.com
wrote:
Is there any reason to restrict file system operations (why not outside
Jaggery application context root) ?
http://jaggeryjs.org/documentation.jag?api=file
saving a file to a specific path is inadvisable cause paths
will depend upon deploying machine.
Can you elaborate more on the requirement - where we can give a solution?
Cheers~
On Tue, Oct 7, 2014 at 10:50 AM, Lochana Menikarachchi loch...@wso2.com
wrote:
Unfortunately, that's not going
to store the files. Adding @sameeraM to the
thread.
Cheers~
On Tue, Oct 7, 2014 at 12:09 PM, Lochana Menikarachchi loch...@wso2.com
wrote:
Hi,
File uploading brings about a number of issues in scalability. For
example - if we upload files to the deployments directory- it's not going
Is there any reason to restrict file system operations (why not outside
Jaggery application context root) ?
http://jaggeryjs.org/documentation.jag?api=file
On Tue, Oct 7, 2014 at 12:20 PM, Lochana Menikarachchi loch...@wso2.com
wrote:
We need to support file uploading to a server location
file.saveAs(String targetLocation);
this saves a given file relative to the Jaggery application context root
Is there anyway to save the file according to absolute path?
Thanks.
--
Lochana Menikarachchi
Senior Tech Lead
WSO2 Inc.
___
Dev mailing list
,
'/').replace(/^[\/]/g, '');
return parent + MODULE_PATH + path;
};
[1]
https://github.com/Madhuka/sugarcane/blob/master/core/sugarcane/scripts/engine/test.js
On Tue, Oct 7, 2014 at 9:37 AM, Lochana Menikarachchi loch...@wso2.com
wrote:
--
Cheers,
Madhuka Udantha
http
lean . enterprise . middleware
On Tue, Oct 7, 2014 at 10:29 AM, Lochana Menikarachchi loch...@wso2.com
wrote:
Dilan, There is a specific requirement.. We need to upload a file to a
given location
Madhuka, That method returns absolute path.. What I want is to upload a
file to a given location
15 matches
Mail list logo