|Re: WTP 3.2 and Tomcat 7 - webapp defined context.xml is broken [message #546852 is a reply to message #546720]
||Wed, 14 July 2010 12:50
| Larry Isaacs
Registered: July 2009
On 7/13/2010 6:38 PM, Nic Baker wrote:|
> Larry Isaacs wrote on Tue, 13 July 2010 14:25
>> It appears the startup process has changed in Tomcat 7 such that the
>> <ResourceLink>, when part of a <context> in server.xml, gets processed
>> before the server is sufficiently initialized. If you open the server
>> editor in Eclipse and enable the "Publish module contexts to separate
>> XML files" option, I believe you will avoid this issue. I'll see about
>> force enabling this option for Tomcat 7 servers in WTP 3.2.1.
> Yep, that workaround fixed the problem. Thanks for the quick and helpful
> Out of curiosity, what drawbacks (if any) are there to having the
> "Public module contexts to separate XML files" option checked? Will it
> make the server startup more slowly, or are there other gotchas I should
> be aware of now that I have this option turned on?
It is probably more "normal" to have it enabled for Tomcat 5.5 and 6.0,
and as you have discovered, kind of required for Tomcat 7. It hasn't
been enabled by default mainly because I'm trying to avoid having the
support for the various versions of Tomcat diverge more than necessary.
Now that it's needed by Tomcat 7, it is worth the effort to enable it
by default for appropriate versions. I'll try to get this into WTP 3.2.2.
Powered by FUDForum
. Page generated in 0.02413 seconds