That's a good question. ServiceMix is imho a perfect place to host your services, because ServiceMix is also a container in addition to being an ESB. You may want to host them in a separate servicemix instance for isolation or management / monitoring purposes, but this is a different problem. Having a single container where you deploy both your services and your integration logic makes things easier imho.
On Thu, Apr 10, 2008 at 3:55 PM, Ivanhoe Abrahams <[EMAIL PROTECTED]> wrote: > Hi everybody > > Yesterday somebody asked a question about where business specific logic > must > be placed so as to better apply SOA principles. > Now I am bumping into the same issue. > > Soon we will start a new project which will require the use of message > transformation and routing to different external clients' services(perfect > for ServiceMix i thought). > As part of this we plan to write a simple Vending Service Layer which will > provide rudimentary accounting like functionality and warehouse > management..etc. This all working directly on a database. > So we will have a portal which speaks to the service layer via the > esb(servicemix), and depending on message content etc. we transform will > route messages to the external client. > > Now I thought, why not expose this service layer as an service engine? > using > jsr181 or CXF-SE. > For me this simplifies things ie. one less server to start up and deploy > to.... > > My question is the same as yesterday's poster's. What is good practice in > this regard in terms of SOA? > I know we can place it anywhere but whats good and whats not. > > Any experience in this regard is highly appreciated > > Ivanhoe > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
