2012/8/25 Mark Thomas :
> On 24/08/2012 20:53, Josh Gooding wrote:
>> Yeah you see what I'm given to work with. The sever.xml will be cleaned
>> up, but i'm trying to get this fixed to upgrade to 6.0.35 or 7.
>>
>> So let me ask this, given that billing-1.0.4 is a branch that contains 4
>> war fil
Mark, Konstantin, thank you very much. As usual I highly appreciate it.
On Fri, Aug 24, 2012 at 4:05 PM, Mark Thomas wrote:
> On 24/08/2012 20:53, Josh Gooding wrote:
> > Yeah you see what I'm given to work with. The sever.xml will be cleaned
> > up, but i'm trying to get this fixed to upgrad
On 24/08/2012 20:53, Josh Gooding wrote:
> Yeah you see what I'm given to work with. The sever.xml will be cleaned
> up, but i'm trying to get this fixed to upgrade to 6.0.35 or 7.
>
> So let me ask this, given that billing-1.0.4 is a branch that contains 4
> war files. Am I able to deploy say b
Yeah you see what I'm given to work with. The sever.xml will be cleaned
up, but i'm trying to get this fixed to upgrade to 6.0.35 or 7.
So let me ask this, given that billing-1.0.4 is a branch that contains 4
war files. Am I able to deploy say billing-1.0.5 on the fly without having
to restart t
2012/8/24 Josh Gooding :
>
>
>
All those debug="" attributes... - Tomcat 5.5 does not support them.
See "Configuration Reference" chapters of documentation, where these
attributes are not mentioned. (Well, nothing fatal - they will be just
silently ignored).
>
> value="
Wow, has it really been that long since I've asked questions here? On to
the meat and potatoes...
I have a tomcat 5.5.23 installation here that I am trying to do some
changes too and I am a bit lost.. Let me try to explain what I want to
do. The application has both a context defined in the ser
