[
https://issues.apache.org/jira/browse/WICKET-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444283#comment-13444283
]
Andrea Del Bene commented on WICKET-4697:
-----------------------------------------
I've tried the 2 quickstarts and I didn't see any difference betwenn Wicket
1.4 and 1.5. They both leave unchanged the src attribute of the component. The
problem seems to be related to the different URL generated by the two version
of Wicket. Version 1.5 add a segment for the namespace (which is 'wicket' by
default) while the URL of version 1.4 points directly to the application's
root.
I've tried to run the example for 1.4 mounting the test page on a path with
more than two segment ('foo/bar') and the problem is same as with Wicket 1.5
> Autolinking not working as soon as component gets a wicket:id
> -------------------------------------------------------------
>
> Key: WICKET-4697
> URL: https://issues.apache.org/jira/browse/WICKET-4697
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.7
> Reporter: Matthias Keller
> Attachments: WICKET-4697.zip
>
>
> While migrating from 1.4.X, we encounter a lot of pages having an image with
> a relative URL set in the HTML, for example <img src="img/logo.gif"/>.
> Now on some pages, those images need to be references, mainly to alter the
> visibility logic or add an attribute modifier of some kind. Now as soon as we
> do
> <img wicket:id="logo" src="img/logo.gif"/>
> and add it using add(new WebMarkupContainer("logo")) , autolinking does not
> work anymore and the src is left as-is.
> Moving all sources to the java files and use ContextImage etc is no real
> option as this would be a *lot* of work and wouldn't make the html readable
> anymore as it would become hard to find all references to the images and also
> isn't logical to have the URL in the java files even though it's static and
> doesn't change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
