Craig, Thanks for the swift response.
On Sat, 2006-10-21 at 06:22 -0500, Craig Setera wrote: > There are a whole bunch of things that could go wrong. The fact that > you originally created the project outside of Eclipse is likely the > culprit though. My guess is that Eclipse isn't happy with the project > to start with... or that it didn't have the required Java nature on the > project. You should definitely be able to convert a *Java* project to a > Mildet suite. Another option would be to create a Midlet suite and then > import your previous project code into the project. I think I must have used "checkin" rather than "import", which probably meant it wasn't a Java project in the first place. In my rush to have something in place (I guess I am being a bit manic this morning), I failed to think (which would probably have led to me trying to "import" :-) and just manually created the .classpath, .project, JAD file with XEmacs and the check in the project again. The project now compiles and executes fine. All that remains is to find out why the program doesn't work, the infrastructure does. -- Russel. ==================================================== Dr Russel Winder +44 20 7585 2200 41 Buckmaster Road +44 7770 465 077 London SW11 1EN, UK [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
