Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of jervis.liu@iona.com designates
 65.223.216.181 as permitted sender)
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: CXF Bug 448: Imported XSD Update
Date: Wed, 21 Mar 2007 23:25:16 -0400
Message-ID: <9A4696F35B459043970EE4A85A317390066853@amer-ems1.IONAGLOBAL.COM>
In-Reply-To: <5dc0f8d50703210446n220bccc0v62ca492aa6796ef4@mail.gmail.com>
Thread-Topic: CXF Bug 448: Imported XSD Update
Thread-Index: Acdrrp5JwZhe0JHyQRC1/yqLu93gVgAf+9Fw
From: "Liu, Jervis" <jliu@iona.com>
To: <cxf-dev@incubator.apache.org>

Good catch, Bharath. Actually there are two cases this xsd stuff wont =
work properly. One is when multiple endpoints deployed in Servlet, what =
you have suggested sounds a good fix, shall work. Another case is when =
endpoint is published under standalone mood, we don't have any support =
for xsd access yet in this case, a fix might look similar to =
org.apache.cxf.transport.http.WSDLQueryHandler.  I have filed JIRA =
http://issues.apache.org/jira/browse/CXF-482 and =
http://issues.apache.org/jira/browse/CXF-483 to track these issues. Also =
please feel free to submit a patch if you are interested in contributing =
more :-)=20

Cheers,
Jervis

> -----Original Message-----
> From: Bharath Ganesh [mailto:bharathganesh@gmail.com]
> Sent: 2007?3?21? 19:46
> To: cxf-dev@incubator.apache.org
> Subject: CXF Bug 448: Imported XSD Update
>=20
>=20
> Hi
>=20
> Looks like the recently checked-in fix for Bug: CXF 448 wont=20
> work in certain
> cases.
> The wsdllocation is stored in the ServletController while the=20
> endpoint is
> built from the CXFServlet (CXFServlet#buildEndpoint). Assume=20
> I have multiple
> endpoints deployed(which would have different wsdllocations).
> I could have a single WAR app deployed in the web server, and publish
> multiple services to it.
> I could programatically publish an endpoint without going through the
> CXFServlet. In such cases this solution would fail.
> I could think of one probable solution to this issue:
>=20
> 1. Currently, while publishing we store the Server with the=20
> ServerRegistry.
> 2. Later when a request comes for an XSD, we get the=20
> corresponding Endpoint
> from the ServerRegistry. (Using the Endpoint's address field)
> 3. Add a method to Endpoint API to get the wsdlLocation from Endpoint.
>=20
> Thus we can get hold of the user supplied wsdl location,=20
> later resolve the
> xsd location relative to it.
> Please tell me if there is a better solution.
>=20
> Thanks
> Bharath
>=20