oxf: namespace and xslt

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

oxf: namespace and xslt

Oliver Charlet
hi folks,
for the records and the developers, here is my report about the strange
disapearance of
the oxf: namespace.

I tried to transform an xpl template file, filling some dynamic parts
and finally  getting
a fully functional xpl in the end. My problem was, that the root element
<p:config
  xmlns:p='http://www.orbeon.com/oxf/pipeline'   
  xmlns:oxf='http://www.orbeon.com/oxf/processors'
 >
turns out like this
<config
    xmlns="http://www.orbeon.com/oxf/pipeline"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 >
the xsl: namespace can be ignored and is of no concern. BUT I was missing
the oxf: namespace decalaration. I wonder if an XSLT processor by definition
should not consider attribute values while transforming. Obviously the saxon
doesn't care. What could I do? After fiddeling around with the
xsl:namespace-alias
tag which didn't bring any result, I just switched to ox: as the prefix.
And here is the funny part:
I know it sounds weird, but I tried it several times: The oxf: prefix is
ALWAYS
removed from the result document. Using ox: with exactly the same
namespace just works
ok.
Now that's strange, isn't it? Maybe some ops guru can think about that?
Maybe it is, because the XSLT processor itself is connected to the same
namespace
(http://www.orbeon.com/oxf/processors)?

:olli

--
-----------------------
oliver charlet
software development

11-041 Olsztyn, Poland

[hidden email]
-----------------------




--
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
Reply | Threaded
Open this post in threaded view
|

Re: oxf: namespace and xslt

Alessandro  Vernet
Administrator
Hi Olivier,

Yes, indeed, this is strange. I don't see at this point why you would
get a different behavior transforming a document using the 'ox' prefix
instead of 'oxf'. Would you have some code that we can run and that
shows this behavior?

Alex

On 12/8/05, Oliver Charlet <[hidden email]> wrote:

> hi folks,
> for the records and the developers, here is my report about the strange
> disapearance of
> the oxf: namespace.
>
> I tried to transform an xpl template file, filling some dynamic parts
> and finally  getting
> a fully functional xpl in the end. My problem was, that the root element
> <p:config
>   xmlns:p='http://www.orbeon.com/oxf/pipeline'
>   xmlns:oxf='http://www.orbeon.com/oxf/processors'
>  >
> turns out like this
> <config
>     xmlns="http://www.orbeon.com/oxf/pipeline"
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>  >
> the xsl: namespace can be ignored and is of no concern. BUT I was missing
> the oxf: namespace decalaration. I wonder if an XSLT processor by definition
> should not consider attribute values while transforming. Obviously the saxon
> doesn't care. What could I do? After fiddeling around with the
> xsl:namespace-alias
> tag which didn't bring any result, I just switched to ox: as the prefix.
> And here is the funny part:
> I know it sounds weird, but I tried it several times: The oxf: prefix is
> ALWAYS
> removed from the result document. Using ox: with exactly the same
> namespace just works
> ok.
> Now that's strange, isn't it? Maybe some ops guru can think about that?
> Maybe it is, because the XSLT processor itself is connected to the same
> namespace
> (http://www.orbeon.com/oxf/processors)?
>
> :olli
>
> --
> -----------------------
> oliver charlet
> software development
>
> 11-041 Olsztyn, Poland
>
> [hidden email]
> -----------------------
>
>
>
>
>
> --
> 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
>
>
>

--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/



--
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
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
Reply | Threaded
Open this post in threaded view
|

Re: oxf: namespace and xslt

Oliver Charlet
hmm. I wrote a test but could not reproduce the error under beta 4.
I was on beta 2 before. Don't know if that really made the difference.
It seems to work fine now. Probably another human error thing... ;-)
Thanks for looking at it anyway.
:oliver

Alessandro Vernet schrieb:
Hi Olivier,

Yes, indeed, this is strange. I don't see at this point why you would
get a different behavior transforming a document using the 'ox' prefix
instead of 'oxf'. Would you have some code that we can run and that
shows this behavior?

Alex

On 12/8/05, Oliver Charlet [hidden email] wrote:
  
hi folks,
for the records and the developers, here is my report about the strange
disapearance of
the oxf: namespace.

I tried to transform an xpl template file, filling some dynamic parts
and finally  getting
a fully functional xpl in the end. My problem was, that the root element
<p:config
  xmlns:p='http://www.orbeon.com/oxf/pipeline'
  xmlns:oxf='http://www.orbeon.com/oxf/processors'
 >
turns out like this
<config
    xmlns="http://www.orbeon.com/oxf/pipeline"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 >
the xsl: namespace can be ignored and is of no concern. BUT I was missing
the oxf: namespace decalaration. I wonder if an XSLT processor by definition
should not consider attribute values while transforming. Obviously the saxon
doesn't care. What could I do? After fiddeling around with the
xsl:namespace-alias
tag which didn't bring any result, I just switched to ox: as the prefix.
And here is the funny part:
I know it sounds weird, but I tried it several times: The oxf: prefix is
ALWAYS
removed from the result document. Using ox: with exactly the same
namespace just works
ok.
Now that's strange, isn't it? Maybe some ops guru can think about that?
Maybe it is, because the XSLT processor itself is connected to the same
namespace
(http://www.orbeon.com/oxf/processors)?

:olli

--
-----------------------
oliver charlet
software development

11-041 Olsztyn, Poland

[hidden email]
-----------------------





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



    


--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/

  

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

-- 
-----------------------
oliver charlet
software development

11-041 Olsztyn, Poland

[hidden email]
-----------------------


--
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