You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Thomas Manson <de...@gmail.com> on 2009/09/02 16:58:04 UTC

Running CXF on a server that don't have an internet connection

Hi,

 I need to run some webservices over JMS in a company. Those webservices are
private to the company and for security reasons, the server that run the
webservices doesn't have an internet connection, which lead to an error like
this :

Line 230 in XML document from class path resource [applicationContext.xml]
is invalid; nested exception is org.xml.sax.SAXParseException: src-resolve:
Cannot resolve the name 'wsdl:tExtensibilityElement' to a(n) 'type
definition' component.

(I'm in a spring application, spring 2.5.6, jdk 1.5)

 I've read here

http://mail-archives.apache.org/mod_mbox/cxf-users/200711.mbox/%3C13632952.post@talk.nabble.com%3E

that the internet connection was the cause and that you can deal with this
issue with a catalog file.

Is there an existing catalog file (with xsd) for CXF so that it can run
without an internet connection ?

the catalog file should be placed in the meta-inf dir of any jar in the
classpath ?

I don't know this catalog thing, so if somebody could give me some light on
this, I would appreciate ;)

Regards,
Thomas.

Re: Running CXF on a server that don't have an internet connection

Posted by Thomas Manson <de...@gmail.com>.
Hi Daniel,

  It's the version 2.2.2.

Thomas.


On Thu, Sep 3, 2009 at 23:06, Daniel Kulp <dk...@apache.org> wrote:

>
>
> Hmm... What version of CXF?   We already have that line in our
> spring.schemas
> file:
> ./api/target/schemas/META-INF/spring.schemas:
>
> http\://schemas.xmlsoap.org/wsdl/2003-02-11.xsd=schemas/wsdl/wsdl.xsd
>
> and that wsdl.xsd in our jar.    Not sure why it wouldn't have been picked
> up.
>
> Dan
>
>
> On Thu September 3 2009 12:10:14 pm Thomas Manson wrote:
> > We find a solution :
> >
> > Add a META-INF directory in the classpath :
> >
> >   META-INF/
> > META-INF/spring.schemas
> > META-INF/xsd
> > META-INF/xsd/2003-02-11.xsd
> >   within spring.schemas
> >
> >
> >
> http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd=META-INF/xsd/2003-02-11.xsd
> >  and http\://schemas.xmlsoap.org/wsdl/*2003-02-11.xsd* is the XSD that
> was
> >  needed when parsing the CXF xml.
> >
> > Restart the application and it works.
> >
> > After that we zipped the META-INF dir to offlineXSD.jar and delete the
> > directory. (jar is better, it has a CRC32 that tells the file is not
> > corrupted)
> >
> >
> > Thomas.
> >
> > On Wed, Sep 2, 2009 at 16:58, Thomas Manson
> <de...@gmail.com>wrote:
> > > Hi,
> > >
> > >  I need to run some webservices over JMS in a company. Those
> webservices
> > > are private to the company and for security reasons, the server that
> run
> > > the webservices doesn't have an internet connection, which lead to an
> > > error like this :
> > >
> > > Line 230 in XML document from class path resource
> > > [applicationContext.xml] is invalid; nested exception is
> > > org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name
> > > 'wsdl:tExtensibilityElement' to a(n) 'type definition' component.
> > >
> > > (I'm in a spring application, spring 2.5.6, jdk 1.5)
> > >
> > >  I've read here
> > >
> > >
> > >
> http://mail-archives.apache.org/mod_mbox/cxf-users/200711.mbox/%3C1363295
> > >2.post@talk.nabble.com%3E
> > >
> > > that the internet connection was the cause and that you can deal with
> > > this issue with a catalog file.
> > >
> > > Is there an existing catalog file (with xsd) for CXF so that it can run
> > > without an internet connection ?
> > >
> > > the catalog file should be placed in the meta-inf dir of any jar in the
> > > classpath ?
> > >
> > > I don't know this catalog thing, so if somebody could give me some
> light
> > > on this, I would appreciate ;)
> > >
> > > Regards,
> > > Thomas.
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Re: Running CXF on a server that don't have an internet connection

Posted by Daniel Kulp <dk...@apache.org>.

Hmm... What version of CXF?   We already have that line in our spring.schemas 
file:
./api/target/schemas/META-INF/spring.schemas:

