ADF Faces & JSF 2.0

[Florin POP]

I was wondering about the new direction of the Faces part ( although
it is not Oracle's part).
How and if ADF will run in a JSF 2.0 context( presuming that WLS will
be JSF 2.0 compatible)?
How ADF Faces will treat <f:ajax/>?
Will the composite components change in the context of the new
components creation using facelets?
There are a lot of question marks regarding the presentation layer (if
Oracle will stick with JSF or switch to another technology)

Florin POP

[Luc Bors]

Florin,
This is probably not the place to post your question as this group is
mainly about methodology. However, I have somewhat the same issues. At
devoxx conference I asked the question when ADF and WLS will be J6EE
and thus JSF20 compatible. The of the record and unofficial answer I
got was: 2010. One more question is if, and if so how, oracle will
support migration.
My suggestion is to take this discussion of this group. Any group
members know where to take this ?
Regards Luc

2009/12/9, Florin POP <pop.flori...@gmail.com>:

> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodolo...@googlegroups.com

--
Verzonden vanaf mijn mobiele apparaat

[Chris Muir]

Hi

I let the question through (yes, most messages are moderated, we get a
few posts that I redirect back to OTN), as I thought it a question
that didn't really suit the OTN forums. I've no issues if people want
to discuss future JDev plans here.

Regards,

CM.

[Koen]

Asked the same question at the same conference. It seems like (or I
hope) Oracle is taking this as priority #1 for future releases.
Definitely looking forward ...

Regards,

Koen

On 9 dec, 21:31, Luc Bors <lucb...@gmail.com> wrote:
> Florin,
> This is probably not the place to post your question as this group is
> mainly about methodology. However, I have somewhat the same issues. At
> devoxx conference I asked the question when ADF and WLS will be J6EE
> and thus JSF20 compatible. The of the record and unofficial answer I
> got was: 2010. One more question is if, and if so how, oracle will
> support migration.
> My suggestion is to take this discussion of this group. Any group
> members know where to take this ?
> Regards Luc
>

> 2009/12/9, Florin POP <pop.florin.nico...@gmail.com>:

[Matthias Wessendorf]

Hi,

the core of ADF Faces 11g is inside of the Apache MyFaces Trinidad
framework.

On the d...@myfaces.apache.org mailing list, things regarding Trinidad
2.0 (JSF 2 version of Trinidad)
are discussed.

HEre is a _temporary_ release notes page, for Trinidad 2.0:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12314297&styleName=Text&projectId=12310661&Create=Create

(yes, JIRA does allows that type of stuff)

So, that may also give you an idea, regarding JSF 2.0 and ADF
Faces... ;-)

Greetings,
Matthias

[Chris Muir]

One thing I'd like to know about ADF Faces/Trinidad's support for JSF
2.0 is how disruptive will it be to both existing skillsets and
existing systems. A fair criticism of JDeveloper is that it "keeps on
changing". Take the changes from UIX to ADF Faces via 10.1.2 to
10.1.3, then the near rebuild of components from ADF Faces to ADF
Faces RC via 10.1.3 to 11g plus the addition of task flows. Now
there's the risk of another major change in the JSF 2.0 additions.
This continous change is leaving a bad taste.

So, ignoring just how cool JSF 2.0 is, would anybody like to comment
on what impact JSF 2.0 will have on, say:

a) the scale of skillset retraining for those familiar with JDev 11g
b) things that we do in 11g that will have to definitely change to
accomodate JSF 2.0
c) rework/migation tasks for our 11g apps to JSF 2.0 in whatever
future release of JDev?

I'm particularly I'm interested in "c" as I'm seeing a few posts on
the JDev OTN forums on how migration between even 11g and 11gR1 is not
successful, ringing alarm bells for the future supports of JSF 2.0.
In turn I'd be interested in things we could do to "futureproof" our
current developments to minimize redevelopment in the newer JSF 2.0
version.

I must admit I have no experience in JSF 2.0, and may be being over
alarmist in this post, but it would be good to hear something soothing
from Oracle to calm my fears, or least my clients.

Cheers,

CM.

[Simon Haslam]

My view would be that ADF 11g is "good enough" for custom enterprise
apps for the time being and that both ADFc/task flows and templates
have worked around some of the limitations in JSF 1.2. There was a big
hit, UI-wise, in going from 10.1.3 to 11.1 but then there were big
benefits too - I'd need some convincing that JSF 2.0 would bring the
same.

One of the advantages for customers adopting Oracle's ADF ought to be
platform stability - there are lots of competing toolsets/frameworks
but I don't think "enterprise" customers have the time or money to
keep rebuilding applications. In my experience, typically an
application is built in response to an initial set of requirements
(and business case) and then has a relatively long life with often
fairly minor change requests. You only need to look at most Forms
applications out there to see that. I suppose it's different for ISVs
where there's a steady revenue stream and customer demand for the
latest features.

Of course in theory, being a metadata-driven framework it shouldn't
matter too much what's underneath (JSF 2.0, Flex, JavaFX etc), but in
practice I expect that level of abstraction is very difficult to
achieve.

The main comfort factor for me is that there is now a juggernaut
development built on 11g so, whatever happens with JSF 2.0, Oracle is
going to have to have a super-slick migration process and provide
support/enhancements to ADF 11g for some considerable time.


Simon

[Sten Vesterli]

I agree with Simon:
a) Before ADF Faces Rich Client, we did not have a "good enough"
selection of UI components, but we have now. No need to drop existing
development waiting for cool new JSF 2.0 components
b) Oracle has built a lot of stuff using Rich Client, so if and when
they go to JSF 2.0, they'll offer a good migration path

Furthermore, Oracles answer to the eternal Flex/SilverLight question
has always been: That's for us to worry about, not for you as a
developer. Just keep using the components and we might offer to render
them differently. Same thing here.

Cheers

Sten Vesterli