Re: "Creating a protocol bridge" tutorial's configs are differentfromBridgeexample's

[gauravsonline <sa...@techmahindra.com>]

Hi Gert,

Sorry, I just overlooked at the wiki. I have just now created an archetype
for "servicemix-saxon-xslt-service-unit". The pom.xml file has the saxon
dependency entry and the xbean.xml file as was desired. So we need not to
add any dependency and/or rename the file servicemix.xml to xbean.xml (as
was the case for "servicemix-lwcontainer-service-unit") as far as we are
using the "servicemix-saxon-xslt-service-unit" artifact. I think no changes
are required on the wiki on this front.

But the stylesheet version has to be modified from 1.0 to 2.0; otherwise it
gives the warning as: 
"Warning: at xsl:stylesheet of : 
Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor"

Regards,
Gaurav


Gert Vanthienen wrote:
> 
> Guarav,
> 
> Is this the only change that is necessary in the XSL file to switch to 
> version 2.0?
> 
> For what the saxon dependency is concerned:
> The previous version of the page used the 
> servicemix-lwcontainer-service-unit archetype to create the 
> bridge-xslt-su.  I have changed that to use 
> servicemix-saxon-xslt-service-unit and that one should automatically put 
> the correct dependency in there to start with.
> 
> Gert
> 
> gauravsonline wrote:
>> Thank you so much. Would like to suggest two more small changes, though
>> not
>> important but it would make the things more concrete.
>>
>> Actually in the XSLT SU, the xsl:stylesheet version is "1.0", which
>> should
>> be "2.0". If not the case then servicemix gives a warning that "saxon
>> engine
>> is 2.0 but the stylesheet version is 1.0".
>>
>> Secondly, the saxon dependency has to be added in the pom.xml file for
>> XSLT
>> SU.
>>
>> <dependencies>
>>         <dependency>
>>             <groupId>org.apache.servicemix</groupId>
>>             <artifactId>servicemix-saxon</artifactId>
>>             <version>3.1-incubating-SNAPSHOT</version>
>>         </dependency>
>> </dependencies>
>>
>> Hope this makes sense. As of know I just have these many changes only.
>>
>> Also thanks for ur reply on the second use case. I will now work on that.
>>
>> Regards....
>> Gaurav 
>>
>>
>> Gert Vanthienen wrote:
>>   
>>> L.S.,
>>>
>>>
>>> First of all, I have changed 
>>> http://cwiki.apache.org/confluence/display/SM/Creating+a+protocol+bridge.  
>>> Could you check if all necessary changes have been done?  This page will 
>>> get replicated to the main site after a while...
>>>
>>> For your second use case: if you do not need any transformations on the 
>>> message content, you can create a service assembly with two service
>>> units:
>>> - one SU based on servicemix-jms, defining the JMS consumer endpoint to 
>>> read messages from a JMS queue (cfr. 
>>> http://incubator.apache.org/servicemix/servicemix-jms.html for 
>>> configuration options)
>>> - the other SU based on servicemix-http, defining the HTTP provider 
>>> endpoint which points to your webservice (cfr. 
>>> http://incubator.apache.org/servicemix/servicemix-http.html for 
>>> configuration options)
>>>
>>> Beware that the service/endpoint name of you HTTP provider endpoint 
>>> should match the names defined in your webservice's WSDL.  You can 
>>> either use the same service/endpoint name on your JMS endpoint or use 
>>> the targetService/targetEndpoint attributes to do the routing.
>>>
>>>
>>> Regards,
>>>
>>> Gert
>>>
>>> gauravsonline wrote:
>>>     
>>>> HI,
>>>> Thanks for your help. Actualy just now I resolved the problem.
>>>> The problem was in the xslt-su. The archtyope by default generates the
>>>> servicemix.xml file and in the example code its xbean.xml file. So just
>>>> renaming the file from servicemix.xml to xbean.xml. The saxon
>>>> dependency
>>>> was
>>>> ok.
>>>>
>>>> Now the next step is to read the messages from the queue and call a web
>>>> service. Could you please help??
>>>>
>>>> Also I would like to request the moderator if they could update this
>>>> thing
>>>> at :
>>>> http://incubator.apache.org/servicemix/creating-a-protocol-bridge.html
>>>> http://incubator.apache.org/servicemix/creating-a-protocol-bridge.html 
>>>>
>>>> in the "XSLT SU" section, as this has costed me two days to resolve.
>>>>
>>>> Thanks all for your help!
>>>>       
>>>
>>>     
>>
>>   
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/%22Creating-a-protocol-bridge%22-tutorial%27s-configs-are-different-from-Bridge-example%27s-tf3162370s12049.html#a10429010
Sent from the ServiceMix - User mailing list archive at Nabble.com.