Here's why that might be the solution.
Within the metamodel we support the concept of mutable collections. This
dates back to the early days of the framework, where one could drag-n-drop
objects into collections to create associations.
When I implemented the wicket viewer I never got around to im
Hi Erik,
If you mark the collection as non-editable, then I suspect this might fix
it. Could you give that a try?
Thx
Dan
On Tue, 21 Jan 2020, 10:05 Dan Haywood,
wrote:
> Thanks, Erik, I'll take a look.
>
>
> On Tue, 21 Jan 2020, 09:59 Erik de Hair, wrote:
>
>> //
>>
>> Hi,
>>
>> I was able
Thanks, Erik, I'll take a look.
On Tue, 21 Jan 2020, 09:59 Erik de Hair, wrote:
> //
>
> Hi,
>
> I was able to reproduce the problem in a sample application. I've
> created an issue [1] and shared the sample app [2]
>
> Please let me know if you need more information.
>
> Erik
>
> [1] https://i
//
Hi,
I was able to reproduce the problem in a sample application. I've
created an issue [1] and shared the sample app [2]
Please let me know if you need more information.
Erik
[1] https://issues.apache.org/jira/browse/ISIS-2269
[2] https://github.com/erikdehair/ISIS-2269
On 1/17/20 11:3
Hi,
We have an order form (view model) with some collection defined as
@Collection()
@CollectionLayout(named = "Routed subnet(s)")
@Getter @Setter
private List routedSubnetsPC;
When I call the following method on an integration test I get an exception:
getWrapperFactory().wrap(orderForm).getRo
