Hurra, i solved the problem in a very elegant way, pardon me being blatant...
As i was in a hurry to begin tests, i simply copyed my original xml so
the second access will point to it.
<xsl:variable name="xmldoc" select="document('doc2.xml')"/>
But that will cause maintenance troubles, cause the original xml can
be modified without notice, and i'll have to check it everitime and so
on...
So now i got the time to do a little thinking and thought maybe the
transformiix guys tought their way was a optimization, thinking if one
wants to access the doc with a given url, that doc should be only
loaded once, and if it's transformed in the mean time so be it.
So i've tryed accessing the same document but thru a diferent uri, like
<xsl:variable name="xmldoc" select="document('doc.xml?mode=replace')"/>
where ?mode=replace is just bogus data and... it works!!!
How about that !!!
On 9/2/05, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
So you're saying the IE behaviour is the behaviour expected from a
conformant processor, and that this is not open to implementation,
right?
You haven't given me enough information to be 100% certain, but as I said,
from the information given it looks like an FF non-conformance.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--