Moving my blog

I’ve moved all the posts and comments from this blog over to No more WordPress hosting for me! For those interested, the PHP feed can be found a

Please update any links and bookmarks. This site is hereby discontinued.

Update: This post was not posted under PHP, so it seems like PlanetPHP had the feed for everything, not just the PHP feed. Not to worry, I’ve submitted the new PHP feed from the new domain.

Setting xsi:type for objects sent over SOAP (inheritance)

This post is pretty much a revamp of a previous post called “Working with X-Fire soap services and inheritance in PHP“. That title was a bit misleading, and not really that good when it came to providing a sample.

Let’s say we have a SOAP method called createCustomer(Customer c), and we have a base class called Customer, which has to subclasses, Person and Organization. Person has firstname, lastname, while Organization as orgname and orgid. Now, the createCustomer call accepts a object of the class Customer, and any derived classes.

When retrieving a Person / Organization over SOAP, PHP automatically creates instances of the correct classes, but when calling createCustomer, passing a Person / Organization it breaks. Out object is sent as a Customer, but with Person or Organization fields added. The SOAP server expects to find a xsi:type for the object we are sending to tell what kind of Customer it is. It seems like PHP does not set this itself (maybe it should?).

I spent quite some time looking for info on how to specify the xsi:type for the objects, and I finally came across SoapVar.

I created a base class which the SOAP classes extended. A method called pack is responsible for setting xsi:type.

(I’m very aware that my pasted code looks like a mess in this blog. I will fix that ASAP).

class BaseClass{
private $namespace = “”; // from your WSDL
protected function pack($obj){
$class_name = get_class($obj);
$namespace = “”;
$pack = new SoapVar($obj, XSD_STRING, “$class_name”, $namespace);
return $pack;

class createCustomer extends BaseClass{
public function setCustomer($customer){
$this->customer = $this->pack($customer);

$customer = new Person();
$customer->setName(“John Doe”);

$request = new createCustomer();


That fixed the problems for me atleast.

PS: If your SOAP classes are prefixed you’ll need to strip the prefix in class_name when creating the SoapVar.

Related posts:

Dying with grace – PHP’s register_shutdown_function

Please see my new blog


I guess I didn’t make the purpose quite clear here. This method will allow you to show custom error messages when PHP hits a fatal error. The shutdown function will always run.

Scripts tend to die, and that’s not usually nice. We do not want to show the user a fatal error nor a blank page (display errors off) . PHP has a function called register_shutdown_function which lets us set up a function which is called at execution shutdown. What this means is that our function will be executed when our script is done executing / dying and PHP execution is about to shut down. By setting up a variable to false at the start of our script, and setting it to true at the very end of the script we can have our shutdown function check if the script completed successfully or not. If our variable is still false we know that we never made it to the last line of our script, hence it died somewhere. I’ve prepared a very basic sample which shows how you can give the user some proper feedback if a fatal error should arise. You’d want to turn of display of fatal errors for this to look nice.

$clean = false;
function shutdown_func(){
global $clean;
if (!$clean){
die(“not a clean shutdown”);


$a = 1;
$a = new FooClass(); // will fail with fatal

$clean = true;

As you can see, the shutdown_func prints something if the clean variable isn’t set to true when the shutdown function runs. This should of course be wrapped in a class (and NOT use globals), and for something more usable I recommend checking EZ Components way of doing this.

Array problems with SOAP and PHP – Updated

Please see my new blog

This is a followup to my post about array problems with SOAP and PHP. The scenario was that when an array with only one object was returned over SOAP the array was discarded and pointed straight to the single object.

Cmm was kind enough to tip me this PHP bug report, which explains that this is actually not a bug, but a feature.

To get arrays containing one single element, simply create the SoapClient as follows:

$x = new SoapClient($wsdl, array(‘features’ => SOAP_SINGLE_ELEMENT_ARRAYS));

Related articles:

Why Delphi for PHP should have used Prado instead of VCL

Please see my new blog

I recently went to a presentation where some guys from CodeGear showcased Delphi for PHP and VCL4PHP. It’s a new product which enables PHP developers to use drag / drop and wysiwyg methods to build applications with PHP. The IDE uses VCL4PHP as the underlying framework.

This kind of tool is something that has had for a long time (ie Visual Not only does it make the development process easier when it comes to building applications, but it also handles setup of applications, default configs etc. Until now there hasn’t been any tools for doing this with PHP, so I sincerely congratulate CodeGear on getting something out to the masses. Their IDE is a really nice tool with lots of potential. It ships with apache, and has lots of nice features like a integrated debugger etc. The immediate draw-back is that it runs on Windows only. My impression is that most PHP developers (atleast above hobby level) works on Linux based workstations, so I imagine getting a strong user base could prove to be difficult.

Now, why do I think that Prado is far superior to VCL, and why would it have been a better choice:

1.Exception handling
Any framework which are viable for larger scale application development should use exceptions. It’s an established way of controlling code flow and making sure the code can recover from error.

VCL: This is the first MAJOR flaw which would possibly be the hardest to fix. I’ve spent some time looking around in the VCL code, and there is some basic exception handling here and there. The problem is that most of the controls does not have any exception handling at all. This makes it very hard and tedious to control the follow when errors occur.

Prado: Usage of exceptions throughout the whole framework, with the possibility to have custom exception handlers lays the foundation implementing proper flows in the application and user friendly feedback when errors occur.

2. Usage with other PHP frameworks
A framework needs to play nice with other framework these days. There is no framework that has everything, so the coder will most likely use any given framework in addition to something else.

VCL: None of the controls I’ve seen while checking out the VCL source code are prefixed. Having controls with class names like ListView, PageControl, TreeNode etc won’t play nice with other frameworks. Also, using class names like Object and Component isn’t something you’d want to have in a framework.

Prado: All components in Prado are prefixed with a ‘T’ like TLabel, TPage, TListView ensures cooperation with other frameworks.

3. Generation of HTML code from controls
VCL: The controls implement a method called dumpContents which basically writes HTML and JavaScript tags and attributes by using echo. Some sub classing is done where the parent renders as well.

The following snip is taken from their CustomLabel code:
552 if (trim($this->LinkTarget)!=””) $target=”target=\”$this->LinkTarget\””;
554 $class = ($this->Style != “”) ? “class=\”$this->StyleClass\”” : “”;
556 echo “<div id=\”$this->_name\” $style $alignment $hint $class”;
558 if ($this->_link==””) echo “$events”;
560 echo “>”;
562 if ($this->_link != “”) echo “<A href=\”$this->_link\” $target

By letting most of the controls be responsible for writing the low-level HTML code it’s much harder to keep the code XHTML valid, and does not exactly scream re-use. See next point for how Prado handles this.

Prado: Controls that render contents in Prado extends TWebControl. I’d like to quote the Prado manual for TWebControl here:
“TWebControl is the base class for controls that share a common set of UI-related properties and methods. TWebControl-derived controls are usually associated with HTML tags. They thus have tag name, attributes and body contents. You can override getTagName to specify the tag name, addAttributesToRender to specify the attributes to be rendered, and renderContents to customize the body content rendering. TWebControl encapsulates a set of properties related with CSS style fields, such as BackColor, BorderWidth, etc.

Subclasses of TWebControl typically needs to override addAttributesToRender and renderContents. The former is used to render the attributes of the HTML tag associated with the control, while the latter is to render the body contents enclosed within the HTML tag.”

4. XHTML code generation
Producing valid XHTML is something we should all strive to do. Not doing so may result in display problems in most browsers.

VCL: I tried to validate a basic demo site created with Delphi for PHP and VCL4PHP. The results speaks for them selves. The generated HTML code is not XHTML compliant. Example from the CustomLabel code again – echo “<A href=\”$this->_link\” $target. Remember that XHTML tags are always lowecase. There are several other problems as well, and the validation link shows some of them.

Prado: The HTML code that Prado generates is mainly done in the parent controls, so keeping the base implementations XHTML valid mostly ensures that the child controls will be as well. This also removes the actual rendering code from the controls, so creating new controls is far easier and cleaner.

5. Validation controls
Input validation is some of the most boring tasks when writing web applications, and it can be fairly difficult to get it right.

VCL: According to the guy from the presentation there is none, but I found a screen cast here. It seems way more tedious than the Prado way, and I can’t tell if it’s released or just in trunk / testing at the moment.

Prado: Prado ship with several validation controls which works both client side and server side. TRequiredFieldValidator, TRegularExpressionValidator and TEmailAddressValidator ensure that the coder can feel very safe when it comes to validating input. TCustomValidator lets the user create custom validation logic to perform tasks (for example login checks). A complete list and usage examples can be found here.

6. Encapsulation
Encapsulation is a way to make sure that the internal state of classes isn’t messed with by code that should not be able to.

VCL: I’ve been looking trough the code trying to find controls that actually use private methods for managing their internals. As far as I can see there is only a fraction of the controls which uses private methods, and when they do it’s only for one or two methods. This is a design no-no when everyone can call everything.

Prado: Only methods which have to be public are public. This ensures proper encapsulation and prevents the coder from accidentally messing up the state of a control.

7. Component properties

VCL: Delphi for PHP stores all component properties in XML files. I see the point of doing this for the sake of the IDE, but when it comes to runtime code I do not. During the demo they showcased how to use smarty templates with VCL, and to add a control which was created in the RAD gui they use markup ala {button1}.

Prado: Prado separates the code and login into two files (.php which holds the page class, and .page which holds the markup). The properties for the components are kept in the .page files which is a much easier way to look at the controls when creating markup. Check this link for a quick intro to how Prado handles this.

8. Usage of globals
VCL: Using globals? We all know this is bad and belongs pretty much belongs in PHP4 applications. If you need a dirty hack it can be a last resort kind of thing, but using it throughout the whole framework?

Example of globals usage:
30 $exceptions_enabled=true;
32 global $use_html_entity_decode;
34 $use_html_entity_decode=true;
36 global $output_enabled;
38 $output_enabled=true;
40 global $checkduplicatenames;
42 $checkduplicatenames=true;

184 /**
185 * Global $application variable
186 */
187 $application=new Application(null);
188 $application->Name=”vclapp”;

These things should be config related and stored in either the application object or a core base class.

I also checked out the blog demo from this page, and usage of globals can be found throughout the applications (global $BlogDB, global $AdminDeleteComment etc).

Prado uses globals in one single file, and that’s the file responsible for generating client side scripts. Settings which span the whole application can usually be accessed from the application object.

9. Ajax

I’m considering to do another post comparing the ajax features in depth, but I just wanted to point out one thing seen in this screencast on AJAX. The coder escapes from PHP to write the javascript, then jumps back into PHP. In Prado things like these follow the same design as the rest of the framework.


I want to do some more in depth comparisons of controls and ajax support later on, but my current impression of VCL4PHP is that it’s “out of date” or not quite on a professional level. Not taking advantage of PHP5 features like interfaces and encapsulation, lacking proper exception handling, key features like validation and not generating valid XHTML code are all major points which I would expect a proper framework to have in place. One has to wonder why CodeGear went in this direction.

If you consider using VCL / Delphi for PHP I recommend that you first stop by the VCL4PHP forums to get some impressions on how people are using it and see their experiences.

I would really like to come in contact with someone that knows VCL4PHP so that a in depth comparison of the different controls can be done.

Custom active controls in Prado Part II

We’ve been working on getting drag-drop features to work in Prado for a while now, and we got it on a level which fills our needs.

The current state lets you register drags, drops and drag-drop. The most annoying limitation we have at the moment is that you only get the drop container on callback. We currently slip around that by sending our data with the callback parameters.

The demo attached here shows dragsdrops (green), drags (yellow) and drops (blue). When an element is dropped the label is updated with the name of the drop element and the callback parameter data. The callback data is currently set up in the js file and it’s only set for the dragdrop elements, but there should be nicer ways to do this.

The component only uses javascript that ships with Prado, so no external libs are required. The actual MyDraggable php class is based on another Prado component, and it probably needs some cleanup as well. The demo ships with Prado 3.1, so just unzip and set correct permissions.

Kudos goes to my co-worker Lars-Olav for getting the client side stuff to work. Javascript is not my strong side 😉

Online demo –
Download source –

Update: Source file is not up to date. Will fix asap.

SoapFault vs Exceptions

When working against complex soap servers from PHP it’s generally a nice thing to be able to act on exceptions and not just provide the error message. I’ve been working against X-Fire web services for the last few months, and every time an exception is thrown it’s returned as a SoapFault with the actual exception name as property in the detail field. I wanted proper exceptions which I could do something useful with, so I poked around and came up with something which fixes this. The basic idea is to catch the soap fault exception, parse it for information and build a new exception based on the name which is retrieved. The code is a bit gritty since the actual name of the exception is a field, but that’s nothing that reflection can’t solve. The doRequest method is the method used to call the web service methods. This is a part of my soap client class.

* Do the soap request
protected function doRequest($name, $args = array()) {
try {
$response = $this->__soapCall($name, $args, $this->options);
return $response;
catch(Exception $e) {
$newEx = $this->buildException($e);
throw $newEx;

* parses a soap fault and returns the error code and message
* used by buildException
* @param SoapFault $e
* @return array
protected function parseSoapFault(SoapFault $e) {
$pos = strpos($e->faultstring, ':');
$code = "";
if($pos) {
$code = substr($e->faultstring, 0, $pos);
$message = trim(substr($e->faultstring, $pos+1, strlen($e->faultstring)));
} else {
$message = $e->faultstring;
return array($code, $message);

* This method takes a SoapFault and builds a proper exception from it
* The SoapFault can hold a server side exception name in it's detail field. This
* method takes a peek to see if that field exists, and if it does the name of the
* field is extracted via reflection. A new exception is created of the class that
* was just retrieved and the message and code is set.
* The message and error code is extracted from the soap fault.
* @param unknown_type $e
* @return unknown
protected function buildException($e){
list($code, $message) = $this->parseSoapFault($e);
if (!isset($e->detail)){ // No exception found
$ex = new GenericException($message,$code);
return $ex;

// get the actual name of the exception
$reflectionObject = new ReflectionObject($e->detail);
$properties = $reflectionObject->getProperties();
$exceptionName = $properties[0]->name;

$exception = new $exceptionName($message,$code);
return $exception;

Prado Resources

When I first started using PHP on a larger scale I didn’t have any experience with frameworks, so I started creating some minor helpers which made my day easier. After my first project I came across Prado. Since I had been using .net previously I grasped the concepts really quickly, so it was love at first sight. It took around a week to get fully productive with Prado, and it’s saved me countless hours of nitty gritty work. Since I first started using Prado I’ve found the forums to be the best source for information and support when I can’t find help in the documentation. The community around Prado isn’t that big (yet), but there are quite a few people which are very active. At first I can be a bit hard to navigate around the available resources, so I’ve composed a list of links which is worth checking out:

A few nice-to-know links and blogs related to Prado:

Planet Prado
Pulls data from most of the major Prado related bloggers. Nice place to stay up to date on what’s going on in the Prado world.

Prado Roadmap
The trac-based road map for the Prado project. Shows the current milestones and planned releases, with information about which features to expect, which bugs are reported and so on.

Prado Blog Tutorial
A step-by-step tutorial on how to build a blog using Prado. Nice place for beginners wanting to learn Prado

Prado Quickstart Tutorial
The term tutorial isn’t quite fitting, since it’s more of a reference. The Quickstart is a nice reference for control and component usage in addition to documenting severa key features and concepts in the Prado framework.

Prado Component Repository
Trac set up for user-submitted components and controls. This project is still in the early stages, but worth keeping an eye on.

Prado Community Project
The Prado Community Project is a new project created by the most active users of Prado. The goal of this project is to ensure that Prado gets a growth in both users and material. There are several projects planned which looks very interesting. If you have some time to offer, please stop by the forums and help us out.

Custom active controls in Prado Part I

There has been lots of interest in the AJAX (active controls) features in Prado lately, but the lack of client side controls has been a turn-off for many. The area that’s gotten most request is drag / drop. Prado 2 had controls for this, but it’s been absent in Prado 3. Several users on the forums has been trying to get it working, but nothing has ever been completed. The main issue has been the communication between the client side scripts and the server side control (callbacks). I’ve spent some time digging trough the Prado code and created a concept control which fires a callback.


MyDraggable.js code



Stay tuned for Part II which hopefully shows something more useful 🙂

Prado 3.1 released!

Earlier today the Prado team released version 3.1 of the Prado Framework. The new features includes AJAX support trough Active Controls, some cool new database support and various other new services and controls. Go here to see the release announcement.

« Older entries