Hi Matthews,
The way OpenJPA is layered supporting non-relational database is quite
feasible. In fact, one of the earlier databases supported by OpenJPA (or
rather Kodo) was an Object database. If the datanse support is developed,
then both JDO and JPA can be supported as a nothe-bound API.
Hi Donald,
All the urgent ones that I'm aware of are in. We'll be running regression
tests this week, but it looks good so far.
-mike
On Wed, Jul 21, 2010 at 3:46 PM, Donald Woods wrote:
> I'd like to start cutting a 2.0.1 release on August 2nd.
> Are there any critical issues that we should t
+1 If the tooling isn't tied to a particular release of OpenJPA, I too think
it should be moved into devtools.
-Jeremy
On Mon, Jul 26, 2010 at 4:07 PM, Michael Dick wrote:
> Agree. If tools has it's own release cycle it makes sense to move it out of
> trunk (if we change the release cycle decisi
Agree. If tools has it's own release cycle it makes sense to move it out of
trunk (if we change the release cycle decision I'd reconsider).
Any objections to moving the code?
-mike
On Mon, Jul 26, 2010 at 4:00 PM, Donald Woods wrote:
> Ture, so even more the point of needing to move it out of
Ture, so even more the point of needing to move it out of trunk...
Also, would be great to integrate such a "migration" tool into the
Eclipse plugin, for an easier to use GUI approach... :-)
-Donald
On 7/26/10 4:43 PM, Pinaki Poddar wrote:
>
> Independency of OpenJPA at this point is deliberate
Independency of OpenJPA at this point is deliberate.
Need more time to understand common operational environment for the toll to
make such judgment.
For example, why some one trying to convert a classic Hibernate mapping
descriptor file *.hbm.xml to a JPA compliant *.orm.xml will require OpenJPA
Also, why not depend on openjpa or openjpa-all like the
openjpa-maven-plugin does, but allow the user to choose which level of
OpenJPA the tool will use for common code reuse?
For example, there doesn't seem to be any depends or reuse of existing
code in openjpa-lib or other modules.
I saw usage o
If these are the requirements (release independent of OpenJPA releases),
then the code should not go into openjpa/trunk but should go into
openjpa/devtools/ as a separate subproject, like the Eclipse plugin.
For now, I've added a openjpa-tools/pom.xml which will allow you to
build a jar based on t
[
https://issues.apache.org/jira/browse/OPENJPA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-1690:
--
Fix Version/s: 2.0.1
> DistinctResultList is not Serializable
> -
[
https://issues.apache.org/jira/browse/OPENJPA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-1722:
--
Fix Version/s: 2.0.1
Affects Version/s: 2.0.0
(was: 2.1.0)
Here is a *suggested requirement* list :
1.1: The tools should be available in a separate openjpa-tools.jar.
Because at this stage openjpa-tools.jar should evolve faster than openjpa
releases.
1.2: The openjpa-tools.jar should be separate download from the usual
download page.
1.3: Th
For the build to work, the parent should be openjpa-parent like all of
the other modules.
To include it in the binary and source distro zipfiles (but not openjpa
or openjpa-all jars) you'll need to update the following files -
openjpa-project/pom.xml
openjpa-project/assembly.xml
openjp
[
https://issues.apache.org/jira/browse/OPENJPA-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-1719:
--
Fix Version/s: 2.0.1
Patch Info: [Patch Available]
> Prepared SQL cache ordering probl
Very cool. I like the idea of a new tools module. Making openjpa-tools as
a sibling of openjpa-parent means it'll get included in the distro, but not
in the base jars? If so, sounds good to me...
-Jeremy
On Thu, Jul 22, 2010 at 4:12 PM, Pinaki Poddar wrote:
>
> Hi,
> Draft version of follo
[
https://issues.apache.org/jira/browse/OPENJPA-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Catalina Wei resolved OPENJPA-1719.
---
Fix Version/s: (was: 2.0.1)
Resolution: Fixed
Fix checked in under trunk revisio
15 matches
Mail list logo
