[offtopic] Container dependant war or not ?

[Vjeran Marcinko <vj...@tis.hr>]

Hi folks.

This is not related to Tapestry, but since most of you here are experienced
with web apps, I just wanted to ask do you prefer developing web app with
some functionality tied with container (datasources, security ...), or the
one contained entirely inside .war thus easier for deployment ?
I'm asking this since I'm wondering is it for example better choice to
develop custom login/authorization system using web framework such as
Tapestry, or just to apply J2EE security, then needing to set
tomcat-users.xml on each Tomcat I'm deploying it ?

Regards,
Vjeran


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: [offtopic] Container dependant war or not ?

[Marcus Brito <mb...@gmail.com>]

Usually I take advantage of all features the container offers to me,
specially the ones that are common across containers, like datasource
and security. Keep in mind, however, that using J2EE security with
Tapestry is tricky -- search the mailing list archives on that
subject.

-- Marcus Brito

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: [offtopic] Container dependant war or not ?

[phillip rhodes <rh...@yahoo.com>]

It is absolutely better that you do not put anything
"sticky" into the war file that required the war to
only be good for production (because of database
passwords), configuration settings.

Define the things that change at the application
server level, e.g. connection pools, URL's etc.

This way, the same "war" file can be used across test,
qa, and production and you limit the impact of
potential changes in your migrations.




--- Vjeran Marcinko <vj...@tis.hr> wrote:

> Hi folks.
> 
> This is not related to Tapestry, but since most of
> you here are experienced
> with web apps, I just wanted to ask do you prefer
> developing web app with
> some functionality tied with container (datasources,
> security ...), or the
> one contained entirely inside .war thus easier for
> deployment ?
> I'm asking this since I'm wondering is it for
> example better choice to
> develop custom login/authorization system using web
> framework such as
> Tapestry, or just to apply J2EE security, then
> needing to set
> tomcat-users.xml on each Tomcat I'm deploying it ?
> 
> Regards,
> Vjeran
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org