[Yanel-dev] xinclude

Wed Jun 5 13:22:47 CEST 2013

Hi Balz

A link like for example

http://lists.wyona.org/pipermail/yanel-development/2013-June/006132.html

but if you resend the content would be fine as well.

I understand that it wasn't the same, but maybe it helps anyway ;-)

Thanks

Michael

Am 05.06.13 10:05, schrieb basZero:
> Hi Michael,
>
> what do you mean by link to the public mailing list?
> I searched my GMail account for it. I can forward you the mail if you 
> like. But as said, the topic was slightly different.
>
> Cheers
> Balz
>
>
> On Wed, Jun 5, 2013 at 9:56 AM, Michael Wechner 
> <michael.wechner at wyona.com <mailto:michael.wechner at wyona.com>> wrote:
>
>     Dear Balz
>
>     Am 04.06.13 17:05, schrieb basZero:
>>     Thanks Michael,
>>
>>     I'll have a look at the yanel view then, seems to be a possibility.
>
>     Please see for example
>
>     http://www.yanel.org//en/documentation/basic-xml-resource-type.html
>
>>
>>     I checked the mails already, the topic was similar, but there it
>>     was about how to render a "&" in the html.
>
>     do you have a link to the public mailing list about this?
>
>     Thanks
>
>     Michael
>
>>
>>     Cheers
>>     Balz
>>
>>
>>     On Tue, Jun 4, 2013 at 5:02 PM, Michael Wechner
>>     <michael.wechner at wyona.com <mailto:michael.wechner at wyona.com>> wrote:
>>
>>         Hi Balz
>>
>>         As a workaround you might make the same resource available
>>         under two URLs, but with different configurations
>>         or you can also configure an additional view and use this
>>         view for xinclude, e.g.
>>
>>         *<xi:include
>>         href="yanelresource:/blabla/blabla?yanel.resource.viewid=xml"/>*
>>
>>         Otherwise I need to check the code more closely how one could
>>         make this work, but IIRC we discussed this before.
>>         Maybe I find something inside the mailing lists...
>>
>>         HTH
>>
>>         Michael
>>
>>         Am 04.06.13 16:50, schrieb basZero:
>>>         Hi michael,
>>>
>>>         resource B is also used directly.
>>>         yes it would work when I set it to application/xml.
>>>
>>>         But there must be a way to do this also in text/html mode...
>>>
>>>         cheers
>>>         balz
>>>
>>>
>>>         On Tue, Jun 4, 2013 at 4:42 PM, Michael Wechner
>>>         <michael.wechner at wyona.com
>>>         <mailto:michael.wechner at wyona.com>> wrote:
>>>
>>>             Dear Balz
>>>
>>>             Does it work when you set the mime type of resource B to
>>>             application/xml and when you use the XML serializer?
>>>             Do you have to access resource B also directly or is it
>>>             only used via xinclude?
>>>
>>>             Cheers
>>>
>>>             Michael
>>>
>>>             Am 04.06.13 15:42, schrieb basZero:
>>>>             dear all,
>>>>
>>>>             I wanted to implement the following, but I struggled.
>>>>
>>>>             *What I have:*
>>>>             - There are two resources (A+B) producing a valid HTML
>>>>             page with mime type "text/html".
>>>>             So when looking at the source of those HTML pages, I
>>>>             see this at the top:
>>>>
>>>>             <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
>>>>             Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
>>>>
>>>>             - Resource B is able to deliver the whole page without
>>>>             menu and sidebar. This is achieved by passing in a URL
>>>>             parameter.
>>>>
>>>>             *What i want:*
>>>>
>>>>             - I would like to call the resource B with
>>>>             contentonly=true and include the resulting HTML code
>>>>             into the page of resource A.
>>>>
>>>>             How can you do that?
>>>>
>>>>             When I use the following in a XSL of resource A...
>>>>
>>>>             *<xi:include href="yanelresource:/blabla/blabla"/>*
>>>>
>>>>             ... it gives me this error:
>>>>             Transformation error:
>>>>             http://www.w3.org/TR/html4/loose.dtd:Line=31;Column=3:
>>>>             exception:org.xml.sax.SAXParseException: The
>>>>             declaration for the entity "HTML.Version" must end with
>>>>             '>'. root-cause:null line: -- Typical usage: line: ^
>>>>             error: org.xml.sax.SAXParseException: The declaration
>>>>             for the entity "HTML.Version" must end with '>'. ).
>>>>
>>>>             If you know something about how to include the HTML
>>>>             output of another resource in the called resource's
>>>>             XSL, let me know.
>>>>
>>>>             Cheers
>>>>             Bas
>>>>
>>>>
>>>
>>>
>>>             --
>>>             Yanel-development mailing list
>>>             Yanel-development at wyona.com
>>>             <mailto:Yanel-development at wyona.com>
>>>             http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>>
>>>
>>>
>>>
>>
>>
>>         --
>>         Yanel-development mailing list Yanel-development at wyona.com
>>         <mailto:Yanel-development at wyona.com>
>>         http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>
>
>     --
>     Yanel-development mailing list Yanel-development at wyona.com
>     <mailto:Yanel-development at wyona.com>
>     http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wyona.org/pipermail/yanel-development/attachments/20130605/84c5439e/attachment.html>