[jboss-jira] [JBoss JIRA] (WFLY-6441) naming context is not setup when starting the persistence unit
Scott Marlow (JIRA)
issues at jboss.org
Wed Mar 30 09:51:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Marlow moved JBEAP-3999 to WFLY-6441:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6441 (was: JBEAP-3999)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JPA / Hibernate
(was: JPA / Hibernate)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 10.0.0.Final
9.0.2.Final
JBoss AS7 7.2.0.Final
JBoss AS7 7.1.1.Final
(was: 7.0.0.GA)
> naming context is not setup when starting the persistence unit
> --------------------------------------------------------------
>
> Key: WFLY-6441
> URL: https://issues.jboss.org/browse/WFLY-6441
> Project: WildFly
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final, 9.0.2.Final, JBoss AS7 7.2.0.Final, JBoss AS7 7.1.1.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> ookup of env-entry throws NameNotFoundException during persistence unit startup
> Version-Release number of selected component (if applicable):
> How reproducible:
> always
> Steps to Reproduce:
> 1. add env-entry in application.xml
> 2. try to lookup during persistent unit startup, e.g.
> public class MyType implements UserType {
> ...
> @Override
> public int[] sqlTypes() {
> try {
> Object ctx = new InitialContext().lookup("java:app/env");
> log.info("java:app/env from JPA = " + ctx);
> } catch (Exception e) {
> log.error("unable to get java:app/env from JPA", e);
> }
> return new int[] { Types.VARCHAR };
> }
> Actual results:
> NameNotFoundException
> Expected results:
> value of env-entry is available
> Additional info:
> On 21.03.2016 23:47, Stuart Douglas wrote:
> > This should fix it (I think): https://github.com/stuartwdouglas/wildfly/tree/jpa-java-namespace
> >
> > Stuart
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list