Hi Ruchira, Find my thoughts below,
On Wed, Nov 23, 2011 at 11:39 PM, Ruchira Wageesha <[email protected]> wrote: > Hi All, > > Most appropriate deployment model of an appdev webapp would be deploying > like a normal webapp which we deploy in AS. > +1, webapp like model is good, but does it have to be bundled up like a war ?. Its better not to. So we can have a model like you write the server side page using JSSP or JSS, and simply drop it to the deployment directory, like we do for PHP scripts in httpd. This will be the best mechanism to realize new GS architecture. > In the appdev framework, we have a set of HostObject(Java classes written > following a convention), Servlets and tags which build the > needed environment for the deployment of JS apps. But there are several > problems with getting this done. > > > 1. We need to keep all the hostobjects, servlets, servlet mappings and > tags in tomcat environment where apps get deployed. How do we achieve this? > I am not familiar with current webapp deployment model. Any guidelines?? > - At the moment in a JS webapp, everything is packed into a war > (hostobjects + servlets + servlet mapings + tags) and deployed in > tomcat. > > We do a similar thing for shindig at present. Shindig has a bunch of servlets, and some guice modules. we are initializing them through a carbon component (gadget.initializer). So anybody want to use gadgets can simply have it by installing the initializer feature. Can we do the same. we packup the appdev framework stuff. which is taglibs, servlets and hostobjects to a AppDev.initializer component. So a person or a product which needs appdev stuff can install this feature, so they can use the defined tags easily. > > 1. For hostobjects like Registry which allows registry calls, how do > we access the registry? Will we have to use WS* api or is there are way to > access OSGI service/or Java methods from the tags/hostobjects. > > Its better to have a registry hostobject in this case, rather than calling the registry remote API via WSRequest. Cant we have the same registry hostobject we using in MS ? It there a limitation on that ? > > 1. Further, if we are developing the new Gadget frontend as a JS > webapp, then we need to have access to the carbon context and get things > like > - Logged in user > - Tenant ID > - Admin cookie > - backserver url / transport information etc. > > I am not sure about the question, but however, during our discussion, what we wanted to really have is the ability to access carboncontext information from JSSPs and JSSes. If we are to develop the same GS views in AppDev framework, we need to have those propertise in AppDev environment too. I believe we can already obtain the HttpSession from JSS, so I guess some information like logedin user is already available. > > 1. According to the requirements of above [3], then the usage of JS > webapp model in gadget server would be the replacement of current carbon > frontend with JS webapps?? > > JS webapp model should be an easy way of creating views rather than creating carbon ui bundles packing them and deploying. Also if we are to deploy these apps like webapps, that means these new UI parts are not installable via P2, or can they ? am not sure about it. But however it is, IMO we need to provide the base, which is the gadget-initializer and the AppDev-initializer instalable via p2, so a user who download vanila Carbon can install these two features and start writing Apps. Regards, /Nuwan > Any suggestions? > > /Ruchira > > -- > Ruchira Wageesha > Software Engineer - WSO2 Inc. www.wso2.com > > Email: [email protected] Blog: [email protected] > Mobile: +94775493444 > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Thanks & Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * <http://www.nuwanbando.com/>
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
