Re: [jsr-314-open] [jsf2.next] <h:head> vs. <head>
by Ed Burns
>>>>> On Tue, 15 Dec 2009 11:30:32 -0500, Andy Schwartz <andy.schwartz(a)oracle.com> said:
AS> I've been wondering whether the requirement to use <h:head> instead of
AS> plain old <head> (eg. in order to pick up the jsf.js when using
AS> <f:ajax>) might be an annoyance for folks who prefer the .xhtml/template
AS> text approach of view definition. If this is annoying, we could
AS> consider removing this requirement, eg. might be able to transparently
AS> turn HTML <head>/<body> into the corresponding components.
For the record, we prototyped this way back in February of 2008 and ran
into some trouble, but I think it could have been worked around.
>>>>> On Tue, 15 Dec 2009 13:26:53 -0800, Jim Driscoll <Jim.Driscoll(a)Sun.COM> said:
JD> Could someone please file this as a spec RFE?
JD> We'll have to do a performance test to really see the implications, but
JD> it does seem like it would be useful to have this.
Roger created 702, which I've marked as a dup of Dan's 700. Also
important is the existing 468, which is for people that want to do their
own <head> yet put something like <h:relocationTarget> in there.
Dreamweaver types wanted this.
Ed
--
| ed.burns(a)sun.com | office: 408 884 9519 OR x31640
| homepage: | http://ridingthecrest.com/
14 years, 11 months
[jsr-314-open] [jsf2.next] Pluggable VDL handler heavy depends from ViewHandler implementation.
by Alexander Smirnov
Recently, I've encouraged some fellows to implement JavaFX VDL (
http://alexsmirnov.wordpress.com/tag/javafx/ ), and we got inconsistent
requirements in the spec that makes ViewDeclarationLanguage
implementation close depended from ViewHandler implementation.
Description of the ViewHandler#writeState says:
public void writeState(FacesContext context) throws IOException;
Take any appropriate action to either immediately write out the
current view’s state information (by calling
StateManager.writeState()), or noting where state information may
later be written.
There are no requirements for viewHandler implementation how to write
state late.
On the other hand, default implementation should call
ViewDeclarationLanguage#renderView method that creates appropriate
writer and put actual state. Therefore, it is not possible to introduce
custom ViewDeclarationLanguage without ViewHandler modifications.
Possible solutions are:
1) Introduce ViewDeclarationLanguage#writeState method that should be
called from ViewHandler#writeState in the same way as renderView method
does.
2) Change default ViewHandler#renderView method requirements that it
should create appropriate ResponseWriter before calling
ViewDeclarationLanguage#renderView method, so ViewHandler can perform
late state writing in consistent way.
I prefer to the #2 solution because that allows to reduce duplicated
code in the ViewDeclarationLanguage implementations, but there is a
problem: VDL may provide additional options for response like buffer
sixe, encoding and content type that required to create ResponseWriter.
Possible solution is to make public
ViewDeclarationLanguage#createResponseWriter(FacesContext context)
method that already exists in the Mojarra implementation.
14 years, 11 months
[jsr-314-open] [jsf2.next] WITHDRAWN Proposal to support new semantic HTML5 tags
by Ed Burns
>>>>> On Sat, 12 Dec 2009 23:08:59 -0800, Jim Driscoll <Jim.Driscoll(a)Sun.COM> said:
JD> For the most part, no. The exceptions appear to be noted in the article
JD> (but, I haven't reviewed the HTML5 spec - it ironically causes Firefox
JD> to crash whenever I try).
JD> So instead of saying <div class="nav">, you instead say <nav>
JD> However, it turns out that there's serious problems with using these
JD> tags, at least according to John Resig (I attended a talk he gave on
JD> Friday).
JD> While the HTML5 shiv referenced below will allow these tags to work in
JD> IE in the basic case, there are still two problems: 1) they won't nest,
JD> and 2) innerHtml won't work with these tags.
JD> So, given those problems, I withdraw the proposal. Since these problems
JD> occur in IE8, it looks like these tags may be as far as 5 years away
JD> from being usable. Tragic.
Withdrawl noted and agreed.
Ed
--
| ed.burns(a)sun.com | office: 408 884 9519 OR x31640
| homepage: | http://ridingthecrest.com/
14 years, 11 months
Re: [jsr-314-open] [ADMIN] java.net hacking after-effects: ChangeLog missing
by Ed Burns
>>>>> On Mon, 04 Jan 2010 17:07:36 -0500, Roger Kitain <Roger.Kitain(a)Sun.COM> said:
RK> HI Imre -
RK> Thanks for digging this up.
RK> I see 54 issues listed here which is a lot better than 24 listed on
RK> java.net site.
RK> As a last resort I think I can get these into a new change log.
Great. Let's see what the O'Reilly people have to say for us before we
undertake any squinting exercises.
Ed
--
| ed.burns(a)sun.com | office: 408 884 9519 OR x31640
| homepage: | http://ridingthecrest.com/
14 years, 11 months
[jsr-314-open] [ADMIN] java.net hacking after-effects: ChangeLog missing
by Ed Burns
I sent this to Sun's internal program team that manages JSF. I'm Cc'ing
here for your information.
EB> Roger and I discussed this on the phone and he has agreed to own the
EB> task of resolving this issue.
EB> As I had feared, the version of the JSF 2.0 changelog that was restored
EB> after the attack is not the most current one. Looking at [1], you can
EB> clearly see that the version is hopelessly out of date: the highest
EB> issue id is C0024. I know we were up around C0048.
EB> I also discovered that the RealWorldJsfLinks page is out of date [2],
EB> but thankfully I found that google's cache had a version that was more
EB> recent. I'm in the process of fixing it now.
EB> ACTION: Roger, can you please make it so [1] has the correct recent
EB> state, as of the date of the attack?
EB> This task must be completed before we can move forward with the "errata"
EB> MR, which we loosely promised (and Dan Allen quickly re-tweeted) in the
EB> Jan-Feb timeframe.
EB> [1] http://wiki.java.net/bin/view/Projects/Jsf2MR1ChangeLog
EB> [2] http://wiki.java.net/bin/view/Projects/RealWorldJSFLinks
Ed
--
| ed.burns(a)sun.com | office: 408 884 9519 OR x31640
| homepage: | http://ridingthecrest.com/
14 years, 11 months
[jsr-314-open] Test
by Andy Schwartz
Sorry for the spam. Temporarily switching to my gmail address for
jsr-314-open as it appears that some traffic may not be making it to
my Oracle address.
Andy
14 years, 11 months
[jsr-314-open] [jsf2next] PROJECT_STAGE system property configuration
by Lincoln Baxter, III
I'd like to revisit this for JSF2.1 -
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=499
Project stage is something that needs to be configurable without
modifying the underlying WAR (and while JNDI support is provided, it
requires container configuration, admittedly not a huge downside.)
However, for those who do not primarily use JNDI for configuration, a
-D system property makes a lot of sense.
I'd also like to propose one other enhancement, which is runtime
configuration of the PROJECT_STAGE through an exposed API. This is
something that I think should be able to turn on and off while the
server is running (For the same reason it must be possible to enable
or disable debug logging or auditing at runtime.)
A simple API on javax.faces.application.Application to grant
functionality of setting PROJECT_STAGE. This is something that is very
easy for us to do, but also grants extreme flexibility, allowing
people to use it how they please.
public void setProjectStage(ProjectStage) {
...
}
Thoughts?
Thanks,
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
14 years, 11 months
Re: [jsr-314-open] wrap ups of JSF Summit 2009
by Ed Burns
>>>>> On Wed, 16 Dec 2009 22:09:58 -0500, Dan Allen <dan.j.allen(a)gmail.com> said:
DA> On Wed, Dec 16, 2009 at 9:49 PM, Andy Schwartz <andy.schwartz(a)oracle.com>wrote:
>> Dan Allen wrote:
>>
>>> I look forward to reading about the conference through another
>>> perspective.
>>>
>>>
>> Here's another, covering JSF Summit + the 3 other conferences that I
>> attended this fall:
>>
>> http://andyschwartz.wordpress.com/2009/12/17/jsf-2-on-the-road/
>>
>> Though be warned: I come from the "It's my stupid blog so I'll make it as
>> long as I want thank you very much" school of blogging. :-)
>>
DA> Wow! Should we give that a book cover and publish it? Hehehe. Looking
DA> forward to reading it.
DA> Hey, does anyone have the picture of the JSF EG at the end of JSF Summit on
DA> their camera? I never saw a tweet about it (or I missed it).
I recall that was on Andy's camera, before he dashed to the airport.
Ed
--
| ed.burns(a)sun.com | office: 408 884 9519 OR x31640
| homepage: | http://ridingthecrest.com/
14 years, 11 months
