Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3DA4811E0E for ; Tue, 13 May 2014 12:21:19 +0000 (UTC) Received: (qmail 13981 invoked by uid 500); 10 May 2014 22:12:30 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 13653 invoked by uid 500); 10 May 2014 22:12:30 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 13445 invoked by uid 99); 10 May 2014 22:12:30 -0000 Received: from Unknown (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 May 2014 22:12:30 +0000 Date: Sat, 10 May 2014 22:12:30 +0000 (UTC) From: "Suresh (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OPENJPA-2500) EJB Transaction Supports attribute causing JPA lazy fetching fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh updated OPENJPA-2500: ---------------------------- Summary: EJB Transaction Supports attribute causing JPA lazy fetching fails (was: EJB Transaction Supports causing JPA lazy Fetching fails) > EJB Transaction Supports attribute causing JPA lazy fetching fails > ------------------------------------------------------------------ > > Key: OPENJPA-2500 > URL: https://issues.apache.org/jira/browse/OPENJPA-2500 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 2.2.2 > Environment: windows 7, Weblogic 10.3.4(11g), SOAPUI 2.3.4, Java 1.6.0.30, EJB 3.0 > Reporter: Suresh > Priority: Minor > > I have an Enterprise Java Bean (EJB) called "A" and method called loadData with EJB "A". > loadData method is marked with Supports Transaction attribute. > loadData method tries to load Employee Data from JPA domain and further lazy fetches Department data and Employee Address Details. > The response has only Employee Data and does not have Department data and Employee Address Details. > If I change EJB method "A" Transaction attribute to Required then all details appear in the response. > Why is Transaction attribute Supports causing JPA lazy fetching fails? -- This message was sent by Atlassian JIRA (v6.2#6252)