in the wizard i choose another name for the bundle. In my case "BundlePrime", but in the faces-config the var name for it is still "bundle". Because my other Bundle has already the "bundle" var, it is not recognized by the application anymore. You can see it here:
Hi Schimi. Thanks for bringing this up. This is something I never tested, quite frankly, because it was all part of the original JSF Pages from Entities wizard. I wonder if that one had this broken as well. I'll look at this as soon as I get a chance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Schmimi. Please download the just-released version 0.15 which fixes your issue. The bundle now defaults to /MyBundle which creates a myBundle variable in faces-xonfig.xml. Enjoy!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since this wizard is a fork of the original, I felt compelled to simply fix the issue and make this wizard better. I'll see if I can file a bug report with them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You know, Schmimi, now as I am describing the "bug" to the NetBeans team, I come to realize that this might not necessarily be an actual bug. Their wizard was designed to generate a whole CRUD application from scratch. As such, the bundle variable is set properly in the faces-config.xml file. It just points to the user-supplied bundle file. Mind you that's different! After all, it asks you for the bundle file, not the name of the reference variable.
That said, I can see your point and that is why I changed it to the current behavior. I'm just unsure if this could be considered an actual bug. But we'll see if anybody responds. For now, I'll set this up as a P4 bug report.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I filed a bug report with NetBeans. Feel free to subscribe to it if you're interested in following or contributing to it. Hope I described the situation accurately.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
in the wizard i choose another name for the bundle. In my case "BundlePrime", but in the faces-config the var name for it is still "bundle". Because my other Bundle has already the "bundle" var, it is not recognized by the application anymore. You can see it here:
Hi Schimi. Thanks for bringing this up. This is something I never tested, quite frankly, because it was all part of the original JSF Pages from Entities wizard. I wonder if that one had this broken as well. I'll look at this as soon as I get a chance.
I've looked for it. Yes, it seems that this happens also in the original wizard. ;) Btw I'm using NetBeans 7.3.
Hi Schmimi. Please download the just-released version 0.15 which fixes your issue. The bundle now defaults to /MyBundle which creates a
myBundlevariable infaces-xonfig.xml. Enjoy!Thx for the fix!
But since thats not actually a bug produced from you, NetBeans should care. :)
Since this wizard is a fork of the original, I felt compelled to simply fix the issue and make this wizard better. I'll see if I can file a bug report with them.
You know, Schmimi, now as I am describing the "bug" to the NetBeans team, I come to realize that this might not necessarily be an actual bug. Their wizard was designed to generate a whole CRUD application from scratch. As such, the bundle variable is set properly in the
faces-config.xmlfile. It just points to the user-supplied bundle file. Mind you that's different! After all, it asks you for the bundle file, not the name of the reference variable.That said, I can see your point and that is why I changed it to the current behavior. I'm just unsure if this could be considered an actual bug. But we'll see if anybody responds. For now, I'll set this up as a P4 bug report.
Ok, I filed a bug report with NetBeans. Feel free to subscribe to it if you're interested in following or contributing to it. Hope I described the situation accurately.