You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by do...@yahoo.de on 2006/02/09 10:18:46 UTC

[Axis2] WSAMapping 0.95-SNAPSHOT

Hi there,

trying to use some of my services created under
release 0.94 in 0.95-SNAPSHOT I got problems with the
wsamapping.  Axis2 won't find the given operations any
more... are there some changes in services.xml syntax
or is it a configuration problem?

Thanks Ted


	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: [Axis2] WSAMapping 0.95-SNAPSHOT

Posted by do...@yahoo.de.
Sorry for annoying you again, here's some of the code
i used:

...
op.setSoapAction("urn:test/operation");
...
client = new ServiceClient();
client.setOptions(op);
client.engageModule(new QName("addressing"));
responseMessage = client.sendReceive(message);
...

This does not lead to a soapaction as wsamapping
value, is there a special method to call for this or
do I have to build the necessary soap header entrys by
myself?

Thanks
Ted



--- Deepal Jayasinghe <de...@opensource.lk> schrieb:

> 
> dont worry if you dont have any WSA-tag in the out
> going message , still
> you can access the operation , if you send the SOAP
> action correctly (i
> mean if you send the soap action as wsamapping
> value) , then it should work.
> 
> 
> 
> donnerdrummel2000-mailing@yahoo.de wrote:
> 
> >I think my problem is at client side. Using a
> >TCPMonitor I noticed that there are no more
> WSA-Tags
> >in my message. These tags were set by default under
> >0.94. So how can I set this behavior in
> 0.95-snapshot
> >as well?
> >
> >Thanks
> >Ted
> >--- Deepal Jayasinghe <de...@opensource.lk>
> schrieb:
> >
> >  
> >
> >>I am sure that should work if you correctly put
> your
> >>wsamapping in
> >>operation tag , any way if you are sure about this
> >>pls create a JIRA
> >>giving a sample service and client (if possible)
> >>
> >>Note : the mapping should look like below
> >><operation name="myOp">
> >>  <parameter name="wsamapping"
> >>    
> >>
> >>>Mymapping</parameter>
> >>>      
> >>>
> >></operation>
> >>
> >>~Deepal
> >>
> >>donnerdrummel2000-mailing@yahoo.de wrote:
> >>
> >>    
> >>
> >>>Hi there,
> >>>
> >>>trying to use some of my services created under
> >>>release 0.94 in 0.95-SNAPSHOT I got problems with
> >>>      
> >>>
> >>the
> >>    
> >>
> >>>wsamapping.  Axis2 won't find the given
> operations
> >>>      
> >>>
> >>any
> >>    
> >>
> >>>more... are there some changes in services.xml
> >>>      
> >>>
> >>syntax
> >>    
> >>
> >>>or is it a configuration problem?
> >>>
> >>>Thanks Ted
> >>>
> >>>
> >>>	
> >>>
> >>>	
> >>>		
> >>>      
> >>>
>
>>___________________________________________________________
> >>
> >>    
> >>
> >>>Telefonate ohne weitere Kosten vom PC zum PC:
> >>>      
> >>>
> >>http://messenger.yahoo.de
> >>    
> >>
> >>> 
> >>>
> >>>      
> >>>
> >>-- 
> >>Thanks,
> >>Deepal
> >>
> >>    
> >>
>
>................................................................
> >  
> >
> >>~Future is Open~ 
> >>
> >>
> >>
> >>    
> >>
> >
> >
> >
> >	
> >
> >	
> >		
>
>___________________________________________________________
> 
> >Telefonate ohne weitere Kosten vom PC zum PC:
> http://messenger.yahoo.de
> >
> >
> >  
> >
> 
> -- 
> Thanks,
> Deepal
>
................................................................
> ~Future is Open~ 
> 
> 
> 



	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: [Axis2] WSAMapping 0.95-SNAPSHOT

Posted by Deepal Jayasinghe <de...@opensource.lk>.
dont worry if you dont have any WSA-tag in the out going message , still
you can access the operation , if you send the SOAP action correctly (i
mean if you send the soap action as wsamapping value) , then it should work.



donnerdrummel2000-mailing@yahoo.de wrote:

