Re: [jsr-314-open-mirror] [jsr-314-open] [490-XmlViews] Chapter 11: The JSF XML View Syntax
by Ed Burns
>>>>> On Fri, 22 Oct 2010 09:23:33 +0700, Cay Horstmann <cay.horstmann(a)gmail.com> said:
CH> As I had understood it, the need for XML was motivated by these usecases:
CH> 1) To allow developers to use standard XML processing tools. In
CH> particular, this requires to be truthful about the nature of the
CH> documents (i.e. not claim that something is an XHTML file when it
CH> isn't, but is really an artifact that will eventually be transformed
CH> into XHTML)
...and the most important manifestation of that, in my opinion, is the
requirement to have *all* elements prefixed. For example, a proper JSF
XML Syntax View would look like this.
<?xml version="1.0" encoding="UTF-8"?>
<weNeedSomeRootElement
xmlns:html="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html">
<h:html>
<h:head><h:title>Raw XML View</h:title></h:head>
<h:body>
<html:h2>XML declaration: consumed</html:h2>
<html:h2>Processing instruction: consumed</html:h2>
<?xml-stylesheet href="funky.xsl" type="text/xml" alternate="yes"?>
<html:h2>CDATA section: consumed</html:h2>
<![CDATA[ <p>This is CDATA</p> ]]>
<html:h2>Comments: consumed</html:h2>
<!-- comments consumed -->
<h:form prependId="false" id="form">
<h:panelGrid id="grid" column="2">
<h:outputText id="text" value="hello" />
<h:commandButton id="button" value="reload" />
</h:panelGrid>
<html:p>html template text</html:p>
</h:form>
</h:body>
</h:html>
</weNeedSomeRootElement>
CH> 2) To not surprise developers with nonstandard XML processing (such as
CH> processing comments).
I'm not sure what you mean here. XML processing instructions are
standard in XML.
--
| edward.burns(a)oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/
| 14 work days until German Oracle User's Group Conference
14 years, 2 months
Re: [jsr-314-open-mirror] [jsr-314-open] Fwd: Fix UIData state saving model
by Ed Burns
>>>>> On Fri, 27 Aug 2010 16:32:21 -0500, Leonardo Uribe <lu4242(a)gmail.com> said:
LU> The OCA was filled. I hope it will be no problem with share this
LU> contribution with myfaces.
I'm about ready to commit the feature to Mojarra head.
I've added the test app and an HtmlUnit driver. Very nice test app.
I just have to slap the standard copyright header on things before
commiting.
Ed
--
| edward.burns(a)oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/
| 7 work days until handoff of JSF 2.1 change log to jcp
14 years, 2 months
[jsr-314-open-mirror] [jsr-314-open] [777-FaceletCache] RESOLVED (was: [2.1 Spec Review] FaceletCache issues)
by Ed Burns
>>>>> On Thu, 21 Oct 2010 16:26:48 -0400, Andy Schwartz <andy.schwartz(a)oracle.com> said:
AS> Some additional issues that turned up while reviewing the API doc:
AS> 1. FaceletCache and FaceletCacheFactory are missing documentation.
AS> The original (Mojarra implementation-specific) version of this
AS> functionality does include documentation, but that doesn't seem to have
AS> carried over into the public API.
DONE.
AS> 2. The doc in FaceletCache.MemberFactory is incorrect
AS> The class doc says: "Factory interface for creating FaceletHandler
AS> instances." However, we're actually creating Facelet instances, not
AS> FaceletHandler instances.
DONE.
AS> 3. Wider access than necessary for some methods in FaceletCache
AS> The original (Mojarra-specific) version of this functionality exposes
AS> the following methods:
AS> public final void init(InstanceFactory<V> faceletFactory,
AS> InstanceFactory<V> metafaceletFactory)
AS> protected final InstanceFactory<V> getFaceletInstanceFactory()
AS> protected final InstanceFactory<V> getMetadataFaceletInstanceFactory()
AS> The equivalent methods in the new public API are:
AS> public void setMemberFactories(MemberFactory<V> faceletFactory,
AS> MemberFactory<V> viewMetadataFaceletFactory)
AS> public MemberFactory<V> getMemberFactory()
AS> public MemberFactory<V> getMetadataMemberFactory()
DONE.
--
| edward.burns(a)oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/
| 12 work days until German Oracle User's Group Conference
14 years, 2 months
Re: [jsr-314-open-mirror] [jsr-314-open] [2.1 Spec Review] ViewHandler.FACELETS_SUPPRESS_XML_DECLARATION
by Ed Burns
>>>>> On Tue, 19 Oct 2010 14:21:08 -0400, Andy Schwartz <andy.schwartz(a)oracle.com> said:
AS> This constant is specified in the 20101013 version of the spec
AS> (JavaDoc). I believe that we can remove this now as this functionality
AS> is covered by the new Facelets processing mode.
I do sympathize with your distaste for the redundancy this brings, but I
submit this request is so common that such redundancy is warranted. Not
everyone will want to go the hog and specify <facelets-processing>.
Therefore, unless you or someone else feels strongly about it, I will
leave this in.
Ed
--
| edward.burns(a)oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/
| 12 work days until German Oracle User's Group Conference
14 years, 2 months