Return-Path: 
 <dev-return-5674-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org>
Delivered-To: apmail-openjpa-dev-archive@www.apache.org
Received: (qmail 85896 invoked from network); 20 Aug 2007 18:31:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 20 Aug 2007 18:31:12 -0000
Received: (qmail 38443 invoked by uid 500); 20 Aug 2007 18:31:09 -0000
Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org
Received: (qmail 38294 invoked by uid 500); 20 Aug 2007 18:31:08 -0000
Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@openjpa.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@openjpa.apache.org>
List-Post: <mailto:dev@openjpa.apache.org>
List-Id: <dev.openjpa.apache.org>
Reply-To: dev@openjpa.apache.org
Delivered-To: mailing list dev@openjpa.apache.org
Received: (qmail 38285 invoked by uid 99); 20 Aug 2007 18:31:08 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2007 11:31:08 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of ppoddar@bea.com designates
 66.248.192.39 as permitted sender)
Received: from [66.248.192.39] (HELO repmmg02.bea.com) (66.248.192.39)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2007 18:31:37 +0000
Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71])
	by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l7KIUgAT019814;
	Mon, 20 Aug 2007 11:30:42 -0700
Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98])
	by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l7KIUeFe017225;
	Mon, 20 Aug 2007 11:30:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7E358.35EBFD3F"
Subject: RE: Question about lists in fluid / xsd
Date: Mon, 20 Aug 2007 11:29:07 -0700
Message-ID: <3992B07C0590B548BB294D31768A1DA260B6F5@repbex01.amer.bea.com>
In-Reply-To: <00042F5A391A1541AA939DEC06CEE7FF899BFA@EX01.QNH.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question about lists in fluid / xsd
Thread-Index: AcfjLsSRL2E4TZC+Tbeegli/oP8u1wAJe/Xg
References: <00042F5A391A1541AA939DEC06CEE7FF899BFA@EX01.QNH.local>
From: "Pinaki Poddar" <ppoddar@bea.com>
To: "Rutger Lubbers" <Rutger.Lubbers@qnh.nl>
Cc: <tuscany-dev@ws.apache.org>, <dev@openjpa.apache.org>
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Virus-Checked: Checked by ClamAV on apache.org

------_=_NextPart_001_01C7E358.35EBFD3F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Rutger,
> I've just started using fluid to generate domain objects and fluid
looks like a very nice package for this :-)

  
  Thank you.
 
 
You are right about the restrictins in generating list of complex types.
It is a limitation of processing SDO properties in Fluid and not of
OpenJPA. My local sandbox copy of Fluid generates mapping for
List<String>. I will update a version in the website (can not do it now
because I have broken some other things :).
 
  If this is support is urgent for you, you can patch
src/main/java/org/apache/openjpa/sdo/mapping/PrimitiveListMapping.java
as follows:
 
        public String getFieldTypeName() {
-               return "java.util.List<" +
-                       ImplHelper.getComponentType(property.getType()).
-                       getInstanceClass().getName() + ">";
+               Type elementType =
ImplHelper.getComponentType(property.getType());
+               if (elementType==null)
+                       elementType = property.getType();
+               return  "java.util.List<" +
elementType.getInstanceClass().getName() + ">";
        }
 
 
  FYI, in the next version Fluid will support dynamic bytecode
generation such that no intermediate code generation will be required.
 
  
 
 
Pinaki Poddar 
972.834.2865 
 


________________________________

	From: Rutger Lubbers [mailto:Rutger.Lubbers@qnh.nl] 
	Sent: Monday, August 20, 2007 8:34 AM
	To: Pinaki Poddar
	Subject: Question about lists in fluid / xsd
	
	

	Hi Pinaki,

	 

	I've just started using fluid to generate domain objects and
fluid looks like a very nice package for this :-)

	 

	A small question about the xsd that fluid (openJPA?) accepts.

	It accepts a complex type as a definition of a list, but it does
not allow a primitive type to be defined as a list. 

	I mean, that it does accept:

	    <xs:element name="authors" >

	            <xs:complexType>

	              <xs:sequence>

	                        <xs:element name="authorName"
type="xs:string" minOccurs="1" maxOccurs="unbounded"/>

	              </xs:sequence>

	            </xs:complexType>

	    </xs:element>

	And does not accept:

	   <xs:element name="authors" type="xs:string" minOccurs="1"
maxOccurs="unbounded"/>

	 

	Is there a reason for this? (I haven't been able to dig deeper
into this, but it looks like the type mapping generated returns a null
implementation for the type of this list...)

	 

	Why this question? The last one is a bit easier to model :-)

	 

	Thanks & Kind Regards,

	 

	Rutger Lubbers

	 


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
------_=_NextPart_001_01C7E358.35EBFD3F--