Hi, need to use an XML file for localization in my application. However,
Wicket is just not recognizing an XML file for this.
I did the XML structure exactly like in the examples, proper UTF-8
encoding, proper doctype for Java properties. I copied the examples into a
newly created UTF-8 text file
Do your files have the correct suffix?
*.properties.xml
Sven
Michael M generi...@gmail.com schrieb:
Hi, need to use an XML file for localization in my application. However,
Wicket is just not recognizing an XML file for this.
I did the XML structure exactly like in the examples, proper UTF-8
Oh boy.. I somehow assumed that .properties is the file-extension for the
normal properties files, and .xml for XML files. So I overlooked the proper
naming-conventions.. sigh.
Thanks, woking now!
2012/8/24 Sven Meier s...@meiers.net
Do your files have the correct suffix?
*.properties.xml
We also have this problem after migrating to 1.5. Everything seems to work
ok, but the logs get full with this error. We did not find a solution to
this.
--
View this message in context:
Hi all,
Here is my use case: I need to fill variables, like {myVar}, that are rendered
into the page. My approach is to use a specialized IResponseFilter for that.
The important point is the filter should be applied to a certain Page of my
application, and more of that, the variable values are
Hi,
In Wicket 1.5.8 there is
org.apache.wicket.request.cycle.PageRequestHandlerTracker which you
can use to get the requested page and the response page. In your case
you need the latter.
PageRequestHandlerTracker.getLastHandler(cycle), then check whether it
is IPageRequestHandler and call
Where do these {myVar}s come from?
Sven
On 08/24/2012 03:32 PM, Guillaume Mary wrote:
Hi all,
Here is my use case: I need to fill variables, like {myVar}, that are rendered
into the page. My approach is to use a specialized IResponseFilter for that.
The important point is the filter should
This is the eighth maintenance release of the Wicket 1.5.x series. This
release brings over 45 bug fixes and improvements.
Git tag:
release/wicket-1.5.8
Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12321662
Maven:
dependency
Thanks Martin, it's easier to find the actual page with
PageRequestHandlerTracker.
Nevertheless, the redirecting case is still not filled because as I
debugged, PageRequestHandlerTracker returns null for both first and last
handler when my filter is called (am i wrong ??). That's almost the same
my {myVar}s comes from HTML, or even model of components
If these placeholders are in your HTML, why don't you just use an
AbstractTransformerBehavior to fill them?
Sven
On 08/24/2012 04:51 PM, guillaume.mary wrote:
Thanks Martin, it's easier to find the actual page with
Because I didn't know AbstractTransformerBehavior ! :)
Many thanks !
I put it on my Page instance so it fullfills the last case of post +
redirect (but the filter is still necessary for components refreshed by
Ajax, otherwise I should add AbstractTransformerBehavior to all components
of my Page)
11 matches
Mail list logo