Re: [eclipselink-dev] EclipseLink 1.1.0

[Gordon Yorke <gordon.yorke@xxxxxxxxxx>]

Yes @JoinColumn and no "mappedBy" marks the OneToMany as unidirectional.

@OneToMany
@JoinColumn(name="CUST_ID") // join column is in table for Order
public Set<Order> getOrders() {return orders;}

--Gordon

Andrei Shakirin wrote:
> Hi All,
>
> This feature looks very promising:
> "Enhancements in JPA include:
>  - a new 1:M mapping without that doesn't require a back pointer or a separate join table to hold the associations."
>
> Is there any sample how to implement unidirectional 1:M without join table?
> Is it possible to use @JoinColumn for it?
> Unfortunatelly my trying was not successful.
>
> Regards,
> Andrei Shakirin.
>
> -----Original Message-----
> From: eclipselink-dev-bounces@xxxxxxxxxxx [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter Krogh
> Sent: Donnerstag, 12. März 2009 19:51
> To: eclipselink-users@xxxxxxxxxxx; eclipselink-dev@xxxxxxxxxxx
> Subject: [eclipselink-dev] EclipseLink 1.1.0
>
> Hi All,
>
> I am happy to announce that EclipseLink 1.1.0 is now complete and available for download here:  www.eclipse.org/eclipselink/downloads .  
>
> There are some useful links off of the download page including a 'getting started page', and the 'release notes' for 1.1.0.
>
> As well as bug fixes, 1.1.0 introduces feature enhancements in the following areas:
>
> First release of DBWS
> The first release of EclipseLink DBWS allows developers to easily and efficiently expose database constructs (tables, SQL, stored procedures). 
>
> Enhancements in JPA include:
>  - a new 1:M mapping without that doesn't require a back pointer or a separate join table to hold the associations. 
>
>  - TABLE_PER_CLASS Inheritance has been added giving greater flexibility in how your relational tables associate with the classes in a hierarchy. 
>
> Enhancements in SDO include:
> This release of EclipseLink includes an implementation of SDO 2.1.1 (JSR 235). This implementation conforms to the final draft and is being included with the final draft as the reference implementation. 
>
> Also I would like to say, thanks to everyone involved for all the hard work in putting this together.  
>
> Peter Krogh and Doug Clarke
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
>