[GitHub] wicket issue #235: Wicket 6105 java.time

2017-10-16 Thread solomax 
Github user solomax commented on the issue:

https://github.com/apache/wicket/pull/235
  
Hello All,

Are we happy with these changes? Is it time to merge? :)


---

WICKET-6481

2017-10-16 Thread Andrea Del Bene 
Hi,

this issue is caused by a problem with mounted entities (pages, resources,
packages). If the path we use starts with segments from IMapperContext the
corresponding mapper is not resolved. For example a page mounted to
'page/foo' is handled with a PageInstanceMapper and not with its
MountedMapper.
What should we do? Should we check the path  when we mount it and rise an
exception if it is not compatible with IMapperContext?

Andrea.

Re: WICKET-6481

2017-10-16 Thread Maxim Solodovnik 
I see no options other than check on startup

On Mon, Oct 16, 2017 at 10:35 PM, Andrea Del Bene 
wrote:

> Hi,
>
> this issue is caused by a problem with mounted entities (pages, resources,
> packages). If the path we use starts with segments from IMapperContext the
> corresponding mapper is not resolved. For example a page mounted to
> 'page/foo' is handled with a PageInstanceMapper and not with its
> MountedMapper.
> What should we do? Should we check the path  when we mount it and rise an
> exception if it is not compatible with IMapperContext?
>
> Andrea.
>



-- 
WBR
Maxim aka solomax