Yes you can. Last week we re-factored that constant to the proper place. If you have Axis2 1.0 then go ahead with that.
I thought you were using Axis2 nightly builds. -- Chinthaka Shyam Shukla wrote: > Hi Eran, > > I couldn't find "org.apache.axis2.Constants.Configuration.TRANSPORT_URL" in > my installed version of axis2 1.0 but the same constant I have got in > "org.apache.axis2.context.MessageContextConstants.TRANSPORT_URL" package. > > Can I use this one to fulfill my need? > > Best Regards, > Shyam Shukla > > -----Original Message----- > From: Eran Chinthaka [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 02, 2006 11:33 PM > To: [email protected] > Subject: Re: Customization of SOAP Envelop using Axis2 1.0 > > options.setProperty(org.apache.axis2.Constants.Configuration.TRANSPORT_URL, > "http://the-real-url-I-want-to-send-my-request.org";); > > > > Shyam Shukla wrote: >> Hi All, >> >> To solve wsa namespace issue as I've mentioned in this email, instead of >> modifying existing handlers I wrote separate handlers and they all are >> working fine to support WS-Addressing namespace >> "http://schemas.xmlsoap.org/ws/2004/03/addressing";. >> >> Now I have again come up with a problem, actually in my current project to >> obtain SAML Assertion from a web service which resides at remote location, > I >> will have to send SOAP request which contains WS-Addressing, WS-Trust, >> WS-Security and WS-Policy over http. I have implemented all these WS-* >> specification using axis2 architecture although I had some problems with >> WS-Addressing but that has been solved by all your inputs. >> >> The problem part is this >> > <wsa:To>urn:GSO-System-Services:external:1.65:GatewaySecurityTokenService</w >> sa:To> tag. As I understand, <wsa:To> tag must point to URL where SOAP >> request is posted and axis2 picks this value to send request over > transport >> protocol e.g. http but in my case as you can see I will have to provide a >> URN over http in a different location other than <wsa:To> value. >> >> I know there is axis2 API to set <wsa:To> tag value but then how will I > send >> it over http at different URL? >> >> >> >> Best Regards, >> Shyam Shukla >> >> -----Original Message----- >> From: Shyam Shukla [mailto:[EMAIL PROTECTED] >> Sent: Monday, July 31, 2006 3:46 PM >> To: '[email protected]' >> Subject: RE: Customization of SOAP Envelop using Axis2 1.0 >> >> Thanks David I've obtained this file and will go through it to make desire >> changes. >> >> I will again bother you if I am stuck somewhere. >> >> Thanks & Regards, >> Shyam Shukla >> >> >> -----Original Message----- >> From: David Illsley [mailto:[EMAIL PROTECTED] >> Sent: Monday, July 31, 2006 2:55 PM >> To: [email protected] >> Subject: Re: Customization of SOAP Envelop using Axis2 1.0 >> >> The AddressingOutHandler shipped with Axis2 (in the addressing module) >> which adds the soap headers can be found at [1]. >> >> David >> >> [1] >> > http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/addressing > /src/org/apache/axis2/handlers/addressing/AddressingOutHandler.java?view=mar >> kup >> >> On 31/07/06, Shyam Shukla <[EMAIL PROTECTED]> wrote: >>> David you got my point I was just going to reply Eran about this point. >>> Actually, in my current project web services which I have to invoke >> support >>> mentioned WSA namespace in this email >>> i.e."http://schemas.xmlsoap.org/ws/2004/03/addressing"; only and I am >>> required to write a client program to invoke those services. >>> So I think I will have to play with axis2 handlers. >>> David, can you please provide me the name and/or location of these > handler >>> file(s) to create only SOAP Request. >>> >>> >>> Best Regards, >>> Shyam Shukla >>> >>> -----Original Message----- >>> From: David Illsley [mailto:[EMAIL PROTECTED] >>> Sent: Monday, July 31, 2006 2:26 PM >>> To: [email protected]; [EMAIL PROTECTED] >>> Subject: Re: Customization of SOAP Envelop using Axis2 1.0 >>> >>> Eran, unfortunately Shyam is looking for the 2004/03 namespace which >>> the current addressing handlers do not support and if you sets the >>> WS_ADDRESSING_VERSION property to >>> "http://schemas.xmlsoap.org/ws/2004/03/addressing";, the submission >>> version is used. >>> >>> Shyam, if you can move up to a newer version of WS-Addressing that is >>> your best option (2004/03 is not widely supported now and won't be >>> going forward. There is broad vendor support for 2004/08 and 2005/08). >>> If you cannot move to one of these specifications, modifying the axis2 >>> handlers to support 2004/03 or writing your own handlers are your >>> other options. >>> >>> David >>> >>> -- >>> David Illsley - IBM Web Services Development >>> >>> On 31/07/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: >>>> No wait, you don't need to change the source code to do that. >>>> >>>> just do the following. >>>> >>>> options.setProperty( >>>> org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION, >>>> >> org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE); >>>> Hope you know how to set the options. >>>> >>>> (Your next question might be that what are the other params that can be >>>> set thru the client api. Do not worry an article on that is coming soon. >>>> There is a small delay in getting that published :).) >>>> >>>> -- Chinthaka >>>> >>>> Shyam Shukla wrote: >>>>> Thanks Chinthaka for your reply. >>>>> I've enabled WS-Addressing and have associated in my SOAP Request. >>>>> My problem is I want to modify the SOAP Envelop part in the request, >> by >>>>> default axis2 1.0 is referring to >>>>> "xmlns:wsa="http://www.w3.org/2005/08/addressing"; namespace as I have >>>>> mentioned in my email while I want WS-Addressing namespace should >> refer >>> to >>>>> "http://schemas.xmlsoap.org/ws/2004/03/addressing"; URL. >>>>> I have gone through all the addressing APIs of axis2 to find out any >> way >>> to >>>>> do it but could not be succeeded. >>>>> I guess now I will have to modify the source code which is responsible >>> for >>>>> generating this part of the SOAP request. >>>>> Can you please let me know which file will I be required to modify or >> Is >>>>> there any API to accomplish this task? >>>>> >>>>> >>>>> Best Regards, >>>>> Shyam Shukla >>>>> >>>>> -----Original Message----- >>>>> From: Eran Chinthaka [mailto:[EMAIL PROTECTED] >>>>> Sent: Monday, July 31, 2006 12:11 PM >>>>> To: [email protected] >>>>> Subject: Re: Customization of SOAP Envelop using Axis2 1.0 >>>>> >>>>> >>>>> What exactly you want to do here? Do you want to send a SOAP request >>>>> with WS-Addressing enabled? >>>>> If yes, the easiest way is to use the ServiceClient api with >> addressing >>>>> enabled (refer the user guide for this) >>>>> >>>>> -- Chinthaka >>>>> >>>>> Shyam Shukla wrote: >>>>>> Hello All, >>>>>> >>>>>> >>>>>> >>>>>> I am just started working with axis2 1.0 with wss4j 1.5 and my task >> is >>>>>> to create SOAP request which refers to WS-Addressing >>>>>> http://schemas.xmlsoap.org/ws/2004/03/addressing while I am getting >>>>>> following format in SOAP request: >>>>>> >>>>>> >>>>>> >>>>>> <soapenv:Envelope >>>>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >>>>>> xmlns:wsa="http://www.w3.org/2005/08/addressing";> >>>>>> >>>>>> >>>>>> >>>>>> Can anyone guide me how can I modify this request? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Thanks in Advance, >>>>>> Shyam Shukla >>>>>> >>>>>> >>>>>> >>>>>> DISCLAIMER ========== This e-mail may contain privileged and >>>>>> confidential information which is the property of Persistent Systems >>>>>> Pvt. Ltd. It is intended only for the use of the individual or entity >>> to >>>>>> which it is addressed. If you are not the intended recipient, you are >>>>>> not authorized to read, retain, copy, print, distribute or use this >>>>>> message. If you have received this communication in error, please >>> notify >>>>>> the sender and delete all copies of this message. Persistent Systems >>>>>> Pvt. Ltd. does not accept any liability for virus infected mails. >>>>> >>>>> >>>>> DISCLAIMER >>>>> ========== >>>>> This e-mail may contain privileged and confidential information which >> is >>> the property of Persistent Systems Pvt. Ltd. It is intended only for the >> use >>> of the individual or entity to which it is addressed. If you are not the >>> intended recipient, you are not authorized to read, retain, copy, print, >>> distribute or use this message. If you have received this communication > in >>> error, please notify the sender and delete all copies of this message. >>> Persistent Systems Pvt. Ltd. does not accept any liability for virus >>> infected mails. >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> DISCLAIMER >>> ========== >>> This e-mail may contain privileged and confidential information which is >> the property of Persistent Systems Pvt. Ltd. It is intended only for the > use >> of the individual or entity to which it is addressed. If you are not the >> intended recipient, you are not authorized to read, retain, copy, print, >> distribute or use this message. If you have received this communication in >> error, please notify the sender and delete all copies of this message. >> Persistent Systems Pvt. Ltd. does not accept any liability for virus >> infected mails. >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> > > > > > DISCLAIMER > ========== > This e-mail may contain privileged and confidential information which is the > property of Persistent Systems Pvt. Ltd. It is intended only for the use of > the individual or entity to which it is addressed. If you are not the > intended recipient, you are not authorized to read, retain, copy, print, > distribute or use this message. If you have received this communication in > error, please notify the sender and delete all copies of this message. > Persistent Systems Pvt. Ltd. does not accept any liability for virus infected > mails. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
signature.asc
Description: OpenPGP digital signature
