Michael Horwitz wrote:
The other approach we are toying with is bundling all the
configuration into the war upfront, and getting the application to
intelligently detect its environment and configure itself
accordingly.
But if you have sticklers in QA (as you describe), I don't see how they
cou
That's an interesting constraint I hadn't thought about. One could follow
the same approach as I describe but instead of rebundling the generated
config settings into the war, they can be generated into a "config"
directory and the startup script can add the config directory to the web
containers
100% agreed! Unfortunately I, like many other I know, work in an environment
where we are strictly forbidden from making any modifications to the binary
after we release to test. The application still has to go to QA, staging and
production environments post test, and a war file is seen by the dep
I know that this is approach suggested by some but I really don't like the
JNDI configuration piece. I prefer having and maintaining all the settings
of my app in just one place.
Here's the approach I use :
http://jroller.com/page/sjivan?entry=spring_updating_settings_of_a
Sanjiv
On 12/8/06, Mi
And you can always add this to your build.xml
and then just call
ant deploy-live
Gilberto C Andrade wrote:
I think you don't need all this!
Just ask your ISP the hostname and build your war:
ant war -Ddatabase.host=localhost:5433 -Dhttp.port=80
-Ddatabase.n
I think you don't need all this!
Just ask your ISP the hostname and build your war:
ant war -Ddatabase.host=localhost:5433 -Dhttp.port=80
-Ddatabase.name=bcoproducao
Gilberto
> Thanks again. I feel kind of stupid. I do use Tomcat and am familiar with
> the doc link you sent. I think I should b
acate,
When you do your build for the deployment server, then something like
"ant -Ddb.host=dbhostname ..."
should work
Mark
acate wrote:
Please re-read my question. The server names will not be the same.
Fadi Samara wrote:
well it depends where your database is located. It is on the
Thanks again. I feel kind of stupid. I do use Tomcat and am familiar with
the doc link you sent. I think I should be more specific. I will be
developing on my work PC using Tomcat 5.x. I will be deploying to a GoDaddy
hosted account, and am not sure what j2ee container they use. So, I am
thi
Not sure which servlet container you use, but as an example take a look at
this howto for Tomcat:
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html
On 12/8/06, acate <[EMAIL PROTECTED]> wrote:
Thank you very much for this information!!! Could you recommend some
onl
Thank you very much for this information!!! Could you recommend some online
documentation might show me an example of how to do this?
Michael Horwitz wrote:
>
> The usual approach is to configure resources such as databases as part of
> the servlet container, and then reference these via JNDI.
The usual approach is to configure resources such as databases as part of
the servlet container, and then reference these via JNDI. It requires a
small change to the applicationContext-resources.xml file to point to the
correct JNDI name, and then some servlet container specific configuration to
s
Please re-read my question. The server names will not be the same.
Fadi Samara wrote:
>
> well it depends where your database is located. It is on the same machine
> you are deploying to, you should be fine with *localost*
>
> On 12/8/06, acate <[EMAIL PROTECTED]> wrote:
>>
>>
>> I am new to
well it depends where your database is located. It is on the same machine
you are deploying to, you should be fine with *localost*
On 12/8/06, acate <[EMAIL PROTECTED]> wrote:
I am new to AppFuse and Spring, but need to build an app that has a mysql
connection. I can build the app locally an
I am new to AppFuse and Spring, but need to build an app that has a mysql
connection. I can build the app locally and use "localhost" as part of the
mysql connection parameters. However, when I deliver the app to the
designated server the host name "localhost" will be different. What is the
app
14 matches
Mail list logo
