for (Behavior behavior : widgetPanel.getBehaviors()) {
if (behavior instanceof AjaxSelfUpdatingTimerBehavior) {
((AjaxSelfUpdatingTimerBehavior) behavior).stop();
}
}
if (refreshTime > 0) {
widgetPanel.add(new AjaxSelfUpdatingTimerBehavior(Duration.seconds(refreshTime)));
}
There are two things to have in mind:
TextField<String> textField = new TextField<String>("txtValue",
new PropertyModel<String>(this, "objectModel"));
When we put a value in our text field, on submit we get : "is not a valid Serializable" error. That shows us Wicket 1.5 does not know that String declaration in our case is a Serializable type. To make models accept a general type , we should now create also the converter used by the component to specify the class type:TextField<String> textField = new TextField<String>("txtValue",
new PropertyModel<String>(this, "objectModel")) {
@Override
public <C> IConverter<C> getConverter(Class<C> type) {
return new AbstractConverter() {
public Object convertToObject(String value, Locale locale) {
return value;
}
@Override
protected Class getTargetType() {
return String.class;
}
};
}
public static Report loadReport(String xml) throws LoadReportException { ... }
public static Report loadReport(InputStream is) throws LoadReportException { ... }
public interface ReportListener {
public void onFinishRun(ReportResultEvent result);
}
Our ReportService will manage report listeners for current logged user:public void addReportListener(ReportListener reportListener) {
reportListeners.put(SecurityUtil.getLoggedUsername(), reportListener);
}
public void removeReportListener() {
reportListeners.remove(SecurityUtil.getLoggedUsername());
}
public void notifyReportListener(ReportResultEvent event) {
ReportListener reportListener = reportListeners.get(event.getCreator());
if (reportListener != null) {
reportListener.onFinishRun(event);
}
}
When the process is finished we will create the event and we will notify all listeners:ReportResultEvent event = new ReportResultEvent(...); reportService.notifyReportListener(event);To use jGrowl in Wicket it's easy with an AjaxBehavior. Messages will be kept in Session FeedbakMessages list.
public class MessageAjaxBehavior extends AbstractDefaultAjaxBehavior {
public void renderHead(IHeaderResponse response) {
super.renderHead(response);
response.renderJavascriptReference(
new JavascriptResourceReference(MessageAjaxBehavior.class, "jquery.jgrowl.js"));
response.renderCSSReference(
new CompressedResourceReference(JGrowlAjaxBehavior.class, "jquery.jgrowl.css"));
response.renderCSSReference(
new CompressedResourceReference(JGrowlAjaxBehavior.class, "jgrowl.css"));
String feedback = renderFeedback();
if (!StringUtils.isEmpty(feedback)) {
response.renderOnDomReadyJavascript(feedback);
}
}
protected void respond(AjaxRequestTarget target) {
String feedback = renderFeedback();
if (!StringUtils.isEmpty(feedback)) {
target.appendJavascript(feedback);
}
}
.......
}
Rendered feedback message contains the jgrowl javascript text. Message can be sticky to live until user close it, or it can have a time-elapsed life using life with a millisecond value.$.jGrowl("message",
{
theme: 'css-class',
sticky: true // life: 5000
}
)
All options of jGrowl can be found here. Label messageLabel = new Label("message", "");
messageLabel .setOutputMarkupId(true);
messageLabel .add(new MessageAjaxBehavior());
And we will initialize push service:
protected void onInitialize() {
super.onInitialize();
initPush();
reportService.addReportListener(new ReportListener() {
public void onFinishRun(ReportResultEvent result) {
if (pushService.isConnected(pushNode)) {
// forward the Message event via the push service
// to the push event handler
Message message = createMessage(result);
pushService.publish(pushNode, message);
}
}
});
}
private void initPush() {
// instantiate push event handler
IPushEventHandler handler = new AbstractPushEventHandler() {
public void onEvent(AjaxRequestTarget target, Message event,
IPushNode node, IPushEventContext context) {
getSession().getFeedbackMessages().add(
new FeedbackMessage(null, event.getText(), messageType));
target.addComponent(messageLabel);
}
};
// obtain a reference to a Push service implementation
pushService = TimerPushService.get();
// install push node into this panel
pushNode = pushService.installNode(this, handler);
}
-Dnext.datasource=Demo -Dnext.report=Timesheetit will make your designer on start to auto-connect to Demo data source and to automatically open Timesheet report.
-Dnext.datasource=Demo -Dnext.report=Timesheet -Dnext.path=/Test/Test1Path is converted to use specific file system separator, so you can enter it as you wish (/Test/Test1, Test/Test1, Test//Test1, \\Test\\Test1, Test\\Test1, \Test\Test1).
<server_data_source_name>@<server_ip>Designer will auto-connect to this data source and the report/chart is downloaded. If a report/chart with the same name exists, user is notified:
nextreports://<server>?user=<loggeduser>&ver=<serverversion>&ref=<serverpathtoentity>This can also be a simple method to pass to someone a report to edit. If that person can access the report (has the needed rights) you do not need to tell him the server, location and let him download the report, modify it and publish it back. You just give him an url.
gconftool-2 -t string -s /desktop/gnome/url-handlers/nextreports/command
'<installed_dir>/nextreports "%s"'
gconftool-2 -s /desktop/gnome/url-handlers/nextreports/needs_terminal false -t bool
gconftool-2 -s /desktop/gnome/url-handlers/nextreports/enabled true -t bool
-Djetty.class.path=C:/Users/user.name/.nextserver/reports
http://<ip>:<port>/reports/<report_file>For Jetty server used by default, there is a contexts folder where you installed the server.
which tell us that reports found at “resourceBase” on the hard disk can be served by the web server’s “contextPath”./reports C:/Users/user.name/.nextserver/reports/
'A' to 'Z' and from 'a' to
'z' are interpreted as pattern letters representing the
components of a date or time string.
Text can be quoted using single quotes (') to avoid
interpretation.
"''" represents a single quote.
All other characters are not interpreted; they're simply copied into the
output string during formatting or matched against the input string
during parsing."2012-01-04T23:59:59.999+02:00Taking forward to create the pattern for such a String results in:
yyyy-MM-dd'T'HH:mm:ss.SSSZNote that we need T not to be a pattern letter, so we unquoted it. We may think everything it's ok. If we need just to show a nice formatted date, we may not even see the difference. But if we want to use date formatted strings for some business, for example to do a Jackrabbit search of entities between two dates, we will found out (not easily) that the pattern is wrong.
2012-01-04T23:59:59.999+0200Because we cannot use a SimpleDateFormat string, we must use Jackrabbit api to format dates:
Calendar cal = Calendar.getInstance(); cal.setTime(date); String formattedDate = ValueFactoryImpl.getInstance().createValue(cal).getString();
<bean id="myBean" class="com.mypackage.MyClass">
<property name="myProperty">
<value>${propertyValue}</value>
</property>
</bean>
<bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> <property name="location"> <value>classpath:myfile.properties</value> </property> </bean>
<bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> <property name="location"> <value>classpath:myfile.properties</value> </property> <property name="systemPropertiesModeName"> <value>SYSTEM_PROPERTIES_MODE_OVERRIDE</value> </property> </bean>
<bean id="settings" class="com.mypackage.SettingsBean"> <property name="storageService" ref="storageService"></property> </bean>
public class SettingsBean {
private StorageService storageService;
public Settings getSettings() {
return storageService.getSettings();
}
@Required
public void setStorageService(StorageService storageService) {
this.storageService = storageService;
}
// helper methods used in Spring with SpEL
public String getPropertyValue() {
Settings settings = getSettings();
return settings.getPropertyValue();
}
}
<bean id="myBean" class="com.mypackage.MyClass">
<property name="myProperty" value="#{settings.getPropertyValue()}"/>
</bean>
<bean id="schedulingTaskExecutor"
class="org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor">
<property name="threadNamePrefix" value="Scheduler-"/>
<property name="corePoolSize" value="#{settings.getSchedulerCorePoolSize()}"/>
<property name="maxPoolSize" value="#{settings.getSchedulerMaxPoolSize()}"/>
<property name="queueCapacity" value="#{settings.getSchedulerQueueCapacity()}"/>
</bean>