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.
JSF pages from Entity class functionality is missing. It's disabled due to retouche merge and should be working before FF.
This functionality needs to be rewritten from scratch due to Retouche. So I don't expect that this will be sooner then in M8.
This feature is dropped in 6.0
*** Issue 98869 has been marked as a duplicate of this issue. ***
Release note added
Is there a reason why to drop this important feature?
The reason is that there was not enough time to port this feature over to the new Java development infrastructure in the 6.0 release. The old code from NetBeans 5.5 does not work with NetBeans 6. If we wanted to add this to NetBeans 6, we would have to extend the 6.0 schedule by another couple months.
But as regression from NetBeans 5.5 (and a major one), it shouldn't be marked as a FEATURE. I'll leave it up to your discretion Peter, but I disagree with the assessment. /Brian
Increasing priority to P1. The lack of this feature forces me to demo Visual Web Pack, because I can't show anything quickly using JSF with manual editing. About 30 different people complained to me so far about this regression, of course mainly evangelists.
> But as regression from NetBeans 5.5 (and a major one), it shouldn't be marked as a FEATURE. I'll leave it up to your > discretion Peter, but I disagree with the assessment. > > /Brian I have to disagree with having defects for dropped features. We also don't have an open defect for not being able to run the IDE on JDK 1.3 even though it used be possible. Dropping any feature can always be seen as a regression, but if there has been a deliberate decision to be drop a certain feature, I don't see the point in having open defects for it - it wouldn't be any different from having defects for non-existing features.
Erno, I wasn't aware this feature was dropped - just postponed past 6.0 (hopefully 6.1). And you can't compare JDK 1.3 (dead or dying) to JSF (growing and an important technology to Sun). Don't underestimate the popularity and usefulness of this feature (beyond just demos). It's very difficult to even find an article on using JPA with NetBeans that doesn't also refer to this feature. At the moment, there are no articles on JPA with NetBeans 6.0. /Brian
Hi Brian, my point wasn't to compare JDK 1.3 with JSF in terms of their usefulness/popularity/future prospects, it was just an example of a dropped feature - if we were to reintroduce support for JDK 1.3, I think it would rather be an enhancement/ feature than a defect. I understand that this feature (i.e. JSF from entities) is important for many people and personally I'm not against bringing it back. That said, I don't think that the importance of JSF is by any means currently underestimated in NetBeans - in fact, you could argue the opposite (given that we don't have any support for some of the more popular frameworks/technologies out there).
The option to bring the festure back in NetBeans 6.x is very much on the table; if we decide to do it, then the resulting application it generates should be compatible with Visual Web features.
Muy importante para mi, es sumamente util
Note that we are getting feedback from users of NetBeans that they were quite angry that this feature was removed - it is not just demoware - real people are using it. C.f. Brian's recent trip reports from Javapolis - perhaps he can attach some of the feedback.
Sure, here's the note from my JavaPolis trip report... Lots of dismay over the missing JSF Pages from Entity Class feature. As one developer told me "I'm sorry, but we used many impolite words when we found that feature missing." Yara Senger (Dream Teamer Vinicius' wife) didn't realize it was missing until the middle of her JSF presentation, during which she had to revert to 5.5.
... and still no real use-case for it
Martin, there are very real use-cases for this feature. Getting a skeleton JSF application up and running against MY data is invaluable. I have spoken to numerous DEVELOPERS that miss this feature greatly. I have added Yara Senger, founder a Globalcode in Brazil to the Cc. Yara, being a real developer (and not just an evangelist like myself), please feel free to add any additional information in support of this feature. /Brian
What I really like in that feature is that the generated code shows a nice way of using JPA with JSF, besides the creation of converters and validators for our "real world" needs. Even when you are not going to use the generated code on your final application it stills valuable since it builds everything over your entities making easier to learn and understand. I beleive that one of the best advantages NetBeans have over any other IDE is the way it delivers educational content: with comments inside JSPs, with the Design Patterns tool, with Blue Prints catalog as a built in project, and many other situations. Another wonderful thing is that it doesn't uses Component binding for every component in the JSP pages like Visual Web Pack does! But I'm very happy that this is being considered in the issue 123536. Thank you Brian for motivating me on this participation and thank you all for making Netbeans 5.5 and 6.0 so good.
My small company has developed a practice, based upon NetBeans 5.5, for creating a software functional prototype which aims to make the fullest use of the code generation features. Two features of central interest are: generation of database tables from the repesentation in Entity Classes of the application's domain data model; generation of an application's View and Controller components using 'JSF Pages from Entity classes'. NetBeans 6 appears to offer further advantages re the 'agile' objectives of our practice so the hope here is that the feature will not be too long delayed.
"JSF pages from Entity class functionality" is back in NetBeans 6.1.
But it's still not working for me (at least in the Beta). I still have these issues: 1) index.jsp is missing the taglib declarations, so the <h:commandLink ...> throws an error. 2) If the controllers are put into a different package then the entity classes, the entity classes are missing their import statements. 3) After fixing those issues, the application fails to run with a RuntimeException: cannot find FacesContext.
Please file individual bug for 'issue'. This one is for the 'feature'. Thanks!
v.
if we are working now on netbean 6 and we need to use this feature jsf from entity class does this mean we have to install version 6.1 comm on this is not good solution for me am wokring on my graduation project here people! please if there is any plug in we can add that would solve the problem