[ 
https://issues.apache.org/jira/browse/CXF-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575839#action_12575839
 ] 

matt hoffman commented on CXF-1272:
-----------------------------------

Same problem here. We developed against CXF and took it all the way up to 
production, where it failed with the error:

src-resolve: Cannot resolve the name 'wsdl:tExtensibilityElement' to a(n) 'type 
definition' component.

Of course, the production server is locked down, so external Internet access is 
restricted.

Note that we're not using the http-conf:conduit tag, but we are using 
http-conf:server and http-conf:destination. Any tag in the http-conf namespace 
should trigger this bug.

The workaround above didn't work for us, using the libraries in the Maven 
repository.


> 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
>             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.

Reply via email to