http\://schemas.xmlsoap.org/wsdl/2003-02-11.xsd=schemas/wsdl/wsdl.xsd

and that wsdl.xsd in our jar.    Not sure why it wouldn't have been picked up.

Dan


On Thu September 3 2009 12:10:14 pm Thomas Manson wrote:
> We find a solution :
> 
> Add a META-INF directory in the classpath :
> 
>   META-INF/
> META-INF/spring.schemas
> META-INF/xsd
> META-INF/xsd/2003-02-11.xsd
>   within spring.schemas
> 
>  
>  http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd=META-INF/xsd/2003-02-11.xsd
>  and http\://schemas.xmlsoap.org/wsdl/*2003-02-11.xsd* is the XSD that was
>  needed when parsing the CXF xml.
> 
> Restart the application and it works.
> 
> After that we zipped the META-INF dir to offlineXSD.jar and delete the
> directory. (jar is better, it has a CRC32 that tells the file is not
> corrupted)
> 
> 
> Thomas.
> 
> On Wed, Sep 2, 2009 at 16:58, Thomas Manson 
<de...@gmail.com>wrote:
> > Hi,
> >
> >  I need to run some webservices over JMS in a company. Those webservices
> > are private to the company and for security reasons, the server that run
> > the webservices doesn't have an internet connection, which lead to an
> > error like this :
> >
> > Line 230 in XML document from class path resource
> > [applicationContext.xml] is invalid; nested exception is
> > org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name
> > 'wsdl:tExtensibilityElement' to a(n) 'type definition' component.
> >
> > (I'm in a spring application, spring 2.5.6, jdk 1.5)
> >
> >  I've read here
> >
> >
> > http://mail-archives.apache.org/mod_mbox/cxf-users/200711.mbox/%3C1363295
> >2.post@talk.nabble.com%3E
> >
> > that the internet connection was the cause and that you can deal with
> > this issue with a catalog file.
> >
> > Is there an existing catalog file (with xsd) for CXF so that it can run
> > without an internet connection ?
> >
> > the catalog file should be placed in the meta-inf dir of any jar in the
> > classpath ?
> >
> > I don't know this catalog thing, so if somebody could give me some light
> > on this, I would appreciate ;)
> >
> > Regards,
> > Thomas.
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: Running CXF on a server that don't have an internet connection

Posted by Thomas Manson <de...@gmail.com>.
We find a solution :

Add a META-INF directory in the classpath :

  META-INF/
META-INF/spring.schemas
META-INF/xsd
META-INF/xsd/2003-02-11.xsd
  within spring.schemas

  http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd=META-INF/xsd/2003-02-11.xsd
  and http\://schemas.xmlsoap.org/wsdl/*2003-02-11.xsd* is the XSD that was
needed when parsing the CXF xml.

Restart the application and it works.

After that we zipped the META-INF dir to offlineXSD.jar and delete the
directory. (jar is better, it has a CRC32 that tells the file is not
corrupted)


Thomas.

On Wed, Sep 2, 2009 at 16:58, Thomas Manson <de...@gmail.com>wrote:

> Hi,
>
>  I need to run some webservices over JMS in a company. Those webservices
> are private to the company and for security reasons, the server that run the
> webservices doesn't have an internet connection, which lead to an error like
> this :
>
> Line 230 in XML document from class path resource [applicationContext.xml]
> is invalid; nested exception is org.xml.sax.SAXParseException: src-resolve:
> Cannot resolve the name 'wsdl:tExtensibilityElement' to a(n) 'type
> definition' component.
>
> (I'm in a spring application, spring 2.5.6, jdk 1.5)
>
>  I've read here
>
>
> http://mail-archives.apache.org/mod_mbox/cxf-users/200711.mbox/%3C13632952.post@talk.nabble.com%3E
>
> that the internet connection was the cause and that you can deal with this
> issue with a catalog file.
>
> Is there an existing catalog file (with xsd) for CXF so that it can run
> without an internet connection ?
>
> the catalog file should be placed in the meta-inf dir of any jar in the
> classpath ?
>
> I don't know this catalog thing, so if somebody could give me some light on
> this, I would appreciate ;)
>
> Regards,
> Thomas.
>