I thought I would throw out a few I found. I must say I am super excited about the inclusion of the j2me client lib.
Here is one "bug" I noticed so far in the J2ME Client Guide p.14
1
2
3
4
5
6
| private void initializeClientManager() {
clientMgr = new JMEClientManager("ChatTest", new JMEDiscoverer(this.getAppProperty("XML-Discovery-URL")),
this.getAppProperty("UsrMgrClassName"));
clientMgr.setListener(this);
clientMgr.discoverGames();
} |
Needs to be changed to:
1
2
3
4
5
6
| private void initializeClientManager() {
clientMgr = new JMEClientManager("ChatTest", new JMEDiscovererImpl(this.getAppProperty("XML-Discovery-URL")),
this.getAppProperty("UsrMgrClassName"));
clientMgr.setListener(this);
clientMgr.discoverGames();
} |
Pretty minor, but not sure if this is how you intended it to work or not. Also, the source for the J2ME chat client is in the docs, but not provided in source form like the other example clients. Again, no big deal
Other than this, I was able to successfully build a J2ME client that can connect and transfer data to the server.
Another thing that may or may not be a bug. It could be my misunderstanding of the discovery service. EA2 clearly creates a discovery.xml after it boots, and it appears to contain accurate information. The notes and documentation kind of imply that the discovery service is built into the new build, and I think that it implies that the discovery.xml would be available via http. Either I can't figure out where it is listening or I am mistaken. I just took the discovery.xml that was generated and threw it on Apache as a workaround.
