The problem was that CKEditor determines via a ‘conditional compilation’ whether the current browser is Internet Explorer or another one.
The CKEditor code (found in env.js) looked like this:

ie		: /*@cc_on!@*/false

In our case, when we used IE, this flag was always false which was incorrect. It should have been set to true via the ‘conditional compilation’: @cc_on!

By default (Deployment mode) Wicket sets the javascript compressor to the DefaultJavascriptCompressor. This compressor is responsible for stripping all comments and whitespaces (in Development mode it is set to null).
This is done in the Application class:

getResourceSettings().setJavascriptCompressor(new DefaultJavascriptCompressor());

While developing we have set Wicket in debug mode. On our demo server this is turned off ofcourse. This means that in debug mode the javascript files were not compressed and not stripped from the comments and whitespaces. In deployment mode it was compressed and stripped.

Wicket stripped out the conditional compilation (!!) to:

ie		: false

This was the reason why it wasn’t working in Internet Explorer.

To fix this don’t use the JavascriptResourceReference to add the ckeditor.js file but use a normal ResourceReference instead. The ckeditor.js is already compressed out-of-the-box.

Note: We used CKEditor 3.6.2 in combination with Wicket 1.4.18
Note 2: More information about ‘conditional compilation’ can be found here.

Click on Continue reading to see the solution.

Open your network preferences, select Advanced and select the tab DNS. Add the following two addresses: 208.67.220.220 and 208.67.222.222 (OpenDNS).

Decrease a field

$myCollection->update(array('_id' => new MongoId($myId)),
array('$inc' => array('item.inStock' => -1)
));

Note: the negative value (-1) of the ‘item.inStock’ field.

Increment / decrease multiple fields at once

$myCollection->update(array('_id' => new MongoId($myId)),
array('$inc' => array(
'item.inStock' => -1,
'item.sold' => 1)
));

Return specific fields

$myCollection->findOne(array('_id' => new MongoId($id)), array('colors'));

This will get one item from the database with the given $id. The result will be the unique mongoId and the ‘colors’ field. So not only the expected ‘colors’ field. Other fields are not returned.

‘Not in’

$query = array(
			"_id" => array('$nin' => $ninArray),
			"item.inStock" => array('$gt' => 0)
		);
$offerCollection->find($query);

This examples will return all items which id is not in the $ninArray and item.inStock > 1

Enjoy!

getRequestCycleSettings().setGatherExtendedBrowserInfo(true);

This method works via a redirect to the BrowserInfoPage and finally it goes to your ‘original’ page. Because of this it is possible that you see the BrowserInfoPage very shortly especially on slow computers/browsers or internet connections. But what if you don’t want this and only want to know whether Javascript is enabled? Please read on…

When the page is rendered it does a call(back) to Wicket. If this callback is possible then we can assume Javascipt is enabled.

How to setup?

e.g. Login.java (Page)

final WebClientInfo clientInfo = (WebClientInfo) WebRequestCycle.get().getClientInfo();
final AbstractDefaultAjaxBehavior behavior = new AbstractDefaultAjaxBehavior()
   @Override
   protected void respond(final AjaxRequestTarget target) {
        if (target != null) {
            clientInfo.getProperties().setJavaEnabled(true);
        }
   }
};
add(behavior);

Label jsEnabledScript = new Label("jsEnabledScript", "wicketAjaxGet('"+ behavior.getCallbackUrl() +"', function() { }, function() { });");
jsEnabledScript.setEscapeModelStrings(false); // do not HTML escape JavaScript code
add(jsEnabledScript);

And in your HTML

<script type="text/javascript" wicket:id="jsEnabledScript"></script>

How to use?

final WebClientInfo clientInfo = (WebClientInfo) WebRequestCycle.get().getClientInfo();
boolean javascriptEnabled = clientInfo.getProperties().isJavaEnabled();

Keep in mind that all Wicket validations will be validated, so we have to take care of the FeedbackPanel (refreshing) as well.

Example:

/**
	 * {@inheritDoc}
	 */
	@Override
	protected WebMarkupContainer newLink(String linkId, final int index) {

			return new AjaxSubmitLink(linkId, m_form) {

			@Override
			protected void onSubmit(AjaxRequestTarget target, Form<?> form) {
				setSelectedTab(index);
				if (target != null) {
					target.addComponent(TabbedComponent.this);
				}
				onAjaxUpdate(target);
			}

			@Override
			protected void onError(AjaxRequestTarget target, Form<?> form) {
				target.addComponent(((FeedbackAware) getPage()).getFeedbackPanel());
			}
		};
	}

See also my other blog about the AjaxTabbedPanel and LazyLoading

What I want to achieve is that an AjaxIndicator (loading image) will be shown on the place were the actual panel will come till it is completely loaded. Especially when you have a lot of components to render this can be handy. See image below.

Example

My solution was to create a class (AbstractLazyLoadTab) on top of the AbstractTab (implements ITab) which will take care of this. It will use the AjaxLazyLoadPanel.

public abstract class AbstractLazyLoadTab extends AbstractTab {
         //removed some lines

	@Override
	public Panel getPanel(String panelId) {
		return new AjaxLazyLoadPanel(panelId){

			private static final long serialVersionUID = 1L;

			@Override
			public Component getLazyLoadComponent(String markupId) {
				return getLazyLoadPanel(final String markupId);
			}
		};
	}

        public abstract Panel getLazyLoadPanel(final String markupId);
}

Now you can use this class as you normally would do when you use AbstractTab.

When your page (or components higher in the hierarchy) implements IAjaxIndicatorAware to show another loading layer it is possible that you now have two loading layers on top of each other. One on the tab and one which will e.g. block the whole page. To avoid that I created an other class which extends the AjaxTabbedPanel and implements the IAjaxIndicatorAware interface.

public class TabbedComponent extends AjaxTabbedPanel implements IAjaxIndicatorAware{
         //removed some lines
        @Override
	public String getAjaxIndicatorMarkupId() {
		//Our tab will take care of the loading layer, so return null.
		return null;
	}
}

Now you can use the classes like this:

  List<ITab> tabs=new ArrayList<ITab>();
    tabs.add(new AbstractLazyLoadTab(new Model("first tab")) {
        public Panel getLazyLoadPanel(String panelId) {
           return new TabPanel1(panelId);
        }
    });

    add(new TabbedComponent("tabs", tabs)

Another solution

If you prefer to have a waiting icon on the right side of the tab itself, you can override the newLink method of AjaxTabbedPanel and use the IndicatingAjaxFallbackLink instead of the AjaxFallbackLink. You will probably have to add the following code to your css file.

span.wicket-ajax-indicator {
float: left;
}

More information about this solution please click here