Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [jira] Created: (CXF-133) Support sending HTTP GET using JAX-WS
 dispatch
Date: Sat, 30 Sep 2006 08:10:18 +0100
Message-ID: <6E76AADE4AD1EC428BEC803AD204C21A03977418@SGBEMB2101.wsatkins.com>
Thread-Topic: [jira] Created: (CXF-133) Support sending HTTP GET using JAX-WS
 dispatch
Thread-Index: AcbkQ5Gvq5aD/x98TFa538RX5nhCHAAG7dcQ
From: "Shaw, Richard A" <richard.shaw@atkinsglobal.com>
To: <cxf-dev@incubator.apache.org>

Does using JAX-WS to perform a HTTP GET allow handlers to be added to the r=
equest ?

If so then I see this as a benefit of using it.

I have a use case in my architecture for this, we have a generic logging co=
mponent which intercepts the logical message in a a handler and writes to a=
 log database. At the moment we can't use it for HTTP GET interfaces.


Richard Shaw

=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=A4=BA=B0`=B0=BA=A4=
=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4

Richard Shaw=20=20
Technical Design Authority - Information Solutions Consultancy=20=20
Intelligent Transport Systems=20

Atkins Highways and Transportation=20
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW

Tel: +44 (0) 1372 756407=20
Fax: +44 (0) 1372 740055
Mob: 07740 817586=20
E-mail: richard.shaw@atkinsglobal.com

www.atkinsglobal.com/its

-----Original Message-----
From: Jervis Liu (JIRA) [mailto:jira@apache.org]=20
Sent: 30 September 2006 04:50
To: cxf-issues@incubator.apache.org
Subject: [jira] Created: (CXF-133) Support sending HTTP GET using JAX-WS di=
spatch

Support sending HTTP GET using JAX-WS dispatch
----------------------------------------------

                 Key: CXF-133
                 URL: http://issues.apache.org/jira/browse/CXF-133
             Project: CeltiXfire
          Issue Type: Sub-task
            Reporter: Jervis Liu


Support sending HTTP GET using JAX-WS dispatch: A HTTP GET request can be s=
ent by using URL.openStream or by using JAX-WS dispatch. Though I do not se=
e much benefit of using the latter, we do need to support it. According to =
JAX-WS spec, this can be done by adding extra non-standard properties into =
request context. A code snippet may look like below:
=20
        Service service =3D Service.createService();
        service.addPort(portQName, "  <http://cxf.apache.org/bindings/xform=
at> http://cxf.apache.org/bindings/xformat", endpointAddress);
        Dispatch<Source> d =3D service.createDispatch(portQName, Source.cla=
ss, Service.Mode.PAYLOAD);
=20
        Map<String, Object> requestContext =3D d.getRequestContext();=20=20=
=20=20=20=20=20=20
        requestContext.put(Message.HTTP_REQUEST_METHOD, new String("GET"));
        requestContext.put(Message.QUERY_STRING, queryString);
        requestContext.put(Message.PATH_INFO, path);=20=20=20=20=20=20=20=
=20
=20
        Source result =3D d.invoke(null);


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

=20=20=20=20=20=20=20=20


This message has been scanned for viruses by MailControl - (see http://blue=
pages.wsatkins.co.uk/?4318150)


This email and any attached files are confidential and copyright protected.=
 If you are not the addressee, any dissemination of this communication is s=
trictly prohibited. Unless otherwise expressly agreed in writing, nothing s=
tated in this communication shall be legally binding.