request.setAttribute("myVar", "value1");

Now in the host page use scriptlet to populate the Javascript Key value pair:

<%
String myVar = "";
myVar= (String)request.getAttribute("myVar");

%>

<script language=”javascript”>

var initParamList = { myVar: “<%myVar%>” };

</script>

Now this variable can be accessed in GWT application using dictionary.

Dictionary dict = Dictionary.getDictionary("initParamList");
String myVar = dict.get("myVar");

To use dictionary, following line needs to be added in gwt.xml file.

 <inherits name=”com.google.gwt.i18n.I18N”/>

"C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\xsd.exe" /c /edb /l:cs /n:"com.test" main.xsd /o:classes

It gives error which is similar to following :

Warning: Schema could not be validated. Class generation may fail or may produce incorrect results.

Error: Error generating classes for schema ‘Main’.
- The datatype ‘some datatype‘ is missing.

‘some datatype‘ is defined in one of imported schemas.

It happens due to the fact that schema location is optional and xsd.exe does not consider that.

To overcome this issue, all the xsd’s which are imported and used in the schema must be included in the command line while running xsd.exe. Something similar to following should work.

"C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\xsd.exe" /c /edb /l:cs /n:"com.test" main.xsd importedxsd1.xsd importedxsd2.xsd /o:classes

This will generate the classes from main.xsd.
main.xsd imports importedxsd1.xsd and importedxsd2.xsd.


import java.util.concurrent.Callable;
import java.util.concurrent.CompletionService;
import java.util.concurrent.ExecutorCompletionService;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;

} catch (InterruptedException e) {
e.printStackTrace();
}
return 1;
}
}


cs.take() waits till the task returns. Callable interface is similar to Runnable. The java docs for concurrent api describes it as :
The Callable interface is similar to Runnable, in that both are designed for classes whose instances are potentially executed by another thread. A Runnable, however, does not return a result and cannot throw a checked exception.

executor.submit can also be called with a Runnable instance task which will return a Future representing that task.

The directory structure is below, which is a very simple maven project structure.

Lets start with service bundle. I call it SumServiceBundle. I have defined an interface which has a single method sum.


package com.test;
public interface SumInterface {
public int sum(int i,int j);
}


The implementation of this interface in Sum.java.

package com.test.impl;
import com.test.SumInterface;
public class Sum implements SumInterface
{
public int sum(int i,int j){
return i+j;
}
}


Now I have to define the service description in spring files present in resources\META-INF\spring.
I have created two files simplesum.xml and simplesum-osgi.xml.

Contents of simplesum-osgi.xml are :
Contents of simplesum.xml are :

These two xml files describes the spring configuration of the bundle once it is deployed. simplesum-osgi.xml exports the simplesum as OSGI service.
One last step for creating the service is to create or generate the manifest file which provide the information about the OSGI bundle. I have kept manifest file at resources\META-INF\MANIFEST.MF.

MANIFEST.MF

Bundle-Version: 1.0
Bundle-SymbolicName: com.test
Bundle-Name: Simple-Sum-Service
Bundle-Vendor: Spring Framework
Export-Package: com.test
Bundle-ManifestVersion: 2
Import-Package: org.osgi.framework;version="1.3",org.springframework.beans.propertyeditors;version="2.5",org.springframework.osgi.service.importer,org.springframework.osgi.service.importer.support,org.xml.sax


Finally the maven pom.xml for this project.

<?xml version=”1.0″?><project>

<modelVersion>4.0.0</modelVersion>
<groupId>com.test.osgi</groupId>
<artifactId>sum-service-bundle</artifactId>
<packaging>jar</packaging>
<name>sum-service-bundle</name>
<version>1.1.2</version>

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
</archive>
</configuration>
</plugin>
</plugins>
</build>
</project>

running mvn clean install will create sum-service-bundle-1.1.2.jar in target folder which can be deployed on equinox.

Now the client. I call it SumServiceClient. When client starts, it calls the sum service. Client class implements BundleActivator.
SumClientActivator.java

package com.client;
import org.osgi.framework.BundleActivator;
import org.osgi.framework.BundleContext;
import org.osgi.util.tracker.ServiceTracker;
import com.test.SumInterface;


public class SumClientActivator implements BundleActivator {
private ServiceTracker finderTracker;


public void start(BundleContext context) throws Exception {
finderTracker = new ServiceTracker(context, SumInterface.class.getName(), null);
finderTracker.open();
SumInterface sumObj =(SumInterface)finderTracker.getService();
System.out.println("calling service");
System.out.println("Result :" +sumObj.sum(10,20));
}


public void stop(BundleContext context) throws Exception {
System.out.println(" Stopping ");
}
}


The Manifest is present in \resources\META-INF\MANIFEST.MF.
MANIFEST.MF

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Sum Client
Bundle-SymbolicName: SumClient
Bundle-Version: 1.0.0
Bundle-Activator: com.client.SumClientActivator
Import-Package: org.osgi.framework,com.test,org.osgi.util.tracker
version: "[1.0.0,2.0.0)"

