the phone can now access a remote server (which is in toni’s laptop).

one problem in displaying is the appointments since they are quite long. in the emulator, it displayed properly however, in the phone, they were cut at the end of the string.

blog by celene navarro and toni trino

Konti na lang talga kulang. hopefully, we could test some of the project features on the application deployed in toni’s mobile phone  by today. Nagloloko kasi yung server kahapon. Anyway! We’re still keeping a positive outlook dahil we know we can do it.

Anyway, implementation details are as follows:

Only a few servlets remain to be finalized. Everything that has be done can communicate using SOAP and successfully supply the changes and requested data by the mobile client. One of the major issues right now is testing the audio part of the consultation since the emulator cannot perform the code successfully. However, when we last deployed it in toni’s phone, it worked! Choi is stil continuing modification of this part with regards to “slimming down” what the player can recognize. Right now, it recognizes various types of files in toni’s phone. These files include audio and video files. Tweaking is necessary. What is challenging here is we can only test if the audio part operates properly (can record and send data to the database) only when the server is up and running.

Malapit na ang finish line. sana we get there before it’s too late.

double time na!

- blog by celene navarro, toni trino and dennis paguio

dito mo na lang check toni

celene navarro

http://javaboutique.internet.com/tutorials/Axis/index.html

the server ip address set for our application once hosted by jrdc is 121.97.188.109

port 9000 shall be used for all transactions, so modifications in our application should be set to this port

celene navarro and toni trino

http://javaboutique.internet.com/tutorials/Axis2/

http://javaboutique.internet.com/tutorials/Axis/axis3.html

Tuloy tuloy na sana…

celene navarro

but my mobile phone returns a “javax.microedition.media.MediaException: Cannot create a DataSource for: null” after trying to create a player with:

Player p = Manager.createPlayer(“capture://audio”);

or Player p = Manager.createPlayer(“capture://audio?encoding=pcm&rate=8000&bits=8&Channels=1″);

or Player p = Manager.createPlayer(“capture://audio?encoding=pcm);

or Player p = Manager.createPlayer(“capture://audio?encoding=amr);

———————————————————————-

but after installing the application on a nokia n70 phone (my groupmate’s) , the

Player p = Manager.createPlayer(“capture://audio”);

and

new PlayerThread(new ByteArrayInputStream(byteArray), “audio/x-wav” ).start();

worked fine. so for now we will use the pcm encoding but amr encoding will be tested too.

i still don;t know why it doesn’t work with my phone.

-dennis paguio

The challenge now is figuring out what modifications to our current serverside code must be made in order to communicate with the new webservice client.

celene navarro

now..we are currently looking and studying webserver side codes..

toni trino

http://www.softwaremaker.net/webservices/swm/Convertor/Convertor.asmx?wsdl

we searched the net for some notes or help. luckily, we found a demo by mr. lukas hasik in his blog..

http://blogs.sun.com/lukas/entry/difference_between_wireless_connection_bridge

hopefully we could find a sample application that he used in his demo and use it as a basis for our project

celene navarro and toni trino