This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 227027 - Some valid PrimeFaces attributes appear with Error like "Not Defined in the Component X"
Summary: Some valid PrimeFaces attributes appear with Error like "Not Defined in the C...
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF Editor (show other bugs)
Version: 7.3
Hardware: All All
: P2 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-05 10:48 UTC by giovannyvelezalt
Modified: 2013-03-05 13:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot of error described (141.99 KB, image/png)
2013-03-05 10:48 UTC, giovannyvelezalt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description giovannyvelezalt 2013-03-05 10:48:46 UTC
Created attachment 132195 [details]
Screenshot of error described

Working on JSF facelet with PrimeFaces 3.4 and 3.5 some valid attributes of components appears with the error described.

In my case it appears with component "<p:fileUpload />" attribute "mode" and "<p:menu />" property "context" .

The same project worked fine on NetBeans 7.2
Comment 1 Martin Fousek 2013-03-05 13:46:45 UTC
Thanks for reporting. The real issue lies in the Primefaces library since its metadata doesn't define all attributes which are allowed.

Your first case <p:fileUpload />" attribute "mode": Looks to be already fixed in the latest Primefaces 3.5. So if you use its JAR your troubles should be gone. BTW, next release 731 should bring support for this 3.5 version so it will be fixed there.

Second case "<p:menu />" property "context": is still missing to be described in their metadata. But to be honest I didn't find any such attribute in their official documentation:
http://www.primefaces.org/documentation.html

If it's correct attribute, please report issue directly against primefaces that there are missing described tags or properties in the primefaces-p.taglib.xml metadata. Thanks a lot.

Closing as wontfix since here we are dependent on the metadata provided by 3rd party library.