Thanks Eric, That was a transcription error on my part. File locations are actually encoded correctly.
Have you seen a situation where a page execution just stops before? Would you like me to package up these pages and send them? Peter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erik Bruchez Sent: Thursday, March 18, 2004 6:31 PM To: OXF Users Subject: Re: Odd Behavior IE vs Mozilla I don't know if this is the cause of your problem, but if the URL starts with "oxf:", there should be an initial "/", e.g. the URL should be "oxf:/app/somefile.xsd". -Erik Peter Charles wrote: > Hi, > > Here is the pipeline that causes the behavior described below: > > The document from the session looks like this > <form> > <file>oxf:app/somefile.xsd</file> > <selection>submit</selection> > <form> > > The problem is that this pipe line works fine with some files and not at > all with others. In Mozilla it works with more files than in IE. > > All files work fine when I hard code the file names.(see commented out > code) > > Thank > > Peter > > <?xml version="1.0" encoding="UTF-8"?> > <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline";> > <p:param name="data" type="output" > debug="schemaAdmin:Model:Output"/> > > <p:processor uri="oxf/processor/session-generator"> > <p:input name="config"> > <key>form</key> > </p:input> > <p:output name="data" id="session" > debug="schemaAdminModel:session"/> > </p:processor> > > <p:processor uri="oxf/processor/xslt"> > <p:input name="data" href="#session"/> > <p:input name="config"> > <xsl:stylesheet > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="1.0"> > <xsl:template match="form/file"> > <config> > <url> > > <xsl:apply-templates/> > </url> > > <content-type>text/xml</content-type> > > <validating>false</validating> > </config> > </xsl:template> > <xsl:template match="form/selection"/> > </xsl:stylesheet> > </p:input> > <p:output name="data" id="config" > debug="schemaAdminModel:config"/> > </p:processor> > > <p:processor uri="oxf/processor/url-generator"> > <p:input name="config" href="#config"/> > <p:output name="data" id="xsd" > debug="schemaAdminModel:xsd"/> > </p:processor> > <!-- > <p:processor uri="oxf/processor/session-serializer"> > <p:input name="data" href="#xsd2"/> > </p:processor> > > <p:processor uri="oxf/processor/url-generator"> > <p:input name="config"> > <config> > > <url>oxf:/app/schemaMenu/schema/data-types.xsd</url> > <content-type>text/xml</content-type> > <validating>false</validating> > </config> > </p:input> > <p:output name="data" id="xsd" > debug="schemaAdmin:XSD:Output"/> > </p:processor> > --> > <!-- CREATE XFORM MODEL --> > > <p:processor uri="oxf/processor/xslt"> > <p:input name="data" href="#xsd"/> > <p:input name="config" > href="oxf:/app/schemaAdmin/XFormModelConstruct2.xsl"/> > <p:output name="data" ref="data"/> > </p:processor> > </p:config> > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Peter Charles > Sent: Wednesday, March 17, 2004 5:10 PM > To: [EMAIL PROTECTED] > Subject: Odd Behavior IE vs Mozilla > > Hello, > > I am getting some odd and differing behavior between IE6 and Mozilla 1.4 > > This is the outline of the application. > > The first page grabs a file listing from disk and present this as a list > to the user. This works fine. > > When selecting one of the files, the file name is passed through the > session to another page where the following happens > > The pages xform is an xpl that reads the file name from the session then > reads the file from disk, and uses the xslt process to create an xform > instance > > The pages model takes the file and uses xlst to create appropriate xform > elements and then push these elements to view. > > Two of the files work fine in Mozilla, on the others the app just stalls > after the xform xpl is executed. None of the debugs in the Model xpl > are executed when the app stalls. > > In IE one of the files works, some hang the browser and some give a > 'page can not be displayed error' > > All of these files work fine when loaded directly into the second page > by hard coding the file names. > > Peter > > > > > > -----<CDE/>----- > Center for Document Engineering > University of California, Berkeley > cde.berkeley.edu > > > _______________________________________________ > oxf-users mailing list > [EMAIL PROTECTED] > http://mail.orbeon.com/mailman/listinfo/oxf-users > > _______________________________________________ > oxf-users mailing list > [EMAIL PROTECTED] > http://mail.orbeon.com/mailman/listinfo/oxf-users _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
