public String[] getSuggestions(String txt){
	String[] suggestions =  new String[]{};

	FullTextSession fullTextSession = Search.getFullTextSession(sf.getCurrentSession());
	SearchFactory searchFactory = fullTextSession.getSearchFactory();
	IndexReader reader = searchFactory.getIndexReaderAccessor().open(MyEntity.class);
	try {
		FSDirectory spellCheckerDir = FSDirectory.open(new File("D:\\lucene\\spellchecker\\com.site.model.MyEntity"));
		SpellChecker spellChecker = new SpellChecker(spellCheckerDir);
		Dictionary dictionary = new LuceneDictionary(reader, "description");
		IndexWriterConfig config = new IndexWriterConfig(Version.LUCENE_35, searchFactory.getAnalyzer("myAnalyzer"));
		spellChecker.indexDictionary(dictionary, config, true);
		suggestions = spellChecker.suggestSimilar(txt, 10);
	} catch (Exception e) {
		e.printStackTrace();
	}
	finally{
		searchFactory.getIndexReaderAccessor().close(reader);
	}
	return suggestions;
}

sf.getCurrentSession() gets standard Hibernate session. If you use EntityManager, there exists a method to obtain FullTextSession.
The example creates new index directory dedicated to spell checking. It adds terms from MyEntity’s description field to the index. spellChecker.indexDictionary adds the terms to the index, and optionally merges it with existing index.

portlet.xml should look like

<portlet>
	<description>wickettest4</description>
	<portlet-name>wickettest4</portlet-name>
	<display-name>wickettest4</display-name>
	<portlet-class>org.apache.wicket.portlet.WicketPortlet</portlet-class>
	<init-param>
		<name>wicketFilterPath</name>
		<value>/bla</value>
	</init-param>
	<supports>
		<mime-type>text/html</mime-type>
		<portlet-mode>VIEW</portlet-mode>
	</supports>
	<portlet-info>
		<title>wickettest4</title>
		<keywords>wickettest4</keywords>
	</portlet-info>
</portlet>

Note new portlet-class. Also, mime-type have to be text/html.

web.xml also changed, notice filter class:

<filter>
	<filter-name>wicket.wicket</filter-name>
	<filter-class>org.apache.wicket.portlet.PortletFilter</filter-class>
	<init-param>
		<param-name>applicationClassName</param-name>
		<param-value>org.wicket.WicketApplication</param-value>
	</init-param>
