Ditto - on "difficult maintance task" Here is our solution - http://www.nabble.com/forum/ViewPost.jtp?post=5906613&framed=y http://www.nabble.com/forum/ViewPost.jtp?post=5906613&framed=y
For maintaining it we would like to use a standalone data model - outside servicemix and again Ditto - "but I'm also not sure if this would violate the EIP concept." Where does this EIP concept is defined? Regards, Radu. Joern Schimmelpfeng wrote: > > Hello, > > I have a question related to the usage of the transformation component. > > We are trying to attach a complex WS datasource to ServiceMix. Our data > souce has round about 50 services with different messages. So this measns > that we need to provide 50 XSLT files for transforming a message for a WS > request and we need another 50 XSLT files for transforming the responses. > > Our service assembly today is that way that we use a router slip, two > transformers and a WS Client for integrating just one service, so need to > replicate that 50 times. > > As you can imagine this leads to a pretty difficult maintance task and > perhaps also to an unecessary high overhead inside ServiceMix. > > So my question is, if there is a way to enhance the transfomation > component so that it is able to select the correct XSLT file itself > depending on the message content and direction (e.g Request/Response). > > I feel myself able to enhance the transformation component that way, but > I'm also not sure if this would violate the EIP concept. > > Please can you give me some guidance how others solved this issue or if a > more complex transformation component would be a valuable goal to > implement? > > Thanks for any help on that issue > Joern > -- View this message in context: http://www.nabble.com/Complex-Message-Transformations-tf2120280.html#a5908675 Sent from the ServiceMix - Dev forum at Nabble.com.
