Component API still has one unimplemented method in UIComponent (I am
working on it as we speak, I will probably have it finished next week! -
you probably cann add the missing part to partial state saving though!)
Werner
Leonardo Uribe schrieb:
Hi
Just as a brief review, this is an updated list about the state of
myfaces core 2.0.0 branch:
Pending tasks
- Facelets PDL
- Client behavior API (depends from facelets and composite component stuff)
- Error handling API (and run through existing classes to make sure the
new exception specification is enforced)
- Partial view API
- Partial State Saving
- Add Flash scope
- New tags (mostly linked to Facelets)
- Unit tests (conversion shale -> myfaces code)
Done tasks (some parts maybe requires testing or minor updates)
- Resource API
- Annotation support
- h:outputScript and h:outputStyleSheet renderer
- Config ordering
- JavaScript API
- Tree visiting API
- SystemEvent API
- New validators (Bean and regex mainly)
- Utility methods (ExternalContext mainly) (requires testing)
regards
Leonardo Uribe
2009/6/9 Leonardo Uribe <lu4...@gmail.com <mailto:lu4...@gmail.com>>
Hi
Good to hear that facelets part will be committed soon. I hope to
start working on javax.faces.behavior api and continue contribute on
other parts of myfaces core 2.0 (for example implement partial state
saving) as soon as tomahawk be released (planned on next week).
regards
Leonardo Uribe
2009/6/9 Simon Lessard <simon.lessar...@gmail.com
<mailto:simon.lessar...@gmail.com>>
We use the Facelets codebase, we just have to rename the package
(already done), use the HandlerDelegate ... thing ... and
implement the Facelets VDL. Those are not part of "standard"
Facelets with existing ASL 2.0 code.
~ Simon
On Tue, Jun 9, 2009 at 11:22 AM, Matthias Wessendorf
<mat...@apache.org <mailto:mat...@apache.org>> wrote:
On Tue, Jun 9, 2009 at 8:20 AM, Ganesh<gan...@j4fry.org
<mailto:gan...@j4fry.org>> wrote:
> Hi,
>
> Facelets are apache 2.0 licensed,
correct
> why do we reinvent them?
they added stuff for JSF 2.0
e.g. <composite:interface> etc
(but didn't put it into the Apache licensed version)
>
> Best regards,
> Ganesh
>
> Simon Lessard schrieb:
>>
>> Hi,
>>
>> On my side I'll try to work and finish Facelets part
within 2 weeks, fater
>> than that is impossible for me atm.
>>
>>
>> Regards,
>>
>> ~ Simon
>>
>> On Tue, Jun 9, 2009 at 9:53 AM, Werner Punz
<werner.p...@gmail.com <mailto:werner.p...@gmail.com>
>> <mailto:werner.p...@gmail.com
<mailto:werner.p...@gmail.com>>> wrote:
>>
>> Matthias Wessendorf schrieb:
>>
>> regarding tree visitor, this may help:
>>
>> https://issues.apache.org/jira/browse/TRINIDAD-1368
>>
>> Thanks for the link, I will get it and compare it to
what I have...
>> I assume there wont be too much which I still can
integrated in
>> the PartialVisitContext since I am rather optimized
already and
>> bound by the spec!
>>
>>
>> Werner
>>
>>
>>
>>
>>
>> -Matthias
>>
>> On Tue, Jun 9, 2009 at 6:37 AM, Werner
>> Punz<werner.p...@gmail.com
<mailto:werner.p...@gmail.com> <mailto:werner.p...@gmail.com
<mailto:werner.p...@gmail.com>>> wrote:
>>
>> Michael Concini schrieb:
>>
>> Wasn't there a plan to have some of the
partial tree
>> traversal work done
>> as part of the Google Summer of Code? I
seem to
>> recall some discussion
>> around this awhile back (don't have time
to dig
>> through the mailing list
>> archives right now to check). Does
anybody remember
>> what the plan was with
>> Google SoC?
>>
>> Interesting question, but I assume I only
have a small
>> subset of the needed
>> functionality implemented, the one we need
for PPR so,
>> I will commit my tomorrow as soon as I have
tested it,
>> whoever wants to do
>> something in GSOC can pick it up and refine
it. But have
>> in mind, my work
>> currently only coveres the area of providing a
>> PartialVisitContext so that I
>> have a complete state for PPR in this area!
>> If someone comes with a better solution I
dont have any
>> problem dropping the
>> code again ;-)
>>
>>
>> Werner
>>
>>
>>
>> Werner Punz wrote:
>>
>> Michael Concini schrieb:
>>
>> All,
>>
>> I thought it might be a good time
to raise the
>> issue of solidifying a
>> plan for the MyFaces 2.0 alpha
release now
>> that we've had a little time to
>> work with the release candidate
draft of the
>> spec. What are the thoughts in
>> the community with respect to
what should be
>> included in an alpha release as
>> well as what the time frame
should be for a
>> release. If we can come up with
>> a target date as well as specific
2.0 features
>> we want to target for
>> inclusion, that should help in
prioritizing
>> the remaining work.
>> From my end, I'd love to see a
working
>> runtime in some form by the end
>> of August if that's reasonable.
As for
>> content, that is definitely more of
>> an open question. Here is my top
list of what
>> I would like to see be at
>> least partially functional for an
alpha release.
>> -backwards compatibility with JSF
1.x apps
>> -base support for facelets and
composite
>> components
>> -AJAX support (should hopefully
be in pretty
>> good shape here thanks to
>> Ganesh and team)
>> -System event support
>> -Partial view traversal
>>
>> Thoughts/concerns/objections?
>>
>> -Mike
>>
>> None from my side not sure how far
Ganesh is with
>> his ajax tag!
>> The scripts already are in pretty
good shape and
>> functionalitywise well
>> ahead of the RI ;-)
>>
>> As for partial Tree traversal minor
sidequestion?
>> Has anyone started to
>> work on this, because I have started
to implement
>> the partial visit context
>> (I have to recheck the jira for this,
because I
>> opened an issue for this
>> under partial render response issue
2116/2241)!
>>
>>
https://issues.apache.org/jira/browse/MYFACES-2241
>>
>> I will commit my code around
tomorrow, it is
>> basically done
>> but needs some testing!
>>
>>
>>
>> Werner
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
