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 t
On 26.2.2011 18:50, ahmet temiz wrote:
1. Remove the path attribute. Docs: "The value of this field must not be
set except when statically defining a Context in server.xml, as it will
be inferred from the filenames used for either the .xml context file or
the docBase."
2. Remov
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:
Is it likely to be the reason of problem ? especially this expression
url="jdbc:postgresql://127.0.0.1:5432/bzk2" in prod
-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 proper
> > 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, i
-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
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 Yönetimi
