support for nillable="true" in WFS Schemas

[steve cameron]

Hello,

I am wondering if there is support for the nillable="true" attribute in
WFS Schemas and hence xsi:null="true" in WFS transaction inserts?

--
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: [phone]
Fax: [phone]
Email: [hidden email]
URL: http://www.imos.org.au/eMII.html


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
deegree-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/deegree-users

[steve cameron]

Stephen Cameron wrote:
> Hello,
>
> I am wondering if there is support for the nillable="true" attribute in
> WFS Schemas and hence xsi:null="true" in WFS transaction inserts?
>
>  
To answer my own question, I think not. I am using deegree 2.2 and get
an error as below:

    Cannot convert value ("") of property "aatams:bottom_depth
(aatams=http://www.imos.org.au/aatams)" in feature with id "" to "Float".

Also, looking at source code I see the following in the
AbstractPropertyType class:

    /**
     * @return The minimum occurrences of the property within the
surrounding feature. Returns '0'
     *         if the property is 'nillable'.
     */
    public final int getMinOccurs() {
        return this.minOccurs;
    }

In the xforms web client that I have built this lack of support is a
problem for me. I have a WFS insert transaction template and I insert
values (as entered or selected by users) into the template. However for
numeric properties that have minOccurs="0" and which the user does not
enter a value (and which should be set to NULL in the datastore) I have
to delete these properties from the template before submitting it to
deegree WFS to avoid the above error. However, under the xforms design
this results in the input control disappearing  from the page, which is
a bit disconcerting.

If there was support for 'nillable' then instead of deleting a property
I could set  xsi:nil="true" before doing the submit and so no problems
(I hope).

Thanks

--
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: [phone]
Fax: [phone]
Email: [hidden email]
URL: http://www.imos.org.au/eMII.html


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
deegree-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/deegree-users

[Markus Schneider-4]

Hi Stephen,

sorry for the slow response.

Stephen Cameron wrote:

>
>> I am wondering if there is support for the nillable="true" attribute in
>> WFS Schemas and hence xsi:null="true" in WFS transaction inserts?
>>
>>  
> To answer my own question, I think not.

That's right. There's no native support in the feature mode for this. Of course you could add support for this by using
XSL in the WFS.

> I am using deegree 2.2 and get an error as below:
>
>     Cannot convert value ("") of property "aatams:bottom_depth
> (aatams=http://www.imos.org.au/aatams)" in feature with id "" to "Float".
>
> Also, looking at source code I see the following in the
> AbstractPropertyType class:
>
>     /**
>      * @return The minimum occurrences of the property within the
> surrounding feature. Returns '0'
>      *         if the property is 'nillable'.
>      */
>     public final int getMinOccurs() {
>         return this.minOccurs;
>     }
>
> In the xforms web client that I have built this lack of support is a
> problem for me. I have a WFS insert transaction template and I insert
> values (as entered or selected by users) into the template. However for
> numeric properties that have minOccurs="0" and which the user does not
> enter a value (and which should be set to NULL in the datastore) I have
> to delete these properties from the template before submitting it to
> deegree WFS to avoid the above error. However, under the xforms design
> this results in the input control disappearing  from the page, which is
> a bit disconcerting.
>
> If there was support for 'nillable' then instead of deleting a property
> I could set  xsi:nil="true" before doing the submit and so no problems
> (I hope).

Would the XSL way be a solution? This could bridge the time until you can use the deegree 3 WFS instead (which will
support nillable/xsi:nil natively) :-)

Best regards,
Markus

--
Markus Schneider

l a t / l o n  GmbH
Aennchenstrasse 19           53177 Bonn, Germany
phone ++49 [phone]       fax ++49 [phone]
http://www.lat-lon.de        http://www.deegree.org



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
deegree-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/deegree-users

[steve cameron]

Hi Markus,

Does this mean I can transform the incoming XML using XSL before it gets
processed by deegree into the datastore? I have used XSL to transform
outgoing responses but not incoming.

Markus Schneider wrote:

> Hi Stephen,
>
> sorry for the slow response.
>
> Stephen Cameron wrote:
>
>  
>>> I am wondering if there is support for the nillable="true" attribute in
>>> WFS Schemas and hence xsi:null="true" in WFS transaction inserts?
>>>
>>>  
>>>      
>> To answer my own question, I think not.
>>    
>
> That's right. There's no native support in the feature mode for this. Of course you could add support for this by using
> XSL in the WFS.
>
>  
>> I am using deegree 2.2 and get an error as below:
>>
>>     Cannot convert value ("") of property "aatams:bottom_depth
>> (aatams=http://www.imos.org.au/aatams)" in feature with id "" to "Float".
>>
>> Also, looking at source code I see the following in the
>> AbstractPropertyType class:
>>
>>     /**
>>      * @return The minimum occurrences of the property within the
>> surrounding feature. Returns '0'
>>      *         if the property is 'nillable'.
>>      */
>>     public final int getMinOccurs() {
>>         return this.minOccurs;
>>     }
>>
>> In the xforms web client that I have built this lack of support is a
>> problem for me. I have a WFS insert transaction template and I insert
>> values (as entered or selected by users) into the template. However for
>> numeric properties that have minOccurs="0" and which the user does not
>> enter a value (and which should be set to NULL in the datastore) I have
>> to delete these properties from the template before submitting it to
>> deegree WFS to avoid the above error. However, under the xforms design
>> this results in the input control disappearing  from the page, which is
>> a bit disconcerting.
>>
>> If there was support for 'nillable' then instead of deleting a property
>> I could set  xsi:nil="true" before doing the submit and so no problems
>> (I hope).
>>    
>
> Would the XSL way be a solution? This could bridge the time until you can use the deegree 3 WFS instead (which will
> support nillable/xsi:nil natively) :-)
>
> Best regards,
> Markus
>
>  
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> ------------------------------------------------------------------------
>
> _______________________________________________
> deegree-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/deegree-users
>  

--
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: [phone]
Fax: [phone]
Email: [hidden email]
URL: http://www.imos.org.au/eMII.html


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
deegree-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/deegree-users

[steve cameron]

Markus, out of interest is deegree 3 close to being useable for WFS-T?

Markus Schneider wrote:

> Hi Stephen,
>
> sorry for the slow response.
>
> Stephen Cameron wrote:
>
>  
>>> I am wondering if there is support for the nillable="true" attribute in
>>> WFS Schemas and hence xsi:null="true" in WFS transaction inserts?
>>>
>>>  
>>>      
>> To answer my own question, I think not.
>>    
>
> That's right. There's no native support in the feature mode for this. Of course you could add support for this by using
> XSL in the WFS.
>
>  
>> I am using deegree 2.2 and get an error as below:
>>
>>     Cannot convert value ("") of property "aatams:bottom_depth
>> (aatams=http://www.imos.org.au/aatams)" in feature with id "" to "Float".
>>
>> Also, looking at source code I see the following in the
>> AbstractPropertyType class:
>>
>>     /**
>>      * @return The minimum occurrences of the property within the
>> surrounding feature. Returns '0'
>>      *         if the property is 'nillable'.
>>      */
>>     public final int getMinOccurs() {
>>         return this.minOccurs;
>>     }
>>
>> In the xforms web client that I have built this lack of support is a
>> problem for me. I have a WFS insert transaction template and I insert
>> values (as entered or selected by users) into the template. However for
>> numeric properties that have minOccurs="0" and which the user does not
>> enter a value (and which should be set to NULL in the datastore) I have
>> to delete these properties from the template before submitting it to
>> deegree WFS to avoid the above error. However, under the xforms design
>> this results in the input control disappearing  from the page, which is
>> a bit disconcerting.
>>
>> If there was support for 'nillable' then instead of deleting a property
>> I could set  xsi:nil="true" before doing the submit and so no problems
>> (I hope).
>>    
>
> Would the XSL way be a solution? This could bridge the time until you can use the deegree 3 WFS instead (which will
> support nillable/xsi:nil natively) :-)
>
> Best regards,
> Markus
>
>  
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> ------------------------------------------------------------------------
>
> _______________________________________________
> deegree-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/deegree-users
>  

--
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: [phone]
Fax: [phone]
Email: [hidden email]
URL: http://www.imos.org.au/eMII.html


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
deegree-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/deegree-users