problem with the validation-processor

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

problem with the validation-processor

ClausR
I've tried to use the validation processor, but I always got the following
exception in the output-line of the validation processor:

com.sun.msv.verifier.jarv.FactoryImpl$WrapperException
with the message: element "document" is not allowed here

What is wrong with the following code or is it not possible to validate against
this specific scheme? If I ommit the validation processor and use #docu as
input of the serializer I get a correct xml-code, what is looking valid against
the used scheme.
The documentation of thr validation processor says, that the output of the
processor is a mirror of the input (decorated with error tags).
An upgrade to Orbeon 3.6 changed nothing.

Any help will be greatly appreciated.
best regards,
Claus

<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
    xmlns:oxf="http://www.orbeon.com/oxf/processors"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:gmd="http://www.isotc211.org/2005/gmd"
    xmlns:xi="http://www.w3.org/2001/XInclude"
    xmlns:stx="http://stx.sourceforge.net/2002/ns">

    <p:param name="instance" type="input"/>

    <p:processor name="oxf:pipeline">
        <p:input name="config" href="../data-access/exist/read-document.xpl"/>
        <p:input name="doc-id" href="#instance#xpointer(/*/doc-id)"/>
        <p:output name="doc-info" id="docu"/>
    </p:processor>

    <p:processor name="oxf:validation">
        <p:input name="data" href="#docu"/>
        <p:input name="schema"
href="http://www.isotc211.org/2005/gmd/metadataEntity.xsd"/>
        <p:input name="config">
            <config>
                <decorate>true</decorate>
            </config>
        </p:input>
        <p:output name="data" id="valstream"/>
    </p:processor>

    <p:processor name="oxf:xml-serializer">
        <p:input name="data" href="#valstream"/>
        <p:input name="config">
            <config>
                <content-type>application/xml</content-type>
            </config>
        </p:input>
    </p:processor>


--
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: problem with the validation-processor

Alessandro Vernet
Administrator
On Jan 19, 2008 6:17 AM,  <[hidden email]> wrote:
> I've tried to use the validation processor, but I always got the following
> exception in the output-line of the validation processor:
>
> com.sun.msv.verifier.jarv.FactoryImpl$WrapperException
> with the message: element "document" is not allowed here

And where is this "document" element? Is it the root of #docu? Does
the schema allow for that? Could it be an issue with namespaces?

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, 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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: problem with the validation-processor

ClausR
I've attached a little application (runable ins the apps-directory),
which illustrates the problem.
Claus

Alessandro Vernet schrieb:

> On Jan 23, 2008 6:39 AM,  <[hidden email]> wrote:
>  
>> thank you for your reply, but I can't find any error in the namespaces.
>> I have stripped not needed details from the project and put a small test-xml
>> inside of the the validate.xpl and got the same error:
>>    element "document" is not allowed here
>>    
>
> What if you put a reference to a file that doesn't exist for sure. Are
> you getting the same error?
>  
No, in the same line 24  (  in line: <p:output name="data"
id="valstream"/>  ) I get::

2008-01-25 14:40:14,102 INFO  ProcessorService  - /valtest/valid -
Received request
2008-01-25 14:40:14,262 ERROR ProcessorService  - Exception at line 24,
column 41 of oxf:/apps/valtest/validate.xpl (reading processor output:
name='data', id='valstream')
com.sun.msv.verifier.jarv.FactoryImpl$WrapperException: element "html"
is not allowed here
    at
com.sun.msv.verifier.jarv.FactoryImpl$ThrowController.error(FactoryImpl.java:145)
    at com.sun.msv.reader.Controller.error(Controller.java:49)
    at com.sun.msv.reader.Controller.error(Controller.java:49)
    at com.sun.msv.reader.GrammarReader.reportError(GrammarReader.java:746)
...

if th link is coded correct:
2008-01-25 14:40:26,652 INFO  ProcessorService  - /valtest/valid -
Received request
2008-01-25 14:40:26,712 ERROR ProcessorService  - Exception at line 24,
column 41 of oxf:/apps/valtest/validate.xpl (reading processor output:
name='data', id='valstream')
com.sun.msv.verifier.jarv.FactoryImpl$WrapperException: element
"document" is not allowed here
    at
