You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Joern Schimmelpfeng <jo...@hp.com> on 2006/08/17 10:56:37 UTC
Complex Message Transformations
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#a5847712
Sent from the ServiceMix - Dev forum at Nabble.com.
Re: Complex Message Transformations
Posted by radu3000 <Ra...@us.ing.com>.
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.
Re: Complex Message Transformations
Posted by Joern Schimmelpfeng <jo...@hp.com>.
Thanks for all replies so far.
So to answer your quesiton Ramon,
we have CRUD operations on 50 different data types. So the operations all
are similar but the content may be qutie differnt.
So I never heard about a modal XSTL. Can you give me hint what that is?
Thanks a lot
Joern
Ramon Buckland-4 wrote:
>
> Hi Joern,
>
> Perhaps you could give a bit of an example of the message formats you
> are dealing with. Are the 50 message types logically similar ?
> or are they vastly different (and each one very different) ?
>
> I am thinking a modal based XSLT would assist.
>
> Regards
> Ramon
>
>
> Guillaume Nodet wrote:
>> I think ease of use is always a valid goal :)
>>
>> How do you plan to select the xslt to apply ? Using xpath rules inside
>> the xslt component ?
>>
>> You may already be able to do that if you merge all your xslt inside
>> one (and use imports maybe so that you can keep them in their own
>> files). The problem would be that each imported xslt must have its
>> own template names so that they don't clash.
>>
>> One other way would be to enhance the xslt component so that it can
>> use a property on the message / exchange to give the path to the xslt.
>> Then you could implement a message enhancer which would put this
>> property before calling the xslt component.
>>
>> On 8/17/06, Joern Schimmelpfeng <jo...@hp.com> 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#a5847712
>>>
>>> Sent from the ServiceMix - Dev forum at Nabble.com.
>>>
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Complex-Message-Transformations-tf2120280.html#a5869763
Sent from the ServiceMix - Dev forum at Nabble.com.
Re: Complex Message Transformations
Posted by Ramon Buckland <no...@thebuckland.com>.
Hi Joern,
Perhaps you could give a bit of an example of the message formats you
are dealing with. Are the 50 message types logically similar ?
or are they vastly different (and each one very different) ?
I am thinking a modal based XSLT would assist.
Regards
Ramon
Guillaume Nodet wrote:
> I think ease of use is always a valid goal :)
>
> How do you plan to select the xslt to apply ? Using xpath rules inside
> the xslt component ?
>
> You may already be able to do that if you merge all your xslt inside
> one (and use imports maybe so that you can keep them in their own
> files). The problem would be that each imported xslt must have its
> own template names so that they don't clash.
>
> One other way would be to enhance the xslt component so that it can
> use a property on the message / exchange to give the path to the xslt.
> Then you could implement a message enhancer which would put this
> property before calling the xslt component.
>
> On 8/17/06, Joern Schimmelpfeng <jo...@hp.com> 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#a5847712
>>
>> Sent from the ServiceMix - Dev forum at Nabble.com.
>>
>>
>
>
Re: Complex Message Transformations
Posted by Guillaume Nodet <gn...@gmail.com>.
I think ease of use is always a valid goal :)
How do you plan to select the xslt to apply ? Using xpath rules inside
the xslt component ?
You may already be able to do that if you merge all your xslt inside
one (and use imports maybe so that you can keep them in their own
files). The problem would be that each imported xslt must have its
own template names so that they don't clash.
One other way would be to enhance the xslt component so that it can
use a property on the message / exchange to give the path to the xslt.
Then you could implement a message enhancer which would put this
property before calling the xslt component.
On 8/17/06, Joern Schimmelpfeng <jo...@hp.com> 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#a5847712
> Sent from the ServiceMix - Dev forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet