Hi Alessio, I am sorry about the delay in the response.
When the work will be done I'll push it via github. It's the official > way to contribute, right? Yeap Going forward we will be using the following repositories: https://github.com/wso2/product-esand https://github.com/wso2/carbon-store The rxt and store modules have been moved to the https://github.com/wso2/carbon-store importAssetFromHttpRequest when new data+file uploads are posted? > This can be done by adding a log at https://github.com/wso2/carbon-store/blob/master/apps/publisher/modules/asset_api.js#L194 (Create operation) and https://github.com/wso2/carbon-store/blob/master/apps/publisher/modules/asset_api.js#L235 (Update operation): log.info(assetReq); I will get back to you on the thumbnail/banner issue you mentioned (Issue does not seem to be their in the current build of the product) Thank You, Sameera On Wed, Jan 21, 2015 at 10:50 AM, Alessio Carenini < [email protected]> wrote: > Hi again, > thank you for clarifying the order of the calls. By now I implemented > visualising data from unbounded tables in "Overview" page and the form > generation in "Edit" page. I modified > * extensions/assets/default/pages/update.jag : the data structure > which was passed to the renderer was lacking all the values from the > unbounded tables > * themes/default/theme.js : generation of the dynamic table rendering > the existing values plus buttons to add/remove rows > > > What I miss now is the "Save/Upload" code. > Do you have an example of the data which is sent to > importAssetFromHttpRequest when new data+file uploads are posted? That > way I'll be able to catch the right data from the form, format it the > way that function expects it, and then modify > importAssetFromHttpRequest to let it manage data from unbound tables. > When the work will be done I'll push it via github. It's the official > way to contribute, right? > > Best regards > > Alessio > > On Tue, Jan 20, 2015 at 7:39 PM, Sameera Medagammaddegedara > <[email protected]> wrote: > > EDIT: > > > > When adding support for unbounded tables you will need to modify the > client > > side code as well make changes to the update logic found in > > {CARBON_HOME}/modules/rxt/ > > scripts/asset/asset.js.These changes involve modifications to the way we > > process the data sent from the client side > > > > > https://github.com/wso2-dev/product-es/blob/master/modules/jaggery-modules/rxt/module/scripts/asset/asset.js#L870 > > importAssetFromHttpRequest > > > > > https://github.com/wso2-dev/product-es/blob/master/modules/jaggery-modules/rxt/module/scripts/asset/asset.js#L82 > > setField method > > > > > > Thank You, > > Sameera > > > > On Tue, Jan 20, 2015 at 1:32 PM, Sameera Medagammaddegedara > > <[email protected]> wrote: > >> > >> Hi Alessio, > >> > >> The update handling logic is as follows: > >> > >> publisher/controllers/ref_apis_router.jag --> > >> publisher/extensions/assets/default/apis/assets.jag --> > >> /modules/asset_api.js > >> > >> The methods called in the asset_api.js can be found in > >> {CARBON_HOME}/modules/rxt/scripts/asset/asset.js > >> > >>> I wonder whether asset update has already been fully implemented > (meaning > >>> that I'm doing something wrong) or this part has yet to be finalised > >> > >> The update functionality has been implemented and should be working > >> > >> Could you provide a bit of details on the use case that causes the > error: > >> > >> Are you encountering this with one of the stock asset types shipped with > >> the ES? > >> If it is a new asset type could you please attach the rxt file and any > >> extensions you have built for it (publisher/extensions/assets) > >> Did this issue occur after the unbounded table changes? > >>> > >>> In case it's unimplemented I'm more than willing to contribute :) > >> > >> I believe this is a bug , but > >> > >> > >> > >> Thank You, > >> Sameera > >> > >> On Tue, Jan 20, 2015 at 12:18 PM, Alessio Carenini > >> <[email protected]> wrote: > >>> > >>> Hi all, > >>> while trying to implement unbound tables in ES 2.0.0-M4, I noticed that > >>> updating an asset containing images causes a File Upload exception > >>> > >>> [2015-01-20 18:03:23,860] ERROR > >>> {org.jaggeryjs.hostobjects.web.RequestHostObject} - Stream closed > >>> org.apache.commons.fileupload.FileUploadException: Stream closed > >>> at > >>> > org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:385) > >>> > >>> In update-asset.js I see little code, so I wonder whether asset update > >>> has already been fully implemented (meaning that I'm doing something > wrong) > >>> or this part has yet to be finalised. Is it a known bug? In case it's > >>> unimplemented I'm more than willing to contribute :) > >>> > >>> Thank you in advance > >>> > >>> Alessio > >>> > >>> ------------------------------------------------------------------- > >>> Alessio Carenini > >>> CEFRIEL - ICT Institute Politecnico di Milano > >>> Via Fucini, 2 - 20133 Milano (Italy) > >>> e: [email protected] - skype: ale.carenini > >>> live messenger: [email protected] - w: www.cefriel.it > >>> p: +39 0223954352 - f: +39 0223954352 > >>> ---------------------------------------------------------------- > >>> _______________________________________________ > >>> Dev mailing list > >>> [email protected] > >>> http://wso2.org/cgi-bin/mailman/listinfo/dev > >> > >> > >> > >> > >> -- > >> Sameera Medagammaddegedara > >> Software Engineer > >> > >> Contact: > >> Email: [email protected] > >> Mobile: + 94 077 255 3005 > > > > > > > > > > -- > > Sameera Medagammaddegedara > > Software Engineer > > > > Contact: > > Email: [email protected] > > Mobile: + 94 077 255 3005 > -- Sameera Medagammaddegedara Software Engineer Contact: Email: [email protected] Mobile: + 94 077 255 3005
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
