The error is unrelated to the file properties.
Jsf is looking for "cidadesController.items" and there is not found.
Check the content of cidadesController, AbstractController.
Check annotations @Named(value = "cidadesController") @SessionScoped
Check method:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-09-01
I was using 4 glassfish with netbeans 7.3. When I moved to glassfish 3, it worked. But the outputText tags appear some warnings regarding the attributes of entities, for example:
<p:column sortby="#{item.id}" filterby="#{item.id}"> / * property * /
<f:facet name="header">
<h:outputtext value="#{bundle.ListCidadesTitle_id}">
</ f: facet>
<h:outputtext value="#{item.id}">
</ p: column></h:outputtext></h:outputtext></f:facet></p:column>
Yes, it does work. The code you're looking at refers to a property inside an abstract class which its attributes are not known to the editor's introspection. Does that make sense?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-09-20
closed topic.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The <p:selectBooleanCheckBox> only get generated if the entity has an actual boolean field. Boolean is not an SQL data type in every database. MySQL has the BIT datatype, and that works. Also, PostgreSQL has a BOOLEAN datatype that represents TRUE and FALSE values. That one works too and your entity will have a boolean field.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-09-21
I have an entity named CITY in my web project. There is no boolean attributes in this entity. Until here, all right. The generator had to create its respective xhtml pages for this entity (create, edit, list and view.xhtml). In the code of list.xhtml, more specifically, in the p:datatable code, the netbeans editor shows some warnings regarding to attributes of CITY entity (i.e., ie, the attributes that are not recognized), that you, Kay Wrobel, explained to me that this is a behavior of editor itself. Ok, think better after, I agree. The code is running perfectly, it´s great to me. I just thought if anything could be done so that these warnings were eliminated. Only that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I change any entry in bundle.properties, an example, MAINTENANCE=MAINTENANCE, for MAINTENANCE=SHOW, presents an error:
FATAL: JSF1073: javax.el.ELException obtido durante o processamento de RENDER_RESPONSE 6: UIComponent-ClientId=, Message=/cidades/List.xhtml @19,27 value="#{cidadesController.items}": java.lang.NullPointerException
FATAL: /cidades/List.xhtml @19,27 value="#{cidadesController.items}": java.lang.NullPointerException
Why?
Thanks,
Allysson Vieira
The error is unrelated to the file properties.
Jsf is looking for "cidadesController.items" and there is not found.
Check the content of cidadesController, AbstractController.
Check annotations @Named(value = "cidadesController") @SessionScoped
Check method:
Best Regards.
I was using 4 glassfish with netbeans 7.3. When I moved to glassfish 3, it worked. But the outputText tags appear some warnings regarding the attributes of entities, for example:
<p:column sortby="#{item.id}" filterby="#{item.id}"> / * property * /
<f:facet name="header">
<h:outputtext value="#{bundle.ListCidadesTitle_id}">
</ f: facet>
<h:outputtext value="#{item.id}">
</ p: column></h:outputtext></h:outputtext></f:facet></p:column>
<p:column sortby="#{item.estado}" filterby="#{item.estado}"> / * property * /
<f:facet name="header">
<h:outputtext value="#{bundle.ListCidadesTitle_estado}">
</ f: facet>
<h: outputText value = "# {} item.estado"
</ p: column></h:outputtext></f:facet></p:column>
Remember that primefaces 3.5 only works with jsf 2.0 and 2.1 Apache MyFaces or Oracle Mojarra, page 13. indexed_primefaces_users_guide_3_5.pdf.
GlassFish 4 runs with jsf 2.2, sect. 1-2 .../4.0/release-notes.pdf
Appears something like this?
Take a screenshot please.
note that the properties of ITEM are not recognized, however, the code works normally. why?
there is no p:selectBooleanCheckBox> in the code.
Yes, it does work. The code you're looking at refers to a property inside an abstract class which its attributes are not known to the editor's introspection. Does that make sense?
closed topic.
The
<p:selectBooleanCheckBox>only get generated if the entity has an actual boolean field. Boolean is not an SQL data type in every database. MySQL has the BIT datatype, and that works. Also, PostgreSQL has a BOOLEAN datatype that represents TRUE and FALSE values. That one works too and your entity will have a boolean field.I have an entity named CITY in my web project. There is no boolean attributes in this entity. Until here, all right. The generator had to create its respective xhtml pages for this entity (create, edit, list and view.xhtml). In the code of list.xhtml, more specifically, in the p:datatable code, the netbeans editor shows some warnings regarding to attributes of CITY entity (i.e., ie, the attributes that are not recognized), that you, Kay Wrobel, explained to me that this is a behavior of editor itself. Ok, think better after, I agree. The code is running perfectly, it´s great to me. I just thought if anything could be done so that these warnings were eliminated. Only that.
Sorry, but that's something within NetBeans I can't control.