Yes. This is the structure that Dev Studio creates. On Mon, May 20, 2013 at 10:57 AM, Shamika Ariyawansa <[email protected]>wrote:
> HI Manisha, > > Is this the same structure that Dev Studio uses? If so this is OK. Only > thing we have to endure is, this should be aligned with Dev studio > deployment. > > Thanks > > > On Mon, May 20, 2013 at 10:48 AM, Manisha Gayathri <[email protected]>wrote: > >> Hi Shamika, >> >> When I create a sample project using the current ESB archetype, >> following is the project structure. >> . >> ├── artifact.xml >> ├── pom.xml >> ├── src >> │ └── main >> │ └── synapse-config >> │ └── proxy-services >> │ └── HelloProxy.xml >> >> >> When building the pom.xml of this sample application, the target will be >> as follows: >> capp >> ├── artifacts >> │ └── proxy-service >> │ └── HelloProxy >> │ ├── HelloProxy.xml >> │ ├── pom.xml >> │ └── target >> │ └── HelloProxy.xml >> └── pom.xml >> >> Is this the required CApp structure that is required? >> >> Thanks >> Manisha >> >> On Fri, May 17, 2013 at 8:07 AM, Shamika Ariyawansa <[email protected]>wrote: >> >>> >>> >>> ---------- Forwarded message ---------- >>> From: Shamika Ariyawansa <[email protected]> >>> Date: Thu, May 16, 2013 at 11:27 PM >>> Subject: [Dev][Appfactory] Deploying ESB aaplication underlying CAPP >>> To: WSO2 Developers' List <[email protected]> >>> Cc: Dimuthu Leelarathne <[email protected]> >>> >>> >>> Hi, >>> >>> We discussed to deploy the ESB applications by deploying whole synapse >>> folder structure to S2 separately. If we go with this approach it would be >>> fine for the simple ESB use cases like adding proxy service. But as far as >>> bit complex scenarios where the registry resources are getting involved are >>> concerned this would be bit hard achieve. >>> >>> Instead of that when deploying can't we create a CAPP including ESB >>> application files from appfactorty side and deploy it in ESB instance >>> through S2. Then its matter of integrating CAPP creation logic with >>> appfactory side. >>> >>> Users won't see it as an CAPP but only for the deployment purposes it is >>> being converted to a CAPP. >>> >>> What are the consequences of this ? >>> >>> Thanks >>> -- >>> Shamika Ariyawansa >>> Senior Software Engineer >>> >>> Mob:+ 94 772929486 >>> >>> >>> >>> -- >>> Shamika Ariyawansa >>> Senior Software Engineer >>> >>> Mob:+ 94 772929486 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> ~Regards >> *Manisha Eleperuma* >> Software Engineer, Solutions TG >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> >> *blog: http://manisha-eleperuma.blogspot.com/* >> *mobile: +94 71 8279777* >> * >> * >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Shamika Ariyawansa > Senior Software Engineer > > Mob:+ 94 772929486 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- ~Regards *Manisha Eleperuma* Software Engineer, Solutions TG WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/* *mobile: +94 71 8279777* * *
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
