Konstantin,
Sorry for the duplicate email to you, but I made one other observation and
wanted to include the message I sent you to the dev list.
Just for grins I modified the I18N sample so that the location was set to "cocoon:/catalogues". I then created a pipeline consisting of:
<map:match pattern="catalogues/*"> <map:generate src="translations/{1}/> <map:serialize type="xml"/> </map:match>
Although this worked just fine I ended up getting a couple of stacktraces in
the error log. I was hoping that if the catalog could come from a pipeline
that I could use that method to merge two files together. Unfortunately,
although it works I can't tolerate the stacktraces in production.
I believe the stack trace occurs because the file couldn't be resolved by
cocoon, probably for messages_en_US.xml and menu_en_US.xml.
loadResourceBundle then calls the DocumentBuilder as a fallback to try to
load the file which causes the stack trace. I'm not really sure why this
second call is necessary, but could the exception be caught and ignored?
Have you tried updating your cvs snapshot? It must be really old now.
Vadim
