Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Yes, it was my fault. Maven referenced the Isis snapshot on my workspace, and it was not updated since 16th January. Thanks again, Martin!!!
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Yes, it was my fault. Maven referenced the Isis snapshot on my workspace, and it was not updated since 16th January. Thanks again, Martin!!!
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Hi, Martin.
I can share my screen through Hangouts.
I'm connected right now, or tomorrow morning I'll be available also, if you
find it useful.
Thanks,
Oscar
El 31/1/2015, a las 21:52, Martin Grigorov mgrigo...@apache.org escribió:
No luck!
I've added -Duser.language=es -Duser.country=ES to my VM properties, and
I've switched my browser locale to German, Polish and Chinese.
The date picker works as desired with all combinations.
http://momentjs.com/docs/#/i18n/ http://momentjs.com/docs/#/i18n/ explains
how to change the locale, so I've tried moment.locale(es) in the F12 Dev
console but the output was en. And this is expected because Isis doesn't
provide custom locales for Moment.js, so only the default EN is available.
Any hints how to reproduce are welcome!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:41 PM, Martin Grigorov mgrigo...@apache.org
mailto:mgrigo...@apache.org wrote:
And a second later I realized that I've reverted Person class to its original
version before trying with the disabled #disabled().
Now I can edit the date field and all seems OK.
I guess it is related to the locale Moment.js uses. I use en_US and I guess
Johan uses nl_NL, and Oscar es_ES.
Trying ...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:36 PM, Martin Grigorov mgrigo...@apache.org
mailto:mgrigo...@apache.org wrote:
I've found info.matchingservice.dom.MatchingSecureMutableObject#disabled and
modified it to return null, thus not disabling the entity, but still it
appeats not editable in the UI...
Please give more details
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:31 PM, Martin Grigorov mgrigo...@apache.org
mailto:mgrigo...@apache.org wrote:
Johan,
How I can reproduce the issue ?
Initially Person object appeared to be immutable in the UI, so I have removed
editing=Editing.DISABLED from its @DomainObject definition.
But it is still immutable, i.e. I cannot edit it.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:09 PM, Martin Grigorov mgrigo...@apache.org
mailto:mgrigo...@apache.org wrote:
I'll try Johan's app now.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 7:31 PM, GESCONSULTOR - Óscar Bou
o@gesconsultor.com mailto:o@gesconsultor.com wrote:
Just to clarify it.
The property is of type:
java.util.Date
HTH,
Oscar
El 31/1/2015, a las 18:30, GESCONSULTOR - Óscar Bou o@gesconsultor.com
mailto:o@gesconsultor.com escribió:
Hi Martin and Johan,
I have an issue perhaps related to this one.
I'm working against latest SNAPSHOT (updated right now).
I have the following Entity:
@PersistenceCapable
public class GenericOrder {
// {{ OrderDate (property)
private Date orderDate;
@MemberOrder(sequence = 000.000.020)
@Column(allowsNull = false)
public Date getOrderDate() {
return this.orderDate;
}
public void setOrderDate(final Date orderDate) {
this.orderDate = orderDate;
}
@SuppressWarnings(static-method)
public Date defaultOrderDate() {
return new Date();
}
// }}
...
}
I create instances with a factory method like this one:
// {{ createGenericOrder (action)
@ActionSemantics(Of.NON_IDEMPOTENT)
@MemberOrder(sequence = 1)
public GenericOrder createGenericOrder(@XMSActionField(locales = {
@XMSLocale(locale = es, caption = Cliente) }) @Named(Customer) final
Customer customer,
@XMSActionField(locales = { @XMSLocale(locale = es, caption =
Descripción) }) @Named(Description) @Optional final String description) {
final GenericOrder genericOrder =
this.newTransientMultiTenantUnnamedEntity(GenericOrder.class, null,
description);
this.wrap(genericOrder).setCustomer(customer);
this.persist(genericOrder);
return genericOrder;
}
And the Order.OrderDate property is properly initialized.
But on the Wicket viewer I see that the date shown is 31-01-20, instead of
31-01-15.
That's been when having on isis.properties:
isis.value.format.date=dd-MM-
If changed to:
isis.value.format.date=DD-MM-
There's no change, showing also 31-01-20.
Thanks,
Oscar
El 30/1/2015, a las 16:55, Martin Grigorov mgrigo...@apache.org
mailto:mgrigo...@apache.org escribió:
Johan,
Do you still face the issue ?
ISIS-1012 has been merged to master already.
Martin Grigorov
Wicket Training and Consulting
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Hi Martin,
It works OK now. Tnx!
It looks like ISIS-1012 solved it. At least that seems logical to me, since I
left the issue unchanged until now.
[Sorry I wasn't online to save you some hassle with my app. Only first time
login gives a user the ability to create a person. My testuser for this is user
'jeanne' pw 'pass'. (See shiro.ini)]
Grtz Johan
blockquote{margin:0px;}
No luck!
I've added -Duser.language=es -Duser.country=ES to my VM
properties, and I've switched my browser locale to German, Polish and Chinese.
The date picker works as desired with all combinations.
http://momentjs.com/docs/#/i18n/ explains how to change the
locale, so I've tried moment.locale(es) in the F12 Dev console but the
output was en. And this is expected because Isis doesn't provide custom
locales for Moment.js, so only the default EN is available.
Any hints how to reproduce are welcome!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:41 PM, Martin Grigorov wrote:
And a second later I realized that I've
reverted Person class to its original version before trying with the disabled
#disabled().
Now I can edit the date field and all
seems OK.
I guess it is related to the locale
Moment.js uses. I use en_US and I guess Johan uses nl_NL, and Oscar es_ES.
Trying ...
Martin Grigorov
Wicket Training
and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at
10:36 PM, Martin Grigorov wrote:
I've
found info.matchingservice.dom.MatchingSecureMutableObject#disabled and
modified it to return null, thus not disabling the entity, but still it appeats
not editable in the UI...
Please give more details
Martin Grigorov
Wicket Training and Consulting
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Just to close the thread here:
Oscar's problem was that Eclipse was still using old version of Isis. After
update and rebuild everything works as desired.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sun, Feb 1, 2015 at 8:08 PM, GESCONSULTOR - Óscar Bou
o@gesconsultor.com wrote:
Hi, Martin.
I can share my screen through Hangouts.
I'm connected right now, or tomorrow morning I'll be available also, if
you find it useful.
Thanks,
Oscar
El 31/1/2015, a las 21:52, Martin Grigorov mgrigo...@apache.org
escribió:
No luck!
I've added -Duser.language=es -Duser.country=ES to my VM properties, and
I've switched my browser locale to German, Polish and Chinese.
The date picker works as desired with all combinations.
http://momentjs.com/docs/#/i18n/ explains how to change the locale, so
I've tried moment.locale(es) in the F12 Dev console but the output was
en. And this is expected because Isis doesn't provide custom locales for
Moment.js, so only the default EN is available.
Any hints how to reproduce are welcome!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:41 PM, Martin Grigorov mgrigo...@apache.org
wrote:
And a second later I realized that I've reverted Person class to its
original version before trying with the disabled #disabled().
Now I can edit the date field and all seems OK.
I guess it is related to the locale Moment.js uses. I use en_US and I
guess Johan uses nl_NL, and Oscar es_ES.
Trying ...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:36 PM, Martin Grigorov mgrigo...@apache.org
wrote:
I've found info.matchingservice.dom.MatchingSecureMutableObject#disabled
and modified it to return null, thus not disabling the entity, but still it
appeats not editable in the UI...
Please give more details
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:31 PM, Martin Grigorov mgrigo...@apache.org
wrote:
Johan,
How I can reproduce the issue ?
Initially Person object appeared to be immutable in the UI, so I have
removed editing=Editing.DISABLED from its @DomainObject definition.
But it is still immutable, i.e. I cannot edit it.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:09 PM, Martin Grigorov mgrigo...@apache.org
wrote:
I'll try Johan's app now.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 7:31 PM, GESCONSULTOR - Óscar Bou
o@gesconsultor.com wrote:
Just to clarify it.
The property is of type:
java.util.Date
HTH,
Oscar
El 31/1/2015, a las 18:30, GESCONSULTOR - Óscar Bou
o@gesconsultor.com escribió:
Hi Martin and Johan,
I have an issue perhaps related to this one.
I'm working against latest SNAPSHOT (updated right now).
I have the following Entity:
@PersistenceCapable
public class GenericOrder {
// {{ OrderDate (property)
private Date orderDate;
@MemberOrder(sequence = 000.000.020)
@Column(allowsNull = false)
public Date getOrderDate() {
return this.orderDate;
}
public void setOrderDate(final Date orderDate) {
this.orderDate = orderDate;
}
@SuppressWarnings(static-method)
public Date defaultOrderDate() {
return new Date();
}
// }}
...
}
I create instances with a factory method like this one:
// {{ createGenericOrder (action)
@ActionSemantics(Of.NON_IDEMPOTENT)
@MemberOrder(sequence = 1)
public GenericOrder createGenericOrder(@XMSActionField(locales =
{ @XMSLocale(locale = es, caption = Cliente) }) @Named(Customer)
final Customer customer,
@XMSActionField(locales = { @XMSLocale(locale = es,
caption = Descripción) }) @Named(Description) @Optional final String
description) {
final GenericOrder genericOrder =
this.newTransientMultiTenantUnnamedEntity(GenericOrder.class, null,
description);
this.wrap(genericOrder).setCustomer(customer);
this.persist(genericOrder);
return genericOrder;
}
And the Order.OrderDate property is properly initialized.
But on the Wicket viewer I see that the date shown is 31-01-20,
instead of 31-01-15.
That's been when having on isis.properties:
isis.value.format.date=dd-MM-
If changed to:
isis.value.format.date=DD-MM-
There's no change, showing also 31-01-20.
Thanks,
Oscar
El 30/1/2015, a las 16:55, Martin Grigorov mgrigo...@apache.org
escribió:
Johan,
Do you still face the issue ?
ISIS-1012 has been merged to master already.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 11:29 AM, Dan Haywood
d...@haywood-associates.co.uk
wrote:
The changing times are because if the
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
I've found info.matchingservice.dom.MatchingSecureMutableObject#disabled
and modified it to return null, thus not disabling the entity, but still it
appeats not editable in the UI...
Please give more details
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:31 PM, Martin Grigorov mgrigo...@apache.org
wrote:
Johan,
How I can reproduce the issue ?
Initially Person object appeared to be immutable in the UI, so I have
removed editing=Editing.DISABLED from its @DomainObject definition.
But it is still immutable, i.e. I cannot edit it.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:09 PM, Martin Grigorov mgrigo...@apache.org
wrote:
I'll try Johan's app now.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 7:31 PM, GESCONSULTOR - Óscar Bou
o@gesconsultor.com wrote:
Just to clarify it.
The property is of type:
java.util.Date
HTH,
Oscar
El 31/1/2015, a las 18:30, GESCONSULTOR - Óscar Bou
o@gesconsultor.com escribió:
Hi Martin and Johan,
I have an issue perhaps related to this one.
I'm working against latest SNAPSHOT (updated right now).
I have the following Entity:
@PersistenceCapable
public class GenericOrder {
// {{ OrderDate (property)
private Date orderDate;
@MemberOrder(sequence = 000.000.020)
@Column(allowsNull = false)
public Date getOrderDate() {
return this.orderDate;
}
public void setOrderDate(final Date orderDate) {
this.orderDate = orderDate;
}
@SuppressWarnings(static-method)
public Date defaultOrderDate() {
return new Date();
}
// }}
...
}
I create instances with a factory method like this one:
// {{ createGenericOrder (action)
@ActionSemantics(Of.NON_IDEMPOTENT)
@MemberOrder(sequence = 1)
public GenericOrder createGenericOrder(@XMSActionField(locales = {
@XMSLocale(locale = es, caption = Cliente) }) @Named(Customer) final
Customer customer,
@XMSActionField(locales = { @XMSLocale(locale = es,
caption = Descripción) }) @Named(Description) @Optional final String
description) {
final GenericOrder genericOrder =
this.newTransientMultiTenantUnnamedEntity(GenericOrder.class, null,
description);
this.wrap(genericOrder).setCustomer(customer);
this.persist(genericOrder);
return genericOrder;
}
And the Order.OrderDate property is properly initialized.
But on the Wicket viewer I see that the date shown is 31-01-20,
instead of 31-01-15.
That's been when having on isis.properties:
isis.value.format.date=dd-MM-
If changed to:
isis.value.format.date=DD-MM-
There's no change, showing also 31-01-20.
Thanks,
Oscar
El 30/1/2015, a las 16:55, Martin Grigorov mgrigo...@apache.org
escribió:
Johan,
Do you still face the issue ?
ISIS-1012 has been merged to master already.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 11:29 AM, Dan Haywood
d...@haywood-associates.co.uk
wrote:
The changing times are because if the datepicker pattern *is* present in
isis.properties, then currently it is interpreted differently than before
... m vs M for months vs minutes.
I'll review the ISIS-1012 branch and merge into master later today, at
which point hopefully the issue should go away.
Thx
Dan
On 29 January 2015 at 08:53, johandoornen...@filternet.nl wrote:
Tnx Martin,
No haste needed at all. It is not a blocking issue at the moment. I will
keep you posted when I discover more - e.g. when I deploy on testserver I
will send you a link.
grtz Johan
Weird, indeed!
I won't have time to try your app today. But I'll do it as soon as I can!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 10:37 AM, wrote:
Hi Martin,
The issue is - for example - I choose januari 15, 2015 in datepicker
and
it displays 13-43-15 in dateinput. In FireFox 13-53-15 and Safari
31-35-15
Next login the values can change.. Really weird.
The code: [1] line 115
Grtz Johan
1.
https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Actor/Person.java
Hi,
The setting is isis.viewer.wicket.datePickerPattern, but if you don't
have
it then it should work just fine with its default [1].
There is no need to wait for ISIS-1012.
I've played a lot with
https://github.com/isisaddons/isis-app-kitchensink
yesterday and didn't find any issue with LocalDate.
What exactly is the problem ?
1.
https://github.com/apache/isis/blob/master/component/viewer/wicket/impl/src/main/java/org/apache/isis/viewer/wicket/viewer/settings/WicketViewerSettingsDefault.java#L98
Martin Grigorov
Wicket Training
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
I'll try Johan's app now.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 7:31 PM, GESCONSULTOR - Óscar Bou
o@gesconsultor.com wrote:
Just to clarify it.
The property is of type:
java.util.Date
HTH,
Oscar
El 31/1/2015, a las 18:30, GESCONSULTOR - Óscar Bou
o@gesconsultor.com escribió:
Hi Martin and Johan,
I have an issue perhaps related to this one.
I'm working against latest SNAPSHOT (updated right now).
I have the following Entity:
@PersistenceCapable
public class GenericOrder {
// {{ OrderDate (property)
private Date orderDate;
@MemberOrder(sequence = 000.000.020)
@Column(allowsNull = false)
public Date getOrderDate() {
return this.orderDate;
}
public void setOrderDate(final Date orderDate) {
this.orderDate = orderDate;
}
@SuppressWarnings(static-method)
public Date defaultOrderDate() {
return new Date();
}
// }}
...
}
I create instances with a factory method like this one:
// {{ createGenericOrder (action)
@ActionSemantics(Of.NON_IDEMPOTENT)
@MemberOrder(sequence = 1)
public GenericOrder createGenericOrder(@XMSActionField(locales = {
@XMSLocale(locale = es, caption = Cliente) }) @Named(Customer) final
Customer customer,
@XMSActionField(locales = { @XMSLocale(locale = es, caption
= Descripción) }) @Named(Description) @Optional final String
description) {
final GenericOrder genericOrder =
this.newTransientMultiTenantUnnamedEntity(GenericOrder.class, null,
description);
this.wrap(genericOrder).setCustomer(customer);
this.persist(genericOrder);
return genericOrder;
}
And the Order.OrderDate property is properly initialized.
But on the Wicket viewer I see that the date shown is 31-01-20, instead
of 31-01-15.
That's been when having on isis.properties:
isis.value.format.date=dd-MM-
If changed to:
isis.value.format.date=DD-MM-
There's no change, showing also 31-01-20.
Thanks,
Oscar
El 30/1/2015, a las 16:55, Martin Grigorov mgrigo...@apache.org
escribió:
Johan,
Do you still face the issue ?
ISIS-1012 has been merged to master already.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 11:29 AM, Dan Haywood
d...@haywood-associates.co.uk
wrote:
The changing times are because if the datepicker pattern *is* present in
isis.properties, then currently it is interpreted differently than before
... m vs M for months vs minutes.
I'll review the ISIS-1012 branch and merge into master later today, at
which point hopefully the issue should go away.
Thx
Dan
On 29 January 2015 at 08:53, johandoornen...@filternet.nl wrote:
Tnx Martin,
No haste needed at all. It is not a blocking issue at the moment. I will
keep you posted when I discover more - e.g. when I deploy on testserver I
will send you a link.
grtz Johan
Weird, indeed!
I won't have time to try your app today. But I'll do it as soon as I can!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 10:37 AM, wrote:
Hi Martin,
The issue is - for example - I choose januari 15, 2015 in datepicker
and
it displays 13-43-15 in dateinput. In FireFox 13-53-15 and Safari
31-35-15
Next login the values can change.. Really weird.
The code: [1] line 115
Grtz Johan
1.
https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Actor/Person.java
Hi,
The setting is isis.viewer.wicket.datePickerPattern, but if you don't
have
it then it should work just fine with its default [1].
There is no need to wait for ISIS-1012.
I've played a lot with
https://github.com/isisaddons/isis-app-kitchensink
yesterday and didn't find any issue with LocalDate.
What exactly is the problem ?
1.
https://github.com/apache/isis/blob/master/component/viewer/wicket/impl/src/main/java/org/apache/isis/viewer/wicket/viewer/settings/WicketViewerSettingsDefault.java#L98
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Jan 28, 2015 at 8:15 PM, wrote:
Hi Martin,
This setting used to work in 1.7.0
isis.value.format.date=dd-MM-
So I guess I wait for ISIS-1012 ?
grtz
Johan
Hi,
Check your isis.properties.
the datepicker pattern should be: DD-MM-
With ISIS-1012 (to be merged) this setting will be deprecated and not
used.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Jan 28, 2015 at 6:31 PM, wrote:
Hi,
A property as org.joda.time.LocalDate does not work well with the
datepicker in my app. Am I missing something - some config item
or...?
Grtz Johan
Óscar Bou Bou
Responsable de Producto
Auditor Jefe de
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
And a second later I realized that I've reverted Person class to its
original version before trying with the disabled #disabled().
Now I can edit the date field and all seems OK.
I guess it is related to the locale Moment.js uses. I use en_US and I guess
Johan uses nl_NL, and Oscar es_ES.
Trying ...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:36 PM, Martin Grigorov mgrigo...@apache.org
wrote:
I've found info.matchingservice.dom.MatchingSecureMutableObject#disabled
and modified it to return null, thus not disabling the entity, but still it
appeats not editable in the UI...
Please give more details
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:31 PM, Martin Grigorov mgrigo...@apache.org
wrote:
Johan,
How I can reproduce the issue ?
Initially Person object appeared to be immutable in the UI, so I have
removed editing=Editing.DISABLED from its @DomainObject definition.
But it is still immutable, i.e. I cannot edit it.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:09 PM, Martin Grigorov mgrigo...@apache.org
wrote:
I'll try Johan's app now.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 7:31 PM, GESCONSULTOR - Óscar Bou
o@gesconsultor.com wrote:
Just to clarify it.
The property is of type:
java.util.Date
HTH,
Oscar
El 31/1/2015, a las 18:30, GESCONSULTOR - Óscar Bou
o@gesconsultor.com escribió:
Hi Martin and Johan,
I have an issue perhaps related to this one.
I'm working against latest SNAPSHOT (updated right now).
I have the following Entity:
@PersistenceCapable
public class GenericOrder {
// {{ OrderDate (property)
private Date orderDate;
@MemberOrder(sequence = 000.000.020)
@Column(allowsNull = false)
public Date getOrderDate() {
return this.orderDate;
}
public void setOrderDate(final Date orderDate) {
this.orderDate = orderDate;
}
@SuppressWarnings(static-method)
public Date defaultOrderDate() {
return new Date();
}
// }}
...
}
I create instances with a factory method like this one:
// {{ createGenericOrder (action)
@ActionSemantics(Of.NON_IDEMPOTENT)
@MemberOrder(sequence = 1)
public GenericOrder createGenericOrder(@XMSActionField(locales = {
@XMSLocale(locale = es, caption = Cliente) }) @Named(Customer) final
Customer customer,
@XMSActionField(locales = { @XMSLocale(locale = es,
caption = Descripción) }) @Named(Description) @Optional final String
description) {
final GenericOrder genericOrder =
this.newTransientMultiTenantUnnamedEntity(GenericOrder.class, null,
description);
this.wrap(genericOrder).setCustomer(customer);
this.persist(genericOrder);
return genericOrder;
}
And the Order.OrderDate property is properly initialized.
But on the Wicket viewer I see that the date shown is 31-01-20,
instead of 31-01-15.
That's been when having on isis.properties:
isis.value.format.date=dd-MM-
If changed to:
isis.value.format.date=DD-MM-
There's no change, showing also 31-01-20.
Thanks,
Oscar
El 30/1/2015, a las 16:55, Martin Grigorov mgrigo...@apache.org
escribió:
Johan,
Do you still face the issue ?
ISIS-1012 has been merged to master already.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 11:29 AM, Dan Haywood
d...@haywood-associates.co.uk
wrote:
The changing times are because if the datepicker pattern *is* present in
isis.properties, then currently it is interpreted differently than
before
... m vs M for months vs minutes.
I'll review the ISIS-1012 branch and merge into master later today, at
which point hopefully the issue should go away.
Thx
Dan
On 29 January 2015 at 08:53, johandoornen...@filternet.nl wrote:
Tnx Martin,
No haste needed at all. It is not a blocking issue at the moment. I will
keep you posted when I discover more - e.g. when I deploy on testserver
I
will send you a link.
grtz Johan
Weird, indeed!
I won't have time to try your app today. But I'll do it as soon as I
can!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 10:37 AM, wrote:
Hi Martin,
The issue is - for example - I choose januari 15, 2015 in datepicker
and
it displays 13-43-15 in dateinput. In FireFox 13-53-15 and Safari
31-35-15
Next login the values can change.. Really weird.
The code: [1] line 115
Grtz Johan
1.
https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Actor/Person.java
Hi,
The setting is isis.viewer.wicket.datePickerPattern, but if you don't
have
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
No luck!
I've added -Duser.language=es -Duser.country=ES to my VM properties, and
I've switched my browser locale to German, Polish and Chinese.
The date picker works as desired with all combinations.
http://momentjs.com/docs/#/i18n/ explains how to change the locale, so I've
tried moment.locale(es) in the F12 Dev console but the output was en.
And this is expected because Isis doesn't provide custom locales for
Moment.js, so only the default EN is available.
Any hints how to reproduce are welcome!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:41 PM, Martin Grigorov mgrigo...@apache.org
wrote:
And a second later I realized that I've reverted Person class to its
original version before trying with the disabled #disabled().
Now I can edit the date field and all seems OK.
I guess it is related to the locale Moment.js uses. I use en_US and I
guess Johan uses nl_NL, and Oscar es_ES.
Trying ...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:36 PM, Martin Grigorov mgrigo...@apache.org
wrote:
I've found info.matchingservice.dom.MatchingSecureMutableObject#disabled
and modified it to return null, thus not disabling the entity, but still it
appeats not editable in the UI...
Please give more details
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:31 PM, Martin Grigorov mgrigo...@apache.org
wrote:
Johan,
How I can reproduce the issue ?
Initially Person object appeared to be immutable in the UI, so I have
removed editing=Editing.DISABLED from its @DomainObject definition.
But it is still immutable, i.e. I cannot edit it.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 10:09 PM, Martin Grigorov mgrigo...@apache.org
wrote:
I'll try Johan's app now.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Jan 31, 2015 at 7:31 PM, GESCONSULTOR - Óscar Bou
o@gesconsultor.com wrote:
Just to clarify it.
The property is of type:
java.util.Date
HTH,
Oscar
El 31/1/2015, a las 18:30, GESCONSULTOR - Óscar Bou
o@gesconsultor.com escribió:
Hi Martin and Johan,
I have an issue perhaps related to this one.
I'm working against latest SNAPSHOT (updated right now).
I have the following Entity:
@PersistenceCapable
public class GenericOrder {
// {{ OrderDate (property)
private Date orderDate;
@MemberOrder(sequence = 000.000.020)
@Column(allowsNull = false)
public Date getOrderDate() {
return this.orderDate;
}
public void setOrderDate(final Date orderDate) {
this.orderDate = orderDate;
}
@SuppressWarnings(static-method)
public Date defaultOrderDate() {
return new Date();
}
// }}
...
}
I create instances with a factory method like this one:
// {{ createGenericOrder (action)
@ActionSemantics(Of.NON_IDEMPOTENT)
@MemberOrder(sequence = 1)
public GenericOrder createGenericOrder(@XMSActionField(locales = {
@XMSLocale(locale = es, caption = Cliente) }) @Named(Customer) final
Customer customer,
@XMSActionField(locales = { @XMSLocale(locale = es,
caption = Descripción) }) @Named(Description) @Optional final String
description) {
final GenericOrder genericOrder =
this.newTransientMultiTenantUnnamedEntity(GenericOrder.class, null,
description);
this.wrap(genericOrder).setCustomer(customer);
this.persist(genericOrder);
return genericOrder;
}
And the Order.OrderDate property is properly initialized.
But on the Wicket viewer I see that the date shown is 31-01-20,
instead of 31-01-15.
That's been when having on isis.properties:
isis.value.format.date=dd-MM-
If changed to:
isis.value.format.date=DD-MM-
There's no change, showing also 31-01-20.
Thanks,
Oscar
El 30/1/2015, a las 16:55, Martin Grigorov mgrigo...@apache.org
escribió:
Johan,
Do you still face the issue ?
ISIS-1012 has been merged to master already.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 29, 2015 at 11:29 AM, Dan Haywood
d...@haywood-associates.co.uk
wrote:
The changing times are because if the datepicker pattern *is* present
in
isis.properties, then currently it is interpreted differently than
before
... m vs M for months vs minutes.
I'll review the ISIS-1012 branch and merge into master later today, at
which point hopefully the issue should go away.
Thx
Dan
On 29 January 2015 at 08:53, johandoornen...@filternet.nl wrote:
Tnx Martin,
No haste needed at all. It is not a blocking issue at the moment. I
will
keep you posted when I discover more - e.g. when I deploy on
testserver I
will send you a link.
grtz Johan
Weird, indeed!
I won't
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Johan, Do you still face the issue ? ISIS-1012 has been merged to master already. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jan 29, 2015 at 11:29 AM, Dan Haywood d...@haywood-associates.co.uk wrote: The changing times are because if the datepicker pattern *is* present in isis.properties, then currently it is interpreted differently than before ... m vs M for months vs minutes. I'll review the ISIS-1012 branch and merge into master later today, at which point hopefully the issue should go away. Thx Dan On 29 January 2015 at 08:53, johandoornen...@filternet.nl wrote: Tnx Martin, No haste needed at all. It is not a blocking issue at the moment. I will keep you posted when I discover more - e.g. when I deploy on testserver I will send you a link. grtz Johan Weird, indeed! I won't have time to try your app today. But I'll do it as soon as I can! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jan 29, 2015 at 10:37 AM, wrote: Hi Martin, The issue is - for example - I choose januari 15, 2015 in datepicker and it displays 13-43-15 in dateinput. In FireFox 13-53-15 and Safari 31-35-15 Next login the values can change.. Really weird. The code: [1] line 115 Grtz Johan 1. https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Actor/Person.java Hi, The setting is isis.viewer.wicket.datePickerPattern, but if you don't have it then it should work just fine with its default [1]. There is no need to wait for ISIS-1012. I've played a lot with https://github.com/isisaddons/isis-app-kitchensink yesterday and didn't find any issue with LocalDate. What exactly is the problem ? 1. https://github.com/apache/isis/blob/master/component/viewer/wicket/impl/src/main/java/org/apache/isis/viewer/wicket/viewer/settings/WicketViewerSettingsDefault.java#L98 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 8:15 PM, wrote: Hi Martin, This setting used to work in 1.7.0 isis.value.format.date=dd-MM- So I guess I wait for ISIS-1012 ? grtz Johan Hi, Check your isis.properties. the datepicker pattern should be: DD-MM- With ISIS-1012 (to be merged) this setting will be deprecated and not used. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 6:31 PM, wrote: Hi, A property as org.joda.time.LocalDate does not work well with the datepicker in my app. Am I missing something - some config item or...? Grtz Johan
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Weird, indeed! I won't have time to try your app today. But I'll do it as soon as I can! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jan 29, 2015 at 10:37 AM, johandoornen...@filternet.nl wrote: Hi Martin, The issue is - for example - I choose januari 15, 2015 in datepicker and it displays 13-43-15 in dateinput. In FireFox 13-53-15 and Safari 31-35-15 Next login the values can change.. Really weird. The code: [1] line 115 Grtz Johan 1. https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Actor/Person.java Hi, The setting is isis.viewer.wicket.datePickerPattern, but if you don't have it then it should work just fine with its default [1]. There is no need to wait for ISIS-1012. I've played a lot with https://github.com/isisaddons/isis-app-kitchensink yesterday and didn't find any issue with LocalDate. What exactly is the problem ? 1. https://github.com/apache/isis/blob/master/component/viewer/wicket/impl/src/main/java/org/apache/isis/viewer/wicket/viewer/settings/WicketViewerSettingsDefault.java#L98 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 8:15 PM, wrote: Hi Martin, This setting used to work in 1.7.0 isis.value.format.date=dd-MM- So I guess I wait for ISIS-1012 ? grtz Johan Hi, Check your isis.properties. the datepicker pattern should be: DD-MM- With ISIS-1012 (to be merged) this setting will be deprecated and not used. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 6:31 PM, wrote: Hi, A property as org.joda.time.LocalDate does not work well with the datepicker in my app. Am I missing something - some config item or...? Grtz Johan
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Hi Martin, The issue is - for example - I choose januari 15, 2015 in datepicker and it displays 13-43-15 in dateinput. In FireFox 13-53-15 and Safari 31-35-15 Next login the values can change.. Really weird. The code: [1] line 115 Grtz Johan 1. https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Actor/Person.java Hi, The setting is isis.viewer.wicket.datePickerPattern, but if you don't have it then it should work just fine with its default [1]. There is no need to wait for ISIS-1012. I've played a lot with https://github.com/isisaddons/isis-app-kitchensink yesterday and didn't find any issue with LocalDate. What exactly is the problem ? 1. https://github.com/apache/isis/blob/master/component/viewer/wicket/impl/src/main/java/org/apache/isis/viewer/wicket/viewer/settings/WicketViewerSettingsDefault.java#L98 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 8:15 PM, wrote: Hi Martin, This setting used to work in 1.7.0 isis.value.format.date=dd-MM- So I guess I wait for ISIS-1012 ? grtz Johan Hi, Check your isis.properties. the datepicker pattern should be: DD-MM- With ISIS-1012 (to be merged) this setting will be deprecated and not used. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 6:31 PM, wrote: Hi, A property as org.joda.time.LocalDate does not work well with the datepicker in my app. Am I missing something - some config item or...? Grtz Johan
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Tnx Martin, No haste needed at all. It is not a blocking issue at the moment. I will keep you posted when I discover more - e.g. when I deploy on testserver I will send you a link. grtz Johan Weird, indeed! I won't have time to try your app today. But I'll do it as soon as I can! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jan 29, 2015 at 10:37 AM, wrote: Hi Martin, The issue is - for example - I choose januari 15, 2015 in datepicker and it displays 13-43-15 in dateinput. In FireFox 13-53-15 and Safari 31-35-15 Next login the values can change.. Really weird. The code: [1] line 115 Grtz Johan 1. https://github.com/johandoornenbal/matching/blob/master/dom/src/main/java/info/matchingservice/dom/Actor/Person.java Hi, The setting is isis.viewer.wicket.datePickerPattern, but if you don't have it then it should work just fine with its default [1]. There is no need to wait for ISIS-1012. I've played a lot with https://github.com/isisaddons/isis-app-kitchensink yesterday and didn't find any issue with LocalDate. What exactly is the problem ? 1. https://github.com/apache/isis/blob/master/component/viewer/wicket/impl/src/main/java/org/apache/isis/viewer/wicket/viewer/settings/WicketViewerSettingsDefault.java#L98 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 8:15 PM, wrote: Hi Martin, This setting used to work in 1.7.0 isis.value.format.date=dd-MM- So I guess I wait for ISIS-1012 ? grtz Johan Hi, Check your isis.properties. the datepicker pattern should be: DD-MM- With ISIS-1012 (to be merged) this setting will be deprecated and not used. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 6:31 PM, wrote: Hi, A property as org.joda.time.LocalDate does not work well with the datepicker in my app. Am I missing something - some config item or...? Grtz Johan
Re: LocalDate UI (datepicker issue) in 1.8.0-Snapshot
Hi Martin, This setting used to work in 1.7.0 isis.value.format.date=dd-MM- So I guess I wait for ISIS-1012 ? grtz Johan Hi, Check your isis.properties. the datepicker pattern should be: DD-MM- With ISIS-1012 (to be merged) this setting will be deprecated and not used. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 6:31 PM, wrote: Hi, A property as org.joda.time.LocalDate does not work well with the datepicker in my app. Am I missing something - some config item or...? Grtz Johan
