Hello all, I have a couple of Java 101 questions on how xsi:schemaLocations below are resolved. (Yeah, I know Google is my friend[1], but he doesn't seem to know much here.)
1.) The URLs given in the schema location (at the bottom below) appear resolvable even if my network connection is turned off, obviously of course that means it can find those files in a location other than on the Web--but where is that location? Where, for example, is "http://cxf.apache.org/jaxws"; located in the CXF JARs? 2.) Should there be a 1-to-1 mapping between namespaces being used and schemas being given in the xsi:schemaLocation value? For example, could a namespace xmlns:cxf="http://cxf.apache.org/foo"; end up needing two or more entries in the xsi:schemaLocation value--or would it normally just be one? Thanks, Glen [1] http://www.w3.org/TR/xmlschema-1/#schema-loc dkulp wrote: > > > You need to add a schema for jaxws URL into the schemaLocation attribute. > > That said, I also think you probably also want: > <jaxws:client > name="{http://www.example.org/doubleit}DoubleItPort"; > createdFromAPI="true"> ....... > > I've attached the client xml config for the MS WF interop plugfest stuff > (http://mssoapinterop.org/ilab/) for WS-Security 1.1 to use as an example. > > .... > > <?xml version="1.0" encoding="UTF-8"?> > <!-- --> > <!-- Copyright (c) 1993-2007 IONA Technologies PLC. --> > <!-- All Rights Reserved. --> > <!-- --> > <beans xmlns="http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:http="http://cxf.apache.org/transports/http/configuration"; > xmlns:jaxws="http://cxf.apache.org/jaxws"; > xmlns:cxf="http://cxf.apache.org/core"; > xmlns:p="http://cxf.apache.org/policy"; > xmlns:sec="http://cxf.apache.org/configuration/security"; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://cxf.apache.org/jaxws > http://cxf.apache.org/schemas/jaxws.xsd > http://cxf.apache.org/transports/http/configuration > http://cxf.apache.org/schemas/configuration/http-conf.xsd > http://cxf.apache.org/configuration/security > http://cxf.apache.org/schemas/configuration/security.xsd > http://cxf.apache.org/core > http://cxf.apache.org/schemas/core.xsd > http://cxf.apache.org/policy > http://cxf.apache.org/schemas/policy.xsd"; >> > -- View this message in context: http://www.nabble.com/%22The-matching-wildcard-is-strict-but-no-declaration-can-be-found%22-error-tp20353811p20711281.html Sent from the cxf-user mailing list archive at Nabble.com.
