Thanks for the tip. I was looking for a `clearCache` or a `clearMetadata` method or something to that extent that I didn't notice the `unmanage/unload` methods. I also found the plugin from Dan

There is a MetaDataManager for each PMF. It loads metadata when it needs to. There is a method unloadMetaDataForClass to unload a class' metadata if needing to do so. There is also a method on

I'm working on a fairly large, slow startup legacy application in which I am slowly trying to integrate DataNucleus. I am also leveraging JRebel, which allows me to modify most classes on the fly

Hi, I'm running into a similar problem as you where I need to create an ugly JDOHelper.getObjectIdAsLong() hack as well due to some legacy Kodo code. Did you get something fully functional finally?

Hi, When 2 queries with the same tenant but different tenantReaders are executed, the second one returns the result of the first one. The SQL generated is the same for the second query while it should

You are using a JEE connection pool but are setting the resource type as "local" hence DN will try to commit the connection (since it commits local things). Your connection (JBoss JCA) then throws an

I'm encountering a strange behaviour for which I have not been able to pinpoint the cause and was hoping that someone could help point me in the right direction. I have an application running under

https://www.datanucleus.org/products/accessplatform_5_2/jdo/persistence.html#jboss7 says that "DataNucleus JCA adapter supports both Local and XA transaction types".

FYI The JCA was written by people who no longer develop DataNucleus, and is dependent on volunteers. Consequently you're pretty much on your own. Clearly JDO is just as usable outside of JCA, creating

As a followup question, does the JCA adapter support anything other than XATransactions? I see the following in ra.xml: <transaction-support>XATransaction</transaction-support> Does it support any

I'm trying to integrate DN (JDO) into my JEE application via the JCA adapter, and configure the Persistence manager to understand BeanManagedTransactions. I am retrofitting this into existing code

I'm trying to integrate my instance of JBoss/Wildfly 10 with the Datanucleus JCA-JDO connector. I saw an original post for JBoss AS7 (https://developer.jboss.org/docs/DOC-17094) as linked from the

Thanks; I hadn't seen that extension. I see that the the JDO pm allows for using JPQL but remaining within the JDO framework. Which from a consistency perspective is great. However, from a

Hi, The disable option doesn't work: @MultiTenant(disable = true) In the MultiTenantHandler DN looks for disabled instead of disable attribute name. And then the disable extension is added if it's not

Suggest that you work out what the Q class should be, get the code from here, and contribute an update.

I have a javax.validation.Min annotation on an Integer field in my JDO entity @Column(allowsNull = "true") @Min(0) @Getter @Setter private Integer scale; The generated Q code for this field is this,

Perhaps you would be better off looking at the DataNucleus (and JDO) documentation. The JDO spec mandates being able to use JPA metadata (XML / annotations) with JDO persistence, and DataNucleus (JPA)

As I am migrating my legacy Kodo based application to DataNucleus, I noticed that the application uses both JDO for most persistence based interaction, however has several JPQL queries which leverage

Works perfectly. Didn't realize that the solution was that straightfoward. I had understood from the javadoc that the `theIdValue` had to be an Identity object. Thanks, Eric

Use of implementation-specific classes is always a bad idea IMHO. Imagine hardcoding Kodo-specific stuff and then finding that you need to change provider some time later ... In the same way, reliance