Ravi,
Volunteers for each database could be an alternative. Maybe volunteering
for database support would be a new requirement for committers? :-) Like
in your case, you seem to have a vested interest in Oracle. And, I tend
towards DB2 and Derby. But, what do we do about other mainstream datab
Hi David,
On Wed, May 13, 2009 at 5:10 PM, David Beer wrote:
> Hi Kevin
>
> I currently use OpenJPA with the H2 database for my embeded programs,
> and will be considering MySQL for larger scale programs. I think that
> the more database vendors or suppliers we can get links with the
> better for
Hi Peter,
I seem to remember some problem that Jeremy found with not processing the
schema name for id generation. But, maybe my memory isn't what it was...
:-) I'll copy Jeremy on this reply to see if this rings a bell with him.
Thanks,
Kevin
On Wed, May 13, 2009 at 5:26 PM, Peter Henderson <
Hi,
JPA does not define this functionality. You could pass in the password via
the application instead of hard-coding it in a persistence.xml. Or, if you
are in an app server environment, you should use a jndi lookup of a
datasource. This would be the most secure.
Kevin
On Tue, May 12, 2009 at
Hi Kevin
Some database vendors usually have some sort of universal contact which
might be the best way of going about it. Posting a one of message to
support forums might well be an idea that could work.
David
On Thu, 14 May 2009 08:46:03 -0500 Kevin Sutter
wrote:
> Hi David,
>
> On Wed, May
Hi All,
I believe this bug has been addressed in JIRAs OPENJPA-557 and OPENJPA-582.
Only not-yet-released OpenJPA versions 2.0 and 1.3 contain the fix but you will
find a workaround in one of these JIRAs.
Cheers,
Milosz
> Hi Peter,
> I seem to remember some problem that Jeremy found with not
Hi,
I work for a Documentum Based product development company. Is there any way
OpenJPA applied for Content Servers.
Thanks
sriram
Sure. Most Content Servers still require some type of database to
persistently store the "content", right? So, the implementation of a
Content Server could easily use Entities to define their data model and use
generic JPA constructs to persist the data. Independent from any particular
database
Kevin,
Actually this is how it works
client ==>docbase(Content Server) ===> database.
(DFC-libraries)
DFC==>Documentum Foundation Classes.
If we are using a docbase from Documentum , is it possible for the client to
connect with docbase using JPA.
like
client ===>JPA===>docbase=
