Please check [1] and [2] for sample implementation of this concept. Thanks, Sameera
[1] https://svn.wso2.org/repos/wso2/trunk/carbon/service-stubs [2] https://svn.wso2.org/repos/wso2/trunk/carbon/components/aar-services/org.wso2.carbon.aarservices.ui/pom.xml On Sun, Mar 6, 2011 at 12:02 PM, Sameera Jayasoma <[email protected]> wrote: > Hi Folks, > > We(Sanjiva, Samisa, Srinath, AmilaM and myself) had an offline discussion > on the subject on the last Friday. We came up with the following idea. > > Create separate project called "service-stubs" at the components, core > level. In this service-stubs project, we generate code for all the wsdls at > once and upload the jar files packaing these generated code to wso2 > dist-repo or SNAPSHOT repo. > > e.g. Consider the aar-services component. We generate the > org.wso2.carbon.aarservices.stub-3.2.0-SNAPSHOT.jar with all the generated > code and upload to our SNAPSHOT repo. Then in the aar-services UI component, > we embed this jar files inside the UI bundle. > > This way we can cut down the time taken to generate code over and over > again. But if someone make changes to these wsdl, that person needs to > upload the stub jar again. > > Thanks > Sameera > > -- > Sameera Jayasoma > Technical Lead and Product Manager, WSO2 Carbon > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://tech.jayasoma.org Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
