Notices tagged with jpa
-
Ah, the link didn't make it in: http://stackoverflow.com/questions/2243730/jpa-hibernate-embedded-and-enum
It is about #Hibernate and I use #EclipseLink here but still the enumeration can be used in #JPA to persist DayOfWeek "compatible" stamps.
-
I wonder if #JPA can persist java.net.InetAddress ? Would be cool if so. cc !java
-
The class does not have a descriptor, or a descriptor that does not use inheritance or uses a ClassExtractor for inheritance
The mentioned message still comes when you have @Inheritance (strategy = InheritanceType.TABLE_PER_CLASS) in your abstract (not-persisted) with latest version of #Payara / #Glassfish which both contains #EclipseLink by default.
Strange that they did not yet fix it. And unfortunally migrating to e.g. #WilfFly (which uses other #JPA) seems not so easy as you may think.
Currently I have no idea how to fix it and sadly I need the strategy as this #JavaEE application is written for an existing database layout.
Someone may have to raise a support ticket mentioning that the #bug is still there.
Reposted with #public visibility. Sorry for double message.
-
@mmn I like #JPA for a good reason, having no #SQL in your program but still be able to do queries (e.g. named queries) with #JPQL (Java Persistence Query Language) which is independent from underlaying database server. Theoretical you can switch from #MySQL to e.g. #PostgreSQL an it *should* work out-of-the-box as long as you don't use native (hard-coded) queries.
-
!java RT @vsatayamas How to call stored procedures in JPA #storedprocedure #jpa #postgresql
http://qttr.at/1en9
-
This doesn't look like high performance to me, if the #JPA has to insert + update + delete (at least, plus necessary select statements). Any ideas how do I have to write it? Don't worry, it will be later #GPLv3 :-)
-
For the last 3 (!) days (including today) I tried to fix the problem that while the #JPA is merging (similar to UPDATE #SQL statement) entities, some tables got filled with new rows (search for "eclipselink insert instead update") which leaves orphaned rows behind. I could enable orphanRemoval=true but that only adds another performance penalty. So I decided to switch to #Hibernate instead of remaining with #EclipseLink. cc !java
-
Glassfish versus Wildfly (Tomcat EE) with custom JARs
I'm currently setting up a #Glassfish container for letting run my #JavaEE applications (will be #GNU #GPLv3 or maybe later #Affero) as this was later my choice after a previous unsuccessful attempt with #WildFly (LAN only).
Back what happened before. First of, I had Glassfish 4.1.1 which is currently bugged (#RuntimeException) and doesn't allow me to setup essential things like #JBDC resources or connection pools. So I tried WildFly next.
My applications have custom JARs (libs) which in Glassfish I need to copy to $DOMAIN_HOME/lib/ (and the #MySQL connector to $GLASSFISH_HOME/modules/) and that is all. With WildFly I had trouble even setting up a really simple #EJB (logging with #log4j over a local interface), because I was not able to find to where to my custom JARs (some really simple JARs are required + log4j). So I tried to setup all as modules (module.xml) but no success.
After many unsuccessful attempts I switched back to #Glassfish and found an older (but working) 4.1 version which finally let my applications and the #JPA stuff all work correctly.
Sadly, I now have to "hang around" with #Oracle which is known to be slow in fixing bugs ... But at least my applications are running ...
Not really a good argument for switching to WildFly or #TomcatEE, right? Or where do I have to put my JARs (and log4j)?
-
Wenn ich das schon wieder lese ...
... dann kommt einem wieder die Galle hoch. :-( Wieder astronomische Anforderungen. Aber ja, man muss ja nicht alles koennen ...
Wissen diese Firmen eigentlich, wie viel da im Einzelnen hinter steckt? Hmm? Noe, wieso auch, einfach mal alles auflisten, was einem in den Sinn kommt.
Aber gut, ich bewerbe mich natuerlich weiter. :-/