>I think my problem is at client side. Using a
>TCPMonitor I noticed that there are no more WSA-Tags
>in my message. These tags were set by default under
>0.94. So how can I set this behavior in 0.95-snapshot
>as well?
>
>Thanks
>Ted
>--- Deepal Jayasinghe <de...@opensource.lk> schrieb:
>
>  
>
>>I am sure that should work if you correctly put your
>>wsamapping in
>>operation tag , any way if you are sure about this
>>pls create a JIRA
>>giving a sample service and client (if possible)
>>
>>Note : the mapping should look like below
>><operation name="myOp">
>>  <parameter name="wsamapping"
>>    
>>
>>>Mymapping</parameter>
>>>      
>>>
>></operation>
>>
>>~Deepal
>>
>>donnerdrummel2000-mailing@yahoo.de wrote:
>>
>>    
>>
>>>Hi there,
>>>
>>>trying to use some of my services created under
>>>release 0.94 in 0.95-SNAPSHOT I got problems with
>>>      
>>>
>>the
>>    
>>
>>>wsamapping.  Axis2 won't find the given operations
>>>      
>>>
>>any
>>    
>>
>>>more... are there some changes in services.xml
>>>      
>>>
>>syntax
>>    
>>
>>>or is it a configuration problem?
>>>
>>>Thanks Ted
>>>
>>>
>>>	
>>>
>>>	
>>>		
>>>      
>>>
>>___________________________________________________________
>>
>>    
>>
>>>Telefonate ohne weitere Kosten vom PC zum PC:
>>>      
>>>
>>http://messenger.yahoo.de
>>    
>>
>>> 
>>>
>>>      
>>>
>>-- 
>>Thanks,
>>Deepal
>>
>>    
>>
>................................................................
>  
>
>>~Future is Open~ 
>>
>>
>>
>>    
>>
>
>
>
>	
>
>	
>		
>___________________________________________________________ 
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>
>  
>

-- 
Thanks,
Deepal
................................................................
~Future is Open~ 



Re: [Axis2] WSAMapping 0.95-SNAPSHOT

Posted by do...@yahoo.de.
I think my problem is at client side. Using a
TCPMonitor I noticed that there are no more WSA-Tags
in my message. These tags were set by default under
0.94. So how can I set this behavior in 0.95-snapshot
as well?

Thanks
Ted
--- Deepal Jayasinghe <de...@opensource.lk> schrieb:

> I am sure that should work if you correctly put your
> wsamapping in
> operation tag , any way if you are sure about this
> pls create a JIRA
> giving a sample service and client (if possible)
> 
> Note : the mapping should look like below
> <operation name="myOp">
>   <parameter name="wsamapping"
> >Mymapping</parameter>
> </operation>
> 
> ~Deepal
> 
> donnerdrummel2000-mailing@yahoo.de wrote:
> 
> >Hi there,
> >
> >trying to use some of my services created under
> >release 0.94 in 0.95-SNAPSHOT I got problems with
> the
> >wsamapping.  Axis2 won't find the given operations
> any
> >more... are there some changes in services.xml
> syntax
> >or is it a configuration problem?
> >
> >Thanks Ted
> >
> >
> >	
> >
> >	
> >		
>
>___________________________________________________________
> 
> >Telefonate ohne weitere Kosten vom PC zum PC:
> http://messenger.yahoo.de
> >
> >
> >  
> >
> 
> -- 
> Thanks,
> Deepal
>
................................................................
> ~Future is Open~ 
> 
> 
> 



	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: [Axis2] WSAMapping 0.95-SNAPSHOT

Posted by Deepal Jayasinghe <de...@opensource.lk>.
I am sure that should work if you correctly put your wsamapping in
operation tag , any way if you are sure about this pls create a JIRA
giving a sample service and client (if possible)

Note : the mapping should look like below
<operation name="myOp">
  <parameter name="wsamapping" >Mymapping</parameter>
</operation>

~Deepal

donnerdrummel2000-mailing@yahoo.de wrote:

>Hi there,
>
>trying to use some of my services created under
>release 0.94 in 0.95-SNAPSHOT I got problems with the
>wsamapping.  Axis2 won't find the given operations any
>more... are there some changes in services.xml syntax
>or is it a configuration problem?
>
>Thanks Ted
>
>
>	
>
>	
>		
>___________________________________________________________ 
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>
>  
>

-- 
Thanks,
Deepal
................................................................
~Future is Open~