On 5/4/06, Ralf Ebert <[EMAIL PROTECTED]> wrote:
Hi,
just tried the wicket localization features and got some questions:
- usually i have in the html things like this:
<h1><wicket:message key="xxx">headline</wicket:message></h1>
Is there a way that lets me write these like this:
<h1 wicket:message="xxx">headline</h1>
Which seems much more convenient...
please see WicketMessageTagHandler.java. It is experimental only and
disabled by default. Reason: it is realy ugly to have something like
wicket:example="tag=key". AttributeModifier are much more convinent
and far less ugly, IMO.
- Is there an easy "markup only" way to get messages in attribute
tags? For example,
<input type="submit" value="Do something"/>
see above. I'm not aware of any other solution.
- My application is grouped in modules and I want to have one property
file per module. From what I've seen it should be easy to implement a
custom StringResourceLoader which just looks for a specified property
file in the package and it's parent packages. Maybe this is something
which might come bundled with Wicket (I couldn't find anything)
because it helps a lot if you have a company translating things for
you and you can hand over 1 property file instead of 20 (one for each
page)?
That is default. Localizer implements a search hierarchy up the
component tree. You only need one properties files per language per
Panel which contains X number of component. Thinking ... That is not
your question, isn't it? Like Application.properties is the last
resort for all messages, you ask for one per java package, right? So,
in addition to the my.pkg.MyPanel.properties it should look in
my/pkg/Wicket.properties as well (may be Wicket.properties is not the
best name).
Something not localization related:
- In my application I need to open a transaction for every request
that's for a page (not for resources) and commit it (if sucessful) or
rollback it (in case of an runtime exception). I also want to use
Wicket's exception handling mechanism, that's why I won't use a
servlet filter. I currently implemented this by using my own
RequestCycleProcessor, which seems fine. But I needed to deactivate
wicket's exception handling (so the exception "bubbles" up to the
respond method and I can rollback) and dispatch into wicket's
exception handling again. Is there a better way to achieve this?
I leave that for someone else to answer
Juergen
Regards,
Ralf
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
