Hi,
I've a standalone RCP application which provides some basic CRUD facility. One of these is where I have a parent object which is assigned a new child. When I run the app and do this I can see the underlying table being updated correctly. The app then refreshes the parent with the current children entities however it does not pick up the changes. When I bounce the application it picks it up again. I'm not sure if this is a caching issue or not, its my first excursion into JPA
My rebuild function calls:
public List<YeFundManager> findAllYeFundManagers() {
return em.createNamedQuery("findAllFundManagers").getResultList();
}
Persistence.xml:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns=" xmlns:xsi=" xsi:schemaLocation=" <persistence-unit name="yearendtax-PU">
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeAssetRecord</class>
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeAssets</class>
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeFmContacts</class>
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeFundManager</class>
<properties>
<property name="eclipselink.jdbc.url" value="jdbcracle:thinfsgdev10:1521fsgdev6" />
<property name="eclipselink.jdbc.driver" value="oracle.jdbc.OracleDriver" />
<property name="eclipselink.jdbc.password" value="icul8ter" />
<property name="eclipselink.jdbc.user" value="yetaxapp" />
<property name="eclipselink.jdbc.read-connections.min"
value="1" />
<property name="eclipselink.jdbc.write-connections.min"
value="1" />
<property name="eclipselink.jdbc.batch-writing" value="JDBC" />
<!-- Logging -->
<property name="eclipselink.logging.level" value="FINE" />
<property name="eclipselink.logging.timestamp" value="true" />
<property name="eclipselink.logging.session" value="false" />
<property name="eclipselink.logging.thread" value="false" />
</properties>
</persistence-unit>
</persistence>
Not sure what else might be useful
I've a standalone RCP application which provides some basic CRUD facility. One of these is where I have a parent object which is assigned a new child. When I run the app and do this I can see the underlying table being updated correctly. The app then refreshes the parent with the current children entities however it does not pick up the changes. When I bounce the application it picks it up again. I'm not sure if this is a caching issue or not, its my first excursion into JPA
My rebuild function calls:
public List<YeFundManager> findAllYeFundManagers() {
return em.createNamedQuery("findAllFundManagers").getResultList();
}
Persistence.xml:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns=" xmlns:xsi=" xsi:schemaLocation=" <persistence-unit name="yearendtax-PU">
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeAssetRecord</class>
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeAssets</class>
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeFmContacts</class>
<class>
com.mgl.yearendtax.datamodel.dao.entities.YeFundManager</class>
<properties>
<property name="eclipselink.jdbc.url" value="jdbcracle:thinfsgdev10:1521fsgdev6" />
<property name="eclipselink.jdbc.driver" value="oracle.jdbc.OracleDriver" />
<property name="eclipselink.jdbc.password" value="icul8ter" />
<property name="eclipselink.jdbc.user" value="yetaxapp" />
<property name="eclipselink.jdbc.read-connections.min"
value="1" />
<property name="eclipselink.jdbc.write-connections.min"
value="1" />
<property name="eclipselink.jdbc.batch-writing" value="JDBC" />
<!-- Logging -->
<property name="eclipselink.logging.level" value="FINE" />
<property name="eclipselink.logging.timestamp" value="true" />
<property name="eclipselink.logging.session" value="false" />
<property name="eclipselink.logging.thread" value="false" />
</properties>
</persistence-unit>
</persistence>
Not sure what else might be useful