Also, in addition to the diagram, we also need a para or two to explain this.
Even I might understand that it is an ESB artifact like a proxy service that we package to a project, people might think that we are putting an ESB inside, given the diagram. On Tue, Feb 15, 2011 at 1:24 PM, Samisa Abeysinghe <[email protected]> wrote: > > > On Tue, Feb 15, 2011 at 1:21 PM, Saminda Wijeratne <[email protected]>wrote: > >> >> >> On Tue, Feb 15, 2011 at 1:12 PM, Samisa Abeysinghe <[email protected]>wrote: >> >>> http://wso2.org/project/carbon-studio/1.0.3/docs/overview.html >>> >>> <http://wso2.org/project/carbon-studio/1.0.3/docs/overview.html>It >>> shows, you go from CApp project to on to create artifacts. >>> >>> That order is incorrect IMHO >>> >> AFAIK in any IDE if you want to create a java class you first have to >> create a java project. CApp project is the container for CApp artifacts at >> the development stage. With the current implementation (1.0.*) what you are >> suggesting is not possible. >> >> >>> You first create artifacts, package those together and end up with the >>> CApp package, >>> >> FYI the final output is called a CAR or CApp Archive. >> > > First of all, none of these Jargon is there on the digram - nor the diagram > should have that either. From a user perspective, this does not make any > sense. Please see the reply that I sent in reply to Azeez. > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
