Hi Christian,
I will look into the snapshot repository problems you mentioned. Thanks!
Regarding the limited API of J2ME: we are actually using this on an J2ME project, targeting MIDP 2.0 and CLDC 1.1. But I am pretty sure it would work for CLDC 1.0 as well.
One of the things that we currently had to do in order to support CLDC 1.1 is to avoid ArrayList, LinkedList - well, basically anything based on java.util.List. So whenever you have something like this:
<property name="foo">
<list>
<bean class="..."/>
<bean class="..."/>
</list>
</property>
... the framework injects a java.util.Vector instance. For Java SE, that would be a little awkward. So I am thinking about making the code generation dependent on the platform you are targeting. (Spring ME is also helpful in Java SE applications, for instance commandline tools in which pulling in the fat Spring runtime would be awkward.)
So, I hope this answers some of your questions. BTW, I like the things you have done. The concurreny utilities come in handy. Let's face it, there is a hell of a lot of stuff missing in Java ME. You are doing a great job making our lives less misserable. ;-)
Cheers,
Wilfred
Hi.
I saw your comment on my article on AgileAdvice, and went to look at SpringME, but found that the snapshot repository was giving errors, and I could not obtain it via Maven. Can you look into that?
The other thing I was thinking about was the fact that you have a dependency on the spring framework itself. While you may not use reflection in your code, spring itself is compiled against code that has a larger API set than is supported under some configurations of Java ME, such as CLDC. Have you tested your container against CLDC 1.1 (for example)? I'm curious, as I have a client, and though I wrote that container as a demo and they liked it, I'm happy to provide them with alternatives. However, it was built for their constraints, so before I go telling them of an alternative I want to make sure it will also satisfy those constraints. Those being that the library doesn't require JRE class library APIs that are not present in CLDC (such as Serializable).
cheers,
Christian.
P.S. Yes, the model of various profiles in J2ME is crap, but it's what they have to deal with, poor things... -cg.