On Fri, Mar 18, 2011 at 12:09 PM, Amila Maha Arachchi <[email protected]> wrote: > > > On Fri, Mar 18, 2011 at 11:53 AM, Tharindu Mathew <[email protected]> wrote: >> >> >> On Thu, Mar 17, 2011 at 7:08 PM, Samisa Abeysinghe <[email protected]> >> wrote: >>> >>> >>> On Thu, Mar 17, 2011 at 5:23 PM, Pradeep Fernando <[email protected]> >>> wrote: >>>> >>>> On Thu, Mar 17, 2011 at 4:03 PM, Harshana Martin <[email protected]> >>>> wrote: >>>> > >>>> > >>>> > On Thu, Mar 17, 2011 at 1:58 PM, Afkham Azeez <[email protected]> wrote: >>>> >> >>>> >> Samisa & I had a discussion on this, and these are the items in order >>>> >> of >>>> >> priority for the different teams. >>>> >> Product Teams >>>> >> 1. Integration tests >>>> >> 2. Introduce service stubs, and take OSGi dependencies on those stubs >>>> >> for >>>> >> all components in your products >>>> I have done this. I have uploaded all the service stubs. the only >>>> remainng thing is updating the ui component poms. >>>> I have done that about a week ago. Now i have to verify again before >>>> committing since wsdls may have changed overtime. >>> >>> This needs to improve. We need to define a new package for stub and use >>> the stub jar as it is, rather than using the same package as the UI >>> component and unzip and re-bundle. >>> >> >> So the suggestion is to make a separate bundle for the stub itself, and >> re-use it in the UI bundle? >> If that is the case, what does it solve? The wsdl out dating issue is >> still present. So I'm wondering what the extra effort will achieve. > > IIRC it is to reduce the time spent on code generation at each build time. >
well, it was the initial plan. But it turns out that we dont acheive that much of advatage by separating the codegen parts. This approach allows us to manage the wsdls (API) in a proper way. with this modification, you just put a stub dependency in to your UI component. The stubs should be updated by the wsdl author. As of now, we have a seperate stub for each wsdl. the next thing to do is moving the codegen classes in to their own package and re-use across the UI components. In that case we can bundle the jar as it is . without unzipping. --Pradeep _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
