Hello,

 

I posted this question some time ago on the user list but never got a reply back so I’m trying here this time.

 

Could someone please help me with this problem I am having another open-source project depends on it (AndroMDA), it could be that I am missing something very obvious but for now I need to patch the code myself to get the export functionality working in a Struts/Tiles tag <tiles:insert…>

 

Thanks for letting me know

 

-- Wouter

 

 

http://team.andromda.org/docs/andromda-bpm4struts-cartridge/index.html

 

 

-----Original Message-----
From:
Wouter Zoons
Sent:
Sunday, July 04, 2004 9:59 PM
To: '
[EMAIL PROTECTED]'
Subject: tiles and export

 

<quote>
 I am able to export my list from a jsp page when i am not using tiles
 in my Struts application
</quote>

 

 

I am experiencing the same problem when using Tiles, I am just getting an “IOException while writing data”, and I know how to solve it.

 

The reason we don’t see the cause is because the original exception is being swallowed here:

http://displaytag.sourceforge.net/xref/org/displaytag/tags/TableTag.html#1101

 

notice how the ioexception is not added to the jspexception as the ‘cause’, I fixed it by changing the line into this one:

throw new JspException("IOException while writing data.", e);

 

when you do that and rebuild the binary you will see a more interesting message: “cannot flush within a custom tag”

 

it means that .flush() is called within a custom tag, in this case <tiles:*>

 

so I patched the sources again, this time removing this line:

http://displaytag.sourceforge.net/xref/org/displaytag/tags/TableTag.html#1097

 

and now it works fine.

 

Can someone from the developer team refactor this flush behavior and expose it as a boolean table attribute ? and while you’re at it, also pass the cause to the exception (or are you perhaps targetting jdk1.2 too ?)

 

This fix is critical to me because the AndroMDA bpm4struts-cartridge is not working properly otherwise (it uses displaytag)

http://team.andromda.org/docs

 

can someone let me know if this will be fixed in the next milestone ? otherwise I will have to keep using my home-made patched version L

 

Thanks in advance, and keep up the very good work!!

 

--

 

Reply via email to