You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Scott Anderson <sa...@ttm.com> on 2001/03/29 17:59:20 UTC
Schema DTDs not kept locally to application.
I noticed a problem with the build-project.sh init process for peer
applications.
The database schema DTD is kept at
http://java.apache.org/turbine/dtd/database.dtd, and since we have an
authenticating firewall here the init process died a thousand nasty
deaths.
Fortunately, our firewall caches browser authentications. After an
authentication, all traffic from the machine is considered authenticated
until the authentication expires again. I went out and hit a web page in
Mozilla, and afterwards the build script ran fine.
People with firewalls that require auth-basic authentication with every
request, however, will probably not be able to retrieve the DTD via the
build script.
I can think of two possible ways to solve this.
1) Move the DTDs local within the TDK.
2) Change the DTD URL to include user authentication information from a
specified property in the newapp.props file.
Regards,
-scott
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Schema DTDs not kept locally to application.
Posted by Daniel Rall <dl...@collab.net>.
Jason van Zyl <jv...@apache.org> writes:
> Scott Anderson wrote:
> >
> > I noticed a problem with the build-project.sh init process for peer
> > applications.
>
> The DTDs are in the turbine jar. If you are using the linux
> JVM then there is a problem and it always tries to get it
> over the network. Are you using a linux JVM? We try to
> get the DTD locally first and if that fails we try
> the turbine webserver. We have a DTDResolver in the torque
> package that does this, you can take a crack at fixing
> it if you know how.
Is the issue that the Sun JDK 1.3 fails to load the DTD from the JAR
when it also can't retrieve it from apache.org?
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Schema DTDs not kept locally to application.
Posted by Jason van Zyl <jv...@apache.org>.
Scott Anderson wrote:
>
> I noticed a problem with the build-project.sh init process for peer
> applications.
The DTDs are in the turbine jar. If you are using the linux
JVM then there is a problem and it always tries to get it
over the network. Are you using a linux JVM? We try to
get the DTD locally first and if that fails we try
the turbine webserver. We have a DTDResolver in the torque
package that does this, you can take a crack at fixing
it if you know how.
>
> The database schema DTD is kept at
> http://java.apache.org/turbine/dtd/database.dtd, and since we have an
> authenticating firewall here the init process died a thousand nasty
> deaths.
>
> Fortunately, our firewall caches browser authentications. After an
> authentication, all traffic from the machine is considered authenticated
> until the authentication expires again. I went out and hit a web page in
> Mozilla, and afterwards the build script ran fine.
>
> People with firewalls that require auth-basic authentication with every
> request, however, will probably not be able to retrieve the DTD via the
> build script.
>
> I can think of two possible ways to solve this.
>
> 1) Move the DTDs local within the TDK.
> 2) Change the DTD URL to include user authentication information from a
> specified property in the newapp.props file.
>
> Regards,
>
> -scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
--
jvz.
Jason van Zyl
jvanzyl@apache.org
http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://tambora.zenplex.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org