Hi Tishan,

Since we can't catch any exceptions properly when simply dropping the files
to the relevant directories, I think going for a admin service call
approach might be better. Also, I think initially there were discussions on
aligning the toolboxes for BAM/CEP. e.g. You have one toolbox for mediation
statistics. When you want batch processing, you drop the toolbox to BAM.
When you want real-time analytics, you drop the toolbox to CEP. So we might
have to discuss the structure of the toolbox with BAM team as well.

Can we create a separate new component for the toolbox? I think none of the
existing component categorizations would fit in with the toolbox. WDYT?

Thanks,
Lasantha

On 29 October 2014 14:38, Tishan Dahanayakage <[email protected]> wrote:

> Hi all,
> I was working on $Subject and following scenario came up.
>
> My initial design was to create a new deployment directory, say
> 'cep-toolbox'. Then write a deployer extending AbstractDeployer. Deployer
> will get deployed toolbox, unzip it and deploy each artifact to respective
> deployment directory again. (Ex: deploy Execution Plan artifact to
> executionplan folder). But the problem with this approach is I can't catch
> any exception occurred when deploying each artifact.
> So the other approach is to create a separate bundle depending on each
> AdminService/BE Service and deploy artifacts using those services. This is
> more like BAM toolbox approach. Any thoughts on these approaches?
>
> Also please suggest a component to add the new bundle if we are going
> through with separate bundle option.
>
> --
> Tishan Dahanayakage
> Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>



-- 
*Lasantha Fernando*
Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: [email protected]
mobile: (+94) 71 5247551
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to