Re: Using query hints for mapping extensions in orm.xml

Hi, On Jan 15, 2007, at 5:12 PM, Patrick Linskey wrote: Hi, It kinda feels like we're corrupting the intended use of query hints. Plus, it seems unfortunate to have to drop back into untyped strings if we can avoid it. I think that there is another approach that we've talked about earlie

RE: No tx commit when providing ManagedRuntime

Also, what happens if you manually call flush() at the end of your persistence operations? This should at least tell us something about whether or not the connections are being used correctly. -Patrick -- Patrick Linskey BEA Systems, Inc. ___

RE: Using query hints for mapping extensions in orm.xml

Hi, It kinda feels like we're corrupting the intended use of query hints. Plus, it seems unfortunate to have to drop back into untyped strings if we can avoid it. I think that there is another approach that we've talked about earlier: use namespaces to intersperse OpenJPA data into the orm.xml fi

RE: Schema and Table Name sometimes being ignored when supplied onl in orm.xml

What do you get when you set the MetaData log channel to TRACE? -Patrick -- Patrick Linskey BEA Systems, Inc. ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., it

Re: No tx commit when providing ManagedRuntime

Matthieu- That's pretty weird. What happens if you just try to manually commit the transaction from the EntityManager itself (with "em.getTransaction ().commit()")? Also, has the global transaction already been started as the point when you obtain the EntityManager from the EntityManagerFa

Re: No tx commit when providing ManagedRuntime

Does your TxMgrProvider provide a correctly functioning TransactionManager? OpenJPA will register a Synchronization with it, which should get committed when your global transaction is committed. It does, I directly provide JOTM transaction manager. The same code works correctly with Hibernate a

Re: Using query hints for mapping extensions in orm.xml

I think this is the way to do it. Isn't this what the QueryHints are intended to do - to allow vendor specific query extensions to hook in :-) Cheers, Rahul Marc Prud'hommeaux wrote: OpenJPA people- A limitation of the JPA specification is that there is no built-in way to put implementati

[VOTE RESULT] Have official OpenJPA site use the confluence wiki page

With 3 votes for and 0 against, the vote passes. I've gone ahead and set up synchronization of the OpenJPA pages with the exported HTML from Confluence (thanks to David Blevins for letting me know how he did it for OpenEJB). Sadly, it's not the most elegant thing in the world: jefft's cron

Using query hints for mapping extensions in orm.xml

OpenJPA people- A limitation of the JPA specification is that there is no built-in way to put implementation-specific extensions in an orm.xml file, which limits the use of OpenJPA's many useful extensions to only being expressible annotations. Past suggestions for getting around this lim

Re: sql statement batching

Hi Kevin, I agree that sql batching is such a huge performance win that most real users would want this feature. Craig On Jan 15, 2007, at 6:39 AM, Kevin Sutter wrote: Marc, Concerning the infrastructure for sql batching support... Do you mean that this support is pluggable into the Ope

Re: No tx commit when providing ManagedRuntime

Matthieu- Does your TxMgrProvider provide a correctly functioning TransactionManager? OpenJPA will register a Synchronization with it, which should get committed when your global transaction is committed. Do you see any log messages at all when you commit the global transaction? On Ja

Schema and Table Name sometimes being ignored when supplied onl in orm.xml

I have entities like this which intentionally omit the schema and table names: @Entity // @Table(name = "V_MBK_KEY") specified in orm.xml public class FeMbkKey implements Serializable { and in orm.xml I add the name and schema: .. CLMR

No tx commit when providing ManagedRuntime

Hi, I now have a working setup (at least something that starts) using a programmaticaly provided datasource and transaction manager. Here is the code now: HashMap propMap = new HashMap(); propMap.put("openjpa.jdbc.DBDictionary", " org.apache.openjpa.jdbc.sql.DerbyDictionary");

Re: Using _attributes

I see. I specifically had problems with relation tables though. I had columns generated as _attribute_OTHERTABLENAME and the first _ didn't make it through Derby. Hence the necessary usage of @ElementJoinColumn. Are these mandated by the spec as well? Yes. And as I said, there are standard

Re: Using _attributes

I see. I specifically had problems with relation tables though. I had columns generated as _attribute_OTHERTABLENAME and the first _ didn't make it through Derby. Hence the necessary usage of @ElementJoinColumn. Are these mandated by the spec as well? On 1/15/07, Abe White <[EMAIL PROTECTED]> wr

Re: Using _attributes

I don't feel pre-fixing with '_' for member level attributes is really necessary, particularly if you're using an IDE. I can see how it would help someone using only vi or emacs recognize what was what, but with the color code and hotkeys and quick-clicking available in IDE's, it just doesn't

Re: Using _attributes

I think it could be nicer and a bit easier if OpenJPA was automatically eliminating the first _ from attribute names to build its default coumn names, don't you think? The default column names are mandated by the JPA specification. And unless you're using OpenJPA-specific mappings, you sh

Using _attributes

Hi, We're using _attributes notations for instance attributes in Ode and I've found slight problems with it in OpenJPA. If you use this notation the default column names chosen by OpenJPA will start with _ which forces you to use @Column and @ElementJoinColumn (unfortunately OpenJPA specific) all

Re: sql statement batching

Marc, Concerning the infrastructure for sql batching support... Do you mean that this support is pluggable into the OpenJPA runtime? That is, is there a pluggable interface for other vendors to provide support for sql batching? Or, is it just that the runtime could be updated to support sql batc