You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Hector Fabio Meza <he...@smartools.com.co> on 2016/07/23 23:29:25 UTC
@MemberOrder and collections
Hi,
I'd like to be sure if the MemberOrder annotation applies also to the
ordering of columns in tables.
I have a superclass with two fields annotated like this
@Column(allowsNull = "true")
@MemberOrder(name = "Details", sequence = "4")
protected Date productiveStart;
@Column(allowsNull = "true")
@MemberOrder(name = "Details", sequence = "5")
@Property(optionality = Optionality.OPTIONAL)
protected Date productiveEnd;
Another class has a collection of a subclass of this class, and when I
enter the details page, the table is showing Productive End before
Productive Start.
Is there something else I need to do to indicate Isis the order of the
properties when rendering a table?
Thanks.
--
Hector Fabio Meza
R&D LEAD SMARTOOLS
(57) 300 2254455 [1]
Skype: hectorf.meza
www.smartools.com.co [2]
Links:
------
[1] tel:%2857%29%20300%206815404
[2] http://www.smartools.com.co/
Re: @MemberOrder and collections
Posted by Hector Fabio Meza <he...@smartools.com.co>.
I just realized the order of the columns in a collection is controlled
by the children's layout.xml instead of the parent's, which is rather
obvious in hindsight.
Thanks again.
El 2016-07-26 08:53, Hector Fabio Meza escribi�:
> Thanks for the answer, Dan. I do have a layout.xml, where I used <fieldset> and <field> to set the order of the fields, but I couldn't find tags to do the same for the collections, so I tried with memberOrder to see if it affected the order of the columns.
>
> I'll try putting the annotations on the getters and see if it has the desired effect.
>
> El 2016-07-25 02:17, Dan Haywood escribi�:
>
> Hi Hector,
> To answer your question : yes, @MemberOrder is used for the column order of tables as well as the ordering of fields on the object form.
>
> I think the issue is actually that the annotations are being ignored because you've placed them on the field (instance variable) whereas Isis only picks up annotations from the getter.
>
> The reason that the annotations are allowed to even be placed on fields is to support using Lombok annotations, eg as in the todoapp.
>
> Also, I notice that you have the @Column #allowsNull annotation as well as @Property#optionality. In fact (assuming the are both on the getter), Isis will use the @Column annotation value.
>
> Also, I suggest using the layout.xml rather than annotations ; it is much more flexible and allows dynamic reloading of layouts (no restart required).
>
> HTH,
> Dan
>
> On 24 Jul 2016 01:29, "Hector Fabio Meza" <he...@smartools.com.co> wrote:
>
> Hi,
>
> I'd like to be sure if the MemberOrder annotation applies also to the ordering of columns in tables.
>
> I have a superclass with two fields annotated like this
>
> @Column(allowsNull = "true")
> @MemberOrder(name = "Details", sequence = "4")
> protected Date productiveStart;
>
> @Column(allowsNull = "true")
> @MemberOrder(name = "Details", sequence = "5")
> @Property(optionality = Optionality.OPTIONAL)
> protected Date productiveEnd;
>
> Another class has a collection of a subclass of this class, and when I enter the details page, the table is showing Productive End before Productive Start.
>
> Is there something else I need to do to indicate Isis the order of the properties when rendering a table?
>
> Thanks.
>
> --
>
> Hector Fabio Meza
>
> R&D LEAD SMARTOOLS
> (57) 300 2254455 [1]
> Skype: hectorf.meza
> www.smartools.com.co [2]
--
Hector Fabio Meza
R&D LEAD SMARTOOLS
(57) 300 2254455 [1]
Skype: hectorf.meza
www.smartools.com.co [2]
--
Hector Fabio Meza
R&D LEAD SMARTOOLS
(57) 300 2254455 [1]
Skype: hectorf.meza
www.smartools.com.co [2]
Links:
------
[1] tel:%2857%29%20300%206815404
[2] http://www.smartools.com.co/
Re: @MemberOrder and collections
Posted by Hector Fabio Meza <he...@smartools.com.co>.
Thanks for the answer, Dan. I do have a layout.xml, where I used
<fieldset> and <field> to set the order of the fields, but I couldn't
find tags to do the same for the collections, so I tried with
memberOrder to see if it affected the order of the columns.
I'll try putting the annotations on the getters and see if it has the
desired effect.
El 2016-07-25 02:17, Dan Haywood escribi�:
> Hi Hector,
> To answer your question : yes, @MemberOrder is used for the column order of tables as well as the ordering of fields on the object form.
>
> I think the issue is actually that the annotations are being ignored because you've placed them on the field (instance variable) whereas Isis only picks up annotations from the getter.
>
> The reason that the annotations are allowed to even be placed on fields is to support using Lombok annotations, eg as in the todoapp.
>
> Also, I notice that you have the @Column #allowsNull annotation as well as @Property#optionality. In fact (assuming the are both on the getter), Isis will use the @Column annotation value.
>
> Also, I suggest using the layout.xml rather than annotations ; it is much more flexible and allows dynamic reloading of layouts (no restart required).
>
> HTH,
> Dan
>
> On 24 Jul 2016 01:29, "Hector Fabio Meza" <he...@smartools.com.co> wrote:
>
>> Hi,
>>
>> I'd like to be sure if the MemberOrder annotation applies also to the ordering of columns in tables.
>>
>> I have a superclass with two fields annotated like this
>>
>> @Column(allowsNull = "true")
>> @MemberOrder(name = "Details", sequence = "4")
>> protected Date productiveStart;
>>
>> @Column(allowsNull = "true")
>> @MemberOrder(name = "Details", sequence = "5")
>> @Property(optionality = Optionality.OPTIONAL)
>> protected Date productiveEnd;
>>
>> Another class has a collection of a subclass of this class, and when I enter the details page, the table is showing Productive End before Productive Start.
>>
>> Is there something else I need to do to indicate Isis the order of the properties when rendering a table?
>>
>> Thanks.
>>
>> --
>>
>> Hector Fabio Meza
>>
>> R&D LEAD SMARTOOLS
>> (57) 300 2254455 [1]
>> Skype: hectorf.meza
>> www.smartools.com.co [2]
--
Hector Fabio Meza
R&D LEAD SMARTOOLS
(57) 300 2254455 [1]
Skype: hectorf.meza
www.smartools.com.co [2]
Links:
------
[1] tel:%2857%29%20300%206815404
[2] http://www.smartools.com.co/
Re: @MemberOrder and collections
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Hi Hector,
To answer your question : yes, @MemberOrder is used for the column order of
tables as well as the ordering of fields on the object form.
I think the issue is actually that the annotations are being ignored
because you've placed them on the field (instance variable) whereas Isis
only picks up annotations from the getter.
The reason that the annotations are allowed to even be placed on fields is
to support using Lombok annotations, eg as in the todoapp.
Also, I notice that you have the @Column #allowsNull annotation as well as
@Property#optionality. In fact (assuming the are both on the getter), Isis
will use the @Column annotation value.
Also, I suggest using the layout.xml rather than annotations ; it is much
more flexible and allows dynamic reloading of layouts (no restart
required).
HTH,
Dan
On 24 Jul 2016 01:29, "Hector Fabio Meza" <he...@smartools.com.co>
wrote:
Hi,
I'd like to be sure if the MemberOrder annotation applies also to the
ordering of columns in tables.
I have a superclass with two fields annotated like this
@Column(allowsNull = "true")
@MemberOrder(name = "Details", sequence = "4")
protected Date productiveStart;
@Column(allowsNull = "true")
@MemberOrder(name = "Details", sequence = "5")
@Property(optionality = Optionality.OPTIONAL)
protected Date productiveEnd;
Another class has a collection of a subclass of this class, and when I
enter the details page, the table is showing Productive End before
Productive Start.
Is there something else I need to do to indicate Isis the order of the
properties when rendering a table?
Thanks.
--
*Hector Fabio Meza*
*R&D Lead smartools*
(57) 300 2254455 <%2857%29%20300%206815404>
Skype: hectorf.meza
www.smartools.com.co