adding soap heander in combination with soap conversion
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
adding soap heander in combination with soap conversion
by Niek Palm
::
Rate this Message:
Hi,
I am trying to add extra information in the soap headers. I have a soap service speaking SOAP 1.1 and potentials clients speaking SOAP 1.1 or SOAP 1.2. I using synpase 1.2 So first I have an endpoint defining my service. <endpoint name="MyEndpoint"> <address uri="http://localhost:8300/soap/service" format="soap11" /> </endpoint> And next a proxy for my clients, The proxy can be invoked over http and https with SOAP 1.1 or SOAP 1.2 messages. <proxy name="MyProxy" transport="http, https"> <target> <inSequence> <header name="mi:info" value="some text" action="set" xmlns:mi="http://www.company.com/metainfo" /> <send><endpoint key="MyEndpoint"></endpoint></send> </inSequence> </target> </proxy> When I simulate a client speaking SOAP 1.1 everything works well. The headers is added to the messages. In case I send a source message by the client using SOAP 1.2 the extra header is not added by synapse. Can anybody help me. Is my configuration wrong? Or is this potential a bug in synapse or axis? Is it possible that the headers are lost during transformation from soap12 to soap11? Regards, Niek Palm ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2 |
|
|
Re: adding soap heander in combination with soap conversion
by Ruwan Linton
::
Rate this Message:
Hi Niek,
I had a quick look at the code which is doing the conversion of the message format from SOAP12 to SOAP11 in the trunk/1.3 active branch and it seems to be copying all the headers including the custom headers. I will test your exact scenario when I get some free time, but at the same time can you please have a look at this with a build from the 1.3 branch?? If there is any issue on the 1.3 branch we can get that fixed for the 1.3 release of Synapse which will be released soon. Thanks, Ruwan 2009/8/20 Niek Palm <niek.palm@...> > Hi, > > I am trying to add extra information in the soap headers. I have a soap > service speaking SOAP 1.1 and potentials clients speaking SOAP 1.1 or > SOAP 1.2. I using synpase 1.2 > > So first I have an endpoint defining my service. > > <endpoint name="MyEndpoint"> > <address uri="http://localhost:8300/soap/service" format="soap11" /> > </endpoint> > > And next a proxy for my clients, The proxy can be invoked over http and > https with SOAP 1.1 or SOAP 1.2 messages. > > <proxy name="MyProxy" transport="http, https"> > <target> > <inSequence> > <header name="mi:info" value="some text" action="set" > xmlns:mi="http://www.company.com/metainfo" /> > <send><endpoint key="MyEndpoint"></endpoint></send> > </inSequence> > </target> > </proxy> > > When I simulate a client speaking SOAP 1.1 everything works well. The > headers is added to the messages. In case I send a source message by the > client using SOAP 1.2 the extra header is not added by synapse. > > Can anybody help me. Is my configuration wrong? Or is this potential a > bug in synapse or axis? Is it possible that the headers are lost during > transformation from soap12 to soap11? > > Regards, Niek Palm > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@...; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com |
|
|
|
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |
