Search SOA2WORLD

Search Results

Wednesday, August 17, 2011

Oracle SOA Certified Expert - Breaking Silence!


After a long silence, there has been something interesting which added new knowledge to my technical skills, and this time a little unusual that I even get to get certified in that new technology.

On August 17th 2011, I finally got certified as a "Oracle Service Oriented Architecture Infrastructure Implementation Certified Expert" or (1Z0-451) certified with 83%, thanks for all the guidance I received from my (ex) SOA R&D team members.

It has been a proud moment for me after a long time the last time when I had such a moment was when we were asked to take "IBM SOA Associate" the next day, which was done on October 31st 2007, even though
I received many other certifications from Expert-Exchange at regular intervals these official certifications have been some what special and thrilling (as we need to take up a exam).



We (SOA R&D Team members at THBS) had a great exposure toward various rising trends of SOA & Cloud Computing, I can proudly say that it was the BEST team I may ever get with undefined boundaries for learning, exposure and experience. I miss my old team mates but will not forget the learning we had together as a team.


Tuesday, March 30, 2010

My Review on Flex 4 and Flash Builder 4



My Explanation for some topics which need clarifications:

The Good:

1) The Two Way Binding : bi directional binding can now be achieved easily, below are the two ways to do it in Flex 4.

a) using @ before the binding string.

<?xml version="1.0" encoding="utf-8"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:s="library://ns.adobe.com/flex/spark"

xmlns:mx="library://ns.adobe.com/flex/mx">

<s:TextInput x="145" y="59" id="textInput1"/>

<s:TextInput x="145" y="89" text="@{textInput1.text}"/>

<s:Label x="91" y="67" text="Text 1 :"/>

<s:Label x="94" y="96" text="Text 2 :"/>

</s:Application>


b) using fx:Binding with twoWay = "true".


<?xml version="1.0" encoding="utf-8"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:s="library://ns.adobe.com/flex/spark"

xmlns:mx="library://ns.adobe.com/flex/mx">

<fx:Binding source="textInput1.text" destination="textInput2.text" twoWay="true" />

<s:TextInput x="145" y="59" id="textInput1"/>

<s:TextInput x="145" y="89" id="textInput2"/>

<s:Label x="91" y="67" text="Text 1 :"/>

<s:Label x="94" y="96" text="Text 2 :"/>

</s:Application>


2) The support for Zend AMF for PHP is a nice move.

3) The Network Monitor and Flex Unit are really helpful, just wish network monitor would have supported SSL.

4) Auto Generation of event handlers and generate form options are nice.


The Bad:

1) Namespace Mess, three default namespaces and allowing mixing of elements badly affects Code readability. As we can create our own namesapce the over all code will be almost unreadable once the source size increase.


xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:s="library://ns.adobe.com/flex/spark"

xmlns:mx="library://ns.adobe.com/flex/mx"

xmlns:myComponenets="test.*"

2) Multiple SWF Mess, breaking them in to smaller SWFs but including necessary ones for a given app might have been better, currently by default all these SWFs are included. Below listed are the default swf files that will be added to your project.

framework_4.0.0.14159.swf
osmf_flex.4.0.0.13495.swf
playerProductInstall.swf
rpc_4.0.0.14159.swf
spark_4.0.0.14159.swf
sparkskins_4.0.0.14159.swf
textLayout_1.0.0.595.swf

3) Blank MXML application swf size 70KB, minimum application deployment size 2.2 MB. The over all size of Flex application is becoming heavy, gradually will become even more heavier if we start using frameworks.

4) I don’t think fx:library or fx:definition and fx:private are of any use better of using Embed Style class objects as they can be addressed from other MXML files, when made public or using getter and setters.

<?xml version="1.0" encoding="utf-8"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

xmlns:s="library://ns.adobe.com/flex/spark"

xmlns:mx="library://ns.adobe.com/flex/mx"

>

<fx:Library>

<fx:Definition name="MyLogo">

<s:BitmapImage source="@Embed('logo40.png')"/>

</fx:Definition>

</fx:Library>

<!-- Way to use a resuable resource -->

<fx:MyLogo/>

<fx:MyLogo/>

<fx:MyLogo/>

</s:Application>

You cannot access the MyLogo outside this MXML file. Instead you can use the Class Object Embed style of Flex 3 and make reusable resources accessible across the project.

5) No pinned full screen as in Silver Light 4. Also no input accepted in full screen mode yet. Regarding the pinned full screen mode there is a deatiled video tutorial at
http://www.silverlight.net/learn/videos/all/fullscreen-window-pinning/

6) Uniformity in Container behavior is lost like Border Container vs. Group, Group has no Visual representation it almost like a logical grouping of components only.

7)Not easy to code without Flash Builder. Creating Style sheets is another pain, this point I think every one accepts, now it has become even more prominent as you can't place the elements where ever you wish have to follow certain order, like you can't where ever you want it has to the last child of your MXML only.

8) Flash Builder 4 HTTP service consumption code generation is buggy, and not easy to fix, it by default passes query param names as 0 and 1, instead of the param names you mention and worst case is the fact that it passes correct params in the new "Test Operation Tab" and on the browser something else all together. But when you use the "Data Services" -> Generate form wizard every thing will be fixed for you.

9) Flash Builder 4 code generation is still no where close to Java code generation in eclipse, neither the copy paste b/w mxml files is error free as it can’t differentiate b/w visual components and service calls. Neither is the action script getter setter generation, you can only select one field and generate its getter and setter.

10) Custom skinning using skinClass (mxml style) is good, but not sure how useful it is for designers (who generally only deal with CSS), in fact it’s really not easy to code until you know the internals of the application skinning. Creating a new skin in this way needs you to do some good research as I am not sure if there is any detailed document explaining this.

11) Syntax for defining a layout for a given container is not kind of unreadable as they are elements of the same parents unlike attributes in previous Flex versions. Generally I would expect only the visual child elements to be part of my parent unlike it's own properties.

12) A additional covering tag is required for each child in a mx:View Stack for navigating across spark components, instead they could have released a complete set of Spark components.

The Ugly:


1) No
support for WSDL 2 or SOAP 1.2 yet.

2) No HTTP PUT or DELETE directly from Client yet!

3) The way Flex use to handle scroll bar was awesome, and was something which was missing in Swing, and now its again back to swing style, where you need to take care of your scroll bar, common whats wrong with Adobe?


4) No complete support to Ruby or ASP.NET yet, I think this will be coming in sooner as Ruby and ROR have gained enough popularity.