Return-Path: 
 <axis-dev-return-47846-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 16149 invoked from network); 3 Aug 2006 10:35:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 3 Aug 2006 10:35:44 -0000
Received: (qmail 62081 invoked by uid 500); 3 Aug 2006 10:35:39 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 61450 invoked by uid 500); 3 Aug 2006 10:35:37 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 61439 invoked by uid 99); 3 Aug 2006 10:35:37 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2006 03:35:37 -0700
X-ASF-Spam-Status: No, hits=0.6 required=10.0
	tests=NO_REAL_NAME
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [203.91.193.21] (HELO wip-ectls-mx1.wipro.com) (203.91.193.21)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2006 03:35:36 -0700
Received: from wip-ectls-mx1.wipro.com (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 9A23F220587;
	Thu,  3 Aug 2006 16:05:09 +0530 (IST)
Received: from blr-ec-bh02.wipro.com (blr-ec-bh02.wipro.com [10.201.50.92])
	by wip-ectls-mx1.wipro.com (Postfix) with ESMTP id 8D86322017E;
	Thu,  3 Aug 2006 16:05:09 +0530 (IST)
Received: from chn-gdy-msg.wipro.com ([10.146.50.99]) by blr-ec-bh02.wipro.com
 with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 3 Aug 2006 16:05:04 +0530
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Need info
Date: Thu, 3 Aug 2006 16:05:00 +0530
Message-ID: <9A85AAC2668A8E4DB9561F85087ECD007D61FD@chn-gdy-msg.wipro.com>
In-Reply-To: <039a01c6b6e7$495bc750$6ec74d0a@persistent.co.in>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Need info
Thread-Index: Aca2xStsqCzZInNUREON3jYSYy0LWgAH705gAAC0RTA=
From: <sudhakar.kondapalli@wipro.com>
To: <axis-dev@ws.apache.org>, <chinthaka@opensource.lk>
X-OriginalArrivalTime: 03 Aug 2006 10:35:04.0144 (UTC)
 FILETIME=[7B26B500:01C6B6E8]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


=0D
Hi All,

  I am basically Java, j2ee guy, But I am very much new to  Webservices.

My present task is , I need to create one search engine , but our client
having that search engine which is already developed in .NET .

So now I want to use that component by using webservices , for that I
searched in net , I got some information regarding axis2 . I down loaded
that axis-1_4 .=0D

I not able to proceed how to start and how to configure that with
tomcat, please any one can explain how to acces that .NET conponent in
my J2ee application.



Thanks and Regards
Sudhakar Kondapalli
=0D

-----Original Message-----
From: Shyam Shukla [mailto:shyam_shukla@persistent.co.in]=0D
Sent: Thursday, August 03, 2006 3:56 PM
To: axis-dev@ws.apache.org; chinthaka@opensource.lk
Subject: RE: Customization of SOAP Envelop using Axis2 1.0

Thanks Eran it worked and now I have one more problem... :) In my SOAP
request header under <wsse:Security> tag, there is <Timestamp> tag as
below:

<wsu:Timestamp
xmlns:wsu=3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urit
y-utility-1.0.xsd" wsu:Id=3D"Timestamp-2086370">

	<wsu:Created>2006-08-02T11:39:58.015Z</wsu:Created>
	<wsu:Expires>2006-08-02T11:44:58.015Z</wsu:Expires>
</wsu:Timestamp>=0D

My task is to modify the format of <wsu:Created> and <wsu:Expires> tags
in a different format like yyyy-mm-ddThh:mm:ssZ and also want to change
the timezone.

Please guide me the way to accomplish this?

Best Regards,
Shyam Shukla

