[
https://issues.apache.org/jira/browse/CXF-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-1272.
------------------------------
Resolution: Fixed
Assignee: Daniel Kulp
I've updated all the schemas to use the full location with the .xsd for the
wsdlish things. Thus, this specific use case is fixed. There MAY still be
an issue if other schema types are used in spring config for other schemas that
don't end in .xsd. The RM and WS-A schemas come to mind. However, I don't
think those would normally end up in the spring config right now, although I
could be wrong.. (The ws policy schema DOES have .xsd, so the policies that
WOULD appear are OK) In anycase, if one of those does become an issue, we'll
log a new bug. (or hopefully spring will get fixed and problem solved)
> Application doesn't start up without internet connection (when providing
> <http-conf:conduit> setting)
> -----------------------------------------------------------------------------------------------------
>
> Key: CXF-1272
> URL: https://issues.apache.org/jira/browse/CXF-1272
> Project: CXF
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 2.0.3
> Environment: IBM WebSphere 6.1 Java5
> Also reproduced when building with maven2
> Reporter: Allard Buijze
> Assignee: Daniel Kulp
> Fix For: 2.0.5
>
>
> When the spring context contains the <http-conf:conduit> tag, additional CXF
> xsd files are parsed. Some of these XSD's rely on the WSDL schema definitions
> found online. However, the XSD is also included in the jar
> (schemas/wsdl/wsdl.xsd).
> When the application starts up without an internet connection, it will fail
> because it cannot find the wsdlExtensibiityElement definition.
> I have modified the xsd to load
> [schemaLocation="classpath:schemas/wsdl/wsdl.xsd"]. Now, the application
> starts up fine without internet connection.
> The file I have modified are:
> * /schemas/wsdl/http.xsd
> * /schemas/wsdl/http-conf.xsd
> * /schemas/wsdl/jms.xsd
> * /schemas/wsdl/xml-binding.xsd
> In all these files, I have removed:
> <import namespace = "http://schemas.xmlsoap.org/wsdl/";
> schemaLocation="http://schemas.xmlsoap.org/wsdl/"/>
> and added
> <import namespace = "http://schemas.xmlsoap.org/wsdl/";
> schemaLocation="classpath:/schemas/wsdl/wsdl.xsd"/>
> Perhaps there are other setting requiring external files, but we haven't come
> across any so far.
> ----
> Background info:
> Our web services are running in a highly protected environment. This means
> that all firewalls are closed, except for a few ports that are needed to
> communicate with our service providers. This means that we do not
> automatically have access to all IP's from our servers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
