You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2009/02/09 14:55:02 UTC

[jira] Commented: (JUDDI-136) How to deal with a table prefix (JUDDI_) when using JPA

    [ https://issues.apache.org/jira/browse/JUDDI-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671856#action_12671856 ] 

Kurt T Stam commented on JUDDI-136:
-----------------------------------

We should keep the setting of the prefix configurable. Unfortunately is does not seem that JPA, and neither the OpenJPA and Hibernate implementations support this.

In Hibernate we will need to add our own ImprovedNameStrategy as described here: http://forum.hibernate.org/viewtopic.php?p=2376564&sid=d707c1d84722234dafbeae72a7e8dba9

In In OpenJPA, this can be
accomplished by creating an extended DBDictionary and overriding the
getValidTableName() method." 
I posted the question on their forum: http://n2.nabble.com/Is-there-any-way-to-configure-a-table-prefix-across-all-entity-tables--td2289858.html

> How to deal with a table prefix (JUDDI_) when using JPA
> -------------------------------------------------------
>
>                 Key: JUDDI-136
>                 URL: https://issues.apache.org/jira/browse/JUDDI-136
>             Project: jUDDI
>          Issue Type: Task
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.0beta
>
>
> We may be able to see how jBPM handles this, they use straight hibernate though. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.