Thank you for your interest.
when I went over my app., something looked suspicious.
I had added an extra context file for pooled postgresql connection
like this:
?xml version=1.0 encoding=UTF-8?
Context path=/usr/local/workspace1/pro1 docBase=pro1
crossContext=true reloadable=true
On 26.2.2011 18:50, ahmet temiz wrote:
?xml version=1.0 encoding=UTF-8?
Context path=/usr/local/workspace1/pro1 docBase=pro1
crossContext=true reloadable=true debug=1
Resource name=jdbc/bzk2 auth=Container type=javax.sql.DataSource
On 26.2.2011 22:29, Ognjen Blagojevic wrote:
3. Remove the reloadable attribute. Docs: This feature is very useful
during application development, but it requires significant runtime
overhead and is not recommended for use on deployed production
applications. That's why the default setting for
hello
Are there anythings I have to do in configuration files to
change from development stages to production stage ?
Especially, what are things to deploy jsf_webapp
in its real host after developing it in the localhost ?
kind regards
--
Ahmet Temiz
Jeoloji Müh.
Afet ve Acil Durum
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ahmet,
On 2/25/2011 1:37 PM, ahmet temiz wrote:
Are there anythings I have to do in configuration files to
change from development stages to production stage ?
Unless you've done foolish things in development, production
configuration should not
Especially, what are things to deploy jsf_webapp
in its real host after developing it in the localhost ?
You will also have to make sure that your URLs are built properly. If
the string localhost appears anywhere in your webapp,
you're probbaly
doing something wrong. Also, if you're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it mat concern,
On 2/25/2011 2:57 PM, spr...@gmx.eu wrote:
Especially, what are things to deploy jsf_webapp
in its real host after developing it in the localhost ?
You will also have to make sure that your URLs are built properly. If
