I think we need a common component for beans.
On Mon, Mar 17, 2014 at 11:48 AM, Isuru Haththotuwa <[email protected]> wrote: > Hi Pradeep, > > On Mon, Mar 17, 2014 at 11:16 AM, Pradeep Fernando <[email protected]>wrote: > >> Hi, >> >> During my effort to run stratos on a single JVM i encountered this issue. >> Due to legacy reasons we have used same package name in both server side >> and client-stub side. Hence when running on single JVM, things not working. >> >> One option is to create different package structure for client-stubs. >> (correct way to do it). >> >> I'm trying to understand the proplem here. >> >> the Cloud Controller exposed the service. >> Autoscalar use that web-service (the generated packages are in a >> different pacakge structure) >> >> So why we generated code with package names with similar names. I still >> dont get it. :) >> >> Other day, i heard that it will eliminate the data type conversions. Can >> you please give me an example. In that case, we may have to create a common >> beans package. >> > > AFAIU, this will not eliminate data type conversions. The back end > services are mostly axis2 services, so the generated service stub pojo will > be extending an axis2 bean class (org.apache.axis2.databinding.ADDBean, > etc). It is not aware of jax-rs information (xmlRootElement, etc.). So, > we still need to convert between the pojo which is generated by the jax-rs > Rest API and the pojo in the service stub. > > If the problem lies in using the same package name for both backend and > service stub, +1 for differentiating between the BE package and service > stub package name. > >> >> thanks, >> ---Pradeep >> >> >> > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha
