Do you have production 11g applications? - ADF Enterprise Methodology Group

Message from discussion Do you have production 11g applications?
Received-SPF: neutral (google.com: 208.97.187.133 is neither permitted nor denied by best guess record for domain of av...@avromroyfaderman.com) client-ip=208.97.187.133;
Message-ID: <6a6de7b7dc43060967dcf4e5545f21be.squirrel@webmail.avromroyfaderman.com>
In-Reply-To: <4A32578D.4080107@quovera.com>
References: <b9174ba7-1aca-4b8e-9c68-d6d4263f240c@default>
    <4A31A7D3.5070708@quovera.com> <4A32578D.4080107@quovera.com>
Date: Fri, 12 Jun 2009 13:27:15 -0700
Subject: Re: [ADF Enterprise Methodology Group] Re: Do you have production 
 11g  applications?
From: "Avrom Roy-Faderman" <av...@avromroyfaderman.com>
To: adf-methodology@googlegroups.com
Cc: "DUNCAN MILLS" <duncan.mi...@oracle.com>,
	"Avrom" <av...@avromroyfaderman.com>,
	"Avrom Roy-Faderman" <aroyfader...@quovera.com>,
	"Peter" <peter_kolet...@compuserve.com>
User-Agent: SquirrelMail/1.4.19
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit

One page apps are the coolest. I haven't been able to put any 11g apps in
production, since all of my current clients are too heavily invested in
Portal to move to WLS, but theoretically it should be possible to make any
app one page (more or less using the page as you'd use a template, just to
provide a frame [in the non-technical sense] for everything else to run
on). I don't know what the performance implications of this are for large
apps (never having made a large app this way--I should emphasize that I
don't know it's bad; it's just that I don't know it isn't bad), but 0
full-page refreshes=mondo desktop app feel.

> John brings up some interesting points.
>
> At my current client we're getting incredibly close to production for our
> first ADF 11g application, and its a corker at 1 page! (ok, there's a bit
> of
> sophistication in that 1 page app, but still only 1 page).  I'm sure a 1
> page app would be a poster child for your needs Shay, it's even got a
> spinnng icon! ;-)
>
> In adopting ADF my client has taken the recommendation on board to start
> small and build up skillsets, resources and similar.  However like John
> indicates, the adoption of ADF is slowed by other peripheral activities,
> tools etc.  WLS has certainly been a learning curve.  The introduction and
> setup of SVN is another, and its disruption of the current change control
> processes.  I've also put a lot of emphasis into teaching teams to do
> proof-of-concepts to see how things do and can work, as well as how to
> write
> design documents that assist the ADF development process.  This all takes
> time.
>
> There have also been 3 other main limiters in our ability to do more:
>
> 1) the organisation has a substantial Forms legacy system + other systems
> to
> maintain; these continously pull team resources away. ADF is still niche,
> not core to their dev strategy purely because of the scale of the legacy
> system
> 2) there are virtually zero other ADF resources available internally and
> externally in the local market. Java resources are somewhat available, but
> to be honest I'm not overly keen to introduce them as they're first
> reaction
> to ADF is usually immature
> 3) continous issues of Forms is more than capable of providing
> "good-enough"
>%2