-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keith,
There is a way to set the repo where the actual dataservice config files reside. The property is DBConstants.DB_SERVICE_REPO (org.wso2.ws.dataservice.DBConstants line 168) I see 2 ways to set this property; 1. If we can set this property at the time of the Mashup Server initialization, the Data Service Admin will pick it up from there and will hopefully prevent storing the file in a wrong location (as it does at present). or 2. Since our storage strategy is user based, I can try setting this config property from the JSP itself. At the JSP level I already know which user is creating the Data Service and will be able to infer the repo location using this information. Thoughts ? Tyrell - -- Tyrell Perera Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/ email: [EMAIL PROTECTED]; cell: +94 77 302 2505 "Oxygenating the Web Service Platform." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIF9cpehFdPcgGx7oRApndAJ9klWAA6fU10g47xn+ussd3aI/zjACfbFfF 5Q0YXRtZ8LZQ87e9mjXDwcY= =3V8x -----END PGP SIGNATURE----- _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
