PowerBuilder 12.5 introduced a number of significant enhancements to web
services support, both for creation and consumption. In particular, the
following were introduced as new features in PowerBuilder.NET:
WCF client proxy WCF service target REST client proxy
We're going to look at what those new features provide and how to use them.
We're also going to look at how we can package some of that functionality so
that it can be used from PowerBuilder Classic applications as well.
Windows Communication Foundation (WCF)
First though, some background. When support for a web service client was
first introduced in PowerBuilder 9, it was done based on an open source
library called EasySOAP. There were some limitations with that
implementation, primarily because the EasySOAP library only supported SOAP
1.1, was limited to XML over HTTP transport, and provided no support for
I plan to make this the first of a series of articles that discuss the new
features in PowerBuilder 11.5, which was released late last year. Of course,
they won't be the first articles we've run on the topic, as we ran an article
on the new Code Access Security features back even before 11.5 was released
and a more recent article on New DataWindow Features. This series of articles
is intended to discuss the major hitters of the remaining features.
At the risk of putting my readers to sleep I'll cover the FDCC compliance
first. Not because most PowerBuilder develope... (more)
First there were the thin clients. Not the Internet thin clients, I'm talking
about the mainframe applications with dumb terminals. Everything ran on the
server; the client was basically there only to display and for input from the
Then PCs came along and a paradigm shift occurred toward thick clients.
Really thick clients in fact. Not only was the user interface running locally
on the PC, but often so was the data access layer, with the application
accessing local database files or perhaps a shared database file on the
network. Key reasons for the shift were a better user... (more)
On November 9, Adobe announced in a blog post that it had decided to cease
efforts to develop browser plugins for mobile devices to play Flash,
indicating that HTML5 was "the best solution for creating and deploying
content in the browser across mobile platforms." In case that sounds like
Adobe abandoned Flash entirely, it should be noted that Adobe indicated their
intentions to continue to develop the AIR player for mobile devices, so that
the role for Flash on mobile devices would be restricted to native apps, just
not browser-based apps.
A few days later in another blog po... (more)
Sybase announced the general availability of PowerBuilder 8 in conjunction
with the celebration of the tenth anniversary of
features in the new version are discussed in a number of articles in this
same issue of PBDJ.
Usability Engineering Program
Sybase announced they are looking for test subjects for their usability
engineering program, whom they will pay to participate.
EAServer Svenska PA System of Sweden
Sybase announced an OE... (more)