TomEE 1.7 just released. I tried nbpfcrudgen-0.27.2-8.0_patch2 with TomEE 1.7, when I generate PF pages, I got error: "Cannot be generated for Java EE 6 sources without server w/ complete java EE 6 Web Profile support.."
Thanks for letting me know that TomEE 1.7 is now out. Haven't tested with it yet. I can tell you though that this message is most likely produced by NetBeans as I don't have any line of code in the CRUD generator that would show this message. It's probably the same as with TomEE 1.6.0.2 which didn't work until I renamed tomee-common-x.x.x.x.jar to tomee-common-x.x.x.jar (made a video on that). I would imagine that TomEE 1.7 has a similar issue. Probably, this time around, the version is not long enough. Try renaming tomee-common.1.7.jar (if it exists) to tomee-common-1.7.0.jar and see if that works. Again, I haven't loaded TomEE 1.7 yet, so I can't say for sure if this works. All I know is how NetBeans is handling the detection, and it's flawed. I have already submitted a bug report to NetBeans,and their code is already fixed for their next release.
Cheers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, I just checked out the new TomEE, and the jars in question do match the pattern that NetBeans is testing for. So I don't know exactly what broke again. I am quiet frankly sick and tired of hunting down these issues with both NetBeans and TomEE. Both of these teams need to start talking ASAP because I'm finding it quite ridiculous that this is still happening. TomEE is like the step-child that doesn't get the attention it rightfully deserves.
Venting now out of the way, I will see if I can hunt down the pieces of code in the NetBeans source tree to see what is up with this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Anonymous. I have spent a considerable amount of time this morning debugging the NetBeans Tomcat support module and found another weakness in the detection mechanisms. I've filed a new bug report with the NetBeans team and hope they will address this issue shortly.
Unfortunately this time, there is no quick fix for getting NetBeans to detect TomEE 1.7 because they are testing for version literals starting with "1.5" or "1.6" and not "1.7". Unless you feel adventurous and start renaming tomee-common-1.7.0.jar to tomee-common-1.6.0.jar, which I wouldn't recommend but you might try it out for yourself. Just be aware that this might break something in TomEE.
Hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
TomEE 1.7 just released. I tried nbpfcrudgen-0.27.2-8.0_patch2 with TomEE 1.7, when I generate PF pages, I got error: "Cannot be generated for Java EE 6 sources without server w/ complete java EE 6 Web Profile support.."
nbpfcrudgen-0.27.2-8.0_patch2-impl,
TomEE 1.7,
NetBeans 8,
JSF 2.1,
PrimeFaces 5,
jdk 8.
Hi anonymous.
Thanks for letting me know that TomEE 1.7 is now out. Haven't tested with it yet. I can tell you though that this message is most likely produced by NetBeans as I don't have any line of code in the CRUD generator that would show this message. It's probably the same as with TomEE 1.6.0.2 which didn't work until I renamed
tomee-common-x.x.x.x.jartotomee-common-x.x.x.jar(made a video on that). I would imagine that TomEE 1.7 has a similar issue. Probably, this time around, the version is not long enough. Try renamingtomee-common.1.7.jar(if it exists) totomee-common-1.7.0.jarand see if that works. Again, I haven't loaded TomEE 1.7 yet, so I can't say for sure if this works. All I know is how NetBeans is handling the detection, and it's flawed. I have already submitted a bug report to NetBeans,and their code is already fixed for their next release.Cheers.
So, I just checked out the new TomEE, and the jars in question do match the pattern that NetBeans is testing for. So I don't know exactly what broke again. I am quiet frankly sick and tired of hunting down these issues with both NetBeans and TomEE. Both of these teams need to start talking ASAP because I'm finding it quite ridiculous that this is still happening. TomEE is like the step-child that doesn't get the attention it rightfully deserves.
Venting now out of the way, I will see if I can hunt down the pieces of code in the NetBeans source tree to see what is up with this.
Hi Anonymous. I have spent a considerable amount of time this morning debugging the NetBeans Tomcat support module and found another weakness in the detection mechanisms. I've filed a new bug report with the NetBeans team and hope they will address this issue shortly.
Unfortunately this time, there is no quick fix for getting NetBeans to detect TomEE 1.7 because they are testing for version literals starting with "1.5" or "1.6" and not "1.7". Unless you feel adventurous and start renaming tomee-common-1.7.0.jar to tomee-common-1.6.0.jar, which I wouldn't recommend but you might try it out for yourself. Just be aware that this might break something in TomEE.
Hope this helps.
I've moved this thread to the Troubleshooting section as this is clearly more than a general discussion point.