Enable Java 2 Security in EE environment causes Access denied exception

why provider's entity manager factory can not be injected to user code. Am I way off base regarding security in OpenJPA and/or JPA in general? Any insights into this topics is greatly appreciated. Thanks. Albert Lee.

Re: WebSphere and transaction managers

functional. Albert Lee On 2/16/07, Patrick Linskey <[EMAIL PROTECTED]> wrote: Hi, It looks like the new WebSphere transaction manager lookup code is missing some functionality available elsewhere. See OPENJPA-149 (https://issues.apache.org/jira/browse/OPENJPA-149) and OPENJPA-153

[jira] Commented: (OPENJPA-150) @Column in @AttributeOverride not honoring table attribute that maps to a secondary table in mappedsuperclass entity

[ https://issues.apache.org/jira/browse/OPENJPA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473784 ] Albert Lee commented on OPENJPA-150: I investigated into this problem and the following changes has corrected

[jira] Created: (OPENJPA-150) @Column in @AttributeOverride not honoring table attribute that maps to a secondary table in mappedsuperclass entity

://issues.apache.org/jira/browse/OPENJPA-150 Project: OpenJPA Issue Type: Bug Components: jdbc, sql Environment: Any Reporter: Albert Lee I have the following scenario mapping entity to 2 tables: - a mapped super class that has a field - a

AttributeOverride to secondary table of entity using mappedsuperclass not honored

) In AnnotationPersistenceMappingParser.setupColumn() method, where the @AttributeOverride annotation is process, it does not seems to extract the table name from the annotation. Can someone give me direction if this is the place to start looking for a solution? And what/where-else should I be looking? 3) May be someone has a better idea how to correct this problem! Thanks. Albert Lee.

Re: [jira] Created: (OPENJPA-126) EntityManagers cannot be serialized

? Any insight is greatly appreciated Thanks Albert Lee On 2/7/07, Patrick Linskey (JIRA) <[EMAIL PROTECTED]> wrote: EntityManagers cannot be serialized --- Key: OPENJPA-126 URL: https://issues.apache.org/jira/browse/O

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

dling of the stanza. - No guarantee this will work in other providers. - But this option is the least restrictive in orm usage All three options are available for use by an application, in order of compliance and portability preferences. Albert Lee. On 1/24/07, Patrick Linskey <[EMAIL PR

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

he openjpa features. 3) if an application wants to be openjpa schema compliance, then use openjpa.orm.xsd in the document header and openjpa can validate the document. However this will prevent the application to be portable to other providers. Albert Lee. On 1/24/07, Kevin Sutter <[EMAIL PROT

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

tp://java.sun.com/xml/ns/persistence/orm_1_0.xsd";> Albert Lee

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

One needs to update the xsi:schemaLocation to point to an valid location of openjpa_orm_1_0.xsd) Albert Lee On 1/22/07, Craig L Russell < [EMAIL PROTECTED]> wrote: If there is a way to include schema-validation="true" when parsing the orm, I expect that this will throw an exc

default value in persistence unit.

clude 4) --> default to "false" --> NOT to exclude If this is the intention of the spec, syntax is in contradiction to mean exclude unlisted classes semantics in the sample. Should the schema default to "true"? Is this the correct interpretation? Or what have I missed? Albert Lee.