I'm hoping someone can help me out with this. I'm using v .28 of the plugin in NB 8.0.2 fresh install, using mariadb datasource and deploying to Tomee 1.7 Plus with PF 5.0 and PF Ext 3.0.0. After changing the code in the ajax events to #{p:component('createButton')} syntax in order to fix the button visibility errors I now get an error reading 'items' on type. I suspect this has something to do with abstraction. Here is my List view:
It seems that the AbstractFacade method findAll is the cause of the problem. The query is null. The exception is thrown from the last line in the method, which calls the query and returns the result..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Paul. The AbstractFacade class is being generated by NetBeans code, which I have no control over. I do want to say that OpenJPA has not been very friendly to me when I was testing with TomEE and Derby. It has some quirks for sure. For example, a field that was defined as a CHAR(1) data type caused some weird mapping exception because OpenJPA tried to interpret that kind of a field as a NUMERIC. And I had to flip some flag in the Data Source to make this stop. I would not be surprised if OpenJPA did something "wonky" for lack of better terms with regards to any of your database fields.
That said, there must be some trace of what went wrong in the server log. I looked at what you provided above and could not properly determine the root cause of the issue. Can you turn on logging inside MariaDB (aka MySQL) and see what SQL statement OpenJPA is trying to submit? Or if it submitted any SQL at all?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Then I changed the target platform to Wildfly. I'm having too many issues trying to make it work on Tomee.Everything seems to be working out of the box with Wildfly. You were right about Java 8 as well.
Last edit: Paul Morris 2015-04-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Paul. I'm looking at my AbstractController template right now, but I don't see any difference. What did you change exactly?
Also, TomEE is a nice concept, and I'm sure many are using it successfully, but others seem to be doing it a bit better it seems. Not bashing TomEE here, in fact, we use it for some small projects here at my work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
and everything worked. With Wildfly everything works just right out of the box. I'm not bashing Tomee either. But Wildfly is a more professional system IMHO and it seems a lot more straightforward to work with. I have the luxury of choice in this project so I made the switch.
Last edit: Paul Morris 2015-04-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm hoping someone can help me out with this. I'm using v .28 of the plugin in NB 8.0.2 fresh install, using mariadb datasource and deploying to Tomee 1.7 Plus with PF 5.0 and PF Ext 3.0.0. After changing the code in the ajax events to #{p:component('createButton')} syntax in order to fix the button visibility errors I now get an error reading 'items' on type. I suspect this has something to do with abstraction. Here is my List view:
Which results in the following output:
Here is what showed up in the server log:
Any help is greatly appreciated. I'm having no end of frustration with this project.
It seems that the AbstractFacade method findAll is the cause of the problem. The query is null. The exception is thrown from the last line in the method, which calls the query and returns the result..
Hi Paul. The
AbstractFacadeclass is being generated by NetBeans code, which I have no control over. I do want to say that OpenJPA has not been very friendly to me when I was testing with TomEE and Derby. It has some quirks for sure. For example, a field that was defined as aCHAR(1)data type caused some weird mapping exception because OpenJPA tried to interpret that kind of a field as aNUMERIC. And I had to flip some flag in the Data Source to make this stop. I would not be surprised if OpenJPA did something "wonky" for lack of better terms with regards to any of your database fields.That said, there must be some trace of what went wrong in the server log. I looked at what you provided above and could not properly determine the root cause of the issue. Can you turn on logging inside MariaDB (aka MySQL) and see what SQL statement OpenJPA is trying to submit? Or if it submitted any SQL at all?
On closer inspection, it does say that the query it was trying to submit was NULL. Have you tried to debug the code?
I managed to get it working by changing the code in AbstractController to this:
Then I changed the target platform to Wildfly. I'm having too many issues trying to make it work on Tomee.Everything seems to be working out of the box with Wildfly. You were right about Java 8 as well.
Last edit: Paul Morris 2015-04-07
Hi Paul. I'm looking at my AbstractController template right now, but I don't see any difference. What did you change exactly?
Also, TomEE is a nice concept, and I'm sure many are using it successfully, but others seem to be doing it a bit better it seems. Not bashing TomEE here, in fact, we use it for some small projects here at my work.
Sorry, my mistake. I didn't have access to my code and was working from memory. It was in AbstractFacade.findAll(). I changed this line:
to:
and everything worked. With Wildfly everything works just right out of the box. I'm not bashing Tomee either. But Wildfly is a more professional system IMHO and it seems a lot more straightforward to work with. I have the luxury of choice in this project so I made the switch.
Last edit: Paul Morris 2015-04-12
View and moderate all "Troubleshooting" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
you must inspect the database server
sometime it shutdown alone
View and moderate all "Troubleshooting" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
this happen every time for as
the solution that I found is very easy
the database server is down
reconnect...