Finally the pom.xml.

<?xml version=”1.0″?><project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.test.osgi</groupId>
<artifactId>sum-client-bundle</artifactId>
<packaging>jar</packaging>
<name>sum-client-bundle</name>
<version>1.1.2</version>
<dependencies>
<dependency>
<groupId>com.test.osgi</groupId>
<artifactId>sum-service-bundle</artifactId>
<version>1.1.2</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.eclipse</groupId>
<artifactId>osgi</artifactId>
<version>3.3.0-v20070530</version>
</dependency>
</dependencies>

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
</archive>
</configuration>
</plugin>
</plugins>
</build>
</project>

Final step is to run “mvn clean install” in both projects and place the bundles in equinox.  When client bundle starts it calls the service and prints result on the console.

An excellent introduction to OSGI by Neil bartlett is here

This will show the OSGI prompt. For getting help type ? or help.

Spring dynamic modules is available on this link.
Now for using spring dynamic modules, the equinox should be made aware of spring jars.This can be done using a simple configuration file. Create a file config.ini. I have placed this file in a directory named config on my system. In this file, all the spring related jar should be specified. The contents of my config.ini are following:

osgi.clean=true
eclipse.ignoreApp=true
osgi.bundles=springdm/aopalliance.osgi-1.0-SNAPSHOT.jar@start, \
springdm/api-0.9.5.jar@start, \
springdm/jcl104-over-slf4j-1.4.3.jar@start, \
springdm/log4j.osgi-1.2.15-SNAPSHOT.jar@start, \
springdm/service-0.9.5.jar@start, \
springdm/services-3.1.200-v20070605.jar@start, \
springdm/slf4j-api-1.4.3.jar@start, \
springdm/slf4j-log4j12-1.4.3.jar@start, \
springdm/spring-aop-2.5.5.jar@start, \
springdm/spring-beans-2.5.5.jar@start, \
springdm/spring-context-2.5.5.jar@start, \
springdm/spring-context-support-2.5.5.jar@start, \
springdm/spring-core-2.5.5.jar@start, \
springdm/spring-osgi-annotation-1.1.2.jar@start, \
springdm/spring-osgi-core-1.1.2.jar@start, \
springdm/spring-osgi-extender-1.1.2.jar@start, \
springdm/spring-osgi-io-1.1.2.jar@start, \
springdm/spring-tx-2.5.4.jar@start, \
springdm/jta-1.0.1.jar@start


I have created directory “springdm” and placed all the spring jars in that directory. Now during the startup, equinox will load all the jars.

To run equinox with configuration option, use following command :
java -jar org.eclipse.osgi_3.3.2.R33x_v20080105.jar -console -configuration config

config is the folder where I have kept config.ini. Now spring dynamic modules can be deployed on equinox.

While Most of the information is already available on mysql.com. Still I am just writing all the steps which I followed to make multiple mysql servers run on my machine. I have used the no installer version (mysql-noinstall-5.0.27-win32.zip).

1. Create two directories for server installation. For me it was c:\mysql1 and c:\mysql2

2. Unzip the package in both the directories.

3. Copy my-small.ini present in root directory with the name my.ini.

4. Change the following mysqld configuration in my.ini. For first instance:

[mysqld]
port = 3307
basedir="C:/mysql1/"
datadir="C:/mysql1/data/"

5. Repeat step 4 for second instance. Use the following values:

[mysqld]
port = 3308
basedir="C:/mysql2/"
datadir="C:/mysql2/data/"


Any other change is not required for simple configuration.

6. From the bin directory run the following command:

C:\mysql1\bin>mysqld ----console
C:\mysql2\bin>mysqld ----console

The servers will start in console mode. A window will open asking you to allow mysql to connect to the internet. Select ok.

7. Once the servers are started, use the following command to connect from client:

C:\mysql1\bin>mysql ----port=3307 -uroot
C:\mysql1\bin>mysql ----port=3308 -uroot


That’s it.

Follow the steps below to integrate tiles2 with spring mvc.

First the maven2 dependencies. Complete dependency set for my project.

<dependency>
<groupid>org.springframework</groupid>
<artifactid>spring</artifactid>
<version>2.5.5</version>
</dependency>

<dependency>
<groupid>org.springframework</groupid>
<artifactid>spring-webmvc</artifactid>
<version>2.5.5</version>
</dependency>

<dependency>
<groupid>org.hibernate</groupid>
<artifactid>hibernate</artifactid>
<version>3.2.5.ga</version>
</dependency>

<dependency>
<groupid>org.hibernate</groupid>
<artifactid>hibernate-entitymanager</artifactid>
<version>3.3.1.ga</version>
</dependency>