-----Original Message-----
From: Eran Chinthaka [mailto:chinthaka@opensource.lk]
Sent: Thursday, August 03, 2006 11:51 AM
To: axis-dev@ws.apache.org
Subject: Re: Customization of SOAP Envelop using Axis2 1.0

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,
>=0D
> 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=0D
> "org.apache.axis2.context.MessageContextConstants.TRANSPORT_URL"
package.
>=0D
> Can I use this one to fulfill my need?
>=0D
> Best Regards,
> Shyam Shukla
>=0D
> -----Original Message-----
> From: Eran Chinthaka [mailto:chinthaka@opensource.lk]
> Sent: Wednesday, August 02, 2006 11:33 PM
> To: axis-dev@ws.apache.org
> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
>=0D
>
options.setProperty(org.apache.axis2.Constants.Configuration.TRANSPORT_U
RL,
> "http://the-real-url-I-want-to-send-my-request.org");
>=0D
>=0D
>=0D
> 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=0D
>> "http://schemas.xmlsoap.org/ws/2004/03/addressing".
>>
>> Now I have again come up with a problem, actually in my current=0D
>> 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,=0D
>> 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:GatewaySecurityTokenServic
e</w
>> sa:To> tag. As I understand, <wsa:To> tag must point to URL where=0D
>> SOAP request is posted and axis2 picks this value to send request=0D
>> over
> transport
>> protocol e.g. http but in my case as you can see I will have to=0D
>> 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?
>>
>>   =0D
>>
>> Best Regards,
>> Shyam Shukla
>>
>> -----Original Message-----
>> From: Shyam Shukla [mailto:shyam_shukla@persistent.co.in]
>> Sent: Monday, July 31, 2006 3:46 PM
>> To: 'axis-dev@ws.apache.org'
>> 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:davidillsley@gmail.com]
>> Sent: Monday, July 31, 2006 2:55 PM
>> To: axis-dev@ws.apache.org
>> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
>>
>> The AddressingOutHandler shipped with Axis2 (in the addressing=0D
>> module) which adds the soap headers can be found at [1].
>>
>> David
>>
>> [1]
>>
>
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/addres
sing
>
/src/org/apache/axis2/handlers/addressing/AddressingOutHandler.java?view
=3Dmar
>> kup
>>
>> On 31/07/06, Shyam Shukla <shyam_shukla@persistent.co.in> 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=0D
>>> 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:davidillsley@gmail.com]
>>> Sent: Monday, July 31, 2006 2:26 PM
>>> To: axis-dev@ws.apache.org; chinthaka@opensource.lk
>>> 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=0D
>>> WS_ADDRESSING_VERSION property to=0D
>>> "http://schemas.xmlsoap.org/ws/2004/03/addressing", the submission=0D
>>> version is used.
>>>
>>> Shyam, if you can move up to a newer version of WS-Addressing that=0D
>>> is your best option (2004/03 is not widely supported now and won't=0D
>>> 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=0D
>>> axis2 handlers to support 2004/03 or writing your own handlers are=0D
>>> your other options.
>>>
>>> David
>>>
>>> --
>>> David Illsley - IBM Web Services Development
>>>
>>> On 31/07/06, Eran Chinthaka <chinthaka@opensource.lk> 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_VERSI
>>>> ON,
>>>>
>>
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=0D
>>>> can be set thru the client api. Do not worry an article on that is=0D
>>>> 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=0D
>>>>> request,
>> by
>>>>> default axis2 1.0 is referring to
>>>>> "xmlns:wsa=3D"http://www.w3.org/2005/08/addressing" namespace as I=0D
>>>>> have mentioned in my email while I want WS-Addressing namespace=0D
>>>>> 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=0D
>>>>> any
>> way
>>> to
>>>>> do it but could not be succeeded.
>>>>> I guess now I will have to modify the source code which is=0D
>>>>> 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:chinthaka@opensource.lk]
>>>>> Sent: Monday, July 31, 2006 12:11 PM
>>>>> To: axis-dev@ws.apache.org
>>>>> Subject: Re: Customization of SOAP Envelop using Axis2 1.0
>>>>>
>>>>>
>>>>> What exactly you want to do here? Do you want to send a SOAP=0D
>>>>> 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=0D
>>>>>> task
>> is
>>>>>> to create SOAP request which refers to WS-Addressing=0D
>>>>>> http://schemas.xmlsoap.org/ws/2004/03/addressing while I am=0D
>>>>>> getting following format in SOAP request:
>>>>>>
>>>>>>
>>>>>>
>>>>>> <soapenv:Envelope
>>>>>> xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/"
>>>>>> xmlns:wsa=3D"http://www.w3.org/2005/08/addressing">
>>>>>>
>>>>>>
>>>>>>
>>>>>> Can anyone guide me how can I modify this request?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks in Advance,
>>>>>> Shyam Shukla
>>>>>>
>>>>>>
>>>>>>
>>>>>> DISCLAIMER =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D This e-mail may contain=
 privileged and=0D
>>>>>> confidential information which is the property of Persistent=0D
>>>>>> Systems Pvt. Ltd. It is intended only for the use of the=0D
>>>>>> 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=0D
>>>>>> use this message. If you have received this communication in=0D
>>>>>> error, please
>>> notify
>>>>>> the sender and delete all copies of this message. Persistent=0D
>>>>>> Systems Pvt. Ltd. does not accept any liability for virus
infected mails.
>>>>>
>>>>>
>>>>> DISCLAIMER
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>> This e-mail may contain privileged and confidential information=0D
>>>>> 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,=0D
>>> copy, print, distribute or use this message. If you have received=0D
>>> 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: axis-dev-unsubscribe@ws.apache.org
>>>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>>
>>>
>>> DISCLAIMER
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> This e-mail may contain privileged and confidential information=0D
>>> which is
>> the property of Persistent Systems Pvt. Ltd. It is intended only for=0D
>> the
> use
>> of the individual or entity to which it is addressed. If you are not=0D
>> the intended recipient, you are not authorized to read, retain, copy,

>> print, distribute or use this message. If you have received this=0D
>> 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=0D
>> infected mails.
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>>
>>>
>>
>=0D
>=0D
>=0D
>=0D
> DISCLAIMER
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> This e-mail may contain privileged and confidential information which=0D
> 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.
>=0D
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>=0D
>=0D




DISCLAIMER
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org



The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and=
 may contain proprietary, confidential or privileged information. If you=
 are not the intended recipient, you should not disseminate, distribute or=
 copy this e-mail. Please notify the sender immediately and destroy all=
 copies of this message and any attachments.=0D

WARNING: Computer viruses can be transmitted via email. The recipient=
 should check this email and any attachments for the presence of viruses.=
 The company accepts no liability for any damage caused by any virus=
 transmitted by this email.
=0D
www.wipro.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org