Posted by: Marek | September 4, 2009

Signal Framework 0.3-beta

A new release of the Signal Framework is available and includes the following features:

  • a simple AOP framework based on proxies,
  • an MVC framework for MIDP and LWUIT APIs
Advertisements
Posted by: Marek | August 13, 2009

Signal Framework 0.3-beta coming soon

The new release is feature-complete. This new release includes the following features:

– a simple AOP framework based on proxies,

– an MVC framework for LWUIT and MIDP APIs.

The framework will be available on SF.net as soon as I update the documentation.

Posted by: Marek | May 1, 2009

Signal Framework 0.2-alpha released

This new release includes the following changes:

  • Updated documentation
  • Lazy initialization
  • Initializing beans
  • Context aware beans
Posted by: Marek | April 14, 2009

Signal Framework 0.2-alpha coming soon

A second release with new IoC features and updated documentation should be available in a week or so.

Posted by: Marek | April 6, 2009

Signal Framework 0.1-alpha released

This initial release contains an early version of a Spring-based IoC container for Java ME (J2ME). The distribution can be downloaded from SourceForge.

Posted by: Marek | April 5, 2009

Signal Framework documentation

The reference documentation (including the Javadocs) for the runtime IoC API is now available: http://docs.aurorasoftworks.com/signalframework/latest/reference/html/index.html

An alpha release of the framework itself should be available in several days.

Posted by: Marek | April 3, 2009

Update on the Signal Framework

The alpha release is almost ready. This initial release will only support a Spring based IoC container for J2ME (the MVC part has not been developed yet). I am working on the relevant documentation.

Posted by: Marek | March 24, 2009

Documentation tool

I am looking for a tool that could transform documentation stored in some generic format (e.g. XML) into multiple formats (single page HTML, multi page HTML, PDF). Any suggestions?

Posted by: Marek | March 24, 2009

Update on the Signal Framework for J2ME

The core component of the Signal Framework is an IoC container based on Spring. Spring itself is too heavyweight for Java ME and relies heavily on reflection, which is very limited in the CLDC 1.1 API (you can only create classes by invoking a no-arg ctor; there is no way to invoke methods or access attributes).

Signal attempts to overcome those limitations while retaining compatibility with the Spring IoC container. Signal reads Spring configuration files and generates Java classes that act as context factories without relying on XML parsing or introspection. The generation of context factories is normally executed as part of a build process of a Java ME application. That way you get the benefits of IoC on mobile devices and can still take advantage of existing Spring tools and skillsets.

Note that currently the implementation is limited to basic functionality of the IoC container without features like AOP, events or lazy initialization. An alpha release should be available on SourceForge in a week or two.

Even tough CLDC and MIDP applications need to be compiled to Java 1.3, it is often convenient to compile the test code with different settings so that Java features like annotations or generics can be used in test cases. The following example shows how to achieve that:

<build>

<plugins>

<plugin>

<artifactId>maven-compiler-plugin</artifactId>

<executions>

<execution>

<id>compile</id>

<phase>compile</phase>

<goals>

<goal>compile</goal>

</goals>

<configuration>

<source>1.3</source>

<target>1.3</target>

<compilerArguments>

<bootclasspath>

${settings.localRepository}/org/microemu/cldcapi11/${j2me.version}/cldcapi11-${j2me.version}.jar${path.separator}${settings.localRepository}/org/microemu/midpapi20/${j2me.version}/midpapi20-${j2me.version}.jar

</bootclasspath>

</compilerArguments>

</configuration>

</execution>

<execution>

<id>test-compile</id>

<phase>process-test-sources</phase>

<goals>

<goal>testCompile</goal>

</goals>

<configuration>

<source>1.6</source>

<target>1.6</target>

</configuration>

</execution>

</executions>

</plugin>

</plugins>

</build>


Note that the testCompile goal needs to be bound to the process-test-sources rather than test-compile, otherwise it will not work correctly (tested with Maven 2.0.9). This seems to be a bug in Maven.

« Newer Posts - Older Posts »

Categories