<dependency>
<groupid>org.hibernate</groupid>
<artifactid>hibernate-commons-annotations</artifactid>
<version>3.3.0.ga</version>
</dependency>

<dependency>
<groupid>hsqldb</groupid>
<artifactid>hsqldb</artifactid>
<version>1.8.0.7</version>
</dependency>

<dependency>
<groupid>concurrent</groupid>
<artifactid>concurrent</artifactid>
<version>1.3.4</version>
</dependency>

<dependency>
<groupid>javax.servlet</groupid>
<artifactid>jstl</artifactid>
<scope>runtime</scope>
<version>1.1.2</version>
</dependency>

<dependency>
<groupid>javax.servlet</groupid>
<artifactid>servlet-api</artifactid>
<version>2.5</version>
</dependency>

<dependency>
<groupid>taglibs</groupid>
<artifactid>standard</artifactid>
<scope>runtime</scope>
<version>1.1.2</version>
</dependency>

<dependency>
<groupid>commons-collections</groupid>
<artifactid>commons-collections</artifactid>
<scope>runtime</scope>
<version>3.2</version>
</dependency>

<dependency>
<groupid>org.apache.tiles</groupid>
<artifactid>tiles-core</artifactid>
<version>2.0.6</version>
</dependency>

<dependency>
<groupid>org.apache.tiles</groupid>
<artifactid>tiles-jsp</artifactid>
<version>2.0.6</version>
</dependency>

<dependency>
<groupid>org.apache.struts</groupid>
<artifactid>struts-tiles</artifactid>
<version>1.3.9</version>
<scope>runtime</scope>
</dependency>

Project structure is like any other maven based web project.

Web.xml -

<servlet>

<servlet-name>myapp</servlet-name>

<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>

<load-on-startup>1</load-on-startup>

</servlet>

<servlet-mapping>

<servlet-name>myapp</servlet-name>

<url-pattern>*.htm</url-pattern>

</servlet-mapping>

Now for integration of tiles2, I will have to make the application aware of tiles. This is done in myapp-servlet.xml. This is spring configuration file for spring mvc. The portion of file relevant for tiles is following:

<?xml version=”1.0″ encoding=”UTF-8″?>

<beans xmlns=”http://www.springframework.org/schema/beans” xsi=”http://www.w3.org/2001/XMLSchema-instance” schemalocation=”http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd”>

<bean id=”viewResolver” class=”org.springframework.web.servlet.view.UrlBasedViewResolver”>

<property name=”viewClass” value=”org.springframework.web.servlet.view.tiles2.TilesView”>
</bean>

<bean id=”tilesConfigurer” class=”org.springframework.web.servlet.view.tiles2.TilesConfigurer”>

<property name=”definitions”>

<list><value>/WEB-INF/tiles-def.xml</value></list>

</property>

</bean>

I have defined the controller mapping using SimpleUrlHandlerMapping.

Next step is to define tiles definition. I have added it in /WEB-INF/tiles-def.xml.

The contents of tiles-def.xml are following :

<?xml version=”1.0″ encoding=”ISO-8859-1″ ?><!DOCTYPE tiles-definitions PUBLIC
“-//Apache Software Foundation//DTD Tiles Configuration 2.0//EN”
“http://tiles.apache.org/dtds/tiles-config_2_0.dtd”>

<tiles-definitions><definition name=”template” template=”/WEB-INF/templates/layout.jsp”>

<put-attribute name=”title” value=”My Application”>

<put-attribute name=”header” value=”/WEB-INF/templates/header.jsp”>

<put-attribute name=”footer” value=”/WEB-INF/templates/footer.jsp”>

</definition>

<definition name=”test” extends=”template”>

<put-attribute name=”title” value=”test MyApp”>

<put-attribute name=”content” value=”/WEB-INF/jsp/test.jsp”>

</definition>

</tiles-definitions>

The controller of the application returns “test” ModelAndView.

public ModelAndView handleRequest(HttpServletRequest request,

HttpServletResponse response) throws ServletException, IOException {

return new ModelAndView(“test”);

}

When this model is returned it will be processed using tiles definitions and renders it as defined in the files.

Next step is to create the layout jsp’s. I have created all the layout files in WEB-INF/templates/ folder. I contains all the jsp’s defined in tiles-def.xml like layout.jsp, header.jsp, footer.jsp ..

Contents of layout.jsp

<%@ taglib uri=”http://tiles.apache.org/tags-tiles” prefix=”tiles”%>

<html>

<head></head>

<body>

<div id=”header”><tiles:insertattribute name=”header”></div>

<div id=”center”><tiles:insertattribute name=”content”></div>

<div id=”footer”><tiles:insertattribute name=”footer”></div>

</body>

</html>

I think these steps are only needed for tiles2 integration with spring mvc. If I have missed anything. Let me know.

]]> http://vivyzer.wordpress.com/2008/09/19/integrating-spring-mvc-tiles2-and-maven2/feed/ 0 vivyzer