migration problems

Hi

I'm migrating an Orbeon 2.8 based application to 3.5 version. I've read the documentation, and made the incompatible changes.

I have two questions:

I cleaned up the OPS sample webapp, I only kept the jars and config files. I also made some changes to the web.xml.

1) I'd like to use the new 'xforms:textarea mediatype="text/html"' element, but id prints an error: 'xforms-element-9 not found'. I must have got rid of something what I shouldn't have. Can anybody give me a hint, what is missing?

2) After fixing all the incompatible changes (like oxf:data in XSLTs), I got the following error stacktrace:

i18n.xsl is a simple XSLT which replaces elements with texts.

2007-03-26 09:55:01,906 http-8080-1 ERROR webapp.ProcessorService  - Exception at oxf:/config/i18n.xsl, line -1, column -1

org.orbeon.oxf.common.OXFException: Cannot modify read-only instance.
    at org.orbeon.oxf.xforms.ReadonlyInstanceData.throwException (ReadonlyInstanceData.java:76)
    at org.orbeon.oxf.xforms.ReadonlyInstanceData.setGenerated(ReadonlyInstanceData.java:96)
    at org.orbeon.oxf.processor.xforms.output.element.XFormsElement.start(XFormsElement.java :138)
    at org.orbeon.oxf.processor.xforms.output.element.ViewContentHandler.startElement(ViewContentHandler.java:71)
    at org.orbeon.oxf.xml.SimpleForwardingContentHandler.startElement(SimpleForwardingContentHandler.java :69)
    at org.orbeon.saxon.event.ContentHandlerProxy.startContent(ContentHandlerProxy.java:349)
    at org.orbeon.saxon.event.ProxyReceiver.startContent(ProxyReceiver.java:162)
    at org.orbeon.saxon.event.NamespaceReducer.startContent (NamespaceReducer.java:168)
    at org.orbeon.saxon.event.ComplexContentOutputter.startContent(ComplexContentOutputter.java:502)
    at org.orbeon.saxon.event.ComplexContentOutputter.startElement(ComplexContentOutputter.java :153)
    ...
  

Thanks in advance.

Zsolt



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Hi Zsolt,

On 3/26/07, Zsolt Czinkos <[hidden email]> wrote:
> 1) I'd like to use the new 'xforms:textarea mediatype="text/html"' element,
> but id prints an error: 'xforms-element-9 not found'. I must have got rid of
> something what I shouldn't have. Can anybody give me a hint, what is
> missing?

Hard to say. Is element 'xforms-element-9' really not there in the
generated HTML, or is it just that the code can't find it for some
reason? I think that the simplest way to solve this one if for you to
create a reproducible case that we can run the XForms sandbox, and
then share this test case with us here.

> 2) After fixing all the incompatible changes (like oxf:data in XSLTs), I got
> the following error stacktrace:
>
> 2007-03-26 09:55:01,906 http-8080-1 ERROR webapp.ProcessorService  -
> Exception at oxf:/config/i18n.xsl, line -1, column -1
>
> org.orbeon.oxf.common.OXFException: Cannot modify read-only
> instance.

Erik or I will post a follow-up response on this one.

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Zsolt, are you using the new xxforms:readonly="true" on xforms:instance?

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Hello,

No I don't use anyof the related attributes. I have an existing webapp written under the Orbeon 2.8., and I just put it into the new Orbeon 3.5. I cleaned up the 3.5 webapp, modeified epilogue.xpl slightly, removed the demo apps.

I made some small changes, like changing oxf:instance to input:instance in XSLT-s, but nothing else.
First, I would like to get the webapp working with the legacy XForms engine. After that, I'll refactor it to the new version.

I have an xslt processor which runs the i18n.xsl script, that's called from the epilogue.xpl. This is in the stack-trace. When I put a debug attribute to the output of this processor, it prints the XML document result, but that's the last step. When debug attribute is present, the stak trace doesn't contain the i18n.xsl, only the epilogue.xpl.

I'll send some short code snippet as soon as I arrive at the office.

Zsolt




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Here they are:

