hepabolu wrote:
Marc Portier said the following on 24/5/07 17:35:
we could start off by checking some more
1/ can jxpath in fact handle namespaces correctly as described above
( in https://issues.apache.org/jira/browse/COCOON-1671#action_12356396
the orginal reporter of the issue states
Carsten Ziegeler wrote:
hepabolu wrote:
Joerg Heinicke said the following on 23/5/07 20:03:
On 23.05.2007 13:07, hepabolu wrote:
+ I would comment (or even close-wontfix?) that bug with a
reference to the above conclusion from carsten. Just in case
somebody would want to apply the patch
Marc Portier wrote:
But taking it one step further: IMHO DomBuilder will use SAXParser down
below somewheree to actually do the parsing. So just setting the
parameter namespace-prefix in the cocoon.xconf will ensure all
saxparsers in the pool to (correctly) have the parameter set... so both
Carsten Ziegeler said the following on 23/5/07 21:43:
If I see this correctly, the difference between the two solutions is
that in the not working case, the DOMBuilder is used to build the DOM
whereas in the working case, the serializer is used and the result is
then parsed again.
As Marc
Helma wrote:
Carsten Ziegeler said the following on 23/5/07 21:43:
If I see this correctly, the difference between the two solutions is
that in the not working case, the DOMBuilder is used to build the DOM
whereas in the working case, the serializer is used and the result is
then parsed
Carsten Ziegeler wrote:
Marc Portier wrote:
But taking it one step further: IMHO DomBuilder will use SAXParser
down below somewheree to actually do the parsing. So just setting the
parameter namespace-prefix in the cocoon.xconf will ensure all
saxparsers in the pool to (correctly) have the
So you can't rely that you get the namespace attributes in the dom
builder.
I think this is where things go wrong.
Note that both binding file and source are generated with a pipeline and
pipelineUtil.toDOM.
I've done some debugging into pipelineUtil.toDOM and this is what I found:
-
hepabolu schrieb:
So you can't rely that you get the namespace attributes in the dom
builder.
I think this is where things go wrong.
Note that both binding file and source are generated with a pipeline and
pipelineUtil.toDOM.
I've done some debugging into pipelineUtil.toDOM and this is
Carsten Ziegeler said the following on 24/5/07 15:57:
hepabolu schrieb:
So you can't rely that you get the namespace attributes in the dom
builder.
I think this is where things go wrong.
Note that both binding file and source are generated with a pipeline
and pipelineUtil.toDOM.
I've done
Helma wrote
Yes. Source is:
oe:version xmlns:oe=openEHR/v1/Version
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ORIGINAL_VERSION
So in fact I want the first line of the binding file to bind to /oe:version
I don't think there are unused prefixes in both binding and source.
Carsten Ziegeler said the following on 24/5/07 16:14:
Helma wrote
Yes. Source is:
oe:version xmlns:oe=openEHR/v1/Version
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ORIGINAL_VERSION
So in fact I want the first line of the binding file to bind to
/oe:version
I don't
Helma wrote:
That's what I'm slowly starting to realise. For proper XML validation I
do need it so I assumed the parser requires this too.
That would partially explain why the binding file (without a
namespaceURI for 'oe') still maps to the source (in the source=file
situation). It would
hepabolu wrote:
Carsten Ziegeler said the following on 24/5/07 16:14:
Helma wrote
Yes. Source is:
oe:version xmlns:oe=openEHR/v1/Version
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ORIGINAL_VERSION
So in fact I want the first line of the binding file to bind to
Carsten Ziegeler wrote:
Helma wrote:
That's what I'm slowly starting to realise. For proper XML validation
I do need it so I assumed the parser requires this too.
That would partially explain why the binding file (without a
namespaceURI for 'oe') still maps to the source (in the
Marc Portier said the following on 24/5/07 17:35:
we could start off by checking some more
1/ can jxpath in fact handle namespaces correctly as described above
( in https://issues.apache.org/jira/browse/COCOON-1671#action_12356396
the orginal reporter of the issue states that this is the case,
hepabolu wrote:
Joerg Heinicke said the following on 22/5/07 22:18:
On 22.05.2007 17:07, Helma van der Linden wrote:
// Create the SAX parser and set the features so it creates the
events we need
SAXParser parser =
(SAXParser)manager.lookup(SAXParser.ROLE);
if(
Carsten Ziegeler wrote:
hepabolu wrote:
Joerg Heinicke said the following on 22/5/07 22:18:
On 22.05.2007 17:07, Helma van der Linden wrote:
// Create the SAX parser and set the features so it creates the
events we need
SAXParser parser =
hepabolu wrote
This is what I get:
source:
oe:version xmlns:oe=openEHR/v1/Version
/oe:version
binding file:
fb:context path=/oe:version xmlns:oe=openEHR/v1/Version
/fb:context
They don't match on oe:version (missing context path)
Debugging after applying the above patch showed
On 23.05.2007 13:07, hepabolu wrote:
+ I would comment (or even close-wontfix?) that bug with a reference
to the above conclusion from carsten. Just in case somebody would
want to apply the patch without giving it more thought...
I just added a comment.
Using the param is an appropriate
Joerg Heinicke said the following on 23/5/07 20:03:
On 23.05.2007 13:07, hepabolu wrote:
+ I would comment (or even close-wontfix?) that bug with a reference
to the above conclusion from carsten. Just in case somebody would
want to apply the patch without giving it more thought...
I just
hepabolu wrote:
Joerg Heinicke said the following on 23/5/07 20:03:
On 23.05.2007 13:07, hepabolu wrote:
+ I would comment (or even close-wontfix?) that bug with a
reference to the above conclusion from carsten. Just in case
somebody would want to apply the patch without giving it more
Guys,
once again I run into a problem with cforms binding with a namespaced
source.
Turns out that the namespace is not passed on to the
JXPathBindingManager. There are (at least?) 3 open JIRA issues on this
topic:
https://issues.apache.org/jira/browse/COCOON-1595
On 22.05.2007 17:07, Helma van der Linden wrote:
// Create the SAX parser and set the features so it creates the events
we need
SAXParser parser =
(SAXParser)manager.lookup(SAXParser.ROLE);
if( parser instanceof Parameterizable ) {
Parameters
On Sep 2, 2004, at 5:43 PM, Marc Portier wrote:
Sylvain Wallez wrote:
Marc Portier wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
If I'm binding an XML document to a form, is it possible to use
namespaces in the binding? (The bound data has namespaces)
After a very long hiatus (didn't know
Gianugo Rabellino wrote:
On Sep 2, 2004, at 5:43 PM, Marc Portier wrote:
Sylvain Wallez wrote:
Marc Portier wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
If I'm binding an XML document to a form, is it possible to use
namespaces in the binding? (The bound data has namespaces)
After a
Carsten Ziegeler wrote:
If I'm binding an XML document to a form, is it possible
to use namespaces in the binding? (The bound data has
namespaces)
not yet, no
it's a long outstanding todo :-(
basically, it boils down to understanding if and how jxpath can do it.
-marc=
--
Marc Portier
Marc Portier wrote:
Carsten Ziegeler wrote:
If I'm binding an XML document to a form, is it possible to use
namespaces in the binding? (The bound data has
namespaces)
not yet, no
it's a long outstanding todo :-(
Ah, ok.
basically, it boils down to understanding if and how
On Thu, 2004-09-02 at 11:55, Marc Portier wrote:
Carsten Ziegeler wrote:
If I'm binding an XML document to a form, is it possible
to use namespaces in the binding? (The bound data has
namespaces)
not yet, no
it's a long outstanding todo :-(
basically, it boils down to
Marc Portier wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
If I'm binding an XML document to a form, is it possible to use
namespaces in the binding? (The bound data has namespaces)
The solution I've used successfully up to now is to bind to a
document that already has a root element
Sylvain Wallez wrote:
Marc Portier wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
If I'm binding an XML document to a form, is it possible to use
namespaces in the binding? (The bound data has namespaces)
The solution I've used successfully up to now is to bind to a
document that
30 matches
Mail list logo
