Help me please

["Vu, Thai" <Th...@parsons.com>]

I don't know what's wrong with my application. I use tiles and whenever
I put <html:form> in a piece of the tiles, the whole piece isn't
processed. Do you think of any problem?

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

Re: Help me please

[Wendy Smoak <ws...@gmail.com>]

On 11/9/05, Vu, Thai <Th...@parsons.com> wrote:
> I don't know what's wrong with my application. I use tiles and whenever
> I put <html:form> in a piece of the tiles, the whole piece isn't
> processed. Do you think of any problem?

Seeing an example of your code would help.  Are you trying to have the
<html:form> in one tile and form elements in another?

--
Wendy

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

Re: strange behaviours of tiles

[Thomas Corte <Th...@knipp.de>]

Hi,

Thomas Corte schrieb:

> I know that this thread is quite old, but I still wonder whether there 
> is a better solution for this. It's quite tedious to find errors in JSPs 
> when the Tiles framework swallows exceptions completely. Is there a 
> patch available that keeps Tiles from doing this?

Nevermind... I found out that a line like

   log4j.logger.org.apache.struts.taglib.tiles=ERROR, A1

in the log4j.properties of the web app at least ensures that any 
exception is properly written to the Tomcat log, which is enough to 
carry one from there.

-- 
Thomas

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

Re: strange behaviours of tiles

[Thomas Corte <Th...@knipp.de>]

Hi,

Laurie Harper wrote:

> Tiles can sometimes 'swallow' errors rendering a JSP without logging 
> them, returning empty pages. Double check your logs first to see if the 
> problem *is* being logged, but if not a couple of approaches you can try 
> to track down the problem:
> 
>  - try loading your JSPs directly if you can (i.e. without going through 
> Tiles). That may not be trivial if your JSPs need data prepopulated by 
> Struts actions though.
> 
>  - try wrapping the content of each JSP with a try / catch (using the 
> JSTL tags or runtime scriptlets) and log any exceptions; this can help 
> you see them before they get swallowed by the Struts/Tiles request 
> processing machinery
> 
>  - try stepping through your JSPs in a debugger. It *really* helps if 
> you have an IDE that supports this well, since just stepping through the 
> Java code generated from the JSP isn't very helpful

I know that this thread is quite old, but I still wonder whether there 
is a better solution for this. It's quite tedious to find errors in JSPs 
when the Tiles framework swallows exceptions completely. Is there a 
patch available that keeps Tiles from doing this?

Regards,

-- 
Thomas

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

Re: strange behaviours of tiles

[Laurie Harper <la...@holoweb.net>]

eve wrote:
> has it ever happened to you that a little apparently insignificant 
> change in the jsp caused tiles not to work and all pages composed with 
> tiles to appear completely blank?
> I really can't find the cause!

Tiles can sometimes 'swallow' errors rendering a JSP without logging 
them, returning empty pages. Double check your logs first to see if the 
problem *is* being logged, but if not a couple of approaches you can try 
to track down the problem:

  - try loading your JSPs directly if you can (i.e. without going 
through Tiles). That may not be trivial if your JSPs need data 
prepopulated by Struts actions though.

  - try wrapping the content of each JSP with a try / catch (using the 
JSTL tags or runtime scriptlets) and log any exceptions; this can help 
you see them before they get swallowed by the Struts/Tiles request 
processing machinery

  - try stepping through your JSPs in a debugger. It *really* helps if 
you have an IDE that supports this well, since just stepping through the 
Java code generated from the JSP isn't very helpful

Good luck!

L.


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

strange behaviours of tiles

[eve <nu...@email.it>]

has it ever happened to you that a little apparently insignificant 
change in the jsp caused tiles not to work and all pages composed 
with tiles to appear completely blank?
I really can't find the cause!