tiles-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aditya Saraf <adi.sa...@gmail.com>
Subject Re: NullPointerException insertDefinition.startTag
Date Thu, 11 Aug 2011 14:33:17 GMT

I was not using the <tiles:setCurrentContainer> tag, because all calls to
the definitions are within the same application context. However, I did put
the <tiles:setCurrentContainer> tag in the problematic file above the
<tiles:insertDefinition> tag and I got a different error.

org.apache.tiles.impl.NoSuchContainerException: The container with the key
'null' cannot be found
Why is the container key defaulting to be null? From documentation it says
that if the containerKey attribute is not specified then the default
containerKey is assumed.

Adi Saraf

On Thu, Aug 11, 2011 at 10:20 AM, Antonio Petrelli <
antonio.petrelli@gmail.com> wrote:

> 2011/8/11 Aditya Saraf <adi.saraf@gmail.com>
> > Thanks for your prompt response. There are no indications in my Tomcat
> > statup log. My logging properties are set to show only INFO, WARN and,
> > SEVERE. What should the container reference point to? maybe my file
> > structure is incorrect? Please let me know.
> >
> There's a thing that I did not understand. Are the calls to definitions
> (the
> working one and the problematic one) in the same application, or different
> applications?
> I try to explain.
> If they are in the same one, then the reason why the container is null is
> because it is done explicitly by using <tiles:setCurrentContainer> tag in
> JSP.
> If they are in different ones, then probably it is a startup problem.
> Antonio

Adi Saraf

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message