PowerBuilder has been around and successful for almost two decades now and after many discussions with PowerBuilder developers, it has become apparent to me what the marquee feature of PowerBuilder really is.  Some developers would comment on the ease of report creation, and others on the presence of client-side processing capabilities, but most only wanted to talk about their beloved Data Window.  After taking a look at what makes the DataWindow tick, it is truly the power of the DataWindow that makes developers’ lives easy.

Over the last 18 months, I’ve gotten to work with a variety of PowerBuilder versions, and had first-hand experience with the Data Window. When you look at it, it is a fantastic piece of tech.  For those of you who don’t understand the concept and what it does, let me try to explain.  The DataWindow is a group of user interface elements that can easily be tied to the database using the PowerBuilder IDE.  What makes the DataWindow so sticky is that once the interface has been defined and the SQL statements have been written, the two-way data connection can be made. Two way data means that if the data is updated on the UI and saved by the user it will be persisted to the database, and if the data changes on the database, upon refresh of the UI that data will be sent back. Developers love this because it is a minimal amount of code to begin developing screens that map to their business requirements quickly. This allows them to focus on the solving the business problem at hand because they do not have to worry about application infrastructure.

Unfortunately, there are number of architectural elements of PowerBuilder that severely limit its ability continue to be a viable option for continued IT support. Most prominently is its lack of support for a rich web environment that can recreate the performance, client side processing capabilities, and UI widgets that are considered standard in today’s Web 2.0 frameworks and delivered in a centrally managed, no-install medium. Also, finding resources to maintain and enhance PowerBuilder are severely hindering the IT department’s ability to continue support these applications as they age. The customers I’m working with are in need of a solution for the deployment issues, legacy language/skillset issues, diminishing support for PowerBuilder, and the need to move to a more open codebase like Java.

To help these customers, we’ve built Java technology that should be an easy transition for current PowerBuilder developers and Java developers interested in building a Java web app that gives that “Desktop Application in a Browser” feeling. In addition to building technology that can meet or exceed the client side capabilities of a PowerBuilder application in the web, Nexaweb has developed a semi-automated process that can quickly cut the process of moving from PowerBuilder to J2EE with greater functionality, flexibility and maintainability.

Modernizing to J2EE from PowerBuilder will be our focus in a demo today (Wednesday, February 17 at 2 p.m. EST) during our webinar with Sierra Atlantic.  I would definitely recommend checking it out.  You can register here: https://www1.gotomeeting.com/register/798601449.

The current state of affairs has most organizations asking IT to build business cases for new expenditures, especially when it comes to updating an application that isn’t necessarily broken.  For IT, broken tends to mean that an application is getting harder to find resources to keep it current, maintenance is time consuming, and the technology it’s built on can’t support the features the business is asking for.  For the business, it’s about revenue.  If an application gives them what they need, let’s them do their job, it works.  However, if they feel the application is holding them back and keeping them from realizing the most revenue possible, it gets top modernization priority. For example several of our most recent banking customers want to leverage existing back office systems (e.g. pricing engines) to extend their global trading systems to external traders, partners and banking customers. This drives significant revenue by dramitically increasing transaction volume and customer satisfaction through eCommerce.

When a decision is made to modernize, the discussion always get political.  Some folks are in favor of building their own application to ensure it serves their business, while others feel the cost savings of going with a Commercial Off-the-shelf Software (COTS) solution is a no brainer.  The build vs. buy dilemma is as old and stubborn as PowerBuilder, Visual Basic and C++ themselves.  Neither approach is wrong, but all have their drawbacks.  Modernizing an application using in-house resources ensures that specific features and functionality will be included, but not without a cost.  A COTS solution can dramatically reduce the costs, but tends to require a trade off of features and functions leaving the business without any real advantage or edge.   So, what’s the answer?  That’s a million dollar question, and a puzzle more and more organizations are having to solve.  How are you approaching modernization at your organization?  Is revenue driving final decisions?  What are your thoughts on the build vs. buy question?

Chris Heidelberger, CEO, Nexaweb

A large percentage of outsourced, onshore and offshore resources, are skilled in XML, Java and other Internet-based languages and development techniques, meaning their ability to tinker with and add features to 3GL/4GL applications is limited at best and that cost savings of such as model is neutralized. Adding to the conversation is the acknowledgment that more than 200 million lines of COBOL code are currently in use while another five million are being written each year. This presents a challenge given the waning number of students studying computer science and the shrinking number of experts in legacy applications.

According to Gartner, “interviews conducted with IT sourcing managers across the Gartner client base hint at what’s to come: Many have seen price hikes of 10% to 15% in certain skills during the past year.”

Still, the dwindling, expensive legacy expert community is not the only IT population that needs to be addressed.  The rise of the millennium generation should also be top of mind.  Gartner research reports: “College students and 20-somethings are heading toward IT-related work in film, music, multimedia, gaming and Internet companies” and that “students enrolling in science, technology, engineering, and mathematics — the STEM disciplines – have declined in developed countries and risen in other countries.  In the United States for instance, computer science enrollment has dropped 39% since 2002.

The costs and reduction in the workforce of experienced legacy IT professionals combined with a shrinking pool of Internet IT resources is a significant issue, but so too is it an opportunity — an opportunity to re-structure IT as a business-driven function. CIO’s, IT executives, and business leaders must identify the roles and competencies that understand how information, processes, and relationships drive business effectiveness and who can lead the development of solutions to support LOB demands. These roles include business process designers and developers, enterprise architects, information modelers, business analysts, and IT financial analysts.  While there is not an overabundance of these resources either, an IT group organized around these roles will require fewer bodies which equates to less operational overhead.  The effect of such a transition however will leave a gap in the more traditional IT roles such as application development, programming, infrastructure and services.

“In China, India and other countries, the IT curriculum attracts enrollment.  Chinese universities graduate about 500,000 IT and high-tech students every year.”  Developing countries such as China and others are quickly becoming part of the workforce solution, but as it relates to Internet-oriented technologies such as Java, .NET, XML and others. Thus, it comes back to application modernization.  There is a tremendous demand among business leaders that IT become business driven.  This requires that IT resources are more business-minded, but such a transition in resource skill set requires growing the IT department and incurring more costs, or focusing the IT organization on these skills and leveraging outsourced resources for development and programming.  To adopt that outsource model effectively however requires that applications and the architecture that supports them exist in a format familiar to that pool of outsource
resources.

Pursuance of an application modernization initiative, regardless of size or scope, is paramount to better utilization of offshore resources.

While working on an application for a client, I encountered some issues with Java’s MessageFormat. In particular, I needed to pass MessageFormat a string that contained single-quotes and curly braces that would be treated literally. This is an issue, because single-quotes and curly braces are special characters in MessageFormat land.

MessageFormat is designed to allow you to dynamically create a string based on a static pattern and a set of inputs. For example, this is from the MessageFormat JavaDoc:

 Object[] testArgs = {new Long(3), "MyDisk"};

 MessageFormat form = new MessageFormat(
     "The disk \"{1}\" contains {0} file(s).");

 System.out.println(form.format(testArgs));

 // output, with different testArgs
 output: The disk "MyDisk" contains 0 file(s).
 output: The disk "MyDisk" contains 1 file(s).
 output: The disk "MyDisk" contains 1,273 file(s).

Seems pretty straight forward. However, say you wanted to format a string that contained curly braces, such as “{ Hello {0}! I’m inside curly braces }”. Of course, to support this, MessageFormat uses single-quotes to specify strings that should be treated literally. So, naively, one might think to format

{ Hello {0}! I'm inside curly braces }

with the following output where {0} = “Joel”

{ Hello Joel! I'm inside curly braces }

We would come up with something like

'{ Hello {0}! I'm inside curly braces '}

This would work, if single-quote were an escape character like many of us are accustomed to using, for instance in regular expressions, and in Java literal strings, backslash “\” is an escape character. Of course, if single-quote were like an escape character, the above example would work and I wouldn’t be writing this post. But the single-quote isn’t an escape character.

The rules for MessageFormat escaping are most easily understood like this:

1. Strings inside single quotes are treated literally
2. Two single-quotes next to each other will be interpreted as a single single-quote, rather than an empty literal string

The understanding of single-quote as an escape character comes from the second rule. In this case, it is similar to “\\” in Java, C, Perl, etc, where to get the literal character “\” rather than an escaped string to be interpreted specially (e.g., “\n” for new line, “\u2297″ for a special Unicode character), you type the escape character twice, i.e., “\\”. However, the two single-quotes in a row are a special case, and most of the time you will use a string inside a set of single-quotes to represent a set of characters that should be ignored by the MessageFormat parser as it searches for placeholders (e.g., {0}, {1}, …).

Following these rules, to format

{ Hello {0}! I'm inside curly braces }

where {0} = “Joel”, i.e.,

{ Hello Joel! I'm inside curly braces }

We really only need to tell the parser to ignore the start and end curly braces. To do this, we will use the following pattern:

'{' Hello {0}! I'm inside curly braces '}'

And that actually works!

Now, let’s look at the problem I was trying to solve, and see if these rules can help us out. The string I was trying to format looked like this:

<label text="{ bind('dataSource=joelDS; select=text; type=ONE_WAY') }" />

I was using this string in an XModify Macro, however, such as this:

<macro:macro xmlns:macro="http://openxal.org/core/macro"
	name="addTradingTab">
	<xm:modifications xmlns:xm="http://openxal.org/core/xmodify">
		<xm:append select="id('container')">
			<label text="{ bind('dataSource={0}; select=text; type=ONE_WAY') }" />
		</xm:append>
	</xm:modifications>
</macro:macro>

Notice that the string to be appended contains a {, a }, and two ‘, all of which need to be escaped, without smothering the {0} from the parser. First lets tell the parser to ignore the first { and last }:

<macro:macro xmlns:macro="http://openxal.org/core/macro"
	name="addTradingTab">
	<xm:modifications xmlns:xm="http://openxal.org/core/xmodify">
		<xm:append select="id('container')">
			<label text="'{' bind('dataSource={0}; select=text; type=ONE_WAY') '}'" />
		</xm:append>
	</xm:modifications>
</macro:macro>

Next, lets escape the single quotes inside the parens:

<macro:macro xmlns:macro="http://openxal.org/core/macro"
	name="addTradingTab">
	<xm:modifications xmlns:xm="http://openxal.org/core/xmodify">
		<xm:append select="id('container')">
			<label text="'{' bind(''dataSource={0}; select=text; type=ONE_WAY'') '}'" />
		</xm:append>
	</xm:modifications>
</macro:macro>

We can test the above string using the MessageFormat demo provided by Sun, which runs in an applet. Entering the

<label text="'{' bind(''dataSource={0}; select=text; type=ONE_WAY'') '}'" />

line in the Pattern field, and entering “joelDS” in the 0 argument, we get:

<label text="{ bind('dataSource=joelDS; select=text; type=ONE_WAY') }" />

Wahoo, it works!

To review:

1. While MessageFormat single-quotes act like escape characters, it is much easier to think of them as a string-literal syntax
2. When in doubt, test your Macro patterns using the MessageFormat demo provided by Sun.

Legacy applications have architectural limitations that prohibit their ability to support large scale deployments. They often necessitate servers and technicians at each location with continuous client software maintenance and service, all creating redundant headcounts, resources and costs.

Application modernization toward an open, web architecture can address these technology limitations as they relate to the demands of globalization and will create new opportunities in terms of people and delivery. First, regarding the architectural limitations of legacy technologies, modernization toward an open, web architecture supports centralized deployments and zero-client installation which significantly lessens the need for local technicians, eliminates client software maintenance needs, and supports a reduction in hardware and infrastructure –consequently lessening energy requirements. From a pure software development perspective, adopting a loosely coupled architectural Web approach can reduce the time to execute a change request by 90 percent.

Secondly, modernization with Internet-based technology creates new methods of delivery and new ways to carve the resources pie. In terms of people, transformation toward an open, standardized application platform allows better utilization of a global workforce, especially from countries such as China and India. In terms of delivery, the lack of skilled IT resources against the demand will drive innovation and investment in new delivery models such as SaaS, IT process automation, and Internet-based service offerings that lessen reliance on human resources to resolve issues that can be solved in other ways.

I just presented a tutorial on Friday on using Direct Web Remoting, Hibernate and dojo.E.  It’s a very simple demo, but demonstrates the power of these three technologies combined to create simple, dynamic Java applications very quickly. The tutorial is available on SlideShare.

Note that there is a bug that obscures the URL for the SVN project.  The URL is http://source.nexaweb.com/svn/repos/trunk/tutorials/ajax/DWRExample/.

You can check out the project via SVN using this URL.

Also, to copy and paste the code snippets, download the document and open directly in PowerPoint. When copying and pasting, watch out for “smart quotes”. Some of the quotation characters in the PPT have been replaced with “smart quotes”, which are not recognized by XML parsers.

This will get even more exciting with the new features of DWR 3.0, which will add a RESTful layer to DWR’s remoting.  To learn more about DWR 3.0, I recommend Joe Walker’s presentation from The Ajax Experience last week.  He’s the lead developer for DWR.

Joel Barciauskas

What is it?

HorizontalBoxContainer and VerticalBoxContainer is a pair of layout managers that allow multiple children components to be laid out either vertically or horizontally. This is similar to BoxLayout from the Java Swing toolkit.

So, why do we need Box Containers?

Box layout is simple to understand and easy to use. It allows us to apply successful “divide and conquer” tactic to User Interface design. The allotted container space can be arbitrarily divided, say, horizontally, then, in turn, each part can be divided vertically and so on, thus leading to potentially complex UI designs.

How is that better than SplitContainer?

xBoxContainer is not intended as a replacement for SplitContainer. It is useful when you want to divide the allotted space into three or more sub-areas. Children can also be set up to resize automatically when the amount of allotted space changes.

Automatic sizing

Both managers allow top/bottom and left/right alignment or “stretch” of children components. In addition, one or more children components can define a ”flex” attribute to claim unallocated Container space. In case of many children with the ”flex” attribute, the value determines the relative elasticity of each component. For example, if one child component has a flex of 2 and another has a flex of 1, the first child component will claim twice as much space to fill the bounds of the Container.

Examples

Here are links to some examples:

VerticalBoxContainer
HorizontalBoxContainer

Source

Complete source code for both HorizontalBoxContainer and VerticalBoxContainer can be found here.

BoxContainer.zip

Legacy applications are an even bigger headache than was originally thought. The announcement of Nexaweb Advance has generated huge attention in the media and has caused a 400% jump in traffic to www.nexaweb.com over a normal 5 day period. Check out some of the coverage below:

Nexaweb offers way to move apps from desktop to Web
InfoWorld
3/3/08

Endless demand for richer experience
InfoWorld
3/3/08

Nexaweb Advance takes RIA value to the enterprise application modernization imperative
ZDNet
3/3/08

Nexaweb Advance Offers Customers Comprehensive Solution for Legacy Modernization and Enterprise Web 2.0 Adoption
Ajax Magazine

Nexaweb Offers Legacy App Migration to Java
Internet News
3/3/08

Nexaweb tool reverse-engineers legacy software
ComputerWorld Canada
3/4/08

Nexaweb tool reverse-engineers legacy software
Daily IT Wire Newsletter
3/4/08

UML tagged for SOA modernization of client/server apps
SearchSOA.com
3/4/08

Nexaweb Automates Web 2.0 Legacy Renewal
Computerwire
3/5/08

Nexaweb tool reverse-engineers legacy software
The Industry Standard
3/10/08

We’ve been working hard on a new version of our development environment and we’re releasing a beta into the world.

Some highlights:

1. Data, data, data - all work flows that interact with data integration have been overhauled
2. Supporting users that have their own Eclipse environment and don’t want ours
3. Editing our “macros” - declarative modification blocks that can be executed on the client
4. Supporting JSON visualization for data sources
5. Results from usability testing has been added in
6. and more…

If you would like to take the beta for a spin, email our support department.

Rob Gagne

I have spent the last few weeks building examples using XML on top of dojo, including an XML version of the mail application (you can see it here http://trac.dojotoolkit.org/ticket/5766).

1. Setting namespace

Since majority of the tags used are still html tag, it makes things much easier to set the default namespace to be html, in this way, there is no need to put html prefix for all the html tags. To do so, you just need to set like this:

<ui xmlns:dijit=”dijit” xmlns:html=”html” xmlns=”html”>
…
</ui>


2. Embedded JavaScript

Using embedded JavaScript can be tricky as it will be underneath the xml parser JavaScript. The solution here is to add html prefix to avoid the confusion of the inner script tag.

Example:

Original html:

<button dojoType=”dijit.form.Button” label=”Click me”>
<script type=”dojo/method” event=”onClick”>
alert(’clicked’);
</script>
</button>

Converted xml:

<ui xmlns:dijit=”dijit” xmlns=”html” xmlns:html=”html”>
<dijit:form.Button label=”Click me”>
<html:script type=”dojo/method” event=”onClick”>
alert(’clicked’);
</html:script>
</dijit:form.Button>
</ui>

It could also be solved by using CDATA as motioned in the following.

3. Inner html

Inner html may raise issue for the xml parser; there are two ways to resolve this issue.

a. Using CDATA to wrap the JavaScript code.
b. Escaping “<” and “>” by “&<” and “&>”

Example:
If we have a div defined as:

<div id=”DivExample”>
Hello World
</div>

And an html code to change the div content :

<button dojoType=”dijit.form.Button” label=”Click me”>
<script type=”dojo/method” event=”onClick”>
document.getElementById(’DivExample’).innerHTML =
“<p>Hello</p>”;
</script>
</button>

Then you can use either one of the method below to replace the html code (but not both):

a: Using CDATA

<ui xmlns:dijit=”dijit” xmlns:html=”html” xmlns=”html” >
<dijit:form.Button label=”Click me”>
<html:script type=”dojo/method” event=”onClick”>
<![CDATA[
document.getElementById('DivExample').innerHTML = "<p>Hello</p>";
]]>
</html:script>
</dijit:form.Button>
</ui>

b: Escaping “<” “>” by “&<” and “&>”

<ui xmlns:dijit=”dijit” xmlns:html=”html” xmlns=”html” >
<dijit:form.Button label=”Click me”>
<html:script type=”dojo/method” event=”onClick”>
document.getElementById(’DivExample’).innerHTML =
“<p>Hello</p>”;
</html:script>
</dijit:form.Button>
</ui>

4. Valid attribute value

For every attribute inside any node, you need to assign a value to it to be a valid xml node.

Example:

<hr noshade size=”1″> is invalid here and should be converted to:
<hr noshade=”true” size=”1″/>.

5. Table

IE is kind of picky for parsing the table tag. To use xml parser, the table must contain <tbody/> in order to display properly in IE. Also colSpan/rowSpan can not be written in all lower case colspan/rowspan.

Example:

<ui xmlns:dijit=”dijit” xmlns:html=”html” xmlns=”html”>
<table border=”1px”>
<tbody>
<tr>
<td>
<label>row 1 col 1</label>
</td>
<td>
<label>row 1 col 2</label>
</td>
</tr>
<tr>
<td colSpan=”2″ style=”text-align:center;”>
<label>row 2 col 1</label>
</td>
</tr>
</tbody>
</table>
</ui>

Without <tbody/>, it will not display in IE, but will show in Firefox. And if using “colspan” instead of “colSpan”, it will not work either for IE yet Firefox works fine.

Jing Wang