RE: Message Addressing Property error

t; > Whelan, Andy > > to: > > axis-user@ws.apache.org > > 30/11/2009 17:47 > > Please respond to axis-user > > Brian > Does WS-Addressing work if it is being sent to an older style JAX- > RPC service? > > From: Brian De Pradine [mailto:prad...

Re: Message Addressing Property error

Hello Andrew, The message indicates that one of the WS-Addressing related headers being sent by your client is not valid, as far as Axis2 is concerned. In order to work out which header you should try again to get TCPMon working, or use the SOAP Monitor described here, [1] [1] http://ws.apache

Re: WS Addressing - Include MessageID in response

ing to modify the module.xml file. > > Andreas > > On Sun, May 24, 2009 at 19:49, Brian De Pradine wrote: > > > > Hi Mohannad, > > > > The only way to do this at the moment is to modify the module.xml file in > > the adddressing.mar to add a parameter

Re: WS Addressing - Include MessageID in response

Hi Mohannad, The only way to do this at the moment is to modify the module.xml file in the adddressing.mar to add a parameter. The parameter should set includeOptionalHeaders to true. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246

Re: It seems that the WS-Addressing Endpoint Unavailable fault is not handled by Axis2, is it?

Hello Jose, On the server side, we never throw an Endpoint Unavailable fault as it is optional and it is not currently needed in axis2. On the client side, we never retransmit messages regardless of the presence or absence of a RetryAfter property. If you are interested in message re-transmiss

Re: Inconsistent behaviour in AddressingOutHandler

Hi Sharath, This issue has been discussed as a part of [1]. I suggest you have a look at it. [1] http://issues.apache.org/jira/browse/AXIS2-3987 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do i

Re: axis2 1.4 and later versions fail to deploy with Java 1.4.2 under RAD6/WAS6.0

Hi Ramesh, In order to get Axis2 1.4 to work with Java 1.4 you need to comment out the following in your axis2.xml file: Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it rig

Re: Null EndpointDescription Parameter in JAXWSMessageReceiver

Hi Ben, I am not sure if this still works. You might be better off repackaging your service as a jar file, and dropping it in your axis2_home/repository/servicejars directory. The JAXWSDeployer will examine all jars within that directory and deploy those classes that have JAX-WS annotations wh

Re: Axis2 WS-Addressing messageid in response

Hi Erwin, Something like the following should work, MessageContext inContext = MessageContext.getCurrentMessageContext(); OperationContext operationContext = inMessageContext.getOperationContext(); MessageContext outMessageContext = operationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL

Re: Setting service scope on JAXWS service

Hi Steve, I do not believe that there is anyway to do this at the moment. Please raise a JIRA issue [1] so that the requirement is not lost. [1] http://issues.apache.org/jira/browse/AXIS2 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal

Re: Axis2 1.4 WAR Distribution: Unsupported major.minor version 49.0

Hello Chris, If you are not using JAX-WS (and as you are using a 1.4.2 jre you aren't) then you can eliminate the errors editing your axis2.xml file to remove the following: Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 In

Re: ServiceClient Port Location Versus Options.setTo(EndpointReference)

Hi Jay, This behaviour doesn't sound correct. Please raise a JIRA [1] and add a few more details on how the client is performing the invocation. Thanks [1] http://issues.apache.org/jira/browse/AXIS2 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319

Re: [Axis2] ws-addressing metadata support?

Hi Enric, I believe that axis2 1.4 will support everything except the WS-Policy extensions for WSDL. It still depends on the older wsaw:UsingAddressing extension. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't fin

Re: Excepetion in AddressingInFaultHandler

Hi Appu, Please create a JIRA to cover this issue. Also, can you gather the request-reponse flow in TCPMon so that we can see what the fault looks like that is coming back to the client. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal

Re: [AXIS2] RESTful using Sun JAX-RS and AXIS2 SOAP

Hi Venky, This is definitely not in the next release of axis2 (i.e. version 1.4), but feel free to raise a JIRA so that it may be considered for a future release. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't fin

Re: WS-Addressing help

r side? > > Regards, > Nuria. > > > > 2008/2/25, Brian De Pradine <[EMAIL PROTECTED]>: > > Hi Nuria, > > You can find information about WS-Addressing support and samples > here, [1] and [2]. > > You can find some information on WS-Policy support here

Re: WS-Addressing help

Hi Nuria, You can find information about WS-Addressing support and samples here, [1] and [2]. You can find some information on WS-Policy support here, [3] [1] http://ws.apache.org/axis2/1_3/adv-userguide.html#client [2] http://ws.apache.org/axis2/1_3/dii.html [3] http://ws.apache.org/axis2/1_3/

Re: Help for WS-Addressing on RPC Client

Hello Regivaldo, You need to set the action explicitly. Try setting the action as follows: options.setAction("..."); Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where

Re: axis2 1.3 wsa:To header usage

Hello Erwin, The thing about intermediaries is that they are usually there to hide the address of the of the ultimate receiver ( imagine a gateway server or proxy for instance ). In that case flowing the address of the ultimate receiver across the intermediary would tend to make having the int

Re: [Axis2] JAX-WS & working at xml level on the client side

nd\""); > } > } > } > > > /** > * @param args > * @throws Exception > */ > public static void main(String[] args) throws Exception { > BasicConfigurator.configure(); > SOAP12Dispatch

Re: [Axis2] JAX-WS & working at xml level on the client side

first time, where will you find the time to do it again? Michele Mazzucco <[EMAIL PROTECTED]> wrote on 11/10/2007 12:47:39: > Hi Brian, > > what do you mean?, do you have any example? > > Thanks, > Michele > > On Thu, 2007-10-11 at 12:45 +0100, Brian De Pr

Re: [Axis2] JAX-WS & working at xml level on the client side

Hello Michele, Try creating a dispatch client. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Michele Mazzucco <[EMAIL PRO

Re: [Axis2] JAX-WS & async server

Hello Michele, Axis2 does not support this Sun proprietary extension. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Miche

Re: [Axis2] javax.xml.ws.soap.Addressing is missing?

Hello Michele, Axis2 does not yet support JAX-WS 2.1, but we are working on it. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it agai

Re: WS-Addressing ReplyTo processing

Hello David, There is no support in Axis2 for doing this at the moment, at least not without modifying the source code directly to add new 'anonymous URIs'. However, this feature may be something that could be added in the future. Please raise a jira [1] so that the requirement does not get los

Re: Addressig configuration at server's side

Hello Marc, If you send a request using the Submission version of WS-Addressing then the response will automatically use the Submission version as well. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time

Re: [Axis2-1.2] how to omit ReplyTo header in outgoing one-way messages

]> wrote on 28/06/2007 22:51:54: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Brian, > > Did you mean to say we should enable this for both addressing versions? > Just wanted to clarify. If yes +1 from me. > > Thanks, > Chinthaka > > Brian De Prad

Re: [Axis2-1.2] how to omit ReplyTo header in outgoing one-way messages

Hello Andreas and Chinthaka, You are correct that the INCLUDE_OPTIONAL_HEADERS property is only used for 2005/08 addressing. It is used to turn on/off the spec defined defaulting behaviour with regard to the addressing headers sent in a message. As the 2004/08 spec does not define similar defau

Re: Axis2-1.2 - missing WS-Addressing headers on the client call

Hello Shantanu, Please raise a JIRA for this issue. Thanks. [1] http://issues.apache.org/jira/browse/AXIS2 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you

Re: AXIS2 : FAULT_ADDRESSING_HEADER_REQUIRED_REASON

Hello Zakaria, To identify the immediate problem you can use TCPMon to look at the fault message that is being returned to the client. This will allow you to identify the header that the server is complaining about and to take corrective action in your application. As far as the missing resour

Re: AXIS2 : FAULT_ADDRESSING_HEADER_REQUIRED_REASON

Hello Zakaria, The message indicates that a required ws-addressing header was missing in the request message and so an exception was returned to the client. On the client the resource bundle containing the actual error message could not be found. What version of axis2 are you using? Cheers Br

Re: SOAPAction mismatch invoking service

Hello Jose, Please raise a JIRA issue to cover this. Thanks. http://issues.apache.org/jira/browse/AXIS2 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you fi

Re: Axis2: mandating WS-Addressing ReferenceParameters from the client

Hello Shantanu, I suspect that this is a bug. Please raise a JIRA issue to cover this. Thanks. http://issues.apache.org/jira/browse/AXIS2 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right

Re: asynchronous messaging question

Hello Michele, I would expect the addressing module to work with the jms transport. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it

Re: [axis2] Axis fault addressing versions

Hello Alan, Please raise a jira to cover this problem. Thanks. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? "alan birtle

Re: [Axis2] Session Management and WS-Addressing

viceGroupId, he can use the same session, and the service can > maintain the session-related data. Unlike a request session, a SOAP > session has a default timeout period, so if the client does not > touch the service for 30 seconds, the session will expire, and if > the client sends th

Re: [Axis2] Session Management and WS-Addressing

Hello, You may find the following link useful, [1] [1] http://www.developer.com/java/web/article.php/3620661 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will y

Re: [Axis2] A required header representing a Message Addressing Property is not present

Hello Nicholas, I believe that you need to explicitly add an action in your client code. options.setAction("urn:doWork"); Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time,

RE: Problem in changes the value of WSA_NAMESPACE

oes this then please let me know. > > Thanks, > Amit Soni > > > From: Brian De Pradine [mailto:[EMAIL PROTECTED] > Sent: Friday, January 12, 2007 5:28 PM > To: axis-user@ws.apache.org > Subject: Re: Problem in changes the value of WSA_NAMESPACE > > > Hello Am

Re: Problem in changes the value of WSA_NAMESPACE

Hello Amit, Axis2 only supports the http://schemas.xmlsoap.org/ws/2004/08/addressing and http://www.w3.org/2005/08/addressing namespaces so what you are trying to do won't work. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 I

RE: axis2 redirection

e.sendRedirect of jsp. So that along with 302 > code is also send the url to resend. But I think in axis2 it is not > handling this. > > Using Axis2-1.1 I found some bug in that and I am not able to > generate the client it self. So I have to use Axis2-1.0 > > > Thanks

Re: axis2 redirection

Hello Amit, Can you provide some more details on what you are trying to do? Also, have you considered trying Axis2 1.1? Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, wh

Re: EndpointReferenceHelper missing

Hello Jose, If you are using Axis2 1.1 then the EndpointReferenceHelper is in addressing.mar Otherwise, you can use the latest nightly build where the EndpointReferenceHelper has been moved to axis2-kernel.jar Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962

Re: support for wsdm (ws-rt, ws-rf ....)

Hello Wolfgang, You should try the link [1]. [1] http://ws.apache.org/muse/ Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again?

RE: WS Addressing :: Axis2 :: JMS Webs ervice lookup issues

Hello Vaibhav, I would have responded earlier, but I was out last week. Anyway, I recall from one of your earlier emails that you were using WebSphere to host your JMS web service. If this is the case, then you may be able to use the new client here [1] to access it. This client runs in a J2SE en

Re: WS Addressing :: http requests response (ReplyTo) on JMS protocol

Hello Vaibhav, I don't think that there is any documentation covering this scenario at the moment, but feel free to contribute some when you finally get it working :-) I would expect the scenario to work, using axis2 1.1, even though I am not sure how you would go about setting up the JMS resour

Re: WS Addressing :: Issue with setting ReplyTo :: Axis2-1.1-SNAPSHOT

Hello Vaibhav, If you want to send a request and have the reply go to somewhere other than the original client then you should not use ServiceClient.sendReceiveNonBlocking(). Instead you should set the ReplyTo using Options.setReplyTo() and then use ServiceClient.fireAndForget(). Cheers Brian D

RE: Urgently need helps - problems with Axis2

Hello, Can you try as._getServiceClient().getOptions().setAction("traceJob"); Cheers Brian DePradine Web Services Development IBM Hursley External  +44 (0) 1962 816319         Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again?

Re: [Axis2] how does Axis know what operation to invoke?

Hello Nirmit, Your SOAPAction will not be in the SOAPEnvelope it will be in the HTTP headers. You can set it by using Options.setAction() in your client code. If you want the action included in the SOAPEnvelope then you must engage the addressing module. Cheers Brian DePradine Web Services Deve

Re: [Axis2] WS soap action question

Hello Wes, Why do you want to check wsa:action first? If soap action and wsa:action are both set then they must be the same, otherwise a fault should be generated. Anyway, the only way at the moment to look at the wsa:action is to engage the Addressing module. This will cause the addressing handl

Re: [Axis2]client ignoring timeout settings

Hello, options.setTimeOutInMilliSeconds() works for me. Cheers Brian DePradine Web Services Development IBM Hursley External  +44 (0) 1962 816319         Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Andrew B <[EMAIL PR

Re: [Axis2] ServiceClient - empty SOAP headers

Hello, It sounds like you haven't engaged the Addressing module in your client. See the EchoNonBlockingDualClient example in the Axis2 User's Guide for details on how to do this. Cheers Brian DePradine Web Services Development IBM Hursley External  +44 (0) 1962 816319         Internal 246319