First, i tried org.apache.poi. It works in local but throw exception when i upload it to google app engine. Then i have to to JExcel, it works well till now.
step 1: setup your spring environment for your google app engine, please refer my previous article for this.
step 2: download jexcelapi, what i used is jexcelapi_2_6_12. Then copy jxl.jar into war/WEB-INF/lib/ and add it to build path.
step 3: configure web.xml to add spring configuration as below
NSDate *today = [[NSDate alloc] init]; NSDateComponents *offsetComponents = [[NSDateComponents alloc] init]; [offsetComponents setHour:1]; [offsetComponents setMinutes:30]; // Calculate when, according to Tom Lehrer, World War III will end NSDate *endOfWorldWar3 = [gregorian dateByAddingComponents:comps toDate:today options:0];
I have been inching to try out google app engine and its capabilities with "app engine + java + BlazeDS + Flex", it works well on my personal website. But "remote object data accessing" is not suitable for client platform like Iphone and Android. I happend find a great topic talking about "app engine + java + spring + REST + JSON", it does help me with my Planned Iphone preject.
The end product will be spring mvc app running in google app engine handling GET, POST, PUT and DELETE http requests with JSON objects in and out utilizing JDO and seesions. And you can access it from you Iphone App. So here you have it. Step by step.
Part One: Once you are finished with this article, you will be able to implement REST services in Google Apps Engine using JAVA, Spring 3.0 and JSON.
Eclipse with google App engine. I am using Eclipse, which is my favorite IDE. There is a lot of article about how to install Google App Engine on eclipse, and google also have great help doc here: http://code.google.com/eclipse/docs/download.html. I believe you can get it done easily and finally you will got something like:
Create a new google Web Application Project: File -> new -> Web Application Project (google), and named it like "gae-json-iphone"
Add Spring Support.
Go Download the latest version of Spring 3 from http://www.springsource.org/download. For this tutorial we have downloaded spring-framework-3.0.0.RELEASE-with-docs.zip, which contains the documentation also. unzip it into a folder where you keep your java libs. Copy the following Jars into war\WEB-INF\llib directory: 1. org.springframework.asm-3.0.0.RELEASE.jar 2. org.springframework.beans-3.0.0.RELEASE.jar 3. org.springframework.context-3.0.0.RELEASE.jar 4. org.springframework.core-3.0.0.RELEASE.jar 5. org.springframework.expression-3.0.0.RELEASE.jar 6. org.springframework.oxm-3.0.0.RELEASE.jar 7. org.springframework.web-3.0.0.RELEASE.jar 8. org.springframework.web.servlet-3.0.0.RELEASE.jar : Also grab your favorite version of log4j.jar and commons-logging-1.1.1.jar. Remember to rename commons-logging-1.1.1.jar to something like commons-logging-1.1.jar, google app engine replaces this jar with its own version with crippled packages, by providing different name we keep both versions and make spring happy. see more why . Once you copied the jars, open project preferences and add those jars to the build library path:
configuring spring. The final version should look like this:
Add JSON support. -- Jackson JSON.Grab the library from here and put jackson-core-1.4.jar and jackson-mapper-1.4.jar file into projects WEB-INF/lib directory
Configure Spring
To configure Spring servlet we need to create servletname-servlet.xml file for spring bean configuration. Our file has to be named rest-json-servlet.xml.
<!-- tell String to scan “com.zpylxapp.iphone” package for any bean annotations --> <context:component-scan base-package="com.zpylxapp.iphone" />
<!-- define message converter to convert messages sent to the server into beans using MappingJacksonHttpMessageConverter --> <bean class="org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter"> <property name="messageConverters"> <list> <ref bean="jsonHttpMessageConverter" /> </list> </property> </bean>
<!-- tells spring to render messages sent from the server to the client using JsonView --> <bean class="org.springframework.web.servlet.view.ContentNegotiatingViewResolver"> <property name="mediaTypes"> <map> <entry key="json"value="application/json" /> </map> </property> <property name="defaultContentType"value="application/json" /> <property name="defaultViews"> <list> <bean class="org.springframework.web.servlet.view.json.MappingJacksonJsonView" /> </list> </property> </bean>
</beans>
Part Two: Using JPA with App Engine. GAE support both JDO and JPA. I use JPA here. see detail of GAE JPA here.
Creating the persistence.xml File. The JPA interface needs a configuration file named persistence.xml . You can create this file in /src/META-INF/persistence.xml :
An app interacts with JPA using an instance of the EntityManager class. You get this instance by instantiating and calling a method on an instance of the EntityManagerFactory class. The factory uses the JPA configuration (identified by the name "transactions-optional") to create EntityManager instances.
Because an EntityManagerFactory instance takes time to initialize, it's a good idea to reuse a single instance as much as possible. An easy way to do this is to create a singleton wrapper class with a static instance, as follows:
@SuppressWarnings("unchecked") @ModelAttribute("user") @RequestMapping(value = "/", method = RequestMethod.POST) public User login( @RequestBody User user, HttpServletRequest request ) throws IOException { logger.debug(user);
// Hardcoded for demo website if( user.getName().equalsIgnoreCase("user1") && user.getPassword().equals("password1") ) { user.setId(1001); user.setEmail("fake@email.com"); //set user session to check if user login or not.Even it is RESTful, we still need "Session" request.getSession(true).setAttribute( Constants.SESSION_USER , user); return user; }
EntityManager em = EMF.get().createEntityManager(); List<User> users; try { javax.persistence.Query query = em.createQuery("select p from User p "); users = (List<User>)query.getResultList(); if(users.size()>0) return users.get(0); } finally { em.close(); } returnnull; } }
Add a preHandle interceptor, to check only if the user is present in the session. If no user is present and user is not trying to log in, send back an error. lets code our interceptor. I named it SessionInerceptor:
One more thing – we need to enable session in google app engine. Add this line to your appengine-web.xml.
<sessions-enabled>true</sessions-enabled>
sessions are backed up by the datastore, you should be able to see the session data using the Data Viewer in the Admin Console.
work on java part is already done. Let us move to Iphone client.
Part Three: Using JPA with App Engine.
To use JSON in Iphone, you need third part library like json-framework. Download JSON_2.2.2.dmg and open it, then drag the JSON directory into your project.
Create a view based iphone project, add button and textfield as following:
Handler to the “login” button is as below. which will get user/password from user input and encapsulate them in a JSON post request. If the user is invalid, give an alert window. If it is valid, the response is a NSDictionary type. It will be display in another TableView based page.
//parse response json data // Create a dictionary from the JSON string @try { NSDictionary *response = [jsonData JSONValue]; id user = [response objectForKey:@"user"]; if(user != nil && [user isKindOfClass:[NSDictionary class]]){ //go to next view UserListViewController *nextview = [[UserListViewController alloc] initWithStyle:UITableViewStyleGrouped]; nextview.user = user; [self presentModalViewController:nextview animated:YES]; [nextview release]; } else{ //alert UIAlertView *myAlert = [[UIAlertView alloc] initWithTitle:@"Error" message:@"invalid user/password!"delegate:nil cancelButtonTitle:nil otherButtonTitles:@"OK", nil]; [myAlert show]; [myAlert release];
} } @catch (NSException * e) { //nothing to do here, just provent to crash when google location search does not work NSLog(@"NSException: ...."); } @finally { [jsonData release]; } }
// Customize the number of rows in the table view. - (NSInteger)tableView:(UITableView *)tableView numberOfRowsInSection:(NSInteger)section { return 3; }
// Customize the appearance of table view cells. - (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {
original link: http://www.androidcompetencycenter.com/tag/alertdialogbuilder/
As we know android provide Activity class for developing application screens. But many a time application needs to show Dialog boxes or floating screen to do simple tasks likes taking input from user or ask for confirmation etc.
In android Dialogs can be created in following 2 ways:
1. Creating a dialog with the help of android Dialog class or its subclass like AlertDialog. 2. Using dialog theme for the activity.
Using android Dialog class: Let see how we can create a dialog with the help of Dialog class. To define a dialog the dialog class has to extend the android Dialog class.
class MyDialog extends Dialog { /** * @param context */ public MyDialog(Context context) { super(context); } }
Define a layout for our dialog. Here is the xml file for of the layout that asks for user’s name.
Now the dialog can be shown by calling the show method like this
… MyDialog dialog = new MyDialog(context); dialog.show(); …
Event handling for the Dialog controls are same as in case of the activity. Modify the dialog code to handle the onclick event on the ok and cancel button.
class MyDialog extends Dialog implements OnClickListener {
public void onClick(View view) { switch (view.getId()) { case R.id.okButton: dismiss(); break; case R.id.cancelButton: cancel(); break; } } }
To close the dialog the dismiss() method can be called. The dialog can call the dismiss method itself or some other code can also close the dialog by calling dismiss().
The dialog also supports cancel. Canceling means the dialog action is canceled and does not need to perform any operation. Dialog can be canceled by calling cancel() method. Canceling the dialog also dismisses the dialog.
When user clicks the phones BACK button the dialog gets canceled. If you do not want to cancel the dialog on BACK button you can set cancelable to false as
setCancelable(false);
Note that the cancel() method call till be able to cancel the dialog (which is the desirable functionality in most cases). The dialog’s cancel and dismiss events can be listened with the help of OnCancelListener and OnDismissListener.
Returning information from dialog: Now our dialog can take the name from the user. We need to pass that name to the calling activity. Dialog class does not provide any direct method for returning values. But our own Listener can be created as follows:
public interface MyDialogListener {
public void onOkClick(String name); // User name is provided here.
public void onCancelClick(); }
The dialog’s constructor has to be modified to take the object of the listener:
Now the calling activity needs to provide the object of the class that implements the MyDialogListener which will gets called on ok or cancel button clicks.
Now we need update the onclick method to return the user name.
public void onClick(View view) { switch (view.getId()) { case R.id.okButton: listener.onOkClick(nameEditText.getText().toString()); // returning the user’s name. dismiss(); break; case R.id.cancelButton: cancel(); break; } }
Using AlertDialog:
AlertDialog is the subclass of the Dialog. It by default provide 3 buttons and text message. The buttons can be made visible as required. Following code creates an AlertDialog that ask user a question and provide Yes, No option.
AlertDialog dialog = new AlertDialog.Builder(context).create();
dialog.setMessage(”Do you play cricket?”); dialog.setButton(”Yes”, myOnClickListener); dialog.setButton2(”No”, myOnClickListener);
dialog.show();
The onClick method code for the button listener myOnClickListener will be like this:
public void onClick(DialogInterface dialog, int i) { switch (i) { case AlertDialog.BUTTON1: /* Button1 is clicked. Do something */ break; case AlertDialog.BUTTON2: /* Button2 is clicked. Do something */ break; } }
AlertDialog.Builder: AlertDialog has a nested class called ‘Builder’. Builder class provides facility to add multichoice or single choice lists. The class also provides methods to set the appropriate Adaptors for the lists, set event handlers for the list events etc. The Builder button calls the Button1, Button2, Button3 as PositiveButton, NeutralButton, NegativeButton.
Here is an example of dialog box with Multichoice list
new AlertDialog.Builder(context) .setIcon(R.drawable.icon) .setTitle(R.string.alert_dialog_multi_choice) .setMultiChoiceItems(R.array.select_dialog_items, new boolean[]{false, true, false, true, false}, new DialogInterface.OnMultiChoiceClickListener() { public void onClick(DialogInterface dialog, int whichButton, boolean isChecked) { /* Something on click of the check box */ } }) .setPositiveButton(R.string.alert_dialog_ok, new DialogInterface.OnClickListener() { public void onClick(DialogInterface dialog, int whichButton) {
/* User clicked Yes so do some stuff */ } }) .setNegativeButton(R.string.alert_dialog_cancel, new DialogInterface.OnClickListener() { public void onClick(DialogInterface dialog, int whichButton) {
/* User clicked No so do some stuff */ } }) .create();
Activity Managed Dialog:
Android also provide facility to create dialogs. Activity created dialog can be managed by Activity methods like showDialog(), onCreateDialog(), onPrepareDialog(), dismissDialog(), removeDialog(). The onCreateDialog create the dialog that needs to be shown, for example
/** * @see android.app.Activity#onCreateDialog(int) */ @Override protected Dialog onCreateDialog(int id) { return new AlertDialog.Builder(this).setMessage(”How are you?”).setPositiveButton(”Fine”, new DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int which) { /* Do something here */ } }).setNegativeButton(”Not so good”, new DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int which) { /* Do something here */ } }).create(); }
You can create multiple dialog boxes and differentiate them with the id parameter. The dialog can be shown with the help of showDialog(id) method. The onCreateDialog method gets called for the first time when showDialog method is called. For subsequent calls to the showDialog() the dialog is not created but shown directly. If you need to update the dialog before it is getting shown then you can do that in onPrepareDialog() method. The methods get called just before the dialog is shown to the user. To close the dialog you can call dismissDialog() method. Generally you will dismiss the dialogs in the click handles of the dialog buttons. The removeDialog() method will remove the dialog from the activity management and if showDialog is again called for that dialog, the dialog needs to be created.
Using android Dialog theme for activity: Another simple way to show the dialog is to make the Activity to work as a Dialog (floating activity). This can be done by applying dialog Theme while defining the activity entry in the AndroidManifest.xml
…
The activity will be shown as a dialog as the activity is using ‘Theme.Dialog’ as theme.
You can do this with a short code by way of a SMS/MMS aggregator like OpenMarket oras another person has posted you can use the SMS Gateway but this requires the knowledge oftheend users carrier name. If your replying to a SMS onthe iPhone I believe you can use the API which in turn would give you the carrier idofthe incoming SMS message you would like to reply to.
"sms: " - brings up the New Message screen, butwith a little blue circle inthe To field thatit a little confusing and probably needs to be deleted.
"sms:?" - brings up the New Message screen, butwith a question mark in a blue circle inthe To field
"sms://" - brings up general Text Messages screen
"sms:&" - brings up the New Message screen, butwith a ampersand in a blue circle inthe To field
"sms:." - brings up the New Message screen, butwith a period in a blue circle inthe To field
how to invite friends from facebook conenct in iphone app:
You can find info aboutusing FBC onthe iPhone here(http://developers.facebook.com/connect.php?tab=iphone)
there are two modes you can use itin. One where your developer secret isinthe phone app, ifthat makes you nervous you can proxy the authentication through your own server. FB developer site has the info along with programmer supported wikis
how to debug EXC_BAD_ACCESS on iPhone http://www.codza.com/how-to-debug-exc_bad_access-on-iphone
Instruments on Leopard: How to debug those random crashes in your Cocoa app
google geocoding UK postcode issue:
oogle Maps API provides a geocoding feature, for finding the latitude and longitude of places or addresses; butitdoesnot work for UK postcodes. This is thanks to Royal Mail who have a copyright onthedata, and are very restrictive with their (expensive) licenses forit.
un the tools within XCode over menu -> run -> startwith performance tool ->......
Introduction to Instruments User Guide http://developer.apple.com/iphone/library/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/Introduction/Introduction.html
Finding iPhone Memory Leaks: A “Leaks” Tool Tutorial
Instruments on Leopard: How to debug those random crashes in your Cocoa app
how to handle & in xml file:
answer: Put thedatain a section and you should get what you want.
<name>name>
How to view contents of NSDictionary variable in Xcode debugger?
In the gdb window you can use po to inspect the object.
The difference between initWithString and stringWithString isthat stringWithString returns an auto-released pointer. This means that you don't need to release it specifically, sincethat will be taken care of next time thatthe auto-release pool cleans up any auto-released pointers. initWithString, onthe other hand, returns a pointer with a retain countof1 - you do need to call release onthat pointer, orelseit would resultin a memory leak.
code for plucking useful bits outofthe addressBook: