Let’s start from beginning, to everything clear later:

SOAP basics

SOAP = Simple Object Access Protocol. It is based on XML mostly via HTTP (POST).
Soap basic structure is basically Envelope with Header and Body inside:

Soap structure

Some example SOAP message looks like this:

POST /InStock HTTP/1.1
Host: www.example.org
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 299
SOAPAction: "http://www.w3.org/2003/05/soap-envelope"

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
  <soap:Header>
  </soap:Header>
  <soap:Body>
     <m:GetStockPrice xmlns:m="http://www.example.org/stock">
     <m:StockName>IBM</m:StockName>
     </m:GetStockPrice>
  </soap:Body>
</soap:Envelope>

WSDL

WSDL stands for: “Web Services Description Language”. It is basically XML – based language that is used for describing the functionality offered by a web service.

There are two possible versions of WSDL: WSDL 1.1 and WSDL 2.0. Since Magento uses WSDL 1.1, I will continue with this WSDL version in this article.

Objects in WSDL

Magento Core API

There are two API types present in Magento by default (I am talking about Magento versions 1.6.2CE and below):

• XML-RPC
• SOAP (API v1 and v2)

More on API types and differences you can find in post: Consuming SOAP web services in iOS by Ivan Kalaica

Accessing Magento API via SOAP – basic steps

1. Create appropriate role (Magento Admin)
2. Create web services user (Magento Admin)
3. Assign created role to the user (Magento Admin)
4. Log-in to web service and retrieve Session Id (Soap Client)
5. Call appropriate method (Soap Client)

Creating Web Service Role

First we should define appropriate roles for web services user, so, log-in to admin panel, go to menu: System/Web services/Roles and click on Add New Role button.

On “Role info” tab, we need to enter some custom Role name, and then click on Role resources tab, choose wanted role resources and Save Role.

Role resources necessary for usage with API are basically defined in each Magento module’s api.xml file in etc folder, and can be checked there what role resources are needed for successful consuming specific API method.

Creating Web Service User

After creating role, let’s create web services user that will have defined role permissions.
Go to menu: System/Web Services/Users and click on “Add New User” button. Under “User Info” tab fill the fields, and pay attention that “User Name” and “API key” values are values that we will use on client side to access API.

Assigning created Role to the User

After that, we just have to click on User Role tab and click on radio-button to assign wanted role to current user.
After that we just need to click Save User button.

Calling Magento API v1 methods

<?php

$api_url_v1 = "http://magento.local/api/soap/?wsdl=1";

$username = 'mobile';
$password = 'mobile123';

$cli = new SoapClient($api_url_v1);

//retreive session id from login
$session_id = $cli->login($username, $password);

//call customer.list method
$result = $cli->call($session_id, 'customer.list', array(array()));

Calling Magento API v2 methods

<?php

$api_url_v2 = "http://magento.local/api/v2_soap/?wsdl=1";

$username = 'mobile';
$password = 'mobile123';

$cli = new SoapClient($api_url_v2);

//retreive session id from login
$session_id = $cli->login($username, $password);

//call customer.list method
$result = $cli->customerCustomerList($session_id);

If you compare those two versions of API calls, you will notice that v1 uses method “call” for ever requested method, and v2 has defined full method name to call.

//API v1 way
$result = $cli->call($session_id, 'customer.list', array(array()));

//API v2 way
$result = $cli->customerCustomerList($session_id);</pre>

Basically, API v2 calls method same way like v1, but there is some kind of wrapper around call method in v2. Somebody will ask: Why Magento did something like this? Why would somebody make different methods for accessing API when we have “call” method already?

Here comes the basic difference between v1 and v2 API in Magento.

To demystify that, we should first look at and compare WSDL for v1 and v2 API in Magento.

If we open url: http://yourserver.com/api/soap/?wsdl we can see that few basic method are inside: call, multiCall, login etc…
But, if we look at http://yourserver.com/api/v2_soap/?wsdl, we will find that there is bunch of methods defined inside.

Imagine that you want to use some generator for SOAP methods to auto-generate your client-side classes end entities for consuming web services.
When using WSDL generated for API v1, we could just generate those few methods which will not tell to our source code generator what methods are available, and what parameters for each methods can we use, what entities we should have on client side … but if we are consuming web services through v2 API, it’s already served for us inside WSDL…

Conclusion:

When using Magento v1 API, we access resources via call method and provide API method name and parameters as parameters of call method.

When using Magento v2 API, we access resources via real method name and we provide parameters as defined in WSDL for each specific method.

OK. When we got this difference, and showed how to consume SOAP, let’s focus on creating own web service methods compatible with API v2.

Practical example: Creating own API v2 method

Basic steps:

1. Create Magento Extension (we are not going explain here how to do it)
2. Create Model for API method
3. Create and configure api.xml file
4. Create wsdl.xml file (with proper definitions)
5. Create wsi.xml file (with proper definitions) (OPTIONAL)

Creating Model for API v2

After properly configuring our config.xml it looks like this:

<?xml version="1.0"?>

<config>
   <modules>
      <Inchoo_Mapy>
         <version>1.0.1</version>
      </Inchoo_Mapy>
   </modules>
   <global>
      <models>
         <inchoo_mapy>
             <class>Inchoo_Mapy_Model</class>
         </inchoo_mapy>
      </models>
   </global>
</config>

Let’s navigate through Magento core files to see where Magento API models are in file-system:

Since we are going to use API v2 only, We will create our model like this:

Creating and configuring api.xml

The easiest way is to copy/paste one of Magento’s api.xml files in our etc folder and make changes there to suit our needs. Our final api.xml should look like this:

<?xml version="1.0"?>
<config>
   <api>
     <resources>
     <!-- START GUSTOMER GROUP RESOURCES -->
       <mapy_customer_group>
            <model>inchoo_mapy/customer_group_api</model>
            <title>Inchoo Customer's Groups API</title>
            <acl>mapy_data</acl>
            <methods>
              <list translate="title" module="inchoo_mapy">
                  <title>Retrieve customer groups</title>
                  <method>mapyItems</method>
              </list>
            </methods>
       </mapy_customer_group>
     <!-- END CUSTOMER GROUP RESOURCES -->
    </resources>
    <v2>
      <resources_function_prefix>
           <mapy_customer_group>mapy_customerGroup</mapy_customer_group>
           </resources_function_prefix>
    </v2>
    <acl>
       <resources>
           <mapy_data translate="title" module="inchoo_mapy">
              <title>Mapy data</title>
              <sort_order>3</sort_order>
           </mapy_data>
       </resources>
    </acl>
  </api>
</config>

Here is logic that has to be implemented in api.xml file. Api.xml file basically connects API calls with php methods inside specific models. Also, the ACL resources are defined here for specific api call.

Creating wsdl.xml file

When working with wsdl.xml and wsi.xml later, if you are happy NetBeans user, I strongly suggest you to search on Google and download the XML Tools plug-in that can make life much easier …

There are few things that we have to fill-in when creating wsdl.xml.

• Bindings
• Port types
• Messages
• Types / Complex types

Also, it’s easier to copy one of Magento’s wsdl files, paste it in our etc folder and remove unnecessary things and add our own inside.

Here is NetBeans – XML Tools screen-shot how this look like:

This  image is showing logic and direction how should we fill-in wsdl.xml:

Let’s now look at real xml source:

After we finished with wsdl, let’s go to http://ourmagento/api/v2_soap/?wsdl=1 to see changes in global wsdl we made. (Don’t forget to clear cache first!).

We can see that all wsdl.xml files including ours are rendered as single.

All available wsdl definitions for current Magento installations are shown and our definitions should be there.

Now we are ready to use our newly created SOAP method.

But, if we want use some generator for client classes with that, for example SUDZC (http://sudzc.com) we need to make one more thing in order to make it possible…

WSI

- WSI is in basic compatibility layer for different frameworks and provides a little bit more information that can be used for example with XSLT to transform definitions into our client source code.
- It’s not essential in order web services to work.
- It is rendered when: Magento admin: System/Configuration/Services/Magento core API/WSI-Compliance configuration value is set to “YES”.

We could say that following sections we have to fill-in inside, in order to add our definitions properly:

• Bindings
• Port types
• Messages
• Types / elements
• Types / complex types

Let’s copy/paste one of Magento’s wsi.xml inside our etc folder first. After that, let’s delete all unnecessary definitions for our SOAP method.

Adding definitions inside WSI except for slightly different definitions are basically the same as for wsdl.xml. If you are using existing wsi.xml, it’s easy to delete unnecessary and rename few nodes to suit your needs. Just follow the rule to fill all of this in the above list (Bindings, Port types … ).

Here you can download archive with basic wsdl.xml, wsi.xml, api.xml so you can easier start writing your own web service methods. Just put these files in your etc folder, rename appropriate things with your own and that’s it.

That would be all for now. If interested in Magento API, stay tuned.

Cheers

Do you want to develop your own Magento mobile application?

Great! I’ll give you some pointers on how to get a grasp on Magento’s XMLConnect, an extension that serves Magento Mobile application.

Keep in mind that XMLConnect extension comes ‘preinstalled’ in Magento CE 1.5 and later, but you can get it from Magento Connect.

The Big Picture

Awhile ago, Magento Mobile was released for iPhone, iPad and Android devices. It consists of two parts: a Magento web store with an XMLConnect extension installed and configured, and a native application itself.

XMLConnect extension’s purpose here is to serve your application with requested data (category listing, product information, etc.) and execute desired actions (buy, log in, checkout, etc.).
Basically, application sends a request (plain HTTP GET/POST) to your Magento store (XMLConnect) and it responds with an XML result.

The best way to get familiar with XMLConnect is to see it in action:

1) Set up a Magento store on your web server with some sample data
2) In Magento admin->Mobile->Manage Apps add a new mobile application
3) Install Magento Mobile on your device
4) Start Magento Mobile on your device with your Magento store url and the app code of the application you just created in Magento admin->Mobile

While exploring Magento Mobile, keep an eye on (Apache) activity log file to see exactly what the application is requesting from the server.
For instance, the first request would probably be the application configuration request.

/xmlconnect/configuration/index/app_code/defand1/screen_size/480×800

We recognize in this request an app code (in this example it is “defand1″) and your device’s screen size (here it’s “480×800″).
Let’s check out what is the result of this request. In your browser navigate to:

http://magentoivica.loc/xmlconnect/configuration/index/app_code/defand1/screen_size/480×800
(obviously, replace “magentoivica.loc” with your web server name. Recognize the rest of the url?)

Voilá, what you should get is an entire configuration of your app (as it is set in your Magento admin) in an XML format.

Using this practice, you can easily explore most of the capabilities of XMLConnect. Also, it may be necessary to get into the code of XMLConnect if you want to master some of the more advanced actions (such as the checkout process).

Ok, now you know basics of using XMLConnect, how to make a request and what to expect as a result. But, how to use this information in an Android (Java) environment?

You probably already know something about parsing XML data. I will show you a better way (probably) which will allow you to have more modularity and sustainability in an Android application development.

So, stay tuned

There are lots of people that visit inchoo.net who are not natural English speakers. This game will be awesome for you. You’ll start thinking about all sorts of different words and hopefully learn how to spell them correctly. But it is not all about learning, this game is fun! There are 3 different mods you can play with: Story Mode, Arcade Mode and Clear the Board.

Story Mode

An increasingly challenging game with 15 levels and a different target for each level. Reach the target score or compose the number of words required to complete the level before the time runs out! Conquer all 5 Letter Block Worlds by completing the 15 levels in one game. Don’t let the board fill in or you’ll loose the game!

Arcade Mode

Freestyle in a random world. The higher you score, the faster blocks will fall on the board. How long will you last? Challenge the your friends to beat your high score through the Open Feint gaming network!

Clear the Board

Look! A board full of blocks! Can you clean it up without shaking the device to get more blocks? Achieve that to enter the global high scores for this game mode!

Warning: Magento is NOT a word. xD

You can buy the app here.

The store is located here and it’s currently featuring two products:

• A completely free Review Alert component for iPhone SDK that gives you the ability to pop-up an alert after a chosen period of time, asking user to review the app.
• A 3D Tag Cloud Component for iPhone SDK, with a special launch discount of 50% available for only $ 49.00 USD!

We hope many more useful code libraries will be released on Surgeworks Mobile’s shop as the time passes by, so make sure you stay tuned to the links above.

First of these brands was Inchoo, dedicated to e-commerce design, development, and marketing. It’s been a while since we figured out that we need a separate micro-brand such as Inchoo for our mobile application development services, and today, we present you the Surgeworks Mobile website.

Surgeworks Mobile is a web presentation of our mobile applications development unit. Homepage, much like Inchoo, features new blog posts. We hope some of our loyal readers here at Inchoo that are also interested in the mobile application development will like the content over there and start following that blog as well.

Site also features the mobile applications that the team already did and there are sections describing the services and the team.

The ShoutEm iPhone app is actually two apps in one: it’s a fully functional Twitter client, but in addition to Twitter, you can also use it to read and write posts to twitter_timelineany of the networks on ShoutEm, as well as StatusNet, the open source microblogging service.

For example, let’s say that you’ve created a network on ShoutEm for your coworkers, but you also have two accounts on Twitter. With the ShoutEm iPhone application, you can easily read the posts and write new ones for all three networks, all from one place.

Here are the most important features of the ShoutEm iPhone application:

* handle multiple accounts on your favorite microblogging networks: ShoutEm, Twitter or StatusNet (Laconi.ca)
* browse through your friend’s statuses, public statuses or mentions
* update your status (with photo or location attached)
* explore user profiles, their followers or statuses/tweets
* follow or stop following users
* explore received or sent private messages; write direct messages to users
* track conversations in our threaded view (ShoutEm specific)
* status search

Click here to download ShoutEm iPhone app for FREE

Now lets get back on memory leak issue created by CFNetwork class. If you create NSURLConnection object you will get this memory leak. First time I meet with this issue I was thinking it was my fault as developer, but when I tracked leak I realized that memory leak is created by framework internally. Instruments tool says clearly – “Responsible caller – CFNetwork”.

Well, this is my own conclusion and I might not be right but considering all given facts the leak is created by CFNetwork class. Also, I am not only one developer that has same issue. Many of iPhone developers has complain on same memory leak created by CFNetwork class. To solve this issue I try to put autoreleas pool like code below but no luck.

NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
…
[pool release];

Also I tried to create NSURLCache object like code below but no luck.

NSURLCache *sharedCache = [[NSURLCache alloc] initWithMemoryCapacity:0 diskCapacity:0 diskPath:nil];
[NSURLCache setSharedURLCache:sharedCache];
[sharedCache release];

If any of you has meet similar issue or maybe has solution for this memory leak please leave comment bellow. Thanks!

View more images on Surgeworks website.

http://code.google.com/p/satisfactionremotecomponent/ 

Flurry Analytics iPhone API is second one. This is really great API that every better developer would integrate. This API is analytics tool for iphone application which provides complete insight analysis of the every app utilization and not just for iPhone platform. Here is little info about it: “Flurry Analytics provides accurate, real time data to developers about how consumers use their mobile applications, as well as how applications are performing across different handsets. Application developers receive aggregated usage and performance data, as well as robust reporting and analysis tools. With this data, developers can identify issues and opportunities, create a more informed product roadmap, increase retention and grow their user base.” You can find more info on this link. 

http://www.flurry.com/product/index.html

From past experience I can confirm that our app users are very satisfied with services that these two tools give them, together with us.

I know you will now say there is “Reachability” named sample app at developer connect library to download, but it ain’t what I am looking for. What I am looking for is feature that will tell me do I have internet connection while I have network connection, to be more accurate, do I have internet connection while I am connected to some wireless local area network? I know, some of you will now say: “Well you can make NSURLConnection and wait for didFailWithError or connectionDidFinishLoading delegate methods”. Yeah, but this again ain’t what I am looking for.

What I was really looking for is something like pinging some host. Again, you will now say: “Well, you might don’t know but Reachability sample app has way to test reachability of given host.” Yeah, but this again ain’t what I am looking for.

I just hope that Apple’s developers will soon add some really easy way to do something like this. Please don’t hesitate to leave comments, and please tell me I am wrong on this one and easy way really exist. Please that I am blind as mole and I can’t see! Thanks!

UIImage *myImage = [UIImage imageNamed:@"me.png"];

UIImageWriteToSavedPhotosAlbum(myImage, self, @selector(image:didFinishSavingWithError:contextInfo:), nil);

// And if you wish add this selector method in code;

- (void) image:(UIImage*)image didFinishSavingWithError:(NSError *)error contextInfo:(NSDictionary*)info;

That’s all you have to add! Quite simple, is it?

- (BOOL)webView:(UIWebView*)webView shouldStartLoadWithRequest:(NSURLRequest*)request navigationType:(UIWebViewNavigationType)navigationType {

if(navigationType == UIWebViewNavigationTypeLinkClicked) {

if (overrideLinksSwitch.on == TRUE) {

[self myMethodAction];

[myWebView stopLoading];

return YES;
}

else {
return YES;
}
}

return YES;
}

You can download example app here.

Here are some of the questions:

One of the most interesting software sales environments on the planet is iPhone. Why programs on the phone ? Do these small programs/apps on the phone make our World better place ? Is this a secret for success ? Why now and not before few years ?

Answer is fairly simple. It’s simple and it is Apple’s. You can make very good money programming software for iPhone and have fun at the same time. Just like I do now. Apple makes world better place. Just kidding but there is still some small amount of true in that sentence.

Why iPhone mobile platform is your choice and since when you are developing apps for iPhone ?

Inchoo company gave me a chance to work along with Surgeworks company on iPhone development in October last year. I accepted the offer and I’m satisfied now I made that decision then. In beginning it was maybe little hard but now I can say I am happy I have then decided to work along with these great people.

Read the rest of interview at this URL:
http://zecina.blogspot.com/2009/04/one-of-most-interesting-software-sales.html

- (void) viewDidLoad {

[NSTimer scheduledTimerWithTimeInterval:3.0f target:self selector: @selector(myMethod) userInfo:nil repeats:YES];

[super viewDidLoad];

}

- (void) myMethod {

NSLog(@"Method execution");

}

And that is it. Again!

invocationWithMethodSignature consists of method selector (which method your invocation will trigger) and target (which object is target). Next you make instance of NSTimer class to define repeat interval. See example below.

- (void) viewDidLoad {

NSInvocation *updateDisplayInvocation = [NSInvocation invocationWithMethodSignature:[self methodSignatureForSelector: @selector (myMethod)]];

[updateDisplayInvocation setSelector: @selector (myMethod)];

[updateDisplayInvocation setTarget: self];

NSTimer *audioDisplayUpdateTimer;

audioDisplayUpdateTimer = [NSTimer scheduledTimerWithTimeInterval:3.0 invocation:updateDisplayInvocation repeats:YES];

[super viewDidLoad];

}

- (void) myMethod {

NSLog(@"Method execution");

}

And that is it!

I always like to prepare app for future changing, for example, if one day I change my mind and want to change existing clicking sound with new one I don’t have to change it everywhere I have create it, I just change value of effect string instance that is implemented in custom made Sound class in static method + (void) soundEffect:(int)soundNumber.

You can see here that I used static method so I don’t have to create instance of that class just to play a sound. When you want to call sound effect from another class just add this line of code [SoundAlert soundEffect:1]; to play for example an click sound effect.  I recommend you to put this call in viewWillDisappear: method so that sound triggers every time when current view exits.

Now finnaly if I want this class to work without errors I must add sound files. Isn’t that logical or what? I am using .aif  audio file so I must be sure to set type string instance value to @”aif” and also set the name of audio file with same name as value of effect string instance. Here is Sound class.

Sound.h

#import <foundation /Foundation.h>
#import <audiotoolbox /AudioToolbox.h>

@interface Sound : NSObject {

}

+ (void) soundEffect:(int)soundNumber;

@end

Sound.m

#import "Sound.h"

@implementation Sound

+ (void) soundEffect:(int)soundNumber {
NSString *effect;
NSString *type;
if (soundNumber == 0) {
effect = @"intro";
type = @"wav";
}
else if (soundNumber == 1) {
effect = @"click";
type = @"aif";
}
else if (soundNumber == 2) {
effect = @"error";
type = @"aif";
}

NSString *value = [[NSUserDefaults standardUserDefaults] stringForKey:@"sound"];
if ([value compare:@"ON"] == NSOrderedSame) {

SystemSoundID soundID;

NSString *path = [[NSBundle mainBundle] pathForResource:effect ofType:type];
NSURL *url = [NSURL fileURLWithPath:path];

AudioServicesCreateSystemSoundID ((CFURLRef)url, &soundID);

AudioServicesPlaySystemSound(soundID);

}
}

- (void)dealloc {
[super dealloc];
}

@end

I have also added switch somewhere in my costume made settings menu that enables user to turn OFF or ON all custom used sounds in app. Here we are checking in which state is switch and if it is on ON position sound will play. You can see how to use NSUserDefaults to save state of switch in my previously post. That’s all!

- (IBAction) saveState {

NSString *value = @"ON";
NSUserDefaults *userPreferences = [NSUserDefaults standardUserDefaults];
if(!switch.on){
value = @"OFF";
[userPreferences setObject:value forKey:@"stateOfSwitch"];
}
[userPreferences setObject:value forKey:@"stateOfSwitch"];

}

This is part of code that loads value in a NSString *value for key stateOfSwitch. When you start your application again and view finisheds with loading button will be in lefted state.

- (void)viewWillAppear:(BOOL)animated {

NSString *_value= [[NSUserDefaults standardUserDefaults] stringForKey:@"stateOfSwitch"];

if([_value compare:@"ON"] == NSOrderedSame){
switch.on = YES;
}
else {
switch.on = NO;
}
[super viewWillAppear:animated];
}

NSUserDefaults class gives us an opportunity to save values without database use. This class uses KVC structure model for saving and loading values. Key-value coding (KVC) defines generic property accessor methods—valueForKey: and setValue:forKey:—which identify properties with string-based keys.

KVC is not meant as a general alternative to using accessor methods—it is for use by code that has no other option, because the code cannot know the names of the relevant properties at compile time. Key-value coding and the dot syntax are orthogonal technologies. You can use KVC whether or not you use the dot syntax, and you can use the dot syntax whether or not you use KVC. Both, though, make use of a “dot syntax”.

In the case of KVC, the syntax is used to delimit elements in a key path. It is important to remember that when you access a property using the dot syntax, you invoke the receiver ’s standard accessor methods (as a corollary, to emphasize, the dot syntax does not result in invocation of KVC methods valueForKey: or setValue:forKey:).

Dose is intended for use with products by Seachem Laboratories. If you use products from our reef line, plant line, or our gravels, then Dose is for you. We’ve taken our online dosing calculators and put them in your pocket.

Seachem provides dosing instructions on all of our products, so you can always determine the proper amounts to dose, but now we’ve made it even easier. We’ve taken our three product lines that normally require some calculation and done the work for you. Some of the values on our labels have been rounded for simplification, but Dose uses precise values to give the most accurate dosing parameters possible. Now all you have to do is enter a few known values and Dose does the rest.

Setting up a new aquarium? Use Dose to figure out how many bags of one of our gravels you’ll need.

You’ve tested your calcium levels in your reef aquarium and they’re low. Use Dose to determine how much of one our calcium supplements to use to get them back up to desired levels.

Dose is also perfect for pet store employees. Help customers determine how much of a product they need to buy or help them set up dosing regimen.

You can check out Dose on iTunes.

• Launch iTunes on your Mac.
• Search for the item you want to link to.
• Right-click or control-click on the item’s name in iTunes, then choose “Copy iTunes Store URL” from the pop-up menu.
  
• The returned URL is an itunes.apple.com link. However, iPhone requires phobos URLs for direct linking to the App Store.
• Therefore, you must replace itunes with phobos in the returned URL.
• Open the modified URL using an NSURL object and the -[UIApplication openURL] method.

- (IBAction)appStoreLink {

[[UIApplication sharedApplication] openURL:[NSURL URLWithString:@"http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=301349397&mt=8"]];

}

Now when you press button linked with appStoreLink IBAction, App Store application will open and you will see Divine Office application. That’s all.