com.sun.msv.verifier.jarv.FactoryImpl$ThrowController.error(FactoryImpl.java:145)
    at com.sun.msv.reader.Controller.error(Controller.java:49)
    at com.sun.msv.reader.Controller.error(Controller.java:49)
    at com.sun.msv.reader.GrammarReader.reportError(GrammarReader.java:746)
...

>> Now I put the ISO-schema on a local place and changed the link, like below and
>> got a new error message from line 24 of validate.xpl:
>>       Cannot load "/valtest/iso19139/gmd/dynamicFeature.xsd" with webapp loader
>>    
>
> Do you have a file /valtest/iso19139/gmd/dynamicFeature.xsd in your
> resources directory, i.e.
> WEB-INF/resources/valtest/iso19139/gmd/dynamicFeature.xsd?
>
>  
No, the dynamicFeature.xsd is correct  located in the gml sub-directory
  ( /valtest/iso19139/gml/dynamicFeature.xsd )
and the only link to it in the scheme from /valtest/iso19139/gml/gml.xsd
is correct
also all links to gml.xsd are ok
> Maybe it would help if you could create a small "app" (that we can put
> under "apps") and that shows this problem. For more on creating an
> "app", see:
>
> http://www.orbeon.com/ops/doc/home-faq#reporting-issues
>
> Alex

Alessandro Vernet schrieb:

> On Jan 19, 2008 6:17 AM,  <[hidden email]> wrote:
>  
>> I've tried to use the validation processor, but I always got the following
>> exception in the output-line of the validation processor:
>>
>> com.sun.msv.verifier.jarv.FactoryImpl$WrapperException
>> with the message: element "document" is not allowed here
>>    
>
> And where is this "document" element? Is it the root of #docu? Does
> the schema allow for that? Could it be an issue with namespaces?
>
> 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