</filter>
<filter-mapping>
	<filter-name>wicket.wicket</filter-name>
	<url-pattern>/bla/*</url-pattern>
	<dispatcher>REQUEST</dispatcher>
	<dispatcher>INCLUDE</dispatcher>
	<dispatcher>FORWARD</dispatcher>
</filter-mapping>

And of course Maven dependencies also changed:

<dependency>
	<groupId>org.apache.wicket</groupId>
	<artifactId>wicket-core</artifactId>
	<version>${wicket.version}</version>
</dependency>
<dependency>
	<groupId>org.apache.portals.bridges</groupId>
	<artifactId>portals-bridges-common</artifactId>
	<version>2.0</version>
</dependency>
<dependency>
	<groupId>org.wicketstuff</groupId>
	<artifactId>wicketstuff-portlet</artifactId>
	<version>${wicket.version}</version>
</dependency>

<dependency>
	<groupId>org.jboss.as</groupId>
	<artifactId>jboss-as-controller-client</artifactId>
	<version>7.0.2.Final</version>
</dependency>

The following example creates new datasource:

public void createDatasource() throws Exception{
	ModelNode request = new ModelNode();
	request.get(ClientConstants.OP).set(ClientConstants.ADD);
	request.get(ClientConstants.OP_ADDR).add("subsystem",
			"datasources");
	request.get(ClientConstants.OP_ADDR).add("data-source",
			"java:jboss/datasources/NewDatasource");

	request.get("jndi-name").set("java:jboss/datasources/NewDatasource");
	request.get("connection-url").set("jdbc:as400://1.2.3.4/SCHEME");
	request.get("driver-class").set("com.ibm.as400.access.AS400JDBCDriver");
	request.get("driver-name").set("jt400.jar");
	request.get("user-name").set("username");
	request.get("password").set("password");
	request.get("pool-name").set("pool_NewDatasource");

	ModelControllerClient client = ModelControllerClient.Factory.create(
			InetAddress.getByName("127.0.0.1"), 9999);
	client.execute(new OperationBuilder(request).build());
}

If you want to check if the datasource already exists, consider following snippet:

public boolean checkIfDatasourceExists() throws Exception {
	ModelNode request = new ModelNode();
	request.get(ClientConstants.OP).set("read-resource");
	request.get("recursive").set(false);
	request.get(ClientConstants.OP_ADDR).add("subsystem", "datasources");

	ModelControllerClient client = ModelControllerClient.Factory.create(
			InetAddress.getByName("127.0.0.1"), 9999);
	ModelNode responce = client.execute(new OperationBuilder(request).build());

	ModelNode datasources = responce.get(ClientConstants.RESULT).get("data-source");

	if (datasources.isDefined()) {
		for (ModelNode dataSource : datasources.asList()) {
			String dataSourceName = dataSource.asProperty().getName();
			if (dataSourceName.equals("java:jboss/datasources/NewDatasource")) {
				return true;
			}
		}
	}
	return false;
}

The examples have the same effect as trying to add datasource from Jboss Administration console.

One way to solve these problems and clean the Eclipse is using -clean argument.
all you need to do is to edit the eclipse.ini file located in your <Eclipse install directory> and add it as the first argument on the first line.
After you upload the eclipse you can delete it until the next time you will need it.

<subsystem xmlns="urn:jboss:domain:web:1.0" default-virtual-server="default-host">
    <configuration>
        <jsp-configuration development="true"/>
    </configuration>
    ...
</subsystem>

And now JBoss behaves as you expect it in development mode: all changes to JSP files are loaded automatically as soon as you change the JSP file.

<meta name="viewport" content="target-densitydpi=device-dpi, width=device-width, height=device-height, initial-scale=1.0" />

You can add additional CSS file that will be used on mobile device only. To achieve this just add CSS media type. In Android developer’s guide at http://developer.android.com/guide/webapps/targeting.html it suggests to target device DPI value like:

<link rel="stylesheet" href="css/mobile.css" type="text/css" media="screen and (-webkit-device-pixel-ratio:1.0)" />

It works fine, but Google Chrome on desktop PC also loads this CSS file.

There is another solution to target mobile devices (both Android, iPhone, Blackberry): to specify maximal width of the screen like:

<link rel="stylesheet" href="css/mobile.css" type="text/css" media="screen and (max-device-width:801px) and (max-width:801px)" />

The problem is that Android (at least 2.3 I’ve tested) recognizes this media type only after page reloading (refreshing) in browser. Googling the web I found the open issue.
I solved it using JavaScript:

if(isMobile){
	var cssLink = document.createElement("link");
	cssLink.setAttribute("type", "text/css");
	cssLink.setAttribute("rel", "stylesheet");
	cssLink.setAttribute("href", "css/mobile.css");
	document.head.appendChild(cssLink);
}

I tested it on my device an it works fine, unless some little delay: the CSS file loads only after JavaScript executes. When google will fix the issue (I hope so…), there will be no delay, since original link is in the HEAD section.

Of course you have to detect mobile device using the JavaScript, I used solution suggested here: http://localstreamer.posterous.com/javascript-code-snippet-how-to-detect-all-mob

After trying do deploy JDBC driver with jboss-as maven plugin using following code in pom.xml I received the NullPointerException in Maven build.

Here is part of maven pom.xml used to deploy the driver to jboss:

					<plugin>
						<groupId>org.jboss.as.plugins</groupId>
						<artifactId>jboss-as-maven-plugin</artifactId>
						<version>7.0.1.Final</version>
						<executions>
							<execution>
								<id>deploy-driver-AS400</id>
								<phase>package</phase>
								<goals>
									<goal>deploy-artifact</goal>
								</goals>

								<configuration>
									<hostname>${jboss-hostname}</hostname>
									<groupId>com.ibm</groupId>
									<artifactId>as400</artifactId>
									<fileName>jt400.jar</fileName>
									<name>jt400.jar</name>
								</configuration>
							</execution>

						</executions>
					</plugin>

In the plugin’s manual at http://docs.jboss.org/jbossas/7/plugins/maven/latest/examples/deployment-example.html it said

The artifact must be already listed as a dependency in the projects pom.xml

but it do not tells in which scope the driver’s JAR have to be: it have to be in compile or runtime scope in order to work. I had it in provided scope. After changing the scope of dependency it works fine.

Here is full stacktrace of the error I received:

[ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.0.1.Final:deploy-artifact (deploy-driver-AS400) on project project-ear: Execution deploy-driver-AS400 of goal org.jboss.as.plugins:jboss-as-maven-plugin:7.0.1.Final:deploy-artifact failed. NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.0.1.Final:deploy-artifact (deploy-driver-AS400) on project project-ear: Execution deploy-driver-AS400 of goal org.jboss.as.plugins:jboss-as-maven-plugin:7.0.1.Final:deploy-artifact failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution deploy-driver-AS400 of goal org.jboss.as.plugins:jboss-as-maven-plugin:7.0.1.Final:deploy-artifact failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:116)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.NullPointerException
at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:191)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
... 20 more

public enum ActionTypeEnum {
	UPDATE,
	CREATE,
	COPY
}

In JSF you can write EL expressions in form:

<h:outputText value="someText"
	rendered="#{listAction.actionType == 'COPY'}"/>

The property actionType in managed bean listAction have to be of type ActionTypeEnum.

It works because each enum in have method valueOf(String stringValue) and JSF attempts to convert String value to enum.