hi, I read somewhere that a webservice which call another webservice isn't loosing coupling. I try to respect as much as possible the SOA principle
Regards, Erik Andrea Zoppello-2 wrote: > > There are not problem with your concept, but in my point of view it's > not the > right way to work with a great product like smx. > > If you need only to do a webservice that make a query and return a > response maybe you > must consider to write simple a java webservices with jdbc logic inside. > > You don't need smx to do that. > > For me the use of an "esb integration products" like smx, fits if you've > need > to define process as composition orchestration of reusable services. > > The power of binding components is to bound the same business logic to > different protocols > channels. > > Regards > Andrea Zoppello > > > > Erik Allais ha scritto: >> Hi andrea, >> >> >> Andrea Zoppello-2 wrote: >> >>> By the way if you think to write db code inside webmethod this code will >>> be only usable with >>> webservices. >>> >>> If you think in term of reusable services, your jdbc services will be >>> usable for example with a JMS input >>> or other supported binding component >>> >>> >>> >> >> I dont want to reuse the access to my DB, I only want to access with >> webservice... >> Do you think there is a problem in my conception? >> Do you think is better to make a reuse component to access to my >> database? >> >> Regards, >> Erik >> > > > -- View this message in context: http://www.nabble.com/JDBC-component-still-exist--tf4085038s12049.html#a11664367 Sent from the ServiceMix - User mailing list archive at Nabble.com.
