On 6 January 2014 14:55, Chohan, Dharmesh <[email protected]> wrote:
> Hi Dan > could you subscribe to this mailing list, Dharmesh? Otherwise, I have to explicitly approve your postings. > > I have got following queries regarding ISIS to what I am trying to achieve. > > > 1. Some of the screens are generated with default titles and links, > e.g. How can I customise the text what is generated. Also how do I > customise the “OK” button. Basically I want to change the “123456789002 > 25-02-2014” and “General” title names. > > > > > > Use either @Title or title() http://isis.apache.org/applib-guide/how-tos/how-to-01-040-How-to-specify-a-title-for-a-domain-entity.html > > 1. I have got a scenario where I want to pass a parameter to a message > or a @Named annotation so that the message is built dynamically. > > > Example: “You have [items?] in the basket”. Items is a variable > parameter. > > I'm not certain what you mean by "message", but from the example you've given I'm guessing this is essentially a read-only property (ContentsSummary) of the entity (ShoppingBasket) that you want to display to the user. If so, you could do: public class ShoppingBasket { // a persisted collection private SortedSet items = ...; // the derived property public String getContentsSummary() { return "You have " + items.size() + " in the basket"; } } ~~~ To suppress the label for this property you could experiment with using the CssClass annotation along with a custom CSS styles in your app.css (under WEB-INF of your application), eg: public class ShoppingBasket { ... @CssClass("suppress-label") public String getContentsSummary() { return "You have " + items + " in the basket"; } } app.css: .suppress-label > some > appropriate > selectors { display: none; } There are other, deeper, integrations (specifically: writing a custom Wicket Component) if this doesn't work as you need. As a general remark, though, as I understand your application architecture, you intend to build a bespoke JSF UI and access this domain model via Restful. So it probably doesn't make sense to do too much integration of the default UI provided by the Wicket viewer. Conversely, I would recommend you start spiking your JSF UI and using the RO API... this is probably your biggest unknown/risk area for you. HTH Dan > Thanks > Dharmesh > > > > >