epilogue.xpl:
------------------

   <p:processor name="oxf:xslt">
        <p:input name="data" href="#data"/>
        <p:input name="config" href=" i18n.xsl"/>
        <p:input name="locale" href="#currControllerData"/>
        <p:output name="data" id="localized-data" debug="LOCALIZED" /> <!-- This is line 45 -->
    </p:processor>

   <!-- LOCALIZED debug is printed in the log. It's OK. -->

    <!-- Run the XForms epilogue -->
    <!-- If you don't use XForms at all, you can bypass this -->
    <p:processor name="oxf:pipeline">
        <p:input name="config" href="/ops/pfc/xforms-epilogue.xpl"/>
        <p:input name="data" href="#localized-data"/>
        <p:input name="instance" href="#instance"/>
        <p:input name="xforms-model" href="#xforms-model"/>
        <p:output name="xformed-data" id="xformed-data" debug="XFORMED-DATA"/> <!-- XFORMED-DATA is not in the log -->
    </p:processor>


The exception:
----------------------

2007-03-28 11:29:14,117 http-9006-Processor25 ERROR webapp.ProcessorService  - Exception at oxf:/config/epilogue.xpl, line 45, column 71, description reading processor output
org.orbeon.oxf.common.OXFException: Cannot modify read-only instance.
        at org.orbeon.oxf.xforms.ReadonlyInstanceData.throwException(ReadonlyInstanceData.java:76)
        at org.orbeon.oxf.xforms.ReadonlyInstanceData.setGenerated (ReadonlyInstanceData.java:96)
        at org.orbeon.oxf.processor.xforms.output.element.XFormsElement.start(XFormsElement.java:138)
        at org.orbeon.oxf.processor.xforms.output.element.ViewContentHandler.startElement (ViewContentHandler.java:
71)
        at org.orbeon.oxf.xml.SAXStore.replay(SAXStore.java:165)
        at org.orbeon.oxf.processor.DebugProcessor$1.readImpl(DebugProcessor.java:76)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read (ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl$ConcreteProcessorFilter.read (ProcessorImpl.j
ava:990)

-------------------------------

I've searched for the xxfomr:readonly attribute, but it is only in the orbeon files (xforms-widget etc). I don't use them.


Thank you for your help.


Cheers,

Zsolt





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On 3/28/07, Alessandro Vernet <[hidden email]> wrote:

I put my app containing the xforms:textarea into the original ops webapp demo application, and there it works. In my own webapp I cleaned up the sample app specific code, and probably I swept something important out. Any idea, what is missing?

BTW, is there any skeleton app, which conatins only a hello world example, without any style, theme wired in it?


Thanks

Zsolt


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

One more piece of information.

Our webapp has a login page, after authentication it displays a mainMenu. The mainMenu uses XPL-s, XForms, and it works. There's a listing page, and that one produces the err, described below.

I'll have a look at the differences between the two views. Any incompatible XForms changes that I missed (when using the xforms attribute in page-flow)?

Any help is appreciated,

Thanks

Zsolt




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Hi

Finally, I've found the error.

Changing xforms:group ref="form" to xforms:group ref="/form" solved the problem. No read-only message now.

Thanks for your attenion.

Zsolt




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Great! Still, I wonder why this would cause Orbeon Forms to believe the
instance is read-only.

-Erik

Zsolt Czinkos wrote:
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Zsolt Czinkos wrote:

> I put my app containing the xforms:textarea into the original ops webapp
> demo application, and there it works. In my own webapp I cleaned up the
> sample app specific code, and probably I swept something important out.
> Any idea, what is missing?

Hard to tell without seeing your files, but you shouldn't need anything
else under RESOURCES except the config and apps directories (and you can
remove all apps under that directory, except maybe apps/context).

> BTW, is there any skeleton app, which conatins only a hello world
> example, without any style, theme wired in it?

Yes, under:

RESOURCES/apps/xforms-hello/*

To remove the examples sidebar, see this FAQ entry:

http://www.orbeon.com/ops/doc/home-faq#remove-sidebar

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Thanks Erik.

Zsolt




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws