Adam,

now I have compiled the trunk version, but a noted that pom is indicating version 1.0.2-SNAPSHOT...
And I need to change some generics to compile with jsf 1.2 ri...

Bruno

Bruno E. Grossi wrote:
Adam,

my version with that lines was retrived from https://svn.apache.org/repos/asf/myfaces/trinidad/branches/faces-1_2-070427/trinidad, in May 10. There is some old, and we are updating only to get "type" on script tags.

Bruno

Adam Winer wrote:
Bruno, I suspect you have some old code lying around
on the classpath.

That said, for the 1.2 version of Trinidad, 1.2.1-SNAPSHOT
is not the most up-to-date version - that'd be the 1.2.1 release.

I'm very curious what version you've been using, because the
lines you're referring to have been absent since some time
in May, IIRC.

-- Adam


On 7/12/07, Bruno E. Grossi <[EMAIL PROTECTED]> wrote:

 Simon,

 I updated trinidad to a snapshot version
(http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/trinidad/trinidad-api/1.2.1-SNAPSHOT/trinidad-api-1.2.1-SNAPSHOT.jar)
from 05-Jul-2007, but I have an error.

 On UIXComponentUINode.__getAdapter(UIComponent component)
(line 439), I have a ClassCastException because __getUINode(component)
method returned an UIComponentUINode for an HtmlTableLayout subclass
component, when __getAdapter(..) expected an UIXComponentUINode.
Investigating that error, I see that Faces Bean isn't instance of
UINodeFacesBean, that forces an construction of an UIComponentUINode.

I observed that faces-bean.properties was changed from my last version,
removing some lines:
org.apache.myfaces.trinidad.component.UIXSingleStep=org.apache.myfaces.trinidadinternal.uinode.nav.SingleStepFacesBean org.apache.myfaces.trinidad.component.html.HtmlCellFormat=org.apache.myfaces.trinidadinternal.uinode.UINodeFacesBean org.apache.myfaces.trinidad.component.html.HtmlRowLayout=org.apache.myfaces.trinidadinternal.uinode.UINodeFacesBean org.apache.myfaces.trinidad.component.html.HtmlTableLayout=org.apache.myfaces.trinidadinternal.uinode.UINodeFacesBean org.apache.myfaces.trinidad.component.html.HtmlScript=org.apache.myfaces.trinidadinternal.uinode.UINodeFacesBean org.apache.myfaces.trinidad.component.core.data.CoreTree=org.apache.myfaces.trinidadinternal.uinode.UINodeFacesBean

 When I add that lines, there are no problems.

 Questions:
 1- Why we need that lines? Why we need to force UINodeFacesBean??
 2- It's need to all UIX components?
 3- Why that lines was removed?
 4- It´s a bug?


 Thanks,
 Bruno E. Grossi



 Simon Lessard wrote:
Err get the nighty build from that url, sorry:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/trinidad/


On 7/11/07, Simon Lessard <[EMAIL PROTECTED]> wrote:
> Hello Bruno,
>
> You can find the source at
http://myfaces.apache.org/trinidad/source-repository.html
>
> As for the nighty builds they can be found at
http://myfaces.zones.apache.org:8081/continuum/projectGroupSummary.action?projectGroupId=13
>
>
>
> Regards,
>
> ~ Simon
>
>
> On 7/11/07, Bruno E. Grossi < [EMAIL PROTECTED]> wrote:
> >
> > Simon,
> >
> > where I find that nighty build, and the source?
> >
> > Thanks,
> > Bruno
> >
> >
> > Simon Lessard wrote:
> > Hello Bruno,
> >
> > Latest nighty build fix the missing type attribute error. The name
attribute error still hold true though. We keep up work to make the
generated markup more standard compliant, but the best workaround you have
for now is to help us with the renderers I fear.
> >
> >
> > Regards,
> >
> > ~ Simon
> >
> >
> > On 7/11/07, Bruno E. Grossi <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi,
> > >
> > > we're validating our JavaEE framework (Powerlogic's jCompany 5.0) to
pass W3C Markup Validator as Strict HTML/XHTML and we found some errors
generated by Trinidad (branch 1.2):
> > >
> > > 1- <tr:form> generates an invalid attribute "name" on <form> tag.
> > > 2- Generated <script> tags don't have a "type" attribute:
> > >
> > > "Error Line 20 column 7: required attribute "TYPE" not specified.
<script>
> > >
> > >
> > >
> > > The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types
the "type" attribute is required on the "script" element and the "alt"
attribute is required for the "img" element.
> > >
> > > Typical values for type are type="text/css" for <style> and
type="text/javascript" for <script>."
> > >
> > >
> > > There are any solution (option or workaround) to solve that problems?
> > >
> > >
> > >
> > > Thanks,
> > > Bruno E. Grossi
> > >
> >
> >
> >
> >
>



Reply via email to