valtest.zip (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problem with the validation-processor

Alessandro Vernet
Administrator
Claus,

On Fri, Jan 25, 2008 at 5:57 AM, rachimow <[hidden email]> wrote:
> I've attached a little application (runable ins the apps-directory),
>  which illustrates the problem.

Thank you for creating this example, and sorry for the delay. I
downloaded the resources as I suspected that this was a problem with a
missing schema, or the server somehow returning something that is not
a schema. I did this with a wget -r -np http://www.isotc211.org/2005/.
Now I get the error:

Cannot read from file /apps/valtest/www.isotc211.org/2005/gmd/dynamicFeature.xsd

And in fact the dynamicFeature.xsd file is also not present in that
directory on the server. I have attached the updated valtest directory
with those files for references.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.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
OW2 mailing lists service home page: http://www.ow2.org/wws

valtest.zip (582K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Re: problem with the validation-processor

ClausR
Hi Alex,

thank you for your reply and your efford to find the error.
Now I have reduced the example with a mini scheme, which demonstrates
why the error arise. Please look in the file gco.xsd and you will see
that there is only a reference inside a directory and ther is also a
workaround to solve the problem. However I think it should work in both
cases, but I'm not a xml-sheme-guru to be sure about this. Other
validation processors (also based on xerces-parser) don't have this
problem. The workaround in the example only works if I validate against
a modified local scheme and not against the original at
http://www.isotc211.org/2005/ what isn't so smart.

Maybe there is an other solution.


Claus



Alessandro Vernet schrieb:

> Claus,
>
> On Fri, Jan 25, 2008 at 5:57 AM, rachimow <[hidden email]> wrote:
>  
>> I've attached a little application (runable ins the apps-directory),
>>  which illustrates the problem.
>>    
>
> Thank you for creating this example, and sorry for the delay. I
> downloaded the resources as I suspected that this was a problem with a
> missing schema, or the server somehow returning something that is not
> a schema. I did this with a wget -r -np http://www.isotc211.org/2005/.
> Now I get the error:
>
> Cannot read from file /apps/valtest/www.isotc211.org/2005/gmd/dynamicFeature.xsd
>
> And in fact the dynamicFeature.xsd file is also not present in that
> directory on the server. I have attached the updated valtest directory
> with those files for references.
>
> 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

valtest_2.zip (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: problem with the validation-processor

Alessandro Vernet
Administrator
Claus,

On Thu, Mar 6, 2008 at 9:36 AM, rachimow <[hidden email]> wrote:

>  thank you for your reply and your efford to find the error.
>  Now I have reduced the example with a mini scheme, which demonstrates
>  why the error arise. Please look in the file gco.xsd and you will see
>  that there is only a reference inside a directory and ther is also a
>  workaround to solve the problem. However I think it should work in both
>  cases, but I'm not a xml-sheme-guru to be sure about this. Other
>  validation processors (also based on xerces-parser) don't have this
>  problem. The workaround in the example only works if I validate against
>  a modified local scheme and not against the original at
>  http://www.isotc211.org/2005/ what isn't so smart.
Sorry for the delay! The error that I saw last time I tried to run
this was a reference to dynamicFeature.xsd which could not be
resolved. How is this related to gco.xsd? I don't see a reference to
in dynamicFeature.xsd.

Also, you are saying that you have a workaround; is that right? What
is it that you did to get around this?

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Re: problem with the validation-processor

ClausR
Hi,

exact that's the problem - there is no direct reference to
dynamicFeature.xsd in the gmd-subschema.


1.To make the problem more clear, in the last mail I'd send a miniexample.
   If you run this, you will get:
       Cannot load "/apps/valtest/minischema/gmd/basicTypes.xsd" with
webapp loader
   but the only reference to basicTypes.xsd is in gco.xsd.
   In the commentlines in gco.xsd. you'll find the workaround.


2. In the original schema  http://www.isotc211.org/2005/ the only reference
    to dynamicFeature.xsd you'll find inside
http://www.isotc211.org/2005/gml/gml.xsd and it looks like

...
        <!-- ====================================================================== -->
        <include schemaLocation="dynamicFeature.xsd"/>
        <include schemaLocation="topology.xsd"/>
        <include schemaLocation="coverage.xsd"/>
...

as workaround I changed the reference to the gml-files inside the
gml-subschema in the following way:

...
        <!-- ====================================================================== -->
        <include schemaLocation="../gml/dynamicFeature.xsd"/>
        <include schemaLocation="../gml/topology.xsd"/>
        <include schemaLocation="../gml/coverage.xsd"/>
...


Therefore as woraround it is necessary
-  to copy the original schema (the complete .../2005/.. directory) to a
private place
-  modify all references inside the gml-subschema like shown above
-  and reference against it ,
but I think this isn't an extra neat solution to work with an ISO schema.

What's amazing me, is the fact that in the other sub-schemas of the
ISO-schema like gmd or gco are in a above shown way.
In my opinion the original gml-like reference should work also - other
validators have no problems with it.

Claus


Alessandro Vernet schrieb:

> Claus,
>
> On Thu, Mar 6, 2008 at 9:36 AM, rachimow <[hidden email]> wrote:
>  
>>  thank you for your reply and your efford to find the error.
>>  Now I have reduced the example with a mini scheme, which demonstrates
>>  why the error arise. Please look in the file gco.xsd and you will see
>>  that there is only a reference inside a directory and ther is also a
>>  workaround to solve the problem. However I think it should work in both
>>  cases, but I'm not a xml-sheme-guru to be sure about this. Other
>>  validation processors (also based on xerces-parser) don't have this
>>  problem. The workaround in the example only works if I validate against
>>  a modified local scheme and not against the original at
>>  http://www.isotc211.org/2005/ what isn't so smart.
>>    
>
> Sorry for the delay! The error that I saw last time I tried to run
> this was a reference to dynamicFeature.xsd which could not be
> resolved. How is this related to gco.xsd? I don't see a reference to
> in dynamicFeature.xsd.
>
> Also, you are saying that you have a workaround; is that right? What
> is it that you did to get around this?
>
> 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: Re: Re: problem with the validation-processor

Alessandro Vernet
Administrator
On Wed, Mar 12, 2008 at 3:41 AM, rachimow <[hidden email]> wrote:
>  What's amazing me, is the fact that in the other sub-schemas of the
>  ISO-schema like gmd or gco are in a above shown way.
>  In my opinion the original gml-like reference should work also - other
>  validators have no problems with it.

This is the sequence of events:

gmd/metadataEntity.xsd, which includes ../gco/gco.xsd
gco/gco.xsd includes ../gco/basicTypes.xsd
gco/basicTypes.xsd imports ../gml/gml.xsd
gml/gml.xsd loads dynamicFeature.xsd

The last step fails because the validator looks for
gmd/dynamicFeature.xsd, which does not exist. Instead it should look
for gml/dynamicFeature.xsd, as the import as done from gml.xsd which
is in the gml directory.

So I think a workaround would be to change that link to be
../gml/dynamicFeature.xsd instead of just dynamicFeature.xsd.

I created a bug for this:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=308849&group_id=168&atid=350207

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Re: Re: Re: problem with the validation-processor

ClausR
Thanks for your efforts

Claus


Alessandro Vernet schrieb:

> On Wed, Mar 12, 2008 at 3:41 AM, rachimow <[hidden email]> wrote:
>  
>>  What's amazing me, is the fact that in the other sub-schemas of the
>>  ISO-schema like gmd or gco are in a above shown way.
>>  In my opinion the original gml-like reference should work also - other
>>  validators have no problems with it.
>>    
>
> This is the sequence of events:
>
> gmd/metadataEntity.xsd, which includes ../gco/gco.xsd
> gco/gco.xsd includes ../gco/basicTypes.xsd
> gco/basicTypes.xsd imports ../gml/gml.xsd
> gml/gml.xsd loads dynamicFeature.xsd
>
> The last step fails because the validator looks for
> gmd/dynamicFeature.xsd, which does not exist. Instead it should look
> for gml/dynamicFeature.xsd, as the import as done from gml.xsd which
> is in the gml directory.
>
> So I think a workaround would be to change that link to be
> ../gml/dynamicFeature.xsd instead of just dynamicFeature.xsd.
>
> I created a bug for this:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=308849&group_id=168&atid=350207
>
> 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
|

Illegal XML type for SQL type: {http://www.w3.org/2001/XMLSchema}int, NUMBER

anpati1
In reply to this post by Alessandro Vernet
Hi,
 
I guess there's no casting happening around here?This is the response for a select statement for an Oracle Number datatype column. What is the xml schema type for sql type number?
 
Thanks,
Anand


Save all your chat conversations. Find them online.

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

Resolved: Illegal XML type for SQL type: {http://www.w3.org/2001/XMLSchema}int, NUMBER

anpati1
Had to remove type attribute from my <sql:get-column-value>
 
and it works.
 
Thanks,
Anand
Anand Patil <[hidden email]> wrote:
Hi,
 
I guess there's no casting happening around here?This is the response for a select statement for an Oracle Number datatype column. What is the xml schema type for sql type number?
 
Thanks,
Anand

Save all your chat conversations. Find them online.
--
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


Forgot the famous last words? Access your message archive online. Click here.

--
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: Resolved: Illegal XML type for SQL type: {http://www.w3.org/2001/XMLSchema}int, NUMBER

Erik Bruchez
Administrator
Anand,

Thanks for letting us know.

-Erik

On Apr 2, 2008, at 6:43 AM, Anand Patil wrote:

> Had to remove type attribute from my <sql:get-column-value>
>
> and it works.
>
> Thanks,
> Anand
> Anand Patil <[hidden email]> wrote:
> Hi,
>
> I guess there's no casting happening around here?This is the  
> response for a select statement for an Oracle Number datatype  
> column. What is the xml schema type for sql type number?
>
> Thanks,
> Anand
> Save all your chat conversations. Find them online.
> --
> 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
>
> Forgot the famous last words? Access your message archive online.  
> Click here.
> --
> 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
--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Illegal XML type for SQL type: {http://www.w3.org/2001/XMLSchema}int, NUMBER

Alessandro Vernet
Administrator
In reply to this post by anpati1
Anand,

On Wed, Apr 2, 2008 at 6:28 AM, Anand Patil <[hidden email]> wrote:
> I guess there's no casting happening around here?This is the response for a
> select statement for an Oracle Number datatype column. What is the xml
> schema type for sql type number?

I guess you are using the SQL processor. You can find more about the
supported types in <sql:param> here:

http://www.orbeon.com/ops/doc/processors-sql#sql-query-update

If this doesn't help, could you quote the code the particular part of
your code (configuration to the SQL processor) that causes this
problem?

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.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
OW2 mailing lists service home page: http://www.ow2.org/wws