Did you check that you don't have any dependencies which override tapestry dependencies? i had several time problems with woodstox and javassist when there where wrong (mostly older) versions resolved (versions differing from tapestry's (transitive) dependencies). the maven tree dependencies view in the eclipse m2eclipse plugin always helped me to solve the problems - i excluded the dependencies from other artifacts.

felix

zack1403 schrieb:
Hey guys this has actually become a big issue as it is breaking a substantial
part of our app.  There is not a single line of my code in the trace.  Ive
tried upgrading to the most recent snapshot with the same results.  It
really looks like its a problem with woodstox.  Can anyone help me out?

Zack


zack1403 wrote:
I am actually able to reproduce one situation where it shows up.  If I
modify the source of ViewEmail.tml the exception shows up.  A restart
promptly fixes it.  This is just one instance, as it will show up from
time to time on production which is not being modified.
I'm not sure it is an issue with the file system as it is showing up on
multiple machines and containers.  The example described above is using
the jetty:run goal and my production machine is using Tomcat.  Is it
possible Stax is trying to something funky and causing that exception?

Zack




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to