It seems like "unparsed-entity-uri()" does not work

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

It seems like "unparsed-entity-uri()" does not work

thao nguyen
Hello,

I have a pipeline which calls an external xslt file with oxf:xslt processor.
That xslt file uses unparsed-entity-uri(). Running it with saxon9 - outside of
the pipeline (not yet check with saxon8 but probably the same result) shows
that it has no problem of retrieving the expected results. However, when
calling it in orbeon pipeline, it always gets empty results. Does orbeon
support unparsed-entity-uri? (I have Orbeon 3.6 installed.)

I appreciate for any help,
Thao


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: It seems like "unparsed-entity-uri()" does not work

thao nguyen
Hi Alex,

Thanks for your info.

Yeap, probably an external small program would be a workaround solution. Maybe it can be called by "exec"?
Do you have a list of not-supported function(s) somewhere? As I hope I don't have all the functions that you don't support! ;-)

Thao

On Fri, Jan 15, 2010 at 9:49 AM, Alessandro Vernet <[hidden email]> wrote:
Thao,

We don't support it. To support unparsed entities, we would have to implement the SAX DTDHandler, which we don't. (We only implement the SAX ContentHandler.) This being said, I've never seen a need for this, but apparently you have ;). Do you have a workaround?

Alex


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: It seems like "unparsed-entity-uri()" does not work

Alessandro  Vernet
Administrator
Thao,

We don't have such a list, but any feature, function or otherwise, that relies on information carried by SAX handlers other than the ContentHandler (such as the DTDHandler, or the LexicalHandler) won't be supported.

One could argue that it is bad practice anyway to rely on anything that is not carried by the ContentHandler, but as usual, there are exceptions, and this is a discussion for another venue :).

Alex

On Jan 17, 2010, at 10:23 AM, Nguyen Thi Ngoc Thao <[hidden email]> wrote:

Hi Alex,

Thanks for your info.

Yeap, probably an external small program would be a workaround solution. Maybe it can be called by "exec"?
Do you have a list of not-supported function(s) somewhere? As I hope I don't have all the functions that you don't support! ;-)

Thao

On Fri, Jan 15, 2010 at 9:49 AM, Alessandro Vernet <[hidden email]> wrote:
Thao,

We don't support it. To support unparsed entities, we would have to implement the SAX DTDHandler, which we don't. (We only implement the SAX ContentHandler.) This being said, I've never seen a need for this, but apparently you have ;). Do you have a workaround?

Alex

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





--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet