You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Brandon Rife <br...@dejazzd.com> on 2001/01/18 21:29:15 UTC
SOAP application development and Internet Paranoia
After many failed attempts of trying to deploy Apache SOAP on a
behind-the-firewall development server we finally figured out that the SOAP
servlet, or something on which it depends, needs access to the Internet
before it will load, presumably, for namespace resolution. Hopefully
someone can confirm or deny this presumption.
Assuming that SOAP's dependence on Internet access is namespace related and
that we would prefer to develop a SOAP application behind closed doors, what
would be the best way for us to proceed? If modifying the source for a
development version of Apache SOAP is the only answer, a broad
characterization how difficult a job that would be would be appreciated.
Thanks,
Brandon Rife
Software Engineer
Spectra
brandon_rife@spectramarketing.com <ma...@spectramarketing.com>
Re: SOAP application development and Internet Paranoia
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Those are URIs, not URLs. Nothing in the SOAP code accesses anything
on the net at startup and it works fine behind a firewall or offline.
Sanjiva.
----- Original Message -----
From: "Rick Kitts" <ri...@digitalthink.com>
To: <so...@xml.apache.org>
Sent: Thursday, January 18, 2001 4:58 PM
Subject: Re: SOAP application development and Internet Paranoia
> Take a look at org/apache/soap/Constants.java. There are a bunch of
> URLs. Download the schemas they represent, modify Constants to
> point to an internal URL and you should be on your way. However
> there may be things deeper in the code which also require access.
>
> Try doing a
>
> find . -name \*.java -print -exec egrep -i http {} \;
>
> and see what you find.
>
> I would love to learn what you've done or be willing to work
> on doing the changes with you if that's what it takes.
>
> ---Rick
>
> Brandon Rife wrote:
>
> > After many failed attempts of trying to deploy Apache SOAP on a
> > behind-the-firewall development server we finally figured out that the
> > SOAP servlet, or something on which it depends, needs access to the
> > Internet before it will load, presumably, for namespace resolution.
> > Hopefully someone can confirm or deny this presumption.
> >
> > Assuming that SOAP's dependence on Internet access is namespace related
> > and that we would prefer to develop a SOAP application behind closed
> > doors, what would be the best way for us to proceed? If modifying the
> > source for a development version of Apache SOAP is the only answer, a
> > broad characterization how difficult a job that would be would be
> > appreciated.
> >
> > Thanks,
> > Brandon Rife
> > Software Engineer
> > Spectra
> > brandon_rife@spectramarketing.com
> > <ma...@spectramarketing.com>
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> > ATT255243.txt
> >
> > Content-Type:
> >
> > text/plain
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
Re: SOAP application development and Internet Paranoia
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Those are URIs, not URLs. Nothing in the SOAP code accesses anything
on the net at startup and it works fine behind a firewall or offline.
Sanjiva.
----- Original Message -----
From: "Rick Kitts" <ri...@digitalthink.com>
To: <so...@xml.apache.org>
Sent: Thursday, January 18, 2001 4:58 PM
Subject: Re: SOAP application development and Internet Paranoia
> Take a look at org/apache/soap/Constants.java. There are a bunch of
> URLs. Download the schemas they represent, modify Constants to
> point to an internal URL and you should be on your way. However
> there may be things deeper in the code which also require access.
>
> Try doing a
>
> find . -name \*.java -print -exec egrep -i http {} \;
>
> and see what you find.
>
> I would love to learn what you've done or be willing to work
> on doing the changes with you if that's what it takes.
>
> ---Rick
>
> Brandon Rife wrote:
>
> > After many failed attempts of trying to deploy Apache SOAP on a
> > behind-the-firewall development server we finally figured out that the
> > SOAP servlet, or something on which it depends, needs access to the
> > Internet before it will load, presumably, for namespace resolution.
> > Hopefully someone can confirm or deny this presumption.
> >
> > Assuming that SOAP's dependence on Internet access is namespace related
> > and that we would prefer to develop a SOAP application behind closed
> > doors, what would be the best way for us to proceed? If modifying the
> > source for a development version of Apache SOAP is the only answer, a
> > broad characterization how difficult a job that would be would be
> > appreciated.
> >
> > Thanks,
> > Brandon Rife
> > Software Engineer
> > Spectra
> > brandon_rife@spectramarketing.com
> > <ma...@spectramarketing.com>
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> > ATT255243.txt
> >
> > Content-Type:
> >
> > text/plain
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
Re: SOAP application development and Internet Paranoia
Posted by Rick Kitts <ri...@digitalthink.com>.
Take a look at org/apache/soap/Constants.java. There are a bunch of
URLs. Download the schemas they represent, modify Constants to
point to an internal URL and you should be on your way. However
there may be things deeper in the code which also require access.
Try doing a
find . -name \*.java -print -exec egrep -i http {} \;
and see what you find.
I would love to learn what you've done or be willing to work
on doing the changes with you if that's what it takes.
---Rick
Brandon Rife wrote:
> After many failed attempts of trying to deploy Apache SOAP on a
> behind-the-firewall development server we finally figured out that the
> SOAP servlet, or something on which it depends, needs access to the
> Internet before it will load, presumably, for namespace resolution.
> Hopefully someone can confirm or deny this presumption.
>
> Assuming that SOAP's dependence on Internet access is namespace related
> and that we would prefer to develop a SOAP application behind closed
> doors, what would be the best way for us to proceed? If modifying the
> source for a development version of Apache SOAP is the only answer, a
> broad characterization how difficult a job that would be would be
> appreciated.
>
> Thanks,
> Brandon Rife
> Software Engineer
> Spectra
> brandon_rife@spectramarketing.com
> <ma...@spectramarketing.com>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
> ATT255243.txt
>
> Content-Type:
>
> text/plain
>
>
Re: SOAP application development and Internet Paranoia
Posted by Rick Kitts <ri...@digitalthink.com>.
Take a look at org/apache/soap/Constants.java. There are a bunch of
URLs. Download the schemas they represent, modify Constants to
point to an internal URL and you should be on your way. However
there may be things deeper in the code which also require access.
Try doing a
find . -name \*.java -print -exec egrep -i http {} \;
and see what you find.
I would love to learn what you've done or be willing to work
on doing the changes with you if that's what it takes.
---Rick
Brandon Rife wrote:
> After many failed attempts of trying to deploy Apache SOAP on a
> behind-the-firewall development server we finally figured out that the
> SOAP servlet, or something on which it depends, needs access to the
> Internet before it will load, presumably, for namespace resolution.
> Hopefully someone can confirm or deny this presumption.
>
> Assuming that SOAP's dependence on Internet access is namespace related
> and that we would prefer to develop a SOAP application behind closed
> doors, what would be the best way for us to proceed? If modifying the
> source for a development version of Apache SOAP is the only answer, a
> broad characterization how difficult a job that would be would be
> appreciated.
>
> Thanks,
> Brandon Rife
> Software Engineer
> Spectra
> brandon_rife@spectramarketing.com
> <ma...@spectramarketing.com>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
> ATT255243.txt
>
> Content-Type:
>
> text/plain
>
>